oxidecomputer / oxidecomputer/opte
Want support for DHCPv6 Reconfigure messages
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
We're currently expanding IPv6 support for guests throughout the product. We haven't yet fully decided on the NAT stance for IPv6, though. That is, to guests see the public IPv6 address directly in the guest, or do we NAT it just like IPv4? If we eschew NAT, we need a way to notify the guest (not just OPTE) that a public address like a Floating IP has changed. The most viable path here is to have OPTE emit a DHCPv6 Reconfigure message, asking the client to renew its lease.
We shouldn't start this work until we make the decision to eschew NAT for IPv6, but I want to keep track of this until then.
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
First resolve the IPv6 NAT decision described in the issue, since the issue says implementation should wait until then. No files, tests, or entry points are named; once the networking direction is settled, trace how OPTE communicates address changes to guests and define completion around clients receiving a DHCPv6 Reconfigure request and renewing their lease.
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
- Needs clarification
- Newbie friendliness
- 20/100