[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] xen 2.0.6 and wifi problems



Hi all,

I'm running xen 2.0.6 with linux 2.6.8 in dom0 and domU. The machine has two NICs - WiFi on network 192.168.157.0/25 and "wired" on 192.168.157.128/25. Dom0 uses .21 (dev wifi0) and .221 (dev wire0) and can access router on over both channels on .1/.129. However when I start up domU and assign addresses .41 to the interface bridged on wifi and .241 to the other, only the wired network works. No luck with wifi.

For my tests I have manually created both bridges and set them in the config file:

[/etc/xen/x1]
nics = 2
vif =  ['mac=00:60:00:00:00:01, bridge=xbr0',
        'mac=00:60:00:00:00:02, bridge=xbr1']

dom0:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xbr0            8000.004063d3d632       no              wire0
                                                        vif6.0
xbr1            8000.0060b3656596       no              wifi0
                                                        vif6.1

Addresses and routes are set the same way on both subnets (relevant parts):

dom0:~# ip addr show
2: wifi0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
    link/ether 00:60:b3:65:65:96 brd ff:ff:ff:ff:ff:ff
    inet 192.168.157.21/25 brd 192.168.157.127 scope global eth0
22: wire0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
    link/ether 00:40:63:d3:d6:32 brd ff:ff:ff:ff:ff:ff
    inet 192.168.157.221/25 brd 192.168.157.255 scope global wire
23: xbr0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:40:63:d3:d6:32 brd ff:ff:ff:ff:ff:ff
    inet 192.168.157.221/25 scope global xbr0
24: xbr1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:60:b3:65:65:96 brd ff:ff:ff:ff:ff:ff
    inet 192.168.157.21/25 scope global xbr1
27: vif6.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
28: vif6.1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

dom0:~# ip route show
192.168.157.128/25 dev xbr0 proto kernel scope link src 192.168.157.221
192.168.157.0/25 dev xbr1 proto kernel scope link src 192.168.157.21

domU:~# ip addr show
# ip addr show
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:60:00:00:00:01 brd ff:ff:ff:ff:ff:ff
    inet 192.168.157.241/25 brd 192.168.157.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:60:00:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 192.168.157.41/25 brd 192.168.157.127 scope global eth1

domU:~# ip route show
192.168.157.128/25 dev eth0  proto kernel  scope link  src 192.168.157.241
192.168.157.0/25 dev eth1  proto kernel  scope link  src 192.168.157.41

No firewall or MAC filtering is set up on any node.

When pinging from domU to the router on the wired subnet it just works. OTOH when pinging on the wifi subnet I can observe the arp packets "who-has 192.168.157.1 tell 192.168.157.41" going out on both xbr1 and wifi0 but they don't arrive at the router, i.e. they are either sent out malformed or not sent at all (I don't know). When pinging from the router the arp request for .41 arrives to domU, but the response doesn't reach the router. I.e. no outgoing traffic from domU over WiFi. Incoming seems to work, dom0 works both ways.

FWIW the WiFi card on xen machine is Prism2.5/PCI with orinoco_pci driver, tried both with and without WEP.

Does anyone have an idea on what could be wrong, workarounds, etc.?

Thanks!

Michal Ludvig
--
* Personal homepage: http://www.logix.cz/michal



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.