WEP Key not working [Solved]

Issues Related to Networking (Wired and Wireless)

Moderator: Moderators

WEP Key not working [Solved]

Postby DrBenway » Tue Feb 28, 2012 4:06

Hi there, I'm brand new to Sabayon. I've just switched over from Mint.

My wireless connections are appearing in the network manager. But my WEP key isn't working. I've tried to configure it using network connections. When I log on it creates a separate connection and changes the key to a long number with a 3 before each letter which is converted into a number and a 6 before each number. For example if my key was ab12ab it creates another connection with 313261623132 as the key. I've run out of ideas. I've heard great things about sabayon and would love to be able to use it.

Any help is greatly appreciated.
Last edited by DrBenway on Fri Mar 09, 2012 1:55, edited 1 time in total.
DrBenway
Baby Hen
 
Posts: 8
Joined: Tue Feb 28, 2012 3:48

Re: WEP Key not working

Postby dunsurfin » Tue Feb 28, 2012 16:38

I'm afraid I can't help you with the WEP problem, so ignore this post if you wish, but I think you would do well to try WPA as WEP has been considered insecure since about 2003/4.
Self-righteousness is a loud din raised to drown
the voice of guilt within us - Eric Hoffer
User avatar
dunsurfin
Sagely Hen
 
Posts: 1270
Joined: Sun Jan 07, 2007 21:38
Location: Newcastle upon Tyne UK

Re: WEP Key not working

Postby Fitzcarraldo » Wed Feb 29, 2012 21:53

KDE? GNOME? Xfce? LXDE? Fluxbox? Cinnamon?

What have you got for your network connection settings?

If you're using KDE, here is what I have in the 'Edit Network Connection - KDE Control Module' window for a WEP network that I use sometimes.

'Connect automatically' unticked

'System connection' unticked

Wireless tab

SSID: <your network name>
Mode: Infrastructure
BSSID: __|__|__|__|__|__
Restrict To Interface: Any
Cloned MAC address: __|__|__|__|__|__
MTU: Automatic

Wireless Security tab

Security: WEP

Key type: Hex or Ascii Key (for 64 or 128 bit)

Key: <your key, which should be a mixture of letters and numbers>

WEP index: 1 (Default)

Authentication: Open System

IPv4 Address tab

Basic settings

Method: Automatic (DHCP)

All other fields blank

'IPv4 is required for this connection' ticked

IPv6 Address tab

Basic settings

Method: Disabled

All other fields blank

'IPv4 is required for this connection' unticked
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7340
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: WEP Key not working

Postby DrBenway » Thu Mar 01, 2012 6:09

I've since removed network manager and replaced wicd as default. It is now accepting my passkey but not finding the IP. When using a static IP, it fails on pinging the AP. I'm using a GNOME environment. The settings are similar to those that you've described. Security : WEP , Key: Passphrase, Index 1, Auth Open, and the rest set to auto. I've tried reading through my wicd log for clues but only came out of it with the drop-out at AP.

Still perplexed.
DrBenway
Baby Hen
 
Posts: 8
Joined: Tue Feb 28, 2012 3:48

Re: WEP Key not working

Postby Fitzcarraldo » Thu Mar 01, 2012 15:06

I don't use Wicd as it doesn't work at all on two of my machines and badly on another. NetworkManager, on the other hand, works well.

What is your wireless controller? Output of lspci command, please.

Any error messages in /var/log/messages?
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7340
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: WEP Key not working

Postby DrBenway » Thu Mar 01, 2012 16:15

Thanks for the reply,

As I was saying I've had less luck with NM

here's the result of lspci:

Code: Select all
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series]
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Cedar HDMI Audio [Radeon HD 5400/6300 Series]
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller
03:00.1 System peripheral: Ricoh Co Ltd Memory Stick Host Controller
03:00.4 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller
04:00.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Optima 88E8059 [PCIe Gigabit Ethernet Controller with AVB] (rev 11)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)


