I think I figgered it out. I turned the cable-modem off because of the Windows Update thing. I switched systems, and forgot to turn the cable-modem on.
Did I confuse NetBSD? Could that have been fixed by running an rc.d script? On Sun, Feb 13, 2022 at 6:20 PM Michael van Elst <mlel...@serpens.de> wrote: > > On Sun, Feb 13, 2022 at 12:51:45PM -0500, Todd Gruhn wrote: > > I doubt I misconfigured anything DHCP related. This started happening > > last night. > > NetBSD worked fine for a couple of months. Could the ISP have changed > > something? > > Possible, but that would of course affect all devices in your network. > The best way is not to guess but to actually watch what happens. Start with > checking the dhcp data with the 'dhcpcd -U' command. > > > -- > Michael van Elst > Internet: mlel...@serpens.de > "A potential Snark may lurk in every tree."