HewlettPackard / HewlettPackard/PacketRusher
[FEATURE] Remove dependency on kernel module
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 193
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Building and installing PacketRusher currently relies on building and loading a kernel module. This makes PacketRusher difficult to package and distribute (ex. as a container image or a snap) and limits its potential usability.
Describe the behavior you'd like
Ability to distribute PacketRusher as a container image and/or snap.
Potential alternatives to kernel modules
- eBPF: Implementing the packet processing logic using eBPF could offer the same performance (kernel level packet decisions) and improving portability
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
No files, tests, or entry points are named. Start by tracing the build and installation steps that require the kernel module, then assess the proposed eBPF and container or snap distribution paths. Done means PacketRusher no longer depends on building or loading that module and can be packaged through at least one requested distribution path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- devops, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100