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-devel

Re: [Xen-devel] Xen and VLANs

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xen and VLANs
From: "Fajar A. Nugraha" <fajar@xxxxxxxxxxxx>
Date: Tue, 25 Jan 2005 09:46:01 +0700
Delivery-date: Tue, 25 Jan 2005 04:07:38 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <41F54D63.2050203@xxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <41F54D63.2050203@xxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041206)
Evan Bigall wrote:

I am using Xen 2.0 with Mandrake 10.1 based hosts and guests.

There seems to be some sort of issue with VLANs and MTUs?

Why bother use VLANS in dom-U?

My VMs have two nics, each connected to a separate bridge.

In Dom1, I do:
vconfig add eth1 5
ip addr add 10.20.8.17/24 broadcast 10.20.8.255 dev eth1.5
ifconfig eth1.5 up

In Dom2, I do:

vconfig add eth1 5
ip addr add 10.20.8.18/24 broadcast 10.20.8.255 dev eth1.5
ifconfig eth1.5 up

Pinging from Dom2 to Dom1, packet sizes smaller than 1469 work, packet sizes of 1469 and larger just hang.

If I set the MTU on the interface down to 1450, I can then ping with any packet size.

Has any done any experimentation with VLANs on Xen? A problem is that the bridge does not support VLANs but I'm trying to work around that in a variety of ways.

I use bridge, setup VLANS on Domain-0, and bridge each eth0.x on Domain-0 to ethy on dom-U.
That way dom-U only sees eth0, eth1, eth2, and so on. It works flawlessly.

Regards,

Fajar


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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