On Tue, Dec 05, 2017 at 07:24:10PM -0500, Raghavendra Hegde wrote: > I am using a 3rd party application that runs on two VMs and uses L2 > messages for health checking between the VMs. The L2 messages use a > proprietary ethertype (0x8e9f) for messaging. I see the L2 message going > out of the VM. However, I don’t see the messages going out of the host. I > disabled port security on the neutron port, and the L2 messages go through > fine. All the L3 message between the two VMs go through fine even with > port- security enabled. My guess is that OVS is dropping the L2 messages. > Is it possible that OVS is dropping the L2 messages because it doesn’t > understand the new ethertype? Do we have to add any new flows to the OVS > tables to allow the proprietary ethertype L2 messages?
OVS does not drop proprietary Ethertypes by default, but the flow table that Neutron installs might. You can use "ofproto/trace" to find out what's happening. See ovs-vswitchd(8) for more information. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
