* privacy_invoked in AP interfaces?
@ 2007-12-12 9:53 Johannes Berg
2007-12-14 4:54 ` Jouni Malinen
0 siblings, 1 reply; 3+ messages in thread
From: Johannes Berg @ 2007-12-12 9:53 UTC (permalink / raw)
To: Jouni Malinen; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: privacy_invoked in AP interfaces?
2007-12-12 9:53 privacy_invoked in AP interfaces? Johannes Berg
@ 2007-12-14 4:54 ` Jouni Malinen
2007-12-14 12:14 ` Johannes Berg
0 siblings, 1 reply; 3+ messages in thread
From: Jouni Malinen @ 2007-12-14 4:54 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: privacy_invoked in AP interfaces?
2007-12-14 4:54 ` Jouni Malinen
@ 2007-12-14 12:14 ` Johannes Berg
0 siblings, 0 replies; 3+ messages in thread
From: Johannes Berg @ 2007-12-14 12:14 UTC (permalink / raw)
To: Jouni Malinen; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
> > 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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-12-14 12:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-12 9:53 privacy_invoked in AP interfaces? Johannes Berg
2007-12-14 4:54 ` Jouni Malinen
2007-12-14 12:14 ` Johannes Berg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).