← Back to NewsTechnical

LoRaWAN Gateway Backhaul: 4G vs Ethernet vs Wi-Fi (and When Satellite Makes Sense)

·6 min read
Rooftop LoRaWAN antenna alongside cellular masts above a town

Most LoRaWAN planning focuses on the radio side: range, antennas, and spreading factors. But a gateway has two connections, and the one that fails most often is the other one. Backhaul is how the gateway reaches your network server, and if it drops, every sensor behind that gateway goes silent.

This guide compares the four realistic backhaul options for LoRaWAN gateways (Ethernet, Wi-Fi, 4G, and satellite) and explains why the choice has more to do with operations than bandwidth.

What Is Gateway Backhaul?

In a LoRaWAN network, sensors talk to gateways over radio. Gateways then forward that traffic over an ordinary IP connection to the LoRaWAN network server, which passes it on to your application. That IP connection is the backhaul.

LoRaWAN traffic is tiny, so bandwidth is almost never the problem. What matters is that the connection is continuous, that it stays up without anyone touching it, and that latency is low enough for downlinks to reach devices inside their receive windows.

The Four Options Compared

BackhaulStrengthsWeaknessesBest For
EthernetStable, low latency, PoE powerDepends on site IT; cabling to roofs is costlySites you own and control
Wi-FiQuick to set upFragile signal, password changes, captive portalsShort indoor pilots only
4G / LTEIndependent of the site, works almost anywhereNeeds SIM management and decent signalMost production deployments
SatelliteWorks with no terrestrial networkHigh power draw and cost per siteGenuinely remote locations

Ethernet

On paper, Ethernet is the best backhaul. It is fast, stable, and can power the gateway over PoE. In practice, the gateway is usually a guest on someone else's network. That means firewall approvals, VLAN requests, and an IT team that may change the network without knowing a gateway depends on it. Running cable to a roof or mast can also cost more than the gateway itself.

Wi-Fi

Wi-Fi is convenient for testing a gateway on a desk. For anything long-lived, it brings the weaknesses of Ethernet (someone else's network) plus its own: weak signal through walls, congested channels, password rotations, and guest networks with captive portals that a gateway cannot click through.

4G / LTE

Cellular backhaul makes the gateway independent of the site. It needs only power and mobile coverage, so there is nothing to negotiate with the building owner and nothing on the local network to break it. Gateways typically use LTE Cat 1 or Cat 4 modems, which comfortably handle LoRaWAN traffic.

The trade-off is operational: someone has to manage SIMs, data plans, and signal quality across the fleet. Latency is higher than on Ethernet, but well within what LoRaWAN downlink timing allows.

Satellite

Low-earth-orbit satellite services have made satellite backhaul far more practical, with much lower latency than older systems. The terminals still draw significantly more power than a gateway and add real cost per site, so they make sense only where there is no usable mobile coverage at all: offshore, mountains, or very remote agricultural land.

The Hidden Cost of Using the Customer's Network

The real cost of site Ethernet and Wi-Fi rarely shows up in a spreadsheet. It shows up as weeks waiting for a firewall change, an outage after a router replacement nobody mentioned, or a support call where the gateway team and the building IT team each believe the problem is on the other side.

Security teams are also, rightly, cautious about unmanaged devices on their networks. Our guide to IoT gateway security explains why outbound-only connectivity helps, but cellular backhaul avoids the question entirely: the gateway never touches the customer's network.

How Much Data Does a LoRaWAN Gateway Use?

Less than most people expect, but more than the sensor payloads alone suggest. Each uplink is wrapped in metadata by the packet forwarder, and the gateway also sends status reports, keepalives, and management traffic. Firmware updates add occasional larger downloads.

A gateway serving a few hundred sensors that report every 15 minutes typically uses tens to low hundreds of megabytes per month. Busy gateways in dense deployments use more. When sizing data plans, measure a real gateway for a few weeks rather than calculating from payload sizes, and leave headroom for updates.

What About Ethernet With 4G Failover?

Some gateways support a wired primary connection with cellular failover. It sounds like the best of both, but it combines the operational overhead of both: you still need IT approval for the wired link, and you still need to manage a SIM. It also makes faults harder to diagnose, because the gateway may be quietly running on its backup for weeks. For most fleets, 4G as the only backhaul is simpler and just as reliable.

How to Choose

  • →Choose Ethernet if you own the site and its network, cabling is easy, and your team controls any changes to it.
  • →Choose 4G if gateways sit on customer sites, rooftops, farms, or anywhere you do not control the local network. This covers most commercial deployments.
  • →Choose satellite only when there is no workable mobile signal, even with an external antenna or a higher mount.
  • →Avoid Wi-Fi for anything beyond a short test.

Note that this is a different question from LoRaWAN vs cellular IoT, which is about how the sensors themselves connect. Using 4G for gateway backhaul keeps the low-power, low-cost benefits of LoRaWAN sensors while removing the site network from the equation.

How EdgePilot Handles Backhaul

Every EdgePilot gateway ships with built-in 4G connectivity, included in the annual price for EU deployments. There is no need for Ethernet, Wi-Fi, or any local internet at the installation site, and no firewall changes to request. We manage the SIMs, monitor connectivity on every gateway, and handle diagnostics remotely through an outbound-only tunnel.

The result is a gateway that only needs power and a mounting point. See what is included in our pricing, or contact us to check coverage for your sites.

Gateway Backhaul FAQ

Can a LoRaWAN gateway work without internet?

Not in a standard deployment. The gateway needs a connection to the network server to forward uplinks and receive downlinks. Some gateways can run a network server locally for isolated edge setups, but you still need connectivity to get data to your applications and to manage the gateway remotely.

Does 4G latency affect LoRaWAN?

Normally, no. LoRaWAN receive windows open at least a second after an uplink, which leaves plenty of time for a typical 4G round trip. On very poor connections, increasing the RX1 delay on the network server adds extra margin for joins and downlinks.

What if there is no 4G coverage at the site?

Try an external cellular antenna, a higher mounting point, or a SIM that can use a different mobile network. Indoor dead spots are often solved by moving the gateway outdoors. If none of those work, satellite backhaul is the fallback for truly remote sites.

Want gateways that don’t depend on site internet?

Every EdgePilot gateway includes managed 4G connectivity, so there’s no site network to negotiate or troubleshoot.

Request a Demo