https://bugzilla.novell.com/show_bug.cgi?id=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c1 --- Comment #1 from Casual J. Programmer 2008-03-21 04:00:59 MST --- Created an attachment (id=203307) --> (https://bugzilla.novell.com/attachment.cgi?id=203307) /var/log/NetworkManager -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c3 --- Comment #3 from Casual J. Programmer 2008-03-21 04:03:16 MST --- Created an attachment (id=203311) --> (https://bugzilla.novell.com/attachment.cgi?id=203311) dmesg -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c4 --- Comment #4 from Casual J. Programmer 2008-03-21 04:04:55 MST --- iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:04:0E:A4:4F:A7 ESSID:">manus manum lavat<" Mode:Master Channel:3 Frequency:2.422 GHz (Channel 3) Quality=93/100 Signal level=-36 dBm Noise level=-127 dBm Encryption key:on IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s 6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Extra:tsf=0000001bda1057e0 Cell 02 - Address: 00:18:84:11:BB:51 ESSID:"FON_UMC711" Mode:Master Channel:5 Frequency:2.432 GHz (Channel 5) Quality=93/100 Signal level=-36 dBm Noise level=-127 dBm Encryption key:off Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=0000001bd4e16a6f Cell 03 - Address: 00:13:49:68:5D:20 ESSID:"ArcorTH" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=43/100 Signal level=-83 dBm Noise level=-127 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 48 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 54 Mb/s Extra:tsf=000000d2f9a89623 Cell 04 - Address: 00:04:0E:E7:DB:36 ESSID:"ksts" Mode:Master Channel:7 Frequency:2.442 GHz (Channel 7) Quality=37/100 Signal level=-87 dBm Noise level=-127 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=000001a2ea797237 Cell 05 - Address: 00:1A:2A:00:0D:7C ESSID:"Arcor-000D02" Mode:Master Channel:9 Frequency:2.452 GHz (Channel 9) Quality=55/100 Signal level=-75 dBm Noise level=-127 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : TKIP CCMP Authentication Suites (1) : PSK IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : TKIP CCMP Authentication Suites (1) : PSK Preauthentication Supported Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=0000000f14143b9e Cell 06 - Address: 00:04:0E:DB:30:04 ESSID:"RISIKO" Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Quality=84/100 Signal level=-49 dBm Noise level=-127 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=00000022a487858a Cell 07 - Address: 00:0C:CE:1D:12:AF ESSID:"Don2" Mode:Master Channel:13 Frequency:2.472 GHz (Channel 13) Quality=42/100 Signal level=-84 dBm Noise level=-127 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Extra:tsf=000006fe7abe819a Cell 08 - Address: 00:15:0C:0B:A2:04 ESSID:"FRITZ!Box Fon WLAN 7050" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=42/100 Signal level=-84 dBm Noise level=-127 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s 6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Extra:tsf=000002912da581b6 Cell 09 - Address: 00:04:0E:3E:77:A5 ESSID:"1860" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=45/100 Signal level=-82 dBm Noise level=-127 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s 6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Extra:tsf=0000003fa3829122 -- 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=372878 Magnus Boman changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-gnome@forge.provo.novell.com |tambet@novell.com -- 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=372878 User clarkt@cnsp.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c6 Clark Tompsett changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clarkt@cnsp.com --- Comment #6 from Clark Tompsett 2008-03-25 09:07:15 MST --- Cannot connect to wpa-supplicant using wpa_gui. You get a message about wpa-supplicant not running. This problem also affects the b43 driver. You can run iwlist scan and see the networks in the area. On another laptop using the rtl8180 driver, if you rmmod rtl8180 then modprobe the driver, wireless networks are then visible. Trying this with b43 still does not allow networks to be seen by NetworkManager. The first machine using the b43 driver is a clean load from A3. The 2nd laptop is an A2 load synced to factory. -- 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=372878 User clarkt@cnsp.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c8 --- Comment #8 from Clark Tompsett 2008-03-31 11:03:56 MST --- Whatever the problem is, wireless is broken. Even setting the essid in yast for the wireless and using ifup, you cannot connect to any AP. Wireless in A3 is unusable. On another machine that is an A2 install that has been updated by syncing to factory works on occasion and will show ap's and connect. Errors from dmesg: Mar 31 10:47:35 linux-xsep ifup: wlan0 Mar 31 10:47:35 linux-xsep ifup-wireless: wlan0 warning: using NO encryption Mar 31 10:47:35 linux-xsep ifup-wireless: command 'iwconfig wlan0 nick linux-xsep' returned Mar 31 10:47:35 linux-xsep ifup-wireless: Error for wireless request "Set Nickname" (8B1C) : Mar 31 10:47:35 linux-xsep ifup-wireless: SET failed on device wlan0 ; Operation not supported. -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c10 --- Comment #10 from Casual J. Programmer 2008-04-01 00:54:32 MST --- re comment #9 same here, only if wpa_supplicant started manually, nm-applet disappears. After restarting the network by service network restart the applet is back and in fact displaying networks. Also with wpa_gui connection can be made, no ip address is acquired though. /etc/wpa_supplicant/wpa_supplicant.conf will need ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel update_config=1 so wpa_gui is able to modify it. -- 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=372878 User clarkt@cnsp.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c12 --- Comment #12 from Clark Tompsett 2008-04-01 06:07:39 MST --- Currently, I cannot see any ap's in A3 with Networkmanager. Using iwlist scan, ap's are visible. Attempting to connect manually by turning off nm, I can connect and get an ip but I cannot get to any network address. I've tried rcnetwork restart several times with nm and it does no help. -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c14 --- Comment #14 from Casual J. Programmer 2008-04-27 02:06:56 MST --- Still seen on "clean" install from Beta1 DVD. -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c16 Casual J. Programmer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |n.maziachvili@linuxgear.nl --- Comment #16 from Casual J. Programmer 2008-04-29 00:08:52 MST --- (In reply to comment #15 from Nico Maziachvili)

