On Wed, Mar 27, 2013 at 12:48 AM, Daniel Dehennin <[email protected]> wrote: > Jesse Gross <[email protected]> writes: > > > [...] > >> It's difficult to read your diagram but isn't vnet16 (where DHCP >> responses are still seen) after OVS? > > Sorry, I'm not sure to understand your question: > > - vnet16 is the interface of the DHCP server > > - isw is the name of the Open vSwitch > > - vnet18 is the interface of the DHCP client > > So, my packets are blocked between vnet16 and isw. > > I made another test: > > - assign to LXC eth1 the same MAC address than vnet16 one > > - assign random MAC addresses to eth1 and breth1 of the KVM hosting the > LXC > > In that situation, everything works fine between the client and the LXC > guest, but then packets from the KVM hosting the LXC[1] never reach isw. > > It looks like Open vSwitch only forward packets with MAC addresses listed > in "ovs-ofctl show isw". > > Is there a way to make it "learn" MAC addresses as they show up on > ports, like any physical switch without MAC filtering.
That's what it does by default. Possibly it has learned the MAC on the wrong port. You can show the MAC table with: ovs-appctl fdb/show <bridge_name> _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
