Build Your Own 5G Mobile Proxy: Step-by-Step Guide from Start to Finish

Introduction

In this step-by-step guide, you'll assemble and launch a working 5G mobile proxy from scratch, resulting in a stable HTTP(S) and SOCKS5 proxy that connects to the internet via a 5G modem. We'll discuss selecting modems and modules, the impact of 5G frequency bands on speed and IP reputation, compare practical measurements of 4G versus 5G, build a 5G node considering antennas, cooling, and power, set up the software, and show you how to safely test and maintain the system.

This guide is suitable for beginners as well as those who have tried proxies on 4G and want to switch to 5G. We use clear language without unnecessary jargon, explaining each action step by step.

No prior knowledge is required. You'll need basic computer skills and a willingness to follow instructions without rushing. If you're in doubt about something, don't worry: there are checkpoints after each stage.

Expected time required: typically 1–2 days for purchasing and assembling hardware, 1–3 hours for software setup, and about 30–60 minutes for testing.

If you're not ready to assemble everything yourself, consider looking into ready-made solutions and services, such as mobileproxy.space. However, this guide is designed for hands-on assembly, so you can fully control quality and costs.

Preparation

Before starting, make sure you have the right equipment and access to a server where you can establish the reverse tunnel. This is necessary because mobile networks typically use NAT, and direct incoming access to your proxy is often unavailable. We'll work around this limitation without breaking any rules using standard remote connection tools.

Required Tools and Access

• A computer or single-board mini-PC with USB 3.0 or M.2 (for example, Raspberry Pi 4/5, Orange Pi 5, x86 mini-PC). A 64-bit OS will be required.
• A 5G modem as an M.2 module or 5G CPE device. We'll discuss the selection below.
• A SIM card from a carrier with a plan for modems/routers that allows tethering and provides 5G access.
• An account and access to a remote server (VPS or dedicated server) with a public IPv4 address, SSH access, and the ability to open several ports.
• Antennas suitable for your carrier's frequency bands (either built-in or external), a quality USB cable, and a power supply with the required wattage.

System Requirements

• OS: Linux (Debian 12 or Ubuntu 22.04/24.04), or OpenWrt on a router that supports 5G modems.
• Free ports: USB 3.0 for M.2 adapter and antennas, Ethernet for connecting to the network and management server.
• Free disk space: at least 8 GB for the system and logs.
• Packages: ssh, autossh, 3proxy or similar proxy server, ModemManager, NetworkManager (or their equivalents).

What to Download, Install, and Configure

• Update the system: apt update, apt upgrade. This will reduce the risk of incompatible packages.
• Install the package set: ModemManager, mmcli, NetworkManager, 3proxy, autossh, iperf3, tcpdump, htop. If using OpenWrt, utilize opkg and corresponding equivalents (modemmanager, umbim/uqmi, 3proxy, autossh).
• Prepare SSH keys for accessing your server. This ensures a stable reverse tunnel without entering a password.

Backups

• Make backups of configurations after setting up each block: network profiles, 3proxy config, autossh systemd units. Store backups in a separate folder and on a remote server.
• If using OpenWrt, save the backup through System → Backup/Flash Firmware → Generate Archive.

Tip: Enter all commands sequentially and record the results. If something goes wrong, you'll have a history of actions to return to.

Basic Concepts

To better understand each step, let’s break down key terms in simple words.

• Mobile Proxy — a program on your device that accepts connections and sends traffic to the internet via a mobile network. Clients connect to the proxy and receive an outgoing IP from the mobile operator.
• 5G Modem/Module — hardware that establishes a 5G connection. This can be an M.2 card in a USB adapter or a ready-made 5G router (CPE).
• 5G Band — radio frequencies on which 5G operates. The band affects speed, ping, and coverage (for example, n78, n28). mmWave offers very high speeds over very short distances, but it’s not available everywhere.
• NSA/SA — modes of 5G. NSA uses both 4G and 5G at the same time, while SA operates solely on a 5G core. This impacts ping and stability.
• Reverse Tunnel — a channel through which the VPS connects back to your proxy despite NAT from the operator. We use standard SSH tools.

