Yes kernel flow_extract finds the tag when kernel module is loaded and works fine. Its only with userspace + vlan.
On Wed, Jun 13, 2012 at 8:22 AM, Jesse Gross <je...@nicira.com> wrote: > On Wed, Jun 13, 2012 at 6:49 AM, ravi kerur <rke...@gmail.com> wrote: >> I am facing an issue in flow matching for incoming vlan packets in ovs >> userspace. In lib/flow.c and flow_extract function, eth->eth_type(line >> no 363) is eth_type_ip. From logs, I see >> >> Jun 12 14:43:43 rkerur-thinkpad-t500 ovs-vswitchd: >> in_port(1),eth(src=00:27:13:67:b9:9b,dst=00:24:7e:68:ae:46),eth_type(0x0800),ipv4(src=10.0.0.3,dst=10.0.0.7,proto=1,tos=0,ttl=64,frag=no),icmp(type=8,code=0) >> Jun 12 14:43:43 rkerur-thinkpad-t500 ovs-vswitchd: >> priority:0,tunnel:0,in_port:0000,tci(0) >> mac(00:27:13:67:b9:9b->00:24:7e:68:ae:46) type:0800 proto:1 tos:0 >> ttl:64 ip(10.0.0.3->10.0.0.7) port(8->0) >> >> I am not sure where the vlan tagged is getting stripped, tcpdump shows >> incoming packets on eth0 has the correct vlan tags. Has anything >> changed recently? I remember this one working fine sometime during >> last week of march when I last tested it. > > I don't think anything has changed in this area recently. Does the > kernel flow extract find the tag? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
