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

RE: [Xen-users] Vlan and Xen

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Vlan and Xen
From: Nathan Eisenberg <nathan@xxxxxxxxxxxxxxxx>
Date: Wed, 10 Feb 2010 16:57:32 -0800
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Wed, 10 Feb 2010 16:58:52 -0800
Dkim-signature: v=1; a=rsa-sha1; c=simple; d=atlasnetworks.us; s=key2; l=1618; t=1265849860; x=1266454660; q=dns/txt; h=DomainKey-Signature: Received:Received:From:To:Date:Subject:Thread-Topic:Thread-Index: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:acceptlanguage:Content-Type: Content-Transfer-Encoding:MIME-Version; bh=uPd5Q34D/LfpCX1yhhGvM z+fySE=; b=GfbfLLKOEe9B0kBMtM/wooenrodmhTg8WRfHLrbSB4aGRqW4ZHwsM KEDlfNwa8ufH1IMdUB9DWE1d/7XvljqkeWnzUHmR6oFPzt9r2i1Ddp1u20Hs5IWz aN1jsd4G5GLg6rBeGGsdtZqxQZqFqFdC8pRSfmWSAZHwEe8qTpf9KM=
Domainkey-signature: a=rsa-sha1; s=key2; d=atlasnetworks.us; c=nofws; q=dns; h=from:message-id; b=t2O9IP0c+48/EYwbOuE3DqkVd9GOoQBBhHl/MeqzgRXF31RLJAhVPY6I0wmC PkOxjr3XhmzWB8AUoo4y7JxFsRupImdDkunA1JavK7/7oR1cJoijdWkWc ggjpxAYdZ8oV99jnYOJRGOQizcs4x6MY3bEoCBX8BC4IZqON58Rpvs=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f1002101407y50c09332h7bfe076d12b3e7bd@xxxxxxxxxxxxxx>
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>
References: <201002101642.o1AGgpBB002386@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1265823328.3084.5.camel@localhost> <7207d96f1002101407y50c09332h7bfe076d12b3e7bd@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqqnYPjg4PZwdm8Qfaf14ySCBX04QAF3Dsg
Thread-topic: [Xen-users] Vlan and Xen
I've been doing a bit of this lately, and I've found I've been most comfortable 
with doing the tagging inside the domU, as if it were a regular server that was 
doing tagged traffic.  There are advantages to doing it in Dom0, I'm sure, but 
it was far easier for me to just do it normally.

Best Regards,
Nathan Eisenberg


> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Fajar A. Nugraha
> Sent: Wednesday, February 10, 2010 2:08 PM
> To: Juan Pablo Lorier
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Vlan and Xen
> 
> On Thu, Feb 11, 2010 at 12:35 AM, Juan Pablo Lorier
> <jplorier@xxxxxxxxxxxxxxxxxxx> wrote:
> > I'm using bonding + vlan in a couple of servers. I managed to get a
> > script from redhat to create the bridges from the bond+vlan (bond0.x)
> > but I'm not shure which is the best way to do this;
> >
> > - I have created the ethx inside the domu from each bond0.x vlan
> interface
> > - Or should I use only one bridge (to bond0) and the inside the domu
> create
> > the eth0.x vlan interfaces?
> 
> Both can work, depending on your needs. For example if domU is a
> "normal" server then it's easier to do vlans inside dom0. However if
> the domU is a firewall connected to many network/vlans, it's easier to
> simply assign the trunk and do vlans inside domU.
> 
> --
> Fajar
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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