Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key

[Jeremy LaCroix]

I am using 64-bit Kubuntu Jaunty on my Gateway M-7315u laptop. My laptop does not require closed source drivers to function, and has functioned with every previous Kubuntu release I've tried. I am using the default Network Manager plasmoid that is added to the plasma panel.

My wireless network is not hidden. It's set up as WEP with a shared key. When I enter the information, the connection fails every time.

On another partition, I have Windows Vista set up which is able to connect to the wireless router every time with the same settings.

I have also tried disabling the mac address filtering of my router, but that doesn't fix anything. The mac address of my laptop is added to the allowed list on my router.

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

With all updates, this is still a problem.

[Asraniel (asraniel)]

Same here.
I also observed that kwallet stores a huge amount of password maps for my wireless network (13 in my case). The maps have names like that:
{2f11eec1-8f0f-4015-801e-a79ce239b6d1};802-11-wireless-security
 {2f11eec1-8f0f-4015-801e-a79ce239b6d1};802-1x
 {4f12200b-6148-499b-85e1-75758f423d38};802-11-wireless-security
 ...........

Probably something goes wrong when saving the WEP password?
I have a open WEP open system. When connecting i get asked at least 3 times for the WEP password (directly, sometimes i have 2 dialogs open at the same time), then the connection fails. Strangely enough usualy 1-2 minutes later suddendly i get the message that i have been connected to the network.

Last bug to fix for me and 9.04 is perfect!

[Asraniel (asraniel)]

And i would like to add that i use a 32bit system, with all upgrades up to today 20.3.09

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

64-bit here.

Asraniel wrote:
> And i would like to add that i use a 32bit system, with all upgrades up
> to today 20.3.09
>

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

I installed Wicd, and it connects to my wireless router with no issues whatsoever, so the problem is clearly a bug in KDE's network manager.

[Steve Langasek (vorlon)]

reassigning to the plasma-widget-network-manager package.

[Aurélien Gâteau (agateau)]

I experienced the same problem. I have an access point with an ascii wep key. I was able to make it run by entering the key in hexadecimal rather than in ascii. Can you try to do so and see if it fixes the problem?

If you need help converting your key to hex, here is a small Python trick I used:

- From the command line, start Python:
python

- Enter your key:
key="YourAsciiKey"

- Enter this:
"".join(["%02x" % ord(x) for x in key])

The hex key should be displayed.

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

My comment doesn't seem to have posted. How odd.