Here's the log without a static IP:

2012/03/01 23:05:08 :: Connecting to wireless network leticia
2012/03/01 23:05:08 :: iwconfig wlan0
2012/03/01 23:05:08 :: /sbin/dhcpcd -k wlan0
dhcpcd[28843]: dhcpcd not running
2012/03/01 23:05:08 :: ifconfig wlan0 0.0.0.0
2012/03/01 23:05:08 :: /sbin/ip route flush dev wlan0
2012/03/01 23:05:08 :: ifconfig wlan0 down
2012/03/01 23:05:08 :: ifconfig wlan0 up
2012/03/01 23:05:08 :: wpa_cli -i wlan0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2012/03/01 23:05:08 :: /sbin/dhcpcd -k eth0
dhcpcd[28849]: dhcpcd not running
2012/03/01 23:05:08 :: ifconfig eth0 0.0.0.0
2012/03/01 23:05:08 :: /sbin/ip route flush dev eth0
2012/03/01 23:05:08 :: ifconfig eth0 down
2012/03/01 23:05:08 :: ifconfig eth0 up
2012/03/01 23:05:08 :: wpa_cli -i eth0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2012/03/01 23:05:08 :: Putting interface down
2012/03/01 23:05:08 :: ifconfig wlan0 down
2012/03/01 23:05:09 :: Releasing DHCP leases...
2012/03/01 23:05:09 :: /sbin/dhcpcd -k wlan0
dhcpcd[28857]: dhcpcd not running
2012/03/01 23:05:09 :: Setting false IP...
2012/03/01 23:05:09 :: ifconfig wlan0 0.0.0.0
2012/03/01 23:05:09 :: Stopping wpa_supplicant
2012/03/01 23:05:09 :: wpa_cli -i wlan0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2012/03/01 23:05:09 :: Flushing the routing table...
2012/03/01 23:05:09 :: /sbin/ip route flush dev wlan0
2012/03/01 23:05:09 :: iwconfig wlan0 mode managed
2012/03/01 23:05:09 :: Putting interface up...
2012/03/01 23:05:09 :: ifconfig wlan0 up
2012/03/01 23:05:11 :: enctype is wep-passphrase
2012/03/01 23:05:11 :: Attempting to authenticate...
2012/03/01 23:05:11 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/001ee3ea9c26', '-D', 'wext']
2012/03/01 23:05:11 :: ['iwconfig', 'wlan0', 'essid', '--', 'leticia']
2012/03/01 23:05:11 :: iwconfig wlan0 channel 1
2012/03/01 23:05:11 :: iwconfig wlan0 ap 00:1E:E3:EA:9C:26
2012/03/01 23:05:11 :: WPA_CLI RESULT IS DISCONNECTED
2012/03/01 23:05:12 :: WPA_CLI RESULT IS DISCONNECTED
2012/03/01 23:05:13 :: WPA_CLI RESULT IS COMPLETED
2012/03/01 23:05:13 :: Running DHCP with hostname DrBenway
2012/03/01 23:05:13 :: /sbin/dhcpcd -h DrBenway --noipv4ll wlan0
2012/03/01 23:05:13 :: dhcpcd[28879]: version 5.2.12 starting
2012/03/01 23:05:13 ::
2012/03/01 23:05:13 :: dhcpcd[28879]: wlan0: broadcasting for a lease
2012/03/01 23:05:13 ::
2012/03/01 23:05:43 :: dhcpcd[28879]: timed out
2012/03/01 23:05:43 ::
2012/03/01 23:05:43 :: DHCP connection failed
2012/03/01 23:05:43 :: exiting connection thread
2012/03/01 23:05:43 :: Sending connection attempt result dhcp_failed
2012/03/01 23:05:43 :: ifconfig eth0
2012/03/01 23:05:43 :: ifconfig wlan0
2012/03/01 23:05:43 :: Forced disconnect on
2012/03/01 23:05:43 :: iwconfig wlan0
2012/03/01 23:05:43 :: /sbin/dhcpcd -k wlan0
dhcpcd[28946]: dhcpcd not running
2012/03/01 23:05:43 :: ifconfig wlan0 0.0.0.0
2012/03/01 23:05:43 :: /sbin/ip route flush dev wlan0
2012/03/01 23:05:43 :: ifconfig wlan0 down
2012/03/01 23:05:43 :: ifconfig wlan0 up
2012/03/01 23:05:43 :: wpa_cli -i wlan0 terminate
2012/03/01 23:05:43 :: /sbin/dhcpcd -k eth0
dhcpcd[28953]: dhcpcd not running
2012/03/01 23:05:43 :: ifconfig eth0 0.0.0.0
2012/03/01 23:05:43 :: /sbin/ip route flush dev eth0
2012/03/01 23:05:43 :: ifconfig eth0 down
2012/03/01 23:05:43 :: ifconfig eth0 up
2012/03/01 23:05:43 :: wpa_cli -i eth0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory


