knetworkmanager fails to connect to WEP networks

English Network/Internet
1

Hi all

Since my update to OpenSuse 11.2 knetworkmanager refuses to connect to WEP enabled networks (worked fine with knetworkmanager 11.1). I am sure that I use the correct password and I tried on 3 different networks. The manager is connecting to open networks and WAP protected networks without problems.
I saw on other forums that there were similar problems with previous versions of networkmanager. But I could not find a solution for my problem.

This is the output for the knetworkmanager log file:

Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) starting connection 'WepWifi'
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0/wireless): access point 'WepWifi' has security, but secrets are required.
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 24 15:04:25 linux-6g9s NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x
Dec 24 15:04:25 linux-6g9s NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Dec 24 15:04:25 linux-6g9s NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0/wireless): connection 'WepWifi' has security, and secrets exist.  No new secrets needed.
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Config: added 'ssid' value 'WepWifi'
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE'
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Config: added 'wep_key0' value '<omitted>'
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Config: added 'wep_tx_keyidx' value '0'
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  Config: set interface ap_scan to 1
Dec 24 15:04:25 linux-6g9s NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> completed
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'KarliWifi'.
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction.
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  dhclient started with pid 2821
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 24 15:04:27 linux-6g9s NetworkManager: <info>  DHCP: device wlan0 state changed normal exit -> preinit
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  Device 'wlan0' DHCP transaction took too long (>45s), stopping it.
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  wlan0: canceled DHCP transaction, dhcp client pid 2821
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  Activation (wlan0/wireless): could not get IP configuration for connection 'WepWifi'.
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  (wlan0): device state change: 7 -> 6 (reason 0)
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
Dec 24 15:05:13 linux-6g9s NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.

iwlist scan outputs:

wlan0     Scan completed :
          Cell 01 - Address: 00:A0:C5:75:AF:E0
                    Channel:6                 
                    Frequency:2.437 GHz (Channel 6)
                    Quality=70/70  Signal level=-40 dBm  
                    Encryption key:on                    
                    ESSID:"WepWifi"                    
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Mode:Master                                
                    Extra:tsf=0000099d22ea6191                 
                    Extra: Last beacon: 192ms ago              
                    IE: Unknown: 00094B61726C6957696669        
                    IE: Unknown: 010482848B96                  
                    IE: Unknown: 030106
          Cell 02 - Address: 00:02:CF:EA:17:C0
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=46/70  Signal level=-64 dBm
                    Encryption key:on
                    ESSID:"Ebb_WLAN"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000000497a0f15a
                    Extra: Last beacon: 4112ms ago
                    IE: Unknown: 00084562625F574C414E
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030106
                    IE: Unknown: 2A0106
                    IE: Unknown: 32040C183060
                    IE: Unknown: 2D1A6E1017FFFF0000010000000000000000000000000C0000000000
                    IE: Unknown: 3D1606070500000000000000000000000000000000000000
                    IE: Unknown: 3E0100
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: 7F0101
                    IE: Unknown: DD07000C4304000000
                    IE: Unknown: 0706434820010E10
                    IE: Unknown: DD1E00904C336E1017FFFF0000010000000000000000000000000C0000000000
                    IE: Unknown: DD1A00904C3406070500000000000000000000000000000000000000

Any ideas what could cause the problem?

2

Please post the output of

/usr/sbin/iwconfig
/sbin/route -n

3

here it is
iwconfig

wlan0     IEEE 802.11abgn  ESSID:"\x02\x1A\xFEC\xFB\xFA\xAA:\xFB)\xD1\xE6\x05<|\x94u\xD8\xBEa\x89\xF9\\xBB\xA8\x99\x0F\x95\xB1\xEB\xF1\xB3"
          Mode:Managed  Frequency:2.437 GHz  Access Point: Not-Associated
          Tx-Power=15 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

/sbin/route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     1      0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

(only eth0 is connected?)

4

