On Tue, Mar 17, 2015 at 11:05:54PM +0200, Chris Picton wrote: > On 2015/03/17 10:21 PM, Ben Pfaff wrote: > >On Tue, Mar 17, 2015 at 10:17:03PM +0200, Chris Picton wrote: > >>At layer3, I can use the 'ip route get *' commands to determine how > >>the kernel will route a packet. Is there any equivalent command to > >>inspect the ovs behaviour. I would like to ask ovs: 'If I send a > >>packet with src mac 00:15:17:91:05:4c which came in on interface > >>bondV tagged with vlan 3, destined to mac 52:54:00:60:29:8c, what > >>port would it be forwarded to?' > >Yes, you can use "ovs-appctl ofproto/trace", please see > >ovs-vswitchd(8) for more details. > Thanks for the speedy reply - I get the results as below: > > What I can see is that on both cases, OVS says it should be > forwarding via a datapath and popping the vlan tag. The datapath > for ports veth-carbon1-3 (working) and vnet0 (not working) appear to > be similar.
Huh. Check what the kernel actually says it's doing for installed flows, with "ovs-dpctl dump-flows". _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
