Networkmanager does not work

krishnarao · 2007-11-02 23:36:35

Hi!
I am using Arch Core Dump with kernet 2.6.22-suspend2. I've not had problems with networking before but after the last upgrade network manager has stopped working with the following output on /var/log/messages.log. I did try removing dhcp and reinstalling dhclient but the solution still did not work
Nov 2 23:19:15 kpad31 NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
Nov 2 23:19:15 kpad31 NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Nov 2 23:19:15 kpad31 NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1
Nov 2 23:19:15 kpad31 NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1
Nov 2 23:19:16 kpad31 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Nov 2 23:19:20 kpad31 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11

The network has a wireless router at 192.168.0.1

franzb · 2007-11-03 00:09:55

I think I've got a similar problem. My wireless connection only ever lasts for about 1 to 2 minutes.

Here's the relevant part of messages.log:

Nov  3 00:39:34 seoul dhclient: bound to 192.168.0.101 -- renewal in 236134 seconds.
Nov  3 00:39:34 seoul NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth1
Nov  3 00:39:34 seoul NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
Nov  3 00:39:34 seoul NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) started...
Nov  3 00:39:34 seoul dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name
Nov  3 00:39:34 seoul dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.domain_name
Nov  3 00:39:34 seoul dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain
Nov  3 00:39:34 seoul dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers
Nov  3 00:39:34 seoul NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon:
Nov  3 00:39:34 seoul NetworkManager: <info>    address 192.168.0.101
Nov  3 00:39:34 seoul NetworkManager: <info>    netmask 255.255.255.0
Nov  3 00:39:34 seoul NetworkManager: <info>    broadcast 192.168.0.255
Nov  3 00:39:34 seoul NetworkManager: <info>    gateway 192.168.0.1
Nov  3 00:39:34 seoul NetworkManager: <info>    nameserver 192.168.0.1
Nov  3 00:39:34 seoul NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov  3 00:39:34 seoul NetworkManager: <info>  Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
Nov  3 00:39:34 seoul NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Nov  3 00:39:35 seoul NetworkManager: <info>  Activation (eth1) Finish handler scheduled.
Nov  3 00:39:35 seoul NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Nov  3 00:39:35 seoul NetworkManager: <info>  Activation (eth1) successful, device activated.
Nov  3 00:39:48 seoul NetworkManager: <info>  eth1: link timed out.
Nov  3 00:39:48 seoul NetworkManager: <info>  nm_device_set_active_link start
Nov  3 00:39:48 seoul NetworkManager: <info>  nm_policy_device_change_check:: old_dev has_link? 1
Nov  3 00:39:48 seoul NetworkManager: <info>  SWITCH: terminating current connection 'eth1' because it's no longer valid.
Nov  3 00:39:48 seoul NetworkManager: <info>  Deactivating device eth1.

Anybody got an idea what could be causing this?

franzb · 2007-11-03 00:33:21

krishnarao, how is your wireless access point configured? I went from WEP back to WPA and now it seems to work for me again. Strange anyway...

I'm not really sure what is causing this.

I found also in my rc.conf.pacnew a new comment which says not to enable dhcp for wireless interfaces, so I commented that one out.

circleback · 2007-11-03 04:31:30

I am tearing my hair out trying to get networkmanager to work. Can you post your rc.conf where it says not to enable dhcp for wireless interfaces?

Damnshock · 2007-11-03 09:43:20

# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
# Don't use this for wireless interfaces, see network profiles below

Anyway, I'm not sure that works with networkmanager....

PS: yes, networkmanager doesn't work for me either

krishnarao · 2007-11-03 09:57:19

The wireless router has WEP encryption only and the reason I don't use WPA is that my other laptop has a RAlink card. I'm able to connect well with wifi-radar and on command line but the knetworkmanager is not able to establish the connection.

