[Bug 687676] New: connecting with knetworkmanager does not work.
https://bugzilla.novell.com/show_bug.cgi?id=687676 https://bugzilla.novell.com/show_bug.cgi?id=687676#c0 Summary: connecting with knetworkmanager does not work. Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rens.groenewegen@xs4all.nl QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 connecting with knetworkmanager does not work. the active networks are shown, one configures the parameters, encryption type etc. is correctly detected, but the network never gets accepted ( the wifi does not establish connection with the accesspoint ) the accesspoint sees the wificlient register and deregister and no further special events or log entries. ( fritz!box 7340, VDSL2/wifi/router ) Reproducible: Always Steps to Reproduce: 1.select new connection 2.select SSID 3.fill in security ( WPA2, ccmp / tkip ) 4. click save & connect Actual Results: networkmanager fails to connect. Expected Results: expected to be connected to my wifi. I have seen this bug in 11.2 and 11.3 as well, reason why I did not switch from 11.1. I reported it, but cannot find this bug anymore, it is the same. This bug makes opensuse 11.4 useless for "normal" users. You need to be scripting savvy etc. to get it to work anyway.. This 11.4 install was build with Suse Studio. ( booting from USB stick ) If I configure the network to be managed traditional, ( ifup/ifdown ) I can make the wifi work with a little script and a simple config file containing the password phrase ( taken straight from the man page ..... ) _________________________________________________________ ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel # home network; allow all valid ciphers network={ ssid="seg0ka-lan-rgb" key_mgmt=WPA-PSK psk="mypasswordgoeshere" } _________________________________________________________ that's all, and it works flawlessly..... -- 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=687676 https://bugzilla.novell.com/show_bug.cgi?id=687676#c1 --- Comment #1 from rens groenewegen <rens.groenewegen@xs4all.nl> 2011-04-14 20:34:20 UTC --- log when connecting with script, no networkmanager Apr 14 21:37:21 linux dhcpcd[3289]: eth0: broadcasting for a lease Apr 14 21:37:32 linux ifdown: wlan0 device: RaLink RT2860 Apr 14 21:37:33 linux dhcpcd[8063]: wlan0: sending signal 15 to pid 7165 Apr 14 21:37:33 linux dhcpcd[8063]: wlan0: exiting Apr 14 21:37:33 linux dhcpcd[7165]: wlan0: received SIGTERM, stopping Apr 14 21:37:33 linux dhcpcd[7165]: wlan0: removing IP address 192.168.1.42/24 Apr 14 21:37:33 linux avahi-daemon[4827]: Withdrawing address record for 192.168.1.42 on wlan0. Apr 14 21:37:33 linux avahi-daemon[4827]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.42. Apr 14 21:37:33 linux avahi-daemon[4827]: Interface wlan0.IPv4 no longer relevant for mDNS. Apr 14 21:37:33 linux dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Apr 14 21:37:33 linux dns-resolver: You can find my version in /etc/resolv.conf.netconfig Apr 14 21:37:33 linux dhcpcd-hook: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Apr 14 21:37:33 linux dhcpcd-hook: You can find my version in /etc/resolv.conf.netconfig ... Apr 14 21:37:33 linux dhcpcd[7165]: wlan0: exiting Apr 14 21:37:34 linux dhcpcd[3289]: eth0: received SIGTERM, stopping Apr 14 21:37:34 linux dhcpcd-hook: ls: cannot access /var/run/netconfig//eth0/: No such file or directory Apr 14 21:37:34 linux dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... Apr 14 21:37:34 linux dns-resolver: You can find my version in /etc/resolv.conf.netconfig Apr 14 21:37:34 linux dhcpcd[3289]: eth0: exiting Apr 14 21:37:57 linux ifdown: wlan0 device: RaLink RT2860 Apr 14 21:37:58 linux dhcpcd[8433]: wlan0: dhcpcd not running Apr 14 21:37:58 linux dhcpcd[8433]: wlan0: exiting Apr 14 21:38:04 linux kernel: [ 326.011830] RX DESC ffff8800b7181000 size = 2048 Apr 14 21:38:04 linux kernel: [ 326.012386] <-- RTMPAllocTxRxRingMemory, Status=0 Apr 14 21:38:04 linux kernel: [ 326.015113] 1. Phy Mode = 0 Apr 14 21:38:04 linux kernel: [ 326.015117] 2. Phy Mode = 0 Apr 14 21:38:04 linux kernel: [ 326.042197] 3. Phy Mode = 0 Apr 14 21:38:04 linux kernel: [ 326.045075] MCS Set = 00 00 00 00 00 Apr 14 21:38:04 linux kernel: [ 326.046696] <==== rt28xx_init, Status=0 Apr 14 21:38:04 linux kernel: [ 326.046764] 0x1300 = 000a4260 Apr 14 21:38:04 linux dhcpcd[8551]: wlan0: hardware address = 00:15:af:7a:d2:ad Apr 14 21:38:04 linux dhcpcd[8551]: wlan0: broadcasting for a lease Apr 14 21:38:04 linux dhcpcd[8551]: wlan0: sending DHCP_DISCOVER with xid 0x9bb2319 Apr 14 21:38:04 linux dhcpcd[8551]: wlan0: waiting for 10 seconds Apr 14 21:38:07 linux dhcpcd[8551]: wlan0: sending DHCP_DISCOVER with xid 0x9bb2319 Apr 14 21:38:09 linux kernel: [ 331.170491] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 987 Apr 14 21:38:09 linux kernel: [ 331.170878] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Apr 14 21:38:13 linux dhcpcd[8551]: wlan0: sending DHCP_DISCOVER with xid 0x9bb2319 Apr 14 21:38:13 linux dhcpcd[8551]: wlan0: got a packet with xid 0x9bb2319 Apr 14 21:38:13 linux dhcpcd[8551]: wlan0: offered 192.168.1.42 from 192.168.1.250 Apr 14 21:38:13 linux dhcpcd[8551]: wlan0: exiting Apr 14 21:38:13 linux dhcpcd[8552]: wlan0: dhcpcd 3.2.3 starting Apr 14 21:38:13 linux dhcpcd[8552]: wlan0: hardware address = 00:15:af:7a:d2:ad Apr 14 21:38:13 linux dhcpcd[8552]: wlan0: broadcasting for a lease Apr 14 21:38:13 linux dhcpcd[8552]: wlan0: offered 192.168.1.42 from 192.168.1.250 Apr 14 21:38:13 linux dhcpcd[8552]: wlan0: got subsequent offer of 192.168.1.43, ignoring Apr 14 21:38:13 linux dhcpcd[8552]: wlan0: checking 192.168.1.42 is available on attached networks Apr 14 21:38:14 linux dhcpcd[8552]: wlan0: leased 192.168.1.42 for 259200 seconds Apr 14 21:38:14 linux dhcpcd[8552]: wlan0: adding IP address 192.168.1.42/24 Apr 14 21:38:14 linux dhcpcd[8552]: wlan0: adding default route via 192.168.1.1 metric 0 Apr 14 21:38:14 linux dhcpcd[8552]: wlan0: adding route to 169.254.0.0/16 metric 0 Apr 14 21:38:14 linux avahi-daemon[4827]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.42. Apr 14 21:38:14 linux dhcpcd[8552]: wlan0: exiting Apr 14 21:38:14 linux avahi-daemon[4827]: New relevant interface wlan0.IPv4 for mDNS. Apr 14 21:38:14 linux avahi-daemon[4827]: Registering new address record for 192.168.1.42 on wlan0.IPv4. li -- 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=687676 https://bugzilla.novell.com/show_bug.cgi?id=687676#c2 --- Comment #2 from rens groenewegen <rens.groenewegen@xs4all.nl> 2011-04-14 20:36:32 UTC --- ==> The config file: linux:~ # cat thuis.cnf ctrl_interface=/var/run/wpa_supplicant network={ ssid="seg0ka-lan-rgb" key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk="its_a_secret" } ==> The dowlan script, that takes a conf file : linux:~ # cat dowlan #!/usr/bin/ksh set -x function setoff { echo setoff # set -x ifdown wlan0 ifconfig wlan0 down psg -nK wpa_supplicant psg -nK dhcpcd psg -nK dhclient } function iwscan { echo iwscan # set -x iwlist wlan0 scan > /tmp/wilist return $? } function setonwpa { echo setonwpa # set -x [ $# -lt 1 ] && return 1 echo killing all daemons.... psg -nK wpa_supplicant psg -nK dhcpcd psg -nK dhclient echo sleep 5 sleep 5 echo resuming.... iwconfig|grep wlan0 ifconfig|grep wlan0 wpa_supplicant -i wlan0 -c $1 -B -dd return $? } function testdhc { echo testdhc # set -x err=`dhcpcd-test wlan0 2>&1|grep -c -i timed` return $err # ok = 0, error = 1 } function dodhc { echo dodhc # set -x dhcpcd wlan0 return $? } function waitforlink { echo waitforlink while [ ` iwconfig |grep -c -i not-associated ` -gt 0 ] do sleep 2 echo -n "." done return $? } setoff while true do iwscan setonwpa $1 && waitforlink && testdhc && dodhc && break 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=687676 https://bugzilla.novell.com/show_bug.cgi?id=687676#c3 --- Comment #3 from rens groenewegen <rens.groenewegen@xs4all.nl> 2011-04-14 21:47:24 UTC --- after installng kdewallet manager, the problem is solved. this is the messages log for a failed attempt, prior to installing kdewallet manager Mar 26 22:59:10 linux NetworkManager[12654]: <info> Trying to start the supplicant... Mar 26 22:59:10 linux kernel: [ 739.836022] <==== rt28xx_init, Status=0 Mar 26 22:59:10 linux kernel: [ 739.836091] 0x1300 = 000a4260 Mar 26 22:59:10 linux dns-resolver: You can find my version in /etc/resolv.conf.netconfig Mar 26 22:59:10 linux NetworkManager[12654]: <info> (wlan0): supplicant manager state: down -> idle Mar 26 22:59:10 linux NetworkManager[12654]: <info> (wlan0): device state change: 2 -> 3 (reason 0) Mar 26 22:59:10 linux NetworkManager[12654]: <info> (wlan0): supplicant interface state: starting -> ready Mar 26 22:59:10 linux nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/netcontrol_servic es' exited with error status 127. Mar 26 22:59:15 linux kernel: [ 745.099974] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 1 021 Mar 26 22:59:15 linux kernel: [ 745.100309] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 22:59:20 linux kernel: [ 750.850873] ===>rt_ioctl_giwscan. 4(4) BSS returned, data->length = 8 05 Mar 26 22:59:20 linux kernel: [ 750.851028] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 22:59:26 linux kernel: [ 756.105731] ===>rt_ioctl_giwscan. 4(4) BSS returned, data->length = 8 05 Mar 26 22:59:26 linux kernel: [ 756.106096] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 22:59:31 linux kernel: [ 761.943484] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 3 87 Mar 26 22:59:31 linux kernel: [ 761.943712] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 22:59:41 linux kernel: [ 771.952539] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 6 21 Mar 26 22:59:41 linux kernel: [ 771.952831] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 22:59:48 linux kernel: [ 778.020113] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 6 21 Mar 26 22:59:48 linux kernel: [ 778.020341] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 22:59:53 linux kernel: [ 783.857922] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 1 021 Mar 26 22:59:53 linux kernel: [ 783.858254] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 22:59:59 linux kernel: [ 789.900126] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 6 21 Mar 26 22:59:59 linux kernel: [ 789.900365] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 23:00:05 linux kernel: [ 795.840471] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 6 21 Mar 26 23:00:05 linux kernel: [ 795.840774] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 23:00:08 linux kernel: [ 798.106235] ===>rt_ioctl_giwscan. 4(4) BSS returned, data->length = 8 05 Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0) starting connection 'seg0ka-lan -rgb' Mar 26 23:00:08 linux NetworkManager[12654]: <info> (wlan0): device state change: 3 -> 4 (reason 0) Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) s cheduled... Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) s tarted... Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) c omplete. Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 26 23:00:08 linux NetworkManager[12654]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0/wireless): access point 'seg0ka- lan-rgb' has security, but secrets are required. Mar 26 23:00:08 linux NetworkManager[12654]: <info> (wlan0): device state change: 5 -> 6 (reason 0) Mar 26 23:00:08 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 26 23:00:11 linux kernel: [ 801.160081] ===>rt_ioctl_giwscan. 4(4) BSS returned, data->length = 8 05 Mar 26 23:00:11 linux kernel: [ 801.160235] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 23:00:11 linux NetworkManager[12654]: <info> (wlan0): supplicant connection state: inactive -> associated Mar 26 23:00:11 linux NetworkManager[12654]: <info> (wlan0): supplicant connection state: associated -> disconnected Mar 26 23:00:17 linux kernel: [ 807.000113] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 3 87 Mar 26 23:00:17 linux kernel: [ 807.000382] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 23:00:17 linux NetworkManager[12654]: <info> (wlan0): supplicant connection state: disconnecte d -> associated Mar 26 23:00:17 linux NetworkManager[12654]: <info> (wlan0): supplicant connection state: associated -> disconnected Mar 26 23:00:20 linux NetworkManager[12654]: <info> (wlan0): device state change: 6 -> 9 (reason 7) Mar 26 23:00:20 linux NetworkManager[12654]: <warn> Activation (wlan0) failed for access point (seg0ka -lan-rgb) Mar 26 23:00:20 linux NetworkManager[12654]: <info> Marking connection 'seg0ka-lan-rgb' invalid. Mar 26 23:00:20 linux NetworkManager[12654]: <warn> Activation (wlan0) failed. Mar 26 23:00:20 linux NetworkManager[12654]: <info> (wlan0): device state change: 9 -> 3 (reason 0) Mar 26 23:00:20 linux NetworkManager[12654]: <info> (wlan0): deactivating device (reason: 0). Mar 26 23:00:22 linux kernel: [ 812.321098] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 6 21 Mar 26 23:00:22 linux kernel: [ 812.321347] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 23:00:28 linux kernel: [ 818.160788] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 6 21 Mar 26 23:00:28 linux kernel: [ 818.161073] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 23:00:34 linux kernel: [ 823.998945] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 6 21 /secret ..skipping Mar 26 23:00:59 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 26 23:00:59 linux NetworkManager[12654]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Mar 26 23:00:59 linux NetworkManager[12654]: <info> Activation (wlan0/wireless): access point 'seg0ka- lan-rgb' has security, but secrets are required. Mar 26 23:00:59 linux NetworkManager[12654]: <info> (wlan0): device state change: 5 -> 6 (reason 0) Mar 26 23:00:59 linux NetworkManager[12654]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 26 23:01:00 linux kernel: [ 850.725671] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 3 87 Mar 26 23:01:00 linux kernel: [ 850.725935] ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Mar 26 23:01:01 linux NetworkManager[12654]: <info> (wlan0): supplicant connection state: disconnecte d -> associated Mar 26 23:01:01 linux NetworkManager[12654]: <info> (wlan0): supplicant connection state: associated -> disconnected Mar 26 23:01:03 linux NetworkManager[12654]: <info> (wlan0): device state change: 6 -> 9 (reason 7) Mar 26 23:01:03 linux NetworkManager[12654]: <warn> Activation (wlan0) failed for access point (seg0ka -lan-rgb) Mar 26 23:01:03 linux NetworkManager[12654]: <info> Marking connection 'seg0ka-lan-rgb' invalid. Mar 26 23:01:03 linux NetworkManager[12654]: <warn> Activation (wlan0) failed. Mar 26 23:01:03 linux NetworkManager[12654]: <info> (wlan0): device state change: 9 -> 3 (reason 0) Mar 26 23:01:03 linux NetworkManager[12654]: <info> (wlan0): deactivating device (reason: 0). -- 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=687676 https://bugzilla.novell.com/show_bug.cgi?id=687676#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |wstephenson@novell.com |ovo.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=687676 https://bugzilla.novell.com/show_bug.cgi?id=687676#c4 Sven Burmeister <sven.burmeister@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |sven.burmeister@gmx.net Resolution| |DUPLICATE --- Comment #4 from Sven Burmeister <sven.burmeister@gmx.net> 2011-12-08 18:44:13 UTC --- This seems to be a duplicate *** This bug has been marked as a duplicate of bug 661425 *** http://bugzilla.novell.com/show_bug.cgi?id=661425 -- 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