On 2012-04-19, Matt Hamilton <ma...@netsight.co.uk> wrote: > David Goldsmith <dgoldsmith <at> sans.org> writes: > >> I believe the "inet" option is missing a 3rd component. After the >> CARP IP and the netmask, you also need the 'last' IP for the subnet, >> in your case it would be 213.133.66.71 (on both servers). >> >> On our servers, we have something like: >> >> inet 10.3.2.1 255.255.255.0 10.3.2.255 > > > I have never needed to manually configure the broadcast address before > on unix. Indeed according to > ifconfig vlan119 it has correctly worked it out:
yeah this is irrelevant, the default "host part all 1's" for the broadcast address works fine for almost all sites. I often go further and just use "10.3.2.1/24" etc. > carp119: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> > mtu 1500 > lladdr 00:00:5e:00:01:77 > priority: 0 > carp: MASTER carpdev vlan119 vhid 119 advbase 1 advskew 10 > groups: carp > status: master > inet 213.133.66.67 netmask 0xfffffff8 broadcast 213.133.66.71 > > I have now removed the trunking to see if that affected it, but no > joy. So I now have: > > bnx0: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> mtu > 1500 Don't know how you got to this state but I'm pretty sure this interface should be in promiscuous mode. If you made changes at runtime then set the config files up how you want and reboot to make sure everything got cleared out correctly. (Yes it should do the right thing all the time but I don't quite trust it, at the very least I know there's at least one problem when removing an interface from a trunk). > If I remove the vlan part and just have the carp interface on top of > bnx0 then I see carp packets on bnx0 > with tcpdump as I'd expect. So clearly there is a serious bug > somewhere about sending carp packets over > vlan interfaces. :( It's certainly not a general problem. Plenty of carp-on-vlan-on-trunk here (mostly on bge and a little bit on vr/em), works fine on the whole.
