Comment # 17 on bug 908375 from Peter Maloney

(In reply to Marius Tomaschewski from comment #8)
> OK, that is, at boot a bridge with STP enabled and a port which gets a link
> does not come UP, while later it does, right?

It is "UP" but no IPv4 assigned.


5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group
default 
    link/ether 4e:30:18:27:25:57 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::4c30:18ff:fe27:2557/64 scope link 
       valid_lft forever preferred_lft forever


> > the bridge does not get its IP address assigned (a major BUG)
> 
> When the bridge link carrier / state is not UP, further layers as IPs
> aren't assigned. This is not a bug. Wicked verifies and assigns IPs
> after the link goes up (without carrier, STP, IP verify .. is useless).

The link was "UP" though (after boot... don't know about when it tried
assigning an IP), rather than "DOWN,NO-CARRIER". And you don't need an IP to
participate in STP.

> At least when use-nanny is enabled, the IPs are assigned later. Without,
> ifup is a one shot and after the time (WAIT_FOR_INTERFACES + bridge STP)
> it is allowed to wait is over, it has to report & exit.

You mean like a "standing order"? This is a concept I like, and have never seen
it in Linux before (except maybe the automounter). (but I don't approve of
network manager which does this too, but has a horrible CLI eg. binary instead
of text files, and commands refuses to work if the network is disconnected)