Did you go through the following list of suggestions?
Q: VLANs don't work.
A: Many drivers in Linux kernels before version 3.3 had VLAN-related
bugs. If you are having problems with VLANs that you suspect to be
driver related, then you have several options:
- Upgrade to Linux 3.3 or later.
- Build and install a fixed version of the particular driver
that is causing trouble, if one is available.
- Use a NIC whose driver does not have VLAN problems.
- Use "VLAN splinters", a feature in Open vSwitch 1.4 and later
that works around bugs in kernel drivers. To enable VLAN
splinters on interface eth0, use the command:
ovs-vsctl set interface eth0 other-config:enable-vlan-splinters=true
For VLAN splinters to be effective, Open vSwitch must know
which VLANs are in use. See the "VLAN splinters" section in
the Interface table in ovs-vswitchd.conf.db(5) for details on
how Open vSwitch infers in-use VLANs.
VLAN splinters increase memory use and reduce performance, so
use them only if needed.
- Apply the "vlan workaround" patch from the XenServer kernel
patch queue, build Open vSwitch against this patched kernel,
and then use ovs-vlan-bug-workaround(8) to enable the VLAN
workaround for each interface whose driver is buggy.
(This is a nontrivial exercise, so this option is included
only for completeness.)
It is not always easy to tell whether a Linux kernel driver has
buggy VLAN support. The ovs-vlan-test(8) and ovs-test(8) utilities
can help you test. See their manpages for details. Of the two
utilities, ovs-test(8) is newer and more thorough, but
ovs-vlan-test(8) may be easier to use.
On Mon, Dec 17, 2012 at 11:05:14AM +0100, Endre Karlson wrote:
> Yes, but I'm still unsure of what's really wrong.
>
> Endre.
>
> 2012/12/17 Ben Pfaff <[email protected]>
>
> > On Mon, Dec 17, 2012 at 12:22:21AM +0100, Endre Karlson wrote:
> > > Hi, is this feasable to do? I'm trying to run some servers inside of a
> > ESXi
> > > host that uses a OpenvSwitch with VLAN tagged ports. I've tagged the port
> > > group with 4095 in the ESXi host and then inside the VM I do:
> > > ovs-vsctl add-br br-virtual
> > > ovs-vsctl add-port br-virtual eth1
> > > ovs-vsctl add-port br-virtual vlan61 tag=61 -- set Interface vlan61
> > > type=internal
> > > ifconfig vlan61 172.16.59.X/24
> > >
> > > But if I try to get traffic going on the vlan61 interface all I can get
> > > going is L2 traffic, L3 is jammed. And I know there's hosts there that's
> > up
> > > and running because I have 2 physical nodes on the same VLAN using the
> > > method described above and they work perfectly.
> > >
> > > Though the funny bit is if I setup the VLAN interface using
> > > vconfig add eth1 61
> > > ifconfig eth1.61 172.16.59.X/24
> >
> > Did you read the VLAN section of the FAQ?
> >
> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
