Hi,
I was just testing hostapd and it told me:
Could not set PrivacyInvoked for interface wlan0
This is because we only allow setting that for STA interfaces, but what
should the setting do for AP interfaces? I don't see any point in it, is
there?
johannes
> > I was just testing hostapd and it told me:
> > Could not set PrivacyInvoked for interface wlan0
> >
> > This is because we only allow setting that for STA interfaces, but what
> > should the setting do for AP interfaces? I don't see any point in it, is
> > there?
>
> The only use for it in the AP mode is to support drivers (or well, more
> likely firmware designs) that insist on generating the Beacon (and Probe
> Response) frames themselves. I would be fine with net/mac80211 not
> supporting such designs, but it would probably be better to continue to
> support this in hostapd (and make it possible to do this with
> cfg/nl80211, too).
Ok, thanks for the clarification.
johannes
On Wed, Dec 12, 2007 at 10:53:07AM +0100, Johannes Berg wrote:
> I was just testing hostapd and it told me:
> Could not set PrivacyInvoked for interface wlan0
>
> This is because we only allow setting that for STA interfaces, but what
> should the setting do for AP interfaces? I don't see any point in it, is
> there?
The only use for it in the AP mode is to support drivers (or well, more
likely firmware designs) that insist on generating the Beacon (and Probe
Response) frames themselves. I would be fine with net/mac80211 not
supporting such designs, but it would probably be better to continue to
support this in hostapd (and make it possible to do this with
cfg/nl80211, too).
--
Jouni Malinen PGP id EFC895FA