Anyway, I may not understand what you're asking me to do, because my router only has two options. I can either enter a passphrase of my own choosing, or I can use 2wire's hex key. (It doesn't allow me to make up my own hex key in the router). Weird, I know, but it's what AT&T forces me to use to connect.

[Aurélien Gâteau (agateau)]

I was not asking to enter the hex key in your router, but in the dialog shown by plasma-widget-network-manager. When I entered the wep key as hex instead of ascii plasma-widget-network-manager connected successfully.

[Javier Jardón (jjardon)]

I have the same problem.

As Aurélien Gâteau, I was able to make it run by entering the key in hexadecimal rather than in ascii. (see https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/339313/comments/7)

In Ubuntu (Gnome) works without problems

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

I used the hex key as you instructed, and still the problem remains. It fails to connect.

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

I got a different router, and I set up a hex key instead of a pass phrase. It still has the same problem. The only difference now is that if I keep trying between 10-25 times, I may possibly get connected.

[Julien (julien-grossholtz-gmail-deactivatedaccount)]

Most of the time I'm able to connect, but it takes some time.

I click on the network I want on the plasmoid and them the small dialog appears :"Enter network connection secrets". I Just have to click on cancel many times because when a dialog is closed an other appears. Typing the passphrase at this point is useless.

After this I click again on my access point essid, the "big" (add network connection) dialog appears and I can type my password, when I click OK, the small dialog appears twice, you have to enter the passphrase on the dialog which appears first (the one behind the other). And... there is a crash : The application KDE Daemon (kded4) crashed and caused the signal 11 (SIGSEGV). Sorry I don't have the backtrace, if there is a need I guess I should install some debug packages ?

After this you "just" have to restart the procedure described in the paragraph above and It will work.

If you what to copy/paste the passphrase in the procedure, be careful after the crash the text you get when pasting is hum... strange.

Don't ask my how I find it...

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

I can confirm the behavior that Julien posted is what happens for me. However, I usually give up before going through all of that. The few times I have went through that entire procedure it has worked.

[Steve Langasek (vorlon)]

Documented at <https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes#Kubuntu Network Management applet does not connect to WPA2 networks>:

The Network Management applet in Kubuntu does not connect to WPA 2 network or some VPN setups. You can use knetworkmanager (available on the DVD) or network-manager-gnome as a workaround. Bug 339313

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

I filed this bug for WEP, not WPA2. This should work in the final
release, especially since it worked before. In my tests, the new network
manager can't connect to ANYTHING that takes a password, it's completely
useless in every regard. I hope that it's removed at the last minute
altogether or fixed, having a non-working network manager by default in
a stable release doesn't strike me as making sense.

Steve Langasek wrote:
> Documented at
> <https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes#Kubuntu Network
> Management applet does not connect to WPA2 networks>:
>
> The Network Management applet in Kubuntu does not connect to WPA 2
> network or some VPN setups. You can use knetworkmanager (available on
> the DVD) or network-manager-gnome as a workaround. Bug 339313
>
> ** Changed in: ubuntu-release-notes
> Status: New => Fix Released
>

[Chris (firewithextrafire)]

I can also confirm the behaviour that Julien posted: it is still an issue even after release. Additionally, it seems that an extra network connection appears on the list of networks each time you do this, and it is completely impossible to use an existing listed connection. This of course makes "Connect Automatically" useless.

Using Kubuntu Jaunty, open network with WEP key. Same whether you use the passphrase or the 26 character hex equivalent.

[Ruairi (ruairi-glenn)]

Sort of same here.

Fresh install of kubuntu 9.04 with a belkin usb wifi dongle based on rtl8187.

Using wep with an ascii key

System picked it up ok, could see wifi networks ok. But when configuring the only wep password options where hex and passphrase, no option for ascii. Neither hex or passphrase worked.

To cut a long story short I had to sudo /etc/network/interfaces and config in there.

[Felix (apoapo)]

Do you have kwalletd running? That fixed it for me. I disabled the kwallet thing a few months ago.. after enabling it again, all passwords are stored in there for my wireless connections.

[Nicolas Réau (kolia)]

Same problem here with my ascii key on a fresh Kubuntu 9.04 upgrade. I fixed it with Aurelien's trick (see comment #9), by converting my ascii key in hexadecimal and entering it this way.

[James L R (jlrose)]

Ok, most of the people here seem to be complaining about WEP, not WPA. I actually do have a WPA2 gateway that I can't connect to. The plasmoid displays no reaction when I try to click on my gateway. Is there a resolution planned for this? Or will I have to use lame work-arounds until the October release?

[Hezekiah Carty (hez)]

apo's fix (comment 21) works for me from the LiveCD (actually LiveUSB) kubuntu final Jaunty release. If I start kwalletd first, then select the network and enter the credentials I am able to connect. I did have to enter the password twice (once on the "long" dialog and once on the "short" dialog), but from there it worked well for me.

Is this something which could be easily fixed, either with updated errata or (preferably) an updated release ISO? This seems to be a very significant issue which could turn a lot of people off from KDE and kubuntu.

[Marios Karaoulis (marios-hellas-23)]

Same here. I can't connect with wep (both ascII and hex). The solution is to remove completly every network-manager and install wicd.
Really it's really annoying how this bug is still here. I am begging thinking switching to opensuse

[FreeMinded (pascal-planetmages)]

Isn't this bug a dupplicate of this here https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/348275

Anyhow, still having this very annoying issue on my ThinkPad X40. I hope it's getting fixed sometime soon.

[Javier Jardón (jjardon)]

James, (https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/339313/comments/23)

see bug 348275 for that

[TubaSoldier (tubasoldier)]

I just downloaded the final release of Jaunty Jackalope. I left Kubuntu nearly a year ago because of ridiculous bugs like this and I see nothing has changed. There should not have to be a workaround installed on a fresh install of Kubuntu. If it doesn't work then dont' put it in.

Thanks for concreting my decision to no longer use this distro.

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

Tuba Soldier,

While Kubuntu will continue to be my main distribution, I have to agree
with your sentiments. There is never an excuse for a regression, and
this all worked fine in 8.10.

[C.J. Steele (cjsteele)]

the kernel-based supplicant is junk in Jaunty. Try wicd, that's allowed me to connect to whatever AP I want.

[dbneeley (dbneeley)]

I attempted to get the "Network manager" plasmoid to work with my wep shared key ASCII passphrase and, like the others here, it would not despite repeated efforts. I then "nuked" the Kubuntu install and installed Ubuntu Jaunty--the network settings worked with the Live CD, so I installed it on the hard drive and...it no longer could be set up to work there,either.

Finally, I reinstalled Kubuntu, plugged into my router and downloaded WICD--which worked the first time without problems. WICD also automatically recognized several of the settings that the Kubuntu Network Manager did not.

This has been such a long-standing problem through multiple releases, why not replace the network manager with WICD--at least until you folks get a clue about what is going wrong with network manager?

Shipping code that is known to be broken in a system which is ostensibly designed for new Linux users to find easy to use is disgraceful, frankly, when there is at least one existing solution that seems to be better.

An alternative might be to have an installation choice to install one or the other so no one would have to search on a wired connection for the solution.

[Jonathan Riddell (jr)]

Please try plasma-widget-network-manager from kubuntu-experimental PPA

deb http://ppa.launchpad.net/kubuntu-experimental/ppa/ubuntu jaunty main

[Juan Luis Cano (astrojuanlu)]

This bug has been affecting me since Kubuntu Intrepid. I solved it downloading the network-manager-gnome http://packages.ubuntu.com/jaunty/network-manager-gnome), which works nicely. However, as I hadn't Internet, I had to download all the packages (and its dependencies, after trying again and again ¬¬) from Windows. I hope it works for you, but I think this bug should be corrected soon.

By the way, when I selected "ascii" instead of "passphrase", typed my ascii key, clicked OK and OK and went back, "passphrase" was selected. I have tried several times to select "ascii", but it changes automatically. Maybe this can be the problem?

[Chris (firewithextrafire)]

plasma-widget-network-manager from kubuntu-experimental behaves a LOT better. On initially connecting, I entered the WEP key and checked "connect automatically", and it asked for the connection details a second time. Patiently I added them in, and lo and behold, connectivity. It also connects automatically on logging in, which is nice.

So not 100% ideal behaviour, but FAR better than the out-of-the-box setup.

[Juan Luis Cano (astrojuanlu)]

Jonathan Riddell's solution <strong>worked!</strong>

I added his line to my repositories, updated my plasma-widget-network-manager... And now I'm connected! :D

Nevertheless, I'd like to point two things:
1º. I had to type my ascii key... as an hex key. That was boring.
2º. I first typed it wrongly, and I wasn't noticed. I expected "You fool! Write your password correctly!" or sth like that.

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

The updated package worked for me too, but not *exactly* as expected.

1.) I updated the package and then rebooted.
2.) I then clicked on the network manager and then clicked on my network
3.) I entered in all of the secret info and clicked okay
4.) It then said that it was connecting
5.) Another window came up asking for my secret info again
6.) It didn't remember anything I typed so I typed it all again
7.) After I typed my secret info, the same window came up asking for the
details again.
8.) Before I was able to enter in the details, I got a message saying
that I was connected

