Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Sedat Dilek]

Hi,

a few hours ago I compiled a new kernel from upstream and put
wireless-testing master-2009-09-30 on top of it.

Last commit a1bec0ecfc76281d5e1ebd33435c67da7dd0fe71
wext: refactor

linux-2.6/master:
84d88d5: Merge branch 'sched-fixes-for-linus' of
git://git./linux/kernel/git/tip/linux-2.6-tip

After installation of the above described kernel, I could not connect
to my AP using wext driver and wpasupplicant (0.6.9-3) from Debian/sid
[1].
With ath5k I could not establish a network connection neither via DHCP
nor via static-IP to my AP (iwl3945 on a second machine works with
self-debianized wpasupplicant 0.7.0+ and static-IP, same kernel).

Just for clarification:
Does wext refactor need a wpasupplicant >= 0.7.0 from hostap GIT repository [2]?

Below you will find some needful informations of my configuration and system.

Kind Regards,
- Sedat -

P.S.:
I can offer a debianized wpasupplicant package for 32bit, if you like.

[1] http://packages.debian.org/sid/wpasupplicant
[2] http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=summary

---- NEEDFUL INFORMATIONS ----

# lspci -nnvv | grep -i ath
02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
802.11abg NIC [168c:1014] (rev 01)
	Kernel driver in use: ath5k

# ps axu | grep -v grep | grep wpa
root      1411  0.0  0.1   4916  1124 ?        Ss   10:59   0:00
/sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0
-D wext -C /var/run/wpa_supplicant

# wpa_cli -iwlan0 status
bssid=00:04:0e:e4:00:3d
ssid=$mySSID
id=0
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=$myIPADDR

# cat /proc/version
Linux version 2.6.32-rc1-iniza-686-kms (Debian 2.6.32~rc1-5)
(sedat.dilek@gmail.com) (gcc version 4.4.1 (Debian 4.4.1-4) ) #1 SMP
PREEMPT Thu Oct 1 04:57:49 CEST 2009

Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Sedat Dilek]

For the sake of completeness:
Herre the WEXT config parameters in kernel dot-config:

# grep -i wext /boot/config-$(uname -r)
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_CFG80211_WEXT=y

- Sedat -

On Thu, Oct 1, 2009 at 11:47 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Hi,
>
> a few hours ago I compiled a new kernel from upstream and put
> wireless-testing master-2009-09-30 on top of it.
>
> Last commit a1bec0ecfc76281d5e1ebd33435c67da7dd0fe71
> wext: refactor
>
> linux-2.6/master:
> 84d88d5: Merge branch 'sched-fixes-for-linus' of
> git://git./linux/kernel/git/tip/linux-2.6-tip
>
> After installation of the above described kernel, I could not connect
> to my AP using wext driver and wpasupplicant (0.6.9-3) from Debian/sid
> [1].
> With ath5k I could not establish a network connection neither via DHCP
> nor via static-IP to my AP (iwl3945 on a second machine works with
> self-debianized wpasupplicant 0.7.0+ and static-IP, same kernel).
>
> Just for clarification:
> Does wext refactor need a wpasupplicant >= 0.7.0 from hostap GIT repository [2]?
>
> Below you will find some needful informations of my configuration and system.
>
> Kind Regards,
> - Sedat -
>
> P.S.:
> I can offer a debianized wpasupplicant package for 32bit, if you like.
>
> [1] http://packages.debian.org/sid/wpasupplicant
> [2] http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=summary
>
> ---- NEEDFUL INFORMATIONS ----
>
> # lspci -nnvv | grep -i ath
> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
> 802.11abg NIC [168c:1014] (rev 01)
>        Kernel driver in use: ath5k
>
> # ps axu | grep -v grep | grep wpa
> root      1411  0.0  0.1   4916  1124 ?        Ss   10:59   0:00
> /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0
> -D wext -C /var/run/wpa_supplicant
>
> # wpa_cli -iwlan0 status
> bssid=00:04:0e:e4:00:3d
> ssid=$mySSID
> id=0
> pairwise_cipher=CCMP
> group_cipher=CCMP
> key_mgmt=WPA2-PSK
> wpa_state=COMPLETED
> ip_address=$myIPADDR
>
> # cat /proc/version
> Linux version 2.6.32-rc1-iniza-686-kms (Debian 2.6.32~rc1-5)
> (sedat.dilek@gmail.com) (gcc version 4.4.1 (Debian 4.4.1-4) ) #1 SMP
> PREEMPT Thu Oct 1 04:57:49 CEST 2009
>

Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Thu, 2009-10-01 at 11:47 +0200, Sedat Dilek wrote:

