It is NOT a good idea to disable or deprioritize IPv6

[lucasmz-dev]

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]

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]

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

[lucasmz-dev]

@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

[FatBastard0]

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!

[Squtzy]

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/

if I have IPV6 enabled and/or try and set "my own" DNS I have the issue of Steam (Games app) giving me extremely low download speeds. By preferring and/or disabling IPV6 I no longer have that issue. Plus my ISP doesn't provide IPV6 yet so no reason to use it.

[lucasmz-dev]

That doesn't seem like a widespread problem + being too unspecific (DNS or IPv6?) it still wouldn't warrant a default

It is possible you have broken IPv6 connectivity and that's causing issues