Public bug reported: Creating a new bridge interface and then raising it will result in the bridge having carrier, even though it has no ports. Any change to the bridge interface, e.g. set its mac address or priority, will cause it to scan all its ports for link state and then properly set its own link state to carrier down. However, if it's raised without adding any ports or changing any of its parameters, it will have carrier until a port is added or any parameter is changed.
More detail on reproduction is here: https://github.com/systemd/systemd/pull/15619#issuecomment-621431802 This is causing bug 1860926. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876784 Title: new bridge interface defaults to having carrier Status in linux package in Ubuntu: New Bug description: Creating a new bridge interface and then raising it will result in the bridge having carrier, even though it has no ports. Any change to the bridge interface, e.g. set its mac address or priority, will cause it to scan all its ports for link state and then properly set its own link state to carrier down. However, if it's raised without adding any ports or changing any of its parameters, it will have carrier until a port is added or any parameter is changed. More detail on reproduction is here: https://github.com/systemd/systemd/pull/15619#issuecomment-621431802 This is causing bug 1860926. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
