You mean you don't know the password for the network, just the hex string?
Anyway, how didn't I notice this earlier:
> Invalid SECURITY setting: WEP
The security setting must be in lowercase, so wep and not WEP.
changing from WEP to wep did it, thank you.
believe it or not the password is the hex string, i saw the router settings myself it is set to 128bit wep hex, there is no plain text password option as far as i know of beside wpa with the router my landlord has.
Anyway, how didn't I notice this earlier:
> Invalid SECURITY setting: WEP
The security setting must be in lowercase, so wep and not WEP.
]]>KEY="s:passwd"
CONNECTION="wireless"
DESCRIPTION=""
INTERFACE=eth1
HOSTNAME=z
IP="dhcp"
DHCP_TIMEOUT=10
ESSID="Andy_Network"
SECURITY="WEP"
KEY="6626811e486EABEE0867088A81"
SCAN="NO"
TIMEOUT=15
But that aside, if you need to connect to a WEP network, I don't think you should use wpa_supplicant. I just checked, and apparently wpa_supplicant can be configured to connect to WEP, but it needs to be configured to do so. Normally you'd just use iwconfig to connect to WEP networks.
I have no idea how these tools (iwconfig vs wpa_supplicant) are selected in netcfg though.
EDIT: for those who know netcfg, it'd probably be helpful if you posted the profile you created and are using.
]]>sudo NETCFG_DEBUG="yes" netcfg Andy_Network
DEBUG: Loading profile Andy_Network
DEBUG: Configuring interface eth1
:: Andy_Network up [ BUSY ] DEBUG: status reported to profile_up as:
DEBUG: Loading profile Andy_Network
DEBUG: Configuring interface eth1
DEBUG: wireless_up start_wpa eth1 /run/network/wpa.eth1/wpa.conf nl80211,wext
> Invalid SECURITY setting: WEP
DEBUG: wireless_up ifup
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant status
DEBUG: wpa_cli -i eth1 -p /run/wpa_supplicant terminate
> WPA Authentication/Association Failed
if I use NetworkManager ihave no problems connecting so i double checked that the setting are right.
im on a macbook pro with the proprietary broadcom-wl driver installed.
anyone have any idea whats wrong and how to fix it.