From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Duffy Subject: Re: network-bridge script reworked Date: Wed, 19 Oct 2005 06:15:18 -0500 Message-ID: <43562AC6.3030006@spamcop.net> References: <20051019093502.GP8705@tpkurt.tagung.uni-hamburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051019093502.GP8705@tpkurt.tagung.uni-hamburg.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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? 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.