This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] wireless card

To: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>, "Deepak Manohar" <mjdeepak@xxxxxxxxx>, <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] wireless card
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 10 Jun 2005 09:30:44 +0100
Delivery-date: Fri, 10 Jun 2005 08:29:55 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVtVzrofqxtvoOtQNSqaxw55TJNKQAAgM6QAA9PP4A=
Thread-topic: [Xen-devel] wireless card
> 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.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>