Why This Matters: Understanding the terms helps you avoid errors during modem setup, frequencies, and tunnel configuration, as well as interpret measurement results correctly.

Step 1: Do You Need 5G for Proxy — When Yes and When No

Goal of the Stage

Determine if 5G will truly benefit your needs or if 4G would suffice. This will save time and budget.

Step-by-Step Instructions

1. Define your goal: Is speed, stability, latency, capacity (number of simultaneous sessions), or IP reliability more important to you?
2. Check 5G coverage with your carrier at your location. If coverage is weak, 5G won’t provide an advantage.
3. Assess your budget. A 5G module and antennas cost more than 4G. If your budget is tight, start with 4G, leaving an upgrade option to 5G.
4. Evaluate requirements for IP reputation. If predictability of pools and geo-accuracy are crucial, check what bands and pools your carrier provides in your area.
5. Compare expected metrics: 5G often delivers 150–600 Mbps and a ping of 10–25 ms in urban settings. 4G typically yields 30–80 Mbps and a ping of 25–45 ms. Align these figures with your needs.

Important Notes: 5G isn't always faster; if the signal is weak or the network is congested, sometimes a quality 4G connection with a good antenna remains more stable.

⚠️ Warning: Don’t rely solely on marketing numbers. Actual speeds depend on frequencies, distance from the base station, congestion, and equipment.

Tip: If your case involves many parallel connections, 5G is usually more resilient during peak hours due to greater cell capacity.

Expected Outcome

You understand when 5G will be beneficial and when 4G is sufficient. An initial decision has been made to transition to 5G or pilot 4G with the option to upgrade.

Potential Issues and Solutions

• Problem: Unsure if 5G coverage is available. Reason: No up-to-date coverage map. Solution: Consult the carrier support and check the network indicator at the installation site.
• Problem: 5G is present, but the speed resembles 4G. Reason: weak signal or NSA mode with restrictions. Solution: Add external antennas, check NSA/SA in the modem, optimize the node placement.

✅ Verification: You have a reasoned decision: you fully understand why you’re transitioning to 5G, and you document success criteria (minimum speed, ping, stability).

Step 2: 5G Modems and Modules — What’s Available and How Much Do They Cost

Goal of the Stage

Select compatible and accessible equipment for your needs, considering budget and installation conditions.

Quick Overview of Categories

• M.2 5G modules (inserted into USB/M.2 adapters, flexible and inexpensive): suitable for DIY projects, require cooling and proper power supply.
• USB/CPE 5G routers (ready-made devices): easier to install, more expensive, sometimes limited in fine-tuning.
• 5G-capable smartphones (tethering mode via USB): appropriate for testing and pilot runs, but inadequate for 24/7 operations.

List of Popular Modules and Approximate Prices (2026)

• Quectel RM520N-GL: 100–130 USD. Sub-6, broad compatibility, good price-stability balance.
• Quectel RM530F-GL: 140–180 USD. Updated platform, steady performance in n78, higher peak speeds.
• Fibocom FM350-GL: 140–190 USD. Supports Sub-6, good compatibility with Linux, requires careful cooling.
• Telit FN980/FN980m: 120–200 USD (often used). Solid foundation, decent drivers, antennas can be tricky to manage.
• SIMCom SIM8262E-M2: 90–120 USD. Budget option for pilots; pay close attention to the revision and firmware.

Available 5G CPE/Routers and Prices

• ZTE MC801A/MC888: 120–200 USD (price varies by revision). User-friendly web interface, external antennas via SMA.
• Huawei 5G CPE Pro 2 (H122-373): 150–220 USD (often used). Reliable but limited customization options.
• MikroTik Chateau 5G ax: 450–650 USD. High-end class, detailed settings, above-average price.

What Other Hardware Is Needed

