Re: xennet0 not connected

[Pierre-Philipp Braun <pbraun%wda-fr.org@localhost>]

Hi Jean-Yves,

Thanks for the quick answer.

Ok to go further, on dom0,

# xm network-list bsd -l
(0
    ((mac 00:16:3e:1d:66:64)
        (handle 0)
        (protocol x86_64-abi)
        (backend-id 0)
        (state 4)
        (backend /local/domain/0/backend/vif/15/0)
        (tx-ring-ref 510)
        (rx-ring-ref 509)
        (feature-rx-notify 1)
        (event-channel 6)
    )
)


# brctl show bridge0
bridge name     bridge id               STP enabled     interfaces
bridge0         8000.90e6baa651c7       no              peth0
                                                        vif15.0
                                                        vif14.0

# ifconfig -a
bridge0   Link encap:Ethernet  HWaddr 90:e6:ba:a6:51:c7
          inet addr:192.168.0.10  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::92e6:baff:fea6:51c7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9343 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8349 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:841985 (822.2 KiB)  TX bytes:2103516 (2.0 MiB)

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:16436  Metric:1
          RX packets:232 errors:0 dropped:0 overruns:0 frame:0
          TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:71888 (70.2 KiB)  TX bytes:71888 (70.2 KiB)

peth0     Link encap:Ethernet  HWaddr 90:e6:ba:a6:51:c7
          inet6 addr: fe80::92e6:baff:fea6:51c7/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:109390836 errors:0 dropped:0 overruns:0 frame:0
          TX packets:218726 errors:0 dropped:0 overruns:0 carrier:11
          collisions:0 txqueuelen:1000
          RX bytes:427272311 (407.4 MiB)  TX bytes:16868595 (16.0 MiB)
          Interrupt:239

sit0      Link encap:UNSPEC  HWaddr 
00-00-00-00-30-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  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)

vif14.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:387 errors:0 dropped:0 overruns:0 frame:0
          TX packets:914 errors:0 dropped:6 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:20154 (19.6 KiB)  TX bytes:114736 (112.0 KiB)

vif15.0   Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:1133 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


On the netbsd domU,

bsd# dmesg | grep xennet
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address 00:16:3e:1d:66:64
xennet0: using event channel 6


bsd# ifconfig -a
xennet0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> 
mtu 1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: 00:16:3e:1d:66:64
        inet 192.168.0.11 netmask 0xffffff00 broadcast 192.168.0.255
        inet6 fe80::216:3eff:fe1d:6664%xennet0 prefixlen 64 scopeid 0x1
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 0x2


bsd# netstat -rn -f inet
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use    Mtu 
Interface
default            192.168.0.1        UGS         0        0      -  xennet0
127/8              127.0.0.1          UGRS        0        0  33648  lo0
127.0.0.1          127.0.0.1          UH          1        4  33648  lo0
192.168.0/24       link#1             UC          1        0      -  xennet0
192.168.0.1        link#1             UHLc        1        8      -  xennet0


> When you tcpdump (in dom0) on the vif associated to NetBSD domU, do you
> actually see the ICMP messages? Can you see them on the bridge0
> interface also on the dom0 side?

# tcpdump -i vif15.0 -vv
tcpdump: WARNING: vif15.0: no IPv4 address assigned
tcpdump: listening on vif15.0, link-type EN10MB (Ethernet), capture size 
96 bytes

It seems nothing comes out of the domU.

Thanks
//Pierre-Philipp