31–40 of 164 posts
Am I the only one that hates IPv6 ergonomics? I have to transcribe IPv4 addresses all the time, I'd hate to try and do it with a 128 bit address. Could they not have gone with 64 bit addresses, was 18,446,744,073,709,551,615 addresses really not enough?
Am I the only one that hates IPv6 ergonomics? I have to transcribe IPv4 addresses all the time, I'd hate to try and do it with a 128 bit address. Could they not have gone with 64 bit addresses, was 18,446,744,073,709,551,615 addresses really not enough?
What's with the cyclical "Ebb and Flow" of IPv6 if you select "IPv6 Adoption" and zoom in?
I wish my fiber ISP was part of that 50%. But nope, here I am behind a CGNAT and was promised IPv6 adoption about a year ago. Unfortunately the only other options in my area (downtown Milwaukee) are some form of wireless, DSL, or Spectrum. Don't get me wrong, even though my speeds are only about 50% of spec (gigabit symmetric), the upload speed alone is a reason to avoid any other provider. I'm also paying about $25/…
What's with the cyclical "Ebb and Flow" of IPv6 if you select "IPv6 Adoption" and zoom in?
Am I the only one that hates IPv6 ergonomics? I have to transcribe IPv4 addresses all the time, I'd hate to try and do it with a 128 bit address. Could they not have gone with 64 bit addresses, was 18,446,744,073,709,551,615 addresses really not enough?
I'm pretty sure I have IPv6, I just haven't figured out how to set it up on my Mikrotik router :/
If you don't need a tunnel it should be pretty painless, just set up firewall rules and enable IPv6 forwarding
Earlier quoted context omitted.
There is a lot of cultural inertia that instantly biases against anything new in sysadmin/netadmin circles. It's super annoying, tbh. A subset of technologists only seem comfortable with the technology that was available when they were 18-24, regardless of how old they get. "What's this? I never needed it before, what's the sysctl to turn it off?"
There is a lot of cultural inertia that instantly biases against anything old and stable in developer circles. It's super annoying, tbh. A subset of developers only seem comfortable with technology invented in the past 18-24 months, regardless of how untested and unstable it is. “What's this? It was written 2 years ago? It must be old and useless. I’m going to require my app to use the latest version and I don’t care…
About 5 years ago, I asked the owner of my fixed wireless ISP if he was planning to support IPv6 and I received a 500 word email rant about the uselessness of v6. I haven't asked again. (I still get a 0/10 score at https://test-ipv6.com/ )
There is a lot of cultural inertia that instantly biases against anything new in sysadmin/netadmin circles. It's super annoying, tbh. A subset of technologists only seem comfortable with the technology that was available when they were 18-24, regardless of how old they get. "What's this? I never needed it before, what's the sysctl to turn it off?"
IP6 requires a bunch of new tooling and configuration, and if running dual stack provides plenty of new opportunities for failure.
0/10 for Xfinity as well on test-ipv6
Xfinity provides /64 prefixes to their customers. There must be some missing configuration on your router. I have a 10/10 score.