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]
Date:	Thu, 17 Sep 2009 08:32:33 +0200
From:	Maciej Rutecki <maciej.rutecki@...il.com>
To:	reinette chatre <reinette.chatre@...el.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Wireless List <linux-wireless@...r.kernel.org>,
	"ilw@...ux.intel.com" <ilw@...ux.intel.com>,
	"Zhu, Yi" <yi.zhu@...el.com>
Subject: Re: WARNING: at net/mac80211/scan.c:267 ieee80211_scan_completed+0x299/0x2b0 
	[mac80211]()

2009/9/17 reinette chatre <reinette.chatre@...el.com>:
[...]
>
> I think there is a potential race here. You start wpa_supplicant in
> background and then immediately request an IP. It is not guaranteed at
> this point that you are associated.
>
> Could you perform the last three steps of your script manually?
>
> Reinette
>
>
>

root@...is:/home/maciek# INTERFACE=wlan0
root@...is:/home/maciek# WPA_FILE=/etc/wpa_supplicant/wpa_supplicant.conf
root@...is:/home/maciek# DRIVER=wext
root@...is:/home/maciek# ifconfig eth0 down
root@...is:/home/maciek# killall dhclient3

Dmesg:
[  130.925689] b44: eth0: powering down PHY

root@...is:/home/maciek# ifconfig $INTERFACE up

Demsg:
[  171.563937] iwl3945 0000:08:00.0: firmware: requesting iwlwifi-3945-2.ucode
[  171.611178] iwl3945 0000:08:00.0: loaded firmware version 15.32.2.9
[  171.688664] Registered led device: iwl-phy0::radio
[  171.688759] Registered led device: iwl-phy0::assoc
[  171.688802] Registered led device: iwl-phy0::RX
[  171.688844] Registered led device: iwl-phy0::TX

root@...is:/home/maciek# killall wpa_supplicant &> /dev/null
(wait 5 seconds)
root@...is:/home/maciek# wpa_supplicant -c $WPA_FILE -D $DRIVER -i $INTERFACE -B
(and wait)

Dmesg:
[  249.340094] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  249.345339] wlan0 direct probe responded
[  249.345347] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  249.347122] wlan0: authenticated
[  249.347152] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  249.349703] wlan0: RX AssocResp from 00:1b:11:f6:0f:28 (capab=0x431
status=0 aid=1)
[  249.349711] wlan0: associated
[  253.411858] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason:
6)
[  256.116488] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  256.118910] wlan0 direct probe responded
[  256.118918] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  256.120663] wlan0: authenticated
[  256.120694] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  256.122944] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28
(capab=0x431 status=0 aid=1)
[  256.122951] wlan0: associated

[...]

[  353.353780] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason: 6)
[  356.070680] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  356.073112] wlan0 direct probe responded
[  356.073121] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  356.074849] wlan0: authenticated
[  356.074879] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  356.077160] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28
(capab=0x431 status=0 aid=1)
[  356.077168] wlan0: associated


(Stop wainting)
root@...is:/home/maciek# dhclient $INTERFACE
Internet Systems Consortium DHCP Client V3.1.2p1
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:02:c3:96:a8
Sending on   LPF/wlan0/00:13:02:c3:96:a8
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPOFFER from 192.168.0.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
Reloading /etc/samba/smb.conf: smbd only.
bound to 192.168.0.102 -- renewal in 474672 seconds.

Dmesg:
[  390.228036] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason:
6)
[  392.969750] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  392.972333] wlan0 direct probe responded
[  392.972342] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  392.974072] wlan0: authenticated

[...]

[  425.722523] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  425.724773] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28
(capab=0x431 status=0 aid=1)
[  425.724782] wlan0: associated
[  429.231829] wlan0: deauthenticated from 00:1b:11:f6:0f:28 (Reason: 6)
[  431.936205] wlan0: direct probe to AP 00:1b:11:f6:0f:28 (try 1)
[  431.938624] wlan0 direct probe responded
[  431.938631] wlan0: authenticate with AP 00:1b:11:f6:0f:28 (try 1)
[  431.940470] wlan0: authenticated
[  431.940502] wlan0: associate with AP 00:1b:11:f6:0f:28 (try 1)
[  431.942754] wlan0: RX ReassocResp from 00:1b:11:f6:0f:28
(capab=0x431 status=0 aid=1)
[  431.942761] wlan0: associated

root@...is:/home/maciek# iwconfig $INTERFACE
wlan0     IEEE 802.11abg  ESSID:"x"
          Mode:Managed  Frequency:2.457 GHz  Access Point: 00:1B:11:F6:0F:28
          Bit Rate=54 Mb/s   Tx-Power=15 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=53/70  Signal level=-57 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@...is:/home/maciek# ping onet.pl
PING onet.pl (213.180.146.27) 56(84) bytes of data.
64 bytes from s4.m1r2.onet.pl (213.180.146.27): icmp_seq=1 ttl=53 time=18.3 ms
64 bytes from s4.m1r2.onet.pl (213.180.146.27): icmp_seq=2 ttl=53 time=21.0 ms
^C
--- onet.pl ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 18.395/19.702/21.009/1.307 ms

===============================

Compare to 2.6.31:
root@...is:/home/maciek# /home/maciek/bin/wifi/wifi_wpa.sh
Internet Systems Consortium DHCP Client V3.1.2p1
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:13:02:c3:96:a8
Sending on   LPF/wlan0/00:13:02:c3:96:a8
Sending on   Socket/fallback
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
Reloading /etc/samba/smb.conf: smbd only.
bound to 192.168.0.102 -- renewal in 596714 seconds.
wlan0     IEEE 802.11abg  ESSID:"x"
          Mode:Managed  Frequency:2.457 GHz  Access Point: 00:1B:11:F6:0F:28
          Bit Rate=1 Mb/s   Tx-Power=15 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption
key:D99A-9047-D4B3-05CD-5AD4-041C-A1A1-577D-CF2C-7BC4-1F49-08F8-9802-2A2D-F5B3-0861
[2]
          Power Management:off
          Link Quality=50/70  Signal level=-60 dBm  Noise level=-127 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Demsg:	
[   92.188241] b44: eth0: powering down PHY
[   92.191643] iwl3945 0000:08:00.0: firmware: requesting iwlwifi-3945-2.ucode
[   92.305225] iwl3945 0000:08:00.0: loaded firmware version 15.32.2.9
[   92.380738] Registered led device: iwl-phy0::radio
[   92.381651] Registered led device: iwl-phy0::assoc
[   92.381685] Registered led device: iwl-phy0::RX
[   92.381708] Registered led device: iwl-phy0::TX
[   98.353640] wlan0: authenticate with AP 00:1b:11:f6:0f:28
[   98.355401] wlan0: authenticated
[   98.355407] wlan0: associate with AP 00:1b:11:f6:0f:28
[   98.357622] wlan0: RX AssocResp from 00:1b:11:f6:0f:28 (capab=0x431
status=0 aid=1)
[   98.357630] wlan0: associated


-- 
Maciej Rutecki
http://www.maciek.unixy.pl
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