Hi,

* Santiago Garcia Mantinan [Mon Sep 06, 2021 at 11:04:58AM +0200]:
> I'm CCing Josué because this seems to be more on ifupdown's side than on
> bridge-utils.

[...]

> I know we are having quite some trouble with the random bridge mac address,
> but this doesn't seem to be one of those cases.
> 
> For what I see this is a problem with DAD, the bridge is created without any
> port attached to it, so the kernel doesn't allow it to transition from:
> 18: br0    inet6 X/64 scope link tentative \       valid_lft forever 
> preferred_lft forever
> to:
> 18: br0    inet6 X/64 scope link \       valid_lft forever preferred_lft 
> forever
[...]

> As for this bug... I believe it is on the ifupdown side, so I think we
> should reasign it, unless you see a way to fix this problem on the
> bridge-utils side, but I can't think about any fix on bridge-utils side
> right now.

bridge-utils disappeared from Debian/testing due to this RC bug,
should we downgrade severity and/or reassign the bug to proceed from
here?

regards
-mika-

Attachment: signature.asc
Description: PGP signature

Reply via email to