Date: Thu, 20 Oct 2005 04:35:32 -1000 From: Jim Thompson <jim@netgate.com> To: Andrew Atrens <atrens@nortel.com> Cc: freebsd-current@freebsd.org, Jiri Mikulas <konfer@mikulas.com>, Andrew Thompson <thompsa@freebsd.org> Subject: Re: ath client bridge Message-ID: <7B0B2AA4-5178-4C0F-BB7B-869CB7FC29AC@netgate.com> In-Reply-To: <D89799D0-71A2-45FC-8AF5-9C1902FFF5F1@netgate.com> References: <43560B6A.4070505@mikulas.com> <20051019091559.GA45009@heff.fud.org.nz> <43565782.8080706@nortel.com> <D89799D0-71A2-45FC-8AF5-9C1902FFF5F1@netgate.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 20, 2005, at 3:24 AM, Jim Thompson wrote:
> 1 0 DA BSSID SA X
more importantly, when a device "behind" the AP sends a packet for
and SA that is behind your "client bridge", how does the AP know
where to send the frame on the wireless medium?
Or, in this case:
> 0 1 BSSID SA DA X
When a device "behind" your client bridge sends a frame through your
client bridge, and "SA" is this "device behind", how can the AP
possibly accept the frame. It doesn't (appear) to come from an
associated STA (SA isn't the address for the device that sent the
packet), and the AP certainly can't ACK the frame, (so why would it
forward it?)
This is why the "4 address" frame type (with FromDS and ToDS both
set) exists.
1 1 RA TA DA SA
RA = device on wireless media "receiving" the frame
TA = device on the wireless media "transmitting the frame"
SA = original source of the packet
DA = original (and ultimate) destination of the packet
jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B0B2AA4-5178-4C0F-BB7B-869CB7FC29AC>