Oh I'm aware, I just wanted to add to the trivial list of issues. But I think there might still be issues with some Snapdragon CPUs.

It could also be that some students have ARM laptops, and they've got an x86 version of Debian.

I'd intercept port 53 traffic for UDP and TCP, that way it doesn't matter what the IP is. I don't know about consumer stuff, but a dst nat rule should work.

You can customise your console login with /etc/issue too!

When it happens, try pressing Alt + SysRq(/PrtSc) + o. If that turns off your computer, then the kernel is still running and something is preventing shutdown; if it doesn't, either SysRq is disabled, or ACPI is broken.

My Mikrotik routers and switches also reboot in seconds (even for upgrades), which I've never seen consumer gear do!

Even my Ubiquiti switches seem to take a minute or so to start forwarding traffic after a reboot; whilst my Mikrotik switches reboot faster than any of my unmanaged switches start up.

Maybe look into using the pstore, it can store kernel panics in ACPI or UEFI variables to be read by the next boot. Usually this is accessible at /sys/fs/pstore, but if systemd-pstore is installed then it should be in the journal, but it can also be here: /var/lib/systemd/pstore.

Cloudflare usually blocks 'unknown' bots, which are basically bots that aren't search crawlers. Also I've got Cloudflare setup to challenge requests for .zip, .tar.gz, or .bundle files, so that it doesn't affect anyone unless they download from their browser.

There's also probably a way to configure something similar in Anubis, if you don't like a middleman snooping your requests.

I just used a bot to read it: https://web.archive.org/web/20250901133211/https://cheapskatesguide.org/articles/debian-netinstall-waf.html

It doesn't look like the normal boot log for Linux (or FreeBSD), so I'm not sure what it is either.

Not really, but once you've patched the driver, run dkms status and dkms build <id from status> (e.g. dkms build nvidia/580.76.05) to rebuild the driver for your current kernel.

When you get it working, it'll be a good idea to write a little guide here for other people to follow.

The official driver already uses DKMS (at least in the newer drivers), so you should be able to patch the code in /usr/src/nvidia-470* and have it apply automatically every kernel update.