Bug 89986 - systemd-networkd: "lost carrier" on simple bridge setup after suspend (systemd219)
Summary: systemd-networkd: "lost carrier" on simple bridge setup after suspend (system...
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Tom Gundersen
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-11 21:23 UTC by Andreas Mayer
Modified: 2019-03-19 12:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Andreas Mayer 2015-04-11 21:23:33 UTC 
Hi,

I got the simplest possible Bridge setup. 

foo.network
[Match]
Name=enp*

[Network]
Bridge=br0

bar.network
[Match]
Name=br0

[Network]
DHCP=v4

and of course the bridge.netdev.


Everything works fine and i can connect containers etc. to the bridge until i suspend my computer. 
After the wakeup, the network is not coming back up. I only get "br0 lost carrier" in the journal. 
If I restart systemd-networkd.service everything works fine again.

Do you need more infos? Can you reproduce this behaviour?


Greetings
Comment 1 Lennart Poettering 2019-03-19 12:33:53 UTC 
I am pretty sure this is fixed in current systemd versions. If this is reproducible on one of the two most current systemd versions (v240, v241) please file a new issue in systemd github.

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.