[SR-Users] forcing socket doesn't work for ACK

[Fred Posner]

The way I've always done this for things like AWS or natted is to use 
one ip/port and advertise the external address and then if I have 
another ip use that for internal... if I only have one IP, use a 
different port.

Example 1:

listen=udp:192.168.25.31:5060 advertise 1.2.3.4:5060 #-- Public Socket
listen=udp:192.168.25.33:5060 #-- Private Socket

Example 2:

listen=udp:192.168.25.31:5060 advertise 1.2.3.4:5060 #-- Public Socket
listen=udp:192.168.25.31:5080 #-- Private Socket

Fred Posner
fred at qxork.com
https://qxork.com
Direct/SMS: +1 (224) 334-3733
Direct/SMS: +1 (336) 439-3733

Need Fred? Call Fred. 336-HEY-FRED
Matrix: @fred:matrix.lod.com

On 4/1/19 3:26 PM, Antony Stone wrote:
> On Monday 01 April 2019 at 21:19:13, David Villasmil wrote:
> 
>> point taken.
>>
>> But if i do have two separate interfaces, i would still have the same
>> issue, wouldn't i?
> 
> No, because (unless AWS works in some totally strange way that I can't imagine
> being the case) the two interfaces would have different IPs and different
> routes, and only one would be your default route to the Internet (ie: public
> IP addresses).
> 
> Then your "internal" machines would connect to the IP on an interface which
> only routes back to them and can't see the Internet, and public connections
> would come in to a different IP on another interface which can route back to
> them.
> 
> Someone with personal familiarity with AWS systems may be able to inject a
> more definite answer here.
> 
> 
> Antony.
> 
>> On Mon, Apr 1, 2019 at 8:17 PM Antony Stone wrote:
>>>
>>> Do you prefer to ask "how can I make this strange networking setup
>>> operate?"
>>> or "how can I arrange my networking so that this service works?"
>