Open pipozzz opened 4 years ago
If my understanding is correct, this is NOT a duplicate of #1971 or #2241 .
Because ProxySQL is behind a TCP load balancer, to me this request makes sense!
Unfortunately it looks like a duplicate:
So I guess the FR are asking to implement support for proxy protocol and extracting source IP from incoming PROXY header, so that it could be used for whitelisting.
It is doable, for example it can be used with nginx to whitelist request which come in to AWS ELB on nginx level and not on AWS ELB net/security rules.
No, I need to use source IP in proxysql firewall whitelisting feature and have more granular option to whitelist certain mysql user from certain IP/subnet to run queries and this proxysql is behind ELB.
Any update?
Any update?
Reopening, because we may work on it sometime in the future
Hi, Looks like there are some conflicts in the merge, so fix is still not available. Is there any plan to take this fix?
We have the same use case -> our proxysql is behind load balancer and we'd like to be able to handle query rules based on actual client IP, right now all connections are 'seen' as originating from load balancer.
We also have a need for this feature, as we are planning to put our ProxySQL servers behind a TCP load balancer.
+1 this would be great to have
Hello,
is it possible to implement proxy_protocol on proxysql to see real remote IP of client ?
We would like to use new feature from v2.0.9 called firewall whitelist, but our proxysql servers are running behind TCP load balancer and we still see only load balancer's IP obviously.
Thank you.