Skip to content

yangerd: classify FRR local routes as kernel, not direct - #1749

Merged
troglobit merged 2 commits into
mainfrom
yanger-frr-bug
Oct 30, 2026
Merged

troglobit merged 2 commits into
mainfrom
yanger-frr-bug

Conversation

@mattiaswal

Copy link
Copy Markdown
Contributor

Description

Checklist

Tick relevant boxes, this PR is-a or has-a:

  • Bugfix
    • Regression tests
    • ChangeLog updates (for next release)
  • Feature
    • YANG model change => revision updated?
    • Regression tests added?
    • ChangeLog updates (for next release)
    • Documentation added?
  • Test changes
    • Checked in changed Readme.adoc (make test-spec)
    • Added new test to group Readme.adoc and yaml file
  • Code style update (formatting, renaming)
  • Refactoring (please detail in commit messages)
  • Build related changes
  • Documentation content changes
    • ChangeLog updated (for major changes)
  • Other (please describe):

FRR keeps a host route for each of an interface's own addresses as
protocol "local". The legacy yanger collector had no mapping for it, so
it fell through to infix-routing:kernel; operational data checks skip
kernel routes. yangerd mapped local to direct, which surfaced those
host routes as stray connected routes. Match the old behaviour.

Signed-off-by: Mattias Walström <lazzer@gmail.com>
Committing and pushing are governed by the same reviewer rules (commit
format, sign-off, no Claude trailer, consolidation) as the code changes,
so the trigger must cover them, not just build/test/change.

Signed-off-by: Mattias Walström <lazzer@gmail.com>
@troglobit
troglobit merged commit 94d29ec into main Oct 30, 2026
10 checks passed
@troglobit
troglobit deleted the yanger-frr-bug branch October 30, 2026 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants