Bug 88317

Summary:	networkd: Can't bring virtual netdev's UP, thus making e.g. dnsmasq unable to start to bring it up.
Product:	systemd	Reporter:	forgetmij
Component:	general	Assignee:	Tom Gundersen <teg>
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	major
Priority:	medium
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description forgetmij 2015-01-12 09:29:44 UTC

When creating a bridge say through systemd-networkd, one cannot seemingly bring up the interface with ip link set dev <virbr0> up.

Thus dnsmasq in this case will not start.

By adding such a device with brctl, it works fine.

By using brctl, one kind of does not need networkd then and so on.

Comment 1 Tom Gundersen 2015-02-09 11:29:14 UTC

Please paste the .netdev file you are using which causes the failure, and the brctl command that works.

Comment 2 Ian Kumlien 2015-03-31 21:35:05 UTC

I don't use a bridge for dnsmasq, but I just switched my gentoo machine over to systemd/networkd due to the speedier boottime.

Anyway, here's some info:
cat /etc/systemd/network/bridge.netdev 
[NetDev]
Name=br0
Kind=bridge

[Bridge]
Cost=0
---

This results in a bridge that is DISABLED. It's configured closely enough so that "ifconfig br0 up" fixes all your problems. But that doesn't help you if you can't reach it.

Comment 3 Lennart Poettering 2019-03-19 12:53:31 UTC

This should be fixed in current systemd versions. 

(You have to add a .network file for the bridge to make sure it is marked UP. The .netdev only creates the naked bridge device, and won't UP it, that's the responsibility of the .network files.)

let's close this here. If there are any issues left with the two most current systemd versions upstream please file issues on systemd github. thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.