Support for "ip nexthop" missing
This includes support for both the "ip nexthop" command itself as well as the "nhid" option in the "ip route" command.
The current code includes support for multipath by using multiple nexthop entries for a given route. However, using nexthop groups can be more efficient because many routes can use the same nexthop group, and nexthop groups can be changed without modifying the related routes. Furthermore, resilient nexthop groups are now supported which can reduce the churn when nexthops are added or deleted from a group.
I'll add that if no one else is working on this, and there are no objections, I or one of my colleagues may be able to implement the support.
I think ip nexthop support is quite interesting , @anfredette any progress on your implementation so far?
Hello, we are also interested in ip nexthop support, are you planning to implement it?
When I opened this issue, I was working on a POC and used multiple nexthop entries for multipath to get things working. However, we ended up going in a different direction, so unfortunately, I'm not available to work on this issue.
Are we still planning to do this ip nexthop?
Minimum work is here: https://github.com/vishvananda/netlink/pull/1139
I may add some other features for my own use cases.