[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: .1q trunks

Mike Richardson <mike.richardson@xxxxxxxxxxxxxxxx> writes:

> The Dom0 has two physical interfaces, one as an 'access' port (I'll be
> using Cisco terminology) and the other is a .1q trunk for up to 150
> VLANs (don't ask, long story). Some of the VLANs on this trunk are for
> managing the DomUs and as such I've created interfaces and bridges for
> each. The rest I want to pass on, as a trunk, to a DomU.
> The DomU will have a management interface which connects to one of the
> above management bridges and it should also have an interface
> connected to the trunk. I want to be able to listen to all the
> broadcast traffic on that trunk.

You forgot to tell your precise problem.  However, if you put a trunk
interface (eth1) into a bridge, the bridge will suck up ALL packets
(tagged and native) unless stopped by an appropriate ebtables rule.
This manifests as NO traffic getting to the tagged interface (eth1.1).

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.