MySQL Server sees the ProxySQL IP and not the ClientsIP

As part of our POC we have ran into an “small” issue, where the MySQL (percona) server sees the IP of the ProxySQL node instead of the clientsIP, which then ofc result in access denied.

We have an LB in front of the ProxySQL, so the connection, looks like this.

MySQLClient→ LB→ProxySQL→MySQLNode(Percona)

Actually the issue is the same if I connect to the ProxySQL IP directly.
MySQLClient→ ProxySQL→MySQLNode(Percona)

What am I missing ?
For MySQL i’ve been looking at “proxy_protocol_networks” and for ProxySQL mysql-proxy_protocol_networks, but im not 100% sure this is what I want?

This is 100% correct, and expected. ProxySQL does not “forward” connections to backend MySQL servers. ProxySQL creates completely new connections, thus you will not see the client IP, you will see the IP of ProxySQL. Client connections connect to ProxySQL and the connection terminates there. A new, separate, connection is opened by ProxySQL to MySQL, and the queries from client are sent over this connection. This has always been the behavior of ProxySQL, and as far as I know, there is no way around this because ProxySQL can use that single backend connection to multiplex many different fronend clients.

Ok, I found this rather old thread, and it seems this will never be done. But a lot could have changed in the last ~ 6 years