On 12/24/2009 10:16 AM, serengeti wrote:
>
> here it is
> iwconfig
>
> Code:
> --------------------
> wlan0 IEEE 802.11abgn ESSID:"\x02\x1A\xFEC\xFB\xFA\xAA:\xFB)\xD1\xE6\x05<|\x94u\xD8\xBEa\x89\xF9\xBB\xA8\x99\x0F\x95\xB1\xEB\xF1\xB3"
> Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
> Tx-Power=15 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0

You need to at least try a connection first. The above ESSID is just garbage,
not the one in your NM log.

5

OK.this is the updated answer

wlan0     IEEE 802.11abgn  ESSID:"WepWifi"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:A0:C5:75:AF:E0
          Bit Rate=11 Mb/s   Tx-Power=15 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:07D3-1767-7E90-3AB6-7CAB-5881-BE
          Power Management:off
          Link Quality=67/70  Signal level=-43 dBm  Noise level=-94 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

The routing table did not change

6

On 12/24/2009 11:26 AM, serengeti wrote:
>
> OK.this is the updated answer
>
>
> Code:
> --------------------
> wlan0 IEEE 802.11abgn ESSID:“WepWifi”
> Mode:Managed Frequency:2.437 GHz Access Point: 00:A0:C5:75:AF:E0
> Bit Rate=11 Mb/s Tx-Power=15 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:07D3-1767-7E90-3AB6-7CAB-5881-BE
> Power Management:off
> Link Quality=67/70 Signal level=-43 dBm Noise level=-94 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0

You have connected and authenticated.

The problem is likely with routing. There have been problems when the wired
connection is enabled on boot. It should be set to be enabled when the cable is
connected. Edit (as root) /etc/sysconfig/network/ifcfg-eth0 and change the
STARTMODE line to ifplugd.

7

Hi lwfinger

Thank you for this hint. STARTMODE was set to ‘auto’.
I changed it to ifplugd and rebooted but the change had no effect.

8

On 12/24/2009 05:26 PM, serengeti wrote:
>
> Hi lwfinger
>
> Thank you for this hint. STARTMODE was set to ‘auto’.
> I changed it to ifplugd and rebooted but the change had no effect.

Have you updated to the latest packages?

9

Yes I do.

I have networkmanager 0.7.1_git20090811-4.2 and NetworkManager-kde4 0.9.svn1043876-1.3.1
from the 11.2 update repository

10

I have the same issue with the kde4 networkmanager widget on both 11.1 and 11.2. The gnome nm-applet (in LXDE or GNOME) or disabling NM (using ifup/ifdown) does work. There does seem to be a new option for wicd in 11.2 though I have not tested that.

11

I had hoped my problems would be solved by 11.2. I have 2 laptops, an HP and lenovo. Both are dual boot 11.2 KDE with windows 7. Neither will logon to my WEP wireless, but they recognize strength of the signal.

I have been easily able to get onto an unsecured wireless network, leading me to believe most of my problems are related to the KWallet.

Since we have log-in passwords, why do we need the extra security to sign into a private wifi?

Nakota

12

On 01/26/2010 06:36 PM, nakota wrote:
>
> I had hoped my problems would be solved by 11.2. I have 2 laptops, an HP
> and lenovo. Both are dual boot 11.2 KDE with windows 7. Neither will
> logon to my WEP wireless, but they recognize strength of the signal.
>
> I have been easily able to get onto an unsecured wireless network,
> leading me to believe most of my problems are related to the KWallet.
>
> Since we have log-in passwords, why do we need the extra security to
> sign into a private wifi?

With WEP, it doesn’t really matter as it is so easily cracked.

Are you using the hexadecimal key, or a passphrase to connect? You must use the
hex key. I do not believe that KWallet is the problem.

With an open network, any nearby user can connect to your network and steal
access from you. Even worse, they could use your network to download kiddie
porn. If the authorities managed to capture the site, guess whose IP number
would be listed as the recipient? I have heard of one case where a computer was
siezed and the supposedly “innocent” person was prosecuted!

13

I understand the dangers of unsecured networks. I am using the hex key without success. I just migrated from KDE (which I prefer) to Gnome and have full function of my wireless now