[Bug 648830] New: essid not set on boot for wireless network
https://bugzilla.novell.com/show_bug.cgi?id=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c0 Summary: essid not set on boot for wireless network Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse-beta@cboltz.de QAContact: qa@suse.de Found By: Beta-Customer Blocker: --- - traditional network (no networkmanager) - unencrypted network named "gaestehaus" (at the openSUSE conference) - configured with YaST2 The essid is not set automatically for the card after booting: # iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off I have to set the essid manually using iwconfig to get the network working. The essid is also lost after resuming from suspend2ram (I think this happens always, but I'm not perfectly sure). The first lines with "wlan" in /v/l/messages after boot: Oct 23 09:13:40 geeko ifup: wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) Oct 23 09:13:40 geeko ifup-wireless: wlan0 starting wpa_supplicant Oct 23 09:13:41 geeko kernel: [ 46.086898] ADDRCONF(NETDEV_UP): wlan0: link is not ready Oct 23 09:13:41 geeko ifup-dhcp: wlan0 Starting DHCP4 client Oct 23 09:13:42 geeko dhcpcd[3122]: wlan0: dhcpcd 3.2.3 starting Oct 23 09:13:42 geeko dhcpcd[3122]: wlan0: hardware address = 00:21:5c:a1:1c:0d Oct 23 09:13:42 geeko dhcpcd[3122]: wlan0: broadcasting for a lease Oct 23 09:13:59 geeko ifup-dhcp: wlan0 DHCP4 continues in background Oct 23 09:14:02 geeko dhcpcd[3122]: wlan0: timed out # grep -v "''$" ifcfg-wlan0 # non-empty settings BOOTPROTO='dhcp' IFPLUGD_PRIORITY='10' NAME='PRO/Wireless 4965 AG or AGN [Kedron] Network Connection' STARTMODE='auto' USERCONTROL='yes' WIRELESS_AUTH_MODE='no-encryption' WIRELESS_BITRATE='auto' WIRELESS_DEFAULT_KEY='0' WIRELESS_ESSID='gaestehaus' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_POWER='yes' WIRELESS_AP_SCANMODE='1' -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c2 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #2 from Vladimir Botka <vbotka@novell.com> 2010-10-26 21:41:18 UTC --- (In reply to comment #0)
Oct 23 09:13:41 geeko kernel: [ 46.086898] ADDRCONF(NETDEV_UP): wlan0: link is not ready
For some reason the the "link is not ready". Would it be possible to post the output of "hwinfo --wlan" and try to locate the problem as described in [1] ? [1] http://en.opensuse.org/SDB:Tracking_down_wireless_problems -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c3 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #3 from Christian Boltz <suse-beta@cboltz.de> 2010-10-27 20:09:45 CEST --- As I wrote, this happened at the openSUSE conference - now I'm home again and can't test with the conference network for obvious reasons. If /var/log/messages or other logfiles are helpful for you, tell me what you need. (And/or ask someone in the SUSE office in Nürnberg to take a laptop with similar hardware and to drive to the BFW ;-) Another sidenote: I remember that in some cases the essid was lost even without suspend or reboot - unfortunately I have no idea why this happened. (Maybe low signal quality, but I'm not sure about this.) "iwconfig wlan0 essid gaestehaus" always fixed my network connection IIRC. That said, I can at least provide the hwinfo output (in case it matters: my wireless is configured for my home network with WPA2 encryption again). # hwinfo --wlan 21: PCI 600.0: 0282 WLAN controller [Created at pci.318] Unique ID: y9sn.g2v+3nPNNo6 Parent ID: Z7uZ.ZQuAvDd0D+2 SysFS ID: /devices/pci0000:00/0000:00:1c.3/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x4229 "PRO/Wireless 4965 AG or AGN [Kedron] Network Connection" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x1121 Revision: 0x61 Driver: "iwlagn" Driver Modules: "iwlagn" Device File: wlan0 Features: WLAN Memory Range: 0xf4000000-0xf4001fff (rw,non-prefetchable) IRQ: 32 (no events) HW Address: 00:21:5c:a1:1c:0d Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d00004229sv00008086sd00001121bc02sc80i00" Driver Info #0: Driver Status: iwlagn is active Driver Activation Cmd: "modprobe iwlagn" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #9 (PCI bridge) -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c4 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #4 from Vladimir Botka <vbotka@novell.com> 2010-10-28 19:31:42 UTC --- (In reply to comment #3)
"iwconfig wlan0 essid gaestehaus" always fixed my network connection IIRC.
# hwinfo --wlan Device: pci 0x4229 "PRO/Wireless 4965 AG or AGN [Kedron] Network Connection" Driver Activation Cmd: "modprobe iwlagn"
I'm running (24/7) Intel 4965 with 11.3 connected to an AP. There shouldn't be any problem with iwlagn. If you observe disconnections when the AP is under heavy load maybe it could help to disable hardware scanning [1] . Thus the iwlagn driver deliver the sniffed and cached list of APs instead of inquiring the APs and waiting for the APs to answer first. Maybe under heavy load some AP doesn't reply in time. But in this case wpa_supplicant shall try and reconnect. It would help to see /var/log/messages and /var/log/wpa_supplicant.log with enabled debugging both in wpa_supplicant and the driver. But to fix it the problem shall be reproducable. I set needinfo here for you or others to deliver more information when you find any repeatable problem. [1] # cat /etc/modprobe.d/50-iwlagn.conf options iwlagn disable_hw_scan=1 -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c5 --- Comment #5 from Christian Boltz <suse-beta@cboltz.de> 2010-10-28 22:47:49 CEST --- As I wrote, the problem only happened at the openSUSE conference and I can't reproduce it at home. Unless someone else can reproduce the problem, this bug will stay in needinfo until the next openSUSE conference ;-) -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c6 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P0 - Crit Sit Status|NEEDINFO |NEW Component|Network |Network InfoProvider|suse-beta@cboltz.de | Product|openSUSE 11.3 |openSUSE 11.4 Severity|Major |Critical --- Comment #6 from Christian Boltz <suse-beta@cboltz.de> 2011-05-12 10:12:46 CEST --- I have the same problem at LinuxTag with openSUSE 11.4 and essid LinuxTag. The interesting thing is that it works with NetworkManager without problems... I'm at LinuxTag until saturday - if you want me to test something, please ask soon ;-) -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c7 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #7 from Vladimir Botka <vbotka@novell.com> 2011-05-12 10:28:49 UTC --- (In reply to comment #6)
I have the same problem at LinuxTag with openSUSE 11.4 and essid LinuxTag.
It would be good to post the output of "nm-tool" together with the wpa_supplicant.log and dmesg to isolate the problem. Could you truncate the log files and turn the debugging on both for wpa_supplicant and iwlagn [1]. [1] http://en.opensuse.org/SDB:Tracking_down_wireless_problems -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c8 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #8 from Christian Boltz <suse-beta@cboltz.de> 2011-05-12 13:19:09 CEST --- Created an attachment (id=429298) --> (http://bugzilla.novell.com/attachment.cgi?id=429298) logs etc. This tar.gz contains the logs you requested from both traditional and networkmanager mode. wpa_supplicant did not log anything in traditional mode. One error I get at rcnetwork (re)start is: wlan0 starting wpa_supplicant Line 5: WPA-PSK accepted for key management, but no PSK configured. Line 5: failed to parse network block. Failed to read or parse configuration '/var/run/wpa_supplicant-wlan0.conf'. The config file (auto-generated by whatever) is included in the tarball - maybe it's "just" a broken config file generation? -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c9 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #9 from Vladimir Botka <vbotka@novell.com> 2011-05-12 15:35:17 UTC --- (In reply to comment #8) Both traditional and NM mode [1-2] seem to be working. But I am not able to locate the problem [2] in the log files. What setting doesn't work for you ? The error message is self-explaining. password psk="secret" is missing in the /var/run/wpa_supplicant-wlan0.conf . Would it be possible to report the failed conditions only ? Also it would be very helpful to either start the wpa_supplicant manually with the "-dddt" option or to set this option to start the wpa_supplicant by the NM [5]. [1] Trying to associate with 08:17:35:dd:17:dd (SSID='LinuxTag' freq=5280 MHz) Associated with 08:17:35:dd:17:dd CTRL-EVENT-CONNECTED - Connection to 08:17:35:dd:17:dd completed (reauth) [id=0 id_str=] [2] # grep -r State: wpa_supplicant.log.networkmanager 1305198702.544223: State: INACTIVE -> SCANNING 1305198704.582625: State: SCANNING -> ASSOCIATING 1305198704.667709: State: ASSOCIATING -> ASSOCIATED 1305198704.667903: State: ASSOCIATED -> COMPLETED 1305198704.684659: State: COMPLETED -> DISCONNECTED [3] wlan0 starting wpa_supplicant Line 5: WPA-PSK accepted for key management, but no PSK configured. Line 5: failed to parse network block. Failed to read or parse configuration '/var/run/wpa_supplicant-wlan0.conf' [4] http://en.opensuse.org/SDB:Tracking_down_wireless_problems#How_to_set_up_a_c... [5] #!/bin/bash SERVICE=/usr/share/dbus-1/system-services/fi.epitest.hostap.WPASupplicant.service sed -i s/"wpa_supplicant "/"wpa_supplicant -dddt "/ $SERVICE -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c10 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #10 from Christian Boltz <suse-beta@cboltz.de> 2011-05-13 16:30:55 CEST --- (In reply to comment #9)
Both traditional and NM mode [1-2] seem to be working.
Unfortunately not. Only NM works. Traditional mode does not even write something to wpa_supplicant.log - therefore you won't find an error message for it in the log.
The error message is self-explaining. password psk="secret" is missing in the /var/run/wpa_supplicant-wlan0.conf .
I'm not sure if it should really be psk="secret" - the LinuxTag network is not encrypted (essid "LinuxTag", no passphrase required). But obviously there's something wrong with the generated config file. How would a working wpa_supplicant-wlan0.conf look like for an unencrypted network?
Also it would be very helpful to either start the wpa_supplicant manually with the "-dddt" option or to set this option to start the wpa_supplicant by the NM [5].
I already did this (the permanent way [5]) before I started collecting the logs. It probably wasn't too useful because the traditional mode did not write anything to the log :-( -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c11 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P0 - Crit Sit |P5 - None Summary|essid not set on boot for |essid not set for |wireless network |unencrypted wireless | |network (traditional mode) Severity|Critical |Major --- Comment #11 from Christian Boltz <suse-beta@cboltz.de> 2011-05-15 17:27:12 CEST --- I'm back home from LinuxTag and therefore resetting the priority of this bug (BTW: thanks for the fast response in the last days!) Now to the technically interesting point: I can reproduce the "essid not set" problem with the network settings I had for the LinuxTag network even at home. This means this bug affects probably all unencrypted networks if you use traditional network mode. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c12 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #12 from Vladimir Botka <vbotka@novell.com> 2011-06-01 17:29:05 UTC --- (In reply to comment #11)
This means this bug affects probably all unencrypted networks if you use traditional network mode.
If the authentication method of the AP is set "open" and wep encryption set to "none" then you shall be able to connect from the command line as root with the command [1]. Check if the interface is connected [2] and if you have dhcp server start the dhclient [3], or setup the IP address manually. Just to be sure, this shall work if you see "Encryption key:off" on the AP you want to connect to [4]. If this procedure works for you, but you can not set it in yast, then we are going to take a look on the sysconfig next. [1] iw dev wlan0 connect SSID [2] iw dev wlan0 link [3] dhclient wlan0 [4] Cell 01 - Address: 00:18:F3:98:D1:9E Channel:1 Frequency:2.412 GHz (Channel 1) Quality=52/70 Signal level=-58 dBm Encryption key:off ESSID:"vlado-test-ap1" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=00000000947a0b7f Extra: Last beacon: 94ms ago IE: Unknown: 000E766C61646F2D746573742D617031 IE: Unknown: 010882848B962430486C IE: Unknown: 030101 IE: Unknown: 2A0100 IE: Unknown: 2F0100 IE: Unknown: 32040C121860 IE: Unknown: DD06001018020010 -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c13 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #13 from Christian Boltz <suse-beta@cboltz.de> 2011-06-02 18:24:08 CEST --- I just disabled encryption on my AP. Test results: (In reply to comment #12)
[1] iw dev wlan0 connect SSID
Works (no output)
[2] iw dev wlan0 link
Connected to 00:14:bf:c9:24:50 (on wlan0) SSID: Pinguin freq: 2452 RX: 66744 bytes (901 packets) TX: 18588 bytes (111 packets) signal: -72 dBm tx bitrate: 54.0 MBit/s
[3] dhclient wlan0
For some reason, wlan0 remembered the IP (I was connected to the same AP with WPA encryption before, that might explain it), therefore I skipped this step. The interesting point is probably that "ping google.de" works :-)
If this procedure works for you, but you can not set it in yast, then we are going to take a look on the sysconfig next.
OK, what's the next thing I have to test? -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c14 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse-beta@cboltz.de --- Comment #14 from Vladimir Botka <vbotka@novell.com> 2011-06-02 19:07:25 UTC --- (In reply to comment #13)
OK, what's the next thing I have to test?
Now you can try and configure the same AP within the YAST traditional ifup/ifdown. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c15 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse-beta@cboltz.de | --- Comment #15 from Christian Boltz <suse-beta@cboltz.de> 2011-06-04 21:35:55 CEST --- Now things get more interesting ;-) (even more than I thought...) I (again) configured my WLAN router to unencrypted mode and deleted/renamed /etc/sysconfig/network/ifcfg-wlan0 before every step to have a clean start. YaST seems to have two different modes for unencrypted networks: a) WEP - Open This works (don't ask why I didn't try it earlier ;-) b) No Encryption With this setting, WLAN doesn't work: # iw dev wlan0 link Not connected. # iwconfig wlan0 wlan0 IEEE 802.11abgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Interestingly, I did _not_ get any error messages on "rcnetwork restart" (see comment #8 for the error messages I got at LinuxTag). The difference is probably that I deleted the existing ifcfg-wlan0 config file before running YaST. (I can provide all relevant config files if you want to compare them.) -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c16 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mvidner@novell.com --- Comment #16 from Vladimir Botka <vbotka@novell.com> 2011-06-06 17:48:34 UTC --- (In reply to comment #15)
I (again) configured my WLAN router to unencrypted mode and deleted/renamed /etc/sysconfig/network/ifcfg-wlan0 before every step to have a clean start.
YaST seems to have two different modes for unencrypted networks:
a) WEP - Open This works (don't ask why I didn't try it earlier ;-)
b) No Encryption With this setting, WLAN doesn't work:
You are right. When the AP is set to use no encryption and no authentication the Yast can't configure and connect the AP with "No Encryption", but "WEP Open" works well. The difference between "No Encryption" and "WEP Open" is, that "WEP Open" shall allow an authentication. "WEP Open" works well. I can see wpa_supplicant configured [1] and connected. When user selects "No Encryption", Yast shall only run [2]. How does the Yast manage wireless "No Encryption" wireless configuration ? [1] ctrl_interface=/var/run/wpa_supplicant ap_scan=1 network={ scan_ssid=1 ssid="vlado-test-ap1" key_mgmt=NONE wep_tx_keyidx=0 } [2] iwconfig wlan0 essid vlado-test-ap1 -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c17 Martin Vidner <mvidner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEEDINFO |ASSIGNED CC| |mt@novell.com, | |vbotka@novell.com InfoProvider|mvidner@novell.com | AssignedTo|vbotka@novell.com |mvidner@novell.com Summary|essid not set for |essid not set for |unencrypted wireless |unencrypted wireless |network (traditional mode) |network (netcontrol, | |no-encryption snafu) --- Comment #17 from Martin Vidner <mvidner@novell.com> 2011-06-07 17:17:37 CEST --- YaST only writes the configuration for NetControl aka sysconfig.rpm The option "No Encryption" differs in setting WIRELESS_AUTH_MODE='no-encryption' instead of WIRELESS_AUTH_MODE='open'. It was added because of bnc#213001. Apparently in "fixing" that bug, the maintainer did not realize that no-encryption is for the UI only and that the ifcfg should still say WIRELESS_AUTH_MODE='open'. That fix never worked. Anyway, it would be nice if NetControl validated the input and reported invalid settings. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c19 Vladimir Botka <vbotka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mt@novell.com --- Comment #19 from Vladimir Botka <vbotka@novell.com> 2011-06-07 18:03:27 UTC --- (In reply to comment #17)
The option "No Encryption" differs in setting WIRELESS_AUTH_MODE='no-encryption' instead of WIRELESS_AUTH_MODE='open'.
Then this patch shall fix it [2]. I've built the sysconfig package to test in [1]. It works for me. Maybe Christian might want to test it too. Marius is ok to submit it ? [1] home:vbotka:branches:openSUSE:11.4:Update:Test/sysconfig [2] diff --git a/scripts/ifup-wireless b/scripts/ifup-wireless index 105ebe9..7994a33 100755 --- a/scripts/ifup-wireless +++ b/scripts/ifup-wireless @@ -304,7 +304,7 @@ EOL # special hack for madwifi test "$DRIVER" = "ath_pci" && run_iw_tool priv authmode 2 ;; - open|opensystem|"") WIRELESS_SEC_MODE="open";; + open|opensystem|no-encryption"") WIRELESS_SEC_MODE="open";; esac fi if [ -n "$WIRELESS_KEY_0" -a \ @@ -403,7 +403,7 @@ setup_wlanngdev() wlanctl dot11req_mibset mibattribute=dot11ExcludeUnencrypted=true AUTHTYPE=sharedkey ;; - open|opensystem|"") + open|opensystem|no-encryption"") wlanctl dot11req_mibset mibattribute=dot11ExcludeUnencrypted=false AUTHTYPE=opensystem ;; @@ -540,7 +540,7 @@ print_network_block() print_network_line ssid WIRELESS_ESSID "$SUFFIX" print_network_line_unquoted priority WIRELESS_PRIORITY "$SUFFIX" case "`eval echo \\$WIRELESS_AUTH_MODE$SUFFIX`" in - open) + open|no-encryption) echo " key_mgmt=NONE" for i in 0 1 2 3 ; do KEY="`eval print_key \\"\\$WIRELESS_KEY_$i$SUFFIX\\" \\$WIRELESS_KEY_LENGTH$SUFFIX`" -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c20 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|mt@novell.com | --- Comment #20 from Marius Tomaschewski <mt@novell.com> 2011-06-08 07:15:40 UTC --- (In reply to comment #17)
Anyway, it would be nice if NetControl validated the input and reported invalid settings.
Yes, as at and many other places. But this is something for the future [when SLE-11-SP2 is done]. (In reply to comment #19)
(In reply to comment #17)
The option "No Encryption" differs in setting WIRELESS_AUTH_MODE='no-encryption' instead of WIRELESS_AUTH_MODE='open'.
Then this patch shall fix it [2]. I've built the sysconfig package to test in [1]. It works for me. Maybe Christian might want to test it too.
Marius is ok to submit it ?
No, see bellow. Further question is: are both cases covered now, that is [1] and [2] from comment 16?
[1] home:vbotka:branches:openSUSE:11.4:Update:Test/sysconfig
[2] diff --git a/scripts/ifup-wireless b/scripts/ifup-wireless index 105ebe9..7994a33 100755 --- a/scripts/ifup-wireless +++ b/scripts/ifup-wireless @@ -304,7 +304,7 @@ EOL # special hack for madwifi test "$DRIVER" = "ath_pci" && run_iw_tool priv authmode 2 ;; - open|opensystem|"") WIRELESS_SEC_MODE="open";; + open|opensystem|no-encryption"") WIRELESS_SEC_MODE="open";; ^^^^^^^^^^^^^^^
This should be open|opensystem|no-encryption|"") I think.
esac fi if [ -n "$WIRELESS_KEY_0" -a \ @@ -403,7 +403,7 @@ setup_wlanngdev() wlanctl dot11req_mibset mibattribute=dot11ExcludeUnencrypted=true AUTHTYPE=sharedkey ;; - open|opensystem|"") + open|opensystem|no-encryption"")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Same.
wlanctl dot11req_mibset mibattribute=dot11ExcludeUnencrypted=false AUTHTYPE=opensystem ;; @@ -540,7 +540,7 @@ print_network_block() print_network_line ssid WIRELESS_ESSID "$SUFFIX" print_network_line_unquoted priority WIRELESS_PRIORITY "$SUFFIX" case "`eval echo \\$WIRELESS_AUTH_MODE$SUFFIX`" in - open) + open|no-encryption) echo " key_mgmt=NONE" for i in 0 1 2 3 ; do KEY="`eval print_key \\"\\$WIRELESS_KEY_$i$SUFFIX\\" \\$WIRELESS_KEY_LENGTH$SUFFIX`"
Can you please review & correct the above and create the patch using "git format-patch" (with author, date, comment, ...) and send to me, so I don't need to fake them while applying it to git? [You may also clone from http://gitorious.org/opensuse/sysconfig, then commit & push to your clone and request a merge then...]. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c21 --- Comment #21 from Vladimir Botka <vbotka@novell.com> 2011-06-08 20:05:13 UTC --- (In reply to comment #20)
are both cases covered now, that is [1] and [2] from comment 16?
Yes, both cases are now covered.
Can you please review & correct the above and create the patch using "git format-patch" (with author, date, comment, ...) and send to me,
Done. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c22 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |maint-coord@suse.de InfoProvider| |maintenance@opensuse.org --- Comment #22 from Marius Tomaschewski <mt@novell.com> 2011-06-09 10:53:02 UTC --- OK, now in http://gitorious.org/opensuse/sysconfig/commit/b54c65525c0577b87f2ed8f3343e5... See also: https://build.opensuse.org/request/show/73086 Just submit it to 11.4:Update:Test when there is ACK for. Martin, when I see correctly, bnc#213001 introduced this for 10.0, that means we need it for every released version (+factory), right? Mr. Maintenance, I think we have to provide / pickup it in updates... OK? Where? -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c23 Martin Vidner <mvidner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com AssignedTo|mvidner@novell.com |mt@novell.com --- Comment #23 from Martin Vidner <mvidner@novell.com> 2011-06-09 13:30:30 CEST --- (In reply to comment #22)
Martin, when I see correctly, bnc#213001 introduced this for 10.0, that means we need it for every released version (+factory), right?
Well, it did not break an existing feature, just added a new non-working one. So I think we should only release the update if the overhead is low. Reassigning to Marius as the fix ended up in his package. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c24 Christian Dengler <cdengler@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cdengler@novell.com --- Comment #24 from Christian Dengler <cdengler@novell.com> 2011-06-09 13:22:56 UTC --- update is okay for me, for 11.4 and 11.3 (if necessary). +1 -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c25 --- Comment #25 from Marcus Meissner <meissner@novell.com> 2011-06-09 13:29:25 UTC --- yes,m sounds sensible for 11.3 and 11.4 +1 -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c27 --- Comment #27 from Marius Tomaschewski <mt@novell.com> 2011-06-09 14:05:32 UTC --- Vladimir, I'm going to submit the packages everywhere. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c28 Christian Dengler <cdengler@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|maintenance@opensuse.org | --- Comment #28 from Christian Dengler <cdengler@novell.com> 2011-06-09 14:19:30 UTC --- You can use the running SwampID: 41535 -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c29 --- Comment #29 from Vladimir Botka <vbotka@novell.com> 2011-06-09 14:47:20 UTC --- (In reply to comment #27)
I'm going to submit the packages everywhere.
Yes, it would be good to put it into the SLE. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c30 --- Comment #30 from Marius Tomaschewski <mt@novell.com> 2011-06-09 15:37:44 UTC --- SWAMPID 41535: bnc#698478,bnc#648830: OBS request id 73192 => openSUSE:11.3:Update:Test OBS request id 73190 => openSUSE:11.4:Update:Test IBS request id 12660 => SLE-11-SP1:Update:Test -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c31 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:sle11-sp1:41 | |716 --- Comment #31 from Swamp Workflow Management <swamp@suse.de> 2011-07-01 09:29:15 UTC --- Update released for: sysconfig, sysconfig-debuginfo, sysconfig-debugsource Products: SLE-DEBUGINFO 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP1 (i386, x86_64) SLE-SERVER 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLES4VMWARE 11-SP1 (i386, x86_64) -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c32 Dirk Mueller <dmueller@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #32 from Dirk Mueller <dmueller@novell.com> 2011-07-01 11:35:31 CEST --- updates released. -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c33 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:sle11-sp1:41 |maint:released:sle11-sp1:41 |716 |716 | |maint:released:11.3:42004 | |maint:released:11.4:42004 --- Comment #33 from Swamp Workflow Management <swamp@suse.de> 2011-07-01 17:28:03 UTC --- Update released for: sysconfig, sysconfig-debuginfo, sysconfig-debugsource Products: openSUSE 11.3 (debug, i586, x86_64) openSUSE 11.4 (debug, i586, x86_64) -- 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=648830 https://bugzilla.novell.com/show_bug.cgi?id=648830#c34 --- Comment #34 from Bernhard Wiedemann <bwiedemann@suse.com> 2011-09-05 19:00:08 CEST --- This is an autogenerated message for OBS integration: This bug (648830) was mentioned in https://build.opensuse.org/request/show/81005 Factory / sysconfig -- 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