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] bridged network without static ip

To: "Thoralf Schulze" <schulze@xxxxxxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] bridged network without static ip
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Tue, 13 Jan 2009 07:03:38 -0700
Cc:
Delivery-date: Tue, 13 Jan 2009 06:04:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
What distro are you running for your dom0?  This is pretty simple to do - I actually do it in a slightly more complicated fashion where I'm pulling in multiple VLAN interfaces on the same physical ethernet interface, and none of my VLAN interfaces have IP addresses.  The configuration is going to be pretty distro-dependent.  In my SLES10 SP2 VMs, in the /etc/sysconfig/network directory, I simple configure the interfaces to come up but not to try to configure an IP on the interface.  This is done with the following two lines:
STARTMODE=auto
BOOTPROTO=none
 
The first line tells the interface to come up automatically; the second line (which can be "static", "dhcp", "bootp" or "none") tells Linux to bring up the interface but not to assign an IP address.  Again, the configuration on the different distributions can be different, so you need to know the syntax for configuring your network interfaces for your particular distribution.
 
-Nick

>>> "Thoralf Schulze" <schulze@xxxxxxxxxxxxxxxxx> 2009/01/12 13:54 >>>
Hi there,

this is probably really lame, but i gotta ask anyways:

let's say that there is a machine (running debian lenny for both the dom0 
and the domUs) with two network interfaces running xen:

- eth0 should be for administrative purposes only: it has an ip from an 
internal network and allows logging in to the dom0 instance on the server
- eth1 is accessible from the outside and will be shared among some domUs, 
serving stuff to the internet

I'd like to set up networking in a way that all traffic on eth1 will never 
reach dom0. For this reason, the peth1 interface should not have a static 
ip - its traffic should merely travel across the eth1 network bridge to 
the domUs.

I tried to set up eth1 as

auto eth1
iface eth1 inet manual

in /etc/network/interfaces  - didn't work. apparently, eth1 isn't really 
up enough to get included in the bridge. In xend-config.sxp, there is a

(network-script 'network-bridge netdev=eth1')

entry, the domUs have

vif = [ 'ip=x.x.x.x.x,mac=w:h:a:t:ev:er,bridge=eth1' ]

statements in their configs.

It would be really great if someone could enlighten me on this ...

Thank you very much in advance,
thoralf.



This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>