Status: Accepted
Owner: jean.deruelle
Labels: Type-Defect Priority-Medium Component-JAIN-SIP
New issue 161 by jean.deruelle: NIO TCP uses incorrect local interface on
multihomed host
https://code.google.com/p/jain-sip/issues/detail?id=161
My product uses a server with two network interfaces, one for SIP and one
for management. SIP requests arrive at the server on the SIP interface,
where they are processed by a firewall application, then passed to the SIP
container on the management interface. Similarly, outgoing SIP requests
should leave the SIP container on the management interface, and arrive at
the firewall application on the SIP interface, which then sends the request
to the network on the SIP interface.
Using the Linux ss utility, I can see that the SIP container is opening a
socket on the SIP interface to the firewall application, also on the SIP
interface. This confuses the firewall application, as it identifies the
socket from the container by looking for a far end address that matches the
management interface
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
