2012/4/19 Stuart Henderson <s...@spacehopper.org>: >> 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.
Overall, this sounds like the "missing arp" issue in some regards. As for the recent threads about carps misbehaving, I had at least one pair of carped servers that worked better when I defined static carppeers and stopped using multicast. Yes, its a workaround, but it made the carps reliable for me. If you can Matt, try to set the carppeer option so it unicasts carp status packets between the hosts over the vlans, and see if it helps. -- To our sweethearts and wives. May they never meet. -- 19th century toast
