Originally published on proxymint.
HiLink turns a USB modem into a tiny router with its own NAT; stick mode hands the host a bare modem. What that changes for a proxy host and for rotation.
TL;DR
-
HiLink puts a router inside the stick. The modem dials the carrier itself and hands your host a 192.168.8.x address over DHCP, so you get a network card, a web UI at 192.168.8.1 and nothing in
mmcli -L. Fine for one stick. - Stick mode gives the host a bare modem. Your machine dials with ModemManager, QMI, MBIM or PPP, sees signal and registration, and reconnects on its own schedule. It is the mode a proxy host with several modems wants.
- The 192.168.8.1 collision is the real problem. Every HiLink stick ships with the same subnet, so four sticks on one box fight over one default route until you renumber them, isolate them in namespaces or route by source address.
- The target does not care which mode you picked. It sees the carrier's public address either way; the mode changes how you control and rotate the modem, not the trust the exit carries.
Key takeaways
-
Run
lsusb -t,ip -br linkandmmcli -Lbefore you change anything. They tell you which driver claimed the stick and whether you have a modem or a network card, which settles half the forum threads on the spot. - Leave a single HiLink stick alone. Converting firmware to save one NAT layer is rarely worth the risk of a dead stick.
- Give every modem its own subnet or namespace on a multi-stick host. Then bind each proxy port to its source address so the exit you log is the exit you used.
- Buy a modem that is already a modem when you are building. An M.2 module in a USB enclosure that speaks QMI or MBIM saves the flashing step entirely.
Read the full guide on proxymint, with the commands, tables and sources.
Top comments (0)