[Xen-users] So close....

[Eric Anderson <eric@xxxxxxxxxxxxxxxx>]

Hello list,

So close, and yet so far ...
I have everything working, as far as I can tell, except for networking.
And that's -half- working.  I hope someone out there can help.  Here's
the situation:
dom0: full network access in and out via wireless interface wlan0.  Can
ping dom1.  
dom1: can ping dom0, but no connectivity to the wide world beyond.
Pings result in:
dom1:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
>From 192.168.1.110 icmp_seq=1 Destination Host Unreachable

--- dom0 ifconfig: -----------
vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:238 errors:0 dropped:0 overruns:0 frame:0
          TX packets:105 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10108 (9.8 KiB)  TX bytes:14293 (13.9 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:40:F4:5E:B9:26
          inet addr:192.168.1.109  Bcast:192.168.1.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17185 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4281 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8683098 (8.2 MiB)  TX bytes:1531852 (1.4 MiB)
          Memory:ec010000-ec0100ff

xen-br0   Link encap:Ethernet  HWaddr 00:40:F4:5E:B9:26
          inet addr:192.168.1.109  Bcast:192.168.1.255
Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:568 errors:0 dropped:0 overruns:0 frame:0
          TX packets:205 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:38069 (37.1 KiB)  TX bytes:28774 (28.0 KiB)
-------------------------------------
dom0: route
root@Eureka:/home/eric # route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     *               255.255.255.0   U     0      0        0
xen-br0
default         192.168.1.1     0.0.0.0         UG    0      0        0
xen-br0

-------------------------------------
dom0: brctl
root@Eureka:/home/eric # brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.0040f45eb926       no              vif1.0
                                                        wlan0

root@Eureka:/home/eric # brctl showmacs xen-br0
port no mac addr                is local?       ageing timer
  1     00:30:1b:33:89:16       no                 0.00
  1     00:40:f4:5e:b9:26       yes                0.00
  2     aa:00:00:52:7f:62       no               287.98
  2     fe:ff:ff:ff:ff:ff       yes                0.00

-------------------------------------
dom1:~# ifconfig
eth0      Link encap:Ethernet  HWaddr AA:00:00:52:7F:62
          inet addr:192.168.1.110  Bcast:192.168.1.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:117 errors:0 dropped:0 overruns:0 frame:0
          TX packets:238 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16249 (15.8 KiB)  TX bytes:10108 (9.8 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:81 errors:0 dropped:0 overruns:0 frame:0
          TX packets:81 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7288 (7.1 KiB)  TX bytes:7288 (7.1 KiB)

-------------------------------------------

Furthermore, starting dom1 seems to result in external dom0 network
connections having problems.  I was ssh'd to dom0 from an external box,
started dom1, and found that my ssh connection was hung.  Attempts at
new ssh connections resulted in "No Route to Host" errors.  After
restarting the dom0 ssh daemon from the physical console, all was well
again.  After that, ssh sessions fail intermittently, in a way that
seems associated with starting a domU.

While running tcpdump on dom0 against wlan0, I can see arp requests that
have originated from dom1, and I can see the arp responses.  But it
seems like dom1 does not receive the responses, thus the "no route to
host" errors.

Thoughts?  This could be an ndiswrapper bug of some sort (maybe it
doesn't correctly support promiscuous operation) but haven't had a
chance to test against a wired network for comparison.

TIA,
Eric




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