| Summary: | can't establish connection with WEP security key | ||
|---|---|---|---|
| Product: | Network Management | Reporter: | Fahad Al-Saidi <Fahad.alsaidi> |
| Component: | Wireless | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | normal | CC: | greenrd, jamundso, lamarque, sebas |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
Do you still suffer from this problem with the network management plasmoid? (In reply to comment #1) > Do you still suffer from this problem with the network management plasmoid? Yes I am still suffering from it. I believe this is because the key is being converted from ascii to hex incorrectly. Try entering the key in hex (you can google for online tools to convert it to hex for you). It should work then. (In reply to comment #3) > I believe this is because the key is being converted from ascii to hex > incorrectly. Try entering the key in hex (you can google for online tools to > convert it to hex for you). It should work then. I tried your solution. Unfortunately, when I convert the password to hex, I couldn't enter it in input box. I wonder why nm-applet works better than plasma applet. I believe you need to change the "Key type" when entering a key in hex. (In reply to comment #5) > I believe you need to change the "Key type" when entering a key in hex. I did that but still I can't enter the hex key. Does the hex key have 0x in front of it? If so, remove the 0x - that's just a code saying "this is hex". (In reply to comment #7) > Does the hex key have 0x in front of it? If so, remove the 0x - that's just a > code saying "this is hex". No. It starts with 616 I believe I see this as well. When I try to manually enter my wireless info, this appears in .xsession-errors:
kcmshell(2601)/Network Management (ui) WirelessPreferences::WirelessPreferences: Could not find deviceUni or AP UNI in args: (QVariant(QString, "{010503cd-19ff-4343-9481-51bfec90e200}") )
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Seems to be a slight change between 1:kde-plasma-networkmanagement-0.9-0.47.20110323.fc15.1.i686 and 1:kde-plasma-networkmanagement-0.9-0.53.20110616git.nm09.fc15.i686 now I can manually add the connection, then activate it with "nmcli con up id Home". This may be a complete red herring however, in that it may be random bits backed by inadequate testing. That's more likely, considering there has been no other feedback here. Is this still happening? I did some changes in WEP code some weeks ago that could have solved this problem. |
Version: unspecified (using KDE 4.4.2) OS: Linux I am using Kubuntu 10.04 and I can't establish a wireless connection with WEP security method. I have installed ubuntu 10.04 in other machine and I can establish the connection without problem. this is information form lshw -C network command: description: Wireless interface product: PRO/Wireless 5100 AGN [Shiloh] Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@0000:03:00.0 logical name: wlan0 version: 00 serial: 00:26:c6:86:fa:0e width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlagn latency=0 multicast=yes wireless=IEEE 802.11abgn resources: irq:31 memory:f4200000-f4201fff Reproducible: Always Steps to Reproduce: try to connect to a wireless network with WEP security method