Re: NM 1.0.6, Bridge takes 30 seconds to initialize

["Nathanael D. Noblet" <nathanael gnat ca>]

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
GENERAL.NAME:                           Bridge connection 1
GENERAL.UUID:                           62a5d08c-1e57-4f03-8ee3-
f9998b6c5714
GENERAL.DEVICES:                        bridge0
GENERAL.STATE:                          activated
GENERAL.DEFAULT:                        yes
GENERAL.DEFAULT6:                       no
GENERAL.VPN:                            no
GENERAL.ZONE:                           dmz
GENERAL.DBUS-
PATH:                      /org/freedesktop/NetworkManager/ActiveConnec
tion/0
GENERAL.CON-
PATH:                       /org/freedesktop/NetworkManager/Settings/2
GENERAL.SPEC-OBJECT:                    /
GENERAL.MASTER-PATH:                    --
IP4.ADDRESS[1]:                         192.168.4.100/24
IP4.GATEWAY:                            192.168.4.1
IP4.DNS[1]:                             192.168.4.1
IP4.DOMAIN[1]:                          noblet.ca
DHCP4.OPTION[1]:                        requested_wpad = 1
DHCP4.OPTION[2]:                        requested_domain_search = 1
DHCP4.OPTION[3]:                        dhcp_server_identifier =
192.168.4.1
DHCP4.OPTION[4]:                        requested_time_offset = 1
DHCP4.OPTION[5]:                        host_name = iridium
DHCP4.OPTION[6]:                        requested_rfc3442_classless_sta
tic_routes = 1
DHCP4.OPTION[7]:                        requested_classless_static_rout
es = 1
DHCP4.OPTION[8]:                        requested_domain_name = 1
DHCP4.OPTION[9]:                        domain_name = noblet.ca
DHCP4.OPTION[10]:                       expiry = 1445007045
DHCP4.OPTION[11]:                       next_server = 192.168.4.1
DHCP4.OPTION[12]:                       broadcast_address =
192.168.4.255
DHCP4.OPTION[13]:                       dhcp_message_type = 5
DHCP4.OPTION[14]:                       requested_broadcast_address = 1
DHCP4.OPTION[15]:                       requested_subnet_mask = 1
DHCP4.OPTION[16]:                       dhcp_lease_time = 4294967295
DHCP4.OPTION[17]:                       ip_address = 192.168.4.100
DHCP4.OPTION[18]:                       routers = 192.168.4.1
DHCP4.OPTION[19]:                       requested_static_routes = 1
DHCP4.OPTION[20]:                       subnet_mask = 255.255.255.0
DHCP4.OPTION[21]:                       requested_nis_servers = 1
DHCP4.OPTION[22]:                       requested_interface_mtu = 1
DHCP4.OPTION[23]:                       requested_ntp_servers = 1
DHCP4.OPTION[24]:                       domain_name_servers =
192.168.4.1
DHCP4.OPTION[25]:                       requested_ms_classless_static_r
outes = 1
DHCP4.OPTION[26]:                       requested_routers = 1
DHCP4.OPTION[27]:                       requested_nis_domain = 1
DHCP4.OPTION[28]:                       network_number = 192.168.4.0
DHCP4.OPTION[29]:                       requested_host_name = 1
DHCP4.OPTION[30]:                       requested_domain_name_servers =
1
IP6.ADDRESS[1]:                         fe80::76d4:35ff:fe1a:b537/64
IP6.GATEWAY:                            


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.