First thing I do on a fresh Linux install is set ipv6 to deactivated. Fixes all my initial Linux install problems. I don't question it, it just works every time.

▲

BadBadJellyBean 3 hours ago | parent | next [-]

Something is very wrong with your network then. I never needed to disable IPv6. Maybe you should question it.

▲

ash 2 hours ago | parent | next [-]

It is harder to maintain two networks instead of one. Potential problems double. Hacks like RFC8305 "Happy Eyeballs" become a must.

▲

PacificSpecific 3 hours ago | parent | prev [-]

Fair enough. I do question it often.

It's a standard Asus router but it's given me a lot of ire. I hate to say it but it's never a problem when I install windows on the same machines

(I'm currently in the process of trying to completely remove windows from my life)

	▲	drewfax 2 hours ago \| parent \| next [-]
		Similar experience. I bought an ASUS router and enabled IPv6. It slowed down everything down. Immediately flashed OpenWrt on it, IPv6 works like charm. It's usually bad configuration done by the router vendors. It doesn't mean IPv6 is bad.
	▲	CrLf 3 hours ago \| parent \| prev [-]
		There are maybe many buggy routers still out there that reset the IPv6 flow label field when they shouldn't, breaking hash-based load-balancers (the symptom is TCP connections spontaneously reset). IIRC, a workaround was to prevent Linux from setting this field, or force-reset it on every outbound packet using netfilter.

▲

xyst 3 hours ago | parent | prev [-]

Skill issue.

▲

CrLf 3 hours ago | parent [-]

UX issue, and UX issues are often downplayed by engineers, leading to adoption failures.

Another such example is SELinux, which would have prevented so many vulnerabilities from being exploited, but whose poor UX also caused everyone to disable it at install time.

SELinux's UX was significantly improved many years later, but already too late to change ingrained opinions. There are a lot of ingrained opinions about IPv6 too.

▲

inigyou 2 hours ago | parent | next [-]

Conversely it means people who have ISPs that do IPv6 just have IPv6 and don't need to turn it off. Because it just works. The other day my IPv4 was down and I didn't even notice.

	▲	CrLf 24 minutes ago \| parent [-]
		I don't expect any ISP to do IPv6 today and deploy routers with a flow label bug... Those types of bugs no longer go unnoticed. IPv6-only ISPs might hit other issues, though. They have to bridge to IPv4 somewhere.

▲

Levitating 2 hours ago | parent | prev [-]

> SELinux's UX was significantly improved many years later

in what way?

	▲	CrLf 43 minutes ago \| parent [-]
		Most of what people see as "SELinux" is actually the default policy, which started out as way too strict. Then SELinux-enabled distros such as Red Hat moved to a policy that only applies to system services, and leaves user-launched binaries as if SELinux was disabled. And even for system services, you can disable SELinux for one service (permissive mode) and leave it enabled for the rest. This has been the case for more than 10 years, but the damage was done. It's now very hard for users even considering learning the basics (which are not hard).