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

[David Villasmil]

Hey Joel!

I’m using only one.
I will double-check that!

Thanks

David

On Tue, 2 Apr 2019 at 15:44, Joel Serrano <joel at textplus.com> wrote:

> David, out of curiosity, are you finally using only one listen= line or
> two in your AWS setup?
>
> More specific: are you only listening on one port with the ‘advertise’ set
> or are you finally listenting on two ports?
>
> If your are using one port only you might find yourself using egress
> (billed) traffic between your instances, so make sure in the captures your
> are really seeing your internal IP in the RR headers when talking to
> internal servers instead of the egress (public) IP.
>
> Thanks,
> Joel
>
> On Mon, Apr 1, 2019 at 13:54 David Villasmil <
> david.villasmil.work at gmail.com> wrote:
>
>> Well,
>>
>> As suggested, i decided to go with a single ip address.
>> Thanks everyone!
>>
>> Thanks to @Federico Cabiddu <federico.cabiddu at gmail.com> i understood
>> why the ACK has no $du. This is because all record-routes have been
>> consumed because this is the final hop.
>>
>> So no record-route, no $du. I have to use the ruri.
>>
>> Regards,
>>
>> David Villasmil
>> email: david.villasmil.work at gmail.com
>> phone: +34669448337
>>
>>
>> On Mon, Apr 1, 2019 at 8:38 PM David Villasmil <
>> david.villasmil.work at gmail.com> wrote:
>>
>>> actually that's a good point, the default gateway.
>>> But, ven if i have 2 different IPs, those 2 would still have direct
>>> contact with the private IPs.
>>>
>>>
>>>
>>> Regards,
>>>
>>> David Villasmil
>>> email: david.villasmil.work at gmail.com
>>> phone: +34669448337
>>>
>>>
>>> On Mon, Apr 1, 2019 at 8:27 PM Antony Stone <
>>> Antony.Stone at kamailio.open.source.it> 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?"
>>>>
>>>> --
>>>> There's a good theatrical performance about puns on in the West End.
>>>> It's a
>>>> play on words.
>>>>
>>>>                                                    Please reply to the
>>>> list;
>>>>                                                          please *don't*
>>>> CC me.
>>>>
>>>> _______________________________________________
>>>> Kamailio (SER) - Users Mailing List
>>>> sr-users at lists.kamailio.org
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-- 
Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190503/d5153e66/attachment.html>