"Here is the classical topology of home network." ... "And all the LAN hosts have one /64 IPv6 prefix."
Are people really deploying IPv6 like this? Rather than a /64 to a vlan?
(Personally, in the home, I'm just using DHCPv6-PD to delegate a different /64 to each VLAN).
Not just because the IoT devices are prone to attack because they may not get many updates, but also because they often need 2.4 GHz or may only support WPA 2. So my main network can be WPA3 only and 5 GHz only but the other networks are more lenient.
People may not know they're running a VLAN, but VLANs aren't uncommon either.
[0] Because what else would you use to decide how to block or permit traffic if you can't distinguish by the interface that the traffic came in on?
That is only because I want to though, I agree that the average home network will not have VLANs.
https://www.telus.com/en/support/article/create-a-guest-netw...
This, on the other hand, is Hacker News.
Also, just because you know how to do it, doesn't mean you want to tinker with a complex network topology on your home network.
But the topology given in the article shows three separate, non-overlapping /64s, one for each host/router. (Although one would assume that the router at least must have an interface in each subnet, even if that's not what the diagram shows).
One might hope these would be on separate VLANs, as overlaying multiple subnets on one VLAN would be a bit iffy. I've not spotted anything in the article other than the diagram to detail interface configs.