Comment 201 for bug 50214

Alexander,

thanks. I wasn't sure it was correct either - it seemed to be showing
AP_SCAN 1 in the log files, and I thought the replacement should have
changed that to AP_SCAN 2. However, dpkg did seem to do a replacement, and
Synaptic showed an ubuntu2 version before, and an ubuntu4 version
afterward. I will play with these things a bit more when I find time.

In the meantime, I will check out the archive deb package and see how I go
with that.

Matt

On Tue, Apr 1, 2008 at 11:01 AM, Alexander Sack <email address hidden> wrote:

> Matt, i cannot tell if you are really running the right network manager
> package as i miss some log output i would expect to see in the latest
> packages. Anyway, the branch is now available as .deb package in the
> archive, so you can test the prebuild debs directly. If you still have
> issues connecting to hidden SSID (or connecting at all), please file a
> new ipw2200 bug.
>
> For the signing error during build: the failure to sign is not a problem
> for local tests. I think the error message would not have popped up if
> you build like:
>
> debuild -b -uc
>
> --
> 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: Fix Released
> 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> ...
>