And here's the output with a static IP:

2012/03/01 23:08:22 :: Connecting to wireless network leticia
2012/03/01 23:08:22 :: iwconfig wlan0
2012/03/01 23:08:22 :: /sbin/dhcpcd -k wlan0
dhcpcd[29240]: dhcpcd not running
2012/03/01 23:08:22 :: ifconfig wlan0 0.0.0.0
2012/03/01 23:08:22 :: /sbin/ip route flush dev wlan0
2012/03/01 23:08:23 :: ifconfig wlan0 down
2012/03/01 23:08:23 :: ifconfig wlan0 up
2012/03/01 23:08:23 :: wpa_cli -i wlan0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2012/03/01 23:08:23 :: /sbin/dhcpcd -k eth0
dhcpcd[29246]: dhcpcd not running
2012/03/01 23:08:23 :: ifconfig eth0 0.0.0.0
2012/03/01 23:08:23 :: /sbin/ip route flush dev eth0
2012/03/01 23:08:23 :: ifconfig eth0 down
2012/03/01 23:08:23 :: ifconfig eth0 up
2012/03/01 23:08:23 :: wpa_cli -i eth0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2012/03/01 23:08:23 :: Putting interface down
2012/03/01 23:08:23 :: ifconfig wlan0 down
2012/03/01 23:08:23 :: Releasing DHCP leases...
2012/03/01 23:08:23 :: /sbin/dhcpcd -k wlan0
dhcpcd[29254]: dhcpcd not running
2012/03/01 23:08:23 :: Setting false IP...
2012/03/01 23:08:23 :: ifconfig wlan0 0.0.0.0
2012/03/01 23:08:23 :: Stopping wpa_supplicant
2012/03/01 23:08:23 :: wpa_cli -i wlan0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
2012/03/01 23:08:23 :: Flushing the routing table...
2012/03/01 23:08:23 :: /sbin/ip route flush dev wlan0
2012/03/01 23:08:23 :: iwconfig wlan0 mode managed
2012/03/01 23:08:23 :: Putting interface up...
2012/03/01 23:08:23 :: ifconfig wlan0 up
2012/03/01 23:08:25 :: enctype is wep-passphrase
2012/03/01 23:08:25 :: Attempting to authenticate...
2012/03/01 23:08:25 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/001ee3ea9c26', '-D', 'wext']
2012/03/01 23:08:25 :: ['iwconfig', 'wlan0', 'essid', '--', 'leticia']
2012/03/01 23:08:25 :: iwconfig wlan0 channel 1
2012/03/01 23:08:25 :: iwconfig wlan0 ap 00:1E:E3:EA:9C:26
2012/03/01 23:08:25 :: WPA_CLI RESULT IS DISCONNECTED
2012/03/01 23:08:26 :: WPA_CLI RESULT IS COMPLETED
2012/03/01 23:08:26 :: Setting static IP : 192.168.1.6
2012/03/01 23:08:26 :: ifconfig wlan0 192.168.1.6 netmask 255.255.255.0
2012/03/01 23:08:26 :: Setting default gateway : 192.168.1.1
2012/03/01 23:08:26 :: route add default gw 192.168.1.1 dev wlan0
2012/03/01 23:08:26 :: Verifying AP association...
2012/03/01 23:08:26 :: Attempt 1 of 10...
2012/03/01 23:08:26 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:30 :: Attempt 2 of 10...
2012/03/01 23:08:30 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:34 :: Attempt 3 of 10...
2012/03/01 23:08:34 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:38 :: Attempt 4 of 10...
2012/03/01 23:08:38 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:40 :: Attempt 5 of 10...
2012/03/01 23:08:40 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:44 :: Attempt 6 of 10...
2012/03/01 23:08:44 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:48 :: Attempt 7 of 10...
2012/03/01 23:08:48 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:52 :: Attempt 8 of 10...
2012/03/01 23:08:52 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:08:56 :: Attempt 9 of 10...
2012/03/01 23:08:56 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:09:00 :: Attempt 10 of 10...
2012/03/01 23:09:00 :: ping -q -w 3 -c 1 192.168.1.1
2012/03/01 23:09:04 :: Connection Failed: Failed to ping the access point!
2012/03/01 23:09:04 :: ifconfig wlan0 0.0.0.0
2012/03/01 23:09:04 :: /sbin/ip route flush dev wlan0
2012/03/01 23:09:04 :: wpa_cli -i wlan0 terminate
2012/03/01 23:09:04 :: exiting connection thread
2012/03/01 23:09:04 :: Sending connection attempt result association_failed
2012/03/01 23:09:04 :: ifconfig eth0
2012/03/01 23:09:04 :: ifconfig wlan0
2012/03/01 23:09:04 :: Forced disconnect on
2012/03/01 23:09:04 :: iwconfig wlan0
2012/03/01 23:09:04 :: /sbin/dhcpcd -k wlan0
dhcpcd[29339]: dhcpcd not running
2012/03/01 23:09:04 :: ifconfig wlan0 0.0.0.0
2012/03/01 23:09:04 :: /sbin/ip route flush dev wlan0
2012/03/01 23:09:04 :: ifconfig wlan0 down
2012/03/01 23:09:04 :: ifconfig wlan0 up
2012/03/01 23:09:04 :: wpa_cli -i wlan0 terminate
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
DrBenway
Baby Hen
 
