Bug 388081

Summary: Wireless Lan WEP 128 bit key connection don't work.
Product: [openSUSE] openSUSE 11.0 Reporter: Luc Evers <lucevers>
Component: NetworkAssignee: Tambet Ingo <tambet>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: lucevers
Version: Beta 2Flags: coolo: SHIP_STOPPER-
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.0   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log files
NetworkManager & wpa_supplicant.log
Test Beta3 Wireless Lan failure with Key
Netmanager inf
screen captures
NetworkManager

Description Luc Evers 2008-05-08 06:40:41 UTC
On portable HP Compac 8230, wireless lan works without WEP key.
Introducing a Web key: connection failed.
Using Yast : during the wirelesss configuration, the software asked for a 
packet download but the connection is not active!

Second try: connect a fix Lan so de software can download the packets he need.
            Packets loaded but wireless lan can't access.


OpenSuse 10.2, 10.3:works fine.



  Regards

  Luc.
Comment 1 Stephan Kulow 2008-05-08 07:08:31 UTC
please provide your yast logs and mention what medium you installed from
Comment 2 Luc Evers 2008-05-10 06:29:40 UTC
Created attachment 214120 [details]
y2log files

Bug 388081: web key 128bit can't connect.
Comment 3 Luc Evers 2008-05-10 06:31:33 UTC
medium: openSUSE-11.0-Beta2-DVD-i386.torrent


 Regards

   Luc.
Comment 4 Stephan Kulow 2008-05-11 06:23:55 UTC
your log file looks like nothing was written to /etc/sysconfig/network/ - can you please verify that?

