From: Maximilian Wilhelm <max@rfc2324.org>
To: xen-devel@lists.xensource.com
Subject: Re: 802.1Q VLAN support
Date: Fri, 7 Dec 2007 01:10:59 +0100 [thread overview]
Message-ID: <20071207001059.GA32510@outback.rfc2324.org> (raw)
In-Reply-To: <1196862536.13581.27.camel@wasserkocher.iplan.com.ar>
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.
next prev parent reply other threads:[~2007-12-07 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 13:48 802.1Q VLAN support Luis Vinay
2007-12-07 0:10 ` Maximilian Wilhelm [this message]
2007-12-07 0:13 ` Stefan de Konink
2007-12-07 0:17 ` Maximilian Wilhelm
2007-12-11 13:28 ` Luis Vinay
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=20071207001059.GA32510@outback.rfc2324.org \
--to=max@rfc2324.org \
--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.