Thanks for the update!
--
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/876350
Title:
Can't connect to (unencrypted) ad-hoc network; iwconfig+dhclient
works; manually setting ESSID (which wasn't set by NM) fixes it --
Ralink RT2860 rt2800pci
Status in “network-manager” package in Ubuntu:
Fix Released
Bug description:
Since my upgrade to Oneiric I can't connect to the unencrypted Ad-hoc network
of my Freifunk community anymore. :(
If I use the (Unity) network-indicator the connection can't be established. I
have an ASUS EeePC 1000 with the Ralink RT2860 chip. With Oneiric my system
uses the rt2800pci kernel module. (I did no changes to the modules or the GRUB
command line etc..)
After digging around I found out the following.
1. During the connection process to the ad-hoc network with the ESSID
"www.freifunk-potsdam.de" I can see this three lines in my /var/log/syslog:
wpa_supplicant[2650]: Authentication with 00:00:00:00:00:00 timed out.
wpa_supplicant[2650]: Trying to associate with SSID 'www.freifunk-potsdam.de'
wpa_supplicant[2650]: Association request to the driver failed
2. I can establish a connection if I do it manually by:
$> iwconfig wlan0 mode ad-hoc
$> iwconfig wlan0 essid "www.freifunk-potsdam.de"
$> dhclient wlan0
3. During the connection process - initiated by clicking on my network in the
network-indicator - I can see that my wlan0 device hasn't set an ESSID. - So
for me its clear why I can't connect. Without a assigned ESSID I cen't get an
IP address. "iwconfig wlan0" during the connection process is:
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Ad-Hoc Frequency:2.412 GHz Cell: Not-Associated
Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
4. If I set the ESSID manually during the connection process -
initiated by clicking on my network in the network-indicator - by
"iwconfig wlan0 essid 'www.freifunk-potsdam.de'" the connection
becomes established and I get an IP address at the end.
To sum it up:
During the connection process for an ad-hoc network during the
network-indicator the ESSID is not set and so no connection can be established.
I would be happy if you can give me an hint for fixing this. :)
Thanks and best regards!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/876350/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
