Description of problem:
I have a hidden wireless network. I add the ssid manually using the NM-app.
NM tries to connect many times but fails to. The only way I can get it to
connect is to issue this command while it is trying to connect: (where <essid>
is your hidden essid)
iwconfig wlan0 essid <essid>
Version-Release number of selected component (if applicable):
Madwifi from LVN:
Steps to Reproduce:
2.Try manually adding hidden essid using the gnome-NM-app
3.Hope that it connects
Failure to connect to hidden wireless network
Success at connecting to hidden wireless network
Attached is part of the messages log file in /var/log which gives a good clue of
what is happening. At the end of the file, it shows that NM connects to the net
when I assign the essid manually using the iwconfig tool.
Here is my lsmod:
Module Size Used by
autofs4 20421 2
nf_conntrack_ipv4 11717 3
ipt_REJECT 7617 2
iptable_filter 6465 1
ip_tables 14213 1 iptable_filter
xt_state 6081 3
nf_conntrack 51977 2 nf_conntrack_ipv4,xt_state
nfnetlink 8281 2 nf_conntrack_ipv4,nf_conntrack
xt_tcpudp 6977 5
x_tables 14277 4 ipt_REJECT,ip_tables,xt_state,xt_tcpudp
cpufreq_ondemand 10317 1
loop 16581 0
dm_mirror 21697 0
dm_multipath 18249 0
dm_mod 46465 2 dm_mirror,dm_multipath
radeon 114145 2
drm 67028 3 radeon
ipv6 245989 8
snd_atiixp 18509 4
snd_seq_dummy 6725 0
snd_atiixp_modem 15177 1
snd_ac97_codec 92389 2 snd_atiixp,snd_atiixp_modem
ac97_bus 6081 1 snd_ac97_codec
wlan_scan_sta 14464 1
snd_seq_oss 29889 0
ath_rate_sample 14592 1
irda 106617 0
snd_seq_midi_event 9793 1 snd_seq_oss
snd_seq 44849 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
b44 25937 0
parport_pc 26981 0
ath_pci 84384 0
crc_ccitt 6081 1 irda
ssb 29893 1 b44
parport 32393 1 parport_pc
wlan 172740 4 wlan_scan_sta,ath_rate_sample,ath_pci
firewire_ohci 18113 0
mii 8385 1 b44
ath_hal 193488 3 ath_rate_sample,ath_pci
snd_seq_device 10061 3 snd_seq_dummy,snd_seq_oss,snd_seq
firewire_core 36097 1 firewire_ohci
crc_itu_t 6081 1 firewire_core
sdhci 17997 0
mmc_core 27333 1 sdhci
snd_pcm_oss 37569 0
snd_mixer_oss 16705 3 snd_pcm_oss
video 19921 0
output 6977 1 video
snd_pcm 63685 4
battery 14025 0
ac 8133 0
button 10321 0
snd_timer 20549 2 snd_seq,snd_pcm
k8temp 8257 0
serio_raw 9029 0
snd 43461 16
soundcore 9633 3 snd
hwmon 6469 1 k8temp
snd_page_alloc 11337 3 snd_atiixp,snd_atiixp_modem,snd_pcm
i2c_piix4 11341 0
i2c_core 21825 1 i2c_piix4
joydev 11649 0
sg 31965 0
sr_mod 17509 0
cdrom 33889 1 sr_mod
ata_generic 8901 0
pata_atiixp 9409 3
libata 99633 2 ata_generic,pata_atiixp
sd_mod 27329 4
scsi_mod 119757 4 sg,sr_mod,libata,sd_mod
ext3 110665 2
jbd 52457 1 ext3
mbcache 10177 1 ext3
uhci_hcd 23633 0
ohci_hcd 21445 0
ehci_hcd 31693 0
Here is my modprobe.d/madwifi:
alias wifi0 ath_pci
alias wlan0 ath_pci
options ath_pci autocreate=sta
Created attachment 253591 [details]
messages file from /var/log/messages showing the results from NM
At first I thought it was an issue with my 'Asus WL100-G' and the b43legacy
driver. After the last kernel update my system doesn't crash anymore after
removing the pcmcia card but still no go when using a hidden ESSID. Network is
fine when I 'unhide' the ESSID.
I'm not using madwifi btw, so this is plain F8 stuff.
i cant connect to hidden networks either. If I enable the ssid broadcast it
works. However, WPA doesnt work at all, ever.
scratch that. since knetworkmanager is now a link to nm-applet....i had to use
gconf-editor to clear out all the remembered wifi networks.....then wpa started
working. BUT, I still can't connect to a hidden network, whether the network
has wep, wpa, or nothing, i still cant connect.
Ideally, knetworkmanager should be brought back (since I use kde). Otherwise, I
find NM to be much more stable than in fc7.
I am seeing the same problem. Something is not right with the hidden SSID.
Also, I have noticed that if you do broadcast the SSID and allow NetworkManager
to connect to the wireless network and then quit broadcasting the SSID the
connection is dropped and can not reconnect.
personally, i blame nm-applet. It is a tranish on my otherwise smoothly running
and for the record im having this issue with an ipw2200 card, not madwifi
I've successfully used ipw2200 with hidden networks; can you see if a straight
wpa_supplicant config will connect for you using ap_scan=2?
WRT atheros, it has in the past needed ap_scan=1. But that is not going to be
special-cased because now that ath5k is in the upstream kernel, it will use
whatever settings the mac80211 stack uses (and all other mac80211-based
drivers). Drivers fundamentally _need_ to support ap_scan=2; ap_scan=1 +
scan_ssid=1 is an optimization of ap_scan=2 that some drivers just cannot support.
hidden SSID support is highly driver dependent and drivers need to get better
before it gets usably better for everyone, even without NetworkManager involved.
Thanks alot Dan! That worked fine for me.
In my /etc/wpa_supplicant/wpa_supplicant.conf file I put the following
and it worked fine after a restart of the services.
Adding ap_scan=2 worked for iwl3945 on x86_64, but scan_ssid=1 breaks it.
No wait, I lie. Will do further diagnosing...
*** Bug 427878 has been marked as a duplicate of this bug. ***
*** Bug 410931 has been marked as a duplicate of this bug. ***
*** Bug 267261 has been marked as a duplicate of this bug. ***
*** Bug 249156 has been marked as a duplicate of this bug. ***
*** Bug 178629 has been marked as a duplicate of this bug. ***
NetworkManager-0.7.0-0.6.7.svn3235.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update NetworkManager'
Using NetworkManager-0.7.0-0.6.7.svn3235.fc8 and kernel-184.108.40.206-105.fc8, the
connection is established nicely! Good work, guys!
However, NM does not seem able to automatically reconnect to the hidden network
after boot. I have to re-add the hidden network manually. This is probably a
different issue. It could be a regression in NM(?) I think this was fixed way
back, but I cant remember all the details.
NetworkManager-0.7.0-0.6.7.svn3235.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
As far as I can see, an earlier snapshot svn3204 has been pushed out to
stable. How did that happen?
Is this bug fixed?
I can't get NetworkManager to connect to a hidden SSID
(In reply to comment #22)
> Is this bug fixed?
> I can't get NetworkManager to connect to a hidden SSID
Yes, it's fixed. You need to update to the latest Fedora 8 updates kernel, and
patch the madwifi driver to advertise SSID scan capability. All in-kernel
drivers have been updated to reflect their scan capability, but since madwifi
isn't part of the kernel it's not something we can fix...
diff -ru madwifi-0 (copy).9.3.3/net80211/ieee80211_wireless.c
--- madwifi-0 (copy).9.3.3/net80211/ieee80211_wireless.c 2007-07-26
+++ madwifi-0.9.3.3/net80211/ieee80211_wireless.c 2008-02-04 07:20:17.000000000
@@ -1026,6 +1026,8 @@
IW_ENC_CAPA_CIPHER_TKIP | IW_ENC_CAPA_CIPHER_CCMP;
+ range->scan_capa = IW_SCAN_CAPA_ESSID;
Ah, it's driver dependent!
So if it doesn't work with the rt73usb driver what do I do?
Well, is the rt73usb driver using the mac80211 stack? If it is, it should
automatically pick up this capability on the latest kernels.
# lsmod|fgrep rt
exportfs 8129 1 nfsd
rt73usb 27201 0
rt2x00usb 12737 1 rt73usb
rt2x00lib 21313 2 rt73usb,rt2x00usb
rfkill 9297 1 rt2x00lib
input_polldev 7369 1 rt2x00lib
crc_itu_t 6081 1 rt2x00lib
mac80211 125265 2 rt2x00usb,rt2x00lib
parport_pc 26981 0
iTCO_vendor_support 7109 1 iTCO_wdt
parport 32393 1 parport_pc
Ok, so it should have the capability. Can you paste in the lines from
/var/log/messages where NM starts up? It should look something like:
NetworkManager: <info> eth1: Device is fully-supported using driver 'ipw2200'.
NetworkManager: <info> eth1: driver supports SSID scans (scan_capa 0x21).
NetworkManager: <info> Now managing wireless (802.11) device 'eth1'.
Feb 4 12:40:53 localhost NetworkManager: <info> starting...
Feb 4 12:40:53 localhost NetworkManager: <info> eth0: Device is
fully-supported using driver 'tg3'.
Feb 4 12:40:53 localhost NetworkManager: <info> Now managing wired Ethernet
(802.3) device 'eth0'.
Feb 4 12:40:53 localhost NetworkManager: <info> Bringing up device eth0
Feb 4 12:40:53 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 4 12:40:53 localhost NetworkManager: <info> Deactivating device eth0.
Feb 4 12:40:53 localhost NetworkManager: <info> (eth0): exporting device as
Feb 4 12:40:53 localhost NetworkManager: <info> wlan0: Device is
fully-supported using driver 'rt73usb'.
Feb 4 12:40:53 localhost NetworkManager: <info> Now managing wireless (802.11)
Feb 4 12:40:53 localhost NetworkManager: <info> Bringing up device wlan0
Feb 4 12:40:53 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 4 12:40:53 localhost NetworkManager: <info> Deactivating device wlan0.
Feb 4 12:40:53 localhost NetworkManager: <info> (wlan0): exporting device as
Feb 4 12:40:53 localhost NetworkManager: <info> (eth0) supplicant interface is
now in state 2 (from 1).
Feb 4 12:40:53 localhost NetworkManager: <info> (wlan0) supplicant interface
is now in state 2 (from 1).
There's no "driver supports SSID scans"
I tried another machine with a PCMCIA card using the b43 driver.
Same problem, can't connect to access point with hidden SSID.
Does NetworkManager on the other machine report anything about SSID scan
capability when it starts up? If that message isn't in the logs, it likely
won't work. You'll need NetworkManager-0.7.0-0.6.7.svn3235 or later, which was
pushed to F8-updates on 2008-01-22. Try updating a bit later today.
I have NetworkManager-0.7.0-0.6.7.svn3204.fc8.i386.rpm as the latest
Is this related to comment #21 ?
Yeah, something got screwed up in update repo generation, and that's being
corrected as I type this, hence the "try updating a bit later today." When you
see 3235 hit the repos, any mac80211-based, ipw2200, hostap, or libertas drivers
should work better with hidden SSIDs for you.
I'll test later.
Will this fix end in F7 as well?
No, it's not present in F7 yet. On track for a 0.6.6 release sometime later
this month though.
It works both for b43 and rt73usb, thanks!