Bugzilla – Bug 154327
NetworkManager: can't connect to WEP encrypted network with Prism 2.5 chip
Last modified: 2007-06-05 09:57:48 UTC
I can't click to "Connect" .. see attachment BTW I can't also connect to my Access-Point with WEP. (orinoco_cs)
Created attachment 70766 [details] Form bug?
This doesn't look exactly like a bug. Please describe in more detail what you did to produce this problem and why it should work.
My way: Start Yast -> config my wireless network card for dhcp and WEP (like in SUSE10.0) -> But not work (wlan has no IP) here.. -> click on knetworkmanager icon in kicker and I can't see my Access-Point only another AP. hmh.. click on connect to another wireless.. fill out the window like my attachment but the connect button is disabled.. Why?
OK then the source of the problem is YaST. Attach the /var/log/YaST2 directory as well as the contents of /etc/sysconfig/network.
Created attachment 70817 [details] y2log
Created attachment 70818 [details] /etc/sysconfig/network files
Created attachment 70929 [details] some error messages form /var/log/messages
I have add some files.. I hope its enough.. if not please contact me.
this is a networkmanager problem i think. please reassign to us back if not.
This actually looks like a driver issue. RML?
(In reply to comment #3) > hmh.. click on connect to another wireless.. fill out the window like my > attachment but the connect button is disabled.. Why? Please omit entering the dashes. They are not part of the key. While typing the hex key you will see the connect button being active once you've entered a key with a reasonable key length.
Tom, please report whether it is now working as expected.
ok the entering works now.. I can click on connect button but no success.. BTW: IMO it's more userfriendly to kill the dashes or write a short note. Now I have tested with ifup in yast and it works better. My way: Yast2 -> config network card -> select ifup -> save this settings.. Start konqueror or firefox and enter url.. no success.. BUT if I enter in konqueror sftp://foo.com ... this works fine.. http(s) in konqueror and firefox works only after restart my kde session. very crazy ;) I install some updates from opensuse factory dir like yast2 and networkmanager rpms but with networkmanager at the moment no success..
(In reply to comment #13) > ok the entering works now.. I can click on connect button but no success.. Tom, could you please provide the output of /var/log/NetworkManager while connecting?
Created attachment 71072 [details] /var/log/NetworkManager
Thanks for the log. Is your AP broadcasting its ESSID? If not, it would be nice to see whether it works if you reconfigure your AP to broadcast its ESSID and try again.
Created attachment 71073 [details] /var/log/NetworkManager Setup with Yast2
yes ESSID is hide.. I will change and test this.
Perfect, thanks!
Created attachment 71075 [details] /var/log/NetworkManager ESSID is active
hmh not work.. ok I can sse my AP but connection failed.. BTW: After I run rcnetwork restart.. I haven't any AP in my NetworkManager list.. NetworkManager autom. scan the net periodly?
Hmm, looks strange, could you please run kwalletmanager and check whether the correct key is stored in the wallet for KNetworkManager? If it does not look like the right key you can correct it directly using the KWallet. The end of the log shows that NM does not see KNetworkManager currently on the bus. Please do the following: * Quit KNetworkManager, make sure that the instance died the hero's death (killall knetworkmanager) * rcnetwork restart * Start KNetworkManager Having this done, please give it (yet) another try. (Yes, NetworkManager automatically scans for networks)
hmh good idea but the entry in kwallet is correct. I remove also this kwalletmanager dir in kwallet.. but the same problem.. /var/log/messages means: Mar 2 23:01:55 linux kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 2 23:01:57 linux kernel: wlan0: New link status: Connected (0001) Mar 2 23:01:57 linux kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 2 23:02:08 linux kernel: wlan0: no IPv6 routers present Mar 2 23:02:11 linux kernel: wlan0: New link status: Disconnected (0002) Mar 2 23:02:11 linux kernel: wlan0: New link status: Connected (0001) Mar 2 23:02:12 linux kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 2 23:02:13 linux kernel: wlan0: New link status: Disconnected (0002) Mar 2 23:02:13 linux kernel: wlan0: New link status: Connected (0001) Mar 2 23:02:15 linux kernel: wlan0: New link status: Disconnected (0002) Mar 2 23:02:15 linux kernel: wlan0: New link status: Connected (0001) Mar 2 23:02:17 linux dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Mar 2 23:02:21 linux dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 Mar 2 23:02:22 linux kernel: wlan0: no IPv6 routers present Mar 2 23:02:28 linux dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 Mar 2 23:02:42 linux dhclient: caught deadly SIGTERM Mar 2 23:02:42 linux dhclient: could not restore resolv.conf: No such file or directory Mar 2 23:03:17 linux kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Do you get the same results when using nm-applet (it is part of the package NetworkManager-gnome)?
nope.. the same problem..
Tom, thanks for doing all the testing. We have a NetworkManager bug. ifup seems to work in general (at least that is how I interpret comment #13). For the log: * Actiontec Electronics Prism 2.5 Wavelan chipset * wlan0: Device is fully-supported using driver 'orinoco_pci'. Robert, any idea? Adjusting summary.
If I disable WEP for my AP it works fine with networkmanager. BTW: I have a ibm thinkpad a31p with Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) and Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
Tom, can you please update to the NetworkManager packages available at: http://primates.ximian.com/~rml/misc/NetworkManager/ An updated package of KNetworkManager which works with the above version of NetworkManager is available, too: http://www.fh-augsburg.de/~thoenig/KNetworkManager/ Please report if this helps.
sorry .. no success.. I think it's the same bug like 144268
Created attachment 72056 [details] 0.6.0cvs20060307-2
Created attachment 73784 [details] Beta8 NetworkManager Crash!
Tom, could you please open a bug for this crash. It will probably help if you attach /etc/sysconfig/network/ifcfg-wlan-id-00:20:e0:8f:a0:58 to the new bug. It has nothing to do with the Prism problem.
is done .. see bug 159394
This is fixed. Marking as duplicate of bug #144268 which covers this issue. *** This bug has been marked as a duplicate of 144268 ***
its not fixed in beta9 and also not fixed with latest NetworkManager, kernel, etc. packages. At the moment if I select NetworkManager in yast I can see 'No network card found...' /var/log/NetworkManager: Apr 10 21:13:11 linux NetworkManager: <information> starting... Apr 10 21:13:12 linux NetworkManager: <debug info> [1144696392.312651] nm_system_device_get_system_config (): found config '/etc/sysconfig/network/ifcfg-wlan-id-00:20:e0:8f:a0:58' for interface 'wlan0' Apr 10 21:13:12 linux NetworkManager: <debug info> [1144696392.312996] nm_system_device_get_system_config (): BOOTPROTO=dhcp Apr 10 21:13:12 linux NetworkManager: <debug info> [1144696392.313399] nm_system_device_get_system_config (): Adding 'Dead23' to the list of trusted networks
Tom, could you please answer my question from comment #16? Thanks!
Could you also test it when using the hostap driver instead of orinoco? Just do 'rmmod orinoco_pci ; modprobe hostap_pci'. hostap is intended to be default, but this is another problem.
with essid or without.. the same problem.. the first time after installation works but after reboot I have no success.. perhabs bug 162750 is a part of this problem.. btw.. I will test comment #37
to comment #37: at the moment I have no orinoco_pci loaded.. but prism2_pci.. I have change this but no success.. also after setup yast to force the hostap_pci driver and also after reboot. After switch to NetworkManager.. KNetworkManager is not startet..(why?) ok I start it manually.. I see KNetworkManager is startet (ok empty icon but it's not the problem) if I click on icon I see NetworkManager is not running.. but: 6578 ? S 0:00 knetworkmanager [kdeinit] 6636 ? Ss 0:00 /usr/sbin/dhcdbd --system 6688 ? Ss 0:00 /usr/sbin/NetworkManagerDispatcher
...? NetworkManager ain't running or?
no good news with rc2.. nothing work for wlan.. only LAN work with NetworkManager.. but KNetworkManager means NetworkManager is not running.......
ups sorry LAN don't work with NetworkManager. If I select NetworkManager and config my LAN Network Card for DHCP KnetworkManager means no network found.
Hm, sorry, but I don't get what you're saying. With my question from comment #40 I just wanted to know whether the NetworkManager daemon process is running or not.
IMHO can you see that with the comment #39 (ps -ax) = it's running - or I'm wrong?
No, in comment #39 it looks like NetworkManager is not running (at least if you had grep'ed the process list for the string 'NetworkManager'). On a NetworkManager-enabled system the command `ps ax | grep NetworkManager` should return something like this: 2650 ? Ssl 0:00 /usr/sbin/NetworkManager 2696 ? Ss 0:00 /usr/sbin/NetworkManagerDispatcher However, in comment #39 I'm missing the NetworkManager process.
I have check this again.. NetworkManager is running: 6452 ? Ss 0:00 /usr/sbin/NetworkManagerDispatcher 6453 ? Ss 0:00 /usr/sbin/NetworkManager 6675 ? S 0:00 knetworkmanager [kdeinit] Apr 27 23:26:09 linux-sts NetworkManager: <information> starting... Apr 27 23:26:09 linux-sts NetworkManager: <debug info> [1146173169.811873] nm_system_device_get_system_config (): found config '/etc/sysconfig/network/ifcfg-wlan-id-00:20:e0:8f:a0:58' for interface 'wlan0' Apr 27 23:26:09 linux-sts NetworkManager: <debug info> [1146173169.812911] nm_system_device_get_system_config (): BOOTPROTO=dhcp Apr 27 23:26:09 linux-sts NetworkManager: <debug info> [1146173169.813541] nm_system_device_get_system_config (): Adding 'Dead23' to the list of trusted networks
At the moment it works with factory install and NetworkManager. But I haven't configured the wlan-card! Only the wired card is configured with dhcp. I think kwallet has the key for my AP. So its o.k. I will test it later with configured wlan-card.
So after I configured my wlan-card with yast - knetworkmanager means no NetworkManager is running.. Correct I can't found any process NetworkManager. I run rcnetwork restart.. I reconfigured with yast no process NetworkManager! Very strange. O.k. I restart my notebook but the same problem. No NetworkManager process. If I enter NetworkManager in konsole as root I receive no feedback.. I "love" the NetworkManager :( Ok I will switch back to unconfigured wlan-card. So I setup this in yast and save this selection.. ( After this action my mousepointer jump during moving - only restart helps here..but this is another problem :) So I can see I have NetworkManager process but Network don't work. But after I restart my computer it works fine..
Tom, you do not need to configure your wireless card in YaST if you want to use NetworkManager. Simply switch your network setup method to "User controlled with NetworkManager" (YaST->Network Devices->NetworkCard). (In reply to comment #48) > But after I restart my computer it works fine.. Confusion! What are you saying? It now does work?
Yes it works.. But IMHO it's not user-friendly if I can setup my wlan-card in yast! I think for most of people its the normally way to setup the wlan-network card in yast. And the user get no feedback why it doesn't work.
(In reply to comment #50) > Yes it works.. Good news! > But IMHO it's not user-friendly if I can setup my wlan-card in yast! I think > for most of people its the normally way to setup the wlan-network card in > yast. And the user get no feedback why it doesn't work. By default users will not run into any problems as it will Just Work after installation. Anyone falling back to old habits (using YaST to configure the wireless card) will most likely not try to use one of the NetworkManager applets to get things working. Thanks for testing and reporting. Closing as FIXED.