[ath_pci] cannot connect to hidden ap

When I patch n-m to use AP_SCAN=1 with ath_pci I can connect to hidden APs.

I uploaded a patched n-m to my PPA so other people can test it:
https://launchpad.net/~sroecker/+archive

Do some cards with ath_pci require ap_scan=1 and some require ap_scan=2 to work with hidden APs?

Hi Steffen,

I've testet one of my Atheros AR5212 adapters (an internal) now, and I can connect using your patch. Will test two external PCMCIA adapters later, and return the results. Great work, thanks.

Off topic - Could you help making a identical test-patch for ZyXEL zd1211rw chipsets, that seem to suffer from excactly the same issue ? - If so I would open a bug concerning this chipset.

Used your patch with 3 different Atheros based adapters (IBM, Netgear and Cisco), and can confirm that they all works with WPA1 secured hidden SSID on different APs.

christiansen, do we have a bug for zd1211rw yet?

if possible, please provide feedback on that branch _before_ it gets uploaded. I am waiting for tests on the other chipset in bug 208306 before uploading this.

Instructions to build this branch:

# install build requirements/dependencies
 1. sudo apt-get build-dep network-manager
 2. sudo apt-get install bzr devscripts

# branch the sources
 3. bzr branch https://code.edge.launchpad.net/~ubuntu-core-dev/network-manager/ubuntu.0.6.x network-manager.ubuntu

# build the sources:
 4. cd network-manager.ubuntu
 5. debuild -b

# install the bits for testing
 6. cd ../; dpkg -i network-manager*deb libnm-*deb

Atheros:
Chipset FAILED completely AND crashed NM. NM could not be restarted. had to reboot computer. may have been low memory issue @ 256 mb causing some boot issues, raised to 384mb memory re-ran test, booting fine now. NM no longer crashing, however could NOT connect to hidden SSID.

8.04 reported chipset as Atheros AR2413 802.11bg NIC - using ath_pci driver.
tested connecting to hidden SSID FAILS, I only use wpa2....is it important to test for wpa1 also just to give feed back ?
tested connecting to exposed SSID SUCEEDS, again, I use wpa2....don't know about wpa1.

This computer is just an old generic computer I built 10 years ago, PIII @500mhz, 384mb memory(now), Nvidia video card, SCSI HD subsystem. Runs 7.10 just fine.

I still have suspicions that 256 mb memory is an issue right now with current beta status. I'm assuming that basic hardware requirements are still the same tho. Pentium class processor and min 256mb memory.

Alexander,
I will try to follow your instructions for patching on the next patch indicated that might fix this chipset. may day a few days to set up a dedicated installable test machine.
PS: I believe that matt and I REALLY were just talking to each other, not really complaining out loud to you or trying to drop hints.

opps, need to clear up one thing, while my machine runs 7.10 just fine, I am not saying that this bug did not exist in 7.10, it did.

ok, please let me know if there are still issues with any ath_pci chipset/driver you have access to. IMO, the current branch should do quite well.

Same problems with Ubuntu 8.04 + Macbook first generation with:
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

Alex, I can do any patching/debuging you need.

-Luke

On Mon, Mar 31, 2008 at 12:28:34PM -0000, Gene Caldwell wrote:
> I still have suspicions that 256 mb memory is an issue right now with
> current beta status. I'm assuming that basic hardware requirements are
> still the same tho. Pentium class processor and min 256mb memory.

