oxidecomputer / oxidecomputer/opte
Early execution of stateless firewall rules on ingress
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
We need a way to execute stateless firewall rules early in the ingress processing stack. This way stateless firewall rules can block high-volume traffic events without incurring large amounts of stateful flow tracking resources.
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
Start by tracing the ingress processing stack and locating the stateless firewall and stateful flow-tracking paths. Done means stateless firewall rules can execute early enough to block high-volume traffic without incurring substantial stateful flow-tracking resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100