Cellular Management

Overview

Every ARROW device carries an integrated LTE modem so that a dropped ethernet link does not mean a device you cannot reach. When the wired connection fails, cellular takes over automatically and the device stays online. Most of the time you will not think about it; the value shows up the day the site network goes down mid-engagement and your device is still there.

Viewing Cellular Status

Open the Cellular section in ARROW Manager to watch the modem in real time. The header tells you the overall state (such as DISCONNECTED), the SIM status, and the current mode (such as LTE). Sub-tabs on the left, Signal & Link, Tower & Cells, Modem & SIM, and Operating Mode, break the detail out by area.

Signal & Link

Start here. This is the view you open when someone reports the device is slow or unreachable and you need to know whether the radio itself is healthy. It leads with an RSSI bar and a plain-language quality rating (EXCELLENT, GOOD, and so on), then breaks out the four readings that actually matter for diagnosis: RSRP, RSRQ, SINR, and RSSI. The Link panel on the right is the practical half: the active interface (such as wwan0), whether it is up or down, the default route, the registration state (searching, registered, and so on), latency, and both the internal and public IP addresses. Hit Refresh to re-read the modem on demand.

ARROW Manager cellular Signal and Link view with RSSI bar and link status

Signal & Link leads with an RSSI quality rating and the underlying RSRP, RSRQ, SINR, and RSSI readings

Tower & Cells

Reach for this when the signal looks weak and you want to understand why. It names the tower operator and SIM brand, then the physical channel the device is camped on: band, EARFCN, Cell ID, PCI, TAC, MCC/MNC, uplink and downlink bandwidth, and the duplex mode. The Carrier Aggregation table shows any extra carriers the modem has bonded for more throughput, and the Neighbor Cells table lists the nearby cells the modem can see, with their RSRP and RSRQ, which tells you whether there is a stronger tower to hand off to.

ARROW Manager Tower and Cells view with channel detail, carrier aggregation, and neighbor cells

Tower & Cells shows the physical channel, carrier aggregation, and the neighbor cells the modem can see

Modem & SIM

This view is about the hardware and the account, not the live signal, so you visit it when confirming what is installed rather than chasing a signal problem. It reports the modem manufacturer, model, and firmware build, along with the SIM’s IMSI and ICCID. The APN Contexts panel lists the access point names the modem is configured with (their CID, IP type, and APN), which is the first thing to check with support when the link connects but no data flows.

ARROW Manager Modem and SIM view with modem identity, SIM identifiers, and APN contexts

Modem & SIM identifies the modem and SIM and lists the configured APN contexts

Operating Mode

This is the one view with a control on it rather than just readouts. It shows whether the device is currently on ethernet, LTE Active, or LTE Idle, and offers a Force LTE Idle action for when you want to keep the modem registered but stop it carrying traffic. The controls only appear when the device is primarily on LTE; when ethernet is doing the work, this view tells you the mode controls are unavailable, which is expected.

Operating Mode shows the current mode and offers Force LTE Idle when the device is primarily on LTE

The Cellular card on the Dashboard gives you the same headline information, carrier, signal, band, and mode, without leaving the overview.

Connection Status

Status	Meaning
Connected	Cellular is online and can route traffic
Registered	Modem is registered with the carrier but may not have data
Disabled	Cellular is intentionally turned off
Disconnected	No cellular connection available

When cellular is connected, a second badge tells you whether it is doing any work: Active Route means traffic is going over LTE right now, while Backup means it is connected and standing by while ethernet carries the load.

Understanding the Signal Metrics

The headline number is signal strength in dBm. As a rough guide: -50 to -70 is excellent, -70 to -85 is good, -85 to -100 is fair, -100 to -110 is poor, and anything below -110 is very poor and likely to be unreliable.

If you need to diagnose a marginal connection, the advanced metrics tell you more than raw strength does. SINR (signal-to-interference-plus-noise) is healthy above 10 dB, RSRP (reference signal received power) above -80 dBm, and RSRQ (reference signal received quality) above -10 dB. Weak RSRP with poor SINR usually points to interference or congestion rather than distance from the tower.

The rest of the connection detail (carrier, mode, band, internal and public IP, latency, and current download and upload speeds) is there when you need to confirm exactly how the device is connected.

Monitoring Data Usage

Cellular data is metered by your carrier, so it is worth knowing where it goes. The Usage tab meters traffic by category, and it is split into four sub-tabs: Live, History, Categories & Rules, and Settings. The same information is also available from Settings under Data Usage.

ARROW Manager cellular data usage with per-category breakdown

The Usage tab meters cellular data with a per-category breakdown

Live

This is the tab to open when you want to know what the device is using right now. It shows the meter’s own status (running or not, how many rules are installed, how often it polls, and how long ago the last tick was), the total since the last measurement tick, and the cumulative total since the meter was installed. The Per-category breakdown table lists in, out, and total bytes for each category, plus the change since the last tick and each category’s share of the total, so you can confirm the device is only using the connection you expect it to.

Live shows the meter status, totals since the last tick, and a per-category breakdown

