Arch Linux

thesbros

Member

Registered: 2015-10-07

Posts: 8

[SOLVED] NetworkManager won't connect on startup

Hello, when I startup/reboot, NetworkManager won't connect to the wired network. Restarting the NetworkManager service fixes it.

Here is the service status at startup:

● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2015-10-07 10:29:56 PDT; 3min 34s ago
 Main PID: 269 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           └─269 /usr/bin/NetworkManager --no-daemon

Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (lo): link connected
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  startup complete
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  wpa_supplicant running
Oct 07 10:29:56 desktop NetworkManager[269]: <warn>  (eth0): failed to find device 2 'eth0' with udev
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (eth0): new Ethernet device (carrier: OFF, driver: 'e1000e', ifindex: 2)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (eth0): interface index 2 renamed iface from 'eth0' to 'enp0s25'
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 07 10:29:58 desktop NetworkManager[269]: <info>  (enp0s25): link connected
Oct 07 10:29:58 desktop NetworkManager[269]: <info>  (enp0s25): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]

Here is the service status after restart of the service:

● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2015-10-07 10:33:38 PDT; 2min 7s ago
 Main PID: 1115 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           ├─1115 /usr/bin/NetworkManager --no-daemon
           └─1120 /usr/bin/dhclient -d -q -sf /usr/lib/networkmanager/nm-dhcp-helper -pf /var/run/dhclient-enp0s25.pid -lf /var/lib/NetworkManager/dhclient-341510d6-63fd-41a2-a687-9a73365014bb-enp0s25.lease -cf /var/lib/NetworkManager/dhclient-enp0s25.conf enp0s25

Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: secondaries -> activated (reason 'none') [90 100 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  NetworkManager state is now CONNECTED_LOCAL
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  Policy set 'Wired connection 1' (enp0s25) as default for IPv4 routing and DNS.
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  Writing DNS information to /usr/bin/resolvconf
Oct 07 10:33:40 desktop dhclient[1120]: bound to 10.0.1.34 -- renewal in 40486 seconds.
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): Activation: successful, device activated.
Oct 07 10:33:45 desktop NetworkManager[1115]: <info>  startup complete

Anyone have any idea what's going on?

Last edited by thesbros (2015-10-08 04:17:35)

c3kay

Member

From: New Zealand

Registered: 2015-04-19

Posts: 61

Re: [SOLVED] NetworkManager won't connect on startup

can you post journalctl -b | grep NetworkManager

thesbros

Member

Registered: 2015-10-07

Posts: 8

Re: [SOLVED] NetworkManager won't connect on startup

— journalctl -b | grep NetworkManager
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  NetworkManager (version 1.0.6) is starting...
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  monitoring kernel firmware directory '/usr/lib/firmware'.
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMVxlanFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMVlanFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMVethFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMTunFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMMacvlanFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMInfinibandFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMGreFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMEthernetFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMBridgeFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMBondFactory (internal)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/libnm-device-plugin-adsl.so)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/libnm-device-plugin-wwan.so)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  WiFi enabled by radio killswitch; enabled by state file
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  WWAN enabled by radio killswitch; enabled by state file
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  WiMAX enabled by radio killswitch; enabled by state file
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  Networking is enabled by state file
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (lo): link connected
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  startup complete
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  wpa_supplicant running
Oct 07 10:29:56 desktop NetworkManager[269]: <warn>  (eth0): failed to find device 2 'eth0' with udev
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (eth0): new Ethernet device (carrier: OFF, driver: 'e1000e', ifindex: 2)
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (eth0): interface index 2 renamed iface from 'eth0' to 'enp0s25'
Oct 07 10:29:56 desktop NetworkManager[269]: <info>  (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 07 10:29:58 desktop NetworkManager[269]: <info>  (enp0s25): link connected
Oct 07 10:29:58 desktop NetworkManager[269]: <info>  (enp0s25): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]

