[Bug 421880] New: Can't connect if wireless SSID not broadcast
https://bugzilla.novell.com/show_bug.cgi?id=421880 Summary: Can't connect if wireless SSID not broadcast Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nick.battle@uk.fujitsu.com QAContact: qa@suse.de Found By: Community User Configuring a WPA wireless client to connect to an AP that doesn't broadcast its SSID used to work perfectly in openSUSE 10.3, but 11.0 fails to add "WIRELESS_AP_SCANMODE='2'" to the ifcfg file, which causes the WPA supplicant to fail to form an association. Details: ipw2200 device, configured for WPA_PSK security, AP's BSSID (and SSID) set via Yast. Subsequently adding WIRELESS_AP_SCANMODE='2' to the ifcfg file and stop/starting the interface cures the problem. The Yast in 10.3 appears to add the scan mode line, which then works first time. More information at http://forums.opensuse.org/network-internet/wireless/393838-ipw2200-failed-s... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=421880
Michal Zugec
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c1
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
User nick.battle@uk.fujitsu.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c2
Nick Battle
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c3
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
User nick.battle@uk.fujitsu.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c4
--- Comment #4 from Nick Battle
I don't *remember* adding the scan mode by hand
On the other hand, the "tips and tricks" link in the openSUSE forums was dated Aug 2007... I *do* remember having to play about with Yast several times to get the correct settings. I wonder whether it is possible to add the scan mode value by some sequence of Yast actions, and once it's there it stays there? If 10.3 Yast never adds it, we'll have to put this one down to my aging memory - though the bug still stands of course.
Could you please try if "iwlist eth1 scan essid your_essid" finds your access point?
That's on 11.0 without the scan mode line? OK, I'll try - though if the SSID isn't being broadcast, I can't see how this can find anything, surely? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c5
--- Comment #5 from Helmut Schaa
That's on 11.0 without the scan mode line? OK, I'll try - though if the SSID isn't being broadcast, I can't see how this can find anything, surely?
As "hidden" networks are not specified in 802.11 most vendors implement it in the following way: Neither the beacon frames nor probe responses contain the SSID. However if a client knows the SSID it can send a probe request for a specific SSID to which the AP will answer (that is what "iwlist ... essid ..." does). Hence a client which knows the SSID is able to scan for APs with that SSID even if they do not broadcast its SSID. Furthermore a client that does not know the SSID can still listen to probe responses to foreign clients in order to reveal hidden networks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=421880
User nick.battle@uk.fujitsu.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c6
--- Comment #6 from Nick Battle
https://bugzilla.novell.com/show_bug.cgi?id=421880
User nick.battle@uk.fujitsu.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c7
--- Comment #7 from Nick Battle
https://bugzilla.novell.com/show_bug.cgi?id=421880
User nick.battle@uk.fujitsu.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c8
Nick Battle
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c9
--- Comment #9 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
User nick.battle@uk.fujitsu.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c10
Nick Battle
Could you please set "DEBUG=yes" in the ifcfg-file, then run "rcnetwork restart" and attach the output of /var/log/messages afterwards?
Nothing appears in /var/log/messages when I do this. I tried with DEBUG=yes and DEBUG='yes'. What I do see in /var/log are messages in "warn" and "wpa_supplicant.log". They are: Sep 2 16:26:04 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:26:29 pollux syslog-ng[2417]: last message repeated 3 times Sep 2 16:26:29 linux kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. Sep 2 16:26:29 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:27:55 linux ifdown: No configuration found for eth0 Sep 2 16:27:55 linux ifdown: Nevertheless the interface will be shut down. Sep 2 16:27:56 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:27:56 linux ifup: No configuration found for eth0 Sep 2 16:27:57 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:27:57 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:27:57 linux kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. Sep 2 16:28:34 linux ifdown: No configuration found for eth0 Sep 2 16:28:34 linux ifdown: Nevertheless the interface will be shut down. Sep 2 16:28:35 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:28:35 linux ifup: No configuration found for eth0 Sep 2 16:28:36 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:28:36 linux SuSEfirewall2: SuSEfirewall2 not active Sep 2 16:28:36 linux kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. and No network configuration found for the current AP CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys No network configuration found for the current AP CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys No network configuration found for the current AP CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys No network configuration found for the current AP CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys No network configuration found for the current AP CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys The "ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command." was the only error I could identify when initially investigating this, but I couldn't find out what it was (Well, it means a lock held while some other command is sent, but I've no idea what that indicates!). Is there some other way to turn on debug - perhaps of the ipw2200 driver? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=421880
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=421880
Christian Zoz
https://bugzilla.novell.com/show_bug.cgi?id=421880
Christian Zoz
https://bugzilla.novell.com/show_bug.cgi?id=421880
Christian Zoz
https://bugzilla.novell.com/show_bug.cgi?id=421880
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c12
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c13
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
User mvdv@spamcop.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c14
Mark Van De Vyver
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c15
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=421880
User nick.battle@uk.fujitsu.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c16
--- Comment #16 from Nick Battle
https://bugzilla.novell.com/show_bug.cgi?id=421880
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=421880#c17
--- Comment #17 from Helmut Schaa
I have an 11.1 release DVD that I will install when I get time, though presumably that will *not* have the fix?
Right.
Will an online update catch up, or
AFAIK, yes. Just get back once you've tried it. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com