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] Bad network! No ARP!

To: "Tom Horsley" <tom.horsley@xxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Bad network! No ARP!
From: "Joris Dobbelsteen" <Joris@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 25 Feb 2008 16:14:10 -0000
Delivery-date: Mon, 25 Feb 2008 08:13:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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: <022520081559.3121.47C2E5D30003C70D00000C3122230703729B0A02D29B9B0EBF970A049C9D0108D203019B@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ach3x4QTGo3JoBPyRf+/xW9qgw1VDgAAX2Zw
Thread-topic: [Xen-users] Bad network! No ARP!
>-----Original Message-----
>From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tom Horsley
>Sent: Monday, 25 February 2008 16:59
>To: xen-users@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-users] Bad network! No ARP!
>
>OK, What obvious bit of networking wisdom am I missing? 
>Everything I try that diverges in the slightest from the 
>default bridge configuration results in a network that is 
>utterly non-functional.

Try "brctl show", it gives some hints to get started.
Ensure iptables is not factor in the equation (ensure all are set to
ACCEPT), just to make sure.
Monitor "xm top" for traffic on the interfaces.

>The simplest case I've tried created a bridge at boot time 
>using the debian /etc/network/interfaces file to define it, 
>and replaced the network-bridge script with a much simpler one 
>that basically does nothing.
>
>My theory was this would give me a network where the virtual 
>machines could speak to one another (since they are connected 
>to the bridge), but not the outside world.
>
>But what I get is VIFs being connected to the bridge by the 
>vif-bridge script, and eth0 being created in the virtual 
>machines, but I can't ping any virtual machine from any other 
>one - ping just times out waiting for something to happen.
>
>I've tried many more complex schemes as well, with the same result :-).
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-users
>


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

<Prev in Thread] Current Thread [Next in Thread>