oxidecomputer / oxidecomputer/omicron
BGP: Allow Operator to define Router-ID explicitly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Today, the BGP Router-ID (RID) is auto-derived in Maghemite by copying a 32-bit Autonomous System Number (ASN) value into the 32-bit RID field.
This can cause potential issues in certain BGP topologies or with certain path attributes, as a deployment where both rack switches joining the same AS would result in both switches having the same Router-ID.
This ticket is meant to request/track the addition of functionality to allow an Operator to define a RID for a given BGP router (ideally per switch).
Contributor guide
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
The issue names no files or tests. Start by locating Maghemite's BGP handling and the code that derives the Router-ID from the ASN, then trace how per-switch configuration reaches each BGP router. Done means an operator can define a Router-ID for a given router, ideally per switch, instead of relying on the ASN-derived value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100