Some drivers handle priority tagged packets specially (generally because they do something with DCB) and don't pass the tag onto the network stack at all, so OVS never has a chance to see it.
On Wed, Nov 16, 2011 at 11:58 PM, Aimal Khan <[email protected]> wrote: > As requested, the general steps of the test I did are following. > > 1. Start OVS using ovs-vswitchd in kernel mode. > > 2. Using a NOX application write a flow at datapath-join using > send_openflow_command function. The flow has dl_vlan and dl_vlan_pcp fields > set to 0, rest of the match fields are wildcarded. > > 3. On OVS side the confirmation of the flow write is done by looking at the > output of following; > > ~/utilities$ ./ovs-ofctl dump-flows br0 > > which gives the following output; > > cookie=0x0, duration=7.931s, table=0, n_packets=0, n_bytes=0, > dl_vlan=0,dl_vlan_pcp=0 actions=output:3 > > 4. Using port 2 of the OVS, send a VLAN tagged packet (both vlan id and vlan > priority set to 0). Confirm the send and the validity of VLAN header (along > with vlan id = 0 and vlan priority = 0) using Wireshark. > > 5. Instead of a packet being received at port 3 (using Wireshark for > confirmation), a packet-in event is generated at the NOX indicating a > flow-table miss. > > Regards, > Khan > > On Thu, Nov 17, 2011 at 12:25 PM, Ben Pfaff <[email protected]> wrote: >> >> On Thu, Nov 17, 2011 at 12:17:22PM +0500, Aimal Khan wrote: >> > On Thu, Nov 17, 2011 at 11:49 AM, Ben Pfaff <[email protected]> wrote: >> > >> > > On Thu, Nov 17, 2011 at 11:49:33AM +0500, Aimal Khan wrote: >> > > > I am having some issues in understanding how OVS deals with VLAN id >> > > > = 0. >> > > > (Using ovs v1.2.0 and NOX). >> > > > >> > > > For example: I have the following flow in the switch: >> > > > >> > > > cookie=0x0, duration=7.931s, table=0, n_packets=0, n_bytes=0, >> > > > dl_vlan=0,dl_vlan_pcp=0 actions=output:3 >> > > > (only VLAN and VLAN priority are set.) >> > > > >> > > > What values of *vlan id* and *vlan pcp* of an inbound packet will >> > > > allow >> > > it >> > > > to match successfully with the flow given above? >> > > > I have tried tagged (vlan id = 0 and vlan pcp = 0) and untagged >> > > > packets; >> > > > the packets were NOT successfully matching the flow described above. >> > > >> > > This flow should match a packet tagged with vlan id 0, vlan pcp 0. >> > >> > That was my first guess as well but I have tested it with packets >> > having *vlan id*=0 and *vlan pcp*=0 (several times actually) and I am >> > unable to get this result. >> >> Can you describe your test for us? > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
