Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Apr 2006 21:10:09 -0700
From:      Sam Leffler <sam@errno.com>
To:        Isaac Waldron <isaac.waldron@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: wpa_supplicant and wi
Message-ID:  <444709A1.7080800@errno.com>
In-Reply-To: <4446F4BF.90405@errno.com>
References:  <9c16502b0604191503u7891e5d6u17eaa3f5dc754c1e@mail.gmail.com>	<9c16502b0604191512ldeccd00r7e58dbf1ef120c43@mail.gmail.com> <4446F4BF.90405@errno.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Sam Leffler wrote:
> Isaac Waldron wrote:
>> I should add that I'm running RELENG_6 updated and compiled on 4/19/2006.
>>
>> On 4/19/06, Isaac Waldron <isaac.waldron@gmail.com> wrote:
>>> I am using a Netgear MA401 with the wi driver, and am having trouble
>>> using wpa_supplicant to set static WEP keys.  I have the wlan_wep.ko
>>> module loaded with wlan and wi built into the kernel.  My
>>> wpa_supplicant.conf looks like this:
>>>
>>> ctrl_interface=/var/run/wpa_supplicant
>>> ctrl_interface_group=wheel
>>>
>>> network={
>>>         ssid="INTERNERD"
>>>         scan_ssid=1
>>>         priority=1
>>>         key_mgmt=NONE
>>>         wep_key0=75745E266D4247372840217E73
>>>         wep_tx_keyidx=0
>>> }
>>>
>>> and wpa_supplicant -i wi0 -c /etc/wpa_supplicant.conf -d -d returns
>>> the following:
>>>
>>> Initializing interface 'wi0' conf '/etc/wpa_supplicant.conf' driver
>>> 'default' ctrl_interface 'N/A'
>>> 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: 4 - start of a new network block
>>> ssid - hexdump_ascii(len=9):
>>>      49 4e 54 45 52 4e 45 52 44                        INTERNERD
>>> scan_ssid=1 (0x1)
>>> priority=1 (0x1)
>>> key_mgmt: 0x4
>>> wep_key0 - hexdump(len=13): 75 74 5e 26 6d 42 47 37 28 40 21 7e 73
>>> wep_tx_keyidx=0 (0x0)
>>> Priority group 1
>>>    id=0 ssid='INTERNERD'
>>> Initializing interface (2) 'wi0'
>>> 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:09:5b:29:81:67
>>> 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 wi0
>>> State: DISCONNECTED -> SCANNING
>>> Starting AP scan (specific SSID)
>>> Scan SSID - hexdump_ascii(len=9):
>>>      49 4e 54 45 52 4e 45 52 44                        INTERNERD
>>> State: SCANNING -> ASSOCIATED
>>> Associated to a new BSS: BSSID=00:14:bf:00:2e:d4
>>> No keys have been configured - skip key clearing
>>> Network configuration found for the current AP
>>> WPA: clearing AP WPA IE
>>> WPA: clearing AP RSN IE
>>> WPA: clearing own WPA/RSN IE
>>> EAPOL: External notification - portControl=ForceAuthorized
>>> Associated with 00:14:bf:00:2e:d4
>>> WPA: Association event - clear replay counter
>>> EAPOL: External notification - portEnabled=0
>>> EAPOL: External notification - portValid=0
>>> EAPOL: External notification - portEnabled=1
>>> EAPOL: SUPP_PAE entering state S_FORCE_AUTH
>>> EAPOL: SUPP_BE entering state IDLE
>>> Cancelling authentication timeout
>>> State: ASSOCIATED -> COMPLETED
>>>
>>> No keys are set on the wi0 interface apparently, as ifconfig reports
>>> deftxkey UNDEF and no  configured keys.  In other outputs from
>>> wpa_supplicant that I've seen, there are lines beginning with
>>> wpa_driver_bsd_key_set that appear to be key setting.
>>>
>>> Does anyone have this working with a MA401 that could help me out?
> 
> Should work; I'll check on it.

Sorry I forgot how poorly wi works; you'll need to stick to command line 
tools until someone decides they want to give it some TLC.

	Sam



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444709A1.7080800>