Posts: 8
Joined: Tue Feb 28, 2012 3:48

Re: WEP Key not working

Postby Fitzcarraldo » Fri Mar 02, 2012 1:00

Hmm... not sure as you're using Wicd and dhcpcd as the DHCP client. I'm using NetworkManager with dhclient as the DHCP client:

Code: Select all
# eix -I networkmanager
[I] net-misc/networkmanager
     Available versions:  0.8-r1 0.8.4.0-r2 (~)0.9.0 (~)0.9.2.0 (~)0.9.2.0-r2 (~)0.9.2.0-r2[1] (~)0.9.2.0-r3 (~)0.9.2.0-r5 {avahi bluetooth connection-sharing dhclient (+)dhcpcd doc gnutls +introspection kernel_linux (+)nss +ppp resolvconf wimax}
     Installed versions:  0.9.2.0-r5(02:54:19 26/02/12)(avahi bluetooth dhclient introspection kernel_linux nss ppp -connection-sharing -dhcpcd -doc -gnutls -resolvconf -wimax)
     Homepage:            http://www.gnome.org/projects/NetworkManager/
     Description:         Network configuration and management in an easy way. Desktop environment independent.

[I] net-misc/networkmanager-vpnc
     Available versions:  (~)0.8.2!t (~)0.9.0!t (~)0.9.2.0 {gnome test}
     Installed versions:  0.9.2.0(17:13:45 07/01/12)(-gnome -test)
     Homepage:            http://www.gnome.org/projects/NetworkManager/
     Description:         NetworkManager VPNC plugin