> a few hours ago I compiled a new kernel from upstream and put
> wireless-testing master-2009-09-30 on top of it.
> 
> Last commit a1bec0ecfc76281d5e1ebd33435c67da7dd0fe71
> wext: refactor
> 
> linux-2.6/master:
> 84d88d5: Merge branch 'sched-fixes-for-linus' of
> git://git./linux/kernel/git/tip/linux-2.6-tip
> 
> After installation of the above described kernel, I could not connect
> to my AP using wext driver and wpasupplicant (0.6.9-3) from Debian/sid
> [1].
> With ath5k I could not establish a network connection neither via DHCP
> nor via static-IP to my AP (iwl3945 on a second machine works with
> self-debianized wpasupplicant 0.7.0+ and static-IP, same kernel).
> 
> Just for clarification:
> Does wext refactor need a wpasupplicant >= 0.7.0 from hostap GIT repository [2]?

Should be ok. Can we see wpa_supplicant -ddt log please?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Sedat Dilek]

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

Here the logs for wpasupplicant v06.9 and v0.7.0.

$ wpa_supplicant -v

$ /sbin/wpa_supplicant -ddt -B -P /var/run/wpa_supplicant.wlan0.pid -i
wlan0 -D wext -C /var/run/wpa_supplicant

- Sedat -

On Thu, Oct 1, 2009 at 9:47 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> On Thu, 2009-10-01 at 11:47 +0200, Sedat Dilek wrote:
>
>> a few hours ago I compiled a new kernel from upstream and put
>> wireless-testing master-2009-09-30 on top of it.
>>
>> Last commit a1bec0ecfc76281d5e1ebd33435c67da7dd0fe71
>> wext: refactor
>>
>> linux-2.6/master:
>> 84d88d5: Merge branch 'sched-fixes-for-linus' of
>> git://git./linux/kernel/git/tip/linux-2.6-tip
>>
>> After installation of the above described kernel, I could not connect
>> to my AP using wext driver and wpasupplicant (0.6.9-3) from Debian/sid
>> [1].
>> With ath5k I could not establish a network connection neither via DHCP
>> nor via static-IP to my AP (iwl3945 on a second machine works with
>> self-debianized wpasupplicant 0.7.0+ and static-IP, same kernel).
>>
>> Just for clarification:
>> Does wext refactor need a wpasupplicant >= 0.7.0 from hostap GIT repository [2]?
>
> Should be ok. Can we see wpa_supplicant -ddt log please?
>
> johannes
>