Stefan, yast2-bootloader had a very similiar bug that was fixed in not using TextEntry any longer. Either this widget should be removed or it should work (if that's the bug).
Comment 5 Michal Zugec 2008-05-11 13:20:23 UTC
No, it seems configuration was written:

2008-05-08 19:19:30 <1> suse11(3698) [YCP] NetworkInterfaces.ycp:1432 List(  ) = [
     "eth0",
     "lo",
     "eth1"
]



 but:

2008-05-08 19:19:18 <3> suse11(3698) [bash] ShellCommand.cc(shellcommand):78               No configuration found for pan0


This leads me to idea that user has xen kernel with xend service running? This (it's documented) doesn't work with NetworkManager (reporter's network type). Also bridge-utils package is not installed, this is probably problem of xen package/pattern
Comment 6 Michal Zugec 2008-05-12 06:34:48 UTC
Please be more verbose
>> Using Yast : during the wirelesss configuration, the software asked for a 
>> packet download but the connection is not active!

This is duplicate of bug #387050


>> On portable HP Compac 8230, wireless lan works without WEP key.
>> Introducing a Web key: connection failed.

Did you use NetworkManager?
Comment 7 Luc Evers 2008-05-12 09:23:59 UTC
 
 You question:
   Did you use NetworkManager?   Answer: Yes.

 during the wireless configuration, the software asked for a 
 packet download but the connection is not active!

  More info:
  ----------
     Msg during configuration:
-----------------------------------------------------------
       Cannot access installation media
       Check whether the server is accessible
       http://download.opensuse.org/update/11.0/
       error Couldn't resolve host.    
-----------------------------------------------------------

 Second test (configure via Yast):

 - Acivate fix eth connection -> oke internet reachable.
 - configure again Wireless connection. -> no error msg
 - deactivate fix eth connection check wireless connection -> noke.
 - configure again Wireless connection -> same problem: the software asked for a 
   packet download. 


Comment 9 Stefan Hundhammer 2008-05-13 12:12:49 UTC
(In reply to comment #4 from Stephan Kulow)
> Stefan, yast2-bootloader had a very similiar bug that was fixed in not using
> TextEntry any longer. Either this widget should be removed or it should work
> (if that's the bug).

?! Please elaborate.

Was it this:

http://lists.opensuse.org/yast-devel/2007-12/msg00011.html
http://lists.opensuse.org/yast-devel/2007-12/msg00033.html

?

Comment 11 Helmut Schaa 2008-05-19 07:17:03 UTC
Luc, as you used NetworkManager could you please attach /var/log/NetworkManager and /var/log/wpa_supplicant?
Comment 12 Luc Evers 2008-05-19 18:08:16 UTC
Created attachment 216572 [details]
NetworkManager & wpa_supplicant.log
Comment 13 Luc Evers 2008-05-19 18:11:27 UTC
 Helmut,
 
 iwconfig information:

eth1      unassociated  ESSID:off/any
          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:14:C1:24:CD:7D
          Bit Rate:0 kb/s   Tx-Power=20 dBm   Sensitivity=8/0
          Retry 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:1   Missed beacon:0

Comment 14 Luc Evers 2008-05-20 06:13:50 UTC
REM
ifcfg-eth1 was filled in, compared with OpenSuse 10.3 -> oke
  
Comment 15 Helmut Schaa 2008-05-20 07:02:06 UTC
Luc, which AP is WEP-encrypted? HomeRouter?
Could you please attach the output of iwlist scan which shows both APs?
Comment 16 Luc Evers 2008-05-20 16:29:03 UTC
Helmut,

I'm using ESSID:"HomeRouter" with a key (channel 10), the others are my neighbors
whithout key.

suse11:/home/luc # iwlist scanning
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

eth1      Scan completed :
          Cell 01 - Address: 00:14:C1:24:CD:7D
                    ESSID:"USR5463"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s
                              6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=99/100  Signal level=-61 dBm
                    Extra: Last beacon: 96ms ago
          Cell 02 - Address: 00:01:E3:07:28:75
                    ESSID:"HomeRouter"
                    Protocol:IEEE 802.11b
                    Mode:Master
                    Frequency:2.457 GHz (Channel 10)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Quality=99/100  Signal level=-21 dBm
                    Extra: Last beacon: 40ms ago
          Cell 03 - Address: 00:15:E9:04:76:94
                    ESSID:"GCC"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=27/100  Signal level=-83 dBm
                    Extra: Last beacon: 3788ms ago

pan0      Interface doesn't support scanning.

Comment 17 Helmut Schaa 2008-05-21 09:22:45 UTC
Tambet, could you give us a hand here?
Comment 18 Tambet Ingo 2008-05-21 09:33:57 UTC
This was a problem with NetworkManager's system settings daemon and should be fixed in beta 3 (NetworkManager-0.7.0.r3649-*).
Comment 19 Luc Evers 2008-05-22 09:20:42 UTC
 Ok, thanks

 I'll test beta 3.
Comment 20 Luc Evers 2008-05-23 19:38:35 UTC
 Test Beta3

 Same problems: HomeRouter(SSID) with key don't work.
                Without key I can make a connection.
                ESSID:"USR5463" works, no key

 During install (not automatic) I saw also that you can't choise the wireless connection.
   Test connection to the internet.
        only eth0 is possible too choise.
        Change Device button only avaulable if you swith from:
            - Yes, Test connection to internet
            - No Skip this test.
        To activate the button (Change device) : 
              - press on No, Skip this test
              - press again Ys, Test connection to internet ...
              Then you can press on 'Change Device' but only ETH0 is availble.
              The system don't see the fix connection is not active and stay
              trying to 'Download the release notes) .
        Another bug I think.

 So, The problem stay on Beta 3, I'll check the data.
 In attach the logs.
   
  
Comment 21 Luc Evers 2008-05-23 19:39:50 UTC
Created attachment 217894 [details]
Test Beta3 Wireless Lan failure with Key
Comment 22 Tambet Ingo 2008-05-26 07:21:57 UTC
I'd like to see /var/log/NetworkManager. Please keep NetworkManager and installation/ifup/yast porblems separate.
Comment 23 Luc Evers 2008-05-26 16:11:46 UTC
Created attachment 218160 [details]
Netmanager inf
Comment 24 Michal Zugec 2008-05-29 14:59:39 UTC
In comment #14 reporter says that written configuration is ok. So I suppose this is not YaST bug, but NetworkManager related
Comment 25 Tambet Ingo 2008-05-29 15:14:00 UTC
According to the log file from comment #23, NM reads a system connection from /etc/sysconfig/network/ifcfg-eth1. That file is for essid 'HomeRouter' and does not provide any passwords. Is that correct? If so, use yast to configure the device and provide the wep keys. Alternatively, you can use NM panel applet's "Connect to Other Wireless Network", fill in essid and security.
Comment 26 Luc Evers 2008-05-30 07:48:39 UTC
   The keys are filled in,see also Comment #14:

   ifcfg-eth1 was filled in, compared with OpenSuse 10.3 -> oke
    

   The problem is iwconfig don't see a key:
   Encryption key:off
Comment 27 Tambet Ingo 2008-05-30 08:01:19 UTC
NetworkManager log shows that the key is requested by wpa_supplicant but NM doesn't have a key for it. It looks to me like a NM's sysconfig parser error.

I think the easiest workaround should be to go to yast and delete the wireless device's configuration (yast -> Network Devices -> Network Settings -> select your wireless card and click "Delete") and use only NetworkManager for connection. Could you try that and let me know if that works?

Can you mail that file (ifcfg-eth1) to me privately (tambet@novell.com) so I can test with it?
Comment 28 Luc Evers 2008-05-31 09:08:38 UTC
I've got the same problems with the  'Delete' action, the system try to connect to the internet. (needs more packets?)
After skiping the questions (see png file delete),wireless device was deleted.
Then trying to make a connection didn't work with HomeRouter (Wep Key),
 Wireless connections without Web Key works.

In attach you find two png files with aa screen capture.
Comment 29 Luc Evers 2008-05-31 09:09:48 UTC
Created attachment 219327 [details]
screen captures
Comment 30 Luc Evers 2008-05-31 09:16:54 UTC
ifcfg-eth1 is send to you privately.
Comment 31 Stephan Kulow 2008-05-31 10:44:35 UTC
sounds specific
Comment 32 Tambet Ingo 2008-06-02 08:16:23 UTC
The ifcfg-eth1 I received was parsed just fine on my machine, so the log file from comment #23 does not seem right:

May 26 20:05:11 lsuse11 NetworkManager: <info>  Activation (eth1/wireless): access point 'System HomeRouter (eth1)' has security, but secrets are required.

The secrets are extracted from ifcfg-eth1 correctly.

There is a bug where NM does not re-read yast configured device configurations when they change (378802, can't check in fixes for 'normal' bugs anymore), maybe you provided the secrets when NM was already running and the old information it had didn't contain secrets yet? Same thing about trying without yast configuration (comment #28), what was the connection name in the applet you tried to activate? If it was "System $essid", then it still tried to use the deleted connection. Restarting NM does not help, configuration file reading is handled by another process (nm-system-settings), so to make sure NM has updated it's information after yast is used to change network settings is to kill that process (it's started again automatically).

Can I see your /var/log/NetworkManager log from when you tested with deleted yast configuration, comment #28?
Comment 33 Luc Evers 2008-06-02 16:52:13 UTC
Created attachment 219576 [details]
NetworkManager
Comment 34 Luc Evers 2008-06-02 16:54:22 UTC
Info Netmangager in attachment
Comment 35 Tambet Ingo 2008-06-03 07:55:03 UTC
The log shows you never removed the yast configuration of the wireless device. The one attempt you did with a connection created from the applet shows you didn't specify any security and that's why that one failed.

It doesn't look like we're getting anywhere over the bugzilla. Is it possible for you to come to irc to speed up things? I'm always on irc.freenode.net #opensuse-gnome channel, nick tambeti.
Comment 36 Luc Evers 2008-06-03 20:57:59 UTC
 Ingo, 

 Tested again and only NetworkManager used, again no connection.

 Maybe the best method is an SSH access to my PC.
 I can give you acces via a fix DSL line, than you can check the configuration
 and the problems with Yast. 

 
Comment 37 Tambet Ingo 2008-06-09 12:01:29 UTC
I'm afraid I can't debug the problem very well, I can't access your nm-applet over the network. I'll try to give all the required steps here:

# First, get a root shell
su -
# Remove yast configuration for eth1
mv /etc/sysconfig/network/ifcfg-eth1 /tmp
# Find the process id of nm-system-settings
ps aux | grep nm-system-settings
# Kill it, replace the proccess id with the correct id from the previous command
kill 1234

Right-click on the applet and choose "Edit Connections...". The connection editor shows up, click on the "Wireless" tab. If it contains any saved networks there, remove all of them (select a row and click "Delete" for each row). Now close the editor with the "Close" button.

Left-click on the applet and choose "HomeRouter" access point from the popup menu. The applet should ask for the WEP key, make sure the "Wireless Security" combo box has the correct authentication method, fill in the "Key" entry and click "Connect".

Let me know if it connects successfully. If not, attach the /var/log/NetworkManager log file here again so we can see what went wrong.
Comment 38 Luc Evers 2008-06-15 20:35:33 UTC
 The procedure for gnome works! 
  Result: successfull.


 Note;
    Took some time because after installing Beta3, the system blocks
    after a while - without error. (keyboard,mouse ..) .
    I shall introduce a new error for this problem. 
    Linux is running on a usb disk.
Comment 39 Tambet Ingo 2008-06-30 12:26:04 UTC
Good to know it works, thanks. The other part of the bug (NM not reading yast configuration correctly) is handled by bug #378802. So can we close this one?
Comment 40 Luc Evers 2008-07-01 18:39:39 UTC
 Oke, no problem to close the case.

  Regards,

  Luc. 
Comment 41 Tambet Ingo 2008-07-02 07:53:17 UTC
Thanks for doing all these steps to help me figure it out!