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.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/355833
Title:
[Jaunty beta] KDE Connection Manager does not work for WEP
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
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 ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/355833/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
