[reSIProcate] (DNS lookup) How to use specified NIC interface for outgoing request in dual nic machine?

[Jason Fischl]

As Byron says, the approach here is to populate the topmost via with a
specific ip address for the interface you want to use. If you don't specify,
it will let the kernel choose.

Jason


On Wed, Mar 26, 2008 at 3:24 PM, Byron Campen <bcampen at estacado.net> wrote:

> This is a tricky problem to solve, since there is no way (that I know of)
> to tell ::socket "Only use this set of IP addresses". About the only way to
> really solve it is to specify the ip you want the traffic to be sent on in
> the topmost Via of requests that you send (ie, set request.header(h_Vias).front().sentHost()="<your
> ip address>"). If you wish to restrict the stack from _receiving_ things on
> the other interface, you can pass your desired ip-address when you call
> SipStack::addTransport() (5th param).
>
> Best regards,
> Byron Campen
>
>
>
> Hi,
>
>   My server has dual NIC. Both nic interfaces are in same subnet. In other
> words, when the sipstack does dns look up for a destination, it can get
> either of NIC for transport interface.  So, when my server sends sip
> messages to wire, sip traffic appears in both NIC.
>
>   I want SIP message only appear from one particular NIC. (because the
> other NIC will only for admin or other purpose).
>
>    Is it possible to achieve this without changing sip stack code? If not,
> how?
>
>
>
> Thanks,
>
> Roland
>  ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from your
> system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20080326/d2eb90d4/attachment.htm>