[ath9k-devel] N mode

[Dmitri Seletski <drjoms@gmail.com>]

intermittent issue is back.
I have noticed it's back once i have 2 another new networks in reach.(i
didnt notice them before)


iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 7A:87:E9:46:02:B1
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=39/70  Signal level=-71 dBm 
                    Encryption key:on
                    ESSID:"WASC-001a6bc94d33-PHILIPS"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Ad-Hoc
                    Extra:tsf=00000150911261b8
                    Extra: Last beacon: 103ms ago
                    IE: Unknown:
0019574153432D3030316136626339346433332D5048494C495053
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 03010B
                    IE: Unknown: 06020000
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD06001018020010
          Cell 02 - Address: 00:1E:58:B4:F6:83
                    Channel:7
                    Frequency:2.442 GHz (Channel 7)
                    Quality=70/70  Signal level=-34 dBm 
                    Encryption key:off
                    ESSID:"dlink"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000104df5
                    Extra: Last beacon: 30ms ago
                    IE: Unknown: 0005646C696E6B
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030107
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
                    IE: Unknown:
DD1E00904C334E1003FFFF000000000000000000000000000000000000000000
                    IE: Unknown:
2D1A4E1003FFFF000000000000000000000000000000000000000000
                    IE: Unknown:
DD1A00904C34070B0800000000000000000000000000000000000000
                    IE: Unknown:
3D16070B0800000000000000000000000000000000000000
                    IE: Unknown: DD0900037F01010000FF7F
                    IE: Unknown: DD0A00037F04010001000000
          Cell 03 - Address: 00:1F:1F:21:AB:7C
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=25/70  Signal level=-85 dBm 
                    Encryption key:off
                    ESSID:"INTELLINET"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Unknown/bug
                    Extra:tsf=0000005eb81d3146
                    Extra: Last beacon: 107ms ago
                    IE: Unknown: 000A494E54454C4C494E4554
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 03010B
                    IE: Unknown: 32040C183060
                    IE: Unknown: 33082001020304050607
                    IE: Unknown: 33082105060708090A0B
                    IE: Unknown:
DD270050F204104A0001101044000101104700102880288028801880A880001F1F21AB7C103C000101
                    IE: Unknown: 050400030000
                    IE: Unknown: 2A0104
                    IE: Unknown:
2D1AEE1117FFFF0000010000000000000000000000000C0000000000
                    IE: Unknown:
3D160B070100000000000000000000000000000000000000
                    IE: Unknown: 7F0101
                    IE: Unknown:
DD180050F2020101000003A4000027A400004243600062323000
                    IE: Unknown:
DD1E00904C33EE1117FFFF0000010000000000000000000000000C0000000000
                    IE: Unknown:
DD1A00904C340B070100000000000000000000000000000000000000
                    IE: Unknown: DD07000C4304000000




i can do more of logging on wpa supplicant. right now i am mentally
incapable of continuing. this is in mixed b/n/g mode. i only care about
gmode,  to make it work. once g mode is sorted lets try to sort out
nmode as well please.


wpa supplicant config below:
cat /root/wpa.conf
network={
    ssid="dlink"
    priority=4
    key_mgmt=NONE
}


Luis R. Rodriguez wrote:
> On Wed, Aug 05, 2009 at 01:10:19PM -0700, Dmitri Seletski wrote:
>   
>> Sorry, please cut out the emotional part.
>> script seemed to help me a bit...
>>     
>
> Dmitry, I don't have time to look at your logs right now, but
> am hoping someone in our team will be soon.
>
> But as far as your disconnects are concerned I'll note that
> some others users were experiencing similar issues when using
> wireless-testing, a few patches were added recently to address
> some of these issues, namely:
>
> commit 3810f40f71ccf690bc10152fb0706f7a4e9b8e87
> Author: Maxim Levitsky <maximlevitsky@gmail.com>
> Date:   Fri Jul 31 18:54:23 2009 +0300
>
>     mac80211: Increase timeouts for station polling
>     
>     Do a probe request every 30 seconds, and wait for probe response,
>     half a second This should lower the traffic that card sends, thus save
>     power Wainting longer for response makes probe more robust against
>     'slow' access points
>     
>     Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
>     Acked-by: Johannes Berg <johannes@sipsolutions.net>
>     Tested-by: Marcel Holtmann <marcel@holtmann.org>
>     Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> commit 9004c35534fbdb452d2f544c8ae59dcadc486465
> Author: Maxim Levitsky <maximlevitsky@gmail.com>
> Date:   Fri Jul 31 18:54:12 2009 +0300
>
>     mac80211: Retry probe request few times
>     
>     Retry 5 times  (chosen arbitary ), before assuming
>     that station is out of range.
>     
>     Fixes frequent disassociations while connected to weak,
>     and sometimes even strong access points.
>     
>     Signed-off-by: Maxim Levitky <maximlevitsky@gmail.com>
>     Acked-by: Johannes Berg <johannes@sipsolutions.net>
>     Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
>
> Check git log net/mac80211/ and see if you see these there.
>
> Also, there does seem to be a regression on wireless-testing
> right now regarding re-association, I'll let you know more
> about it the more I find but I believe Johannes is already
> working on it, I am not really sure of the details or if
> this can be affecting you right now.
>
> Also, 'iw dev wlan0 connect foo' will work but expect to be
> disconnected eventually due to noise or in your case due to
> inactivity. Instead of scripting out a way to always connect
> you can just use wpa_supplicant to help 'roam' so that it
> keeps re-associating for you if disconnected. I tend to 
> use 'iw dev wlan0 connect foo' only to test things, if I want
> to ensure I always remain connected I use wpa_supplicant with
> roaming enabled, I do this even with no encryption enabled.
>
> mcgrof at tux ~ $ cat mosca.conf 
> ctrl_interface=/var/run/wpa_supplicant
> ap_scan=1
> network={
> 	ssid="mosca"
> 	scan_ssid=1
> 	key_mgmt=NONE
> }
>
> sudo wpa_supplicant -D nl80211 -c mosca.conf -i wlan0
>
> While at it you might as well get the latest supplicant from git:
>
> git clone git://w1.fi/srv/git/hostap.git
> cd hostap/wpa_supplicant
> cp defconfig .config
>
> Then edit .config and ensure you have these enabled:
>
> # Driver interface for generic Linux wireless extensions
> CONFIG_DRIVER_WEXT=y
> # Driver interface for Linux drivers using the nl80211 kernel interface
> CONFIG_DRIVER_NL80211=y
>
> Build it and install it.
>
> Keep in mind we need to address two issues here:
>
> 1) Your current disconnect issues
> 2) Your card not being able to complete association (was this the issue?)
>    to your AP when 802.11n is enabled.
>
> We should focus on both for sure but be sure to help try to isolate the
> issues so we don't get them mixed up.
>
> To help more with this it may help for you to put logs for both separetely,
> from the kernel, 'iw event -t', and the wpa_supplicant logs with "-d" added
> to increase verbosity.
>
> Can you please create two directories and put logs into them for both of these
> issues? The easier it is to separate the issues and review the logs the easier
> it will be review your issues and help you resolve them.
>
> Don't bother with tcpdump/wireshark dumps for now. Only provide them if
> you are asked.
>
>   Luis
>   

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: iwevent.txt
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090915/d10d1d3e/attachment-0002.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wpa_sup.txt
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090915/d10d1d3e/attachment-0003.txt