Arch Linux

Erwya

Member

Registered: 2015-10-07

Posts: 2

Network starts before kernel have set udev rules

Greetings Arch users!

I have recently got an error after a fresh install Arch linux. Networking isn't starting at boot. Manually telling netctl to start the interface after boot though result in a correctly configured connection, making me understand that the network configuration isn't the problem here. I have also tried to set parameters for waiting longer before kicking up the interface, but it seems not working here.

/etc/netctl/net1:
Description='Networking'
Interface=net1
Connection=ethernet

IP=static
Address=('*.IPv4.*')
Gateway='*.IPv4.*'
DNS=('*.IPv4.*')

## For IPv6 autoconfiguration
#IP6=stateless

## For IPv6 static address configuration
IP6=static
Address6=('*.IPv6.*')
Gateway6='*.IPv6.*'

TimeoutUp=300
TimeoutCarrier=300
ForceConnect=yes

Digging in the journal reveals that netctl trying to activate the interface when it still doesn't exist. Following the journal shows that shortly after, the results of the udev rules activates and give the interface it's correct settings.

$ journalctl -xe: (only significant part showed)
-- A new seat seat0 has been configured and is now available.
oct 07 09:43:22 Arch network[231]: Starting network profile 'net1'...
oct 07 09:43:22 Arch systemd[1]: Started Getty on tty1.
-- Subject: Unit getty@tty1.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit getty@tty1.service has finished starting up.
--
-- The start-up result is done.
oct 07 09:43:22 Arch network[231]: Interface 'net1' does not exist
oct 07 09:43:22 Arch network[231]: Failed to bring the network up for profile 'net1'
oct 07 09:43:22 Arch systemd[1]: Reached target Login Prompts.
-- Subject: Unit getty.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit getty.target has finished starting up.
--
-- The start-up result is done.
oct 07 09:43:22 Arch systemd[1]: netctl@net1.service: Main process exited, code=exited, status=1/FAILURE
oct 07 09:43:22 Arch systemd[1]: Failed to start Networking.
-- Subject: Unit netctl@net1.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@net1.service has failed.
--
-- The result is failed.
oct 07 09:43:22 Arch systemd[1]: netctl@net1.service: Unit entered failed state.
oct 07 09:43:22 Arch systemd[1]: netctl@net1.service: Failed with result 'exit-code'.
oct 07 09:43:22 Arch systemd[1]: Reached target Network.
-- Subject: Unit network.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit network.target has finished starting up.

-- Unit network.target has finished starting up.
--
-- The start-up result is done.
oct 07 09:43:22 Arch systemd[1]: Started OpenSSH Daemon.
-- Subject: Unit sshd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit sshd.service has finished starting up.
--
-- The start-up result is done.
oct 07 09:43:22 Arch systemd[1]: Reached target Multi-User System.
-- Subject: Unit multi-user.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit multi-user.target has finished starting up.
--
-- The start-up result is done.
oct 07 09:43:22 Arch systemd[1]: Reached target Graphical Interface.
-- Subject: Unit graphical.target has finished start-up
--
-- Unit multi-user.target has finished starting up.
--
-- The start-up result is done.
oct 07 09:43:22 Arch systemd[1]: Reached target Graphical Interface.
-- Subject: Unit graphical.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit graphical.target has finished starting up.
--
-- The start-up result is done.
oct 07 09:43:22 Arch systemd[1]: Startup finished in 3.425s (kernel) + 1.047s (userspace) = 4.473s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel

-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required 3425825 microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 1047211 microseconds.
oct 07 09:43:22 Arch sshd[240]: Server listening on 0.0.0.0 port 22.
oct 07 09:43:22 Arch sshd[240]: Server listening on :: port 22.
oct 07 09:43:22 Arch kernel: e1000 0000:00:08.0 eth1: (PCI:33MHz:32-bit) (*.MAC.*)
oct 07 09:43:22 Arch kernel: e1000 0000:00:08.0 eth1: Intel(R) PRO/1000 Network Connection
oct 07 09:43:22 Arch kernel: piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
oct 07 09:43:22 Arch kernel: e1000: eth0 changing MTU from 1500 to 9000
oct 07 09:43:22 Arch kernel: e1000 0000:00:08.0 enp0s8: renamed from eth1
oct 07 09:43:22 Arch kernel: e1000 0000:00:03.0 net1: renamed from eth0
oct 07 09:43:25 Arch kernel: floppy0: no floppy controllers found
oct 07 09:43:27 Arch kernel: random: nonblocking pool is initialized
oct 07 09:43:27 Arch login[237]: pam_unix(login:session): session opened for user erwya by LOGIN(uid=0)
oct 07 09:43:27 Arch systemd[1]: Created slice user-0.slice.
-- Subject: Unit user-0.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit user-0.slice has finished starting up.

I see several ways to solve this using quirky solutions or give up some of the configurations. What I would like to do is an elegant and efficient solution of the problem that let me keep the settings.

I also wonder if I encountered a bug because those settings has also successfully been used before on different machines.

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: Network starts before kernel have set udev rules

You should have a /etc/systemd/system/netctl@net1.service file, please show its contents.

---

1000

Erwya

Member

Registered: 2015-10-07

Posts: 2

Re: Network starts before kernel have set udev rules

Thanks for answer. I have installed another system today which doesn't show this problem. On this system the problem still persist. Reenabling netctl net1 does not work either. The only big differences between the systems that make sense for me is that this system is running from a SSD (instead of a HDD), making me guess if the problem appears just because it starts very fast (~3s).

The service file shows:
.include /usr/lib/systemd/system/netctl@.service

[Unit]
Description=Networking
BindsTo=sys-subsystem-net-devices-net1.device
After=sys-subsystem-net-devices-net1.device

Last edited by Erwya (2015-10-08 18:31:53)