I cannot connect to my WIFI/WPA network using iwl3945 driver.
debian:/home/u# iwlist wlan0_rename scanning
wlan0_rename Scan completed :
Cell 01 - Address: 00:1D:7E:43:B3:3F
ESSID:"APTEKA"
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=73/100 Signal level:-61 dBm Noise
level=-127 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
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; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000003b5a033363
debian:/home/u# cat /etc/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
ssid="APTEKA"
scan_ssid=1
key_mgmt=WPA-PSK
psk="xxx"
}
debian:/home/u# wpa_supplicant -Dwext -iwlan0_rename
-c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0_rename' conf '/etc/wpa_supplicant.conf'
driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=root'
Line: 2 - start of a new network block
ssid - hexdump_ascii(len=6):
41 50 54 45 4b 41 APTEKA
scan_ssid=1 (0x1)
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='APTEKA'
Initializing interface (2) 'wlan0_rename'
Interface wlan0_rename set UP - waiting a second for the driver to
complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:77:bc:bb:ec
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
ctrl_interface_group=0 (from group name 'root')
Added interface wlan0_rename
Ignore event for foreign ifindex 7
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0_rename' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=6):
41 50 54 45 4b 41 APTEKA
Trying to get current scan results first without requesting a new scan
to speed up initial association
Received 0 bytes of scan results (0 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=16
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=11)
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=2462)
Received 300 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=6):
41 50 54 45 4b 41 APTEKA
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=16
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=11)
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=2462)
Received 300 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=16
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=11)
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=2462)
Received 300 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=6):
41 50 54 45 4b 41 APTEKA
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=16
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=11)
Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=2462)
Received 300 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:00:01:00:00:1d ssid='' wpa_ie_len=0 rsn_ie_len=0 caps=0x10
skip - SSID mismatch
No suitable AP found.
Setting scan request: 5 sec 0 usec
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0_rename
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6
I've used driver included in kernel 2.6.24.2 and
compat-wireless-2008-06-13 . The same results
Regards
Maciek Kaliszewski
----------------------------------------------------------------------
Z Map24 Twoja droga jest prosta! Sprawdz!
kliknij >>> http://link.interia.pl/f1e3b
On Sat, Jun 14, 2008 at 11:42:03AM +0200, Johannes Berg wrote:
> Yeah, it should be in there. Building a 64-bit wpa supplicant is quite
> hard unless you have all 64-bit libs already, so maybe it's easier to
> apply Dave's patches.
Yes, I know.. I did it once on PS3 and it took some time figuring out
which packages I need to install to get proper 64-bit libraries and
compiler available. It didn't help that that was the first time I used
the particular distro, but anyway, it is doable if one does not want to
update the kernel. I hope that the patches go in soon, though, since
neither patching a kernel or building 64-bit user space from scratch is
something I would consider a good end user requirement.. ;-)
--
Jouni Malinen PGP id EFC895FA
On Fri, Jun 13, 2008 at 02:18:18PM +0200, Maciek Kaliszewski wrote:
> I cannot connect to my WIFI/WPA network using iwl3945 driver.
Any chance that adding a line like this in /etc/modprobe.conf is
helpful?
options iwl3945 disable_hw_scan=1
Worth a shot... :-)
John
--
John W. Linville
[email protected]
Tomas Winkler wrote:
>
>> Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=11)
>> Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=2462)
>>
>
> What system kernel are you using. This looks something we've already solved...
> Tomas
> --
>
Kernel is
uname -a
Linux debian 2.6.24.2 #1 SMP Mon Feb 11 10:22:07 UTC 2008 x86_64 GNU/Linux
I've used iwl3945 driver included in this kernel , but also I've tried
compat-wireless-2008-06-13 . No change.
Regards
Maciek Kaliszewski
----------------------------------------------------------------------
Podbij Dziki Zachod!Gra strategiczna online
Sprawdz >>> http://link.interia.pl/f1dff
On Sat, Jun 14, 2008 at 12:24:09AM +0200, Maciek Kaliszewski wrote:
> You are right . It may be wpa_supplicant issue . (I'm moving to hostap list
> as soon as I get subscribed )
> Kernel is amd64 and wpa_supplicant is i386 binary.
Isn't this the known issue with ioctl compat code when using 64-bit
kernel with 32-bit user space? wireless-tools has some workaround code
for figuring out what kernel is trying to say in WEXT data, but
wpa_supplicant does not have such workaround since I do not believe it
belongs to every user space program that is using WEXT.
If I've understood correctly, Dave Miller is working on cleaning up the
compat WEXT code (see "Proper compat WEXT support" thread from June 3rd
for the patch series). I would hope that that fixes issues with
64/32-bit systems without require all user space programs to be modified
to be aware of the bogus data from the kernel. As a temporary
workaround, it might help to build 64-bit wpa_supplicant for that
kernel.
--
Jouni Malinen PGP id EFC895FA
On Fri, Jun 13, 2008 at 3:18 PM, Maciek Kaliszewski <[email protected]> wrote:
> I cannot connect to my WIFI/WPA network using iwl3945 driver.
>
> debian:/home/u# iwlist wlan0_rename scanning
> wlan0_rename Scan completed :
> Cell 01 - Address: 00:1D:7E:43:B3:3F
> ESSID:"APTEKA"
> Mode:Master
> Channel:11
> Frequency:2.462 GHz (Channel 11)
> Quality=73/100 Signal level:-61 dBm Noise level=-127 dBm
> Encryption key:on
> IE: WPA Version 1
> Group Cipher : TKIP
> Pairwise Ciphers (1) : TKIP
> Authentication Suites (1) : PSK
> 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; 6 Mb/s; 9 Mb/s
> 12 Mb/s; 48 Mb/s
> Extra:tsf=0000003b5a033363
>
> debian:/home/u# cat /etc/wpa_supplicant.conf
> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
> network={
> ssid="APTEKA"
> scan_ssid=1
> key_mgmt=WPA-PSK
> psk="xxx"
> }
>
>
> debian:/home/u# wpa_supplicant -Dwext -iwlan0_rename
> -c/etc/wpa_supplicant.conf -dd
> Initializing interface 'wlan0_rename' conf '/etc/wpa_supplicant.conf' driver
> 'wext' ctrl_interface 'N/A' bridge 'N/A'
> Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
> Reading configuration file '/etc/wpa_supplicant.conf'
> ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=root'
> Line: 2 - start of a new network block
> ssid - hexdump_ascii(len=6):
> 41 50 54 45 4b 41 APTEKA
> scan_ssid=1 (0x1)
> key_mgmt: 0x2
> PSK (ASCII passphrase) - hexdump_ascii(len=16): [REMOVED]
> PSK (from passphrase) - hexdump(len=32): [REMOVED]
> Priority group 0
> id=0 ssid='APTEKA'
> Initializing interface (2) 'wlan0_rename'
> Interface wlan0_rename set UP - waiting a second for the driver to complete
> initialization
> SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
> capabilities: key_mgmt 0xf enc 0xf
> WEXT: Operstate: linkmode=1, operstate=5
> Own MAC address: 00:1b:77:bc:bb:ec
> wpa_driver_wext_set_wpa
> wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
> wpa_driver_wext_set_countermeasures
> wpa_driver_wext_set_drop_unencrypted
> RSN: flushing PMKID list in the driver
> Setting scan request: 0 sec 100000 usec
> EAPOL: SUPP_PAE entering state DISCONNECTED
> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> EAPOL: SUPP_BE entering state INITIALIZE
> EAP: EAP entering state DISABLED
> ctrl_interface_group=0 (from group name 'root')
> Added interface wlan0_rename
> Ignore event for foreign ifindex 7
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0_rename' added
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b06 len=12
> State: DISCONNECTED -> SCANNING
> Starting AP scan (specific SSID)
> Scan SSID - hexdump_ascii(len=6):
> 41 50 54 45 4b 41 APTEKA Trying
> to get current scan results first without requesting a new scan to speed up
> initial association
> Received 0 bytes of scan results (0 BSSes)
> CTRL-EVENT-SCAN-RESULTS
> Selecting BSS from priority group 0
> Try to find WPA-enabled AP
> Try to find non-WPA AP
> No suitable AP found.
> Setting scan request: 0 sec 0 usec
> Starting AP scan (broadcast SSID)
> Scan requested (ret=0) - scan timeout 5 seconds
> EAPOL: disable timer tick
> RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
> Wireless event: cmd=0x8b19 len=16
> Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=11)
> Invalid freq in scan results (BSSID=00:00:01:00:00:1d m=0 e=2462)
What system kernel are you using. This looks something we've already solved...
Tomas
On Fri, 2008-06-13 at 16:00 +0200, Maciek Kaliszewski wrote:
> debian:/home/u# dpkg -l |grep wpa
> ii wpasupplicant 0.6.3-1
> Client support for WPA and WPA2 (IEEE 802.11
>=20
> It is standard debian/lenny package .
> Should I compile wpa_supplicant from source ?
>=20
> On other computer debian/lenny also ,and p54pci.ko driver everything
> works ok.
=EF=BB=BFMake sure you don't have any obsolete version of wpa_supplican=
t in
PATH.
Try removing "scan_ssid=3D1". Also try ESSID scanning in iwlist:
iwlist wlan0_rename scanning essid APTEKA
If the recompiled wpa_supplicant fails, try asking in
[email protected] (the list for wpa_supplicant and hostapd)
--=20
Regards,
Pavel Roskin
On Fri, Jun 13, 2008 at 4:23 PM, John W. Linville
<[email protected]> wrote:
> On Fri, Jun 13, 2008 at 02:18:18PM +0200, Maciek Kaliszewski wrote:
>> I cannot connect to my WIFI/WPA network using iwl3945 driver.
>
> Any chance that adding a line like this in /etc/modprobe.conf is
> helpful?
>
> options iwl3945 disable_hw_scan=1
>
> Worth a shot... :-)
>
I would suggest to upgrade supplicant as iwlist is apparently working
> John
> --
> John W. Linville
> [email protected]
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Pavel Roskin wrote:
> On Fri, 2008-06-13 at 16:00 +0200, Maciek Kaliszewski wrote:
>
> =20
>> debian:/home/u# dpkg -l |grep wpa
>> ii wpasupplicant 0.6.3-1
>> Client support for WPA and WPA2 (IEEE 802.11
>>
>> It is standard debian/lenny package .
>> Should I compile wpa_supplicant from source ?
>>
>> On other computer debian/lenny also ,and p54pci.ko driver everything
>> works ok.
>> =20
>
> =EF=BB=BFMake sure you don't have any obsolete version of wpa_supplic=
ant in
> PATH.
> =20
I've checked and 0.6.3 is latest development version of wpa_supplicant.
> Try removing "scan_ssid=3D1". Also try ESSID scanning in iwlist:
> iwlist wlan0_rename scanning essid APTEKA
> =20
Removing scan_ssid doesn't help .
iwlist wlan0_rename scanning essid APTEKA
gives the same results like
iwlist wlan0_rename scanning
and
iwlist wlan0_rename scanning essid AAAA
so driver ignores essid parameter
> If the recompiled wpa_supplicant fails, try asking in
> [email protected] (the list for wpa_supplicant and hostapd)
>
> =20
It looks like driver issue (driver is returning bogus data)
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:00:01:00:00:1d ssid=3D'' wpa_ie_len=3D0 rsn_ie_len=3D0 caps=3D0x1=
0
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:00:01:00:00:1d ssid=3D'' wpa_ie_len=3D0 rsn_ie_len=3D0 caps=3D0x1=
0
skip - SSID mismatch
No suitable AP found
there is no AP with BSSID 00:00:01:00:00:1d and hidden SSID in vicinity=
=20
=2E There is only one (my) AP in the range .
Moreover p54pci.ko driver (from the same family ) works just fine=20
with this version of wpa_supplicant .
Command line and config file I run wpa_supplicant with is the same.
Regards
Maciek Kaliszewski
--
----------------------------------------------------------------------
Tania telefonia internetowa!
Sprawdz >>> http://link.interia.pl/f1e2e
On Fri, 2008-06-13 at 22:22 +0200, Maciek Kaliszewski wrote:
> I've checked and 0.6.3 is latest development version of wpa_supplicant.
> > Try removing "scan_ssid=1". Also try ESSID scanning in iwlist:
> > iwlist wlan0_rename scanning essid APTEKA
> >
> Removing scan_ssid doesn't help .
>
> iwlist wlan0_rename scanning essid APTEKA
>
> gives the same results like
>
> iwlist wlan0_rename scanning
> and
> iwlist wlan0_rename scanning essid AAAA
> so driver ignores essid parameter
Well, if iwlist doesn't confuse the driver by "essid", neither should
wpa_supplicant.
> It looks like driver issue (driver is returning bogus data)
But why does iwlist display the same data correctly? If iwlist can
parse it, wpa_supplicant should be able to parse it as well.
Google search for "Invalid freq in scan results" finds another such case
back in year 2004:
http://lists.shmoo.com/pipermail/hostap/2004-March/thread.html#6134
> there is no AP with BSSID 00:00:01:00:00:1d and hidden SSID in vicinity
> . There is only one (my) AP in the range .
Of course. It looks like the initial "00:00:01:00" is bogus and the
final "00:1d" is the beginning of the correct BSSID.
> Moreover p54pci.ko driver (from the same family ) works just fine
> with this version of wpa_supplicant .
> Command line and config file I run wpa_supplicant with is the same.
It may be an alignment issue. Different drivers may include different
data, in different order.
I suggest that you debug wpa_supplicant, specifically
wpa_driver_wext_get_scan_results() in src/drivers/driver_wext.c. Try
printing iwe->cmd and iwe->len before the switch. And please move it to
the hostap list. If there is anything definitely wrong with the driver,
then please let us know.
--
Regards,
Pavel Roskin
> > You are right . It may be wpa_supplicant issue . (I'm moving to hostap list
> > as soon as I get subscribed )
> > Kernel is amd64 and wpa_supplicant is i386 binary.
>
> Isn't this the known issue with ioctl compat code when using 64-bit
> kernel with 32-bit user space?
Yes.
> wireless-tools has some workaround code
> for figuring out what kernel is trying to say in WEXT data, but
> wpa_supplicant does not have such workaround since I do not believe it
> belongs to every user space program that is using WEXT.
I think only Jean disagrees.
> If I've understood correctly, Dave Miller is working on cleaning up the
> compat WEXT code (see "Proper compat WEXT support" thread from June 3rd
> for the patch series). I would hope that that fixes issues with
> 64/32-bit systems without require all user space programs to be modified
> to be aware of the bogus data from the kernel. As a temporary
> workaround, it might help to build 64-bit wpa_supplicant for that
> kernel.
Yeah, it should be in there. Building a 64-bit wpa supplicant is quite
hard unless you have all 64-bit libs already, so maybe it's easier to
apply Dave's patches.
johannes
Sorry I've sent it off-list. resent
Tomas Winkler wrote:
> On Fri, Jun 13, 2008 at 4:23 PM, John W. Linville
> <[email protected]> wrote:
>
>> On Fri, Jun 13, 2008 at 02:18:18PM +0200, Maciek Kaliszewski wrote:
>>
>>> I cannot connect to my WIFI/WPA network using iwl3945 driver.
>>>
>> Any chance that adding a line like this in /etc/modprobe.conf is
>> helpful?
>>
>> options iwl3945 disable_hw_scan=1
>>
>> Worth a shot... :-)
>>
>>
> I would suggest to upgrade supplicant as iwlist is apparently working
>
debian:/home/u# rmmod iwl3945.ko
debian:/home/u# insmod
/lib/modules/2.6.24.2/updates/drivers/net/wireless/iwlwifi/iwl3945.ko
disable_hw_scan=1
The same results with wpa_supplicant.
debian:/home/u# dpkg -l |grep wpa
ii wpasupplicant 0.6.3-1
Client support for WPA and WPA2 (IEEE 802.11
It is standard debian/lenny package .
Should I compile wpa_supplicant from source ?
On other computer debian/lenny also ,and p54pci.ko driver everything
works ok.
Regards
Maciek Kaliszewski
----------------------------------------------------------------------
Mieszkasz w USA? Zobacz portal dla Polonii!
kliknij >>> http://link.interia.pl/f1e36
Pavel Roskin wrote:
> I suggest that you debug wpa_supplicant, specifically
> wpa_driver_wext_get_scan_results() in src/drivers/driver_wext.c. Try
> printing iwe->cmd and iwe->len before the switch. And please move it to
> the hostap list. If there is anything definitely wrong with the driver,
> then please let us know.
>
>
You are right . It may be wpa_supplicant issue . (I'm moving to hostap
list as soon as I get subscribed )
Kernel is amd64 and wpa_supplicant is i386 binary.
Regards
Maciek Kaliszewski
----------------------------------------------------------------------
Podbij Dziki Zachod!Gra strategiczna online
Sprawdz >>> http://link.interia.pl/f1dff