• M.2 → USB 3.0 adapter with 3.3V power supply, thermal pad, and heatsink.
• Antennae: 2x2 or 4x4 MIMO depending on the module. For n78, directional panel antennas are preferable.
• Power supply 5V/3A for SBC and 12V/2–3A for CPE (check device specifications).

Important Notes: Cross-check regional versions of the modules with your carrier's frequencies. Verify antenna connectors (IPEX MHF4, SMA, TS-9) and buy appropriate adapters.

Tip: Aim to purchase modules with the latest firmware revisions. Newer firmware often resolves NSA/SA and compatibility issues.

✅ Verification: You now have a finalized shopping list: module, adapter, antennas, power supply, and OS media. The total budget is acceptable.

Potential Issues and Solutions

• Problem: The module overheats. Reason: no heatsink or inadequate cooling. Solution: use a thermal pad and an aluminum heatsink with a fan, ensuring airflow around the unit.
• Problem: Antennas don’t fit the connector. Reason: different connector type. Solution: purchase an MHF4→SMA or TS-9→SMA adapter, checking polarity.

Step 3: 5G Frequency Bands (n78, n28, mmWave) and Their Impact on IP Reputation

Goal of the Stage

Understand which bands work with your carrier and how they influence speed, stability, and IP address reputation.

Key Bands

• n78 (3.3–3.8 GHz, mid-band): primary urban working range. Typically delivers 150–600 Mbps, ping 10–25 ms, middle-distance coverage. Good for everyday proxy use.
• n28 (700 MHz, low-band): long-distance coverage, better penetration into buildings. Speed is moderate (50–200 Mbps), but stability is good.
• mmWave (24–39 GHz): very high speeds with line-of-sight, but limited range. Rarely applicable for proxies due to installation complexities.

How Bands Influence IP Reputation

• Frequency itself does not alter IP reputation but correlates with the address pool allocated by the carrier for specific cells and technologies. Urban n78 often offers greater capacity and variety of pools.
• In n28, there may be fewer addresses in the pool and more IP repetition. This isn't necessarily bad, but it affects predictability.
• In NSA modes, some traffic may pass through 4G anchors, which influences routing and the geolocation of the IP.

Tip: Conduct tests at various points in your location and at different times of day. Compare the stability of the IP pool and latency.

⚠️ Warning: Never use tools to spoof or falsify network parameters that may violate operator rules or laws. This guide focuses on proper and safe configuration.

Expected Outcome

You’ve chosen your target band(s) and understand where to install the antenna and how your expectations regarding IP reputation are linked to coverage area.

Problems and Solutions

• Problem: The device always defaults to 4G. Reason: weak 5G signal or priority settings. Solution: optimize the antenna, shorten the cable, move the device closer to a window, check network priority settings in the modem.
• Problem: Frequency often shifts, leading to IP geolocation changes. Reason: dynamics of the carrier's pools. Solution: switch to a more stable band or change locations within the building.

✅ Verification: You have recorded the chosen frequencies and a plan for antenna installation for optimal RSRP/RSRQ/SINR.

Step 4: Real Measurements of 4G vs. 5G — Speed, Ping, Stability

Goal of the Stage

Compare 4G and 5G in practice at your exact location. This is key to making an objective decision.

Step-by-Step Measurement Instructions

1. Connect the modem in 4G mode (if selectable) and check signal metrics: RSRP, RSRQ, SINR. Document the results.
2. Run iperf3 to your server: on the server, execute iperf3 -s, on the node, run iperf3 -c YOUR_SERVER_IP -t 30. Document average upload and download speeds (reverse-testing if needed).
3. Check latency: ping -c 20 YOUR_SERVER_IP. Record average ping and jitter (variation).
4. Repeat the tests in 5G NSA/SA mode if available. Again, document speed and ping.
5. Repeat each test set in the morning, afternoon, and evening. This will show you how network load affects performance.

Summary Results (Example)

