#854: no ssid found scanning for access point when trying to connect
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version:
Keywords: | Patch_attached: 0
--------------------------------------+-------------------------------------
I have posted questions to the user mailing list and been on the irc
channel to no avail. I am running Debian 2.6.17 kernel and have downloaded
the latest version 0.9.2 and still get the same errors. It is not really
an error but a failure to recognize the correct SSID of my AP. My AP is
functioning properly as my wife's apple ibook connects using WPA/AES.
Following is the documentation of the steps I took. The odd thing is that
a manual scan for the AP shows the correct BSSID and SSID of the AP but
when I try to bring up the interface using either the wpa_supplicant tool
or the boot time configuration provided by Debian it fails to get the
correct SSID from the AP, hence it will not connect. My AP is broadcasting
its SSID as that is one of the first things I checked for.
While I was in the chat room someone with the name p0g0 suggested that the
driver was mistakenly using WPA2 instead of WPA. We went over the
configuration and in fact I am configured properly for WPA, not WPA2.
I am using a Dlink WDA-1320 wireless PCI card, trying to connect to a
Dlink WBR-1310 AP. The purchase of the card was motivated by the
AP since I figured that there would be fewer compatibility issues.
I did notice that the WDA-1320 is not listed on your website as
supported/working but I did see it was supported on the linux-wireless
website.
Here is the diary of my steps to try to connect.
I have set up the router properly and can connect using WPA (WPA-PSK/AES
cipher)
with my wife's Ibook, so I know it is working properly.
I am running Debian Sarge 2.6.17 kernel.
Here are the messages from inserting the ath_pci module:
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (0.9.2)
ath_rate_sample: 1.2 (0.9.2)
ath_pci: 0.9.4.5 (0.9.2)
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 23
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 7.8 phy 4.5 radio 5.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0xfebe0000, irq=23
Nothing here, pretty much as expected.
I have followed several HOW-TOs on your site to no avail. First I tried
the boot method as described in the disto specific section of your site.
I added the followin lines to the interfaces file:
iface ath0 inet dhcp
wpa-driver wext
wpa-ssid olympus
wpa-key
ef90a1414ae9569c7dd16b9ecc46997c7fdaadd7185c11b1cf2aaaa72e7c4dc4
I intentionally left out the auto option so I could bring it up manually.
I also tried 3 different values for the wpa-key. First I tried the value
above.
It is the value generated by the wpa_passphrase utility. The second is the
value I passed in to the wpa_passphrase utility. The third was the passed
in
value surrounded by quotes to eliminate the possibility of
misinterpretation
due to the special characters.
All three resulted in the following output at runtime:
[EMAIL PROTECTED]:~# ifup ath0
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
wifi0: unknown hardware address type 801
sit0: unknown hardware address type 776
Listening on LPF/ath0/00:15:e9:4c:2b:d4
Sending on LPF/ath0/00:15:e9:4c:2b:d4
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database.
Exiting.
Failed to bring up ath0.
Obviously something is wrong. I then followed the howto for wap which led
me to the following actions:
I followed the newbie howto. The first part was unnecessary as it was
already
installed. I then inserted the wlan_scan_sta module:
modprobe wlan_scan_sta
Brought up the interface with a fixed IP:
ifconfig ath0 192.168.2.10 (this address is on the same class C subnet the
AP is configured for and is just below the DHCP address range it would
have given out if it had worked)
which resulted in the following:
[EMAIL PROTECTED]:/etc/network# ifconfig
ath0 Link encap:Ethernet HWaddr 00:15:E9:4C:2B:D4
inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::215:e9ff:fe4c:2bd4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 00:15:F2:6F:AD:F9
inet addr:192.168.1.252 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:f2ff:fe6f:adf9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1569 errors:0 dropped:0 overruns:0 frame:0
TX packets:264 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:296309 (289.3 KiB) TX bytes:28442 (27.7 KiB)
Interrupt:16 Base address:0xe400
eth1 Link encap:Ethernet HWaddr 00:50:BA:37:D4:CC
inet addr:192.168.254.1 Bcast:192.168.254.255
Mask:255.255.255.0
inet6 addr: fe80::250:baff:fe37:d4cc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1853 (1.8 KiB) TX bytes:1853 (1.8 KiB)
wifi0 Link encap:UNSPEC HWaddr 00-15-E9-4C-2B-D4-00-00-00-00-00-00-
00-00-00
-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2274 errors:0 dropped:0 overruns:0 frame:1762
TX packets:4910 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:230918 (225.5 KiB) TX bytes:225860 (220.5 KiB)
Interrupt:23 Memory:f90e0000-f90f0000
Then I scanned for my AP:
[EMAIL PROTECTED]:/etc/network# wlanconfig ath0 list scan
SSID BSSID CHAN RATE S:N INT CAPS
olympus 00:15:e9:d1:55:8a 11 54M 22:0 100 EPSs WPA
This information is all correct. The SSID and BSSID are exactly what I
expected
to see.
I then attempted to invoke wpa_supplicant with the following file
(generated
earlier prior to adding the stanza to the interfaces file):
network={
key_mgmt=WPA-PSK
proto=WPA
ssid="olympus"
#psk="HEX0&w39DO0(nds#4wa24Tb65j9eF)2tss"
psk=ef90a1414ae9569c7dd16b9ecc46997c7fdaadd7185c11b1cf2aaaa72e7c4dc4
}
This resulted in the following output:
[EMAIL PROTECTED]:/etc# wpa_supplicant -dd -Dmadwifi -iath0
-c/etc/wpa_supplicant.conf
Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver
'madwifi'
Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
key_mgmt: 0x2
proto: 0x1
ssid - hexdump_ascii(len=7):
6f 6c 79 6d 70 75 73 olympus
PSK - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='olympus'
Initializing interface (2) 'ath0'
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
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Own MAC address: 00:15:e9:4c:2b:d4
wpa_driver_madwifi_set_wpa: enabled=1
wpa_driver_madwifi_del_key: keyidx=0
wpa_driver_madwifi_del_key: keyidx=1
wpa_driver_madwifi_del_key: keyidx=2
wpa_driver_madwifi_del_key: keyidx=3
wpa_driver_madwifi_set_countermeasures: enabled=0
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK, IFLA_IFNAME: Interface 'wifi0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
RTM_NEWLINK, IFLA_IFNAME: Interface 'ath0' added
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=8
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Wireless event: cmd=0x8b19 len=8
IWEVGENIE overflow
Received 226 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:15:e9:d1:55:8a ssid='' wpa_ie_len=0 rsn_ie_len=0
skip - no WPA/RSN IE
No suitable AP found.
Setting scan request: 5 sec 0 usec
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
I notice a few interesting things here.
First the following:
Line: 1 - start of a new network block
key_mgmt: 0x2
proto: 0x1
ssid - hexdump_ascii(len=7):
6f 6c 79 6d 70 75 73 olympus
PSK - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='olympus'
This block indicates it is looking for the correct SSID, I do not know if
the
key_mgmt and proto values are correct but I must assume they are.
Next the following:
Starting AP scan (broadcast SSID)
Wireless event: cmd=0x8b1a len=8
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
EAPOL: Port Timers tick - authWhile=0 heldWhile=0 startWhen=0 idleWhile=0
Wireless event: cmd=0x8b19 len=8
IWEVGENIE overflow
Received 226 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 0
0: 00:15:e9:d1:55:8a ssid='' wpa_ie_len=0 rsn_ie_len=0
skip - no WPA/RSN IE
No suitable AP found.
I notice it is trying to do a scan for the AP but I notice it gets the
BSSID
but not the SSID. I thought this may be the problem so I went back and
changed
the interfaces file to reflect the BSSID instead of the SSID:
iface ath0 inet dhcp
wpa-driver wext
wpa-bssid 00:15:e9:d1:55:8a
wpa-key "HEX0&w39DO0(nds#4wa24Tb65j9eF)2tss"
This yeilded the same results as using the SSID of olympus. I then changed
the wpa_supplicant.conf file to reflect the BSSID:
network={
key_mgmt=WPA-PSK
proto=WPA
bssid=00:15:e9:d1:55:8a
#psk="HEX0&w39DO0(nds#4wa24Tb65j9eF)2tss"
psk=ef90a1414ae9569c7dd16b9ecc46997c7fdaadd7185c11b1cf2aaaa72e7c4dc4
}
This again yeilded the same results.
--
Ticket URL: <http://madwifi.org/ticket/854>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
