From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Hidden SSID's
Date: Mon, 29 Jan 2007 08:00:11 -0500 [thread overview]
Message-ID: <1170075611.2895.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1170019717.30318.0.camel@johannes.berg>
On Sun, 2007-01-28 at 22:28 +0100, Johannes Berg wrote:
> On Sat, 2007-01-27 at 07:08 -0500, Dan Williams wrote:
>
> > I really, really don't know why ieee80211 uses <hidden>, but it's a pain
> > in the ass and should NOT be done for d80211. I don't know if we can
> > ever remove it from ieee80211 though for backwards compat reasons.
>
> Ugh. /me makes a note for the cfg80211/we compat layer. This is a
> mess :(
Well, there's no way a userspace program could depend on all hidden SSID
APs having the <hidden> tag, since if you stick in another,
non-ieee80211-stack card it won't be like that. So I don't think we
should care about <hidden> in d80211, but I don't think we can remove it
from ieee80211 either. The only case where we'll care about it is if we
move to common scan-result processing code, and there we may have to put
a compat flag in that the driver can set or something. But we should
definitely _not_ use <hidden> in d80211 or cfg80211, because any program
depending on <hidden> just won't work with anything other than an ipw
card.
Dan
next prev parent reply other threads:[~2007-01-29 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 3:48 Hidden SSID's Larry Finger
2007-01-27 12:08 ` Dan Williams
2007-01-27 15:29 ` Larry Finger
2007-01-28 21:28 ` Johannes Berg
2007-01-29 13:00 ` Dan Williams [this message]
2007-01-30 3:09 ` Jouni Malinen
2007-01-30 3:36 ` Dan Williams
2007-01-30 4:52 ` Larry Finger
2007-01-30 5:08 ` Jouni Malinen
2007-01-30 7:08 ` Larry Finger
2007-01-30 22:56 ` Jouni Malinen
2007-01-31 2:35 ` Larry Finger
2007-02-01 18:46 ` Jouni Malinen
2007-01-28 22:18 ` Larry Finger
2007-01-30 22:53 ` Jouni Malinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1170075611.2895.2.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.