RE: [Xen-users] eth0 on dom0 not working on a bridged conf

["Dustin Henning" <Dustin.Henning@xxxxxxxxxxx>]

I think eth0 should be included under interfaces here:

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
                                                        vif3.0

The appropriate brctl command will add it to the bridge (not at a Linux
machine to get you that command).  This is because peth0 is the physical
connection to the network and eth0 is where your address is assigned.  This
is the normal setup for older versions of xen, except eth0 should have been
automatically added to the bridge during startup.  On newer versions, xenbr0
is deprecated and eth0 is the bridge (which has the address assigned to
itself).
        Dustin

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Javier Merino
Sent: Wednesday, September 03, 2008 12:20
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] eth0 on dom0 not working on a bridged conf

Hi,

  I've installed xen 3.0.3 from packages (xen-linux-system) on a debian 
etch, and i've configured it with network-bridge script in the default 
way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me.

the problem I have:

  I cannot ping any outer machine from dom0 (nor any outer machine can 
ping me). It gives me a "Destination Host Unreachable" message that 
makes me think there is no arp response.

other symptoms:

  I can ping from dom0 any domU's I create...
    ... and from those domU's I can ping dom0 and also the outer 
machines that I was unable to ping from dom0. => so, xenbr0 if working 
properly with peth0, vifX.0 (and eth0 on domU's)

  Configuration looks fine in comparation with other xen 3.0 machines I 
have working. Here is a "/etc/xen/scripts/network-bridge status":

============================================================
6: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:14:5e:da:3a:a2 brd ff:ff:ff:ff:ff:ff
    inet 172.30.1.16/24 brd 172.30.1.255 scope global eth0
    inet6 fe80::214:5eff:feda:3aa2/64 scope link
       valid_lft forever preferred_lft forever
13: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet6 fe80::200:ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever
 
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
                                                        vif3.0
 
172.30.1.0/24 dev eth0  proto kernel  scope link  src 172.30.1.16
default via 172.30.1.1 dev eth0
 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
172.30.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         172.30.1.1      0.0.0.0         UG    0      0        0 eth0
============================================================


  If I manually "/etc/xen/scripts/network-bridge stop",  eth0 begins 
working correctly with the exterior (I can ping, ssh, outer machines and 
viceversa).

  dmesg, xend.log and xen-debug.log looks fine for me, but I may missed 
up something .

  I've installed tshark to test the communications when network-bridge 
is up, but my knowledge is not enough to understand what's happening. 
I'll send the output of whatever you ask me.

Thanks if anyone can help. I am lost after trying almost my best.

_______________________________________________
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