routed assumes it alone controls the routing table and tinkers with

routes it is not supposed to touch trying to aggregate them, which
has unwanted effects when other routing daemons (bgpd) are running.
note that bgpd behaves and only touches its own routes.
workaround by ignoring routes with RTF_PROTO1 set, which bgpd sets for its
routes.
from a discussion with Arvid Grotting <arvidg@netfonds.no>, who tested
a diff of same functionality (basically only formatting and comment
different).
ok deraadt

0 files changed, 0 insertions, 0 deletions