IAX bind to multiple IP's problem

Hi Guys,

Versions of Asterisk past 1.4.19 don't appear to bind to multiple IP's, only the first listed. Having searched the docs, I can't find anything that's really changed. Even setting the IP to 0.0.0.0 doesn't help. Anyone else come across this?

I should add that I can register to multiple IP's, it's just that I can't peer. If I only list 1 IP in iax.conf it works.

regards

Hi

What does

Quote:

netstat -aln |grep 4569

i have to say? as on 1.4.26 it binds as expected.
But dont forget its the first thats the default.
When using alias IP addreses I never set the real interface as one that its bound to.


Even going back to 1.2 it still works as per the release notes and samples. IE the first defined interface is the default

This is from 1.2.24

bindadd=internalip
bindadd=externalip

Code:

1229/1229        192.168.XX.11X (D)  255.255.255.255  4569          OK (4 ms) peer_out/se  193.XXX.XXX.98  (S)  255.255.255.255  4569          UNREACHABLE

bindadd=externalip
bindadd=internalip

Code:

1229/1229        192.168.XX.11X (D)  255.255.255.255  4569          UNREACHABLE peer_out/se  193.XXX.XXX.98  (S)  255.255.255.255  4569          OK (32 ms)

bindaddr=0.0.0.0

Code:

1229/1229        192.168.XX.11X  (D)  255.255.255.255  4569          OK (4 ms) peer_out/se  193.XXX.XXX.98  (S)  255.255.255.255  4569          OK (36 ms)

Ian

This is the output

udp 0 0 192.168.20.251:4569 0.0.0.0:*
udp 0 0 192.168.20.219:4569 0.0.0.0:*
udp 0 0 192.168.20.218:4569 0.0.0.0:*

If I NAT a public IP to 20.251 via a PIX it works, the remaining two do not work.

The remote * reports the host as UNREACHABLE

I do not have this issue with anything prior to 1.4.22

That said, registrations DO work just fine.

Quote:

When using alias IP addreses I never set the real interface as one that its bound to.

Not sure If I follow what you're saying here. I'm using virtual IP addresses for the local addresses.


This also looks interesting

Quote:

Yeah, the real issue with the IAX multi IP bind is not with incoming connections to the extra bind addresses, but with outgoing connections using the wrong address. The reason I use the bindaddr for IAX is to force the source IP for outgoing IAX connections to use the virtual IP and if you have 0.0.0.0 specified, IAX uses the NIC address of the outgoing interface

Further to my last, as a quick test I loaded 1.4.19.2, same config, and it WORKS! I can only assume therefore that post this version IAX on multiple virtual IP's is broken.

https://issues.asterisk.org/view.php?id=7315

Which is fairly old has been re-introduced in later versions.

regards

Hi

Quote:

I'm using virtual IP addresses for the local addresses.

Are you using a virtual IP address ? or are are you using alias addresses for a single nic. They are 2 similar but different things. Virual IPs are for load balancing a single IP over multiple machines and alias addresses are for multiple addresses on a single nic.

That aside 1.4.18.1 works as per the bug and hence not binding to the real nic address to allow it to work in a redundent configuration.

if it works in 1.4.19 the stick with it, your lucky.

SIP suffers from the same problem on some gateways.

Ian

You're right, the terminology is confusing. Webmin calls them virtual IP's, but using your words, they are alias's. Either way it's broke I don't have a problem with 19.2, but I'd really like to apply the security fixes in the later versions.

I have raised another bug report, but reading the old ones, it's not considered a real issue, which is surprising.

regards