feature wish: --block-ipv4
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 3.4k
- PR merge metrics
- No merged PRs in 30d
Description
I've been speaking to people that want to move to ipv6 only inside their networks, and their VPNs.
This brings up the same problem we had with ipv4 only + redirect-gateway VPNs and clients trying to access dual-stack hosts - "the other protocol" will then leak out to the Internet (assuming dual-stack on the client ISP for a long time).
Thus, we need --block-ipv4 with similar semantics as --block-ipv6...
(Note: whether or not --block-ipvX should also auto-enable --redirect-gateway <x> is up for discussion, but it needs to be consistent between IPv4 and IPv6)
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 locating the existing --block-ipv6 implementation and its tests, then compare how redirect-gateway behavior is handled for each protocol. Done means a consistent --block-ipv4 counterpart with documented semantics, including a resolved decision about automatic redirect-gateway behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100