[-- Attachment #2: wpasupplicant-069.txt --]
[-- Type: text/plain, Size: 3646 bytes --]

wpa_supplicant v0.6.9
Copyright (c) 2003-2009, Jouni Malinen <j@w1.fi> and contributors
1254429474.982896: Initializing interface 'wlan0' conf 'N/A' driver 'wext' ctrl_interface '/var/run/wpa_supplicant' bridge 'N/A'
1254429475.079713: Interface wlan0 set UP - waiting a second for the driver to complete initialization
1254429476.080009: SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
1254429476.080032:   capabilities: key_mgmt 0xf enc 0xf flags 0x0
1254429476.084533: WEXT: Operstate: linkmode=1, operstate=5
1254429476.084633: Own MAC address: 00:05:4e:46:b4:1f
1254429476.084644: wpa_driver_wext_set_wpa
1254429476.084658: wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
1254429476.084677: wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
1254429476.084689: wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
1254429476.084699: wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
1254429476.084710: wpa_driver_wext_set_countermeasures
1254429476.084717: wpa_driver_wext_set_drop_unencrypted
1254429476.084724: RSN: flushing PMKID list in the driver
1254429476.084792: Setting scan request: 0 sec 100000 usec
1254429476.084849: WPS: UUID based on MAC address - hexdump(len=16): 55 2a 23 9b 14 1f 53 7a 89 c6 98 d8 83 ac a7 26
1254429476.084876: WPS: Build Beacon and Probe Response IEs
1254429476.084888: WPS:  * Version
1254429476.084896: WPS:  * Wi-Fi Protected Setup State (0)
1254429476.084904: WPS:  * Version
1254429476.084908: WPS:  * Wi-Fi Protected Setup State (0)
1254429476.084913: WPS:  * Response Type (2)
1254429476.084921: WPS:  * UUID-E
1254429476.084928: WPS:  * Manufacturer
1254429476.084933: WPS:  * Model Name
1254429476.084938: WPS:  * Model Number
1254429476.084942: WPS:  * Serial Number
1254429476.084946: WPS:  * Primary Device Type
1254429476.084951: WPS:  * Device Name
1254429476.084955: WPS:  * Config Methods (0)
1254429476.084960: WPS:  * RF Bands (3)
1254429476.088433: EAPOL: SUPP_PAE entering state DISCONNECTED
1254429476.088441: EAPOL: KEY_RX entering state NO_KEY_RECEIVE
1254429476.088448: EAPOL: SUPP_BE entering state INITIALIZE
1254429476.088458: EAP: EAP entering state DISABLED
1254429476.088486: Using existing control interface directory.
1254429476.088527: ctrl_iface bind(PF_UNIX) failed: Address already in use
1254429476.088543: ctrl_iface exists and seems to be in use - cannot override it
1254429476.088548: Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
1254429476.088563: Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

1254429476.088573: Failed to add interface wlan0
1254429476.088582: State: DISCONNECTED -> DISCONNECTED
1254429476.088592: wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
1254429476.088599: WEXT: Operstate: linkmode=-1, operstate=5
1254429476.088615: No keys have been configured - skip key clearing
1254429476.088621: EAPOL: External notification - portEnabled=0
1254429476.088628: EAPOL: External notification - portValid=0
1254429476.088633: wpa_driver_wext_set_wpa
1254429476.088642: wpa_driver_wext_set_drop_unencrypted
1254429476.088649: wpa_driver_wext_set_countermeasures
1254429476.088655: No keys have been configured - skip key clearing
1254429476.089339: Cancelling scan request
1254429476.089349: Cancelling authentication timeout
1254429476.089411: WEXT: Operstate: linkmode=0, operstate=6

[-- Attachment #3: wpasupplicant-070.txt --]
[-- Type: text/plain, Size: 3961 bytes --]

wpa_supplicant v0.7.0
Copyright (c) 2003-2009, Jouni Malinen <j@w1.fi> and contributors
1254429555.677208: Initializing interface 'wlan0' conf 'N/A' driver 'wext' ctrl_interface '/var/run/wpa_supplicant' bridge 'N/A'
1254429555.733937: Interface wlan0 set UP - waiting a second for the driver to complete initialization
1254429556.734139: SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
1254429556.734160:   capabilities: key_mgmt 0xf enc 0xf flags 0x0
1254429556.737759: WEXT: Operstate: linkmode=1, operstate=5
1254429556.737818: Own MAC address: 00:05:4e:46:b4:1f
1254429556.737825: wpa_driver_wext_set_wpa
1254429556.737831: wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
1254429556.737841: wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
1254429556.737846: wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
1254429556.737851: wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
1254429556.737855: wpa_driver_wext_set_countermeasures
1254429556.737858: wpa_driver_wext_set_drop_unencrypted
1254429556.737861: RSN: flushing PMKID list in the driver
1254429556.737879: Setting scan request: 0 sec 100000 usec
1254429556.737948: WPS: UUID based on MAC address - hexdump(len=16): 55 2a 23 9b 14 1f 53 7a 89 c6 98 d8 83 ac a7 26
1254429556.737959: WPS: Build Beacon and Probe Response IEs
1254429556.737965: WPS:  * Version
1254429556.737968: WPS:  * Wi-Fi Protected Setup State (0)
1254429556.737972: WPS:  * Version
1254429556.737974: WPS:  * Wi-Fi Protected Setup State (0)
1254429556.737977: WPS:  * Response Type (2)
1254429556.737979: WPS:  * UUID-E
1254429556.737982: WPS:  * Manufacturer
1254429556.737984: WPS:  * Model Name
1254429556.737986: WPS:  * Model Number
1254429556.737988: WPS:  * Serial Number
1254429556.737991: WPS:  * Primary Device Type
1254429556.737993: WPS:  * Device Name
1254429556.737995: WPS:  * Config Methods (0)
1254429556.737997: WPS:  * RF Bands (3)
1254429556.739312: EAPOL: SUPP_PAE entering state DISCONNECTED
1254429556.739316: EAPOL: Supplicant port status: Unauthorized
1254429556.739319: EAPOL: KEY_RX entering state NO_KEY_RECEIVE
1254429556.739321: EAPOL: SUPP_BE entering state INITIALIZE
1254429556.739325: EAP: EAP entering state DISABLED
1254429556.739328: EAPOL: Supplicant port status: Unauthorized
1254429556.739331: EAPOL: Supplicant port status: Unauthorized
1254429556.739343: Using existing control interface directory.
1254429556.739361: ctrl_iface bind(PF_UNIX) failed: Address already in use
1254429556.739371: ctrl_iface exists and seems to be in use - cannot override it
1254429556.739373: Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
1254429556.739380: Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

1254429556.739385: Failed to add interface wlan0
1254429556.739388: No keys have been configured - skip key clearing
1254429556.739391: State: DISCONNECTED -> DISCONNECTED
1254429556.739396: wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
1254429556.739399: WEXT: Operstate: linkmode=-1, operstate=5
1254429556.739407: EAPOL: External notification - portEnabled=0
1254429556.739410: EAPOL: Supplicant port status: Unauthorized
1254429556.739412: EAPOL: External notification - portValid=0
1254429556.739415: EAPOL: Supplicant port status: Unauthorized
1254429556.739418: wpa_driver_wext_set_wpa
1254429556.739422: wpa_driver_wext_set_drop_unencrypted
1254429556.739425: wpa_driver_wext_set_countermeasures
1254429556.739428: No keys have been configured - skip key clearing
1254429556.739682: Cancelling scan request
1254429556.739686: Cancelling authentication timeout
1254429556.739704: WEXT: Operstate: linkmode=0, operstate=6

Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 656 bytes --]

On Thu, 2009-10-01 at 22:44 +0200, Sedat Dilek wrote:
> 
> 1254429476.088527: ctrl_iface bind(PF_UNIX) failed: Address already in use
> 1254429476.088543: ctrl_iface exists and seems to be in use - cannot override it
> 1254429476.088548: Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
> 1254429476.088563: Failed to initialize control interface '/var/run/wpa_supplicant'.
> You may have another wpa_supplicant process already running or the file was
> left by an unclean termination of wpa_supplicant in which case you will need
> to manually remove this file before starting wpa_supplicant again.

Umm...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Sedat Dilek]

