Menu

1 / 2

One Abuse Complaint Later: Hardening a Home Proxy Without Blocking All UDP

Reading 0:00
15s threshold

This piece continues a previous write-up on diagnosing injected TCP resets [1] . That one was about proving where a connection failed. This one is about keeping a shared exit within its provider's rules and recoverable when its own tooling fails.

Part 1. The incident: forty minutes to first complaint

The setup is boring on purpose. One cheap virtual server, a gigabit port, a proxy core (Xray) with a REALITY inbound, and a house full of devices that route through it by domain rules on the router. Nothing exotic; the build takes an evening and about twenty dollars a year. It served video, cloud sync, and late night music discovery before this incident.

Then a family member installed a torrent client.

The client did what torrent clients do. It announced itself to public trackers, joined the public DHT network through its bootstrap nodes, and started moving gigabytes at line rate.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.