Date: Thu, 20 Oct 2005 05:00:19 -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: <D2B220B2-6945-4F30-9D9B-83EC91D74E40@netgate.com> In-Reply-To: <4357AEE4.7050503@nortel.com> References: <43560B6A.4070505@mikulas.com> <20051019091559.GA45009@heff.fud.org.nz> <43565782.8080706@nortel.com> <D89799D0-71A2-45FC-8AF5-9C1902FFF5F1@netgate.com> <7B0B2AA4-5178-4C0F-BB7B-869CB7FC29AC@netgate.com> <4357AEE4.7050503@nortel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 20, 2005, at 4:51 AM, Andrew Atrens wrote: > Jim Thompson wrote: > >> 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? >> > > > Aha. I had SA confused with TA. Please replace SA with TA on my > last response. :) > > The kludge I see my deliberant 'wireless' bridges use is some kind > of 'mac nat', > so SA gets replaced by TA when the client bridges the packet out to > the AP. You may want to wait for Sam's WDS code, which includes a really nice "client bridge" mode that doesn't involve the translation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D2B220B2-6945-4F30-9D9B-83EC91D74E40>