From: Celejar <celejar@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>,
bcm43xx-dev <bcm43xx-dev@lists.berlios.de>,
"Luis Rodriguez" <Luis.Rodriguez@atheros.com>
Subject: Re: Can't connect to AP with hidden essid with 2.6.27-rc6
Date: Fri, 19 Sep 2008 14:27:40 -0400 [thread overview]
Message-ID: <20080919142740.60e2c0e8.celejar@gmail.com> (raw)
In-Reply-To: <43e72e890809191105p26841666l50a4a139a7177590@mail.gmail.com>
On Fri, 19 Sep 2008 11:05:35 -0700
"Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
> On Fri, Sep 19, 2008 at 9:13 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>
> > I do not think a bisection is necessary. Your successful test of the
> > old regulatory code suggests to me that there is some kind of problem
> > with the CRDA database.
>
> BTW the "old regulatory code" is actually not "old regulatory code"
> but instead static regulatory definitions slapped in the kernel just
> as they were before but under the new regulatory infrastructure guise.
>
> > Luis - to fill you in, he can connect to an AP with a hidden essid
> > using the old regulatory code, but not using CRDA. There seems to be
> > some critical difference between them.
>
> Thanks for bringing this up Larry.
>
> If by old regulatory code you mean with CONFIG_WIRELESS_OLD_REGULATORY
> then I would narrow the search down to testing as follows:
>
> --- Without crda:
>
> mv /sbin/crda /sbin/crda-foo
> sudo rmmod your_driver mac80211 cfg80211
> sudo modprobe your_driver
>
> # Check channels using iw
>
> --- With crda:
> mv /sbin/crda-foo /sbin/crda
> sudo rmmod your_driver mac80211 cfg80211
> sudo modprobe your_driver
>
> # check channels using iw
> ---
>
> By default when CONFIG_WIRELESS_OLD_REGULATORY is set the built-in
> "US" static regulatory domain is used. If crda is present though a new
> regulatory domain will be updated onto the kernel, so we'll get the
> new regulatory domain built by crda from the original db.txt. Without
> crda present the static regulatory domain shall be used.
>
> What frequency is the AP on?
I (the user) am currently connecting successfully with CRDA to a hidden
essid AP. I previously had claimed that it was still not working, even
though the iw channel output looked good, but it currently seems to be
okay. I may have previously done something wrong, such as not
rebuilding CRDA for the current kernel, although in that case I'm not
sure why the iw output would have been correct. In any event, at this
point it seems that it may have been some mistake on my part. Thanks
for the help, sorry for the noise, and I'll report back if I see any
more trouble.
> Luis
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
next prev parent reply other threads:[~2008-09-19 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080916220904.75283811.celejar@gmail.com>
[not found] ` <48D06B9E.70307@lwfinger.net>
[not found] ` <20080918004509.23a4bdc9.celejar@gmail.com>
[not found] ` <48D1E42C.70904@lwfinger.net>
[not found] ` <20080918015202.8c5f6381.celejar@gmail.com>
[not found] ` <48D24911.80101@lwfinger.net>
[not found] ` <20080918160957.94ea063d.celejar@gmail.com>
[not found] ` <48D2D728.6070105@lwfinger.net>
[not found] ` <20080919001050.d9ed273a.celejar@gmail.com>
2008-09-19 16:13 ` Can't connect to AP with hidden essid with 2.6.27-rc6 Larry Finger
2008-09-19 18:05 ` Luis R. Rodriguez
2008-09-19 18:27 ` Celejar [this message]
2008-09-19 18:33 ` Luis R. Rodriguez
2008-09-19 19:18 ` Larry Finger
2008-09-19 20:01 ` Celejar
2008-09-19 20:49 ` Luis R. Rodriguez
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=20080919142740.60e2c0e8.celejar@gmail.com \
--to=celejar@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=Luis.Rodriguez@atheros.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).