GUIDE

Network Setup for BoxPhone

LAN, Wi-Fi, IP, and bandwidth — what to think about before scaling

Sikrid Team2026-04-267 min read

Before launching BoxPhone, the thing most people skip is network infrastructure. A consumer router can't handle 100 devices — when you scale up, the network becomes a bottleneck before the hardware does.

How networking works in a BoxPhone system

Every device in a BoxPhone fleet needs:

Internet connectivity (via Wi-Fi or proxy)
A connection to the host PC (over USB or ADB-over-TCP)
An assignable per-device IP

Once you scale past 50 devices, consumer routers run into trouble: DHCP tables overflow, NAT pools exhaust, and throughput drops.

What each component does

Router

You need one that supports:

100+ concurrent device connections
VLAN configuration
Static DHCP / IP reservation
QoS (Quality of Service) for traffic prioritization

Recommended: Ruijie EG series, MikroTik RB series, UniFi USG/UDM — not the free router from your ISP.

Wi-Fi vs LAN

	Wi-Fi	LAN
Stability	Medium	High
Phone compatibility	Native	Via USB tether
Scaling to 100+	Needs multiple APs	Use a switch
Best for	General BoxPhone use	Heavy automation

Most setups use Wi-Fi because Android handles it natively — but you need enterprise-grade APs.

Bandwidth

Rough estimates:

Device scrolling normal content: ~0.5–1 Mbps
Device watching live streams: ~2–3 Mbps
Device uploading video: ~3–5 Mbps

100 devices on a mixed workload need around 150–200 Mbps peak both download and upload (500/500 Mbps fiber as a floor).

What you need — setup

Internet line — 500/500 Mbps fiber or better
Enterprise router — supports 100+ devices
Wi-Fi APs — business-class such as UniFi, TP-Link Omada, or Aruba — 1 AP per 30–50 devices
Switch (if using LAN) — Gigabit switch with VLAN support
Static DHCP — assign a fixed IP per device for easier debugging
Proxy management — software that assigns a proxy per device (see What is a proxy?)

Common failure points

Consumer router that can't scale — DHCP overflow at 50 devices
Wi-Fi channel congestion — multiple APs on the same channel
NAT port exhaustion — 100 devices × many sessions = ports run out
ISP throttling — some ISPs throttle silently
No static DHCP — you can't tell which device has which IP when debugging

Summary

Network is not something you can add later — it's the foundation of the whole system.

Invest in the network properly once — it's far cheaper than rebuilding after you outgrow it.

FAQ

01Can I use a regular home router?+

Yes, for 5–15 devices. Beyond that, consumer routers run into DHCP table overflows, NAT pool exhaustion, and throughput drops. We recommend moving to enterprise-grade gear.

02How much bandwidth do I need for 100 devices?+

Peak around 150–200 Mbps for a mixed workload. We recommend 500/500 Mbps fiber as a minimum — live streaming and uploads in particular need upload headroom.

03Wi-Fi or LAN — which is better?+

Most setups use Wi-Fi because Android connects natively. But you need enterprise-grade APs, roughly 1 AP per 30–50 devices. LAN is the right choice for heavy automation workloads.

04Do I need to set up VLANs?+

At 50+ devices, yes. VLANs separate device groups, contain failures so a problem in one group doesn't propagate, and make debugging far easier.