Hello Thomas, That did the trick! No idea why STP was on. Just rebooted to verify and it came up in 2 seconds. Much nicer. Now to check if bringing the VMs up on boot causes any issues.
Thank you, -- Nathanael On Tue, 2015-10-20 at 15:20 +0200, Thomas Haller wrote: > On Tue, 2015-10-20 at 07:02 -0600, Nathanael D. Noblet wrote: > > On Tue, 2015-10-20 at 09:36 +0200, Thomas Haller wrote: > > > > > > The bridge device has no carrier for the long time. > > > What about your STP configuration? > > > > > > What gives: > > > > > > brctl showstp bridge0 > > > > No idea what much of this means however the output is: > > http://paste.fedoraproject.org/281430/14453458 > > > > > > > > and > > > > > > nmcli connection show 'Bridge connection 1' > > > > connection.id: Bridge connection 1 > > connection.uuid: 62a5d08c-1e57-4f03-8ee3- > > f9998b6c5714 > > connection.interface-name: bridge0 > > connection.type: bridge > > connection.autoconnect: yes > > connection.autoconnect-priority: 0 > > connection.timestamp: 1445345713 > > connection.read-only: no > > connection.permissions: > > connection.zone: dmz > > connection.master: -- > > connection.slave-type: -- > > connection.autoconnect-slaves: -1 (default) > > connection.secondaries: > > connection.gateway-ping-timeout: 0 > > connection.metered: unknown > > ipv4.method: auto > > ipv4.dns: > > ipv4.dns-search: > > ipv4.addresses: > > ipv4.gateway: -- > > ipv4.routes: > > ipv4.route-metric: -1 > > ipv4.ignore-auto-routes: no > > ipv4.ignore-auto-dns: no > > ipv4.dhcp-client-id: -- > > ipv4.dhcp-send-hostname: yes > > ipv4.dhcp-hostname: -- > > ipv4.never-default: no > > ipv4.may-fail: yes > > ipv6.method: auto > > ipv6.dns: > > ipv6.dns-search: > > ipv6.addresses: > > ipv6.gateway: -- > > ipv6.routes: > > ipv6.route-metric: -1 > > ipv6.ignore-auto-routes: no > > ipv6.ignore-auto-dns: no > > ipv6.never-default: no > > ipv6.may-fail: yes > > ipv6.ip6-privacy: 0 (disabled) > > ipv6.dhcp-send-hostname: yes > > ipv6.dhcp-hostname: -- > > bridge.mac-address: -- > > bridge.stp: yes > > bridge.priority: 32768 > > bridge.forward-delay: 15 > > bridge.hello-time: 2 > > bridge.max-age: 20 > > bridge.ageing-time: 300 > > ... > > > Does any of that help? I should note that without the bridge the > > interface configuration was the same (DHCP etc) but doesn't suffer > > from > > this delay. Part of the problem I used to have when I had the VMs > > come > > up on boot was that the bridge would get the wrong MAC address > > somehow > > and then the dhcp server would provide the wrong address to some of > > them. > > I think the delay is caused by your bridge, as you configured it. If > you don't need/want STP, disable it. > > http://www.linuxfoundation.org/collaborate/workgroups/networking/br > idge#Spanning_Tree_Protocol > > > $ nmcli connection modify "Bridge connection 1" bridge.stp no > > > and re-activate the connection > > Thomas _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
