David Lamparter

> Can we have a list (interface types) of bug'd kernel drivers ? Could it be limited to those interfaces until the kernel's ones will be fixed ? I only...

> The issue was identified with the tun/tap driver […] At initialization, the module reports `IFF_RUNNING & !IFF_LOWER_UP` then `IFF_RUNNING & IFF_LOWER_UP`. I don't see this behavior, what exactly do...

Ok, I think it should work. I hope we won't have the opposite problem with another driver though. If that happens we should just revert this.

> Please rebase and resolve conflicts. sure, here you go @westes

Just noticed that the print in the NB code is also misleading - it prints microseconds but the format was `%lus`, i.e. it prints "99999s", `u` being the printf specifier...

The > :x: [CI] Verify Source is because I did a force push 2 minutes after opening the PR and manually aborted the CI run on the old commit (it's...

reopening because CI github script is b0rked

> binaries that are not drastically required from the package we deliver. > In our environment, we will never use the CLI. So strictly speaking, we do not need the...

> It looks like the 'disable-vtysh' is used when cross-compiling, when the clippy tool is being built. That may be a construction of David L's - is it still necessary?...

FRR only configures the routing tables for the kernel to work with, you are not showing any details on that. Please add the output of `ip route list` and `ip...