WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: .1q trunks

To: Mike Richardson <mike.richardson@xxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: .1q trunks
From: Ferenc Wagner <wferi@xxxxxxx>
Date: Mon, 17 Oct 2011 22:26:09 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 17 Oct 2011 13:28:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20111005081704.GP3556@xxxxxxxxxxxxxxxx> (Mike Richardson's message of "Wed, 5 Oct 2011 09:17:04 +0100")
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20111005081704.GP3556@xxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
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).
-- 
Regards,
Feri.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>