All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evan Bigall <evan.bigall@scalent.com>
To: xen-devel@lists.sourceforge.net
Subject: Xen and VLANs
Date: Mon, 24 Jan 2005 11:32:51 -0800	[thread overview]
Message-ID: <41F54D63.2050203@scalent.com> (raw)

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?

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.

Evan



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

             reply	other threads:[~2005-01-24 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 19:32 Evan Bigall [this message]
2005-01-24 20:16 ` Xen and VLANs David Becker
2005-01-25  2:46 ` Fajar A. Nugraha
  -- strict thread matches above, loose matches on Subject: below --
2005-01-24 20:15 Ian Pratt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41F54D63.2050203@scalent.com \
    --to=evan.bigall@scalent.com \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.