Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ECMP only supports previously configured/learned next-hops #226

Open
rubensfig opened this issue Sep 13, 2019 · 0 comments · May be fixed by #432
Open

ECMP only supports previously configured/learned next-hops #226

rubensfig opened this issue Sep 13, 2019 · 0 comments · May be fixed by #432
Labels
bug

Comments

@rubensfig
Copy link
Contributor

rubensfig commented Sep 13, 2019 •
edited

Expected Behavior

The routes should be configured on the switch, even though the next hops are not learned.

Actual Behavior

Route is not configured on the switch, even after next-hop resolution. Leads to a break in kernel-switch state.

Steps to Reproduce the Problem

Configure the following route, while not having any nexthop.

ip route add $ECMP_ROUTE nexthop via $NEIX weight 1 nexthop via $NEIY weight 2
@rubensfig rubensfig added the bug label Oct 23, 2019
@KanjiMonster KanjiMonster linked a pull request Apr 30, 2024 that will close this issue
implement proper ECMP route handling #432
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

implement proper ECMP route handling bisdn/basebox
1 participant
@rubensfig