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.

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

It is NOT a good idea to disable or deprioritize IPv6 #3061

Open
lucasmz-dev opened this issue Nov 23, 2024 · 4 comments
Open

It is NOT a good idea to disable or deprioritize IPv6 #3061

lucasmz-dev opened this issue Nov 23, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@lucasmz-dev
Copy link

lucasmz-dev commented Nov 23, 2024

Describe the bug

This tool recommends the user and automatically selects this option (disable IPv6) on many presets.

Expected behavior

This should not be the default, neither recommended.

Screenshots

Additional context

The explaining behind it seems to be "if you don't have IPv6, it's faster" and to a certain point that's true, it would've meant no checking for AAAA records and such, however, most software already deals with this gracefully.
Browsers for example will detect that there is no IPv6 connectivity and ignore IPv6 and go directly to using IPv4-only.

All this is essentially dealt with, and where it is not, it is isn't worth the trade off of no IPv6.

IPv6 will give many, many people outside North America access to a proper public internet address, not one behind CGNAT where P2P and other applications are broken.

Because IPv6 is also cheaper, it can also end up having better routing than IPv4, an example for me was having 6ms to Cloudflare instead of 31ms.

Happy Eyeballs: https://www.rfc-editor.org/rfc/rfc6555
IPv6 SLAAC Privacy Extensions: https://datatracker.ietf.org/doc/rfc4941/ https://www.internetsociety.org/resources/deploy360/2014/privacy-extensions-for-ipv6-slaac/

@lucasmz-dev lucasmz-dev added the bug Something isn't working label Nov 23, 2024
@lucasmz-dev
Copy link
Author

There is one situation where disabling IPv6 is benefitial, and that's when you're forced to use a broken IPv6 stack. That's pretty much it though, and even on those, a lot of apps will indeed trigger Happy Eyeballs.

My suggestion: do not ever default to enabling this option, you can keep it, but put the reasoning behind to "only choose this if you have a broken IPv6 connection, not if you simply don't have one"

@zmileski
Copy link

selects "Prefer IPv4 over IPv6" not "disable IPv6"

@lucasmz-dev
Copy link
Author

lucasmz-dev commented Nov 23, 2024

@zmileski that would also not be a great default, same reasons as above

though as a replacement (still, the fact it should not be the default still applies) it is better if the user is forced to use a broken IPv6 network

@lucasmz-dev lucasmz-dev changed the title It is *NOT* a good idea to disable IPv6 It is NOT a good idea to disable or deprioritize IPv6 Nov 24, 2024
@FatBastard0
Copy link

I've prayed the uninstall and it doesn't put the ivp6 back on. If anybody in this sees a way to reactivate through a program or a script, please let me know. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants