Arch Linux

yodermk

Member

Registered: 2012-07-17

Posts: 86

[SOLVED] bridge slave not coming up on boot - NetworkManager

Recently switched from a pretty static net config to managed by NM, and also to my primary ethernet being a bridge device so I can use VMs with their own IPs.  The main IP of the system is also a slave of the bridge, and it is not coming up on boot.  I've messed with autoconnection settings for both the ethernet device and the slave, and nothing seems to help. Here's what I currently have. Any ideas?

[root@pizza ~]# nmcli con show
NAME         UUID                                  TYPE      DEVICE 
br0 slave 1  0ecc44ad-d42d-4f53-a1bb-c3befcd6bbdd  ethernet  eth1   
bridge-br0   42398a40-1440-43a2-a069-572428b81679  bridge    br0    
Profile 1    8de7ff68-7b40-49a6-99b1-a3d252e83a3e  ethernet  --     
[root@pizza ~]# nmcli con show bridge-br0 
connection.id:                          bridge-br0
connection.uuid:                        42398a40-1440-43a2-a069-572428b81679
connection.stable-id:                   --
connection.type:                        bridge
connection.interface-name:              br0
connection.autoconnect:                 yes
connection.autoconnect-priority:        2
connection.autoconnect-retries:         -1 (default)
connection.auth-retries:                -1
connection.timestamp:                   1515885989
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          1 (yes)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
[...]
[root@pizza ~]# nmcli con show br0\ slave\ 1 
connection.id:                          br0 slave 1
connection.uuid:                        0ecc44ad-d42d-4f53-a1bb-c3befcd6bbdd
connection.stable-id:                   --
connection.type:                        802-3-ethernet
connection.interface-name:              eth1
connection.autoconnect:                 yes
connection.autoconnect-priority:        1
connection.autoconnect-retries:         -1 (default)
connection.auth-retries:                -1
connection.timestamp:                   1515885989
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      br0
connection.slave-type:                  bridge
connection.autoconnect-slaves:          1 (yes)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
[...]

To get it up after a reboot I have to

nmcli con up br0\ slave\ 1

Thanks!

Last edited by yodermk (2018-01-14 19:14:49)

yodermk

Member

Registered: 2012-07-17

Posts: 86

Re: [SOLVED] bridge slave not coming up on boot - NetworkManager

Looking at the other recent thread about networks not starting, I checked the services set to enabled.

[root@pizza ~]# systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
org.cups.cupsd.path                         enabled
autovt@.service                             enabled                                                                                               
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
gdm.service                                 enabled
getty@.service                              enabled
haveged.service                             enabled
libvirtd.service                            enabled
netctl.service                              enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
nginx.service                               enabled
nsd.service                                 enabled
ntpd.service                                enabled
org.cups.cupsd.service                      enabled
sshd.service                                enabled
sshdgenkeys.service                         enabled
unbound.service                             enabled
org.cups.cupsd.socket                       enabled
remote-fs.target                            enabled

21 unit files listed.

Prior to this there was also netctl@home.service which might be a relic of what I had before I switched to NM.  But I just disabled it and rebooted and the problem persists.

Anything else here that might conflict?

circleface

Member

Registered: 2012-05-26

Posts: 639

Re: [SOLVED] bridge slave not coming up on boot - NetworkManager

You have NetworkManager.service and netctl.service both enabled.  You will have to choose which one you want to use and disable the other.

yodermk

Member

Registered: 2012-07-17

Posts: 86

Re: [SOLVED] bridge slave not coming up on boot - NetworkManager

Yay that's it!  Thanks!

Disabled netctl since I think that's a relic of my former config.