[1] "sabayon-distro" /var/lib/layman/sabayon-distro

Found 2 matches.

Notice that I'm using a later version of NetworkManager than the version in the Entropy repository, and that my USE flags are different to those in the Sabayon Entropy package:

net-misc/networkmanager-0.9.2.0-r2
Network configuration and management in an easy way. Desktop environment independent.
binary → standard → sabayon-weekly → amd64 → 5 | revision: 0 | date: 2012-01-17 19:59:30.990000
Repository sabayon-weekly
Sub-repository sabayon-distro
License GPL-2
Required space 4.6MB
Category net-misc
Slot 0
Tag N/A
CHOST x86_64-pc-linux-gnu
CFLAGS -O2 -ftree-vectorize -march=x86-64 -pipe -floop-interchange -ftree-loop-distribution -floop-strip-mine -floop-block
CXXFLAGS -O2 -ftree-vectorize -march=x86-64 -pipe -floop-interchange -ftree-loop-distribution -floop-strip-mine -floop-block
Checksum 54511849ecc9bdb041401e62f4b2df94
SHA 256 2e29957aa74ddf934688624d8d57a1da41ef3b74f10cb90f53f52bf2a9bd214e
Package file packages/amd64/5/net-misc:networkmanager-0.9.2.0-r2~0.tbz2
Package size 1.2MB
USE flags introspection -dhclient -bluetooth userland_GNU resolvconf multilib kernel_linux -gnutls wimax elibc_glibc -doc ppp connection-sharing avahi nss dhcpcd amd64
Keywords ~amd64 ~arm ~ppc ~ppc64 ~x86
Injected False

This is what /var/log/messages should contain if you use NetworkManager and dhclient as the DHCP client, and you select a WEP network connection:

Code: Select all
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) starting connection 'FitzsHub-59EB'
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0/wireless): access point 'FitzsHub-59EB' has security, but secrets are required.
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Mar  1 23:23:56 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar  1 23:24:02 meshedgedx NetworkManager[6754]: get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Activation (wlan0/wireless): connection 'FitzsHub-59EB' has security, and secrets exist.  No new secrets needed.
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Config: added 'ssid' value 'FitzsHub-59EB'
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Config: added 'scan_ssid' value '1'
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Config: added 'key_mgmt' value 'NONE'
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Config: added 'auth_alg' value 'OPEN'
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Config: added 'wep_key0' value '<omitted>'
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Config: added 'wep_tx_keyidx' value '0'
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> Config: set interface ap_scan to 1
Mar  1 23:24:03 meshedgedx NetworkManager[6754]: <info> (wlan0): supplicant interface state: inactive -> scanning
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Mar  1 23:24:06 meshedgedx kernel: [11557.362803] wlan0: authenticate with 00:17:3b:4f:92:4d (try 1)
Mar  1 23:24:06 meshedgedx kernel: [11557.561660] wlan0: authenticate with 00:17:3b:4f:92:4d (try 2)
Mar  1 23:24:06 meshedgedx kernel: [11557.564478] wlan0: authenticated
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> (wlan0): supplicant interface state: authenticating -> associating
Mar  1 23:24:06 meshedgedx kernel: [11557.571693] wlan0: associate with 00:17:3b:4f:92:4d (try 1)
Mar  1 23:24:06 meshedgedx kernel: [11557.575602] wlan0: RX AssocResp from 00:17:3b:4f:92:4d (capab=0x411 status=0 aid=3)
Mar  1 23:24:06 meshedgedx kernel: [11557.575609] wlan0: associated
Mar  1 23:24:06 meshedgedx kernel: [11557.583620] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> (wlan0): supplicant interface state: associating -> completed
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'FitzsHub-59EB'.
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> dhclient started with pid 12020
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Mar  1 23:24:06 meshedgedx dhclient: Internet Systems Consortium DHCP Client 4.2.3-P1 Gentoo-r0
Mar  1 23:24:06 meshedgedx dhclient: Copyright 2004-2011 Internet Systems Consortium.
Mar  1 23:24:06 meshedgedx dhclient: All rights reserved.
Mar  1 23:24:06 meshedgedx dhclient: For info, please visit https://www.isc.org/software/dhcp/
Mar  1 23:24:06 meshedgedx dhclient:
Mar  1 23:24:06 meshedgedx NetworkManager[6754]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Mar  1 23:24:06 meshedgedx dhclient: Listening on LPF/wlan0/00:21:6a:9a:68:4c
Mar  1 23:24:06 meshedgedx dhclient: Sending on   LPF/wlan0/00:21:6a:9a:68:4c
Mar  1 23:24:06 meshedgedx dhclient: Sending on   Socket/fallback
Mar  1 23:24:06 meshedgedx dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Mar  1 23:24:07 meshedgedx avahi-daemon[6978]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::221:6aff:fe9a:684c.
Mar  1 23:24:07 meshedgedx avahi-daemon[6978]: New relevant interface wlan0.IPv6 for mDNS.
Mar  1 23:24:07 meshedgedx avahi-daemon[6978]: Registering new address record for fe80::221:6aff:fe9a:684c on wlan0.*.
Mar  1 23:24:08 meshedgedx dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Mar  1 23:24:08 meshedgedx dhclient: DHCPOFFER from 192.168.1.254
Mar  1 23:24:08 meshedgedx dhclient: DHCPACK from 192.168.1.254
Mar  1 23:24:08 meshedgedx dhclient: bound to 192.168.1.73 -- renewal in 42629 seconds.
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info>   address 192.168.1.73
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info>   prefix 24 (255.255.255.0)
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info>   gateway 192.168.1.254
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info>   hostname 'meshedgedx'
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info>   nameserver '192.168.1.254'
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info>   domain name 'home'
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Mar  1 23:24:08 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Mar  1 23:24:08 meshedgedx avahi-daemon[6978]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.73.
Mar  1 23:24:08 meshedgedx avahi-daemon[6978]: New relevant interface wlan0.IPv4 for mDNS.
Mar  1 23:24:08 meshedgedx avahi-daemon[6978]: Registering new address record for 192.168.1.73 on wlan0.IPv4.
Mar  1 23:24:09 meshedgedx NetworkManager[6754]: <info> Clearing nscd hosts cache.
Mar  1 23:24:09 meshedgedx NetworkManager[6754]: <info> (wlan0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Mar  1 23:24:09 meshedgedx NetworkManager[6754]: <info> Policy set 'FitzsHub-59EB' (wlan0) as default for IPv4 routing and DNS.
Mar  1 23:24:09 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) successful, device activated.
Mar  1 23:24:09 meshedgedx NetworkManager[6754]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Mar  1 23:24:16 meshedgedx kernel: [11567.964765] wlan0: no IPv6 routers present

I'd try the following (you'll need a working wired network connection while you do it):

1. Delete Wicd from the default runlevel, and re-add NetworkManager to the default runlevel:

Code: Select all
# rc-update del wicd default
# rc-update add NetworkManager default

2. Re-install NetworkManager but use Portage so that latest version is installed and so that it is rebuilt to use dhclient instead of dhcpcd:

a) Edit the file /etc/make.conf and make sure it has the following lines in it at the end of the file:

Code: Select all
PORTDIR_OVERLAY="${PORTDIR_OVERLAY} /usr/local/portage/"
ACCEPT_LICENSE="*"

(Delete the line PORTDIR_OVERLAY="/usr/local/portage/" if already in the file.)

b) Do the following:

