Re: wpa_supplicant with NDIS-wrapped wireless card and WPA-PSK reboots 6.1-pre



Carlos Amengual <listas@xxxxxxxxxxxxxxxx> wrote:

My system is a 6.1-PRERELEASE as of yesterday afternoon, but the same
happened with a RELENG_6 as of a month ago.

I set up a D-Link AirPlus DWL-520+ wireless PCI adapter in an old
server, and NDISwrapped it (got an AIRPLUS_SYS.ko).

When running wpa_supplicant -dd -indis0 -Dndis
-c/etc/wpa_supplicant.conf, the system reboots after printing:

--------------------------------------------------------
Initializing interface 'ndis0' conf '/etc/wpa_supplicant.conf' driver
'ndis' Configuration file '/etc/wpa_supplicant.conf' ->
'/etc/wpa_supplicant.conf' Reading configuration file
'/etc/wpa_supplicant.conf' ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0 (from group name 'wheel')
Line: 6 - start of a new network block
ssid - hexdump_ascii(len=11):
47 4e 43 57 49 52 45 4c 45 53 53 GNCWIRELESS
scan_ssid=1 (0x1)
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=26): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='GNCWIRELESS'
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: 1 adapter names found
NDIS: 1 adapter descriptions found
NDIS: 0 - ndis0 - ndis0
NDIS: Adapter description prefix 'ndis0'
ndis_get_oid: oid=0xd010122 len (512) failed
NDIS: verifying driver WPA capability
NDIS: WPA key management supported
NDIS: WPA-PSK key management supported
ndis_set_oid: oid=0xd01011b len (4) failed
NDIS: Failed to set OID_802_11_ENCRYPTION_STATUS (6)
NDIS: TKIP encryption supported
NDIS: driver supports WPA
NDIS: driver capabilities: key_mgmt 0x5 enc 0x4 auth 0x3
Own MAC address: **:**:**:**:**:**
wpa_driver_ndis_set_wpa: enabled=1
ndis_get_oid: oid=0xd010101 len (6) failed

My /etc/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
#
# home network; allow all valid ciphers
network={
ssid="GNCWIRELESS"
scan_ssid=1
key_mgmt=WPA-PSK
psk="**********************"
}

Does it make a difference if you additionally put the
bssid in /etc/wpa_supplicant.conf?

Since I upgraded from RELENG_5 to RELENG_6
I have to use both the ssid and the bssid
to get ndis0 to associate.

I only use wep encryption and don't know if a failed
attempt to associate with wpa_supplicant can cause
a reboot, but it's worth a try.

You should also check if you can associate to
the (unencrypted) network with ifconfig by hand.

Fabian
--
http://www.fabiankeil.de/

Attachment: signature.asc
Description: PGP signature



Relevant Pages

  • Re: selectively bind a NDIS IM
    ... If is is a specific adapter identified by hardware ID, the you can write a NDIS "Notify Object" that is run at install time. ... A Notify Object can restrict bindings to a specific VID/PID. ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS-cable status
    ... for the adapter shows a "red X" and Network Connections shows "Network Cable ... my driver will redirect any traffic to the other adapter transparent to the ... > the NIC directly using a mechanism that bypasses the NDIS IM filter. ... >> but still the status of network connection becomes cable unpulgeed. ...
    (microsoft.public.development.device.drivers)
  • Re: How to change the IP address under the wince?
    ... you should be able to change the registry and then tell NDIS to rebind ... the adapter to be disconnected, ... > For restart you have two options. ...
    (microsoft.public.windowsce.app.development)
  • Re: put nic into promisquous mode
    ... Be aware that even if your adapter support promiscuous mode and set only if ... you have hub connected lan you'll receive all other host packets, ... >> Can anyone tell me how to configure a NIC or its NDIS ... > adapters are an example of an adapter that does not support promiscuous ...
    (microsoft.public.development.device.drivers)
  • Re: adapter questions
    ... Speaking for network (NDIS) adapters, ... the registry key that opens via INetCfgComponent::OpenParamKey. ... >Is it possible through NDIS or any other way to know if an adapter in my ...
    (microsoft.public.development.device.drivers)

Quantcast