Is anybody using only IPv6 in their home lab? I keep running into weird problems where some services use only IPv6 and are “invisible” to everyone (I’m looking at you, Java!) I end up disabling IPv6 to force everything to the same protocol, but I started wondering, “why not disable IPv4 instead?” I’d have half as many firewall rules, routes and configurations. What are the risks?
It fucking sucks. I’ve been hearing about it for twenty plus years and it’s caused me more problems than it’s solved. Comcast DNS routinely breaks connecting to niche sites like Microsoft 365 😑. Its overly complicated and easier to screw up. If turning off IPv6 would stop solving more problems maybe I’d give it a better go, but as it stands it’s like the USB-c standard of a clusterfuck of poor design and implementation in practice.
I’m sorry you’ve had a poor experience, but I’ve had nothing but smooth sailing since my ISP gave me a /64. I had to re-learn most of what I knew and unlearn a few bad v4 habits, but v6 has solved issues that I was tired of dealing with. I can’t imagine what you’re doing to think it’s more complicated and easier to screw up than v4.
If DNS wouldn’t constantly break I’d be more open to learning. Right now what’s the point?
And that is the biggest problem it is different then ipv4 and you have to learn new stuff. My worst was up keeps changing the prefix so I had to find out how to write an allow rule that ignored the prefix and only allowed the end but since they always stayed the same.
Lets say you have a bunch of self hosted servers. How are you tracking their ips on ipv6? Are you able to type the ip off the top of your head? I feel like its very simple with ipv4.
Use the names. I connect to my self hosted services all the time over ipv6 using DNS. Still use ipv4 to ssh though as my prefix changes alot,sometimes multiple times a day.
Having used Azure for a few years now I feel like that might not be entirely on Comcast.
Maybe, but I have yet to see another home ISP with the same problem.