From: Simon Barber <simon@superduper.net>
To: Umar Qureshey <umar.qureshey@lantronix.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Hardware requirements for bridging wired+wireless together
Date: Wed, 19 May 2010 15:55:48 -0700 [thread overview]
Message-ID: <4BF46C74.9000000@superduper.net> (raw)
In-Reply-To: <F24C979D1AFD4E4292B911441CBA242407FCCA@2putt.int.lantronix.com>
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@superduper.net]
>>> Sent: Wednesday, May 19, 2010 1:59 PM
>>> To: John W. Linville
>>> Cc: Umar Qureshey; bridge@lists.linux-foundation.org
>>> Subject: Re: [Bridge] 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.
next prev parent reply other threads:[~2010-05-19 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 20:17 [Bridge] Hardware requirements for bridging wired+wireless together Umar Qureshey
2010-05-18 19:32 ` Nicolas de Pesloüan
2010-05-18 23:38 ` Umar Qureshey
2010-05-18 23:51 ` Stephen Hemminger
2010-05-19 17:15 ` Umar Qureshey
2010-05-19 19:20 ` John W. Linville
2010-05-19 20:59 ` Simon Barber
2010-05-19 21:08 ` Umar Qureshey
2010-05-19 22:55 ` Simon Barber [this message]
2010-05-19 21:01 ` Umar Qureshey
2010-05-19 23:02 ` Simon Barber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF46C74.9000000@superduper.net \
--to=simon@superduper.net \
--cc=bridge@lists.linux-foundation.org \
--cc=umar.qureshey@lantronix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.