Version: 0.1 prerelease (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu18 dapper) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15-26-386 Hello, Computer : HP Nx6125 AMD 64 Wifi Card : BCM4318 Wifi installed with the ndiswrapper method. Bugs : When I try to connect the laptop with the wifi network with the help of knetworkmanager, the software shows "28% / Activation Stage : Configuring device", and stops during 1 minute. After that, the software run normally but without wifi connection. > The software Knetworkmanager is functionnal with the wired networks. > The software Knetworkmanager scans allready the wifi networks, but don't connect with them. > I can configure and use without problem the wifi connection with the System settings. > My file (/etc/network/interfaces contains only these both lines : auto lo iface lo inet loopback Thanks for your help.
I have this "28% problem" as well, together with some more info which might be relevant. If I use the "traditional ifup/ifdown" method, I can get wireless connectivity, but only if I "ifdown eth0" first. This makes me think it's a dchp issue: knetwork manager won't let me disable eth0, and if this was allowed then wireless might work. I use kde in SUSE 10.1; however, I get a similar issue with gnome in Ubuntu dapper - I have to deactivate the wired network before the wired network will work (having been activated). I suspect it's the same issue. My computer is a Fujitsu Siemens amilo a1630 (AMD64) and I'm running 32 bit Suse 10.1. My wireless card is a ralink rt2500 mini-pci, and I compiled the drivers from source as per a wordpress.linux wiki. If you come up with a knetworkmanager beta that you'd like me to try on my laptop, let me know.
If you have WPA/TKIP access point, you should create profile manually for it. When I associated with my HP nx7010 - Ubuntu Dapper (ipw2100) by clicking on the founded wifi network and after I wrote the passphrase into the input field I stopped at near 28% too. After I have created the profile manually, and chosed from the dropdown list the WPA/TKIP, it moved forward after 28% (for me). I think this is because of the detection of WPA/TKIP and WPA/AES problem.
I do have the same issue. I can't connect to my WPA2/AES network automatically, but if I enter all data by hand it works. Sadly only for that one time, after that I need to do it by hand again...
also have this problem, It gets to 28% then keeps asking for wpa passhprase over and over and over again. I am using 0.1 on Opensuse 10.2 with KDE 3.5.5
I also have the 28% hang issue. If I configure my wireless router to broadcast my SSID my OpenSuse 10.2 laptop connects.
I have a Netgear WG511v2 card, with the troublesome Marvell/Libertas chipset, that requires ndiswrapper. The card will not connect to my access point using KNetworkManager. However, if I go into YaST|Network Devices|Network Card and choose 'Traditional Method with ifup' and setup the card manually to use ndiswrapper under Module Name, it connects fine (open or WEP only. WPA still won't play!) I've tried identical settings using NetworkManager instead of ifup, but no joy. The connection light goes green on my card, the orange activity light flickers occasionally. But no pings, no internet connection, no access to my router admin page at 192.168.0.1. Using the icon in the tray I can bring up the detected networks (so scanning works fine) but when I attempt to connect to my network I get the 'connection progress' speech bubble with a progress bar that fills up almost instantly to 28%, stalls there for a couple of seconds with tray icon showing an animated cog, then disappears completely and I remain unconnected. Open, WEP and WPA all produce the same result. Switch back to ifup method, with same settings, and the card works (apart from WPA). Great looking app. Frustrating that it doesn't work in my case. Hope this helps with diagnosis. Rich
Since all these comments mention different drivers, I suspect that the problem lies in the NetworkManager daemon or in the drivers. If possible, please install the gnome nm-applet and see if it works with that. NB 3945abg users: There is a known problem that this driver sends disconnects during the connection setup process that breaks NetworkManager - see the NetworkManager List.
> ------- Since all these comments mention different drivers, I suspect that > the problem lies in the NetworkManager daemon or in the drivers. If > possible, please install the gnome nm-applet and see if it works with that. For the 28% issue, have a look at https://bugzilla.novell.com/show_bug.cgi?id=194049. If you are using a WPA connection and it works with YaST but not NM, the explanation could be found here: https://bugzilla.novell.com/show_bug.cgi?id=230684
I'm on OpenSuse 10.2 and I have this same problem always at start-up! My wifi card is an USB D-LINK DWL-G122(B1). I need to kill knetworkmanager and restart it so it is able to handle the wireless connection.
I have the same kind of problem with an MSI CB54G2 cardbus adpter (RT2500 chip) on a FujitsuSiemens Amilo A1650, running Kubuntu Feisty 32bit. KNetworkManager detects AP's, but pauses at 28% in the network connection progress bubble when connecting (either open or WEP, WPA not tried yet). Actually when it pauses so, the wifi link goes up but network connection doesn't work. If I "manually" issue a dhclient command at this point, the network connection goes up, but shuts down after a minute when knetworkmanager gives up attempting connection. Looks like it doesn't figure out it should start a dhcp request ?!?
Supporting comment #10. I am experiencing the very same problem, screens attached. Upon clicking on the SSID to connect to, I am asked for authentication specifics. Using WPA-Enterprise, TTLS, my username+password and a different anonymous identity, the correct CA I click connect. Then in the background the auth process completes successfully, but during that (may take a few seconds), the GUI pops back up asking for my credentials again. If I then do a command-line dhcpcd, I get an address and can use the network; i.e. authentication is successful, but the GUI doesn't wait for that to happen and instead immediately jumps back. See screenshots for pre-connection settings, and the intermediate state of iwconfig when the credentials widget re-pops up. The command-line session after waiting a few seconds is then: aragorn-mobile:/home/swinter # iwconfig lo no wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. eth1 IEEE 802.11g ESSID:"eduroam" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:A3:83:2D:AB Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:019F-F13D-89CA-EDC7-6A39-AF1B-4F68-4E73 Security mode:open Power Management:off Link Quality=76/100 Signal level=-53 dBm Noise level=-86 dBm Rx invalid nwid:0 Rx invalid crypt:41 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 aragorn-mobile:/home/swinter # dhcpcd eth1 aragorn-mobile:/home/swinter #
Created attachment 21171 [details] Initial configuration widget and state of iwconfig
Created attachment 21172 [details] re-popup of auth widget while iwconfig is in intermediate state (no encryption key assigned yet)
I have the same problem on Toshiba A100 with 3945ABG Intel Pro/Wireless connection. In fact to connect my network, I have to close the applet, turn off radio kill switch, launch again the knetworkmanager, choose my network on the list, enter my passphrase manualy, click on OK, wait 10 to 12 seconds, turn on the kill radio switch and then IT CONNECTS MY NETWORKS most of the time. If I try to connect another network with correct parameters it does'nt work anyway. On Yast, my configuration is : Intel Pro/Wireless 3945ABG mode [on plug] [external zone] (same problem in any configuration I've tryed all combination) [Shared] WPA2 AES with passphrase [energy ...] not checked Thanks for your support and help.
Hi all, After making updates, here is the news : On startup via an Intel Corporation 3945ABG Wireless board, knetworkmanager indicates "WPA" in place of "WPA2" for my network and cannot connect it (28%...) . So I have to QUIT and to RELAUNCH knetworkmanager. After that it detects correctly a WPA2 secutity protocol and after asking for the key, it connects the my network without trouble and works correctly. I hope this help... Thanks anyway.
I also have this problem both in SuSE 10.3 and all Sabayon Linux versions. I have an ipw3945 driver. I do not know if it is a driver problem. This my story: I have a wireless open network (no passfraces or hex keys or any of those). Knetworkmanager can see my network and shows that the signal strength is quite high. When I try to connect to that network however, it stacks at 28% and it doesn't connect. I try several times to no avail. Nothing. On the other hand trying: # su # /etc/init.d/netword restart # dhcpcd eth1 it connects nicely and painless. I have the same problem not only with SuSE 10.3 x86_64, but with Sabayon PE 1.1 x86_64 and all Sabayon previous editions. In the first boot it may manage to connect. If you do suspend in RAM (which by the way doesn't work in SuSE) or suspend to disk, then after resume it can't connect. Hope this helps.
i have the same problem - suse 10.3 x86 , also ipw3945 without encryption. dhclient eth1 works but knetowrkmanager refuses to make it
even without suspending the bug occurs - is there anything more I can do to describe the problem? any logs You want me to send?
I have this bug as well. I'm attaching the output of lshw and the contents of /var/log/syslog to this bug during an attempt to connect to a WEP protected wireles network.
Created attachment 24398 [details] Output of lshw and content of /var/log/syslog Output of lshw and content of /var/log/syslog during a connection attempt and until knetworkmanager had connected back to the wired network.
Hi fellows, the knetworkmanager doesn't run regularly. I haven't got a clue why not. Since a couple of months I cannot handle with ftp services within my wlan between Linux and Mac in either direction. Could there be a connection? It runs when I turn off (funny situation) the firewall of my Mac which is not in the DMZ, so without authentification it works. For what the hell is the knetwork-guy good? I would be thankful for a little help giving me back the use of my ftp stuff I just wanted to send a bug report. Could anybody make exactly that as an easy thing? I hope I did it right now, but I suppose it ends somewhere close to /dev/null. Eigentlich spreche ich Deutsch und kapiere denkbar wenig von dem anzuklickenden Kauderwelsch. Der einfache Knopf zum Versenden der Fehlermeldung zeigte nur eine weitere Fehlermeldung. The simple click to send the bug report showed another one with the useless information to look at bugs.kde.org that confused me even MUCH more than I could get any help. Is there anyone who could post this information to a place where it could give anyone a help who understands technical English? I don't hope any more to get any help out of this, just more confusion. I wouldn't dare to construct my homepage like this
*** Bug 147414 has been marked as a duplicate of this bug. ***
Hi folks, after having read the notes on the link I only can guess that others have got the same problem. Possibly my English isn't good enough, Starting with the question "What's a CC list?" (please do not answer) just more and more questions come up when reading that text. Sorry, but I don't see any help in your service, no idea how to post any text, no idea how to find an answer in the lasting lists of texts written possibly carefully. Am Samstag, 2008-06-14 16:04 schrieb owner@bugs.kde.org: [bugs.kde.org quoted mail]
Hi People.. I use kubuntu 8.04 hardy on an Acer extensa 5220 laptop with ndiswrapper (atheros 5007 eg) and have spent approx 2 days of numerous re-installs to get Knetworkmanager to work ok, I only got knetworkmanager to connect once. then it dumped me off :( I tried (and am now using) WPA2 AES, although TKIP behaviour seems the same. the 'bug' seems to be in the encryption negotiation, as knetworkmanager works easily without encryption here. - the applet has stuck at 28% and then 78% (or so) and eventually errors saying cannot connect etc etc - ironically i am now using gnome-network manager with good success by putting a symlink to nm-applet into the .kde/autostart directory and disabling autostart of knetworkmanager. gnome nm-applet always asks for my wpa password (which i remember) and manually enter it. for security reasons, this seems fine for me. strange that i had the same experience with Linux Mint 5 KDE (ce) but didnt try gnome's nm-applet. so it "seems" that networkmanager itself is good, its just the KDE implementation that has this problem for me. Ethernet works perfectly. of course it could just be me :) Mark_uk
Can confirm this bug.
There are lots of bug reports regarding problems with knetworkmanager on Kubuntu Hardy and Intrepid. See: https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/259278 and its duplicates. Users are having problems setting up static IP connections and connecting to encrypted networks. One workaround is to install the Gnome version of the applet for Network Manager, but this does not fix the underlying problem with Knetworkmanager.
I've read through all the comments above, and there are many possible causes. I have written the following troubleshooting guide for NetworkManager problems http://userbase.kde.org/NetworkManagement to help you to learn to isolate the cause of a problem. I am concentrating on Network Management in KDE 4 now, but this may be helpful to pin down any core bugs in KNetworkManager or new bugs in NM-kde4. I won't fix any cosmetic or 'missing feature' bugs in KDE 3 now though.
Closing, I don't think this will be useful in KNM 4.