[ipw2200] Cannot connect to hidden ssid with network-manager >=0.6.6-0ubuntu1

Bug #199679 reported by gpothier
20
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Medium
Basilio Kublik

Bug Description

Binary package hint: network-manager

As per https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/199066/comments/13

Network manager (0.6.6-0ubuntu1) fails to connect to my WEP-encrypted network.
This is with Kubuntu Hardy. Chip is Intel Corporation PRO/Wireless 2915ABG

I can connect manually using iwconfig/dhclient:
sudo iwconfig eth1 essid **** key ****
sudo dhclient eth1

Attached is my complete /var/log/syslog. Latest failed connection attempt around 20:26.
Can I provide more information?

Revision history for this message
gpothier (gpothier) wrote :
Revision history for this message
Carlos Perelló Marín (carlos) wrote :

I have the same problem with an open network both with ipw220 and iwl3945 drivers

Revision history for this message
Alexander Sack (asac) wrote :

are you using a hidden SSID?

Revision history for this message
Rune Evjen (rune-evjen) wrote : Re: [Bug 199679] Re: [ipw2200] Cannot connect with network manager 0.6.6-0ubuntu1

Yes, I can confirm that associationg with a network with SSID hidden does
not work.

Associating with a network with SSID broadcast does work with hardy and the
iwl driver.

rune

Revision history for this message
Christiansen (happylinux) wrote : Re: [ipw2200] Cannot connect with network manager 0.6.6-0ubuntu1

I too can confirm probmels to connect to APs with hidden SSIDs using labtops with both ipw2200 and ipw2915, after upgrading to Hardy beta 6 and network-manager 0.6.6-0ubuntu1.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
do you still experience this issue with the current version of the application?

Thanks in advance

Changed in network-manager:
assignee: nobody → sourcercito
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Christiansen (happylinux) wrote :

Hi Basilio,
I do still experience the same problems as described above (WPA1 and Hidden SSID), after I have upgraded to network-manager 0.6.6-0ubuntu2 and the other updated packages for Hardy from tonight.

Downgrading the network-manager to 0.6.5 (used in Hardy Alpha 5 and below) by removing these tree packages (sequenced) :
  1) network-manager-kde_0.2ubuntu1-0ubuntu12_i386.deb
  2) network-manager_0.6.6-0ubuntu1_i386.deb
  3) libnl1_1.1-1_i386.deb
and then installed thees tree packages downloaded from launchpad.net instead :
  1) libnl1-pre6_1.0~pre6-6_i386.deb
  2) network-manager_0.6.5-0ubuntu16.7.10.0_i386.deb
  3) network-manager-kde_0.2ubuntu1-0ubuntu7_i386.deb
my wireless connections works again. I do not see this as a lasting solution to the the problem, but as a test that the APs and the hardware in my boxes works as it is expected to.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
this seems fairly similar to bug #50214, could you please take a look, and see if the workaround at comment https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/50214/comments/119 works for you as well.

Thanks

Steve Langasek (vorlon)
Changed in network-manager:
importance: Low → Medium
milestone: none → ubuntu-8.04
status: Incomplete → Confirmed
Revision history for this message
Christiansen (happylinux) wrote :

Hi Basilio,

I have been following the bug #50214 you mention for several K/Ubuntu releases, as it has a lot of good info regarding NM and hidden WPA networks - thanks to the work of Alexander Sack, who seems to be rather structured in solving the problems.
The workaround you mention is one I've used for years, even in none K/Ubuntu distros without NM, as its a fast an sure winner whenever NM doesn't work - I've used this workaround since Hardy Alpha 6, where the NM 0.6.6 stopped working on all the wireless adapers I'm testing (Intel, Atheros, Zyxel, Netgear and Cisco), when I have to download the NM 0.6.5 packages mentioned in my description above...

Tanks anyway, I hope the NM 0.6.6 is going to even more mature (supporting even more adapters) than the K/Ubuntu patched NM 0.6.5 did just before Gutsy was released.

Revision history for this message
Alexander Sack (asac) wrote :

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.

Revision history for this message
Alexander Sack (asac) wrote :

