[Jaunty beta] KDE Connection Manager does not work for WEP

[VaclavPe]

I can not connect to my network with KDE Network manager.

If I run following commands from command line, it works well:
> sudo iwconfig eth1 essid VPLan
> sudo iwconfig eth1 key restricted dead-beef-00
> sudo ifconfig eth1 192.168.1.99 up
> sudo route add default gw 192.168.1.254
> echo nameserver 192.168.1.254 > /etc/resolv.conf

I use WEP with hexadecimal key.

In fact, I am filling this bug from system configured that way. "Network management" icon is anyway not aware that I have connection and says "eth1: Not connected".

If KDE Network Manager is not able to set this network, where should I put it to have the configuration permanent after each boot of the system ?

[Mathieu Trudel-Lapierre (cyphermox)]

Thank you for reporting this bug to Ubuntu 9.04 reached EOL on October 23, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Ubuntu 10.04 and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

[VaclavPe (vaclavpe)]

Hi Mathieu,

you can happily close this bug as there is probably nobody who is still affected with this bug after almost 3 years.

I know that this kind of support is free and based on willingness of people. But this is still a waste of your time. If there was nobody from april 2009 who could have a look at this problem, now it is really too late. I am sorry to say it.

Anyway, thank you for your information.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]