Code: Select all
$ su
Password:
# # Following is just because Sabayon was not pre-configured to use Portage:
# equo install git
# emerge --sync
# layman -S
# layman -d sabayon
# layman -d sabayon-distro
# layman -a sabayon
# layman -a sabayon-distro
# layman -S
# # OK, now its is OK to install the package:
# FEATURES="-collision-detect -protect-owned" USE="-dhcpcd dhclient -resolvconf -connection-sharing" emerge -1v networkmanager
# etc-update # In case there are some config files to update. Enter -3 then answer yes to all.
# equo rescue spmsync # Tell Entropy what you did via Portage.
#

I still have the contents of /etc/NetworkManager/nm-system-settings.conf as:

Code: Select all
[main]
plugins=ifnet,keyfile

[ifnet]
managed=true
auto_refresh=false

3. Re-install nm-applet if you previously removed it:

Code: Select all
# emerge -1v nm-applet

4. Cross fingers, stop wicd and restart networking using NetworkManager:

Code: Select all
# /etc/init.d/wicd stop
# /etc/init.d/NetworkManager restart

5. Run nm-applet (but not as root user):

Code: Select all
$ nm-applet &

Then configure a WEP connection and try to connect.
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7340
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: WEP Key not working

Postby DrBenway » Fri Mar 02, 2012 2:42

Unfortunately I'm running into the same problem with NM as I did before. i.e adding a passkey in that's a variation on the one I entered. I've reinstalled it set it as default. Made sure it's using dhclient and is updated. I can't open /var/log/messages, unknown file type, however to see if there's any errors.

again thanks for the help
DrBenway
Baby Hen
 
Posts: 8
Joined: Tue Feb 28, 2012 3:48

Re: WEP Key not working

Postby Fitzcarraldo » Fri Mar 02, 2012 10:34

You can't open /var/log/messages even as root user?!

