Aleks, I'm really thank you for your timely response.
I checked "proxy_protocol on;" option is working fine and watched the L4
machine send proxy protocol header like "PROXY TCP4 [Ip1] [Ip2] [Port1]
[Port2]".
Really thank you.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,263299,26330
Hi WANJUNE.
Am 06-12-2015 07:14, schrieb WANJUNE:
In NginX reverse mode,
There is a problem that can't get real client's Ip address.
[snipp]
I don't want to use http ssl listen becase of SSL handshaking burden on
NginX.
I decided to use stream codec like below.
stream {
upstream aa34
In NginX reverse mode,
There is a problem that can't get real client's Ip address.
If I use Http protocol, I can simply handle this problem with below http
configuration.
http {
server {
listen 80;
location / {
proxy_set_header X-forwarded-for;
pro
Never mind - a new proxy target was misconfigured. Doh!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253313,253318#msg-253318
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Additional information: I caught it in the act, and something about this
trigger and the setup is causing nginx to loop - the client ip address is
actually right and nginx is proxying the request to itself as fast as it
can. Restarting nginx stops the loop. This is version 0.7.65. I tried
We have a cluster of 4 nginx proxies behind a piranha load balancer setup.
This morning we suffered a DOS attack, however the "client" address appears
to have only gotten logged correctly the first time, the rest have the
virtual ip address targeted as the "client", and it's unclear how or why
tha
That's very helpful info. Thanks!
So getsockname() and getpeername() returns the initial subflow, what's the
API to get other subflows?
Edit: found my answer:
https://datatracker.ietf.org/doc/rfc6897/?include_text=1 by
using setsockopt() and getsockopt()
The functions getpeername() and getsockna
Hi,
> Since iOS7 supports TCP Multipath now, I think more and more devices
> will start support it.
Not if the servers don't support it.
Apple pushed for a specific reason:
To avoid having a broken TCP session when the IP address of the handheld
changes, which would interrupt Apple's Siri.
But
Hello,
Since iOS7 supports TCP Multipath now, I think more and more devices will
start support it.
But TCP Multipath allows many client IPs connected to the same server,
suppose Nginx in this case, how would access_log record all of the IPs?
Just curious question :)
_
