On Sun, Jan 17, 2010 at 02:18:55AM -0600, David C. Rankin wrote:
On 01/09/2010 12:16 PM, Josef Wolf wrote:
With 11.2, I could not activate wlan on my laptop. After lots of googling, I found that following commands do the trick:
zypper remove networkmanager-kde4 zypper install networkmanager-gnome gtk-update-icon-cache -f /usr/share/icons/hicolor nm-appet &
Now the problem is that there seem to be no way to put nm-applet into the panel so that it starts automatically.
Any hints how to start nm-applet automatically?
Unless you have a compelling reason not to, I would suggest using yast to configure your wireless card to use "Traditional ifup" method of activation and set the card to start "At Boot".
Thanks for your suggestion, David! Actually, this would have been one of my next questions.
I have used network manager for a couple of years and about nine months ago, I just went back to traditional ifup and I am sorry I didn't do it sooner. If you have many (known) wireless APs to connect to, that can be handled in your config files.
Ah, I was not aware of that. I thought NM is the only way to handle multiple AP's. Besides, I also got the impression that NM is the "future" and that the traditional way would be deprecated. Can you give me an example how to properly configure multiple (known) AP's so that they can be changed on-the-fly?
If you have many (unknown) wireless APs to connect to each day -- then staying with nm may be your best bet.
I don't have a use-case for that (yet). But even if there would be one, that could also be handled by traditional config files, I guess.
Traditional ifup solves many of the nm problems, but the biggest problem it solved for me was the problem of not having an IP until logon. It was always a pain having a box running, but not being able to access it via ssh, etc.. until someone physically started a desktop.
Yes, that's an issue for me too.
Configuring the wireless connection from the cli is actually much simpler than relying on the nm magic.
Since I configure my systems automatically by a system similar to cfengine, not only the NM magic, but all the "modern" ways of configuring the system via GUI are a problem for me :-((
Just a simple 'iwlist wlan0 scan' or 'wlanconfig wlan0 scan' (or the equivalent for your card) and you have the list of available APs with much more information than you get from looking at the nm screen. Then just follow up with iwconfig to associate to the AP of your choice and use dhclient or dhcpcd to get an IP address and your done.
Yeah, but where do I go from here? Google finds me lots of contradictory information about wlan configuration. I guess I have to use wpa-supplicant for WPA2-AES? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org