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. 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@lists.xensource.com http://lists.xensource.com/xen-users
Am Monday, den 25 February hub Tom Horsley folgendes in die Tasten: Hi!> 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.That should work.> 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.Did you do "tcpdump -n -i <your brige interface>" on Dom0? Maybe parallel tcpduming on the eth0 devices in the DomUs to see both sides of the "wire".> I''ve tried many more complex schemes as well, with the same result :-).Then they weren''t complex enough ;) Ciao Max -- Follow the white penguin. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Tom Horsley >Sent: Monday, 25 February 2008 16:59 >To: xen-users@lists.xensource.com >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@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users