Comment by duskwuff

Comment by duskwuff 4 days ago

6 replies

I wouldn't be surprised if a lot of the hardware under management (e.g. IP cameras, NVRs, cable modems) lacks support for IPv6, and/or the customer networks that it's resident on don't have working IPv6 transit.

zokier 4 days ago

The solution is to run ipv6 on the overlay and have the customer site gateway thing they have to translate it to target ipv4. Conveniently you can do the translation it more or less statefully and very easily because you can just embed the ipv4 addr in ipv6. For example you could grab a /64 prefix, assign 32 bits to customer/gateway id and other 32 bits to target ipv4 addr.

  • wmf 4 days ago

    Basically Teredo.

    • eqvinox 3 days ago

      Basically NAT64. (Teredo requires the IPv4 hosts to have awareness of it, this doesn't.)

reactordev 4 days ago

It’s definitely on the software side… The human side.

  • eqvinox 4 days ago

    The squishy side.

    Coincidentally I think that's an overestimation on the number of devices that don't support IPv6. At this point, vendors have to go out of their way to disable IPv6, and they lose out on some government/enterprise tenders that require IPv6 even if they're not running it (yet).

    • reactordev 4 days ago

      Right, IPv6 is baked into the NIC, so it’s up to developers to use it.