Arch Linux

mouseman

Member

From: Outta nowhere

Registered: 2014-04-04

Posts: 298

[solved] netctl not setting ip on second interface

I installed netctl and created 2 profiles:

Description='Static IP connection on eno1'
Interface=eno1
Connection=ethernet
IP=static
Address=('10.26.14.23/24')
Gateway=('10.26.14.1')
DNS=('10.26.14.65')
NTP=('0.arch.pool.ntp.org' '1.arch.pool.ntp.org' '2.arch.pool.ntp.org')
ExcludeAuto=no

Description='Static IP connection on enp1s0f0u1 for storage backend'
Interface=enp1s0f0u1
Connection=ethernet
IP=static
Address=('172.16.10.23/24')
ForceConnect=yes
ExcludeAuto=no

The profile for enp1s0f0u1 does not set the IP address.

systemctl status shows:

● netctl@enp1s0f0u1.service - Static IP connection on enp1s0f0u1 for storage backend
     Loaded: loaded (/usr/lib/systemd/system/netctl@.service; enabled; preset: disabled)
    Drop-In: /etc/systemd/system/netctl@enp1s0f0u1.service.d
             └─profile.conf
     Active: active (exited) since Sat 2025-04-12 14:01:13 CEST; 6min ago
 Invocation: 174102a282394abbba90505c5cf5544e
       Docs: man:netctl.profile(5)
   Main PID: 533 (code=exited, status=0/SUCCESS)
     Status: "online"
   Mem peak: 3.8M
        CPU: 172ms

Apr 12 14:01:09 kvm03 systemd[1]: Starting Static IP connection on enp1s0f0u1 for storage backend...
Apr 12 14:01:09 kvm03 network[533]: Starting network profile 'enp1s0f0u1'...
Apr 12 14:01:13 kvm03 systemd[1]: Started Static IP connection on enp1s0f0u1 for storage backend.
Apr 12 14:01:13 kvm03 network[533]: Started network profile 'enp1s0f0u1'

Journalctl output:

-- Boot 83d0de37811d41e38171d077bee37e39 --
Apr 12 13:28:47 kvm03 systemd[1]: Starting Static IP connection on enp1s0f0u1 for storage backend...
Apr 12 13:28:47 kvm03 network[534]: Starting network profile 'enp1s0f0u1'...
Apr 12 13:28:51 kvm03 systemd[1]: Started Static IP connection on enp1s0f0u1 for storage backend.
Apr 12 13:28:51 kvm03 network[534]: Started network profile 'enp1s0f0u1'
Apr 12 14:00:39 kvm03 systemd[1]: Stopping Static IP connection on enp1s0f0u1 for storage backend...
Apr 12 14:00:39 kvm03 network[1035]: Stopping network profile 'enp1s0f0u1'...
Apr 12 14:00:39 kvm03 network[1035]: Stopped network profile 'enp1s0f0u1'
Apr 12 14:00:39 kvm03 systemd[1]: netctl@enp1s0f0u1.service: Deactivated successfully.
Apr 12 14:00:39 kvm03 systemd[1]: Stopped Static IP connection on enp1s0f0u1 for storage backend.
-- Boot e4bcf63ee4ed440da0beddf71a5412c1 --
Apr 12 14:01:09 kvm03 systemd[1]: Starting Static IP connection on enp1s0f0u1 for storage backend...
Apr 12 14:01:09 kvm03 network[533]: Starting network profile 'enp1s0f0u1'...
Apr 12 14:01:13 kvm03 systemd[1]: Started Static IP connection on enp1s0f0u1 for storage backend.
Apr 12 14:01:13 kvm03 network[533]: Started network profile 'enp1s0f0u1'

I searched how to increase verbosity but I can't find out how or if that's even possible.

Any ideas why the second nic isn't getting an IP address?

There is no conflicting dhcpcd or dhclient.

Thanks!

Last edited by mouseman (2025-04-12 13:30:41)

mouseman

Member

From: Outta nowhere

Registered: 2014-04-04

Posts: 298

Re: [solved] netctl not setting ip on second interface

Nevermind, I couldnt figure it out and didn't want to wait (sorry).

I resorted to using Network Manager instead. I am using Ansible to configure multiple hosts and I thought it would be easier with netctl and plain text files, but there's actually a nmcli module for Ansible.