Thanks for the answer.
It was a simple config issue. Subinterfaces pops vlan tag when they recieve
the tag frame as they assume packets reached destiny. Just adding eth0 to
the ovs worked.
El jue., 30 ago. 2018 a las 4:37, IWAMOTO Toshihiro (<iwam...@valinux.co.jp>)
escribió:
> On Wed, 29 Aug 2018 07:12:27 +0900,
> Alvaro Jimenez wrote:
> > I'm trying to recieve tagged packets and route them using ovs depending
> on
> > the VLAN tag value. I created and added eth0.101, eth0.201 and eth0.301
> to
> > the ovs bridge. I'm able to recieve packets in those VLAN type
> > subinterfaces but there's no VLAN tag when i tcpdump them. Moreover,
> when i
> > tcpdump eth0 interface i am able to see the tagged frames.Of course I am
> > also unable to read VLAN header on controller as there is no VLAN header.
> > Are the vlan type subinterfaces popping the VLAN tag? Is there any other
> > way or configuration to recieve the tagged frames on the controller?
> >
>
> Seems like an ovs configuration issue.
>
> See these:
>
> http://docs.openvswitch.org/en/latest/faq/vlan/
> ovs-vswitchd.conf.db(5)
>
> I guess you need to set up vlan_mode properly and use ovs-vsctl
> add-port instead of ip link command.
>
> --
> IWAMOTO Toshihiro
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel
