For various reasons that include Asterisk restrictions and Metaswitch restrictions, I've had to setup multiple IP addresses to talk to different partitions of a Metaswitch with Asterisk...
That means, for all practical purposes, my config looks like: /etc/hostname.em0: inet 10.10.10.2 255.255.255.0 NONE inet alias 10.10.10.3 255.255.255.0 inet alias 10.10.10.4 255.255.255.0 /etc/asterisk/sip.conf: [meta1] host=10.10.10.100 bindaddr=10.10.10.2 .. [meta2] host=10.10.10.100 bindaddr=10.10.10.3 .. [meta3] host=10.10.10.100 bindaddr=10.10.10.4 .. After upgrading, I now take advantage of the new, reworked routing table. Now, when packets come in to 10.10.10.4 or 10.10.10.3, asterisk never gets them. I thought about the routing table changes and how claudio or mpi described the multiple-/24 config on the same interface as broken (you are creating multiple network routes pointing to the same interface, which is apparently a broken concept) and then I changed /etc/hostname.em0 to this: /etc/hostname.em0: inet 10.10.10.2 255.255.255.0 NONE inet alias 10.10.10.3 255.255.255.255 inet alias 10.10.10.4 255.255.255.255 which is the old school, recommended way. (I seem to remember the same-netmask-for-multiple-IPs-on-an-interfce as passable/usable one point, but it certainly isn't now) And it works. Just thought I'd mention this on misc since I am probably not the only person who is binding multiple IPs in the same subnet to an interface? Chris
