Show all posts by user
Discussions in Spanish
Page 1 of 1 Pages: 1
Results 1 - 9 of 9
thanks for the reply.
indeed, we are generating the split_clients directive on the host it's running.
by
larsg
-
Nginx Mailing List - English
Hi!
is it possible to use an hostname from local /etc/hosts as proxy_bind value?
In our current
Background:
We use nginx 1.8.1 as reverse proxy.
In order to overcome the "Overcoming Ephemeral Port Exhaustion" problem (64k+ connections), we use proxy_bind to iterate over all loccally available IP addresses and assign them as source IP (see https://www.nginx.com/blog/overcoming-ep
by
larsg
-
Nginx Mailing List - English
Hi Guys,
we solved the problem and I wanted to give you feedback about the solution.
Finally it was an problem with our linux ip routes.
After implementing source based policy routing this nginx configuration worked.
Thank you for your support!
Kind Regards
Lars
Summary of Solution:
split_clients "${remote_addr}${remote_port}AAAA" $source_ip {
10% 192.168.1.130;
1
by
larsg
-
Nginx Mailing List - English
Hi Reinis,
yes, IPs exist:
ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.130 netmask 255.255.255.0 broadcast 192.168.1.255
ether fa:16:3e:1e:ad:da txqueuelen 1000 (Ethernet)
...
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.131 netmask 255.255.255.0 broadcast 192.168.1.255
oka
by
larsg
-
Nginx Mailing List - English
Hi everybody,
ok, I recognized another linux network problem that I solved now. Situation now is like following:
When I call my upstream address via curl (on the nginx host) by selecting the corresponding local interface (eth0-9 = 192.168.1.130-139) everything is fine.
curl https://192.168.1.21:443/remote/events --insecure --interface eth0
But when I specify the same IP address that
by
larsg
-
Nginx Mailing List - English
Thanks for the advice.
I implemented this approach. Unfortunately not with 100% success.
When enabling sysctl option "net.ipv4.ip_nonlocal_bind = 1" it is possible to use local IP addresses (192.168.1.130-139) as proxy_bind address.
But than using such an address (other than 0.0.0.0), nginx will produce an error message.
Interesting aspect is: attribute "server" in the lo
by
larsg
-
Nginx Mailing List - English
Hi,
we are operating native nginx 1.8.1 on RHEL as a reverse proxy.
The nginx routes requests to a backend server that can be reached from the proxy via a single internal IP address.
We have to support a large number of concurrent websocket connections - say 100k to 500k.
As we don't want to increase the number of proxy instances (with different IPs) and we cannot use the "proxy_bind
by
larsg
-
Nginx Mailing List - English
Hi,
I want to use nginx as reverse proxy for an A/B testing scenario.
The nginx should route to two versions of one backend service. The two versions provides this service via different URL paths.
Example:
* x% of all requests https://edgeservice/myservice should be routed to https://1.2.3.4/myservice,
* the other 100-x% should be routed to https://4.3.2.1/myservice/withAnothePath.
F
by
larsg
-
Nginx Mailing List - English