oxidecomputer / oxidecomputer/omicron
NAT entries go missing if switch zone is restarted in early networking.
Open
@internet-diglett is already working on this.
Since Jul 16, 2024.
networking
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In #5037 and #4650 we noticed an issue where NAT entires would not be fully populated on scrimlet reboot. This is because the entity making these entries is the sled agent launching a zone that requires NAT entries. Further analysis is provided in #4857. However, the aforementioned rely on Nexus and RPW machinery to create an eventually consistent NAT situation. If nexus is not running, we have no recourse in early networking and are left without critical NAT entries needed for things like time synchronization.
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.
Assessment
This issue has not been assessed yet.