After a reboot of my new server, the Kea DHCP server did not respond to DHCPDISCOVERs or DHCPREQUESTs

Saw an exceptionally bad commercial tie-in the other days, Oreos, and Star Wars

My pet Roomba, Dobby, got a thread wrapped around his constantly rotating whisk brush. Soon after that, a carpet loop got wrapped in there, too.

I falsely believed that I had found a wordle state where an elaborate regular expression with alternations gives fewer possible answers than a simple regexp in a pipeline with extra greps.

I was wrong.

I had to use the world’s dumbest keyboard at a parking lot in downtown Denver.

I’ve found graffiti evidence of “Sardine”, a denizen of downtown Denver, probably homeless.

A long time ago a friend of mine had the double-LP progressive rock album Jeff Wayne’s Musical Version of The War of the Worlds. I dredged up a bootleg on youtube and listened to it again.

After I upgraded my WRT3200ACM router to OpenWRT v23.05.3, my laptop took minutes to get an IPv4 address when connected to my WRT3200ACM router’s WiFi. It only takes seconds to get an IPv4 address when connected to my other WiFi.

I ended up downgrading OpenWRT on the WRT3200ACM, but first I did a lot of work trying to track down the problem.

After I upgraded to OpenWRT 23.05.3, my Linksys WRT3200ACM WiFi router seems to interact poorly with my Dell E7470 laptop. It takes many tens of seconds for that laptop to acquire an IPv4 address via DHCP.

I decided to downgrade OpenWRT Linux on the router from 23.05.3 to 19.07.10. I believe it was running 19.07 before I started on my sysadmin journey of switching to a new server.