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/
Home Products Support Community News


Re: [Xen-users] xen vlans in domU

To: Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] xen vlans in domU
From: Alexander Kriventsov <avk@xxxxx>
Date: Tue, 03 Aug 2010 14:27:44 +0400
Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 03 Aug 2010 03:29:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100803101807.GA8814@xxxxxxxxxxxxxxxxxx>
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: <4C57E3B9.2070807@xxxxx> <AEC6C66638C05B468B556EA548C1A77D01A0ADF4@trantor> <20100803101807.GA8814@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv: Gecko/20100713 Thunderbird/3.1.1
03.08.2010 14:18, Mark Adams пишет:

I used the instructions/scripts at the following link to do my VLAN's.
Works pretty well!


I think that vlanbr2 is bridge for vlan 2 and vlanbr3 for vlan 3.
If I want to use vlan 2 and vlan 3 in one domU I should write in config vif = [ 'bridge=vlanbr2', 'bridge=vlanbr3' ] and in this domU I will get two interfaces eth0 and eth1. Is it correct? But I want to have another, I want to have on domU all these vlans on one interface and configure it through vconfig.

On Tue, Aug 03, 2010 at 07:49:03PM +1000, James Harper wrote:

I'm trying to use vlan in domU, but have something strange:
I created bridge on eth0. This interface was configured as trunk with
vlan 300, 301. I use this bridge in my domU, and I can see tagged
packets when run tcpdump in domU. Also I created interface on domU to
work with vlan 300. On this interface I see untagged packets in vlan300.
And everything looks fine.
But when I'm trying to send out packets through interface with vlan300
something happen. On domU in eth0 interface i see that packet was tagged
as vlan 300, but on dom0 I see that package doesn't have tag and sending
to switch as untagged which is incorrect.

Why does kernel remove tag from outgoing packets?
Is anyone using trunk inside of domU?

I'm using xen 3.4.3 on Centos 5.5 with kernel 2.6.18.

I'm not sure I quite understand what you want to do, but I think you need to 
use ebtables, in particular the 'broute' table, to tell Linux how you want 
tagged packets to behave. One thing I was never able to do was to tell Linux to 
place a copy of the tagged packet on one bridge so that I could have a trunk to 
a DomU whilst simultaneously l2 routing packets to their correct interfaces.


Xen-users mailing list

Alexander Kriventsov

Xen-users mailing list

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