[Xen-users] Re: ADDRCONF(NETDEV_UP): vif1.0: link is not ready

To:	Xen-users@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-users] Re: ADDRCONF(NETDEV_UP): vif1.0: link is not ready
From:	Ryan <niespam@xxxxxxxxx>
Date:	Wed, 31 Jan 2007 08:36:48 -0500
Delivery-date:	Wed, 31 Jan 2007 05:36:46 -0800
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=UlmqB0rXFucKFhVOnLv6luAtMnFpoPtqoiwcUzHM9xlvGAcVGztt0xEztv5XwspHP1d7fb0g/zJ9kNuXQidsK9ieh3cPTwaWlAaEcRbgyTI1xssOCRuKsNBy7GanF1lMNfFlpNKuyGJ6vQ04SoXPXKIj3+yJKwhZLDl06x+30L8=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<7a3d2e840701301941p2f5c8368pf6fa8bff8e3c8dd8@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References:	<7a3d2e840701301941p2f5c8368pf6fa8bff8e3c8dd8@xxxxxxxxxxxxxx>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

By the way, I forgot to add, this message

ADDRCONF(NETDEV_UP): vif1.0: link is not ready

(also in the subject) is from /var/log/messages, I thought it may help some of you networking gurus out there. - Thanks, Ryan

On 1/30/07, Ryan <niespam@xxxxxxxxx> wrote:

Hello,

I'm trying to set up my xen bridge (xenbr0). The good news is that it works.... sort of.... I can see packets coming from the vif, but they are intermittent. I tracked it down to this step....

brctl addbr xenbr0
brctl stp xenbr0 off
brctl setfd xenbr0 0
ip link set xenbr0 up
brctl addif xenbr0 eth0

As soon as the last command exits, my network gets flaky, it seems as if part of the network is missing (i.e. I can't ping machines I could ping before). The same goes for my domU. As soon as I issue this command...

brctl addif xenbr0 eth1

everything is OK again. Any ideas?

Thanks,
Ryan

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users