A diagram comparing the two main LoRaWAN Gateway Modes: Packet Forwarder forwarding all data, and Built-in LNS processing data locally.

LoRaWAN Gateway Modes Explained: Packet Forwarder vs. Built-in LNS

Written by: Robert Liao

|

Published on

|

Time to read 5 min

Robert Liao, Technical Support Engineer

Robert Liao is an IoT Technical Support Engineer at Robustel with hands-on experience in industrial networking and edge connectivity. Certified as a Networking Engineer, he specializes in helping customers deploy, configure, and troubleshoot IIoT solutions in real-world environments. In addition to delivering expert training and support, Robert provides tailored solutions based on customer needs—ensuring reliable, scalable, and efficient system performance across a wide range of industrial applications.

Summary

So, you've selected a LoRaWAN gateway for your IoT project. Now you're faced with a critical configuration choice that will define your entire network architecture: should you run it in Packet Forwarder mode or as a gateway with a Built-in LoRaWAN Network Server (LNS) ?

This guide dives deep into these two primary LoRaWAN Gateway Modes .

We'll break down how each mode works, provide a head-to-head comparison of their pros and cons, and offer clear advice on which to choose for your specific application—whether you're connecting to a public network or building a secure, private IoT solution.

Introduction: Your Gateway is Ready, But What's Next?

You've unboxed your new LoRaWAN gateway, powered it on, and it's ready to connect. But connect to what, and how? This is a fundamental question that I've seen trip up many developers. The way your gateway handles data packets determines your network's latency, reliability, security, and cost. It's a strategic decision that goes far beyond a simple configuration toggle.

At its core, every LoRaWAN packet needs to get from your sensor, through the gateway, to a LoRaWAN Network Server (LNS), which is the brain of the network. The choice of LoRaWAN gateway mode dictates where that brain lives. Does it live in the cloud, or can it live directly inside your gateway? As we covered in our Ultimate Guide to the Industrial LoRaWAN Gateway , understanding this trade-off is key to building a successful LoRaWAN solution.


A diagram comparing the two main LoRaWAN Gateway Modes: Packet Forwarder forwarding all data, and Built-in LNS processing data locally.


Packet Forwarder: The "Bridge" of LoRaWAN Gateway Modes

Packet Forwarder mode is the most traditional and common of the LoRaWAN gateway modes .

How it Works: The Data Path

In this LoRaWAN gateway mode , the gateway acts as a simple and "dumb" bridge. Its only job is to receive all raw LoRaWAN radio packets from the air and immediately forward them, usually over a standard IP connection (Ethernet, Wi-Fi, or Cellular), to a separate, external Network Server. This LNS can be a public service like The Things Network , a commercial platform, or a self-hosted ChirpStack instance running in the cloud or a data center.

Pros and Cons of Packet Forwarder Mode

  • Pros:
    • Simple Configuration: Incredibly easy to set up; just point the gateway to your LNS IP address.
    • Centralized Management: Ideal for large fleets pointing to a single cloud LNS.
    • Public Network Ready: The required mode for connecting to public LoRaWAN networks.
  • Cons:
    • Requires Constant Internet: If the internet backhaul fails, the gateway becomes a paperweight.
    • Higher Latency: The round-trip to the cloud is unsuitable for real-time control. This is a key consideration when choosing between LoRaWAN gateway modes .
    • Security Concerns: Raw data passes through the public internet and third-party servers.

Built-in LNS: The "All-in-One" LoRaWAN Gateway Mode

With the rise of more powerful hardware, a new, more robust LoRaWAN gateway mode has become popular: running the Network Server directly on the gateway. A gateway with these capabilities offers a complete, self-contained solution.

How it Works: The Data Path

In this LoRaWAN gateway mode , the LoRaWAN gateway is the Network Server. It receives LoRaWAN packets, processes them, de-duplicates them, and handles all the LoRaWAN MAC layer logic right on the device. It then forwards the decrypted application data directly to your application server, often via a lightweight MQTT message. This is a true edge computing architecture.

Pros and Cons of Built-in LNS Mode


  • Pros:
    • Maximum Security: Data can be processed entirely on your local network.
    • Ultra-Low Latency: Downlink commands are nearly instantaneous.
    • Offline Operation: This is the killer feature. The local network continues to function perfectly even if the internet fails. This is a major advantage of this LoRaWAN gateway mode .
  • Cons:
    • Requires a More Powerful Gateway: Needs sufficient CPU and RAM to run the LNS software (e.g., ChirpStack ).
    • More Involved Setup: Initial LNS configuration is more complex than Packet Forwarder mode.

A comparison table infographic detailing the differences between LoRaWAN Gateway Modes: Packet Forwarder versus Built-in LNS.


Choosing Between LoRaWAN Gateway Modes

So, how do you decide which of the LoRaWAN gateway modes is right for you? It comes down to your application's requirements.

  • Choose Packet Forwarder Mode if:
    • You are connecting to a public or existing third-party LoRaWAN network.
    • Your application is not time-sensitive and can tolerate internet latency.
  • Choose Built-in LNS Mode if:
    • You are building a private LoRaWAN network for a specific site (like a farm, factory, or building).
    • You require high reliability, offline operation, and ultra-low latency.
    • Data sovereignty and security are your top priorities.

The Robustel R1520LG Industrial LoRaWAN Gateway shown operating in both LoRaWAN Gateway Modes: Packet Forwarder and Built-in LNS.


Conclusion

The choice between LoRaWAN gateway modes is a foundational decision in your IoT network design. While the Packet Forwarder mode offers simplicity and easy access to public networks, the Built-in LNS mode provides the security, reliability, and performance demanded by serious industrial and commercial applications. By understanding the Packet Forwarder vs Built-in LNS trade-offs and selecting a flexible, industrial-grade gateway, you can build a LoRaWAN solution that is perfectly tailored to your project's unique requirements.

Frequently Asked Questions (FAQ)

Q1: Can I switch from Packet Forwarder to Built-in LNS mode later?

A1: Yes, on a flexible gateway like the R1520LG. You can start by forwarding packets to a cloud server and later decide to install and run the ChirpStack LNS directly on the gateway for a fully private network, or vice versa.

Q2: Does running a built-in LNS use a lot of the gateway's cellular data?

A2: No, it actually saves data. When the LNS is running locally, only the small, processed application data is sent over the cellular backhaul, not the much larger raw LoRaWAN packets with their metadata.

Q3: What is ChirpStack and why is it mentioned for built-in LNS?

A3: ChirpStack is the leading open-source LoRaWAN Network Server. Because it's open-source and efficient, it can be installed directly onto a powerful gateway (often using Docker), making it the most popular choice for creating a private, all-in-one LoRaWAN gateway with a built-in LNS.