NAT64

So it's running on my desk right now, but getting it also integrated with a thread border router so I can get multiple devices and feed it into this one border router device and it would go up to Lion or whatever platform that you could imagine because the biggest issue with that has always been the NAT traversal the ability to basically take all these interconnect devices usually on IPv6 and then send them out to whatever server you're trying to talk to And that's what Particle tried to do with their system.

And they were running into so many headaches running that NAT64 on an NRF52.

I think that's the main reason why they gave up on that project.

It was just infeasible.

If you are standardizing on IPv6, external IPv6 addresses are now supported for standard Cure networking across VPC subnets and load balancing in preview.

And over in Cloud NAT, NAT64 support for PrivateNet is generally available, enabling seamless IPv6 to IPv4 network address translation.

In security and IAM, VPC Service Controls has added automated remediation suggestions to its violation analyzer in preview.

When an access denial occurs, the remediation engine parses the audit logs and generates narrowly-scoped, least-privileged policy updates, proposing exact ingress or egress rules, VPC accessible services updates, or context-aware access levels to resolve perimeter blocks quickly.

So third-party sites, website content, anything you're consuming off those platforms, if they don't have v6 support, it's not like you're going to change it overnight.

You can obviously put it through a translator, So you could have control over the capability to put it through a NAT64, but the reality is you can't do that for everyone at home unless you're doing VPN.

But if you're doing local internet hop-off, you have zero control over how that's going to play out.

Yeah,