In my opinion, the goal now is to make it only ask for the wireless info
ONCE. When the second and subsequent windows come up asking for the
data, it makes the user think they entered in the data wrong, even
though they didn't. At least I'm connected though!

Juanlu001 wrote:
> Jonathan Riddell's solution <strong>worked!</strong>
>
> I added his line to my repositories, updated my plasma-widget-network-
> manager... And now I'm connected! :D
>
> Nevertheless, I'd like to point two things:
> 1º. I had to type my ascii key... as an hex key. That was boring.
> 2º. I first typed it wrongly, and I wasn't noticed. I expected "You fool! Write your password correctly!" or sth like that.
>

[Felix (apoapo)]

I think you are suffering from the kwallet-disabled bug mentioned above. Try to install and enable your Kwalletmanager (kwalletd). The plasma-widget-networkmanager should then use the kwallet as a password storage.

[Marios Karaoulis (marios-hellas-23)]

Please help. After using for several days wicd, i just entered one wired connection through wicd.
After this i cant'connect to any wireless connection. It shows signal but no connection
I reinstalled it, remove it and install gnome-network-manger, etc but i can't connect to any wireless conection.
I tried it for both wep and wpa wireless.
any ideas?

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

Thank you, but I prefer not to use knetworkmanager, as it drives me
nuts. I prefer to have my passwords saved without asking for a master
password each time.