• 4G: down 40–70 Mbps, up 10–25 Mbps, ping 28–45 ms, average stability, occasional drops to 20 Mbps during peak hours.
• 5G NSA (n78): down 180–420 Mbps, up 40–120 Mbps, ping 12–22 ms, high stability, rare drops to 120–150 Mbps.
• 5G SA (n78): down 220–600 Mbps, up 60–180 Mbps, ping 9–18 ms, high stability, even fewer drops.

Tip: Keep a table with the date, time, frequency, and results. This will help you identify patterns and select the best load windows.

Expected Outcome

You now possess objective figures for 4G and 5G at your location. It’s clear what advantages 5G offers in your specific case.

Potential Issues and Solutions

• Problem: Results vary significantly. Reason: the network is congested or there's interference. Solution: increase the number of repetitions, test at different hours, and optimize the antenna.
• Problem: iperf3 displays low speeds. Reason: limitations on your server. Solution: check if the CPU/network is sufficient on the server side.

✅ Verification: You now have a summary with speed, ping, and stability values for both 4G and 5G across three different time windows.

Step 5: Assembling the 5G Node — Modem, Antennas, Heat, Power

Goal of the Stage

Physically assemble a node that maintains a 5G session reliably around the clock.

Step-by-Step Instructions

1. Install the 5G module into the M.2 adapter. Align the connector keys and secure it with screws without overtightening.
2. Apply a thermal pad to the modem chip and install a heatsink. If a fan is available, attach it so that airflow moves along the radiator's fins.
3. Connect the antennas to the module's connectors. For MHF4, be gentle: press the connector straight down until it clicks.
4. Connect the adapter to the USB 3.0 port of your mini-PC with a high-quality short cable. Avoid using extenders.
5. Insert the SIM card into the adapter's slot. Ensure that the PIN code is disabled or known.
6. Prepare the power supply. For SBC, use a 5V/3A power source, for CPE, follow the device specifications. Avoid cheap power supplies.
7. Place the node near a window or closer to an external wall. If using an external antenna, run the coaxial cable for minimal length, avoiding sharp bends.

Important Notes: Heat is the primary enemy of the 5G module. Temperatures above 70–80°C will lead to throttling and disconnections. Use a heatsink, airflow, and ensure there’s space around the unit.

Tip: Consider placing a thermal sensor or monitor the modem's temperature through mmcli if supported, so you can observe conditions under load.

Expected Outcome

The node is assembled, the modem is connected, antennas are installed, and power is stable. The node is ready for software configuration.

Issues and Solutions

• Problem: The modem is not recognized. Reason: a poor-quality USB cable or lack of power. Solution: replace the cable, connect directly to the board, or try another port.
• Problem: Weak signal. Reason: poor placement. Solution: move it closer to a window, raise the antenna higher, or select another window.

✅ Verification: The command lsusb shows your device, and dmesg shows that the modem was recognized without power errors.

Step 6: Installing the OS and Connecting the Modem (NSA/SA)

Goal of the Stage

Ensure the modem can reliably connect to the 5G network, check NSA/SA, and confirm the operational profile.

Step-by-Step Instructions (Linux Debian/Ubuntu)

1. Update the system: apt update && apt -y upgrade.
2. Install the packages: apt -y install modemmanager network-manager usb-modeswitch 3proxy autossh iperf3.
3. Restart the modem: unplug and plug the USB back in, wait 15–30 seconds.
4. Check detection: mmcli -L. The modem /org/freedesktop/ModemManager1/Modem/0 should display.
5. Disable the PIN on the SIM or enter it: mmcli -m 0 --pin=YOUR_PIN (if required), then mmcli -m 0 --disable-pin.
6. Create a connection: nmcli con add type gsm ifname cdc-wdm0 con-name 5g apn=internet user='' password=''. If the interface is different, use its name (e.g., cdc-wdm1).
7. Bring the connection up: nmcli con up 5g. Wait 10–20 seconds.
8. Check the status: mmcli -m 0 — look for state: connected, access tech: 5g-nsa or 5g-sa.
9. Pin the network selection if necessary: mmcli -m 0 --set-allowed-modes='4g|5g', then mmcli -m 0 --set-preferred-mode='5g'.
10. Check IP: ip a on the interface wwan0/cdc-wdm0. Ensure there’s an IPv4 and/or IPv6 address.

