Date: Fri, 24 Aug 2012 10:54:26 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Bernhard Schmidt <bschmidt@techwires.net> Cc: freebsd-wireless@freebsd.org Subject: Re: Feature-poor default WPA userland software (hostapd, wpa_supplicant) configuration -- is it inetntional? Message-ID: <CAJ-VmombqZGXVqrteU9u%2BeZTkFvymYQ1LBeHLeC3SuK3KbZ7vA@mail.gmail.com> In-Reply-To: <201208241951.06694.bschmidt@techwires.net> References: <199007581.20120824202155@serebryakov.spb.ru> <201208241910.35576.bschmidt@techwires.net> <CAJ-Vmon2Bxn1r8QDohKxePYE=b2ctpA4ArfAqNeO314PyR0Lug@mail.gmail.com> <201208241951.06694.bschmidt@techwires.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 August 2012 10:51, Bernhard Schmidt <bschmidt@techwires.net> wrote: >> There's also likely a whole bunch of driver and stack things we need. >> Eg, we need correct VLAN handling (which is fine, we SHOULD have it in >> net80211, I just don't think it's been tested in a long time.) There's >> also off-channel traffic support which I know we don't currently do. > > Na.. not VLAN over WLAN (well, yeah, that needs to be looked into > also), hostapd is able to shove STAs into different VLANs (on the wired > interface) based on Radius rules. Right. I wonder what the "vlan" tag in the net80211 node is for. Is that for VLAN over WLAN? Yeah, being able to map a STA into a VLAN would be cool, but then we'd have to figure out where to do the bridging and how to tell net80211 to do that mapping to vlan subinterfaces.. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmombqZGXVqrteU9u%2BeZTkFvymYQ1LBeHLeC3SuK3KbZ7vA>