On 10/12/11 2:27 PM, [email protected] wrote:
"If you put 0.0.0.0, it will bind to all addresses. In a HA Cluster, on the active node, if you have a box address of 192.168.1.101 and a floating address of 192.168.1.102, then if you use bindaddr=0.0.0.0 you will find that phones on the 192.168.1.x subnet will not register on the floating address, which of course defeats the point of HA clustering. What happens is that the registration packets go to the floating address 192.168.1.102 but the response packets appear to come from 192.168.1.101 [same NIC but the packet contains the base address attached to the NIC], so the registration fails." Any idea how to solve this?
try use 2 different subnet addresses instead of both addresses on the same subnet. e.g. 192.168.1.101/24 & 192.168.2.101/24 and also use "ip" command to add the address to the interface instead of "ifconfig" and eth0:x notation. that way the OS will pick the correct address when responding to in coming packets. the problem is when you assign 2 addresses to the same interface on the same subnet, one of them will be primary and the other will becomes secondary on that subnet. the OS will always pick the primary address when sending out packets on that subnet. -- Edwin Lam <[email protected]> Systems Engineer, OfficeWyze, Inc. Ph: +1 415 439 4988 Fax: +1 415 283 3370 http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0xD6506D20 -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
