Xen devel - Jun 2005 - wireless card

Hi all,

 Has anyone setup a wireless card on xen-3.0-devel either on dom0 or domU? 

 The setup that we have 

 eth0 -- Intel ProLan   
 eth1 -- Orinoco Gold Card 802.11b

 both these interfaces got IPs from the dhcp server in dom0. 

 In /etc/xen/scripts/network we changed the "netdev" to
"eth1".

 Now from domU we were not able to send any packets to the external network. 
(but we cud ping the dom0 interface).

 Any help wud be appreciated.

thanks
deepak

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

I haven''t done it under xen. Some (all?) wireless cards have trouble
sending packets with a forged MAC address (something to do with
association to an access point). I think the way it works is that the
MAC address of the wireless client is associated to the AP, and so if
you start sending packets with a different MAC address, the AP is going
to reject them, and if the AP tries to send packets to the MAC of domU,
it won''t be able to see it in its list of associated MAC addresses.

At home (no xen, ultrasparcII) I bridge an ethernet adapter to a
wireless card (intersil prism2.5 chipset using hostap driver) which
works fine, but the wireless card is running as an AP so the rules are
reversed.

You may be able to set up an AP to AP bridge (is it called WDS??)
between your xen box and the AP to allow what you want to do.

If you give some more information about your setup I might be able to
offer some other suggestions, eg are you bridging or natting or routing
eth1 to domU (my comments above are based on bridging).

James
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Deepak Manohar
> Sent: Friday, 10 June 2005 10:56
> To: Xen-devel@lists.xensource.com
> Subject: [Xen-devel] wireless card
> 
> Hi all,
> 
>  Has anyone setup a wireless card on xen-3.0-devel either on dom0 or
domU?
> 
>  The setup that we have
> 
>  eth0 -- Intel ProLan
>  eth1 -- Orinoco Gold Card 802.11b
> 
>  both these interfaces got IPs from the dhcp server in dom0.
> 
>  In /etc/xen/scripts/network we changed the "netdev" to
"eth1".
> 
>  Now from domU we were not able to send any packets to the external
> network.
> (but we cud ping the dom0 interface).
> 
>  Any help wud be appreciated.
> 
> thanks
> deepak
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

> I haven''t done it under xen. Some (all?) wireless cards have 
> trouble sending packets with a forged MAC address (something 
> to do with association to an access point). I think the way 
> it works is that the MAC address of the wireless client is 
> associated to the AP, and so if you start sending packets 
> with a different MAC address, the AP is going to reject them, 
> and if the AP tries to send packets to the MAC of domU, it 
> won''t be able to see it in its list of associated MAC addresses.
[James: well spotted!]

The easiest way to work around this is to use a routed rather than
bridged setup in dom0.

Take a look at the network-router and vif-route scripts.

Ian
 

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