Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feature wish: --block-ipv4 #652

Open
cron2 opened this issue Dec 6, 2024 · 1 comment
Open

feature wish: --block-ipv4 #652

cron2 opened this issue Dec 6, 2024 · 1 comment
Labels
DCO dco-win enhancement feature non-trivial change this is a larger code change, not a simple bugfix

Comments

@cron2
Copy link
Contributor

cron2 commented Dec 6, 2024

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)
@cron2 cron2 added enhancement DCO non-trivial change this is a larger code change, not a simple bugfix dco-win feature labels Dec 6, 2024
@cron2
Copy link
Contributor Author

cron2 commented Dec 6, 2024

10:42 < dazo> and ... Core/3 has --block-ipv4 too ....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
DCO dco-win enhancement feature non-trivial change this is a larger code change, not a simple bugfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cron2