Setting up a proxy gateway follows a fixed sequence: connect power and network, insert SIMs, log in, confirm registration, create pools, and test the first connection through a mobile egress path. This guide walks through those steps on a typical proxy gateway such as Telarvo's SK Multi-WAN series.
Each step is deliberately small because the order matters: a gateway with no signal produces no egress path, a pool with the wrong SIM group produces the wrong exit address, and a test that skips verification proves nothing about production readiness. Work the six steps in sequence and keep notes as you go.
Before You Start
Gather the essentials first:
You need the gateway unit with antennas and power supply, SIM cards activated on data plans with carrier terms documented, a computer on the same network, and the default login details from the manual.
Confirm SIM activation before inserting; most first-time problems trace back to inactive cards.
The environment matters as much as the parts list. The gateway needs a location with a clear antenna path and stable power, so avoid metal cabinets, windowless closets, and shared power strips that trip under load. Check the signal for each SIM after placement, because a card that registers weakly at installation will fail intermittently later.
Documentation should be ready before the first login: the model and firmware version, the SIM list with carrier and plan terms, the management IP or DHCP reservation, and the support channel for the unit. That one page turns later troubleshooting from a puzzle into a lookup, and it is much easier to write during setup than to reconstruct after a problem.
Network planning is part of preparation. Decide whether the gateway gets a static IP or a DHCP reservation, which subnet the LAN clients use, and whether management is reachable only from a dedicated management VLAN. Writing these decisions down avoids a reconfiguration session after the device is already in production.
Source SIMs with the plan terms written down: data allowance, speed, rotation tolerance, and the carrier's position on SIM-based gateway use, because a plan intended for a phone may not be appropriate for continuous gateway traffic.
Step 1-6
Step 1 connects and powers on: attach the antennas, insert the SIMs, connect the WAN and LAN cables, and power on. Wait for the device to show ready status before continuing, because the management interface may not be reachable until the unit finishes booting.
Step 2 finds and logs in: look up the gateway's IP in the router's DHCP list or on the device display, open it in a browser, and log in with the default credentials. Change the default password in the same session and restrict management access to trusted IPs; a proxy appliance left on defaults is an open door to your egress paths.
Step 3 configures the network: set each WAN connection as its own interface, confirm the LAN and management IPs, and verify internet connectivity on every uplink. Multi-WAN models treat each link separately, so a link left unconfigured will not appear in the pool options.
Step 4 verifies SIM registration: check the SIM status page and confirm each card shows registered and a usable signal. A SIM with no signal will not produce a usable egress path, and a card that registers weakly will fail intermittently under load.
Step 5 creates pools and assigns IPs: define pools from the SIM groups, choose the rotation mode for each pool, and assign pools to users or applications. Keep the mapping explicit—one pool per team or workload—so a routing change later touches one pool instead of the whole fleet.
Step 6 tests the first connection: configure a client with the proxy host, port, and credentials, connect, and verify the exit address belongs to the expected carrier and region. Repeat the test on a second pool to confirm that pool assignment, not luck, produced the result.
After the first connection passes, finish the operational tasks before real traffic: set log retention, confirm the alert path for SIM failures, back up the configuration, and record the pool registry in the operations notes. These four items take minutes at setup and prevent the most common failure mode of proxy fleets—a SIM silently dropping out of rotation.
Verification should test more than one path. A single successful connection confirms the gateway works, but it does not confirm pool separation, so run the same test with a second user on a second pool and confirm the exit addresses differ when the pools use different SIM groups.
Credentials and access belong in the same pass. Create per-user accounts with minimum permissions, set a password policy, and record who can change rotation modes or reassign SIMs; when a team grows from three users to thirty, per-user access control is what keeps the gateway manageable.
Keep the test results—exit address, latency, and the pool used—on the same page as the SIM list. When a user later reports the wrong region, the recorded baseline tells you whether the pool changed or the carrier reassigned the address.
Troubleshooting First-Time Problems
| Symptom | Likely cause | Fix |
|---|---|---|
| No signal on a SIM | Antenna or activation | Check antenna connection and SIM activation |
| Cannot log in | Wrong IP or credentials | Check DHCP list and default credentials |
| Connection refused | Port or credentials | Verify proxy port and assigned credentials |
| Wrong exit address | Pool assignment | Check which SIM/pool the client used |
The table works best as a decision order, not a menu. If the first test fails, check SIM registration, then the WAN link, then the pool assignment, and change one variable at a time; changing everything at once leaves you without a diagnosis. Note what you changed, because the note becomes the start of the operations log.
Most first-time failures are environmental rather than defective: an antenna lying flat on a metal shelf, a SIM not yet activated, or a client pointed at the wrong pool. Each has a visible symptom, which is why the status pages and the pool list are the first places to look.
If a symptom persists after the table, escalate with evidence rather than a description: capture the SIM status page, the WAN link state, the pool list, and the client-side error. The supplier can diagnose from that set of facts much faster than from a screenshot of the error alone.
Telarvo Expert Views
Most setup tickets are SIM-side: a card not activated, an antenna lying flat on a metal shelf, or a pool pointed at the wrong SIM group. Work through registration and signal before touching network settings, and change the default password on day one.
— Network Infrastructure Engineer, Telarvo Store
Validation note: IP persistence, uniqueness, and geolocation precision depend on carrier addressing and plan terms; verify behavior in your operating markets.
Conclusion
A proxy gateway goes from box to first connection in six steps when SIM registration and pool configuration are handled in order—and governance starts the same day.
The six-step sequence is also the baseline for governance: the password change, the pool registry, and the log-retention decision belong in the same session as the first connection. A gateway that is set up once, documented, and monitored is infrastructure; one that is set up and forgotten is a risk.
Key Takeaways for B2B Buyers
Confirm SIM activation and signal before configuring anything else; change default credentials at login and restrict management access; assign pools per user or application with the correct rotation mode; and verify the exit address matches the expected carrier and region.
Questions to Ask Before Committing
Ask which SIM plans and carrier terms apply to the egress paths you will use, whether rotation mode can be configured per pool and per user, what access control, logging, and log-retention the management interface provides, and how warranty, support, and firmware updates are documented.
Ask Telarvo Store for a proxy gateway configuration review and confirm the SK Multi-WAN model that matches your egress-path count before quoting.
FAQs
Do I need one SIM per pool?
Each pool needs at least one active SIM; more SIMs give more concurrent egress paths. Treat each active connection as one independently routable path for planning.
How do clients connect?
Through the proxy host and port with assigned credentials; some platforms support SOCKS5. Confirm protocol support per model.
Can I change rotation mode later?
Yes—mode is a pool setting and does not require new hardware.
What should I do if the gateway stops passing traffic?
Check SIM registration, WAN link status, and pool assignment in that order.
What if I need more egress paths later?
Add SIMs to the pool and confirm the model's SIM-slot and channel limits; rotation distributes traffic across the new paths without reconfiguring clients.