linux-kernel - Re: Probe Timeouts with 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f7848160905020420t114db70dq4018bab2ab53fc8f@mail.gmail.com>
Date:	Sat, 2 May 2009 07:20:44 -0400
From:	Parag Warudkar <parag.lkml@...il.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, niel.lambrechts@...il.com
Subject: Re: Probe Timeouts with 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8

On 5/2/09, Johannes Berg <johannes@...solutions.net> wrote:
> Parag,
>
>> Just got around to downloading today's compat-wireless and it doesn't
>> work for me - frequent disconnects this time with response timeouts -
>>
>>  9731.902114] wlan1: RX ReassocResp from 00:1e:e5:6a:2c:c2
>> (capab=0x411 status=0 aid=1)
>> [ 9731.902117] wlan1: associated
>> [ 9886.744022] wlan1: no probe response from AP 00:1e:e5:6a:2c:c2 -
>> disassociating
>> [ 9887.594299] wlan1: authenticate with AP 00:1e:e5:6a:2c:c2
>> [ 9887.596953] wlan1: authenticated
>> [ 9887.596958] wlan1: associate with AP 00:1e:e5:6a:2c:c2
>> [ 9887.600997] wlan1: RX ReassocResp from 00:1e:e5:6a:2c:c2
>> (capab=0x411 status=0 aid=1)
>> [ 9887.601000] wlan1: associated
>> [ 9930.640019] wlan1: no probe response from AP 00:1e:e5:6a:2c:c2 -
>> disassociating
>
> This looks like something entirely different.
>
>> Of course mainline continues to work fine after reverting
>> 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8.
>
> Can you make sure the txpower is set correctly, on your compat? Just say
> "iwconfig wlan0" or whatever _while_ associated -- and check that it
> reports 15dBm or so.

It shows 27 dBm when associated - both for mainline and compat.
Still get the disassociated messages.

wlan1     IEEE 802.11bgn  ESSID:"pbwloft2"
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:1E:E5:6A:2C:C2
          Bit Rate=1 Mb/s   Tx-Power=27 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:21F9-23AF-AEBB-A427-4ADC-8596-C915-ADC8 [2]
Security mode:open
          Power Management:on
          Link Quality=38/70  Signal level=-72 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Parag
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/