Found the one case where IPv6 in a dual-stack home network actually worked way better than IPv4 which worked 50/50. Fucked up network topologies which shouldn't exist.
Friend complained to me that after switching to Ethernet on the living room PC, some websites would stop loading on it randomly between days. After checking the usual like DNS being fucky, and Windows drivers, I've found between reboots that the computer would get IPs assigned to it via DHCP in different networks (192.168.0.0/24 and 192.168.1.0/24). An intriguing hunt for the issue began which uncovered the attached cursed topology.
IPv6 managed to live in this cursed environment via SLAAC, but for DHCP enabled IPv4, it was simply too much. Somehow it went unnoticed for many years besides the occasional "Living room WiFi stopped working".
Behold.
screenshot-20260630-183508-82.png
Friend complained to me that after switching to Ethernet on the living room PC, some websites would stop loading on it randomly between days. After checking the usual like DNS being fucky, and Windows drivers, I've found between reboots that the computer would get IPs assigned to it via DHCP in different networks (192.168.0.0/24 and 192.168.1.0/24). An intriguing hunt for the issue began which uncovered the attached cursed topology.
IPv6 managed to live in this cursed environment via SLAAC, but for DHCP enabled IPv4, it was simply too much. Somehow it went unnoticed for many years besides the occasional "Living room WiFi stopped working".
Behold.
screenshot-20260630-183508-82.png
スプリットショックウイルス †
