From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: Networking problems with debian packages Date: 03 Mar 2005 15:45:11 +0100 Message-ID: <87d5ugpz48.fsf@bytesex.org> References: <200503031213.27518.xen.christian@safersignup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <200503031213.27518.xen.christian@safersignup.com> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Christian Wicke Cc: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org Christian Wicke writes: > Does anyone know what is the correct way to make this work? The xen start script network setup doesn't work very good for me as well. Sometimes it works, sometimes it doesn't, havn't figured yet why. I simply make eth0 a bridge early in the boot process, before the network setup. Hooking into /etc/init.d/boot.local works for me, see below for the few script lines. Then let the distribution start scripts configure the eth0 device as usual. Disable /etc/xen/scripts/network (by inserting "exit" at line #2 for example), so xend will not try to do the bridge setup again. Configure your xen domains to use eth0, i.e. "vif = [ 'bridge=eth0' ]". Works fine for me. HTH, Gerd # make eth0 a bridge ip link set name hw-eth0 dev eth0 brctl addbr eth0 brctl addif eth0 hw-eth0 ip link set up hw-eth0 -- #define printk(args...) fprintf(stderr, ## args) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click