[solved] netcfg mistakes wep for wpa

One · 2011-07-05 08:36:45

Hello there,

I'm having some issues with netcfg.

At home I can either access the internet through a wired ethernet connection (homee profile), or through the wireless (homew profile). I thus created two profiles for netcfg:

# homee
CONNECTION='ethernet'
DESCRIPTION='DHCP Ethernet connection at home'
INTERFACE='eth0'
IP='dhcp'

#homew
CONNECTION='wireless'
DESCRIPTION='WEP wireless connection at home'
INTERFACE='wlan0'
SECURITY='wep'
ESSID='dlink900'
KEY='####'
IP='dhcp'
# Uncomment this if your ssid is hidden
HIDDEN=yes

When I try to turn on the wireless profile, I get

# netcfg homew
:: homew up                                               [BUSY]
 > WPA Authentication/Association Failed                  [FAIL]

which suggests that netcfg is doing something wrong.

In rc.conf my networking section consists of the following:

interface=eth0
address=
netmask=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This requires the netcfg package
#
NETWORKS=(homee)

In addition, is there a way to tell netcfg to try homee first, and if it does not work to try homew?

Thanks

Last edited by One (2011-07-05 13:47:22)

dobedo · 2011-07-05 10:05:12

For the wireless profile, not sure it's really a WPA problem. Have you tried this: https://wiki.archlinux.org/index.php/Ne … ion_failed

One · 2011-07-05 10:31:36

Thank you for your reply dobedo.

I have set the TIMEOUT to 60, as suggested, and tried to set the ESSID with the PRE_UP directive. No effect.

With my eeePC, running Debian, I am able to connect with manual configuration. I wonder now if the problem is still with netcfg or with the driver, but I am sure that the correct driver is loaded.

Gusar · 2011-07-05 10:34:15

That's a generic error message, and misleading in this case, has nothing to do with wpa vs wep.

Did you write the key in hex format or as a regular string? If string, you need to prefix it with a s:

KEY="s:blahblah"

The alternative being hex:

KEY="626c6168626c6168"

Also, slightly off-topic but kinda still relevant: Why are you using wep in the first place? And why a hidden ssid? You know it's not really hidden, right? All it does is cause problems (maybe even the exact one you have currently), while not making you any safer.

One · 2011-07-05 13:01:28

Thank you, Gusar.

My key is hex and should be fine.

I'm at my parent's place and they are happy with WEP and the hidden ESSID. Maybe I'll give it a try with a clear ESSID.

Thanks

One · 2011-07-05 13:46:25

Essid should be clear but it still shows up blank.

I specified the channel as well as the essid in PRE_UP and it now works.

CONNECTION='wireless'
DESCRIPTION='WEP wireless connection at home'
INTERFACE='wlan0'
SECURITY='wep'
ESSID='dlink900'
KEY='####'
IP='dhcp'
# Uncomment this if your ssid is hidden
HIDDEN=yes
PRE_UP='iwconfig $INTERFACE essid $ESSID channel 10'

Last edited by One (2011-07-05 13:46:47)

Arch Linux

#1 2011-07-05 08:36:45

[solved] netcfg mistakes wep for wpa

#2 2011-07-05 10:05:12

Re: [solved] netcfg mistakes wep for wpa

#3 2011-07-05 10:31:36

Re: [solved] netcfg mistakes wep for wpa

#4 2011-07-05 10:34:15

Re: [solved] netcfg mistakes wep for wpa

#5 2011-07-05 13:01:28

Re: [solved] netcfg mistakes wep for wpa

#6 2011-07-05 13:46:25

Re: [solved] netcfg mistakes wep for wpa

Board footer