How about using

split_clients "${remote_addr}AAA" $proxy_ip {
10% 192.168.1.10;
10% 192.168.1.11;
...
* 192.168.1.19;
}

proxy_bind $proxy_ip;

where $proxy_ip is populated via split clients module to spread the
traffic to 10 internal IPs.

or add 10 new listener ports (or ips) to your backend server instead,
(and perhaps use least connected load balancing) in upstream {} set of
10 backends. eg:

upstream backend {
least_conn;
server 192.168.1.21:443;
server 192.168.1.21:444;
server 192.168.1.21:445;
server 192.168.1.21:446;
server 192.168.1.21:447;
server 192.168.1.21:448;
server 192.168.1.21:449;
server 192.168.1.21:450;
server 192.168.1.21:451;
server 192.168.1.21:452;
}




On Tue, Mar 7, 2017 at 1:21 PM, Rainer Duffner <rainer@ultra-secure.de> wrote:
>
> Am 07.03.2017 um 22:12 schrieb Nelson Marcos <nelsonmarcos@gmail.com>:
>
> Do you really need to use different source ips or it's a solution that you
> picked?
>
> Also, is it a option to set the keepalive option in your upstream configure
> section?
> http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive
>
>
>
>
> I’m not sure if you can proxy web socket connections like http-connections.
>
> After all, they are persistent (hence the large number of connections).
>
> Why can’t you (OP) do the upgrade to 1.10? I thought it’s the only
> „supported" version anyway?
>
>
>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx