[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: network-bridge script reworked

Hi Charles,

On Wed, Oct 19, 2005 at 06:15:18AM -0500, Charles Duffy wrote:
> Kurt Garloff wrote:
> >It now works much better for me:
> >* we got rid of ifconfig
> >* it works for netdev != eth0
> >* arp on and off are symmetric as are ifdown and ifup
> >* ifup will be passed the ifcfg config file name if needed
> >  (the ifup may otherwise figure that the veth0 hardware is 
> >   NOT the same as the original ${netdev} and not use the same
> >   config -- this happens on SUSE. Charles Coffing tracked this
> >   one down.)
> Does this updated network-bridge, like my patch posted to this list on 
> 10/14 under the title "[PATCH] network-bridge script support for 
> multiple external interfaces", allow support for multiple loopback 
> interfaces?

The network-bridge script currently expects to be started just once; 
on the second call you won't have a veth0 any more and thus the script 
will not do anything to your $netdev.

> I have a situation where my Xen host has physical interfaces on multiple 
> networks and gives Xen instances access to one or the other based on 
> where they're supposed to be; this implies modifying all the hardcoded 
> references to veth0 or vif0.0.

veth0 and vif0.0 are currently hardcoded; I did remove all occurences
of eth0 and peth0 though (and replace it by ${netdev} and p${netdev}).

Is it possible to create more than one veth0 in dom0?

Do you want ot have a look into combining your work into mine?

Kurt Garloff, Director SUSE Labs, Novell Inc.

Attachment: pgpcz7zkga0kk.pgp
Description: PGP signature

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.