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] vif-bridge is driving me nuts

To: Matt Ayres <matta@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] vif-bridge is driving me nuts
From: Mike Wray <mike.wray@xxxxxxxxxx>
Date: Wed, 05 Jan 2005 11:43:11 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 05 Jan 2005 11:51:41 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <1104897167.13440.26.camel@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <1104897167.13440.26.camel@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0RC1 (X11/20041201)
Matt Ayres wrote:
Hi,

I'm having a few problems with vif-bridge...

1) I wanted to change the bridge interface names to be more user
friendly and be named after the domain name, not the id.

Unfortunately you will have trouble with this. The names of network
interfaces are limited to 15 characters - and domain names are not.


I figured making this change in /etc/xen/scripts/vif-bridge would do it:

# Add/remove vif to/from bridge.
#brctl ${brcmd} ${bridge} ${vif}
#ifconfig ${vif} $OP
brctl ${brcmd} ${bridge} ${domain}
ifconfig ${domain} $OP

I tried running it by hand and it says the interface doesn't exist.  My
question is... where/when is the tunnel device created?  This is mostly
a cosmetic change compared to the second problem, which is a
functionality problem..

2) In the example usage it shows the last parameter as ip= with a list
of subnets.  How do I pass this ip information to vif-bridge from the
domains configuration file?  I'd really like to use the functionality it
has to limit which domain will be forwarded IP's (to prevent IP
stealing), but for the life of my I can't figure it out... it definitely
does NOT pass the ip variable from the config file as that is already
set.

I'm wondering where vif-script is executed by xend.. I did a grep over
xend itself along with the entire /usr/lib/python/xen directory and only
found a single reference to vif-script and that is where it loads in
from the config file.  Perhaps just knowing more about how xend deals
with vif-script will help me along here.


Mike


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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