### Description

I would like to implement support for the Proxy Protocol as implemented by 
HAProxy and AWS ELBs. The main advantage this brings is better connection 
information, even behind multiple layers of NAT or LBs. This feature was 
already discussed a couple of years ago, and it appears the project was not 
against receiving a patch that adds support for this protocol: 
https://lists.kamailio.org/pipermail/sr-users/2016-June/093497.html

For example, at the moment, my Kamailio deployment is "blind" when it comes to 
the origin of inbound TCP connections, because it is only able to report the 
internal IP address of our ELBs, rather than the actual IP address of the 
client, and IP address of the LB the connection was received on. Dixa is 
offering to sponsor work (my own hours) to implement this, and we would also be 
a production user of this feature.

The Proxy Protocol is fairly well documented here: 
https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt

As far as I know, AWS ELBs only implement version 1 of the protocol, but I 
believe there is value in implementing both (while we're at it), and the second 
version of the protocol is a lot easier to parse, anyway.

I'm opening this feature request to a/ track progress, b/ discuss 
implementation details.

-- 
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/1757
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to