No, but it’s far easier to explain how to configure your home network such that 182.168.1.* is for your regular devices like laptops, etc. and 192.168.2.* is for your IoT devices. Then block all access from 192.168.2.* to the internet so your IoT devices can’t “phone home”, can’t auto-update without your knowledge, can’t end up as part of a botnet, etc.

[–] StopSpazzing@lemmy.world 6 points 1 day ago (1 children)

That's the thing, you are still thinking in ipv4 terms, and that's ok. It's a different way to think of things using ipv6 and the proper way to configure them. No worries tho. Not like you are being forced to ipv6 for internal home networks.

[–] porous_grey_matter@lemmy.ml 8 points 1 day ago (1 children)

Ok, so what would the equivalent be?

[–] bubblewrap@sh.itjust.works 12 points 22 hours ago

Create a new /64 and don't give it a route to the internet.