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.

Misunderstanding aside, thanks for the link!

It's 3.6GB upload though, which doesn't make much sense for a firmware update. The download usage was 96MB. But I agree that's it's probably something failing and retrying.

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 shouldn't be because you're not actually the owner of the IP address. If any user could get a cert, they could impersonate any other.

They're 'shortlived' 7 day certs, verified using a HTTP challenge. It doesn't matter who owns the IP, it's just a matter of who holds the IP.

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