Problem with wpasupplicant v0.6.9 seems to be fixed with my latest kernel:

Upstream (2.6.32-rc1-git2) with wireless-testing (master-2009-09-30) on top

I am sorry if I confused people...

- Sedat -

On Thu, Oct 1, 2009 at 11:47 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Hi,
>
> a few hours ago I compiled a new kernel from upstream and put
> wireless-testing master-2009-09-30 on top of it.
>
> Last commit a1bec0ecfc76281d5e1ebd33435c67da7dd0fe71
> wext: refactor
>
> linux-2.6/master:
> 84d88d5: Merge branch 'sched-fixes-for-linus' of
> git://git./linux/kernel/git/tip/linux-2.6-tip
>
> After installation of the above described kernel, I could not connect
> to my AP using wext driver and wpasupplicant (0.6.9-3) from Debian/sid
> [1].
> With ath5k I could not establish a network connection neither via DHCP
> nor via static-IP to my AP (iwl3945 on a second machine works with
> self-debianized wpasupplicant 0.7.0+ and static-IP, same kernel).
>
> Just for clarification:
> Does wext refactor need a wpasupplicant >= 0.7.0 from hostap GIT repository [2]?
>
> Below you will find some needful informations of my configuration and system.
>
> Kind Regards,
> - Sedat -
>
> P.S.:
> I can offer a debianized wpasupplicant package for 32bit, if you like.
>
> [1] http://packages.debian.org/sid/wpasupplicant
> [2] http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=summary
>
> ---- NEEDFUL INFORMATIONS ----
>
> # lspci -nnvv | grep -i ath
> 02:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5212
> 802.11abg NIC [168c:1014] (rev 01)
>        Kernel driver in use: ath5k
>
> # ps axu | grep -v grep | grep wpa
> root      1411  0.0  0.1   4916  1124 ?        Ss   10:59   0:00
> /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0
> -D wext -C /var/run/wpa_supplicant
>
> # wpa_cli -iwlan0 status
> bssid=00:04:0e:e4:00:3d
> ssid=$mySSID
> id=0
> pairwise_cipher=CCMP
> group_cipher=CCMP
> key_mgmt=WPA2-PSK
> wpa_state=COMPLETED
> ip_address=$myIPADDR
>
> # cat /proc/version
> Linux version 2.6.32-rc1-iniza-686-kms (Debian 2.6.32~rc1-5)
> (sedat.dilek@gmail.com) (gcc version 4.4.1 (Debian 4.4.1-4) ) #1 SMP
> PREEMPT Thu Oct 1 04:57:49 CEST 2009
>

Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Holger Schurig]

