As discussed back in #3343: Router Advertisements should never contain a ::/0 route.
A default route is indicated by setting the Router Lifetime to > 0. This was originally fixed
by @fichtner in e67dade, but the ::/0 route is still added for CARP interfaces and "static
mode" interfaces (introduced in 66dc0e9).
If CORE_NEXT.b tag exists do not use anything else anymore,
otherwise if CORE_NEXT* something exists use this, otherwise
hands off from manual tag pattern matching.
Since this is based on computation of CORE_ABI input we
can use this on the development track to always figure out
the correct version to use without checking the CORE_ABI
explicitly.
Use CORE_NEXT in a file replacement as well.
Removed more fluff, concepts anf functionality are there.
Plugin conflict labels could probably require improvement,
but the way they work is relatively complicated, but maybe
it is only getting late.
As soon as we have plugin JSON metadata we can ship the
plugin conflict rework as well as that seems to help a lot
when recovering from strange situations (mostly development
things, but we never know).
o show updates tab log tracking progress icon
o get rid of spurious messages when tracking updates tab
o use "status" name to register the first tab
o ignore empty log messages when configd restarts
o table-condensed use everywhere padding a small td on the left
o ditch accept plugin again, users can remove them now manually
o remove fluffy wording from buttons
The plugins accept/reinstall functionality is not fully
reworked yet. There are some backend issues with it
that need to be sorted out. The general idea is to move
the buttons to the Status page to avoid clutter in the
plugins list.
Although it looks nice to return the current configured rule overwrites, it's confusing when querying items. Remove the rule overwrites and only show what's being use now, needs an apply to update.
o Don't try to cleanup single rule changes, since we can't measure the impact of the policy upfront
o Add a grid in the policy editor to show the single overwrites so the user can easily delete them if needed (small number of items isn't an issue, a lot will be)
o warn the user if he/she uses more 100 custom additions, often its better to switch to other definitions (prevent slow config access for all components)
