OVS ports are trunks by default. As I said, the setting for "trunks" does not matter in your case because you are not using "normal".
To match on traffic that is tagged or untagged, match on vlan_tci or dl_vlan. See ovs-ofctl(8). On Fri, Aug 19, 2016 at 08:02:55PM +0200, james hopper wrote: > Aren't OVS ports trunks by default? I tried matching dl_type=0x8100 as well as > dl_vlan without explicitly setting ports as trunks. But it also did not work. > > So what options do I have, if I have to pass tagged traffic through OVS? or if > i have to take certain actions against tagged traffic? > > Sent: Friday, August 19, 2016 at 6:59 AM > From: "Ben Pfaff" <[email protected]> > To: "james hopper" <[email protected]> > Cc: "OVS Discussion" <[email protected]> > Subject: Re: [ovs-discuss] Vlan Tagged packets switching issue > On Fri, Aug 19, 2016 at 03:10:01PM +0200, james hopper wrote: > > Hey everyone, > > I have a small test setup in which Router-1 <---> OVS-2.5 <-----> Router-2 I > > want OVS to switch packets between two interfaces seamlessly. However, I am > > facing issue in switching Vlan tagged packets whereas untagged traffic is > > passing without any issue. I have used very simple two rules as mentioned > > below. Can anyone point me what I am missing here ? > > > > ovs-ofctl add-flow br0 table=0, in_port=1,action=output:2 > > ovs-ofctl add-flow br0 table=0, in_port=2,action=output:1 > > > > I have made both ports (1 and 2 trunk ports) > > > > ovs-vsctl set port eth1 trunks=0,10,20 > > ovs-vsctl set port eth2 trunks=0,10,20 > > There are two issues here. First, VLAN 0 includes untagged traffic. > Second, "trunks" affects only the behavior of the "normal" action. It > does not influence other OpenFlow matches or actions in any way. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
