NDIS und wpa_supplicant

fsck

fsck

Well-Known Member
n'Abend zusammen.

Ich habe von einem Kollegen recht günstig eine Asus WL-138gE WLAN-Karte mit Broadcom-Chipsatz bekommen. Der NDIS-Treiber liess sich relativ problemlos kompilieren. Allerdings weigert sich das Ding vehement, mit dem AP zu kommunizieren.

Hier mal meine /etc/wpa_supplicant.conf (habe schon an allen möglichen Parametern gedreht, aber vielleicht ist ja doch was dabei, was so nicht OK ist...)
Code: 
eapol_version=2
ap_scan=2

network={
	ssid="Nicht-die-Frauenklinik"
	scan_ssid=0
	priority=5
	proto=WPA RSN
	key_mgmt=WPA-PSK
	pairwise=CCMP TKIP 
	group=CCMP TKIP 
	psk="***********"
}

Der Output von wpa_supplicant mit der "-D ndis"-Option:
Code: 
Initializing interface 'ndis0' conf '/etc/wpa_supplicant.conf' driver 'ndis' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
eapol_version=2
ap_scan=2
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=22):
     4e 69 63 68 74 2d 64 69 65 2d 46 72 61 75 65 6e   Nicht-die-Frauen
     6b 6c 69 6e 69 6b                                 klinik          
BSSID - hexdump(len=6): 00 12 bf 7c 44 1c
scan_ssid=0 (0x0)
priority=5 (0x5)
proto: 0x3
key_mgmt: 0x2
pairwise: 0x18
group: 0x18
PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
   id=0 ssid='Nicht-die-Frauenklinik'
Initializing interface (2) 'ndis0'
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
NDIS: Packet.dll version: FreeBSD WinPcap compatibility shim v1.0
NDIS: 1 adapter names found
NDIS: 1 adapter descriptions found
NDIS: 0 - ndis0 - ndis0
NDIS: Adapter description prefix 'ndis0'
OID_802_11_CAPABILITY - hexdump(len=128): (der Übersicht halber weggelassen)
NDIS: Driver supports OID_802_11_CAPABILITY - NoOfPMKIDs 16 NoOfAuthEncrPairs 14
NDIS: 0 - auth 0 encr 1
NDIS: 1 - auth 0 encr 0
NDIS: 2 - auth 1 encr 1
NDIS: 3 - auth 1 encr 0
NDIS: 4 - auth 3 encr 4
NDIS: 5 - auth 4 encr 4
NDIS: 6 - auth 5 encr 4
NDIS: 7 - auth 6 encr 4
NDIS: 8 - auth 7 encr 4
NDIS: 9 - auth 3 encr 6
NDIS: 10 - auth 4 encr 6
NDIS: 11 - auth 5 encr 6
NDIS: 12 - auth 6 encr 6
NDIS: 13 - auth 7 encr 6
NDIS: driver capabilities: key_mgmt 0x1f enc 0xf auth 0x3
NDIS: OID_802_11_PMKID (flush) - hexdump(len=8): 08 00 00 00 00 00 00 00
Own MAC address: 00:15:f2:7a:7e:84
wpa_driver_ndis_set_wpa: enabled=1
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Setting scan request: 0 sec 100000 usec
Added interface ndis0
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Nicht-die-Frauenklinik'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 24 pairwise 24 key_mgmt 2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
ndis_set_oid: oid=0xd010119 len (4) failed
NDIS: Failed to set OID_802_11_PRIVACY_FILTER (1)
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
....
....
ndis_get_oid: oid=0xd010101 len (6) failed
ndis_get_oid: oid=0xd010101 len (6) failed
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Nicht-die-Frauenklinik'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 24 pairwise 24 key_mgmt 2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
....
...


...und mit "-D bsd":
Code: 
Initializing interface 'ndis0' conf '/etc/wpa_supplicant.conf' driver 'bsd' ctrl_interface 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
eapol_version=2
ap_scan=2
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=22):
     4e 69 63 68 74 2d 64 69 65 2d 46 72 61 75 65 6e   Nicht-die-Frauen
     6b 6c 69 6e 69 6b                                 klinik          
BSSID - hexdump(len=6): 00 12 bf 7c 44 1c
scan_ssid=0 (0x0)
priority=5 (0x5)
proto: 0x3
key_mgmt: 0x2
pairwise: 0x18
group: 0x18
PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
   id=0 ssid='Nicht-die-Frauenklinik'
Initializing interface (2) 'ndis0'
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:f2:7a:7e:84
wpa_driver_bsd_set_wpa: enabled=1
wpa_driver_bsd_set_wpa_internal: wpa=3 privacy=1
wpa_driver_bsd_del_key: keyidx=0
wpa_driver_bsd_del_key: keyidx=1
wpa_driver_bsd_del_key: keyidx=2
wpa_driver_bsd_del_key: keyidx=3
wpa_driver_bsd_set_countermeasures: enabled=0
wpa_driver_bsd_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Added interface ndis0
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Nicht-die-Frauenklinik'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 24 pairwise 24 key_mgmt 2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
No keys have been configured - skip key clearing
wpa_driver_bsd_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
wpa_driver_bsd_associate: ssid 'Nicht-die-Frauenklinik' wpa ie len 22 pairwise 3 group 3 key mgmt 1
wpa_driver_bsd_associate: set PRIVACY 1
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATING -> DISCONNECTED
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Nicht-die-Frauenklinik'
Cancelling scan request
WPA: clearing own WPA/RSN IE
...
...


Hoffe, das geht irgendwie, ich bin mit meinem Latein am Ende... :(
 
Ich kann Entwarnung geben, ohne genau zu wissen, woran es gelegen hat.
Möglicherweise waren die Module nicht in der richtigen Reihenfolge geladen...:confused:

Ich tippe allerdings eher auf ein mechanisches Problem, ich hatte gestern auch unter Windows Pings, die lagen jenseits von gut und böse. Nach ein bisschen drehen an der Antenne ist unter beiden Betriebssystemen alles so, wie's sein soll. :)

...fast: Das DHCP scheint ein wenig lange zu dauern und hatte heute früh beim Hochfahren sogar einen Timeout... Ist aber nicht weiter tragisch.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Zurück
Oben