Tip: If your carrier only provides IPv6, ensure your clients and server support IPv6. For mixed scenarios, it's convenient to have a dual-stack configuration.

Important Notes: In NSA modes, ping and stability depend on 4G anchors. If you often experience “jumping” modes, check antenna placement and node location.

Expected Outcome

The modem connects reliably to the 5G network, showing NSA or SA mode, and there is an IP address and default gateway.

Problems and Solutions

• Problem: Connection does not come up. Reason: incorrect APN. Solution: clarify the APN with the carrier and set it in the profile.
• Problem: Only 4G, no 5G. Reason: weak signal or unavailable band. Solution: reposition the antenna, check allowed bands with the carrier, and verify the region of the modem.

✅ Verification: mmcli indicates connected and shows either 5g-nsa or 5g-sa while the ping to your server is stable within the target range.

Step 7: Setting Up the Proxy Server (HTTP and SOCKS5) and Security

Goal of the Stage

Raise a local proxy on the node and restrict access to it exclusively through the reverse tunnel.

Step-by-Step Instructions (3proxy)

1. Install: apt -y install 3proxy.
2. Create a user for access: add a line in the config with a username and password.
3. Open the 3proxy config, usually located at /etc/3proxy/3proxy.cfg. Example of minimal configuration: auth strong; users user:CL:StrongPasswordHere; allow user; proxy -p3128 -a -n -e; socks -p1080 -a -n -e; flush. Here, -p specifies HTTP and SOCKS ports, -e makes it exit through the default route (mobile network).
4. Limit binding to localhost if you plan to access it solely via the tunnel: proxy -p3128 -i127.0.0.1; socks -p1080 -i127.0.0.1.
5. Restart the service: systemctl restart 3proxy && systemctl enable 3proxy.
6. Check that the ports are listening: ss -lntp | grep -E '3128|1080'. It should show LISTEN on 127.0.0.1.

Tip: Do not leave the proxy open on the internet. Initially, restrict access to 127.0.0.1, and publish it only through the reverse tunnel with authorization.

Expected Outcome

The local HTTP and SOCKS5 proxies are operational, and access is confined exclusively to the localhost interface.

Problems and Solutions

• Problem: Client fails to authorize. Reason: incorrect username or password. Solution: verify users in the config and restart the service.
• Problem: Traffic isn’t going through 5G. Reason: the default route isn’t set on the mobile interface. Solution: ensure that the mobile interface is the default route, or configure policy routing.

✅ Verification: Local check with curl --proxy http://user:pass@127.0.0.1:3128 http://your_server processes correctly, and traffic from your mobile IP is visible on the server.

Step 8: Publishing the Proxy through a Reverse Tunnel on VPS

Goal of the Stage

Make the proxy accessible from the outside despite the carrier's NAT while remaining compliant and secure.

Step-by-Step Instructions