... after this round of testing I will sort the remaining issues to specialised per-chipset bugs.

Revision history for this message
Alexander Sack (asac) wrote :

well, this one is already a per-chipset one :)

Revision history for this message
Alexander Sack (asac) wrote :

i did some cleanups of the hidden ssid tweaks on the branch. The new behaviour is:

  * use scan_ssid 1 with AP_SCAN 1 for all scan_capa_ssid drivers
  * use scan_ssid 1 with AP_SCAN 1 for all drivers with buggy
    scan_capa_ssid and buggy ap_scan and explicitly set essid through
    wireless tools to help driver to find bssids of hidden ssid
      Drivers with buggy scan_capa_ssid: ipw2200
      Drivers with buggy ap_scan 2: iwl3945, iwl4965
  * use AP_SCAN 2 for all other drivers
    - update debian/patches/42b_fix_ap_scan_hidden.patch

Revision history for this message
Dan McCombs (overridex) wrote :

Using the test branch above from this morning, this is letting me connect to a hidden ssid network with ipw2200, which I could not connect to yesterday... so far so good.

Revision history for this message
Alexander Sack (asac) wrote :

one more addition: to install the build dependencies to build the branch, run:

 sudo apt-get build-dep network-manager

Revision history for this message
gpothier (gpothier) wrote :

Hi, the situation is a bit random for me, using the branch (fetched today).
NM usually fails to connect once, then causes the applet to ask for the WEP key again, then succeeds. Everytime it fails I notice that the DHCP daemon is not even starting.
I attach the syslog.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 0.6.6-0ubuntu4

---------------
network-manager (0.6.6-0ubuntu4) hardy; urgency=low

  * fix hidden networks for chipsets that do not have scan_capa enabled
    driver. (LP: #50214, #200950, #203793, #199679). The following
    behaviour is now implemented:
      * use scan_ssid 1 with AP_SCAN 1 for all scan_capa_ssid drivers
      * use scan_ssid 1 with AP_SCAN 1 for all drivers with buggy
        scan_capa_ssid and buggy ap_scan and explicitly set essid through
        wireless extensions to help driver to find bssids of hidden ssid
          Drivers with buggy scan_capa_ssid: ipw2200
          Drivers with buggy ap_scan 2: iwl3945, iwl4965
      * use AP_SCAN 2 for all other drivers and set essid through wireless
        extensions forcefully.
        - update debian/patches/42b_fix_ap_scan_hidden.patch
    - add debian/patches/42b_fix_ap_scan_hidden.patch
    - update debian/patches/series

 -- Alexander Sack <email address hidden> Fri, 28 Mar 2008 10:38:42 +0100

Changed in network-manager:
status: Confirmed → Fix Released
Revision history for this message
gc (greger-cronquist) wrote :

With some update published yesterday, my computer no longer connects to my hidden ssid (I had to go public again). Attached what I think is the relevant part of my syslog, where first the failed attempt to connect to the hidden SSID "gc" and then a successful attempt to connect to "default" is shown. When I change "gc" to public, it works as it should.

Revision history for this message
Christiansen (happylinux) wrote :

Hi gpothier and gc,

I too experience trouble with the latest network-manager-0.6.6-0ubuntu5 (in Hardy RC) and the Intel 2200BG and 2915ABC adapters. I've tried to make a minor change to the latest brance supplyed by Alexander Sack, using AP_SCAN 1 (instead of 2) as it seems it was in NM-0.6.5 for Gutsy. I have now been using this patched network-manager-0.6.6-0ubuntu6~test1 (attached as archive) for a couple of days now, an it has solved the problem I was experiencing (identical to gpothier description, juse in Kubuntu). If you are interested, you could try them out.

You probably only need the 1. "libnm-util0_0.6.6-0ubuntu6~test1_i386.deb" and the 2. "network-manager_0.6.6-0ubuntu6~test1_i386.deb" from the attached archive, sequentially installed.

BTW Please have a look at the new bug #21706 opened on this issue too.

Revision history for this message
Christiansen (happylinux) wrote :

The archive with the compiled binary for the issue above.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.