From: Kadianakis George <desnacked@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: mac80211 and hidden ESSIDs in 2.6.28
Date: Fri, 8 May 2009 21:46:57 +0300 [thread overview]
Message-ID: <20090508184656.GB4529@grayskull> (raw)
In-Reply-To: <20090508184135.GA4529@grayskull>
On 21:41 Fri 08 May , Kadianakis George wrote:
> So, any ideas?
> Do you need any extra info?
Original post (http://marc.info/?l=linux-wireless&m=124059633132688&w=2):
Greetings,
this bug: http://bugs.gentoo.org/show_bug.cgi?id=262862 seems to
reveal a bug in mac80211 being unable to handle APs that don't
broadcast their ESSIDs.
The issue appeared in the 2.6.28 versions (2.6.27 worked alright) of
the Linux kernel and it seems to be fixed in 2.6.29.
A bugzilla entry for this specific bug was created over here:
http://bugs.gentoo.org/show_bug.cgi?id=267368
Any ideas on what caused it and which patch fixed it?
Thanks
prev parent reply other threads:[~2009-05-08 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 18:05 mac80211 and hidden ESSIDs in 2.6.28 Kadianakis George
2009-05-08 18:41 ` Kadianakis George
2009-05-08 18:46 ` Kadianakis George [this message]
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=20090508184656.GB4529@grayskull \
--to=desnacked@gmail.com \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox