Back to all articles
GUIDE

Network Setup for BoxPhone

Sikrid Team avatarSikrid TeamSikrid Engineering Team

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

2026-04-267 min read
Before you fire up BoxPhone, the part most people skip is the network. A regular consumer router just can't handle 100 devices — and once you scale, the network becomes the bottleneck way before the hardware does.

How the network fits in

Every device in a BoxPhone fleet needs three things:

  • Internet (over Wi-Fi or proxy)
  • A connection back to the host PC (USB or ADB-over-TCP)
  • Its own IP address

Once you go past 50 devices, consumer routers start having a bad time — DHCP tables overflow, the NAT pool runs out, throughput drops.

What each piece does

Router

Pick one that can handle:

  • 100+ devices connected at the same time
  • VLAN configuration
  • Static DHCP / IP reservation
  • QoS — so you can prioritize traffic

We recommend Ruijie EG series, MikroTik RB series, or UniFi USG/UDM. Not the free router your ISP gives you.

Wi-Fi vs LAN

Wi-FiLAN
StabilityMediumHigh
How phones connectNativeVia USB tether
Scaling to 100+Multiple APs neededUse a switch
Best forGeneral BoxPhone useHeavy automation

Most setups land on Wi-Fi because Android just works with it. But you do need enterprise-grade APs to make it stable.

Bandwidth

Rough numbers to plan around:

  • A device scrolling normal content: ~0.5–1 Mbps
  • A device watching a live stream: ~2–3 Mbps
  • A device uploading video: ~3–5 Mbps

100 devices on a mixed workload peaks at around 150–200 Mbps both directions — so 500/500 Mbps fiber as the floor.

What you need to put together

  1. Internet line — 500/500 Mbps fiber or better
  2. Enterprise router — handles 100+ devices
  3. Wi-Fi APs — business-class like UniFi, TP-Link Omada, or Aruba — 1 AP for every 30–50 devices
  4. Switch (if using LAN) — Gigabit switch with VLAN support
  5. Static DHCP — pin a fixed IP to each device so debugging stays sane
  6. Proxy management — software that hands a different proxy to each device (see What is a proxy?)

Where it usually breaks

  • Consumer router that can't keep up — DHCP overflows at 50 devices
  • Wi-Fi channel congestion — multiple APs sitting on the same channel
  • NAT port exhaustion — 100 devices × lots of sessions = the router runs out of ports
  • ISP throttling — some ISPs throttle quietly without telling you
  • Not setting up Static DHCP — when something breaks, you can't tell which IP belongs to which device

Wrapping up

The network isn't something you bolt on later — it's the foundation everything else sits on.

Spend the money once and do it right — it's a lot cheaper than rebuilding the whole thing after you outgrow it.

FAQ

01Can I use a regular home router?+

Sure, up to 5–15 devices. Past that, consumer routers start running into DHCP table overflows, NAT pools running out, and throughput dropping. Move to enterprise gear before it bites you.

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

Peak around 150–200 Mbps on a mixed workload. We'd say 500/500 Mbps fiber is the floor — live streaming and uploads in particular need that upload headroom.

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

Most setups use Wi-Fi because Android handles it natively. But you do need enterprise-grade APs, roughly 1 AP per 30–50 devices. If you're running heavy automation, LAN is the better call.

04Do I have to set up VLANs?+

Past 50 devices, yes. VLANs split your device groups apart so one group's problem doesn't take down everything, and debugging gets way easier.

Read next

Related Articles

All articles →
READ MORE / INQUIRE

Ready to deploy BoxPhone? — Talk to the Sikrid team

We design and assemble BoxPhone in Thailand with a complete Enterprise Device Management system in a single platform. See more on TikTok @sikridphonefarmth