@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](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/load_balancer_administration/s1-lvs-routing-vsa).
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 or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2103#issuecomment-543919438
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
