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


[Xen-users] xen vlans in domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xen vlans in domU
From: Alexander Kriventsov <avk@xxxxx>
Date: Tue, 03 Aug 2010 13:39:05 +0400
Delivery-date: Tue, 03 Aug 2010 02:42:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv: Gecko/20100713 Thunderbird/3.1.1

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.


Alexander Kriventsov

Xen-users mailing list

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