Originally published on proxymint.
What a mobile proxy farm is made of, why modems drop off USB under load, how rotation behaves on real SIMs, what carrier terms say, and what breaks first.
TL;DR
- The proxy software is the easy part of a farm. Policy routing with one table per modem gets a curl --interface working in an afternoon; power, USB, heat and SIM contracts are where the weeks go.
- A modem that keeps vanishing is usually the hub. USB 2.0 ports are held to 500 mA and transmit bursts brown modems out, which shows in dmesg as a USB disconnect and a fresh device number.
- Reconnecting does not promise a new IP. The carrier's NAT picks the public address and tends to keep a subscriber on one, so log 50 reconnects per SIM before you trust your rotation.
- The target sees the carrier and your host, not the modem. The ASN is the carrier's, the TCP stack is whatever runs the proxy, and the 4G or 5G radio is invisible.
Key takeaways
- Put modems on powered hubs and spread them across controllers. Check lsusb -t before buying more modems, because twelve SIMs behind one USB 2.0 controller share 480 Mbit/s.
- Read each SIM's plan before you scale it. Consumer terms often bar server-style use, and a suspended line costs more time than the SIM did.
- Never touch the IMEI. Changing it is a criminal offence in the UK, whatever a farm guide says.
- Monitor in layers and alert on the first one that fails. Bus, interface, bearer, route, target: an alert that only says proxy down is useless at 2 a.m.
Read the full guide on proxymint, with the commands, tables and sources.