FWIW, IPv6 has worked just fine for me since they enabled it (I don't think I had it when I initially got them as my ISP). I also have found them pretty responsive to even technical feedback, but maybe I've just been lucky.
Of course, there was that one time they "upgraded" our building and forgot to re-plug my line to the router, but, oh well..
Overall, this seems like a super niche topic for HN. :)
I believe it heavily depends on what kind of infrastructure you are using with them.
If you are on their old legacy network (aka, you have a RJ45 Ethernet jack into your house) you will likely going to have more issues than if you are on their (X)GPON network.
I had IPv6 working for a while on mine, but realize that for some insane reason that there was basically only one v6 prefix across my entire distribution switch (basically the switch shared with a few 100 other properties). so anytime that i was going to get a v6 i was effectively stealing it from another flat/house.
unfortunately trying to get in touch with anyone from Hyper-optic is really tricky, so I just gave up
they have since upgraded some of the infrastructure in the path, mostly moving away from Huawei to Nokia, but I am not entirely sure that has improved the situation.
I would argue that having to pay more than $20 for an address, having to do weird NAT hole punching to get a direct connection between two machines, and having an internet that can easily be completely scanned by hackers are all things that are not "working".
Working for you != working for everyone
Basically functioning != Working as well as it could
There are more advantages to IPv6. We don't see all of the advantages because we can't use them, because we are still largely stuck in an IPv4 world. This is a problem caused by not enabling IPv6.
My ISP provides me with upto 8 ipv4 addresses if I want them. At auction an IPv4 to buy is only $20 each. not $20 a month, $20. Having an ISP rips you off is not mitigated with ipv6, you still have an ISP that rips you off.
I have to put firewall rules in anyway (as I don't want a random device on the internet to be able to talk to my bathroom speaker), so what's the difference?
I get an RTP stream pushed from a source, if I want it on my laptop I dst-nat it to my laptop, if I want it on my desktop I dst-nat it to my desktop, no need to change the destination on the source IP. How would I do that with ipv6 - DNS I guess, if the source supports DNS lookups (some do, most don't)
I also have the advantage of being able to steer outgoing traffic via either my DSL or via my 4g depending on various rules (including source IP, target IP, protocol, src/dest ports, DSCP tags etc). I believe I can do this with NPT on ipv6, same as on ipv4.
But sure, security through obscurity is useful.
In any case I still have to maintain an ipv4 network as some services still won't work on ipv6 only subnets (even with NAT64 and DNS64), so the choice is either having an ipv4 network, or having an ipv4 and ipv6 network.
Of course, there was that one time they "upgraded" our building and forgot to re-plug my line to the router, but, oh well..
Overall, this seems like a super niche topic for HN. :)
If you are on their old legacy network (aka, you have a RJ45 Ethernet jack into your house) you will likely going to have more issues than if you are on their (X)GPON network.
I had IPv6 working for a while on mine, but realize that for some insane reason that there was basically only one v6 prefix across my entire distribution switch (basically the switch shared with a few 100 other properties). so anytime that i was going to get a v6 i was effectively stealing it from another flat/house.
unfortunately trying to get in touch with anyone from Hyper-optic is really tricky, so I just gave up
they have since upgraded some of the infrastructure in the path, mostly moving away from Huawei to Nokia, but I am not entirely sure that has improved the situation.
https://datatracker.ietf.org/doc/html/rfc4448#section-4.6
Working > New
Working for you != working for everyone
Basically functioning != Working as well as it could
There are more advantages to IPv6. We don't see all of the advantages because we can't use them, because we are still largely stuck in an IPv4 world. This is a problem caused by not enabling IPv6.
Of course, once you figure out it's IPv6 related you can then work on figuring out what's actually going on.
I have to put firewall rules in anyway (as I don't want a random device on the internet to be able to talk to my bathroom speaker), so what's the difference?
I get an RTP stream pushed from a source, if I want it on my laptop I dst-nat it to my laptop, if I want it on my desktop I dst-nat it to my desktop, no need to change the destination on the source IP. How would I do that with ipv6 - DNS I guess, if the source supports DNS lookups (some do, most don't)
I also have the advantage of being able to steer outgoing traffic via either my DSL or via my 4g depending on various rules (including source IP, target IP, protocol, src/dest ports, DSCP tags etc). I believe I can do this with NPT on ipv6, same as on ipv4.
But sure, security through obscurity is useful.
In any case I still have to maintain an ipv4 network as some services still won't work on ipv6 only subnets (even with NAT64 and DNS64), so the choice is either having an ipv4 network, or having an ipv4 and ipv6 network.
The former is less work and more secure.
I haven't had the same problems this guy has, although I do believe his issues are real.