knetworkmanager 4.4.1 does not connect properly

Board index

Page 1 of 1 (6 posts)

Tags:

Riinse Registered Member Posts 167 Karma 2 OS	knetworkmanager 4.4.1 does not connect properly Tue Mar 09, 2010 10:43 pm Hi, I recently installed opensuse 11.2 with kde 4.4.1 on my laptop. With 11.0 and kde 3.5 it connected correctly to my wireless network (atheros wireless card, WEP security on wireless), but the current setup is giving problems: while knetworkmanager connects to the wireless network, the connection does get an ip address, but gateway and dns aren't configured. The result is that i can browse on the local network (e.g. go to 192.168.2.5 and open the configuration of my access piont) but can't reach the internet. when i use yast to setup the network, everything works fine. Can you help me getting knetworkmanager to behave properly? Kind regards, Rinse Riinse, proud to be a member of KDE forums since 2008-Oct.
bcooksley Administrator Posts 19765 Karma 87 OS	Re: knetworkmanager 4.4.1 does not connect properly Wed Mar 10, 2010 5:08 am Can you please check the content of /var/log/NetworkManager? KDE Sysadmin [img]content/bcooksley_sig.png[/img]
Riinse Registered Member Posts 167 Karma 2 OS	Re: knetworkmanager 4.4.1 does not connect properly Sun Mar 14, 2010 9:07 pm Thanks for your quick reply. I cleaned out the log file and then tried to connect with knetworkmanager. I;m getting the following output in /var/log/Knetworkmanager: Code: Select all Mar 14 21:54:07 linux-zrcg NetworkManager: <info> (wlan0): device state change: 8 -> 2 (reason 0) Mar 14 21:54:07 linux-zrcg NetworkManager: <info> (wlan0): deactivating device (reason: 0). Mar 14 21:54:07 linux-zrcg NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 6892 Mar 14 21:54:07 linux-zrcg NetworkManager: <info> (wlan0): taking down device. Mar 14 21:54:07 linux-zrcg nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1. Mar 14 21:54:12 linux-zrcg NetworkManager: <info> (wlan0): bringing up device. Mar 14 21:54:12 linux-zrcg NetworkManager: <info> (wlan0): device state change: 2 -> 3 (reason 0) Mar 14 21:54:12 linux-zrcg NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) starting connection 'draadloos_thuis' Mar 14 21:54:17 linux-zrcg NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0) Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0/wireless): access point 'draadloos_thuis' has security, but secrets are required. Mar 14 21:54:17 linux-zrcg NetworkManager: <info> (wlan0): device state change: 5 -> 6 (reason 0) Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 14 21:54:17 linux-zrcg NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x Mar 14 21:54:17 linux-zrcg NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'. Mar 14 21:54:17 linux-zrcg NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'. Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> (wlan0): device state change: 6 -> 4 (reason 0) Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 14 21:54:17 linux-zrcg NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0/wireless): connection 'draadloos_thuis' has security, and secrets exist. No new secrets needed. Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Config: added 'ssid' value 'draadloos' Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Config: added 'scan_ssid' value '1' Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Config: added 'wep_key0' value '<omitted>' Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Config: added 'wep_key1' value '<omitted>' Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0' Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 14 21:54:17 linux-zrcg NetworkManager: <info> Config: set interface ap_scan to 1 Mar 14 21:54:17 linux-zrcg NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Mar 14 21:54:22 linux-zrcg NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Mar 14 21:54:24 linux-zrcg NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating Mar 14 21:54:24 linux-zrcg NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated Mar 14 21:54:24 linux-zrcg NetworkManager: <info> (wlan0): supplicant connection state: associated -> completed Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'draadloos'. Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Mar 14 21:54:24 linux-zrcg NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0) Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. Mar 14 21:54:24 linux-zrcg NetworkManager: <info> dhclient started with pid 7109 Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Mar 14 21:54:24 linux-zrcg NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit Mar 14 21:54:24 linux-zrcg NetworkManager: <info> DHCP: device wlan0 state changed preinit -> reboot Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled... Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started... Mar 14 21:54:24 linux-zrcg NetworkManager: <info> address 192.168.2.2 Mar 14 21:54:24 linux-zrcg NetworkManager: <info> prefix 24 (255.255.255.0) Mar 14 21:54:24 linux-zrcg NetworkManager: <info> gateway 192.168.2.1 Mar 14 21:54:24 linux-zrcg NetworkManager: <info> nameserver '192.168.2.1' Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. Mar 14 21:54:24 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Mar 14 21:54:25 linux-zrcg NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0) Mar 14 21:54:25 linux-zrcg NetworkManager: <info> Activation (wlan0) successful, device activated. Mar 14 21:54:25 linux-zrcg NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. Mar 14 21:54:25 linux-zrcg nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1. looks like the last line is the problem? This is the output of route -n using knetworkmanager: Code: Select all `Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo` And this with yast: Code: Select all Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 wlan0 Regards, Rinse Riinse, proud to be a member of KDE forums since 2008-Oct.
bcooksley Administrator Posts 19765 Karma 87 OS	Re: knetworkmanager 4.4.1 does not connect properly Mon Mar 15, 2010 5:34 am I have that last line present on my system also, yet it sets the default route ok... yet the log also indicates that your machine recieves the default route correctly. Can you please make sure that no manual settings for any form of IP settings exist in KNetworkManager? KDE Sysadmin [img]content/bcooksley_sig.png[/img]
Riinse Registered Member Posts 167 Karma 2 OS	Re: knetworkmanager 4.4.1 does not connect properly Wed Mar 17, 2010 8:25 pm Checked, and i cannot find any manual configuration present. I also wiped the home directory after this new installation of opensuse, so i don't expect there can be anything left of any old configuration of previous installations. I also tried if installing the madwifi kernel module would make any difference. Although knetworkmanager connects a lot faster than with athk_5, the problem still exists. The odd thing is that the previous installation, using an older version of suse, (and afaik kde 4.2 or 4.3) worked without any problems. Riinse, proud to be a member of KDE forums since 2008-Oct.
bcooksley Administrator Posts 19765 Karma 87 OS	Re: knetworkmanager 4.4.1 does not connect properly Thu Mar 18, 2010 4:36 am It is unlikely to be your kernel, given that it actually connects to the network without issues... It might be possible that the connection configuration is somehow damaged, try recreating it. Otherwise, try asking wstephenson in #solid on Freenode. KDE Sysadmin [img]content/bcooksley_sig.png[/img]