Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#590 DISPATCHER. Commit #9448 breaks dispatcher pings

trunk
closed-invalid
modules (454)
5
2013-01-15
2012-11-27
Nick Altmann
No

After this commit dispatcher pings are going from incorrect interface on multihomed opensips.

Discussion

  • Hello Nick,

    Could you please give us a little more information about your setup and scenario ?

    Regards,
    Vlad

     
    • assigned_to: nobody --> vladut-paiu
     
  • Nick Altmann
    Nick Altmann
    2012-11-28

    Common setup, dispatcher module with hosts from RFC1918 network and hosts from external network. Two network interfaces - internal and external. Before this commit internal gateways pings from internal ip, external pings from external ip. After commit it tries to send packets to external gateways from internal interface.

     
  • Nick,

    1) do you set any socket info in the dispatcher table for the destinations you are probing ?

    2) do you have the mhomed parameter enabled in core ?

    3) do you see in logs any ERRORs related to dispatcher probing ?

    Regards,
    Bogdan

     
  • Nick Altmann
    Nick Altmann
    2012-12-18

    1, Only destination like sip:8.8.8.8:5060;transport=udp, socket column is empty.
    2. mhomed=yes
    3. No errors in log.

    Before patch OPTIONS go from external interface, after patch they're go from internal.

     
  • Nick,

    I was not able to replicate your case - using trunk, once the mhomed is enabled, the correct outbound interface is used.
    So are you sure mhomed is used?

    Regards,
    Bogdan

     
  • it proved to be configuration error.

     
    • status: open --> closed-invalid