[Home]

Summary:ASTERISK-08842: bindaddr=0.0.0.0 no bind to eth0:1
Reporter:german aracil boned (tecnoxarxa)Labels:
Date Opened:2007-02-19 11:28:58.000-0600Date Closed:2011-06-07 14:03:01
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) sipphoneregtoeth0_1_bindaddr235.cap
( 1) sipphoneregtoeth0_1.cap
( 2) sipphoneregtoeth0.cap
Description:When put bindaddr=0.0.0.0 on sip.conf, asterisk, listen on 0.0.0.0 but, interfaces like eth0:1 eth0:2, no listen. I can't register with this ip/interface from SIP client.

****** ADDITIONAL INFORMATION ******

If you put binaddr=x.x.x.x ip from eth0:1 interface, this asterisk work. But no for listen in all ips/interfaces.

Comments:By: Olle Johansson (oej) 2007-02-19 11:59:42.000-0600

You need to tell us much more in order for us to be able to help you. What operating system/distro, which version, what do you see when you list open ports for SIP etc etc.

By: Olle Johansson (oej) 2007-02-19 12:02:46.000-0600

Something that is not a bug can't be reported as MAJOR.

By: german aracil boned (tecnoxarxa) 2007-02-19 12:17:21.000-0600

More info:

Dist: Debian etch
Kernel pack.: Linux XXXXXX 2.6.18-3-686 #1 SMP Mon Dec 4 16:41:14 UTC 2006 i686 GNU/Linux

IPTABLES Empty.

eth0 with kernel module tg3

sip.conf:
If bindaddr=x.x.x.x (where x.x.x.x = ip of eth0:1) work if bindaddr = 0.0.0.0, eth0:1 no respond, no work, no listen.

NOTE: SERVICES HOW SSH WORK GOOD.



By: german aracil boned (tecnoxarxa) 2007-02-19 12:29:02.000-0600

Notes:

If I call function ast_ouraddrfor (acl.c), this return eth0 ip, no eth0:1 ip. If I call function ast_sip_ouraddrfor (chan_sip.c) YES ! I have correct ip. Ip of eth0:1 interface.

Thats the problem ? I need see it.

By: Olle Johansson (oej) 2007-02-19 12:34:08.000-0600

Which sip ports does your asterisk bind to?

By: german aracil boned (tecnoxarxa) 2007-02-20 04:35:58.000-0600

5060 UDP

Looking this problem..

I think, when sip client send message with register to asterisk server on port 5060 and ip of interface eth0:1, asterisk answer with ip of interface eth0.

with option (sip.conf) bindaddr=0.0.0.0
I like capture trace with Wireshark and in packet Trying, after Request REGISTER, on contact, Asterisk send 212.230.0.34 ip always. When I send Request REGISTER to 212.230.0.34 (eth0) or 212.230.0.35(eth0:1)
FILES: eth0 -> sipphoneregtoeth0.cap | eth0:1 -> sipphoneregtoeth0_1.cap

with option (sip.conf) bindaddr=212.230.0.35
I can send request REGISTER, and on packet, section contact, asterisk send 212.230.0.35
FILE: sipphoneregtoeth0_1_bindaddr235.cap

Any idea ?



By: Tilghman Lesher (tilghman) 2007-02-20 10:23:10.000-0600

You're doing multi-homed interfaces, and we use the routing table to decide what IP address to place on outgoing packets.  If your routing table does not select that IP network, then we won't use that address, plain and simple.

This is a feature request, and as such, it cannot remain on here more than a few days.  Please post your request to the Wiki, possibly with a bounty on the bounty page.

By: german aracil boned (tecnoxarxa) 2007-02-20 11:49:53.000-0600

Sorry. All ok

I add this line to route table:

route add defaut gw x.x.x.x eth0:1

and now, work fine. But other services was working without this line on eth0:1

By: Tilghman Lesher (tilghman) 2007-02-20 11:55:29.000-0600

How many of those services are UDP services, not TCP?

By: german aracil boned (tecnoxarxa) 2007-02-20 12:16:36.000-0600

none of this services are UDP. All services are TCP.

By: Russell Bryant (russell) 2007-02-20 16:52:25.000-0600

TCP services would not have this same issue.  :)

By: Olle Johansson (oej) 2007-02-21 02:34:48.000-0600

configuration issue