From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Fajar A. Nugraha" Subject: Re: Xen and VLANs Date: Tue, 25 Jan 2005 09:46:01 +0700 Message-ID: <41F5B2E9.2070005@telkom.co.id> References: <41F54D63.2050203@scalent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <41F54D63.2050203@scalent.com> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org 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