On Tuesday 25 March 2008 10:54:56 Gavin Panella wrote: > Hi Fernando, > > A few of us have looked into this, but we can't find the change that > might have caused it. To be honest, we're unsure of what exactly > you're seeing. Please can you elaborate a bit? Perhaps paste some > examples of the messages before and after? > > Thanks, Gavin. I've attached a LP bug email report I received a few minutes. Have a look below: > -- > can't connect to hidden network -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786 GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by...
--- Begin Message ---
- To: ubuntu@xxxxxxxxxxxxx
- Subject: [Bug 50214] Re: can't connect to hidden network
- From: Alexander Sack <asac@xxxxxxxxxx>
- Date: Mon, 24 Mar 2008 21:03:48 -0000
- Authentication-results: mx.google.com; spf=pass (google.com: domain of bounces@xxxxxxxxxxxxx designates 91.189.90.139 as permitted sender) smtp.mail=bounces@xxxxxxxxxxxxx
- Delivered-to: ubuntu@xxxxxxxxxxxxx
- References: <20060618130307.13137.82029.malonedeb@xxxxxxxxxxxxxxxxxxx>
- Reply-to: Bug 50214 <50214@xxxxxxxxxxxxxxxxxx>
- Sender: bounces@xxxxxxxxxxxxx
please test the branch above. instructions on how to get it to your disc can be found at the branch url given to build you can just run $ debuild -b out of the branch directory. use dpkg -i to install the packages for testing. If you still cannot connect to hidden SSID, please attach your complete /var/log/syslog to the bug and state clearly if you could connect to hidden networks in gutsy. -- can't connect to hidden network https://bugs.launchpad.net/bugs/50214 You received this bug notification because you are a direct subscriber of the bug. Status in NetworkManager: Fix Released Status in Source Package "network-manager" in Ubuntu: Confirmed Status in Source Package "knetworkmanager" in Baltix GNU/Linux: Invalid Bug description: Since I installed dapper clean from CD, NM won't connect to my own hidden network., however it did before. The network was even in the list after a few seconds, the new feature of reverse mac scanning in 0.6.2. Now even if I use "connect to other network" and I enter everything in there, the connection won't be a success. Not hiding the SSID solves the problem immediately, just as manually connecting to the AP with iwconfig eth1 essid <mine> ...
--- End Message ---
Attachment:
signature.asc
Description: This is a digitally signed message part.
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)