1. Generate an SSH key on the node: ssh-keygen -t ed25519 -N '' -f ~/.ssh/id_ed25519.
2. Copy the key to the VPS: ssh-copy-id user@IP_VPS. Ensure passwordless login.
3. Check if the port on the VPS (for example, 60080 for HTTP and 61080 for SOCKS) is accessible: ensure that the firewall allows incoming connections on these ports.
4. Create a rinetcat check or simply run nc -l -p 60080 on the VPS to confirm that the port is open (disable it afterward).
5. Manually raise the reverse tunnel for testing: ssh -N -R 0.0.0.0:60080:127.0.0.1:3128 -R 0.0.0.0:61080:127.0.0.1:1080 user@IP_VPS. Keep the terminal open and test the connection to VPS_IP:60080/61080 from an external client.
6. If the test is successful, create a systemd unit for autossh, making the tunnel auto-start. Example systemd unit at /etc/systemd/system/autossh-proxy.service: [Unit] Description=Autossh Reverse Proxy After=network-online.target Wants=network-online.target; [Service] User=root Restart=always Environment="AUTOSSH_GATETIME=0" ExecStart=/usr/bin/autossh -N -M 0 -o ServerAliveInterval=30 -o ServerAliveCountMax=3 -R 0.0.0.0:60080:127.0.0.1:3128 -R 0.0.0.0:61080:127.0.0.1:1080 user@IP_VPS; [Install] WantedBy=multi-user.target.
7. Activate the service: systemctl daemon-reload && systemctl enable --now autossh-proxy.
8. Check that the ports on the VPS are listening: ss -lntp | grep -E '60080|61080' (run this on the VPS). It should show LISTEN on 0.0.0.0.

Tip: To enhance security, limit VPS access via the firewall by IP addresses of your clients or use mandatory authorization in 3proxy. Never leave public ports unmonitored.

Expected Outcome

Your proxy is available at IP_VPS:60080 (HTTP) and IP_VPS:61080 (SOCKS5). Access is authorized, and the carrier's NAT does not hinder connectivity.

Problems and Solutions

• Problem: The port only listens on 127.0.0.1 on the VPS. Reason: 0.0.0.0 wasn’t specified in -R. Solution: indicate -R 0.0.0.0:PORT:127.0.0.1:PORT.
• Problem: The tunnel drops. Reason: mobile network disconnects. Solution: use autossh with ServerAlive options and service restarts in case of errors.

✅ Verification: An external client connects to the VPS:ports, authenticates on 3proxy, and traffic flows through the mobile network of the node.

Step 9: Pitfalls — NSA/SA, Carrier Throttling, Stability

Goal of the Stage

Avoid common traps associated with 5G modes, traffic limitations, and disconnections.

NSA vs. SA

• In NSA, you depend on 4G anchors. With poor 4G, ping and stability can drop, even if 5G is available.
• In SA, ping is usually lower and more stable, but SA availability depends on the operator and region.

Carrier Throttling

• Operators may restrict speeds based on traffic type or after a certain volume. This is standard tariff policy.
• Select plans for modems with clear terms. Study the tariff description to avoid unforeseen restrictions.

Disconnections and Overheating

• Overheating causes speed drops and disconnections. Monitor temperatures and enhance cooling.
• Power supply must be stable; otherwise, the modem will drop over USB and lose connection.

Tip: Set up monitoring: periodic checks of mmcli state and restarting the connection if it hangs. Do this carefully and not too frequently to avoid network sanctions.

✅ Verification: You have an action plan for each scenario: switch installation location, replace antennas, improve power and cooling, and correctly choose a tariff.

Results Verification

Checklist

• The node powers on and does not overheat under load.
• The modem connects to 5G (NSA/SA) reliably, without frequent reconnections.
• The local 3proxy is functional, accessible from 127.0.0.1, and requires authorization.
• The reverse tunnel is active, ports on the VPS are listening, and accessible externally based on firewall rules.
• Traffic from the external client flows through your mobile IP.

How to Test

1. On the external client, set up the proxy IP_VPS:60080 with a username and password, open several websites, and compare load speeds.
2. On the VPS, run iperf3 -s, and on the client run iperf3 -c IP_VPS via the SOCKS5 proxy or tunneling option. Compare with local tests.
3. Check latency: ping and trace from the client to popular nodes through the proxy. Values should correspond with your measurements from the node.

Tip: Keep a log: date, time, speed, ping, stability, and modem temperature. This will facilitate problem-solving.

✅ Verification: Stable access to resources through the proxy, expected speed and ping, absence of unexpected disconnections during 2–4 hours of continuous testing.

Common Errors and Solutions

