Don't enable IPV6?

So my ISP recently announced that they support IPV6 so I enabled it in my router. I've been using it since then and didn't notice anything good nor bad.

Today I wa son Reddit and mentioned that I was using Google's DNS for IPV4 and IPV6 then one dude said "do not enable IPV6 if you are using IPV4" so I started wondering what all that is about. He didn't reply back to me when I asked for the reasoning behind this. Is there anything bad doing this that I am missing.

I searched on Google and this is one post I read:

Now I have to mention that I have been having issues with the connection on my Galaxy S20+ when I connect to WiFi, a speedtest would show regular speeds but when browsing NBR from my phone would have a hard time connecting to that site or would take ages to load, if I disabled my WiFi and just used regular data it's fast and snappy again so I'm not sure if enabling IPV6 has anything to do with this but I will disable it for now.

Just wanted to get the PROs opinion on this.

I don't know if it's a placebo effect but I am finding the loading of sites much faster now. I will try browsing Notebook Review Forum on my phone for a while if it works then all my suffering all these days could have been from IPV6

 

I keep IPv6 disabled on all devices for security purposes. Configuring a firewall for IPv6 as well adds a lot of complexity without good reason.

 

I posed this question to my son, who is a security expert. He would agree with you. He indicated that properly configuring for IPV6 is not a trivial problem, and that he would not encourage it until there are clearer benefits. We will definitely need it in the future, but not just yet.

 

I think this is actually a great topic. I don't disagree with the above posters, they make valid points, while I do have IPv6 enabled.

Even putting security aside, its still complicated even performance wise. If your ISP uses 6RD or a form of IPv6 through IPv4 tunneling you will see higher latency on IPv6 vs IPv4. Also if your target website has a similar stopgap IPv6 through IPv4 implementation you'd have slower load times even if you have more proper IPv6 implementation on your end. Best to keep IPv4 prioritized and use IPv6 as fall back if you want to use IPv6, some routers allow this. Earlier I did have some issues with some sites when using IPv6 like DSL Reports Speed Test that would fail, though it's resolved now. My ISP Comcast uses Dual Stack. My Old ISP CenturyLink used 6RD and I always had IPv6 set to fallback on it.

IPv6 as necessity for clients is an inevitability as we are running out of IPv4 dresses but they are still refarming some old unused ones and bringing them back into the usable pool, for now. Also an ISP can still use a large number of IPs on their own internal network for their clients and use NAT to connect to external networks just like how at home you only have one IP from your ISP but have numerous clients on the internal network thanks to your router using NAT. So for now you can keep it disabled if you want.

If anyone finds fault with anything above feel free to correct me!

 

For the LAN side it's just going to make things overly complicated.

WAN side just disable it and let the ISP handle the translations as you'll be able to properly manage firewall settings with IPv4 much easier.

V6 is more of a provider need due to the exhaustion of v4 address space due to everyone now having multiple devices that are all needing an IP to operate.