The problem is not the WiFi chipset - it's the IEEE802.11 standard. The standard does not allow for 'promiscuous mode' (not to be confused with monitor mode), nor does it require clients and access points to support 4 address format frames which the bridge needs to work. Simon On 05/19/2010 02:08 PM, Umar Qureshey wrote: >>> -----Original Message----- >>> From: Simon Barber [mailto:simon@xxxxxxxxxxxxxx] >>> Sent: Wednesday, May 19, 2010 1:59 PM >>> To: John W. Linville >>> Cc: Umar Qureshey; bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx >>> Subject: Re: Hardware requirements for bridging > wired+wireless together >>> >>> I did write an ebtables module to work around this 802.11 3 address >>> problem - it performed L2 NAT on DHCP, ARP and IP packets, so > allowing >>> an 802.11 client be added to a bridge. It was released under GPL > about 5 >>> years ago (from my previous company Instant802/Devicescape), but I > can't >>> find the source anymore!!! >>> >>> Simon > > That would be very useful. Probably even more useful now than 5 years > ago! Apparently, Windows does MAC-level NAT allowing for the bridging > of Ethernet and WiFi interfaces irrespective of the underlying Wifi > chipset. > > ********************************************************************** > This e-mail is the property of Lantronix. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail, or the information contained herein, to anyone other than the intended recipient is prohibited. _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
