Hi, It was indeed related to the interfaces being in promiscuous mode. I managed to find the root cause, and have a workaround.
On Fri, Oct 3, 2014 at 4:32 AM, Chris Bennett <[email protected]> wrote: >> I'm running my LXC base & container on top of VMware ESX, and thus my vSwitch > has to be in promiscuous mode. I'm seeing frames coming in on the uplink port > (equiv to your port 1) with a source mac of that of the LXC container. That > to > me would explain why OVS's fdb shows port id 1 for those mac addresses. > The networking hosts have two interfaces, which are bonded. This is the cause of the ovswitch seeing arp requests also appearing on port 1, and thus incorrectly learning where that mac address is. I disabled on link, and the problem went away. However I need both those links for redundance. So now the question has become how to use these two links, without creating arp loops. Any ideas there? Krist -- [email protected] [email protected] Bern, Switzerland _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
