

Tailnet appears to be Tailscale which is Wireguard underneath. This means it operates at layer 3 (IP). However a bunch of smart home stuff (mDNS, WoL, etc) all depend on layer 2 connectivity (same subnet).
That means some stuff won’t work correctly.


Tailnet appears to be Tailscale which is Wireguard underneath. This means it operates at layer 3 (IP). However a bunch of smart home stuff (mDNS, WoL, etc) all depend on layer 2 connectivity (same subnet).
That means some stuff won’t work correctly.


Mine was flashing my Emporia Vue2 home energy monitoring system with ESPHome
I’m always interested in sensors (got a bunch of home made Air Quality and CO2 sensors) so seeing real time energy was cool.
With the per circuit sensing I’m experimenting with identifying if my fridge is left open, or identifying when my clothes washer is finished.


It’s not generally a hardware problem. It’s a resourcing problem. Companies like GitHub will have complex software and architecture. IPv6 requires them to get a pool of IP addresses, come up with an IP address management strategy, make sure all hosts have IPv6 addresses meaning that now provisioning systems and tooling to management DNS has to plumb IPv6 addresses through too.
Then the software stack has to support it. Maybe their fraud detection or auditing systems have to now support IPv6 which means changes to API schemas.
None of this is a good reason why they shouldn’t do it, but I’ve had to make similar decisions at my job as a software engineer on what looks to be simple but actually requires changes across systems.
It just updated on my phone to the new icon. I tried to give it a chance but wow that looks not great. Something about the scale and lack of discerning features.