[OpenSIPS-Users] Load balancer probing from incorrect interface

[Bill W]

Hey Bogdan,

Yes, I have 3 listen= lines; two with public IPs and one with a private IP.

When I remove the mhomed=1 then things work as intended except for the 
probing.  I can proxy traffic correctly on all interfaces.

When I enable mhomed=1, then I get the errors below.

Thanks,
Bill


On 11/10/2010 5:38 AM, Bogdan-Andrei Iancu wrote:
> Hi Bill,
>
> is your opensips actually listening (configured as listener in .cfg) on
> a interface in the private network (where the probing needs to be done) ??
>
> Regards,
> Bogdan
>
> Bill W wrote:
>> Hey Bogdan,
>>
>> I enabled the mhomed=1 parameter, and now I'm getting a bunch of
>> errors in the logs.
>>
>> ERROR:tm:t_uac: no socket found
>> ERROR:load_balancer:lb_do_probing: probing failed
>> ERROR:core:get_out_socket: no socket found
>> ERROR:tm:uri2sock: no corresponding socket for af 2
>>
>> Thoughts?
>>
>> Bill
>>
>>
>> On 11/8/2010 6:05 AM, Bogdan-Andrei Iancu wrote:
>>> Hi Bill,
>>>
>>> as you have a multi interface system, have you tried to enable the
>>> "mhomed" global parameter?
>>> http://www.opensips.org/Resources/DocsCoreFcn16#toc60
>>>
>>> Regards,
>>> Bogdan
>>>
>>> Bill W. wrote:
>>>> As an update, the load balancer probe appears to use the ip address
>>>> specified by the first listen= directive.
>>>>
>>>> If I list the public IP first, then the probe tries to talk to the
>>>> internal IP from the external interface IP.
>>>>
>>>>
>>>> On 11/7/10 6:18 PM, Bill W. wrote:
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> I've got an opensips-1.6.3-tls installation using multiple interfaces
>>>>> and load balancing.
>>>>>
>>>>> My internal interface is rfc1918 space and my external interface has
>>>>> public IPs.
>>>>> listen=udp:10.0.10.3:5060
>>>>> listen=udp:66.180.205.3:5060
>>>>>
>>>>>
>>>>> I have the following load_balancer configuration:
>>>>> id | group_id | dst_uri | probe_mode
>>>>> ----+----------+-------------------+------------
>>>>> 1 | 1 | sip:66.180.205.11 | 2
>>>>> 2 | 1 | sip:66.180.205.12 | 2
>>>>> 3 | 2 | sip:10.0.10.1 | 2
>>>>> 4 | 2 | sip:10.0.10.2 | 2
>>>>>
>>>>>
>>>>> What's happening is that the load balancer is trying to probe the
>>>>> public
>>>>> IPs from the private interface IP (and failing of course).
>>>>>
>>>>> tcpdump output on internal interface:
>>>>> 18:13:26.471734 IP 10.0.10.3.5060> 66.180.205.11.5060: SIP, length:
>>>>> 18:13:28.473802 IP 10.0.10.3.5060> 66.180.205.11.5060: SIP, length:
>>>>>
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Thanks,
>>>>> Bill
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>