apo wrote:
> I think you are suffering from the kwallet-disabled bug mentioned above.
> Try to install and enable your Kwalletmanager (kwalletd). The plasma-
> widget-networkmanager should then use the kwallet as a password storage.
>

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

In my last comment I said "I prefer not to use knetworkmanager" but I
meant to say "I prefer not to use kwalletmanager". When I use
kwalletmanager it asks for a master password each time and I prefer not
to be bothered with a master password or otherwise. Sorry for the confusion.

[Scott Kitterman (kitterman)]

Fixed in plasma-widget-networkmanagement 0.1~svn1011298-0ubuntu2 (package was renamed in karmic).

[humufr (humufr-deactivatedaccount)]

Scott I am not so sure. I still unable to connect on a wep network. I have to use nm-applet to do it. Perhaps look toward pardus, their plasmoid doesn't have this problem.

[humufr (humufr-deactivatedaccount)]

I forgot to say that I am using karmic updated today

[dyug (dyug)]

Update 2009-09-06 from Kubuntu Backports https://launchpad.net/~kubuntu-ppa/+archive/backports version plasma-widget-networkmanagement - 0.1~svn1017841-0ubuntu2~jaunty3

Not connect WEP Shared key

previous version 0.1~svn1002787~jaunty1~ppa2 - worked

[jc1985 (jc1985)]

I've had the same problem (working 1002787 and not working 1017841) but with a WPA2 key : I deleted the previously configured networks, and then it worked

[dyug (dyug)]

Delete previously configured networks, add new connetions - not worked.

[shadetree (pde-gotsky)]

New testing Kubuntu, like everything but this same WEP bug:-( Decided to test Ubuntu, everything worked the first time:-) But I still like the KDE feel.

[BryanLawrence (b-n-lawrence)]

I have two versions of kubuntu on my laptop. 8.04 which works, and the other one. The other one was on 9.04 jaunty, which had this bug, just upgrade to karmic alpha 5. Still doesn't work out of the box, since I can't get my ascii wep key recognised ... so it's not invalid yet ...

[Mario Theodoridis (mario-schmut)]

Just installed karmic alpha 6 and had to dig out a network cable because i use a 40 bit WEP pass phrase. This is definitely not fixed. Also i'm not sure there is such a thing as 64 bit WEP hex key, but i may have missed something.

[Thomas Hellermann (izarael)]

I use Kubuntu Karmic and for me it's definately not fixed. My university uses a WEP protected nework and I'm unable to connect. WPA2 works without problems.

[Ryan Novosielski (novosirj)]

What version are people using on Jaunty or Karmic? I have no problem with it since installing this version:

ii network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 network management framework daemon
ii network-manager-gnome 0.7.1~rc4.1-0ubuntu2 network management framework (GNOME frontend
rc network-manager-kde 1:0.7svn864988-0ubuntu8 KDE systray applet for controlling NetworkMa
ii network-manager-vpnc 0.7.1~rc4.20090316+bzr21-0ubuntu2 network management framework (VPNC plugin)
ii plasma-widget-network-manager 0.1~svn1017841-0ubuntu2~jaunty4 Network Management widget for KDE4 Plasma

However, I've not gotten hidden ESSID + WPA Enterprise working yet... I haven't tried that hard though.

I have a 128-bit ASCII WEP key. Since the ASCII option went away (not passphrase, which is different), I just enter the HEX version of that key. Works fine.

[Tom Shaw (firephoto)]

This is not fixed, yesterday's 9-23 desktop-i386 install Kubuntu Karmic. WEP 128 bit passprase doesn't work, not as shared, not as open, not with single quotes enclosing, not with double quotes enclosing the passphrase. This is getting a bit ridiculous, give us a permanent fix or please include the Wicd debs on the default install so we can have working and reliable network management.

[humufr (humufr-deactivatedaccount)]

Same here I do think there are a problem for knetworkmanager to communicate with wallet because the password is never remember. Another solution than wicd is to kill knetworkmanager and use nm-applet (gnome version are working fine it's just the kubuntu interface the problem not network-manager).

[Asraniel (asraniel)]

in that case can't you use the option of the inferface to not use kwallet for the password? it can save it in it's own file, perhaps this can be used as a workaround.

[BryanLawrence (b-n-lawrence)]

@Ryan: I could maybe work out the hex equivalent of my ascii key, but that defeats the purpose of having an ascii key at all.

I appreciate we live in kde4-land now, not kde3-land, but it all worked fine in kde3-land, so this is a major major regression
at the moment. Like i said earlier, between this and bluetooth problems (now fixed I think), I'm still stuck on kubuntu 8.04.

[Ryan Novosielski (novosirj)]

ASCII passphrase is not the same as 40 or 128-bit ASCII WEP though. Not
sure which you are trying to use. For me, my ASCII 128-bit option went
away. Why? I don't know, but I now type the HEX PW. If you are using an
actual ASCII passphrase and THAT isn't working, that's another matter.

...... Original Message .......
On Fri, 25 Sep 2009 07:41:50 +0000 "BryanLawrence" <email address hidden>
wrote:
>@Ryan: I could maybe work out the hex equivalent of my ascii key, but
>that defeats the purpose of having an ascii key at all.
>
>I appreciate we live in kde4-land now, not kde3-land, but it all worked
fine in kde3-land, so this is a major major regression
>at the moment. Like i said earlier, between this and bluetooth problems
(now fixed I think), I'm still stuck on kubuntu 8.04.
>
>--
>Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
>https://bugs.launchpad.net/bugs/339313
>You received this bug notification because you are a direct subscriber
>of the bug.

[Störm Poorun (subs-olan)]

This bug is still present in Kubuntu Karmic 9.10 beta - plasma-widget-networkmanagement package does not offer the user an option to enter a 40 or 128-bit ASCII WEP key (which is not the same as a passphrase). Using the hex workaround is not realistic (nor reasonable) for the majority of users.

[Störm Poorun (subs-olan)]

Re: Comment #82 - I agree there is a workaround, but that doesn't mean the software works as expected.

The issue is not whether the network works by using a workaround, but that as the default network management package in Kubuntu the software MUST offer the user the option to enter the WEP ASCII key when Kubuntu 9.10 is released or lots of users will be floundering with effectively no internet access, unable to a) figure out what's wrong, b) get internet access to find out how to fix it, and c) may be unable to implement the workaround easily.

[mlx (myxal-mxl)]

#88,#89: !default - I installed Karmic beta last week and didn't get the plasma widget. The default seems to have been changed to knetworkmanager (the systray utility used back in 8.04).That said, I haven't checked if it works with said WEP key.

[Störm Poorun (subs-olan)]

Can we upgrade this to critical? It would effectively be an internet blocker for many users.

[Störm Poorun (subs-olan)]

See upstream bug: https://bugs.kde.org/show_bug.cgi?id=199786

It seems that a reliable algorithm hash isn't available to convert the 40 and 104bit ASCII WEP keys to HEX.

128bit keys are available, and implemented already (pass phrase?).

Though, does anyone know why other OSes (and Gnome(?)) manage this?

I would argue that the previous capability, even if not 100%, is worth implementation (albeit with a warning that it may not work).

Furthermore, when a user attempts to enter a 40 or 104bit ASCII key I propose that they should get a warning saying ASCII keys may not work, there should then be an attempt at a conversion to HEX, and if that fails, they should receive a warning explaining the situation and how to obtain and enter a HEX key. At minimum this warning would prevent people from flailing around (especially with no internet connection) trying to find out what's 'broken' with their systems.

[Ryan Novosielski (novosirj)]

There is definitely a reliable method available, as 'iwconfig <dev> enc s:<ascii key>' works every time. In fact, I usually do this on the machine and read the hex key from iwconfig's output to come up with the hex key I need for these new incarnations of the GUI. It's definitely not plug-and-play but works once saved. But if iwconfig can handle it, why can't these GUI's?

 ..... Original Message .......
On Mon, 12 Oct 2009 23:35:11 +0000 "Störm Poorun" <email address hidden> wrote:
>See upstream bug: https://bugs.kde.org/show_bug.cgi?id=199786
>
>It seems that a reliable algorithm hash isn't available to convert the
>40 and 104bit ASCII WEP keys to HEX.
>
>128bit keys are available, and implemented already (pass phrase?).
>
>Though, does anyone know why other OSes (and Gnome(?)) manage this?
>
>I would argue that the previous capability, even if not 100%, is worth
>implementation (albeit with a warning that it may not work).
>
>Furthermore, when a user attempts to enter a 40 or 104bit ASCII key I
>propose that they should get a warning saying ASCII keys may not work,
>there should then be an attempt at a conversion to HEX, and if that
>fails, they should receive a warning explaining the situation and how to
>obtain and enter a HEX key. At minimum this warning would prevent people
>from flailing around (especially with no internet connection) trying to
>find out what's 'broken' with their systems.
>
>
>
>** Bug watch added: KDE Bug Tracking System #199786
> http://bugs.kde.org/show_bug.cgi?id=199786
>
>--
>Kubuntu Jaunty: Cannot Connect To Wireless Network with WEP shared key
>https://bugs.launchpad.net/bugs/339313
>You received this bug notification because you are a direct subscriber
>of the bug.

[Asraniel (asraniel)]

actually there is really no reliable method available. that it works for you is pure luck. depending on the AP manufacturer, another hash is used. So it can very well be that most of the APs sold in you town come from the same manufacturer have the same hash. But for others it won't work.
By the way, windows has the exact same problem. Their solution is to provide a hash anyway, but then it magicaly fails on certain wireless networks and you have no idea why.
Not sure whatthe best thing to do is, i think there will be less problems if there is no hash provided for 64bit wep (which is depreciated anyway).

[Jonathan Riddell (jr)]

re-closing this bug, the original problem is solved. I have opened bug 453260 for the ascii key problem.

[Ryan Novosielski (novosirj)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No, actually, I'm pretty certain now that you are not correct. I believe
you are thinking of ASCII passphrase, not ASCII key. Converting ASCII
keys to HEX and back again is merely HEX representations of ASCII
characters. I don't care what sort of router or card you're using,
ABCDEFG in ASCII is 41424344454647 in HEX.

Asraniel wrote:
> actually there is really no reliable method available. that it works for you is pure luck. depending on the AP manufacturer, another hash is used. So it can very well be that most of the APs sold in you town come from the same manufacturer have the same hash. But for others it won't work.
> By the way, windows has the exact same problem. Their solution is to provide a hash anyway, but then it magicaly fails on certain wireless networks and you have no idea why.
> Not sure whatthe best thing to do is, i think there will be less problems if there is no hash provided for 64bit wep (which is depreciated anyway).
>

- --
 ---- _ _ _ _ ___ _ _ _
 |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II
 |$&| |__| | | |__/ | \| _| |<email address hidden> - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrZThYACgkQmb+gadEcsb6GuACgk/aEjUF6xkrVKqJJyF6Xi2k1
Zo4An0RmhI5L7SYEYEyBXi0yclW2RCes
=TQhI
-----END PGP SIGNATURE-----

[Adric Riedel (adric-riedel)]

Using Kubuntu Karmic 64bit; up to date... I WAS using the KDE network-manager plasmoid without problem before the upgrade; now I am unable to actually connect to the network even though I can see it. On the other hand, I just installed and activated nm-applet and it worked as expected and as the kde-network-manager plasmoid used to.

Therefore, the problem is with either the kde-network-manager plasmoid or the Kubuntu version thereof.

[Lukos (luke-briner)]

Not sure how many of the reported problems are related but after I REMOVED all the existing connections and created them again, I have had no problems at all. Before I did this, when I clicked on the name of the network in the GUI, nothing happened at all, it didn't even try and connect. Not sure if it is possible but the upgrade could remove all the old connections or at least you need to look at why it is having problems with the saved data.

[Sigra (u-admin-sjrlinux-com)]

just downloaded kubuntu 9.10 and installed a fresh copy on desktop and dual boot on netbook. the wired works great from both. the wireless is a bust. it shows 4 wireless in the area. and on ours when you click it and try connect it shows it correct that wpa personal. but when you type in the password and try to connect. it dont even try. switched back to ubuntu after trying ever combination i could. once this bug is fixed so a fresh install works on wireless we will be switching back. I am sure can go in here and type in this and that and make it work or add wicd. but I prefer to install OS that is ready to run without having to get technical.

[humufr (humufr-deactivatedaccount)]

Still not working and karmic is out. I just download a new version for my brother in law but because of this problem it was an ubuntu one not a kubuntu. Well done guys... So I know that using nm-applet is working fine but it's just a workaround and it's not working with a live cd.

[paddy (paddy-piments)]

Why is this bug closed ?!

I did apt-get update and apt-get upgrade just this afternoon yet I still have a pile of shit NM hemorrhoid thing that can not connect.

If the problem is known and solved , get an update out. I don't want to wait until the next major buntu release to use my computer.

This is now damn near one year since this was reported and something a basic as getting your hemorrhoid widgets to accept a WEP key is still not working? Pathetic.

There's not much point in a fix if there's no update.

This sort of thing makes me despair of linux ever getting it together.

[Mike Weaver (miweaver)]

I realise that this is now an older bug but it appears to be the same in the latest Ubuntu 10.04. Like other correspondents, I was unable to log into (authenticate) WEP networks but was able to log into WPA-PSK networks. I have tried unloading Network Manager and loading wicd - same problem. However, I think i have found the problem. It is alluded to by Ryan on here on 17 Oct 2009.

I set up a spare wireless AP today with the same parameters as the one at work that I was unable to authenticate to - SSID SNAP WEP authentication password 12345. I still had the same problem - was unable to authenticate. However, in a blinding flash, I remembered that when I set the password - 12345 - on the wireless AP, it gave me four 10 digit hex KEYS (my caps). I changed the key on the WEP details for the SNAP network to the first key - E235485511. It worked!!! I then checked on-line for a 'WEP key generator' and found that the pass-phrase 12345 would ALWAYS generate the self-same keys. So this seems to be the problem - the WEP networks actually require the Hex key that is generated when you enter a 'normal' pass-phrase. In my case, it wanted key #1 - the one I have shown above. Now I accept that I may have been staring this in the face for a while as WICD (and Network Manager) actually asks for the WEP key and I - and I suspect many other people with the same problem - have been entering the WEP "pass-phrase" instead. BUT - my home WPA-PSK network also asks for the 'pre-shared key' and when I type in my everyday common English passphrase - it works!! There is clearly no consistency here! For WEP, I MUST NOT type in the normal ASCII passphrase, but for WPA I MUST type in the normal ASCII passphrase........

This is the sort of error that will completely throw people. OK, many - most? - wireless networks today probably use WPA but WEP is still around. BTW, I disagree with the statement read here that the 'hash will vary by AP manufacturer'. I suspect that the keys generated for a specific passphrase will always be the same. Hopefully, this CAN be easily fixed.

[Aurélien Gâteau (agateau)]

Mike, did you select "Key" or "Passphrase"

[Aurélien Gâteau (agateau)]

Mike: in "Key type", did you select "Passphrase" or "Hex or Ascii Key"? I think you need "Hex or Ascii Key" (see attached screenshot)

[Mike Weaver (miweaver)]

Thanks Aurelien for the comments. There is more to this sad tale......! I bought my laptop to work on Monday after the successful authentication at home on my 'pseudo' work (WEP) network - and it STILL would not authenticate! Then I remembered that I had a Linksys USB wireless NIC at home, so I decided to give that a try. It shows up as wlan0, and after a couple of (small) changes in the configuration at home, it successfully connected to my WPA network. As it is 11b/g, of course, it is also faster than the embedded IPW2100, so a bonus. That proved that it worked as a device - ie driver; supplicant; manager chain was all good. I bought my laptop in to work this morning - plugged in the USB and it immediately connected to the WEP network. Success at last! So it looks as though there is something very odd about the combination of (work) network authentication and the ipw2100 driver since everything works with the Linksys USB device.

Now to answer your question - and first with a question? Where did you get your included screenshot from? Which program / command gives you that dialog? I have never seen such a screen. Recall that I am now using Wicd 1.7.0 and NOT Network manager. In that application, there is a 'Properties' option that offers WEP(Passphrase) and WEP(Hex[0-9/A-F]). I presume I have connected with the WEP(Hex...) option where I have entered key#1 E235485511. However, I see that I have ALSO entered the passphrase - 12345 - in the WEP(Passphrase) option. If I try to remove either, I get a warning dialog that the "network requires encryption to be enabled".

I'll send a couple of screenshots that might show what I mean. Thanks again for taking the time to respond.

[Mike Weaver (miweaver)]

See attached screenshots. Thanks

[Aurélien Gâteau (agateau)]

My screenshots come from the Plasma Network Management widget, which is the product this bug report is about. I am afraid you are not in the best place to ask for help regarding wicd.

[Alex Valavanis (valavanisalex)]

Jaunty reached end-of-life on 23 October 2010. The bug is marked as "invalid" in later versions of Ubuntu

[Jānis Kangarooo (kangarooo)]

THIS affects 10.04 LTS

I set in router
WEP
Shared
ASCII
passw is word 13 chars long for example: 13chrpassword
With android no problem.
BUT ubuntu 10.04.03 LTS Netbook remix cant connect.
i can connect while in Router i set WEP Open or Mixed witch means its both Open and Shared but cant connect from ubuntu while just Shared.

I found in internet that some kernel update made it not work anymore.
https://www.google.com/search?client=ubuntu&channel=fs&q=ubuntu+wep+shared+ascii+13+cant&ie=utf-8&oe=utf-8

[Jānis Kangarooo (kangarooo)]

UPDATE.
I was able to connect. I did something whats nowhere written to be logical to do.
In one of links from my previos post in google https://www.google.com/search?client=ubuntu&channel=fs&q=ubuntu+wep+shared+ascii+13+cant&ie=utf-8&oe=utf-8
in page https://bugzilla.redhat.com/show_bug.cgi?id=444847
theres given page http://www.corecoding.com/utilities/wep2hex.php
to use it for some reason to transcode your ascii (normal word 5 or 13 char long) pass to hex
i tryd and it gives 2 hexes
1.) KEYs for non apple computers/networks:
(104/128bit) hashed key:

2.) KEYs for apple networks or if the AP is a airport express:
(40/64bit) key:

