<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">So on your AWS deployment are you working without ANTIFLOOD(pike)?<br />
<br />
I still don’t understand how and why to use tcp_accept_haproxy.</div>
</div>
<div name="messageReplySection">On 9 Nov 2020, 11:49 +0200, Sergey Safarov <s.safarov@gmail.com>, wrote:<br />
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">
<div dir="ltr">In AWS I now use the network load balancer without enabled HAproxy protocol.
<div>On EC2 instances used two ENI.</div>
<div>First for traffic via NLB for Inbound traffic.</div>
<div>And second ENI for outbound traffic.</div>
<div><br /></div>
<div>This works but, maybe complex to implement.</div>
<div><br /></div>
<div>Now I looking to:</div>
<div>1) enable TCP + HAproxy protocol support in Kamailio;</div>
<div>2) add UDP + HAproxy protocol feature support;</div>
<div>3) add connection support "with" and "without" HAproxy protocol.</div>
<div><br /></div>
<div>But I am not a developer and cannot say when it implemented.</div>
<div><br /></div>
<div>If your usage case, is business requirements and need extended HAproxy implementation in Kamailio, then your company can hire devs from the community.</div>
<div><br /></div>
</div>
<br />
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Nov 9, 2020 at 11:22 AM Joey Golan <<a href="mailto:joeygo@gmail.com">joeygo@gmail.com</a>> wrote:<br /></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div name="messageBodySection">
<div dir="auto">Maybe I miss understood you.<br />
For local installations you mean HAProxy with transparent mode?<br />
<br />
I have a functioning setup without proxy protocol enabled but without anitflood enabled because all traffic comes from same HAProxy address.<br />
<br />
I’m not sure I understand the purpose of tcp_accept_haproxy. When and how this parameter should be used?<br />
<br />
Thanks,<br />
Joey.</div>
</div>
<div name="messageReplySection">On 9 Nov 2020, 0:27 +0200, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" target="_blank">s.safarov@gmail.com</a>>, wrote:<br />
<blockquote type="cite" style="border-left:thin solid grey;margin:5px;padding-left:10px">
<div dir="ltr">Why you cannot use this in the local installation?
<div><br /></div>
<div>On AWS I have multiple kamailio servers behind ELB.<br /></div>
<div><br /></div>
<div>Why you do not use a network load-balancer? NLB also offers HAproxy protocol support (TCP and UDP).</div>
<div><br /></div>
<div>In AWS installation you can use dedicated Kamailio groups for inbound connections and SIP clients with registration.</div>
<div>And use other Kamailio group for outbound connections like carriers.</div>
<div><br />
Sergey</div>
</div>
<br />
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Nov 8, 2020 at 9:07 PM Joey Golan <<a href="mailto:joeygo@gmail.com" target="_blank">joeygo@gmail.com</a>> wrote:<br /></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div name="messageBodySection">
<div dir="auto">It doesn’t make much sense to me. <br />
On local installations (on-premise) I have 1 HAProxy and multiple kamailio servers.<br />
On AWS I have multiple kamailio servers behind ELB.</div>
</div>
<div name="messageReplySection">On 8 Nov 2020, 19:45 +0200, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" target="_blank">s.safarov@gmail.com</a>>, wrote:<br />
<blockquote type="cite" style="border-left:thin solid grey;margin:5px;padding-left:10px">
<div dir="ltr">you can try place haproxy + NAT on your own Linux router.
<div>In this case inbound connections with be delivered via HAproxy.<br />
Outbound connections will be NAT-ed on the same host, to the same IP.</div>
</div>
<br />
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, Nov 8, 2020 at 6:31 PM Joey Golan <<a href="mailto:joeygo@gmail.com" target="_blank">joeygo@gmail.com</a>> wrote:<br /></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div name="messageBodySection">
<div dir="auto">Hello,<br />
I have a kamailio server running behind HAProxy with proxy protocol v2 enabled.<br />
In Kamailio I have set the parameter tcp_accept_haproxy=yes and loaded tcpops module.<br />
UEs are registered using TLS and kamailio sees that the message has received from their real ip address + port and not HAProxy ip + port.<br />
When UE A calls UE B, kamailio is trying to reach UE B using his real ip address and port instead of HAProxy IP address + port.<br />
<br />
I know I can get the tcp ip and port of HAProxy using $tcp(c_si) and $tcp(c_sp) but I can’t make it work.<br />
What is the right way to do this? How should I use these variables properly in order to establish the call successfully?<br />
<br />
Thanks,<br />
Joey.</div>
</div>
</div>
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br />
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br /></blockquote>
</div>
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br />
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br /></blockquote>
</div>
</div>
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br />
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br /></blockquote>
</div>
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br />
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br /></blockquote>
</div>
</div>
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br />
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br /></blockquote>
</div>
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
sr-users@lists.kamailio.org<br />
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users<br /></blockquote>
</div>
</body>
</html>