United States IPv6 adoption over 50% • Hacker News Board

Re: United States IPv6 adoption over 50%

#161

Post by VectorLock » Mon, Jan 03, 2022, 3:23 AM UTC

brendoelfrendo wrote: post #128

VectorLock wrote: post #120

Earlier quoted context omitted.

"anything inside my home network from anywhere on the internet" doesn't sound much like robust access controls. I wouldn't trust the horrible default passwords and lax security built into most devices for home use to be exposed directly to the Internet even with a firewall.

Robust access controls would be things like certificate auth, MFA is cool, fail2ban is good, maybe throw in some roles there; whatever floats your boat. So yeah, your security model should involve not using default passwords and not using devices that have unchangeable default passwords. Again, people are depending on something that isn't really designed to provide security to provide security. Devices that have horr…

If your threat model involves baby sitting every device in your network and making sure they're robustly secure.

Some people just want their lightswitches to work.

Re: United States IPv6 adoption over 50%

#162

Post by Dagger2 » Tue, Jan 04, 2022, 3:59 PM UTC

usr1106 wrote: post #159

zamadatix wrote: post #154

Earlier quoted context omitted.

In 464XLAT something on the client side (be it say Android phone itself or TMobile home router) acts as a CLAT to translate local v4 to v6. On the T-Mobile egress it'll act as a PLAT and convert back. There is some other glue to make these two work together. They had a good NANOG talk on it a few years back https://youtu.be/Xl-hIyZSAmA For other offerings like NB-IoT or business PCN you're still able to do either it'…

That's interesting. We use a Sierra Wireless EM 7455 (IIRC, not in work mode now...) with generic global firmware. I am 100% sure our software performs no 4 to 6 translation. So it would need to be in the modem. But that would mean it needs to be a standardized operator-independent protocol. Never heard that such thing exists. > I'm not sure if there are still any legacy connectivity options that will fallback to v4.…

464xlat is standardized and can be set up automatically. All it needs is a DNS query to any v4-only hostname to detect if DNS64 is in operation.

Most 4g modems work as routers exposing an ethernet interface to the host, so it's certainly possible that it's doing 464xlat in the firmware, and if it doesn't tell you on some sort of status page then the only real hint that it's doing it would be a reduced path MTU.

I wouldn't be surprised if T-Mobile offer legacy service to any type of business contract or non-phone client though.

Re: United States IPv6 adoption over 50%

#163

Post by usr1106 » Thu, Jan 06, 2022, 1:02 AM UTC

Dagger2 wrote: post #162

usr1106 wrote: post #159

Earlier quoted context omitted.

That's interesting. We use a Sierra Wireless EM 7455 (IIRC, not in work mode now...) with generic global firmware. I am 100% sure our software performs no 4 to 6 translation. So it would need to be in the modem. But that would mean it needs to be a standardized operator-independent protocol. Never heard that such thing exists. > I'm not sure if there are still any legacy connectivity options that will fallback to v4.…

464xlat is standardized and can be set up automatically. All it needs is a DNS query to any v4-only hostname to detect if DNS64 is in operation. Most 4g modems work as routers exposing an ethernet interface to the host, so it's certainly possible that it's doing 464xlat in the firmware, and if it doesn't tell you on some sort of status page then the only real hint that it's doing it would be a reduced path MTU. I wou…

> Most 4g modems work as routers exposing an ethernet interface

Not idea about most. I have seen it that way, but our Sierra Wireless requires ModemManager and appears as a wwan network interface.

Re: United States IPv6 adoption over 50%

#164

Post by Dagger2 » Sat, Jan 08, 2022, 4:33 AM UTC

thyrsus wrote: post #118

sneak wrote: post #10

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?"

As a sysadmin, I'd be fine if the stuff on top supported ipv6. E.g., I'm not aware of support for ipv6 in Kubernetes. In anticipation, where can I catch up on ipv6 routing? Does the number of route entries explode? I do need a "business reason" to adopt it, since the Center for Internet Security benchmark dings your system if it is turned on.

Kubernetes does do v6 today. Given the amount of address space a Kubernetes cluster can use, it's useful there.