since im on Ubuntu i tryd 1st pasting in NM Wifi Connection as WEP 40/128-bit key & then WEP 128-bit Passphrase
both didnt work.

I just now wanted to try also 2nd option but that shouldnt work couse its for apple comps.. BUT it worked as WEP 40/128-bit key

Why?

So maybe this helps making solution?

Problem im having i made Wifi router and Repeater to work. My Repeater works only using none or WEP security. Using Open or Mixed i cant connect from Ubuntu to router. Im now trying on wifi and repeater using wep shared and android works great and btw i fount that using usb and tethering then Ubuntu auto-recognized it as Lan.
But using Shared makes all work better but ubuntu only connects to Wifi but not to repeater now using shared.
Strange things.

[Jānis Kangarooo (kangarooo)]

UPDATE- I have TL-WR340G router my repeater TL-WA500G set up to work BUT works in Windows but not in Ubuntu. For 1/2 year ive tried different settings and setups. So now i have HEX 128bit open WEP key (couse my repeater has only wep repeating or no key repeating function) and repeater has same HEX 128bit open WEP. Android was allways even with noncopatible options able to connect. Like Hex key shared repeated open but on Android i put ASCII. Now i just tried on WIndows and its working. So theres big problem in Ubuntu- cant connect no way to repeater.