That’s the reason I killed IPv6 on my network.
That’s the reason I killed IPv6 on my network.
Only when it’s traumatizing.
Things that seem to go well and then later need intervention are the worst.
Suddenly I’m Gandalf: “I have no memory of this place.”
A hairy network issue!
The switch (that I’m returning today, after it failed completely yesterday evening) is a bit fancier than your average switch. It kept reverting to default settings, including its default IP address - which meant it was not using the same set of networking instructions as my router, preventing everything it was connected to from accessing the internet.
I had a switch wig out today and whatever it was doing poisoned all the dhcp leases on the network as they came up for renewal (assigned IPs on the wrong subnet - even though it wasn’t supposed to assign IPs at all). It took me a very long time to figure out, because not everything failed at once. Plus, even after I’d swapped the switch, some devices just started working, and others needed their leases reset manually. An hour in, my wife was in the fetal position clutching a squishmallow.
Well, I just realized I completely goofed, because I went with .arpa instead of .home.arpa, due to what was surely not my own failings.
So I guess I’m going to be changing my home’s domain anyway.