• Mandatory Cloud Connectivity: Bambu Lab’s firmware and apps route data through Chinese Tencent servers, sparking fears of potential remote “kill-switch” capabilities.

Perhaps this will have the silver lining of helping Bambu to roll back their newer cloud-only firmwares. They’re decent printers offline.

Hope I didn’t step on toes. The gist of what you said is on the money.

I love that ipv6 is becoming more mainstream and well implemented. That said, some providers in my home country still don’t support or use ipv6.

Perhaps I can improve this a little.

SLAAC is for stateless assignment of an address without dhcp. It’s what android uses exclusively for example. Delegated prefixes (/64) can be assigned by SLAAC or DHCPv6, and openwrt works with either. OP’s provider may not even use SLAAC, or at least make it secondary since SLAAC and DHCPv6 don’t always play nicely.

In the case of privacy extensions, this is up to the clients. Some clients might even not use them. Global temporary addresses are an attempt to stop fingerprinting. They’re largely ineffective these days however. Importantly, that temporary global address is still globally accessible (remember, there is no NAT), although most OS’s will ignore incoming connections. Otherwise, correctly, clients should have a couple of ipv6 global addresses.

There is misunderstanding here, perhaps about what the OP asked. I’ve interpreted the question to be why there are two different ipv6 addresses. I suspect you’ve interpreted it to be why is there a ipv4 and ipv6 addresses. At least I hope so.

I gather that insulting internet randos is what you do for a living.

Cgnat is for ipv4, has nothing to do with ipv6. Suggest reading up on ipv6.

This is fairly normal to receive 2 ipv6 addresses, depending on your provider. In my case, I receive a /128 address (single global address), and a /48 address (delegated global prefix). In addition, there is the link local address that will be fe80:… Delegated prefixes allow your internal devices to be assigned a global address within that subnet and access ipv6 resources directly. Feel free to ask more.

And the misleading article continues to circulate. Bose are not open sourcing any software. They are simply publishing the API for the device so that others might build software.