inet with layer 3 jump rather than ip and ip6
- Dominant language
- No language data
- Stars
- 9
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thanks for sharing that nftables. Experimenting with ip, ip6 and inet in nftables, the approach used in https://wiki.nftables.org/wiki-nftables/index.php/Simple_ruleset_for_a_server with a jump according to layer 3 protocol from an inet table chain was less error-prone to me. What is your view of that approach?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the repository's nftables template with the linked Simple ruleset for a server guidance, focusing on ip, ip6, and inet chains and the proposed layer 3 jump. A maintainer decision is needed before implementation; done would require a concrete, agreed change to the template or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100