NullNet-ai / NullNet-ai/nullnet
Use eBPF to handle the network layer wherever it's possible
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5
- Forks
- 2
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 19
Description
Currently we're using a mix of iptables, nfqueue, and eBPF to handle the Nullnet's networking.
We should convert all the iptables-like code to eBPF following the cilium model.
[!NOTE]
As stated in the
nfqueue-rationale.mddocument, probably not all the network-layer code can be successfully migrated toeBPF
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 reading nfqueue-rationale.md and comparing the current iptables, nfqueue, and eBPF networking paths with the Cilium model referenced in the issue. Identify which network-layer code can be migrated and which cannot; done means the applicable iptables-like code uses eBPF while the documented exceptions remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100