[SR-Users] t_relay changing source IP?

Wed Oct 27 17:26:05 CEST 2021

That is my understanding as well, and the current configuration works that way for 99.99% of the requests.  It's just the random occasional "glitch" where it tries to relay from the interface IP instead of the IP it came into.

I will take a look at the process and socket lists, but to be honest I don't think it's going to provide much insight.  This is a very intermittent issue, but frequent enough that it's causing issues.

-----Original Message-----
From: Henning Westerholt <hw at gilawa.com>
Sent: Tuesday, October 26, 2021 10:27 PM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
Cc: Brooks Bridges <bbridges at call48.com>
Subject: RE: [SR-Users] t_relay changing source IP?

Hello,

in case of UDP Kamailio should use the process which received the message to also send it out (if you do not use anything like forcing a particular send socket or multi-homed).

Anything unusual if you look e.g. with "kamcmd corex.list_sockets" ? Which Kamailio processes are processing the messages, e.g., if you compare the Kamailio log pid with the "kamcmd ps" output?

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com

-----Original Message-----
From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of Brooks Bridges
Sent: Tuesday, October 26, 2021 5:00 PM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
Subject: Re: [SR-Users] t_relay changing source IP?

We are using UDP everywhere currently.  TCP is on the roadmap, but not implemented yet except for xhttp_rpc communication.

-----Original Message-----
From: Daniel-Constantin Mierla <miconda at gmail.com>
Sent: Monday, October 25, 2021 11:29 PM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>; Brooks Bridges <bbridges at call48.com>
Subject: Re: [SR-Users] t_relay changing source IP?

Hello,

what is the outgoing transport protocol? UDP or TCP/TLS?

Cheers,
Daniel

On 26.10.21 00:51, Brooks Bridges wrote:
> apologies, I missed the second half of your post.  We do not, and I know I could explicitly tell it to use that IP, however I am more interested in figuring out what might cause it to decide to use the interface IP, seemingly without a clear reason.  I am not a fan of static configuration of things like that in shared environments.
>
> -----Original Message-----
> From: Brooks Bridges
> Sent: Monday, October 25, 2021 3:48 PM
> To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
> Subject: RE: [SR-Users] t_relay changing source IP?
>
> Correct.
>
> listen=lo:5060
> listen=eth0:5060
> listen=eth1:5060
> listen=XXX.XXX.XXX.XXX:5060  (<--- HA IP)
>
> -----Original Message-----
> From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of Alex
> Balashov
> Sent: Monday, October 25, 2021 3:35 PM
> To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
> Subject: Re: [SR-Users] t_relay changing source IP?
>
> I take it you have listeners on both the interface IP and the HA IP?
>
> Absent ‘mhomed=1’, do you regulate egress interface selection for all t_relay() cases with $fs explicitly? If not, try that.
>
>> On Oct 25, 2021, at 6:25 PM, Brooks Bridges <bbridges at call48.com> wrote:
>>
>> That's been set to 0 since inception and this has just recently become an issue.
>>
>> -----Original Message-----
>> From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of
>> Alex Balashov
>> Sent: Monday, October 25, 2021 3:19 PM
>> To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
>> Subject: Re: [SR-Users] t_relay changing source IP?
>>
>> Does the behaviour differ depending on whether ‘mhomed’ is on?
>>
>> https://www.kamailio.org/wiki/cookbooks/5.5.x/core#mhomed
>>
>>> On Oct 25, 2021, at 6:15 PM, Brooks Bridges <bbridges at call48.com> wrote:
>>>
>>> So we have a box that's bound to all interfaces on the server, and one specific IP address (that is an HA IP), and I've run into a bit of an odd behavior that I cannot explain.
>>>
>>> For 99.9999% of our traffic, the invites come into the HA IP, and then are forwareded out the HA IP to an SBC for further processing.  In a very rare instance however, I have found that there is an invite coming in the HA IP, and for some unknown reason it gets forwarded out the *interface* ip instead of the HA IP.
>>>
>>> For example:
>>>
>>> Working:
>>> 1.2.3.4 -- invite --> 9.8.7.6 (ha IP) -- invite --> 5.6.7.8 (sbc)
>>>
>>> Non working:
>>> 1.2.3.4 -- invite --> 9.8.7.6 (ha IP) *something happens here*
>>> 9.8.7.5 (interface IP) -- invite --> 5.6.7.8 (sbc)
>>>
>>> I've been through tm, tmx, and the incoming invite of a working and non working request with a fine toothed comb and I cannot for the life of me explain this behavior.  Any thoughts?
>>> Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.
>>>
>>> __________________________________________________________
>>> Kamailio - Users Mailing List - Non Commercial Discussions
>>> * sr-users at lists.kamailio.org
>>> Important: keep the mailing list in the recipients, do not reply only to the sender!
>>> Edit mailing list options or unsubscribe:
>>> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> --
>> Alex Balashov | Principal | Evariste Systems LLC
>>
>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>>
>>
>> __________________________________________________________
>> Kamailio - Users Mailing List - Non Commercial Discussions
>>  * sr-users at lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to the sender!
>> Edit mailing list options or unsubscribe:
>>  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.
>> __________________________________________________________
>> Kamailio - Users Mailing List - Non Commercial Discussions
>>  * sr-users at lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to the sender!
>> Edit mailing list options or unsubscribe:
>>  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> --
> Alex Balashov | Principal | Evariste Systems LLC
>
> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
>   * sr-users at lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the sender!
> Edit mailing list options or unsubscribe:
>   * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
>   * sr-users at lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the sender!
> Edit mailing list options or unsubscribe:
>   * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--
Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone)
  * https://www.asipto.com/sw/kamailio-advanced-training-online/

Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
  * sr-users at lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
  * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.