dislabled

You're right that IPv6 doesn't need NAT for its original purpose (address scarcity). But "there is no NAT in IPv6" isn't quite accurate: NAT still exists in IPv6

NAT66 (stateful, like NAT44) exists but is discouraged. More relevant is NPTv6, a standardized stateless 1:1 prefix translation, not the many-to-one port-overloaded NAT you're used to from IPv4. It doesn't do address+port multiplexing, so it doesn't break peer-to-peer the way NAT44 does. So the "NAT is the enemy of p2p" argument applies to stateful NAT44-style translation — not really to NPTv6, which preserves end-to-end host addressability and just swaps the prefix.

You can absolutely build a fully functional internal network on ULA (fd00::/8) alone — routing, DNS, services, all independent of any ISP-delegated prefix. But ULA is explicitly non-routable on the public internet, so a pure ULA network is isolated: internal-only, no internet reachability.

Afaik apt-get upgrade would not add or remove packages, where dist-upgrade would. However apt upgrade will install new packages but not remove any. Where full-upgrade (new naming, but dist-upgrade is also kept for the same function) will also remove packages.

Good post. And i would like to add for anyone to be able to use hypervisor escape, you also need a vulnerability in the software presented to the internet. And even then, the chance that anyone would waste a zero day on a homelab is pretty slim..

Idk know if you can still get the ifan03, but I personally use an ifan04-H (230v 50hz) with esphome flashed on it.

In automation, there is more steps than that. You would use barriers, where one should be physical. For certain applications, you would also use a failsafe feedback loop. In this case, disaster could have been averted with a flow restrictor valve.

Nah, I have it as a vm on a 2u server. I used to have it on a 1 metre extension also, and as soon as I changed the aqara devices, network was stable. I only changed the adapter because I wanted one on LAN.

I used to have a sonoff zigbee 3.0 stick, which was a good device. But back then I still had problems. It probably depends on how many devices you have, but for me, especially when I had a lot of aqara router devices, they took down the whole network from time to time. And they would constantly fall out of the network. I still have one socket switch left, and it triggers by turning on the light in the same room(IKEA switch). There is no automation linked for this.. Only solution is to downgrade the firmware of the socket switch several versions.

I'd just like to warn about the reverse way, using aqara products on a general hub. I'm running HA with z2m myself, and used to have a whole array of aqara devices. They caused me nothing but problems, so I have slowly phased them out to similar devices which actually follow the zigbee standard.

Yeah I know, i have turned down 2 potential ISPs already, because they use cgnat. Too bad, because they are cheaper. Just wish ipv6 would really catch on soon.

Yeah, I just made a quick script that queries my public IP every 5 minutes, then changes the a-records via the registrar's API, if it detects a change.

My ISP only have static ipv4 available for businesses. The price increase is quite a lot. I have been experimenting with ipv6, though I will loose connection when I am at someone else's WiFi with no ipv6.. It's there as a fallback for now.

I don't really see why you shouldn't... I have mine behind a reverse proxy, which puts SSL on the public endpoint. The biggest "issue" today, is the isp rotating my ipv4 address to often.