LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   NetworkManager cannot connect to wired connection in Slackware 14.1 (https://www.linuxquestions.org/questions/slackware-14/networkmanager-cannot-connect-to-wired-connection-in-slackware-14-1-a-4175484525/)

qlands 11-14-2013 03:11 AM

NetworkManager cannot connect to wired connection in Slackware 14.1
 
Hi,

I recently upgraded to stalckware 14.1 but NetworkManager cannot connect to the wired connection:

I get in:
syslog
Code:

Nov 14 11:59:06 mdarkstar NetworkManager[3423]: <warn> (pid 3767) unhandled DHCP event for interface wlan0
Nov 14 11:59:06 mdarkstar NetworkManager[3423]: <warn> Connection disconnected (reason -3)
Nov 14 11:59:06 mdarkstar NetworkManager[3423]: <warn> Connection disconnected (reason -3)
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <warn> the dhcpcd backend does not support IPv6.
Nov 14 11:59:10 mdarkstar dhcpcd[3943]: dhcpcd already running on pid 3634 (/var/run/dhcpcd-eth0.pid)
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <warn> Activation (eth0) failed for connection 'Wired connection 1'
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: stop: assertion `priv->pid > 0' failed

messages
Code:

Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) starting connection 'Wired connection 1'
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> NetworkManager state is now CONNECTING
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> dhcpcd started with pid 3943
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): DHCPv4 client pid 3943 exited with status 1
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> NetworkManager state is now DISCONNECTED
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Marking connection 'Wired connection 1' invalid.
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): deactivating device (reason 'none') [0]
Nov 14 11:59:10 mdarkstar NetworkManager[3423]: <info> (eth0): canceled DHCP transaction, DHCP client pid

And a restart to rc.inet1
Code:

Polling for DHCP server on interface eth0:
dhcpcd[4066]: version 6.0.5 starting
dhcpcd[4066]: eth0: waiting for carrier
dhcpcd[4066]: eth0: carrier acquired
dhcpcd[4066]: eth0: soliciting an IPv6 router
dhcpcd[4066]: eth0: soliciting a DHCP lease
dhcpcd[4066]: eth0: offered 172.26.17.56 from 172.26.0.165
dhcpcd[4066]: eth0: leased 172.26.17.56 for 259200 seconds
dhcpcd[4066]: eth0: adding host route to 172.26.17.56 via 127.0.0.1
dhcpcd[4066]: eth0: adding route to 172.26.17.0/24
dhcpcd[4066]: eth0: adding default route via 172.26.17.254
dhcpcd[4066]: forked to background, child pid 4112

In the configuration of NetworkManager to the wired connection I have IPv6 disabled because I am not connecting to a IPV6 network.

Any idea what is wrong or what do I need to change

Thanks,
Carlos

allend 11-14-2013 05:24 AM

From the email to root titled " Welcome to Linux (Slackware 14.1)! "
Quote:

With NetworkManager or wicd, it's
a good idea to remove any existing network configuration in
/etc/rc.d/rc.inet1.conf first. This can be done by running netconfig
and setting the machine to use loopback. Then, if you're using
NetworkManager run it a second time and select NetworkManager.

qlands 11-14-2013 07:16 AM

I followed this thread http://www.linuxquestions.org/questi...-a-4175484128/

where its said change DHCP[0]="no" in rc.inet1.conf . After that and a restart NetworkManager works fine with my wired connection even if the network I am connecting to is DHCP

Who can explain this? Bug?

Thanks,
Carlos

allend 11-14-2013 07:34 AM

Quote:

Nov 14 11:59:10 mdarkstar dhcpcd[3943]: dhcpcd already running on pid 3634 (/var/run/dhcpcd-eth0.pid)
NetworkManager expects to be able to start dhcpcd. With an entry DHCP[0]="yes" in /etc/rc.d/rc.inet1.conf, the dhcpcd daemon has already been started. You need to eliminate the conflict by not starting dhcpcd from an entry in rc.inet1.conf

vtel57 01-21-2014 07:49 PM

allend,

Thank you! I just ran across this same issue in a 32 bit install on my old Dell Latitude 610. I was banging my head against the desk. I couldn't figure out why I was having eth0 issues with this installation when my recent 14.0 was working fine. The diff, you reminded me above, is that I was NOT using Network Manager in the previous install, so NM was having a conflict at startup because I already had the dhcpcd started at boot. Killed DHCP in inet1.conf. All's well. :)

Regards,

~Eric

yenn 03-12-2014 02:25 AM

Quote:

Originally Posted by allend (Post 5064201)
From the email to root titled " Welcome to Linux (Slackware 14.1)! "
Code:

With NetworkManager or wicd, it's
a good idea to remove any existing network configuration in
/etc/rc.d/rc.inet1.conf first. This can be done by running netconfig
and setting the machine to use loopback. Then, if you're using
NetworkManager run it a second time and select NetworkManager.


Well, wicd works fine with already started dhcpcd and I was always wondering what is wrong with Network Manager. Although now I see that combining these two things might not be the brightest idea.


All times are GMT -5. The time now is 01:33 AM.