SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is anyone else having this problem in 11.2 under GNOME? I have gone through various steps, including enabling broadcast of the SSID of my access point, connecting successfully, then disabling broadcast of SSID, and then unable to reconnect. I am using NetworkManager to manage connections, and have read that there may be a bug in this version of NetworkManager for GNOME as well as the one for KDE. Anyone know of any workarounds for this, or any lines that may need to be added to configuration files, such as wpa_supplicant.conf?
Certainly plenty of evidence elsewhere (including still open bugzilla report) of the problem in KDE (and not just in Opensuse 11.2) but not seen it reported in Gnome; in fact another distro's support suggests using Gnome nm as a solution under Kde!
I encountered it under KDE as late as RC2 and got round it by unhiding the AP, using "manage networks" (not just adding the new connection) to set up the AP then it continued to work once the AP was re-hidden. But I've since seen reports of that not working. Not had chance to try out the final release version yet.
But all that relates to KDE - as I said, not seen it as an issue in Gnome.
A related observation on wicd / Ubuntu (9.04 or 9.10) / Compaq 6930p on one end and a Thomson SpeedTouch 585i V6 WLAN router on the other end. I am able to connect if the SSID is hidden, but it takes a long time (5 minutes), several manual connect attempts and (most strangely, at least to me) I need to go close to the router (i.e., to the same room; 3 meters / 10 feet). When the SSID is not hidden, the connection is established 'immediately' (most often established by the time the laptop has completed user login) and from a greater distance (different floor).
As WPA encryption is IMO necessary and sufficient, I have no problems to broadcast the SSID. But I have no explanation for this behavior.
I am also seeing this. I'm running openSuSE 11.2 with kde and I can't connect to hidden ssid's at all. Not even wicd will work, and that's what I use on my Slack box.
I also have this issue with KDE and my hidden SSID. Having done a lot of distro hopping in the past, it's not unique to SuSE by any means. In the end, my SSID has been left broadcasting itself in order to allow KDE to find and reconnect after the initial setup.
I had the same issue and another post said to run this it worked like a charm for me. I rebooted just to see and I was still able to connect ot my hidden ssid wireless.
I did it without having configured the wireless connection, I just ran the command and it built the wireless connection for me, I just added the wep password.
iwlist wlan0 scanning essid hiddenwireless
Just change the word hiddenwireless to your ssid name and you are good to go.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.