In both logs you have

1254429476.088527: ctrl_iface bind(PF_UNIX) failed: Address already in use
1254429476.088543: ctrl_iface exists and seems to be in use - cannot override it
1254429476.088548: Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore

are you sure that no other wpa_supplicant did
run when you made the logs?

If yes, then just remove the file and re-run wpa_supplicant.
Be sure to run it as "root".

-- 
http://www.holgerschurig.de

Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?

[Sedat Dilek]

The logs were not helpful (running wpa_supplicant in background), I
send new ones to Johannes via PM directly.
I was not sure if the logs had sensitive informations.
The problem was discussed on IRC and the problem with v0.6.9 does not
exist anymore.

- Sedat -

On Fri, Oct 2, 2009 at 9:10 AM, Holger Schurig
<hs4233@mail.mn-solutions.de> wrote:
> In both logs you have
>
> 1254429476.088527: ctrl_iface bind(PF_UNIX) failed: Address already in use
> 1254429476.088543: ctrl_iface exists and seems to be in use - cannot override it
> 1254429476.088548: Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
>
> are you sure that no other wpa_supplicant did
> run when you made the logs?
>
> If yes, then just remove the file and re-run wpa_supplicant.
> Be sure to run it as "root".
>
> --
> http://www.holgerschurig.de
>