The minimum memory requirements for Ubuntu 8.04 using the liveCD install
method are 384MB, as documented at
<https://help.ubuntu.com/community/Installation/SystemRequirements>.

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

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

  * add ath_pci to the has_buggy_apscan_2 drivers which is reported
    to fix hidden SSID issues (LP: #208306) - submitted by Steffen Röcker
    - update debian/patches/42b_fix_ap_scan_hidden.patch
  * move code that sets essid through wireless tools to the end of the
    activation sequence and in turn reinstantiate code that sets ssid on
    wpasupplicant to its original position in that sequence.
    - update debian/patches/42b_fix_ap_scan_hidden.patch
  * be sure that wpasupplicant doesn't lock the control sockets on reconnect;
    we do this by sending SIGTERM _after_ the control socket connection to
    supplicant was closed on network-manager side, then wait for 1/4th second
    and send a SIGKILL.
    - add debian/patches/42c_terminate_supplicant_cleanly.patch
    - update debian/patches/series
  * add zd1211rw to the set of has_buggy_apscan_2_drivers to fix hidden
    network issues (LP: #209466)
    - update debian/patches/42b_fix_ap_scan_hidden.patch

 -- Alexander Sack <email address hidden> Mon, 31 Mar 2008 23:09:55 +0200

Alexander,
sent private email 1 min ago about build patching errors...
Gene

Alexander,
Ok, got fatal errors at gpg stage of build instructions above, however after reading what Matt posted in other bug thread about this same issue, I decided to just ignore the fatal error and continued to next step, step 6 which installed the package.

the branch above in your build instructions does not appear to resolve my connection issue to hidden SSID's.

Then 3 minutes later I see above that you have released a patch to the build servers.....so then 5 minutes later I see that updates are now available, 2 of which are the NM software, so I install the updates again and test again for hidden network SSID's. Sorry, my chipset still does not work with hidden SSID's. I tried with WPA1 and WPA2, no luck at all.

As long as the SSID is being broadcasted, I can connect tho. One more thing I would like to note: signal strength is 50% weaker for 8.04 than it is for 7.10 at the client. I have an AP within feet of the test machine, and I also have a repeater in the same vicinity, I get 100% signal strength/quality for this test machine running 7.10, but only 50% signal strength/quality for 8.04.... of course this is for an exposed SSID.

Atheros AR2413 802.11bg NIC - using ath_pci driver

Just want to confirm that the network-manager-0.6.6-0ubuntu5 that now is released to the repositories WORKS for me. Used it for both WPA1 and WPA2 secured hidden networks without glitches.

SUCESS !!! the newest release of NM 6.6.ububtu5 seems to work as it should, I do not see any issues so far.....however I am seeing a big problem with the signal strength. I have placed a repeater 12 inches away from this client and can only get less than 50% signal strength at 36 to 46 MB connection speed. This is a clear cut issue with 8.04, I can take this same exact setup and run 7.10 @ 100% signal strength with a full 54mb connection established.

on a different note now that this connection seems resolved for me...I have attached a screen shot of some very contradictory indicators about the wifi connection while it was still having problems: there are several indicators in this screen shot, half say I am connected to the net, half say I cannot be connected at all. NM shows full connection strength while there is no IP data displayed while system monitor shows IP traffic, yet firefox can't connect to the net.................

network-manager-0.6.6-0ubuntu5 works at Purdue. Thanks Alex!

Well, apparently it's not as fixed as we'd like. I just installed 8.04 beta yesterday on my laptop (previously running 6.06 and connecting to my non-SSID-broadasting wireless with no trouble), and was unable to connect. I found this bug report, so I plugged in a cable to the router and upgraded all packages to the current versions (including network-manager-0.6.6-0ubuntu5). Unfortunately, I'm still getting the exact same results as shown in Gene's screen shot (two posts above). the tray icon shows me connected w/ 97% signal strength, but connection info shows I have no IP address, and I am unable to use the network. Is there something I'm overlooking here? (Oh, and I just tried connecting to some non existent network with a total nonsense name and it still shows I have 97% signals strength for that one too :p)

My wireless is using WEP (it's an old Toshiba router and that's the only security mode it has).

Please let me know what I can do to help pin down this bug so we can hopefully get a fix before release.

I'm sorry, I was mistaken - I am unable to connect when the SSID is broadcast either so I am likely seeing a different bug, though it looks the same when the SSID is hidden.