Displaying 4 results from an estimated 4 matches for "mydestip".
2017 Mar 13
2
tcpbind and source IP address
...lication (chan_sip in this
> case)
> should request kernel to use the specific source IP address (used in bind
> directive) for outgoing packets, however it seems to be done only for
> UDP.
> For outgoing packets on TCP/5061 I see the following:
> IP *192.168.0.172*.47596 > <mydestip>.5061: Flags [S], seq 2529313754,
> win
> 29200, options [mss 1460,sackOK,TS val 82765588 ecr 0,nop,wscale 7],
> length
> 0
> And with UDP as transport:
> IP *192.168.0.177*.5060 > <mydestip>.5060: SIP: OPTIONS ....
The underlying code does this already. It connects u...
2017 Mar 13
2
tcpbind and source IP address
On Mon, Mar 13, 2017, at 03:52 AM, Kseniya Blashchuk wrote:
> Hi!
> Attached sip.conf and interface config as well. In this case we use only
> TLS, but I have checked with TCP - same situation, 192.168.0.172 is used
> as
> a source. For UDP 192.168.0.177 is used as expected.
Does the output of netstat -a confirm that it is bound to only that IP
address? If so, then it seems
2017 Mar 13
2
tcpbind and source IP address
...Mon, Mar 13, 2017, at 08:43 AM, Kseniya Blashchuk wrote:
> Mmh sorry I'm afraid I did not understand your last message. Yes the code
> does that but only with UDP, for TCP the source address is 192.168.0.172
> though it's bound to 192.168.0.177:
> IP 192.168.0.172.47596 > <mydestip>.5061
> If it was a system/kernel issue, then why is the behavior different for
> TCP
> and UDP? I thought that maybe the application does not request the bound
> address as a source in case of TCP...
The chan_sip module, from looking at the code, does use the bound
address when con...
2017 Mar 13
2
tcpbind and source IP address
...t 08:43 AM, Kseniya Blashchuk wrote:
> > Mmh sorry I'm afraid I did not understand your last message. Yes the code
> > does that but only with UDP, for TCP the source address is 192.168.0.172
> > though it's bound to 192.168.0.177:
> > IP 192.168.0.172.47596 > <mydestip>.5061
> > If it was a system/kernel issue, then why is the behavior different for
> > TCP
> > and UDP? I thought that maybe the application does not request the bound
> > address as a source in case of TCP...
>
> The chan_sip module, from looking at the code, does u...