Arch Linux - br0 is down, or has no allocated address

[beluga]

I'm running archlinux-on-b3 with the latest modifications (thanks a lot, sakaki, for maintaining it!). After recent updates, I noticed my IRC bot started dropping off. It turned out that the old IP is not retained, when DHCP lease expires.

This is seen in journal:

Code: Select all

touko 05 15:03:41 archb3 systemd[1]: Starting A lightweight DHCP and caching DNS server...
touko 05 15:03:41 archb3 dnsmasq[2113]: dnsmasq: syntax check OK.
touko 05 15:04:11 archb3 wait-for-br0.sh[2114]: br0 is down, or has no allocated address
touko 05 15:04:11 archb3 systemd[1]: dnsmasq.service: Control process exited, code=exited, status=1/FAILURE
touko 05 15:04:11 archb3 systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
touko 05 15:04:11 archb3 systemd[1]: Failed to start A lightweight DHCP and caching DNS server.

I have read the topic about the wait-for-br0.sh script, but I am out of ideas on what might be the cause. My dnsmasq service is the one in the topic.
I am not using Shorewall (as advised by the readme of archlinux-on-b3).
I am not using wifi.

[beluga]

Could it be this is the same systemd-networkd regression currently being discussed here: https://github.com/systemd/systemd/issues/9252 ?

With 'ip link show' I get

Code: Select all

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 00:22:02:00:3c:92 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br0 state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:22:02:00:3c:93 brd ff:ff:ff:ff:ff:ff
4: br0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether da:96:93:4e:4c:81 brd ff:ff:ff:ff:ff:ff

[Gordon]

Seems likely.

In your case, since the bridge is in fact rather pointless because it only has one interface, I'd simply delete the bridge and link the protocol(s) directly to eth1.