• Problem: Proxy is accessible on the internet without authorization. Reason: 3proxy config listens on 0.0.0.0 without restrictions. Solution: Bind to 127.0.0.1 and publish only via reverse tunnel, enable auth strong and users.
• Problem: Poor speed on 5G. Reason: Weak signal, long coaxial cables, overheating. Solution: Move the node, use directional antennas, shorten the cable, improve cooling.
• Problem: Tunnel drops every 5–10 minutes. Reason: Network drops or NAT timeout. Solution: use autossh with ServerAliveInterval=30 and ServerAliveCountMax=3, restart the service on errors.
• Problem: No 5G, only 4G. Reason: unavailable 5G band at the installation point. Solution: change node location, use an external antenna, check allowed frequencies with the operator.
• Problem: Proxy is not reaching the network through the mobile interface. Reason: The default route isn't set to wwan0. Solution: set priority for the mobile interface or configure policy routing.
• Problem: High ping and jitter. Reason: overloaded cell or NSA with poor anchor. Solution: change testing time, try another location, improve reception.
• Problem: Random drops in 3proxy. Reason: memory shortage or package conflict. Solution: update 3proxy, check logs, limit max clients, increase resources.

Additional Capabilities

Advanced Settings

• Policy-based routing: send proxy traffic strictly through the mobile interface, while system updates go through another.
• IPv6 support: if the operator provides IPv6, enable it in 3proxy and on the server so clients can utilize dual-stack access.
• Limits and quotas: restrict speed for clients through 3proxy to prevent any single user from overloading the channel.

Optimization

• Node location selection: minimize obstacles and reflections, orient the antenna towards the nearest base station.
• Cooling: add a thermal sensor and a script for emergency load reduction during overheating.
• Logs and alerts: send notifications when the tunnel drops or when switching between NSA/SA modes.

Tip: If managing dozens of nodes independently isn't your preference, consider specialized dashboards and ready-made solutions like mobileproxy.space, where some tasks are automated.

FAQ

• Question: How much performance gain does 5G provide compared to 4G? Answer: In typical urban areas, 2–6 times for download, 2–5 times for upload, with latency reduced by 1.5–2 times. It heavily depends on coverage and network load.
• Question: Is an external antenna necessary? Answer: No, but it is critical in weak signal areas. For n78, a directional panel antenna often yields significant SINR improvements.
• Question: How can I tell if I have SA? Answer: mmcli shows access tech: 5g-sa. Also, ping will drop, and reliance on 4G will cease.
• Question: Can I use a smartphone as a modem? Answer: For pilots — yes, via USB tethering. For 24/7 — no, overheating and instability are likely.
• Question: Is static IP addressing necessary? Answer: No, the mobile proxy uses the operator's outgoing IP. Publication goes through a reverse tunnel to your server.
• Question: What should I do if speeds drop dramatically in the evening? Answer: This is peak hour traffic. Check antenna orientation, adjust bands, or move the node closer to the base station.
• Question: How can I safely update the system? Answer: Take snapshots of configurations, update packages one at a time, and check proxy and tunnel functionality after each step.
• Question: Can I scale to dozens of nodes? Answer: Yes, use auto-configuration, centralized monitoring, and multiple VPS to distribute the load.
• Question: How can I impact IP reputation? Answer: Reputation is formed by providers and services. Choose stable 5G ranges and locations, avoiding overloading a single IP with multiple aggressive requests.

Conclusion

You have completed the entire process: assessed the viability of 5G, selected equipment, understood frequency bands, assembled and cooled the node, configured the 5G connection (NSA/SA), installed and secured 3proxy, published access via a reverse tunnel, and tested performance quality. Now you possess a reproducible scheme for a mobile 5G proxy that can be scaled and maintained. If you want to save time on management and gain automation, consider specialized services like mobileproxy.space. To reinforce your understanding, return to the pitfalls section and double-check your location and plan. You can also add monitoring, alerts, client balancing, and quotas. Happy working!