Log after restart:

Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  NetworkManager (version 1.0.6) is starting...
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  monitoring kernel firmware directory '/usr/lib/firmware'.
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  WiFi hardware radio set enabled
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  WWAN hardware radio set enabled
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMVxlanFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMVlanFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMVethFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMTunFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMMacvlanFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMInfinibandFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMGreFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMEthernetFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMBridgeFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMBondFactory (internal)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/libnm-device-plugin-adsl.so)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/libnm-device-plugin-wwan.so)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  WiFi enabled by radio killswitch; enabled by state file
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  WWAN enabled by radio killswitch; enabled by state file
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  WiMAX enabled by radio killswitch; enabled by state file
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  Networking is enabled by state file
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  (lo): link connected
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  (enp0s25): new Ethernet device (carrier: OFF, driver: 'e1000e', ifindex: 2)
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  keyfile: add connection in-memory (341510d6-63fd-41a2-a687-9a73365014bb,"Wired connection 1")
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  (enp0s25): created default wired connection 'Wired connection 1'
Oct 07 10:33:38 desktop NetworkManager[1115]: <info>  wpa_supplicant running
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): link connected
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  Auto-activating connection 'Wired connection 1'.
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): Activation: starting connection 'Wired connection 1' (341510d6-63fd-41a2-a687-9a73365014bb)
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  NetworkManager state is now CONNECTING
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  Activation (enp0s25) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  dhclient started with pid 1120
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>    address 10.0.1.34
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>    plen 24 (255.255.255.0)
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>    gateway 10.0.1.1
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>    server identifier 10.0.1.1
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>    lease time 86400
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>    nameserver '10.0.1.1'
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>    domain name 'hsd1.or.comcast.net.'
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): DHCPv4 state changed unknown -> bound
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): device state change: secondaries -> activated (reason 'none') [90 100 0]
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  NetworkManager state is now CONNECTED_LOCAL
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  Policy set 'Wired connection 1' (enp0s25) as default for IPv4 routing and DNS.
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  Writing DNS information to /usr/bin/resolvconf
Oct 07 10:33:40 desktop NetworkManager[1115]: <info>  (enp0s25): Activation: successful, device activated.
Oct 07 10:33:45 desktop NetworkManager[1115]: <info>  startup complete

c3kay

Member

From: New Zealand

Registered: 2015-04-19

Posts: 61

Re: [SOLVED] NetworkManager won't connect on startup

might be that dhclient is not configured to run at boot with systemd. dhclient needs to have unit files written for it because they don't come with the package, but network manager can run the process by itself when explicitly requested. write a custom systemd unit for dhclient and see if that works.

or, perhaps an easier method seeing as you don't use ipv6, try changing the dhcp settings NetworkManager.conf to

dhcp=internal

and reboot. if that doesn't work change it back to what it was before and go the unit file route.

Last edited by c3kay (2015-10-08 02:03:48)

thesbros

Member

Registered: 2015-10-07

Posts: 8

Re: [SOLVED] NetworkManager won't connect on startup

Neither dhcp=internal nor the unit file worked. I think it has something to do with this:

<warn>  (eth0): failed to find device 2 'eth0' with udev

Is the network interface not getting initialized before NetworkManager starts up somehow?

c3kay

Member

From: New Zealand

Registered: 2015-04-19

Posts: 61

Re: [SOLVED] NetworkManager won't connect on startup

you could try forcing that device assignment in udev. but because it's working and the device is assigned the new name before nm tries to connect, i'm not sure that's the problem.

the codes issued by network manager in the boot sequence indicate that the device is being managed by nm, but there's no ip assignment, so no autoip or dhcp. the e1000e module is loaded and it's assigned a new device name after udev failed to recognise it. you're looking at these reason codes here:

https://developer.gnome.org/NetworkMana … /spec.html

so 10 20 2 = 802.1X supplicant failed (because there's no wifi), autoip failed (can't get an IP), and then nm is managing the connection. which is why you can then see and start the connection from nm later on. the further reason codes 20 30 40 indicate that ip assignment is still failing and there's no connection.

the unit prior to launching nm only has no dhcp process spawned, but the unit has started dhclient after manually launching nm, which then allows it to connect. then so not a module issue, because the module loaded at boot.

can you post the unit file you're using for dhclient, and the output of systemctl status $unitfile?

