LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-14-2013, 03:11 AM   #1
qlands
Member
 
Registered: Sep 2010
Posts: 53

Rep: Reputation: 0
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
 
Old 11-14-2013, 05:24 AM   #2
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,409

Rep: Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835
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.
 
Old 11-14-2013, 07:16 AM   #3
qlands
Member
 
Registered: Sep 2010
Posts: 53

Original Poster
Rep: Reputation: 0
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
 
Old 11-14-2013, 07:34 AM   #4
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,409

Rep: Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835
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

Last edited by allend; 11-14-2013 at 07:50 AM.
 
2 members found this post helpful.
Old 01-21-2014, 07:49 PM   #5
vtel57
Member
 
Registered: Jul 2006
Location: Tampa, FL, USA
Distribution: Slackware64
Posts: 858

Rep: Reputation: 88
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
 
Old 03-12-2014, 02:25 AM   #6
yenn
Member
 
Registered: Jan 2011
Location: Czech Republic
Distribution: Slackware, Gentoo
Posts: 153

Rep: Reputation: 21
Quote:
Originally Posted by allend View Post
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.
 
  


Reply

Tags
connection, ipv6, networkmanager, wired


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot connect to ethernet with wired connection Ubuntu 12.10 tontoOz Ubuntu 5 03-13-2013 07:30 AM
[SOLVED] why my wireless can't connect without wired connection? wubai Linux - Networking 19 10-25-2012 09:45 PM
Unable to connect a wired connection requesting help lonely14 Linux - Newbie 1 07-09-2012 03:41 AM
How to get wired and wireless connection at the same time using NetworkManager? veeruk101 Linux - Newbie 3 07-04-2011 10:58 PM
Slackware 13.0 & WICD - Slow wired connection, no wireless connection xTyrant Linux - Laptop and Netbook 2 10-14-2009 11:58 PM


All times are GMT -5. The time now is 02:48 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration