@eschmidbauer IMHO the underlying issue is that there exists several ways how this proxy feature could be used. I will borrow some terms from IP LVS here to make it clear link.

The way I see it implemented in tcp_accept_haproxy is the "direct routing" type. This load balancer does not stay in the path, they hand-down the session to the real server(s). This usally works (at least in IPS) that the real server has a (non-arp) virtual IP address that it shares with the balancer. Therefore it can send the packet with the correct IP and port back directly to the user. The real server needs to get transparently get all the incoming IP and port information, and this is what the proxy protocol implementation in Kamailio is providing.

What Joel and also you are suggesting is another one, the "NAT Routing" type. Here the load balancer stays in the path and the real server uses a different IP address as the balancer. The real server is will be always behind the balancer.

I would suggest to keep the discussion in this feature request to the two additional PVs. If you want to discuss the "NAT routing" balancing type, please open a new issue or write an e-mail to sr-dev.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.