Re: Bridging - cannot ping other DomU hosts

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Thu, Feb 03, 2011 at 01:18:44PM -0800, Doug Sampson wrote:
> Hello-
> 
> I'm following the NetBSD Xen tutorial at
> http://www.lumbercartel.ca/library/xen/how-to and I've got two Windows
> Xen instances going. Today I discovered that I couldn't ping to the
> second Windows DomU from the other Windows DomU and vice versa. I also
> discovered that none of the Windows DomU domains could ping the Xen
> machine. But I can ping Dom0 and all DomU instances from outside the Xen
> host inside the LAN. Do I need to modify the routing tables in the Xen
> host in order to allow pinging within the Xen environment? 
> 
> 
> Does the ifconfig output look correct?:
> 
> xen# ifconfig -a
> wm0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
> mtu 1500
>  
> capabilities=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UD
> P4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx,TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TS
> O6>
>         enabled=0
>         address: 00:30:48:df:3a:fa
>         media: Ethernet autoselect (1000baseT
> full-duplex,flowcontrol,rxpause,txpause)
>         status: active
>         inet 192.168.101.42 netmask 0xffffff00 broadcast 192.168.101.255
>         inet6 fe80::230:48ff:fedf:3afa%wm0 prefixlen 64 scopeid 0x1
> wm1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>  
> capabilities=7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UD
> P4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx,TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TS
> O6>
>         enabled=0
>         address: 00:30:48:df:3a:fb
>         media: Ethernet autoselect
>         status: no carrier
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
>         inet 127.0.0.1 netmask 0xff000000
>         inet6 ::1 prefixlen 128
>         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
> bridge0: flags=41<UP,RUNNING> mtu 1500
> xvif3.0: flags=8923<UP,BROADCAST,NOTRAILERS,PROMISC,SIMPLEX,MULTICAST>
> mtu 1500
>         capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
>         enabled=0
>         address: 00:16:3e:01:00:13
>         inet6 fe80::216:3eff:fe01:13%xvif3.0 prefixlen 64 scopeid 0x9
> tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
> 1500
>         address: f2:0b:a4:40:32:0f
>         media: Ethernet autoselect
>         inet6 fe80::f00b:a4ff:fe40:320f%tap0 prefixlen 64 scopeid 0xa
> xvif5.0: flags=8923<UP,BROADCAST,NOTRAILERS,PROMISC,SIMPLEX,MULTICAST>
> mtu 1500
>         capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
>         enabled=0
>         address: 00:16:3e:01:00:14
>         inet6 fe80::216:3eff:fe01:14%xvif5.0 prefixlen 64 scopeid 0xc
> tap1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
> 1500
>         address: f2:0b:a4:36:f5:16
>         media: Ethernet autoselect
>         inet6 fe80::f00b:a4ff:fe36:f516%tap1 prefixlen 64 scopeid 0xd
> xen#

can you also show the output of 'brconfig -a' ?
And also the config file for your domUs ?
what emulation is the virtual interface using in windows
(intel gigabit, realtek, ne2000, other ?)

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--