| Summary: | ASTERISK-07127: [post 1.4] even though asterisk binds to 0.0.0.0 it wont allow IAX client registration to eth alias | ||
| Reporter: | barthek (barthek) | Labels: | |
| Date Opened: | 2006-06-08 11:21:15 | Date Closed: | 2006-07-11 16:28:07 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | my config: linux gentoo running kernel 2.6.15, primary eth0 interface with IP address x.x.x.51 and its alias (eth0:1) having address x.x.x.52. scenario 1: with default bindaddr (0.0.0.0) option I am unable to register to asterisk with iax client using IP .52.( I get time outs). I am successful with .51 though. scenario 2: after changing bindaddr to .52 I am able to register OK. ****** ADDITIONAL INFORMATION ****** it seems asterisk does not react at all to the arriving packets in scenario 1; even though I see the packets with tcpdump, there is no sign in asterisk of any action taken | ||
| Comments: | By: Joshua C. Colp (jcolp) 2006-06-09 11:12:40 I've labbed this up and I know why it's happening... it's just a question of the best way to fix it. I'll explain what's happening (at least in my lab environment) Box 1 sends NEW to Box 2, received on eth0:1 (192.168.2.66) Box 2 sends ANSWER to Box 1, gets sent on eth0 (192.168.2.4) Box 1 refuses to accept the packet because source IP address (192.168.2.4) is not that of where it was sent (192.168.2.66). Box 1 sends back an INVAL to Box 2. And the exchange thereafter kind of goes down hill. I'll poke through and see if there is anything I can do. By: Brian West (bkw918) 2006-06-09 11:46:06 This was reported almost two years ago by anthm on bug 2611 and he and I both agree this is a Major bug and a flaw not only in IAX but SIP suffers the same fate. /b By: Joshua C. Colp (jcolp) 2006-06-09 12:05:54 The easiest way to make this work (which I tested) is to explicitly bind to each IP address like so: bindport=4569 bindaddr=192.168.2.4 bindport=4569 bindaddr=192.168.2.66 By: Brian West (bkw918) 2006-06-10 12:20:59 You shouldn't have to do this. Also you can do bindaddr=ip:port /b By: Serge Vecher (serge-v) 2006-06-12 19:17:46 alright, well since there is "existing behavior" for 1.2 that can be used, moving this issue to trunk-one. Anybody willing to contribute code? By: Joshua C. Colp (jcolp) 2006-07-11 16:28:06 Well, since nobody has outright volunteered... closing this, although we have ideas on how to accomplish this so it may happen. | ||