i have clean beta1 install. wireless working fine here with same intel chip.

Do you use GNOME Desktop as well ? -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c18 --- Comment #18 from Casual J. Programmer 2008-04-29 01:16:15 MST --- Created an attachment (id=211041) --> (https://bugzilla.novell.com/attachment.cgi?id=211041) /var/log/NetworkManager -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c20 --- Comment #20 from Casual J. Programmer 2008-04-29 01:42:14 MST --- Created an attachment (id=211043) --> (https://bugzilla.novell.com/attachment.cgi?id=211043) /var/log/NetworkManager Last activity: Three times in succession selected "System >manus manum lavat< (wlan0) -- 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=372878 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c22 --- Comment #22 from Casual J. Programmer 2008-05-04 03:02:22 MST --- Also this seems to be connected to Bug 384660, if disabling eth0 (wired NIC) NetworkManager does connect to an open AP at least. Connection to WPA2 secured AP still not possible, although wpa_supplicant is running. Now at oS11.0B2 NetworkManager-gnome-0.7.0.r664-12 NetworkManager-glib-0.7.0.r3556-9 NetworkManager-0.7.0.r3556-9 wpa_supplicant-0.5.10-25 -- 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=372878 User sshaw@decriptor.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c24 --- Comment #24 from Stephen Shaw 2008-05-08 09:52:14 MST --- I just installed from the Gnome Live 32bit beta2 disc and once I added the madwifi drivers, it came right up and worked. -- 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=372878 User nine@detonation.org added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c26 Stefan Seifert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nine@detonation.org --- Comment #26 from Stefan Seifert 2008-05-30 08:37:48 MDT --- I still see this same problem with today's Factory. With an iwl3945 NetworkManager fails to start wpa_supplicant. After manually starting as suggested in comment #9, it now finds networks and successfully connected (using WEP). Is a reinstall necessary to get this fixed? Would be the first in 10 years of using SuSE... -- 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=372878 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c28 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |birger.kollstrand@googlemail.com --- Comment #28 from Tambet Ingo 2008-06-05 00:56:53 MDT --- Please attach your /var/log/NetworkManager log file here. -- 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=372878 User casualprogrammer@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c30 --- Comment #30 from Casual J. Programmer 2008-06-07 01:09:54 MDT --- This has gotten much better for me, although some issues remain. My main AP is using WPA2 and is connected to without problem. I can connect to an open AP in the vicinity, but it took a lot of tries and seemed to work at first when PC was running on battery ( sounds weird somehow ). I also can connect to a WEP128 AP at large which also took a lot of tries and only worked if the key was entered in HEX. All of the connections could be made with Windows XP, which also seems to have a higher sensitivity, as more APs are seen. For instance I could connect to an AP not shown by the applet by using "Connect to Other Wireless Network" If you want to split up issues to multiple bugs, please say so. Notebook: Fujitsu Siemens Amilo Si 1520 Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express Monitor: QUANTADISPLAY LCD Monitor 1280x800@60Hz Wireless: Intel PRO/Wireless 3945ABG Network Connection Sound: 82801G (ICH7 Family) High Definition Audio Controller Desktop: gnome-desktop-2.22.1-25 YaST GUI: yast2-control-center-qt-2.16.2-10 OS: openSUSE 11.0 (i586) VERSION = 11.0 Kernel: 2.6.25.4-10-pae NetworkManager-0.7.0.r3685-5 NetworkManager-glib-0.7.0.r3685-5 NetworkManager-gnome-0.7.0.r729-6 -- 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=372878 User casualprogrammer@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c32 --- Comment #32 from Casual J. Programmer 2008-06-07 01:24:11 MDT --- Created an attachment (id=220855) --> (https://bugzilla.novell.com/attachment.cgi?id=220855) /var/log/wpa_supplicant.log The wpa_supplicant log for good measure. -- 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=372878 User birger.kollstrand@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c34 --- Comment #34 from Birger Kollstrand 2008-06-09 00:58:45 MDT --- Created an attachment (id=220928) --> (https://bugzilla.novell.com/attachment.cgi?id=220928) NetworkManager log file -- 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=372878 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER- -- 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=372878 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c35 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |birger.kollstrand@googlemail.com --- Comment #35 from Tambet Ingo 2008-06-09 03:44:15 MDT --- Commenting the log file from #34: Jun 9 08:38:27 linux-6uqi NetworkManager: <info> Activation (wlan0/wireless): connection 'WPR' requires no security. No secrets needed. So NM thinks the AP does not use any authentication methods, tries to get an address using DHCP and fails. Does the access point WPR broadcast it's ssid (ie, is it hidden?)? Do you use knm or nm-applet? If you use knm, does it work with nm-applet (NetworkManager-gnome package)? It looks like you created that connection yourself (either using connection editor or "Connect to Other Wireless Network"), did you specify wireless security there? -- 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=372878 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c37 --- Comment #37 from Michael Meeks 2008-06-09 05:39:08 MDT --- FWIW, I'm also having no joy connecting to my un-encrypted, open access point locally - I have a 3945ABG rev2 too. -- 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=372878 User birger.kollstrand@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c39 --- Comment #39 from Birger Kollstrand 2008-06-10 04:43:36 MDT --- It seems like my wlan setup got totally messed up, and since I could not manage to find wich config files are involved, I reinstalled 11.0rc1 from scratch. And voila! I not got network connection! -- 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=372878 User gfarrell@netspeed.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c41 Geoff Farrell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gfarrell@netspeed.com.au --- Comment #41 from Geoff Farrell 2008-06-15 06:34:30 MDT --- This particular combination (Dell 1720, Intel PRO/Wireless 3945ABG) has not been able to connect under 10.3, or openSUSE11.0-RC1-KDE4-LiveCD-i386, until 11.0-RC1 was updated from the 'oss' and 'non-oss' repositories. The relevant packages were updated to: kernel-default-2.6.25.5-1.1 NetworkManager-0.7.0-r3685-5 NetworkManager-glib-0.7.0-r3685-5 NetworkManager-kde-0.7-r815970-3 iwl3945-ucode-2.14.1.5-50 The kernel-default was updated first, by itself, then the computer was re-booted. As soon as KDE became established, the wireless tray icon identified a successful connection, without any action by the user. There were three separate icons in the tray regarding network connections (as was the case with the standard 11.0-RC1 packages. Then the NetworkManager and iwl3945-ucode packages were updated. Immediately, the wireless connection was lost, and couldn't be regained just by re-booting or restarting NetworkManager. The following sequence shows the steps taken in troubleshooting the wireless connection. 'Item' numbers refer to paragraph numbers in the attachment. Overall summary, in sequence: 1. Initial attempt at connection on first boot did not connect wlan0 to WAP (Item 6). 2. First attempt at connection using 'KNetworkManager tray icon-> Connect to other network-> FarNet' did not work. It seems that exchange of 'connection secrets' was unsuccessful (Item 7). 3. Next attempt at connection using 'KNetworkManager tray icon-> Edit Connections-> FarNet-> Edit Connection, completing info, then-> Connect & Save' worked. This was probably because the correct WPA passphrase was entered instead of the existing 64-char hex string (Item 8). Despite this, subsequent entry into this dialog showed the same 64-char hex string (Item 10). This did not prove to be a barrier to future connections. 4. Selecting 'KNetworkManager tray icon-> Deactivate connection-> FarNet (wlan0)' did not deactivate the connection (Item 11). 5. Selecting 'KNetworkManager tray icon-> Deactivate connection-> Disable wireless' did disable the connection (Item 12). 6. Selecting 'KNetworkManager tray icon-> Deactivate connection-> Enable wireless' successfully re-started the connection (Item 14). 7. Selecting 'KNetworkManager tray icon-> Connect to other network-> FarNet' successfully stopped/started the connection (Item 16). 8. Selecting 'KNetworkManager tray icon-> Edit Connections-> FarNet-> Edit Connection, completing info, then-> Connect & Save' - leaving Shared Key at the 64-character version - successfully stopped/started the connection (Item 18). 9. After re-booting the computer, the connection was established automatically, very quickly after KDE started; no user intervention was required (Item 20). *** Observations. 1. The 'FarNet' Shared Key had been entered with the original 11.0-RC1-KDE4-LiveCD-i386 version of KNetworkManager (NetworkManager-kde), before the updated version was installed from the 'oss' repository (NetworkManager-kde-0.7r815970-3). It probably had to be re-entered before the new version stored it correctly, or could access it correctly. After this, wireless connections performed without fault. 2. Regardless of 1a, it is confusing to the user to see the 'wrong' Shared Key in that dialog. This seems to be a regression from 10.3, which showed this behaviour. The original 11.0-RC1 version distributed in the LiveCD showed the 'correct' ASCII Shared Key (in the user's eyes, at least). This behaviour could have been introduced in the bringing together of the tray icons, which was mentioned in the ChangeLog for the updated version. 3. The default location of 'wpa_supplicant.conf' (at /etc/wpa_supplicant/wpa_supplicant.conf') is probably wrong. NetworkManager works correctly in the traditional /etc/wpa_supplicant.conf location. 4. Correct operation of NetworkManager in connecting to an Intel PRO/Wireless 3945ABG device has been confirmed. -- 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=372878 User gfarrell@netspeed.com.au added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c43 --- Comment #43 from Geoff Farrell 2008-06-15 22:05:21 MDT --- The issue seems to be with the file /home/<user>/.kde/share/config/knetworkmanagerrc. It has the 64-char hex string in the definition of section: [ConnectionSecrets_<16-char ASCII string>_802-11-wireless-security] Type=802-11-wireless-security Value_psk=<string><64-char hex string></string>\n It is the same 64-char hex string that appears when accessing the 'KNetworkManager tray icon-> Edit Connections-> FarNet-> Edit Connection' set of dialogs. Changing this entry to: [ConnectionSecrets_<16-char ASCII string>_802-11-wireless-security] Type=802-11-wireless-security Value_psk=<string></string>\n allowed the wlan0 connection to be made. However, despite changing knetworkmanagerrc content, the same 64-bit char hex string appears in any subsequent connection attempt in the dialogs accessed through 'KNetworkManager tray icon-> Edit Connections-> FarNet-> Edit Connection'. If something is supposed to change that to the raw 20-char ASCII passphrase input by the user, and pass it along to wpa_supplicant, then it's not happening. -- 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=372878 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c45 --- Comment #45 from Michael Meeks 2008-06-17 05:48:38 MDT --- Sure; I have RC3 with my iwl3945 - DHCP appears to fail horribly, and only by setting a static IP / gateway etc. can I get working networking [ which in itself seems extremely curious ]. Other machines attached to the same network wirelessly appear to work well. Tambet, sorry - I've not got time now (snatched minutes from baby) to follow your instructions. -- 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=372878 User quentin.jackson@exclamation.co.nz added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c47 Quentin Jackson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |quentin.jackson@exclamation.co.nz --- Comment #47 from Quentin Jackson 2008-06-18 02:47:08 MDT --- Sorry guys added to wrong bug :( -- 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=372878 User tonussi@farmaco.ufsc.br added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c49 Carlos Tonussi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tonussi@farmaco.ufsc.br Version|RC 1 |Final --- Comment #49 from Carlos Tonussi 2008-07-27 18:57:11 MDT --- Well, I think this is the right place. I am also having problems to connect to wireless router with this version of opensuse (11). The knetworkmanager do not connect, although it sees all networks in the neighborhood. It also get the shared key I put in the wireless settings of a windows XP in another machine, which is getting the network correctly. I'm using an Acer aspire 5710-6139 notebook with intel pro 3965 wireless. When I was using opensuse 10.3 on it, I never had problems with the wireless connection. As I realize in the lines above it seems that there is no solution yet. I updated knetworkmanager to the version 0.7r826733-7.1 from kde:backports repository. I would downgrade to 10.3 if I could find the rpms of alsa 1.0.15 again, since the 1.0.14 version shipped with 10.3 did not make the sound to work in this notebook. But this is not the topic here.... -- 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=372878 User tonussi@farmaco.ufsc.br added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c51 --- Comment #51 from Carlos Tonussi 2008-07-29 19:37:11 MDT --- I've done a new install. However, I just found that knmanager connects to any non encrypted wireless network. So, it seems that the problem is the way knm is facing the encryption protocols. Thus, I have disabled the router security protocols. Then, I narrowed the ip range to only those needed in my network, and enabled the lease of static ip for a specific mac address. This circumvented the bug of KNM, but left my network without security. -- 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=372878 User n.maziachvili@linuxgear.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=372878#c53 --- Comment #53 from Nico Maziachvili 2008-07-30 03:34:14 MDT --- i confirm Thomases experiences (comment 52). same intel 3945 chip here. in my case most of the time knetworkmanager doesn't even display available networks (while 'iwlist scan' does show them). often even being connected to my own network it still doesn't display it as available!!! connecting to network takes at least 30 seconds. i have noticed strange behaviour: when KNM connects to network and shows it on the list as available (which is not often) i know that if i suspend to ram it will reconnect to network when coming from suspend. in all other cases it fails to reconnect. -- 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.