On Sun, Sep 04, 2016 at 07:12:43PM +0000, Fredrik Dahlberg wrote: > I am trying to get carp to work with ovs(2.5.0, ubuntu 16.04). > > Carp is set up with the same mac address on the carp interfaces, trying to > determine who is master like this: > 20:55:56.326841 00:00:5e:00:01:19 (oui Unknown) > 01:00:5e:00:00:12 (oui > Unknown), ethertype IPv4 (0x0800), length 70: 192.168.43.2 > vrrp.mcast.net: > CARPv2-advertise 36: vhid=25 advbase=1 advskew=50 authlen=7 > counter=4581652178833997382 > 20:55:56.382550 00:00:5e:00:01:19 (oui Unknown) > 01:00:5e:00:00:12 (oui > Unknown), ethertype IPv4 (0x0800), length 70: 192.168.43.4 > vrrp.mcast.net: > CARPv2-advertise 36: vhid=25 advbase=1 advskew=100 authlen=7 > counter=11630556296063315122 > (The difference in advskew here shows they are different sources.) > > However, ovs won't let any frames through if they arrive on the "wrong" > port according to the fdb. When sniffing on the bridge I can only see > packets from the source that started first. This easily leads to a > situation where I end up with multiple carp masters, and even if it didn't, > we have to wait for the entry in the fdb to time out before the new master > is visible to the network. > > Any suggestions on how to solve this? Any way to allow frames on the > "wrong" port to update the fdb?
I don't understand what you mean by the "wrong" port. Open vSwitch implements a conventional MAC learning algorithm. What's carp trying to do, and why doesn't it work with MAC learning? _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