Code: Select all
$ ls -la /var/log/messages
-rw------- 1 root root 65715 Mar  2 09:26 /var/log/messages
$ tail -n 5 /var/log/messages
tail: cannot open `/var/log/messages' for reading: Permission denied
$ su
Password:
# tail -n 5 /var/log/messages
Mar  2 09:26:27 localhost su[7591]: pam_unix(su:session): session opened for user root by sabayonuser(uid=1000)
Mar  2 09:26:42 localhost su[7591]: pam_unix(su:session): session closed for user root
Mar  2 09:27:06 localhost su[7603]: Successful su for root by sabayonuser
Mar  2 09:27:06 localhost su[7603]: + /dev/pts/1 sabayonuser:root
Mar  2 09:27:06 localhost su[7603]: pam_unix(su:session): session opened for user root by sabayonuser(uid=1000)
#

You're going to need to do some more investigation to try and find out what the problem isn't. Temporarily disable encryption on your router, create a new connection using nm-applet and see if it works (ping and browse internet). Then, temporarily set your router to use WPA-TKIP, create a network connection using nm-applet and see if that works (ping and browse internet).
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7340
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: WEP Key not working

Postby DrBenway » Sat Mar 03, 2012 9:06

Unfortunately it's not my router to play with.

But here's my /var/log/messages:

Code: Select all
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Auto-activating connection 'leticia'.
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0) starting connection 'leticia'
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0/wireless): connection 'leticia' has security, and secrets exist.  No new secrets needed.
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Config: added 'ssid' value 'leticia'
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Config: added 'scan_ssid' value '1'
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Config: added 'key_mgmt' value 'NONE'
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Config: added 'auth_alg' value 'OPEN'
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Config: added 'wep_key0' value '<omitted>'
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Config: added 'wep_tx_keyidx' value '0'
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> Config: set interface ap_scan to 1
Mar  3 15:47:33 localhost NetworkManager[7340]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Mar  3 15:47:34 localhost kernel: [  172.668541] wlan0: authenticate with 00:1e:e3:ea:9c:26 (try 1)
Mar  3 15:47:34 localhost kernel: [  172.670539] wlan0: authenticated
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> (wlan0): supplicant interface state: authenticating -> associating
Mar  3 15:47:34 localhost kernel: [  172.690176] wlan0: associate with 00:1e:e3:ea:9c:26 (try 1)
Mar  3 15:47:34 localhost kernel: [  172.692536] wlan0: RX ReassocResp from 00:1e:e3:ea:9c:26 (capab=0x431 status=0 aid=4)
Mar  3 15:47:34 localhost kernel: [  172.692542] wlan0: associated
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> (wlan0): supplicant interface state: associating -> completed
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'leticia'.
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> dhcpcd started with pid 8539
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> Activation (wlan0) Beginning IP6 addrconf.
Mar  3 15:47:34 localhost avahi-daemon[7651]: Withdrawing address record for fe80::4e0f:6eff:fee3:5ae2 on wlan0.
Mar  3 15:47:34 localhost avahi-daemon[7651]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::4e0f:6eff:fee3:5ae2.
Mar  3 15:47:34 localhost avahi-daemon[7651]: Interface wlan0.IPv6 no longer relevant for mDNS.
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Mar  3 15:47:34 localhost dhcpcd[8539]: version 5.2.12 starting
Mar  3 15:47:34 localhost dhcpcd[8539]: wlan0: broadcasting for a lease
Mar  3 15:47:34 localhost NetworkManager[7340]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Mar  3 15:47:35 localhost avahi-daemon[7651]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::4e0f:6eff:fee3:5ae2.
Mar  3 15:47:35 localhost avahi-daemon[7651]: New relevant interface wlan0.IPv6 for mDNS.
Mar  3 15:47:35 localhost avahi-daemon[7651]: Registering new address record for fe80::4e0f:6eff:fee3:5ae2 on wlan0.*.
Mar  3 15:47:44 localhost kernel: [  182.979522] wlan0: no IPv6 routers present
Mar  3 15:47:54 localhost NetworkManager[7340]: <info> (wlan0): IP6 addrconf timed out or failed.
Mar  3 15:47:54 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) scheduled...
Mar  3 15:47:54 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) started...
Mar  3 15:47:54 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Timeout) complete.
Mar  3 15:48:04 localhost dhcpcd[8539]: timed out
Mar  3 15:48:04 localhost NetworkManager[7340]: <info> (wlan0): DHCPv4 client pid 8539 exited with status 1
Mar  3 15:48:04 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Mar  3 15:48:04 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started...
Mar  3 15:48:04 localhost NetworkManager[7340]: <warn> Activation (wlan0/wireless): could not get IP configuration for connection 'leticia'.
Mar  3 15:48:04 localhost NetworkManager[7340]: <info> (wlan0): device state change: ip-config -> need-auth (reason 'none') [70 60 0]
Mar  3 15:48:04 localhost kernel: [  202.716617] wlan0: deauthenticating from 00:1e:e3:ea:9c:26 by local choice (reason=3)
Mar  3 15:48:04 localhost NetworkManager[7340]: <info> Activation (wlan0/wireless): asking for new secrets
Mar  3 15:48:04 localhost NetworkManager[7340]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete.
Mar  3 15:48:04 localhost kernel: [  202.736351] cfg80211: Calling CRDA to update world regulatory domain
Mar  3 15:48:04 localhost NetworkManager[7340]: <info> (wlan0): supplicant interface state: completed -> disconnected


At one point it says it's connected:

Mar 3 15:47:34 localhost NetworkManager[7340]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'leticia'.


But then it can't find the IP:

Mar 3 15:48:04 localhost NetworkManager[7340]: <warn> Activation (wlan0/wireless): could not get IP configuration for connection 'leticia'.


Also it seems that it's still using dhcpcd rather than dhclient. How can I switch?
DrBenway
Baby Hen
 
Posts: 8
Joined: Tue Feb 28, 2012 3:48

Next

Return to Networking and Wireless

Who is online

Users browsing this forum: No registered users and 1 guest