oxidecomputer / oxidecomputer/dendrite
Need support for the same next-hop via multiple interfaces
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
Since adding support for IPv6 and BGP unnumbered, it is now possible (and valid) for the same next-hop IP to exist across multiple interfaces.
A simple example of this would be a route with ECMP paths pointing to two different nodes with the same manually configured link-local IP, i.e. 3fff::/64 via (fe80::1%eth1, fe80::1%eth2).
NDP entries must be tracked via (IP, interface) rather than just IP, as it is perfectly valid for these IPs to be coupled with different MAC addresses.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how NDP entries and route next-hops are tracked for IPv6, BGP unnumbered, and ECMP paths. Confirm the relevant handling distinguishes each next-hop by both IP and interface, then verify that identical link-local addresses on separate interfaces can use different MAC addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100