thesbros

Member

Registered: 2015-10-07

Posts: 8

Re: [SOLVED] NetworkManager won't connect on startup

Unit file:

[Unit]
Description=dhclient on %I
Wants=network.target
Before=network.target

[Service]
ExecStart=/usr/bin/dhclient -d %I

[Install]
WantedBy=multi-user.target

Then `systemctl enable dhclient@enp0s25`.

Error for unit file:

Oct 07 19:54:43 desktop dhclient[288]: Failed to get interface index: No such device
Oct 07 19:54:43 desktop dhclient[288]: If you think you have received this message due to a bug rather
Oct 07 19:54:43 desktop dhclient[288]: than a configuration issue please read the section on submitting
Oct 07 19:54:43 desktop dhclient[288]: bugs on either our web page at www.isc.org or in the README file
Oct 07 19:54:43 desktop dhclient[288]: before submitting a bug.  These pages explain the proper
Oct 07 19:54:43 desktop dhclient[288]: process and the information we find helpful for debugging..
Oct 07 19:54:43 desktop dhclient[288]: exiting.
Oct 07 19:54:43 desktop systemd[1]: dhclient@enp0s25.service: Main process exited, code=exited, status=1/FAILURE
Oct 07 19:54:43 desktop systemd[1]: dhclient@enp0s25.service: Unit entered failed state.
Oct 07 19:54:43 desktop systemd[1]: dhclient@enp0s25.service: Failed with result 'exit-code'.

For some reason dhclient thinks the interface doesn't exist on startup. If I do `systemctl start dhclient@enp0s25` after booting, it starts fine.

c3kay

Member

From: New Zealand

Registered: 2015-04-19

Posts: 61

Re: [SOLVED] NetworkManager won't connect on startup

if you don't start the connection via nm manually, but rather restart the nm service, does dhclient start with nm?

thesbros

Member

Registered: 2015-10-07

Posts: 8

Re: [SOLVED] NetworkManager won't connect on startup

Oh, I never started the connection manually. I've been restarting the systemd service. I said in the OP "Restarting the NetworkManager service [...]". And yes, if I restart the nm service, it starts dhclient.

c3kay

Member

From: New Zealand

Registered: 2015-04-19

Posts: 61

Re: [SOLVED] NetworkManager won't connect on startup

sorry, my bad.

is the interface set in dhclient.conf?

Last edited by c3kay (2015-10-08 03:50:10)

thesbros

Member

Registered: 2015-10-07

Posts: 8

Re: [SOLVED] NetworkManager won't connect on startup

Yes, I tried both

interface "eth0" {
    send dhcp-client-identifier <mac address>;
}

and

interface "enp0s25" {
    send dhcp-client-identifier <mac address>;
}

c3kay

Member

From: New Zealand

Registered: 2015-04-19

Posts: 61

Re: [SOLVED] NetworkManager won't connect on startup

try no interface line. let it detect and use whatever it finds.

thesbros

Member

Registered: 2015-10-07

Posts: 8

Re: [SOLVED] NetworkManager won't connect on startup

Tried that too. I think I might just use dhcpcd instead of NetworkManager if I can't figure this out since I only have one wired connection.

c3kay

Member

From: New Zealand

Registered: 2015-04-19

Posts: 61

Re: [SOLVED] NetworkManager won't connect on startup

these are the reasons i gave up on nm. i use netctl and dhcpcd. never fails.

thesbros

Member

Registered: 2015-10-07

Posts: 8

Re: [SOLVED] NetworkManager won't connect on startup

Yep, switched to dhcpcd and everything works perfectly. Thanks for the help.

jokercap

Banned

Registered: 2016-11-27

Posts: 1

Re: [SOLVED] NetworkManager won't connect on startup

how to switch to dhcpcd .. i have the same issue on kali linux

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,859

Website

Re: [SOLVED] NetworkManager won't connect on startup

Then ask on the Kali Linux forums instead of necrobumping topics on this forum..

https://wiki.archlinux.org/index.php/Co … bumping.22
https://wiki.archlinux.org/index.php/Co … .2Aonly.2A

Closing.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.