@xHire It's entirely possible that fixing the problem will be something I do myself. It's a small shop, as evidenced by the fact that I was setting up my own work machine.
Post
Thanks for pointing out the fix for anyone who needs it, but (there's always a "but") isn't it a bit strange to be running only IPv6 on a LAN?
@ecadre The LAN was dual stack with working IPv4 and broken IPv6.
The Debian installer kept picking the IPv6 addresses and not failing over to IPv4 - it might have done so eventually, if I had waited long enough, but I had things to do!
I'm sure there are other ways to work around the issue, but this was simple and did the job.
@HerraBRE Hm… did you report the problem? Perhaps your cool company should improve its network monitoring or (even better) transition to IPv6-only LAN while retaining reachability of IPv4-only services. That would ensure fast problem detection and wouldn’t increase the burden on network administrator(s).
(Or at least IPv6-mostly if your cool company still has some legacy HW that isn’t IPv6-ready.)
@xHire It's entirely possible that fixing the problem will be something I do myself. It's a small shop, as evidenced by the fact that I was setting up my own work machine.