History

Use History when a data bill looks high and you want to find the spike. It plots usage over time in fixed windows, and you can switch the range with the 1h, 24h, 7d, and 30d buttons. Each row is a time bucket with its in and out bytes stacked together; hover a row for the per-category detail behind the total.

History breaks usage into time buckets over 1h, 24h, 7d, or 30d ranges

Categories & Rules

This tab is where the buckets in Live and History are defined. It lists every category with its color, slug, name, description, and whether it is enabled, and marks the built-in ones (DNS, NTP, NetBird control, and the rest) so you can tell them apart from your own. You would come here to add a New category or edit the rules that classify traffic into it, for example to break out a specific host you want to watch separately.

ARROW Manager Usage Categories and Rules tab listing traffic categories

Categories & Rules defines the buckets that traffic is sorted into and the rules that classify it

Settings

The Settings tab controls the meter itself. A Tracking enabled master switch turns the counters and samples on or off, and Auto-install on boot decides whether the classification rules are reinstalled every time ARROW Manager starts. You also set the poll interval and how many days of history to retain here. Saving reinstalls the underlying rules so the kernel state matches, and a Last install line at the bottom confirms it worked.

Settings controls tracking, auto-install on boot, the poll interval, and retention

Automatic Failover

Failover is automatic and needs no input from you. As long as ethernet is up and has real internet access, cellular sits in backup mode and traffic goes over the wire. The moment ethernet drops, or stays plugged in but loses internet, or its gateway becomes unreachable, cellular promotes itself to the active route and carries traffic over LTE. When ethernet recovers, cellular steps back down to backup.

You can always tell which link is carrying traffic by the default route interface shown in ARROW Manager: vmbr0 means the ethernet bridge is active, and wwan0 means the cellular modem is active.

LTE Bridge Mode (Advanced)

Everything above is about keeping the device itself reachable. LTE Bridge Mode is a different, deliberately narrow feature: it builds a dedicated bridge that routes your virtual machines’ traffic out over cellular. You would reach for this only in a corner case, such as needing an isolated internet path for a VM when no ethernet is available.

LTE Bridge Mode costs $20 per gigabyte. Treat it as temporary. Use it for emergency access or short isolated tests, and switch back to ethernet for normal operation.

The Settings page surfaces the bridge state so you know what is configured before you turn it on: whether Bridge Mode is enabled, whether the vmbr1 interface exists, whether the LTE connection (wwan0) is active, whether NAT rules are in place, and how many VMs are attached to the bridge.

Enabling and disabling

To enable it, open ARROW Manager, go to Settings > Connectivity, and find LTE Bridge Mode (Advanced). The LTE connection must be active first. Click Enable LTE Bridge and confirm the cost warning.

To turn it off, return to Settings > Connectivity and click Disable LTE Bridge, then confirm. Any VMs attached to vmbr1 will lose connectivity until you point them back at a normal bridge.

Configuring VMs for the LTE Bridge

Getting a VM onto the bridge is two steps: attach it in Proxmox, then give it an address inside the VM.

In Proxmox, enable LTE Bridge Mode in ARROW Manager, edit the VM’s hardware, change its Network Device bridge from vmbr0 to vmbr1, and restart the VM.

Inside the VM, DHCP is the easy path and what we recommend: set the interface to DHCP and it will pick up an address in the 192.168.2.10-250 range, a gateway of 192.168.2.1, and DNS automatically. If you need a static address instead, use an IP in 192.168.2.2-254 with a 255.255.255.0 subnet mask, a gateway of 192.168.2.1, and a DNS server such as 8.8.8.8.

To confirm the VM is actually egressing over cellular, check its public IP from inside:

curl ifconfig.me

That should return the cellular public IP address.

Under the hood, the bridge is a vmbr1 interface at 192.168.2.1/24 with a DHCP server handing out addresses in the 192.168.2.10-250 range. NAT rules translate VM addresses onto the LTE interface, IP forwarding is enabled between vmbr1 and wwan0, and the whole bridge disables itself automatically if the LTE connection drops so you are never left with a dead route.

Troubleshooting

Cellular shows Disconnected. This is usually signal, SIM, or hardware. Check signal strength from a different location, ask VTEM Labs support to verify the SIM, and restart the device if the modem seems wedged.

Connected but no internet. The link is up but data is not flowing, which typically means an exhausted data plan, a carrier outage, or an APN problem. Wait out carrier issues, contact VTEM Labs to confirm the plan is active, and check whether other cellular devices work in the same spot.

LTE Bridge will not enable. The most common reason is that the LTE connection is not active, since the bridge requires it. Confirm “LTE Connection” shows active, refresh the status, and restart ARROW Manager if needed.

A VM cannot get out through the bridge. Confirm the VM’s network device is set to vmbr1, that it has an address in the 192.168.2.x range, and that every bridge status indicator is green. Test with DHCP before trying a static IP.

ARROW Manager Network - Network status and management
VPN Management - VPN connectivity
Device Management - Managing ARROW devices