This is the output of messages.log when networkmanager tries to make the connection
Nov 3 09:46:12 kpad31 NetworkManager: <info> SUP: response was 'OK'
Nov 3 09:46:12 kpad31 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Nov 3 09:46:12 kpad31 NetworkManager: <info> SUP: response was 'OK'
Nov 3 09:46:12 kpad31 NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Nov 3 09:46:12 kpad31 NetworkManager: <info> SUP: response was 'OK'
Nov 3 09:46:12 kpad31 NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Nov 3 09:46:12 kpad31 NetworkManager: <info> SUP: response was 'OK'
Nov 3 09:46:12 kpad31 NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Nov 3 09:46:16 kpad31 NetworkManager: <info> nm_device_set_active_link start
Nov 3 09:46:16 kpad31 NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Conn
ected to access point 'modem'.
Nov 3 09:46:16 kpad31 NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 3 09:46:16 kpad31 NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Nov 3 09:46:17 kpad31 NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
Nov 3 09:46:17 kpad31 NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Nov 3 09:46:17 kpad31 NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1
Nov 3 09:46:17 kpad31 NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1
Nov 3 09:46:18 kpad31 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
Nov 3 09:46:24 kpad31 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
Nov 3 09:46:37 kpad31 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
Nov 3 09:46:48 kpad31 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
Nov 3 09:47:02 kpad31 NetworkManager: <info> Device 'eth1' DHCP transaction took too long (>45s), stopping it.
Nov 3 09:47:02 kpad31 dhclient: There is already a pid file /var/run/dhclient-eth1.pid with pid 6276
Nov 3 09:47:02 kpad31 dhclient: killed old client process, removed PID file
Nov 3 09:47:03 kpad31 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) scheduled...
Nov 3 09:47:03 kpad31 NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth1
Nov 3 09:47:03 kpad31 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) started...
Nov 3 09:47:03 kpad31 NetworkManager: <info> Activation (eth1) New wireless user key requested for network 'modem'.
Nov 3 09:47:03 kpad31 NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Timeout) complete.
Nov 3 09:47:05 kpad31 dhclient: DHCPRELEASE on eth1 to 192.168.0.1 port 67
Nov 3 09:47:05 kpad31 NetworkManager: <info> DHCP daemon state is now 11 (unknown) for interface eth1
Nov 3 09:47:05 kpad31 NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth1
Nov 3 09:47:06 kpad31 NetworkManager: <WARN> nm_dbus_get_user_key_for_network_cb(): nm_dbus_get_user_key_for_network_cb()
: dbus returned an error. (org.freedesktop.NetworkManagerInfo.GetKeyError) org.freedesktop.NetworkManagerInfo.GetKeyError
Nov 3 09:47:06 kpad31 NetworkManager: <info> Activation (eth1) failure scheduled...
Nov 3 09:47:06 kpad31 NetworkManager: <info> Activation (eth1) failed for access point (modem)
Nov 3 09:47:06 kpad31 NetworkManager: <info> Activation (eth1) failed.

This is the messages.log output with wifi-radar
Nov 3 09:47:21 kpad31 dhcpcd[6316]: eth1: hardware address = 00:0c:f1:0e:41:dc
Nov 3 09:47:21 kpad31 dhcpcd[6316]: eth1: broadcasting for a lease
Nov 3 09:47:23 kpad31 NetworkManager: <info> nm_policy_device_change_check:: !old_dev && !new_dev!!
Nov 3 09:47:24 kpad31 dhcpcd[6316]: eth1: offered 192.168.0.5 from 192.168.0.1
Nov 3 09:47:24 kpad31 dhcpcd[6316]: eth1: checking 192.168.0.5 is available on attached networks
Nov 3 09:47:25 kpad31 dhcpcd[6316]: eth1: leased 192.168.0.5 for 259200 seconds
Nov 3 09:47:25 kpad31 dhcpcd[6316]: eth1: no renewal time supplied, assuming 129600 seconds
Nov 3 09:47:25 kpad31 dhcpcd[6316]: eth1: no rebind time supplied, assuming 226800 seconds
Nov 3 09:47:25 kpad31 dhcpcd[6316]: eth1: adding IP address 192.168.0.5/24
Nov 3 09:47:25 kpad31 dhcpcd[6316]: eth1: adding default route via 192.168.0.1 metric 0
Nov 3 09:47:25 kpad31 dhcpcd[6316]: eth1: adding route to 169.254.0.0/16 metric 0
Nov 3 09:47:25 kpad31 dhcpcd[6316]: eth1: exiting
Nov 3 09:47:48 kpad31 NET: Registered protocol family 10
Nov 3 09:47:48 kpad31 lo: Disabled Privacy Extensions
Nov 3 09:47:48 kpad31 ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 3 09:47:48 kpad31 Mobile IPv6
Nov 3 09:49:33 kpad31 NetworkManager: <info> nm_policy_device_change_check:: !old_dev && !new_dev!!

I still can't understand why dhclient sends dhcp request to 255.255.255.255 when it should be doing so to 192.168.0.1
Is it that the avahi daemon is not running

sykesm · 2007-11-03 11:20:25

some of the things I tried which got me reconnected but hasn´t resolved the basic problem yet

http://bbs.archlinux.org/viewtopic.php? … 57#p295457

franzb · 2007-11-03 12:51:52

krishnarao I can confirm that I get the same errors (dhcp related) that show up in your log when I try to connect to a WEP access point with knetworkmanager. Maybe the upstream maintainers have listed this in their bug db? I will have a look. If not I'll submit it as a bug.

krishnarao · 2007-11-03 22:11:01

I can confirm that I'm able to connect successfully by commandline, wifi-radar and wlassistant.

Arch Linux

#1 2007-11-02 23:36:35

Networkmanager does not work

#2 2007-11-03 00:09:55

Re: Networkmanager does not work

#3 2007-11-03 00:33:21

Re: Networkmanager does not work

#4 2007-11-03 04:31:30

Re: Networkmanager does not work

#5 2007-11-03 09:43:20

Re: Networkmanager does not work

#6 2007-11-03 09:57:19

Re: Networkmanager does not work

#7 2007-11-03 11:20:25

Re: Networkmanager does not work

#8 2007-11-03 12:51:52

Re: Networkmanager does not work

#9 2007-11-03 22:11:01

Re: Networkmanager does not work

Board footer