[systemd-devel] device state UNKNOWN

arnaud gaboury arnaud.gaboury at gmail.com
Mon Mar 10 07:32:02 PDT 2014


Hi,

No idea why my bridge device, br0, has a state unknown.

$ ip addr
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN group default
    link/ether 66:73:a3:0a:44:f9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.94/24 brd 192.168.1.255 scope global br0
       valid_lft forever preferred_lft forever
    inet6 fe80::6473:a3ff:fe0a:44f9/64 scope link
       valid_lft forever preferred_lft forever

$ systemctl status systemd-networkd
Mar 10 14:32:25 hortensia systemd-networkd[335]: Failed to save link
data /run/systemd/network/links/3: No such file or directory
Mar 10 14:32:25 hortensia systemd-networkd[335]: br0: netdev ready
Mar 10 14:32:25 hortensia systemd-networkd[335]: br0: link is up
Mar 10 14:32:25 hortensia systemd-networkd[335]: br0: carrier on
Mar 10 14:32:25 hortensia systemd-networkd[335]: br0: link configured
Mar 10 14:32:25 hortensia systemd[1]: Started Network Service.

$ ls -al /run/systemd/network/links
drwxr-xr-x 2 root root 60 Mar 10 14:32 ./
drwxr-xr-x 3 root root 80 Mar 10 14:32 ../
-rw-r--r-- 1 root root 55 Mar 10 14:32 3

$ cat /run/systemd/network/links/3
# This is private data. Do not parse.
STATE=configured

**********************
$ cat /etc/systemd/network/bridge.link
[Match]
Name=br0

[Link]
NamePolicy=database onboard slot path
MACAddressPolicy=persistent

$ cat /etc/systemd/network/bridge.netdev
[Match]
Host=hortensia

[NetDev]
Name=br0
Kind=bridge

$ cat /etc/systemd/network/30-bridge.network
[Match]
Name=br0

[Network]
Description="bridge connection"
DHCP=no
Address=192.168.1.87/24
Gateway=192.168.1.254
DNS=192.168.1.254

**********************************

It seems to me that this device is configured, so why is its state
unknown  and not UP ? Shall I use a netctl profile to bring it UP,
like I do for enp7s0 ?


More information about the systemd-devel mailing list