networking

A half-remembered Mbps-to-bytes formula left the 3proxy bandlim cap at 5 Mbps instead of 40. The manual said bits all along.

TL;DR: A 3proxy bandwidth cap configured at 40 Mbps actually limited traffic to 5 Mbps because bandlim expects bits per second, not bytes, so the fix was changing 5000000 to 40000000. The same commit trimmed a GoAccess dashboard to three panels, surfacing the URL table immediately. Lesson: verify unit conversions against the manpage.

A time-based bandwidth cap on a home LAN using Squid delay pools: bytes vs bits, the acl time trap, container TZ, and a second unlimited pool.

Months spent blaming an anti-bot; the culprit was an Indonesian ISP's DNS redirecting duckduckgo.com to Trustpositif.

TL;DR: Headless browser tests inside Docker kept failing on DuckDuckGo, and I wasted months blaming anti-bot fingerprinting. The real culprit was Indonesian ISP DNS poisoning; Kominfo's 2015 mandate redirects port 53 queries, so duckduckgo.com resolved to a wrong IP. The fix was one flag: docker run --dns 1.1.1.1 restored access instantly.