All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Brackley <lists-xen-devel@lucidsolutions.co.nz>
To: Xen development list <xen-devel@lists.xensource.com>
Subject: Network-bridge script with bonding and vlan
Date: Fri, 21 Oct 2005 00:34:40 +1300	[thread overview]
Message-ID: <002c01c5d56a$4260d8a0$0100a8c0@balls> (raw)

I'm trying to get the latest x86_64 development release running with eth0 & 
eth1 bonded (using 802.3ad) with VLAN support.  I am trying to get a VLAN 
support running with the intention of putting each domU on its own VLAN. 
Given that the dom0 machine won't have an IP address on any of the domU 
VLAN's, there should be reasonable network isolation between the domains.

I can get the bonding/vlan configuration working on a machine without Xen. 
However I am having troubles getting the VLAN interfaces bridged correctly 
to the xen0 and xenU domains vif interfaces. I'm unsure as to which 
interfaces should have what MAC address, and/or how to do that.

I've managed to get the VLAN support working on an older version of Xen 
devel x86, but found I had to run tcpdump in dom0 on each VLAN interface 
(presumably to put it into promiscuous mode).

Any help would be appreciated.

Greg.

             reply	other threads:[~2005-10-20 11:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 11:34 Greg Brackley [this message]
2005-10-20 11:48 ` Network-bridge script with bonding and vlan Ewan Mellor
2005-10-21  1:16   ` Greg Brackley
2005-10-21  9:26     ` Ewan Mellor
2005-10-21 11:23       ` Greg Brackley
2005-10-21 15:08         ` Ted Kaczmarek
2005-10-22 10:16           ` Greg Brackley
2005-10-22 10:17           ` Greg Brackley
2005-10-22 10:34             ` Ewan Mellor
2005-10-22 10:49       ` Greg Brackley
2005-11-23 10:35         ` Network-bridge script with bonding and vlan - WORKAROUND Greg Brackley

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='002c01c5d56a$4260d8a0$0100a8c0@balls' \
    --to=lists-xen-devel@lucidsolutions.co.nz \
    --cc=greg.brackley-dated-1130412881.026793@lucidsolutions.co.nz \
    --cc=xen-devel@lists.xensource.com \
    /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.