[Xen-users] Dual nics work only with the 1st DomU

["Brian" <brian@xxxxxxxxxx>]

I have a LAN (eth0) and WAN (eth2) interface.

Dom0 has static ips for both as well as 2 DomU's:

auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
        address 192.168.0.9
        netmask 255.255.255.0
        broadcast 192.168.0.255
        network 192.168.0.0

allow-hotplug eth2
auto eth2
iface eth2 inet static
        address XX.XXX.81.105
        netmask 255.255.255.248
        broadcast XX.XXX.81.111
        network XX.XXX.81.104
        gateway XX.XXX.81.110
        dns-nameservers XX.XXX.81.106

<snippet from> xend-config.sxp:
#(network-script network-bridge)
(network-script multi-network-bridge)
(vif-script vif-bridge)

multi-network-bridge:
#!/bin/sh

dir=$(dirname "$0")

"$dir/network-bridge" "$@" vifnum=0 netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth2

After 1st VM is started:
xenhost xen # brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00248c790091       no              peth0
                                                        vif8.0
eth2            8000.00a0c967d78d       no              peth2
                                                        vif8.1
xenhost xen #

iptables output:

Chain FORWARD (policy ACCEPT 488 packets, 57330 bytes)
num   pkts bytes target     prot opt in     out     source              
destination
1       44  4649 ACCEPT     all  --  *      *       192.168.0.13        
0.0.0.0/0           PHYSDEV match --physdev-in vif8.0
2        0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
0.0.0.0/0           PHYSDEV match --physdev-in vif8.0 udp spt:68 dpt:67 3 
      0     0 ACCEPT     all  --  *      *       XX.XXX.81.108       
0.0.0.0/0           PHYSDEV match --physdev-in vif8.1
4        0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
0.0.0.0/0           PHYSDEV match --physdev-in vif8.1 udp spt:68 dpt:67

Connectivity on the Lan and wan!

After 2nd VM is started:

xenhost xen # brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.00248c790091       no              peth0
                                                        vif8.0
                                                        vif9.0
eth2            8000.00a0c967d78d       no              peth2
                                                        vif8.1
                                                        vif9.1
xenhost xen #

Chain FORWARD (policy ACCEPT 1069 packets, 107K bytes)
num   pkts bytes target     prot opt in     out     source              
destination
1       44  4649 ACCEPT     all  --  *      *       192.168.0.13        
0.0.0.0/0           PHYSDEV match --physdev-in vif8.0
2        0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
0.0.0.0/0           PHYSDEV match --physdev-in vif8.0 udp spt:68 dpt:67 3 
      0     0 ACCEPT     all  --  *      *       XX.XXX.81.108       
0.0.0.0/0           PHYSDEV match --physdev-in vif8.1
4        0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
0.0.0.0/0           PHYSDEV match --physdev-in vif8.1 udp spt:68 dpt:67 5 
      0     0 ACCEPT     all  --  *      *       192.168.0.14        
0.0.0.0/0           PHYSDEV match --physdev-in vif9.0
6        0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
0.0.0.0/0           PHYSDEV match --physdev-in vif9.0 udp spt:68 dpt:67 7 
      0     0 ACCEPT     all  --  *      *       XX.XXX.81.109       
0.0.0.0/0           PHYSDEV match --physdev-in vif9.1
8        0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
0.0.0.0/0           PHYSDEV match --physdev-in vif9.1 udp spt:68 dpt:67

PING 192.168.0.14 (192.168.0.14) 56(84) bytes of data.
>From 192.168.0.9 icmp_seq=2 Destination Host Unreachable

Doesn't matter which VM is started first, the second never has
connectivity on either interface.

Ideas?



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


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