Just because we're past Peak Woke doesn't mean that Woke is over.

touched on something that confuses almost everyone when they start running servers.

💡 UFW — what it actually is

UFW = Uncomplicated Firewall, a simple front-end for iptables (or nftables on newer systems).

It doesn’t get installed by default on every Linux box — it’s an optional package that sits on top of the firewall already built into the kernel.

• iptables / nftables = the real firewall (always part of Linux).
• UFW = a “friendly tool” to manage rules more easily.

So even when UFW isn’t installed, your router still has firewall capability — you’ve just been managing it directly through iptables (that’s what your router scripts are using).

echo "=== ... ===" — Just headers.

ip addr show | grep -E "^[0-9]|inet" — Lists interfaces and IPs (both v4 and v6).

ip route — Shows routing table; you want a default route via your WAN.

cat /etc/dhcp/dhcpd.conf | grep -E ... — Peeks at ISC DHCP config for key lines.

systemctl status isc-dhcp-server — Is the ISC DHCP daemon running/enabled?

iptables -t nat -L -n — Shows NAT rules; you usually need a MASQUERADE on WAN.

iptables -L FORWARD -n — Shows forwarding rules/policy.

cat /proc/sys/net/ipv4/ip_forward — Must be 1 for routing to work.

ping -c 1 8.8.8.8 — Tests raw internet reachability (no DNS).

cat /var/lib/dhcp/dhcpd.leases | grep -E "lease|hardware" — Shows leases being handed out.

• Why a reverse proxy (nginx)? Terminates TLS, serves static fast, routes multiple apps/domains, and protects/isolates backends; port conflicts happen only if both nginx and Apache bind 80/443—run only one on 80/443 and put the other on 8080 (or disable it).

• Yes, host on the i7/3090: use a single front door (nginx/Traefik) on 80/443, put each site/app in Docker (Apache/PHP-FPM, Node, etc.) on high ports, and keep GPU workloads in separate containers/VMs with resource limits; if you insist on Apache, run it behind nginx on 8080.

• Those CodeCanyon apps (usually PHP/Laravel + MySQL/Redis/queue) will run fine; they default to OpenAI/Claude keys, but if they allow a custom “OpenAI-compatible” base URL you can point them to a local server (Ollama/LM Studio/vLLM/OpenWebUI) on the 3090 for text/images/TTS.

Web-server defense setup and explanations

https://forumla.us/2025/10/31/8633/

DEI

Repurposing a Ni-Cd Charger for Li-Ion Batteries

(Maker-Fixer Edition)

Your old Ni-Cd charger can live again. It’s got the guts — transformer, rectifier, and housing — it just needs brains. We’ll keep the power section and add modern control so it can safely charge Li-ion tool packs or custom builds.

What You’ll Need

• Your Ni-Cd charger (rated 9.6 – 18 V output)
• One DC-DC buck converter (example: LM2596 module)
• One BMS board (Battery Management System) for your cell count
• 1S = 4.2 V cutoff
• 2S = 8.4 V cutoff
• 3S = 12.6 V cutoff
• 4S = 16.8 V cutoff
• Connectors (XT60 or barrel plug)
• A bit of 14–18 AWG silicone wire
• Optional: heatsink or small printed enclosure

How It Works

1. The Ni-Cd charger becomes your DC power supply. It no longer controls charging — it just provides raw DC voltage.
2. The buck converter trims that voltage to the exact target for your Li-ion pack (4.2 V per cell × number of cells).
3. The BMS board connects directly to the battery pack and handles all the smart stuff — balancing, over-current, and full-charge cutoff.

Example:

If you’re charging a 3-cell (3S) Li-ion pack, set the buck converter to 12.6 V output.

For a 4-cell (4S) pack, set it to 16.8 V.

Wiring Sequence

Ni-Cd charger (+) → input of buck converter

Ni-Cd charger (–) → input of buck converter

Buck converter output (+) → BMS “B+”

Buck converter output (–) → BMS “B–”

Battery pack wires → BMS board according to your cell count (B1, B2, B3, etc.)

Your tool or device connects to the BMS “P+” and “P–” pads.

Optional Add-Ons

• Use a small voltmeter display on the output so you can quickly confirm charging voltage.
• Keep the original LED on the Ni-Cd charger housing and rewire it to the BMS “charge complete” or power LED if you like indicators.
• You can even add a small 12 V fan to the case if you plan on charging large packs.

Typical Part Sources

• LM2596 buck converter module – a couple bucks online
• 3S/4S BMS board – about five bucks
• XT60 connectors – a few dollars for a pack
• Heat shrink and wire – grab a cheap silicone kit

Summary

Your Ni-Cd charger’s job now is simple: be the power brick.

The buck converter and BMS do the thinking.

No more junk drawer electronics — just a solid, functional Li-ion charger that fits in your maker space.

router setup

• Dell router with UFW firewall, DHCP, NAT, Nginx reverse proxy

• Nginx on Dell proxying localad.us and photola.us to Apache