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] 802.1Q VLAN support

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] 802.1Q VLAN support
From: Maximilian Wilhelm <max@xxxxxxxxxxx>
Date: Fri, 7 Dec 2007 01:10:59 +0100
Delivery-date: Thu, 06 Dec 2007 16:11:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1196862536.13581.27.camel@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: xen-devel@xxxxxxxxxxxxxxxxxxx
References: <1196862536.13581.27.camel@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
Am Wednesday, den  5 December hub Luis Vinay folgendes in die Tasten:

Hi!

>   I'm working on adding the 802.1Q vlan suport to Xen. Half of the work
> is done. The idea is that we can specify something like this on the domU
> configuration file:

> vlan = [ 'pdev=eth1, vlanid=123, bridge=xenbr1123',
>          'pdev=eth1, vlanid=100 ' ]

What should that actualy do?
I guess you want to connect vlan 123 from a trunk on eth1 to
xenbr1123. And the next line?

Why not just use the linux way and create vlan interfaces?
e.g. 
# vconfig add eth1 123
# vconfig add eth1 100

and then put eth1.123 to xenbr123 and use this?

> perhaps even specify an IP address (I founded this usefull in some
> implementations), and then, as allways:

What's the purpose of the IP here?

[...]
> I'll check if the bridge is already created before connecting the VIF,
> at domU creation, if not bring it up, and when destroying the domU, also
> check if other domU is using the same bridge before shuting it down.

I just create all the vlan interfaces, bondings and bridges via the
networking setup of my OS on bootup so everything is just there.
No need to think about networking stuff after setup once.

> All this raises me some questions:

>   - Suggestions/advices regarding on where/how put my code?
>   - Could it bring problems if I add this code in 'xen/xm/create.py'?

> gopts.var('vlan', val="iface=IFACE,vlanid=VLANID,vlanbridge=VLANBRIDGE",
>           fn=append_value, default=[],
>           [...]

I don't speak parseltongue :)

Ciao
Max
-- 
        Follow the white penguin.

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

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