New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
personally I enable IPv6 preference where possible so anything IPv6-enabled I connect to uses IPv6 instead of IPv4
no attachment to it at all
0% for me as we don't have it yet, same as 80% word wide ISP's.
https://www.google.com/intl/en/ipv6/statistics.html
For some services, I prefer to listen on the IPv6 port, I think it's harder to find
Zero.
I avoid services which don't offer at least a shared IPv4.
ipv6 sucks, but i still use telnet and xmodem too.
Only to connect with IPV6-only server @host_c
Some path also has better performance with ipv6
Indirectly, nitter, invidious, redlib, binternet, etc which uses ipv6 space
I still consider IPv6 experimental, due to the amount of outages I see.
I have a few hosts where I've forgotten to disable IPv6.
That said at some point I do intend to slowly introduce IPv6 to my haproxy setup, but I was never comfortable doing that while my home ISP didn't offer IPv6 and I had no easy way of testing things were working. They do now support IPv6, so I will do the work to set up my home router to use it, but probably not for another couple of months. I've not had IPv6 at home for ~5 years now, so a bit longer is no big deal.
ipv6 is essential for people behind gfw, because of its super bigger address space, it’s harder for firewall to intervene. now it’s quite rare to block ipv6 in real life.
I love ipv6, untill I see letters in a address that my brain is used to see only numbers, I have nothing against it, yet it was rushed too early in my view.
For my home connection IPv6 usage is fairly common but not universal. On my VPSs I typically configure services to run dual stack by default since providers usually allocate much more IPv6 space than IPv4.
IPv4 is still required since many services and APIs are still IPv4 only.
I disable it on all my personal stuff.
My home and office ISP doesn't have IPv6 support. My mobile carriers don't support it. There is literally nothing I ever need access to that is only available over IPv6 that can't be reached over IPv4. Easier to just disable it completely for my personal stuff since it serves no purpose on my end.
From a business standpoint, we support it because it's expected to be supported but we do so minimally.
As long as there are people disabling IPv6, it won't be supported.
I use different ISPs and both use ipv6 as the primary and ipv4 as failback.
It's a privacy risk, without RFC4941. I just disabled it on all my device that doesn't need to be accessible from outside
On PTRDNS authoritative nameservers I see about 26% traffic over IPv6, all the rest is IPv4.
It's true that a lot of hosts and ISP do not implement any monitoring for IPv6, I've had quite a bit of IPv6 outages where at the same time IPv4 worked fine and no one else seemed concerned nor interested in any way.
It's good as backup connectivity too. You wouldn't believe how often ip4 is down but ipv6 still works at some providers. And vice versa as the other gentlemen say of course.
IPv6 is disabled on my PC:)
Wow xmodem takes me back !!!
Ward Christensen and I worked together and I launched one of the first BBS's in the UK which used it. I reckon Zuckerberg got all of his ideas from us.
As far as IPv6, at FOSSVPS we provide primarily NAT and IPv6. I initially found v6 a PIA but with AAAA records created, I find having the big range of v6 addresses makes things much easier.
The majority of our clients are from S.E. Asia and v6 (as @igctt mentioned) is much more convenient. However Europeans tend to be using NAT / v4.
So I provide NPM (Nginx Proxy Manager) for NAT users to connect http/s to VPS or they could use v6 direct.
Recently I moved all my thelounge -> IRC servers connections to IPv6 (with IPv4 as a fallback). It's much easier for me to deal with people who come to IRC via webchat to harass others, spam, etc., as most of them are behind NAT or dynamic IPv4.
With IPv6 connectivity, however, their IPs are usually allocated from individual /64 or /48 prefixes and once they get banned they don't know why refreshing connection don't allow them to come back
This does not affect people who use proper IRC clients, but lazy modern-day people on my network prefer webchat.
I have been pushing IPv6 for almost two decades. I've made sure even my DNS servers are on IPv6, and TLD name servers had v6 glue.
Naturally, Slow Servers is IPv6 first.
We could've switched over fully with a stronger effort, but a lot of people have been digging their heels in. The amount of money wasted on every single IPv4 address is staggering, for no real benefit.
We are building a short list for recommended IPv6 providers, to be picked among routed IPv6 hall of shame based on editor's assessment.
Now we know which providers to not include in the short list, and you'll be one of them.
Gaps we often see include:
Let's add:
This is interesting how it varies so widely~
on tmobile by default in newest deployments there is no IPv4 service (no NAT too), you are v6 only + dns servers that will resolve A-only to AAAA into ISP IPv6 space where last two chunks are the v4 and drop the A record. I frequently cannot ssh directly to any v4 ip.
I don't really care as long as it's $7/y I'll jump into the queue
Yapp, that is on me, i completely forgot about that, will ping you later.
Now that is a hard no, the service provided by that man is a A++++++, if he will not have ipv6 by 2055, I DON'T CARE !
as usual,
HOST-C
PS: even @yoursunny agreed, as I recall, in a thread that a 64 bit address with numbers would have been enough. Or am I mistaking. - a bit off-topik here.
Yes, may issue is with the god dam letters in ipv6
Deal! I'll pay by screenshot ♥️
I always wondered why no IPV5 ? 209.19.44.23.63
Wouldn't it have added a few billion IP's to the pool ? I don't know enough about networking to figure it out myself.