From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] N mode
Date: Mon, 18 May 2009 17:24:16 -0700 [thread overview]
Message-ID: <20090519002416.GU20637@tesla> (raw)
In-Reply-To: <43e72e890905181710y2646a79dr3f041f7aef143de2@mail.gmail.com>
On Mon, May 18, 2009 at 05:10:04PM -0700, Luis Rodriguez wrote:
> On Mon, May 18, 2009 at 4:59 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > On Mon, May 18, 2009 at 04:34:49PM -0700, Dmitri Seletski wrote:
> >> Luis R. Rodriguez wrote:
> >> > On Mon, May 18, 2009 at 4:09 PM, Dmitri Seletski <drjoms@gmail.com> wrote:
> >> >
> >> >
> >> >> compat-wireless-2009-05-19 # grep CONFIG_MAC80211_DEFAULT_PS config.mk
> >> >> CONFIG_MAC80211_DEFAULT_PS=n
> >> >> CONFIG_MAC80211_DEFAULT_PS_VALUE=1
> >> >>
> >> >> make :)
> >> >>
> >> >> make unload
> >> >> make install
> >> >> modprobe ath9k
> >> >> ip link set wlan0 up
> >> >> iwconfig wlan0 essid dlink
> >> >>
> >> >> last (IMHO)relevan't dmesg messages(got loads of dmesg history today)
> >> >>
> >> >>
> >> >> [14147.633677] phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81:
> >> >> mem=0xffffc200114e0000, irq=19
> >> >> [14182.582492] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> >> >> [14216.110829] wlan0: direct probe to AP 00:1e:58:b4:f6:83 try 1
> >> >> [14216.310267] wlan0: direct probe to AP 00:1e:58:b4:f6:83 try 2
> >> >> [14216.316846] wlan0 direct probe responded
> >> >> [14216.316848] wlan0: authenticate with AP 00:1e:58:b4:f6:83
> >> >> [14216.320962] wlan0: authenticated
> >> >> [14216.320964] wlan0: associate with AP 00:1e:58:b4:f6:83
> >> >> [14216.520277] wlan0: associate with AP 00:1e:58:b4:f6:83
> >> >> [14216.527099] wlan0: deauthenticated (Reason: 9)
> >> >>
> >> >
> >> > I believe reason 9 is you're AP tells you that you are trying to
> >> > associate to it without first having authenticated.
> >> >
> >> >
> >> >> [14217.527273] wlan0: direct probe to AP 00:1e:58:b4:f6:83 try 3
> >> >> [14217.727264] wlan0: direct probe to AP 00:1e:58:b4:f6:83 timed out
> >> >> [14231.356054] wlan0: authenticate with AP 00:1e:58:b4:f6:83
> >> >> [14231.359188] wlan0: authenticated
> >> >> [14231.359191] wlan0: associate with AP 00:1e:58:b4:f6:83
> >> >> [14231.367102] wlan0: deauthenticated (Reason: 9)
> >> >>
> >> >
> >> > And we repeat this here.
> >> >
> >> >
> >> >> [14232.367277] wlan0: direct probe to AP 00:1e:58:b4:f6:83 try 1
> >> >> [14232.567284] wlan0: direct probe to AP 00:1e:58:b4:f6:83 try 2
> >> >> [14232.570837] wlan0 direct probe responded
> >> >> [14232.570843] wlan0: authenticate with AP 00:1e:58:b4:f6:83
> >> >> [14232.573250] wlan0: authenticated
> >> >> [14232.573434] wlan0: associate with AP 00:1e:58:b4:f6:83
> >> >> [14232.773283] wlan0: associate with AP 00:1e:58:b4:f6:83
> >> >> [14232.780130] wlan0: deauthenticated (Reason: 9)
> >> >>
> >> >
> >> > And here.
> >> >
> >> >
> >> >> [14233.780276] wlan0: direct probe to AP 00:1e:58:b4:f6:83 try 3
> >> >> [14233.784639] wlan0 direct probe responded
> >> >> [14233.784645] wlan0: authenticate with AP 00:1e:58:b4:f6:83
> >> >> [14233.799082] wlan0: authenticated
> >> >> [14233.799087] wlan0: association with AP 00:1e:58:b4:f6:83 timed out
> >> >>
> >> >> Access point in N mode only currently.
> >> >>
> >> >
> >> > Hm OK.
> >> >
> >> >
> >> >> Switching to mixture of N, G, B and dmesg throws this:
> >> >> [14233.799087] wlan0: association with AP 00:1e:58:b4:f6:83 timed out
> >> >> [14435.358964] wlan0: authenticate with AP 00:1e:58:b4:f6:83
> >> >> [14435.362920] wlan0: authenticated
> >> >> [14435.362922] wlan0: associate with AP 00:1e:58:b4:f6:83
> >> >> [14435.371750] wlan0: RX AssocResp from 00:1e:58:b4:f6:83 (capab=0x421
> >> >> status=0 aid=1)
> >> >> [14435.371752] wlan0: associated
> >> >> [14435.372601] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> >> >> [14435.839637] wlan0: disassociated (Reason: 8)
> >> >>
> >> >
> >> > This is the STA has left. Hm, lets try upgrading your supplicant...
> >> > Can you try upgrading to the latest from git?
> >> >
> >> > git://w1.fi/srv/git/hostap.git
> >> >
> >> > Luis
> >> >
> >>
> >> Hello Luis.
> >> I have no idea what authentication you are talking about.
> >> I am sure that i dont use any authentication.
> >
> > I'm talking about the 802.11 authentication which is always
> > required prior to association (even when no encryption is enabled).
> >
> > Can you try a newer wpa_supplicant to see if that helps?
>
> That is, use a plaintext supplicant as follows:
>
> mcgrof at tesla ~ $ cat plaintext.conf
> ctrl_interface=/var/run/wpa_supplicant
> ap_scan=1
> network={
> key_mgmt=NONE
> ssid="your-ssid"
> scan_ssid=1
> }
>
> wpa_supplicant -i wlan0 -c plaintext.conf
Hm yeah nevermind this should have no effect, plain old wext should
caused auth/assoc to go well.
Can you provide the output of the dmesg log by and running the same
commands (no wpa_supplicant) but first modprobe ath9k as follows:
modprobe ath9k debug=0x00000200
Luis
next prev parent reply other threads:[~2009-05-19 0:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 12:46 [ath9k-devel] N mode Dmitri Seletski
2009-05-16 21:23 ` Dmitri Seletski
2009-05-18 15:33 ` Luis R. Rodriguez
2009-05-18 20:56 ` Dmitri Seletski
2009-05-18 20:57 ` Dmitri Seletski
2009-05-18 21:14 ` Luis R. Rodriguez
2009-05-18 21:33 ` Dmitri Seletski
2009-05-18 22:45 ` Luis R. Rodriguez
2009-05-18 23:09 ` Dmitri Seletski
2009-05-18 23:29 ` Luis R. Rodriguez
2009-05-18 23:34 ` Dmitri Seletski
2009-05-18 23:59 ` Luis R. Rodriguez
2009-05-19 0:10 ` Luis R. Rodriguez
2009-05-19 0:24 ` Luis R. Rodriguez [this message]
2009-05-19 0:33 ` Dmitri Seletski
2009-05-19 0:41 ` Luis R. Rodriguez
2009-05-19 18:55 ` Dmitri Seletski
2009-05-26 21:42 ` Luis R. Rodriguez
[not found] ` <4A2E8611.6010401@gmail.com>
[not found] ` <20090609214205.GD12776@tesla>
[not found] ` <4A2EDB3B.9020503@gmail.com>
[not found] ` <20090609220733.GF12776@tesla>
[not found] ` <4A2EDF1E.4000707@gmail.com>
[not found] ` <4A3445CC.7010607@gmail.com>
[not found] ` <20090615160144.GB19674@tesla>
2009-06-15 17:47 ` Luis R. Rodriguez
2009-06-15 20:28 ` Dmitri Seletski
[not found] ` <4A36CFF9.6070506@gmail.com>
[not found] ` <20090616003715.GA5492@tesla>
2009-07-25 0:49 ` Dmitri Seletski
2009-07-25 17:37 ` Senthilkumar Balasubramanian
2009-07-25 18:54 ` Dmitri Seletski
2009-07-27 20:04 ` Dmitri Seletski
2009-08-05 3:43 ` Dmitri Seletski
2009-08-05 15:34 ` Luis R. Rodriguez
2009-08-05 15:54 ` Dmitri Seletski
2009-08-05 16:34 ` Dmitri Seletski
2009-08-05 17:11 ` Luis R. Rodriguez
2009-08-05 19:51 ` Dmitri Seletski
2009-08-05 20:10 ` Dmitri Seletski
2009-08-05 20:53 ` Luis R. Rodriguez
2009-08-05 20:57 ` Luis R. Rodriguez
2009-08-06 13:53 ` [ath9k-devel] N compile SUSE bnc
2009-08-06 19:42 ` Pavel Roskin
2009-09-15 11:28 ` [ath9k-devel] N mode Dmitri Seletski
2009-05-18 23:36 ` Dmitri Seletski
2009-05-18 21:09 ` Luis R. Rodriguez
2009-05-18 21:17 ` Dmitri Seletski
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=20090519002416.GU20637@tesla \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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.