Date: Thu, 13 Jan 2005 16:57:42 -0800 From: Ben Becker <benjamin.becker@gmail.com> To: freebsd-current@freebsd.org Subject: Re: Atheros and SIS bridging problem Message-ID: <38d37be7050113165733434463@mail.gmail.com> In-Reply-To: <41E6FA7F.2070406@errno.com> References: <38d37be7050111092379f2a898@mail.gmail.com> <20050113065003.GA2336@tongi.org> <38d37be7050113143868516018@mail.gmail.com> <41E6FA7F.2070406@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Jan 2005 14:47:27 -0800, Sam Leffler <sam@errno.com> wrote:
> Those devices tunnel using a 4-address 802.11 format specifically
> designed for this. Like I said, what you need is not currently
> supported. The encapsulation work is actually very simple; the hard bit
> is how everything ties into the system. I happen to be working on this
> but results will not be available for a while.
>
> Sam
Would this be as simple as using the struct ieee80211_frame_add4
instead of ieee80211_frame and setting the proper ToDS and FromDS
values in the control settings? It looks like you've done most of the
work already. Is there anything else that needs to be done aside from
updating all of the net80211 and device driver functions that
reference ieee80211_frame?
I'm going to start working on a hack for this since I need the feature
for a project I'm working on. I don't want to keep pestering you with
this since you're already working on it, but I'm more than happy to
help incorporate this feature in any way I can. Obviously, any tips
and pointers would be greatly appreciated.
-Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38d37be7050113165733434463>