Hi Xianwen Chen,
> An open WEP network is a network that > does not require
> password or key.
I'm quite sure a Open-Key WEP connection is different from a Open Network
(unprotected), since a Open WEP, despite not requesting authentication (as
opposed to Shared-Key WEP), still holds a hexadecimal WEP key, which is
required for data encryption after connection. If your network is truly Open
WEP, then in my experience, wpa_supplicant needs that key in order to
successfully attach to the network. So , in addition to what Scole Mail said,
if you happened to find out you need a WEP key for real, you could make use of
a similar configuration in /etc/wpa_supplicant.conf:
network={
ssid="xxxxx"
key_mgmt=NONE
wep_key0=$hex_key #(10 characters)
wep_tx_keyidx=0
priority=x
}
For Shared-Key WEP, simply add :
auth_alg=SHARED
And then try connecting:
wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf
You can also avoid using wpa_supplicant at all:
ifconfig $interface ssid xxxxxx nwkey $wep_key
Best whishes
On 1 February 2018 22:34:48 CET, "Xianwen Chen (陈贤文)" <[email protected]>
wrote:
>Dear Dave,
>Thank you. An open WEP network is a network that does not require
>password or key.
>Sincerely,
>Xianwen
>
>On Thu, Feb 1, 2018 at 6:34 PM, David Young <[email protected]> wrote:
>> On Thu, Feb 01, 2018 at 11:25:21AM +0000, Chen, Xianwen (陈贤文) wrote:
>>> Dear NetBSD users,
>>>
>>> I am having trouble connecting NetBSD to an open WEP wireless
>network,
>>> called "ks-guest". Because my Android mobile phone is able to
>connect
>>> to "ks-guest", the network is functioning.
>>
>> What do you mean by an "open WEP" network? Seems like any WEP
>network
>> should have a key, but you're not configuring the interface with any
>> key.
>>
>> Dave
>>
>> --
>> David Young
>> [email protected] Urbana, IL (217) 721-9981
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
