KNetworkManager can't connect to non broadcasted networks
I'm not sure if it's my fault, specific site config, or NetworkManager issue. My WLAN is provided by an AP that doesn't broadcast the ESSID. Of course KNetworkManager can't see it until I select "Connect to other wireless network", and enter the data manually. But after I do that, I have two problems: a) KNM stats the connection, configures the correct WEP key (I can see it with iwconfig) but it does not associate with the ESSID (it shows "off/any", and KNM status stops at 28%), then I have to "iwconfig essid LocalWLAN" manually. After that KNM continues normal operation, loads dhclient, and then shows that the network is up. b) After my first successfull connection to this network, the information gets stored on KWallet, and I can see it there, (Options/Show Networks), but if I select the network and click OK, nothing happens (KNM doesn't try to connect to it), so I need to manually select "Connect to other wireless network" and re-enter manually my network data. After that I repeat the steps on (a), and everything works fine. I guess it's something with the fact that the AP isn't broadcasting the ESSID, since I have wireless at home and my desktop computer broadcasts it so KNM detects (although I can't connect because it's Ad-Hoc mode, bug #153232). Unfortunately I can't activate the ESSID broadcasting because my office AP doesn't have this feature (TrendNET). Any help on those issues? -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net
Am Montag, 24. April 2006 17:58 schrieb Mauricio Teixeira (netmask):
I'm not sure if it's my fault, specific site config, or NetworkManager issue.
My WLAN is provided by an AP that doesn't broadcast the ESSID. Of course KNetworkManager can't see it until I select "Connect to other wireless network", and enter the data manually. But after I do that, I have two problems:
a) KNM stats the connection, configures the correct WEP key (I can see it with iwconfig) but it does not associate with the ESSID (it shows "off/any", and KNM status stops at 28%), then I have to "iwconfig essid LocalWLAN" manually. After that KNM continues normal operation, loads dhclient, and then shows that the network is up.
b) After my first successfull connection to this network, the information gets stored on KWallet, and I can see it there, (Options/Show Networks), but if I select the network and click OK, nothing happens (KNM doesn't try to connect to it), so I need to manually select "Connect to other wireless network" and re-enter manually my network data. After that I repeat the steps on (a), and everything works fine.
I guess it's something with the fact that the AP isn't broadcasting the ESSID, since I have wireless at home and my desktop computer broadcasts it so KNM detects (although I can't connect because it's Ad-Hoc mode, bug #153232). Unfortunately I can't activate the ESSID broadcasting because my office AP doesn't have this feature (TrendNET).
Any help on those issues?
Known bug, should be fixed with RC2. See: https://bugzilla.novell.com/show_bug.cgi?id=166125 -- Üdvözlettel -- Mit freundlichen Grüssen, Marcel Hilzinger
Marcel Hilzinger wrote:
Known bug, should be fixed with RC2. See: https://bugzilla.novell.com/show_bug.cgi?id=166125
Access denied You are not authorized to access bug #166125. Maybe that's why I didn't find the ticket. :) Can someone shed a light on that, or even make the ticket public? -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net
"Mauricio Teixeira (netmask)"
I'm not sure if it's my fault, specific site config, or NetworkManager issue.
My WLAN is provided by an AP that doesn't broadcast the ESSID. Of course KNetworkManager can't see it until I select "Connect to other wireless network", and enter the data manually. But after I do that, I have two problems:
a) KNM stats the connection, configures the correct WEP key (I can see it with iwconfig) but it does not associate with the ESSID (it shows "off/any", and KNM status stops at 28%), then I have to "iwconfig essid LocalWLAN" manually. After that KNM continues normal operation, loads dhclient, and then shows that the network is up.
b) After my first successfull connection to this network, the information gets stored on KWallet, and I can see it there, (Options/Show Networks), but if I select the network and click OK, nothing happens (KNM doesn't try to connect to it), so I need to manually select "Connect to other wireless network" and re-enter manually my network data. After that I repeat the steps on (a), and everything works fine.
I guess it's something with the fact that the AP isn't broadcasting the ESSID, since I have wireless at home and my desktop computer broadcasts
I have knetworkmanager working with networks that do not broadcast the ESSID, so it should work in general.
it so KNM detects (although I can't connect because it's Ad-Hoc mode, bug #153232). Unfortunately I can't activate the ESSID broadcasting because my office AP doesn't have this feature (TrendNET).
Any help on those issues?
Reporting it in bugzilla might be an option, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas Jaeger wrote:
Reporting it in bugzilla might be an option,
Found a quite similar bug: https://bugzilla.novell.com/show_bug.cgi?id=168250 This still remains in RC2. -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net
participants (3)
-
Andreas Jaeger -
Marcel Hilzinger -
Mauricio Teixeira (netmask)