[Xen-users] bridge network

[ClÃment FÃvrier <clement.analogue@xxxxxxxxx>]

Hello,

I've some trouble to set up a bridge interface for xen. I don't have
any connexion on the domUs.
There the ifconfig on dom0

% ifconfig
eth0      Link encap:Ethernet  HWaddr 00:24:1d:83:c5:2e
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Packets reÃus:11493 erreurs:0 :0 overruns:0 frame:0
          TX packets:6448 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          Octets reÃus:9080439 (9.0 MB) Octets transmis:748808 (748.8 KB)

lo        Link encap:Boucle locale
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:HÃte
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          Packets reÃus:117 erreurs:0 :0 overruns:0 frame:0
          TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          Octets reÃus:9105 (9.1 KB) Octets transmis:9105 (9.1 KB)

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          adr inet6: fe80::fcff:ffff:feff:ffff/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Packets reÃus:157 erreurs:0 :0 overruns:0 frame:0
          TX packets:938 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:32
          Octets reÃus:49408 (49.4 KB) Octets transmis:140139 (140.1 KB)

xenbr0    Link encap:Ethernet  HWaddr 00:24:1d:83:c5:2e
          inet adr:192.168.1.11  Bcast:192.168.1.255  Masque:255.255.255.0
          adr inet6: fe80::224:1dff:fe83:c52e/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Packets reÃus:8788 erreurs:0 :0 overruns:0 frame:0
          TX packets:5915 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          Octets reÃus:8779779 (8.7 MB) Octets transmis:677650 (677.6 KB)


Now on the domU

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3e:3d:ea:27
          inet6 addr: fe80::216:3eff:fe3d:ea27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1115 errors:0 dropped:4 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:151392 (151.3 KB)  TX bytes:59472 (59.4 KB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



The result of brctl

 % brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.00241d83c52e       yes             eth0
                                                        vif1.0



And finally the network/interfaces files for respectively the dom0 and the domU

% cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto xenbr0
iface xenbr0 inet dhcp
        bridge-ports eth0
        bridge_stp on
        bridge_maxwait 0
        bridge_fd 0



# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
#iface eth0 inet dhcp
iface eth0 inet dhcp


The domU don't have ip address.
Also, here what happens when I try to do ifdown/ifup eth0 on the domU

# ifup eth0
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:16:3e:3d:ea:27
Sending on   LPF/eth0/00:16:3e:3d:ea:27
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x354cbeab)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x354cbeab)
DHCPOFFER of 192.168.1.10 from 192.168.1.254
DHCPNAK from 192.168.1.254 (xid=0x354cbeab)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x354cbeab)
DHCPNAK from 192.168.1.254 (xid=0x354cbeab)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x354cbeab)
DHCPNAK from 192.168.1.254 (xid=0x354cbeab)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xcaf926a)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0xcaf926a)
DHCPOFFER of 192.168.1.10 from 192.168.1.254
DHCPNAK from 192.168.1.254 (xid=0xcaf926a)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0xcaf926a)
DHCPNAK from 192.168.1.254 (xid=0xcaf926a)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x742fbc7f)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x742fbc7f)
DHCPOFFER of 192.168.1.10 from 192.168.1.254
DHCPNAK from 192.168.1.254 (xid=0x742fbc7f)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x742fbc7f)
DHCPNAK from 192.168.1.254 (xid=0x742fbc7f)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x5fabac51)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x5fabac51)
DHCPOFFER of 192.168.1.10 from 192.168.1.254
DHCPNAK from 192.168.1.254 (xid=0x5fabac51)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x5fabac51)
DHCPNAK from 192.168.1.254 (xid=0x5fabac51)
DHCPREQUEST of 192.168.1.10 on eth0 to 255.255.255.255 port 67 (xid=0x5fabac51)
DHCPNAK from 192.168.1.254 (xid=0x5fabac51)



Thank you for your help :)
ClÃment

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users