systemd-networkd: constant state of "configuring" [SOLVED]

graysky · 2016-12-21 20:05:15

I am using systemd-networkd to control a bridge and it the en0 device is in a constant state of configuring. Everything functions normally, it's just odd to me. Anyone else with this setup? Do you have the same?

% networkctl
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  2 en0              ether              carrier     configuring
  3 br0              ether              routable    configured

Here is my actual setup:

% cd /etc/systemd/network
% cat br0.netdev
[NetDev]
Name=br0
Kind=bridge

% cat br0.network
[Match]
Name=br0
[Network]
DHCP=yes

% cat uplink.network
[Match]
Name=en0
[Network]
Bridge=br0

Last edited by graysky (2016-12-21 21:57:34)

damjan · 2016-12-21 21:07:05

That's nothing to worry about.

Afaik there's an issue reported upstream about networkd, it'll get fixed eventually.

ewaller · 2016-12-21 21:12:32

Check the output of netctl -a status I'll bet there is no address for en0 and I bet that is a criterion for being 'configured'

graysky · 2016-12-21 21:31:47

@damjan - I saw something about this on github but it was closed.
@ewaller - Not using netctl I don't think that command is valid syntax.

ewaller · 2016-12-21 21:34:55

Clearly I've danbramage. I meant networkctl -a status

graysky · 2016-12-21 21:39:14

Ah!

% networkctl -a status
● 1: lo
       Link File: n/a
    Network File: n/a
            Type: loopback
           State: carrier (unmanaged)
         Address: 127.0.0.1
                  ::1

● 2: eth0
       Link File: n/a
    Network File: /etc/systemd/network/uplink.network
            Type: ether
           State: carrier (configuring)
          Vendor: Intel Corporation
           Model: Ethernet Connection (2) I218-V
      HW Address: 43:8a:1b:9e:a7:a3 (Micro-Star INT'L CO., LTD.)

● 3: br0
       Link File: n/a
    Network File: /etc/systemd/network/br0.network
            Type: ether
           State: routable (configured)
      HW Address: e2:00:12:be:7d:a6
         Address: 10.1.10.101
                  fe80::c001:11ff:febe:fee0
         Gateway: 10.1.10.1 (ASUSTek COMPUTER INC.)
             DNS: 10.1.10.1

ewaller · 2016-12-21 21:48:16

Yeah, en0 has no address, but br0, which is bridged through en0 does. I agree with damjan that it is probably not right to flag it as
'configuring' as nothing is (or is expected to) happen. But, I'll bet the lack of address and routability are reasons it is not yet defined as 'configured' Mayhaps they need some other state name.

graysky · 2016-12-21 21:57:19

I think you're right... I might verify that there isn't an open ticket against systemd about it and then report. Thanks.

Arch Linux

#1 2016-12-21 20:05:15

systemd-networkd: constant state of "configuring" [SOLVED]

#2 2016-12-21 21:07:05

Re: systemd-networkd: constant state of "configuring" [SOLVED]

#3 2016-12-21 21:12:32

Re: systemd-networkd: constant state of "configuring" [SOLVED]

#4 2016-12-21 21:31:47

Re: systemd-networkd: constant state of "configuring" [SOLVED]

#5 2016-12-21 21:34:55

Re: systemd-networkd: constant state of "configuring" [SOLVED]

#6 2016-12-21 21:39:14

Re: systemd-networkd: constant state of "configuring" [SOLVED]

#7 2016-12-21 21:48:16

Re: systemd-networkd: constant state of "configuring" [SOLVED]

#8 2016-12-21 21:57:19

Re: systemd-networkd: constant state of "configuring" [SOLVED]

Board footer