After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 741687 - Bridge slave connection not nrought up on resume / wake from sleep
Bridge slave connection not nrought up on resume / wake from sleep
Status: RESOLVED DUPLICATE of bug 742675
Product: NetworkManager
Classification: Platform
Component: general
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-12-17 23:00 UTC by Adam Williamson
Modified: 2015-01-12 15:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Adam Williamson 2014-12-17 23:00:37 UTC
Affects at least Fedora 21 and current Fedora 22, with NetworkManager-0.9.10.0-14.git20140704.fc22.x86_64 .

I have a simple bridge config with a wired connection, for virt purposes:

[adamw@adam NetworkManager (master)]$ cat /etc/sysconfig/network-scripts/ifcfg-em1 
DEVICE=em1
HWADDR=blah
ONBOOT=yes
BRIDGE=br1
IPV4_FAILURE_FATAL=yes
IPV6_FAILURE_FATAL=no
[adamw@adam NetworkManager (master)]$ cat /etc/sysconfig/network-scripts/ifcfg-br1 
DEVICE=br1
ONBOOT=yes
TYPE=Bridge
BOOTPROTO=dhcp
STP=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME="Bridge br1"
UUID=blah
ZONE=home
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

Whenever I resume the system from sleep, the connection does not fully resume. I have to run 'nmcli con up "System em1"' as root to bring it back.

Here are the NetworkManager log messages across a cycle of suspend/resume/manually bring up connection. I run the nmcli con up at 14:18:28, for the two minutes after waking up and before I do that, the connection is not working.

Dec 17 14:15:17 adam.happyassassin.net NetworkManager[922]: <info> sleep requested (sleeping: no  enabled: yes)
Dec 17 14:15:17 adam.happyassassin.net NetworkManager[922]: <info> sleeping...
Dec 17 14:15:17 adam.happyassassin.net NetworkManager[922]: <info> NetworkManager state is now ASLEEP
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (em1): link disconnected (deferring action for 4 seconds)
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (br1): link disconnected (deferring action for 4 seconds)
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> wake requested (sleeping: yes  enabled: yes)
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> waking up...
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (em1): deactivating device (reason 'sleeping') [37]
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (em1): enslaved to br1
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (br1): detached bridge port em1
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (em1): released from master br1
Dec 17 14:16:22 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 17 14:16:23 adam.happyassassin.net NetworkManager[922]: <info> (em1): preparing device
Dec 17 14:16:26 adam.happyassassin.net NetworkManager[922]: <info> (em1): link connected
Dec 17 14:16:26 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Dec 17 14:16:26 adam.happyassassin.net NetworkManager[922]: <info> (br1): link disconnected (calling deferred action)
Dec 17 14:16:43 adam.happyassassin.net NetworkManager[922]: <info> Connectivity check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with 'Error resolving 'fedoraproject.org': No address associated with hostname'.
Dec 17 14:16:43 adam.happyassassin.net NetworkManager[922]: <info> Connectivity check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with 'Error resolving 'fedoraproject.org': No address associated with hostname'.
Dec 17 14:17:03 adam.happyassassin.net NetworkManager[922]: <info> Connectivity check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with 'Error resolving 'fedoraproject.org': No address associated with hostname'.
Dec 17 14:17:03 adam.happyassassin.net NetworkManager[922]: <info> Connectivity check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with 'Error resolving 'fedoraproject.org': No address associated with hostname'.
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) starting connection 'System em1'
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) scheduled...
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) started...
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 2 of 5 (Device Configure) scheduled...
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 1 of 5 (Device Prepare) complete.
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 2 of 5 (Device Configure) starting...
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 2 of 5 (Device Configure) successful.
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 2 of 5 (Device Configure) complete.
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) started...
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (br1): bridge port em1 was attached
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) connection 'System em1' enslaved, continuing activation
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (br1): link connected
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (br1): attached bridge port em1
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) Stage 3 of 5 (IP Configure Start) complete.
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> (em1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dec 17 14:18:28 adam.happyassassin.net NetworkManager[922]: <info> Activation (em1) successful, device activated.
Comment 1 Dan Williams 2015-01-12 15:57:28 UTC

*** This bug has been marked as a duplicate of bug 742675 ***