Search

how to configure private lorawan® channels on rak gateways

Learn how to set up private LoRaWAN channels on RAK gateways for custom frequencies, TTN, ChirpStack, and region-specific IoT deployments.

Overview

This feature allows RAK gateways in Packet Forwarder (PF) mode to support user-defined LoRaWAN private channels, offering flexible frequency and parameter configuration. It enables integration with custom regional frequencies or proprietary server-defined bands outside standard LoRaWAN regional specs.

In real-world deployments, LoRaWAN networks often require custom channel plans due to:

  • Region-specific frequency regulations not fully covered by standard LoRaWAN regional profiles

  • Custom frequency plans used by servers like ChirpStack or The Things Stack that fall outside LoRaWAN regional defaults, requiring the gateway to match those exact frequencies

  • Private or closed networks isolating devices on non-standard frequencies to reduce interference

  • Alignment with existing spectrum allocations in mixed-network environments (e.g., utilities, mining, agriculture)

How It Works

Private channels can be configured directly through the WisGateOS2 Web UI, allowing you to define a custom set of channels that the gateway will use for LoRa® communication.

Once configured, these private channels replace the default regional channel plan. The gateway will then operate only on the selected frequencies for both uplink and downlink.

This approach ensures:

  • Full compatibility with LoRaWAN servers that use custom frequency plans, such as ChirpStack or The Things Stack.

  • Flexible deployment in non-standard or region-specific frequency environments.

Private Channel Setup

This section explains how to configure private channels on a RAK gateway.

Preparations

Before you begin, complete the following steps:

  1. Obtain the exact frequency plan from your LoRaWAN network server.

  2. Verify configuration alignment. The gateway's private channel settings must exactly match the server-defined frequency plan to ensure proper uplink and downlink communication.

🗒️
NOTE

This guide uses The Things Network (TTN) Israel 917~920 MHz plan, covering channels 1-4 and 11-14, as an example.

  1. Check official references. Detailed frequency information can be found in the LoRaWAN Frequency Plans for The Things Stack.

  2. Confirm gateway registration. Make sure the RAK gateway is already registered in TTN with the correct frequency plan selected.

RAK Gateway Registered in TTN
Figure 1: RAK Gateway Registered in TTN

 

RAK Gateway Configuration

Private LoRaWAN channels can be enabled only when the gateway is running in Packet Forwarder mode. Make sure the gateway is in this mode before configuring the channels.

  1. Access the RAK gateway's web UI.

  2. Navigate to LoRa > Configuration. 

Packet forwarder Work mode
Figure 2: Packet forwarder Work mode
  1. Under Frequency Plan, click to expand the View detailed regional parameters of the frequency plan dropdown.
Select a frequency plan
Figure 3: Select a frequency plan
  1. Set Conform to LoRaWAN to OFF and confirm the action.
Confirmation Prompt for Conform to LoRaWAN OFF
Figure 4: Confirmation Prompt for Conform to LoRaWAN OFF
  1. Click Edit under LoRa Concentrator.
Edit LoRa Concentrator
Figure 5: Edit LoRa Concentrator
  1. Manually configure the frequencies based on your server's plan.
Configure Frequency Plan
Figure 6: Configure Frequency Plan

  1. Click Confirm to apply channel configuration.

Apply Channel Configuration
Figure 7: Apply Channel Configuration

  1. Click Save changes to store the configuration.

Verify Gateway Status in TTN

  1. Open the TTN Console.
  2. Navigate to your registered gateway.
  3. Verify that the gateway status shows recent activity (e.g., Last activity 5 seconds ago).
🗒️
NOTE

RAK gateways automatically connect to the TTN EU1 cluster when operating in Packet Forwarder mode. To connect to other TTN clusters (e.g., US1, AS1) or to different network servers such as ChirpStack or a private LNS, you must update the gateway’s packet forwarder settings with the correct server address and port.

 

Gateway connected status
Figure 8: Gateway connected status

Troubleshooting

Issue Possible Cause Suggested Solution

 

No uplink packets visible

Incorrect server address or protocol

Make sure that the gateway is set to Packet Forwarder mode and verify that the server communication settings are correctly configured for your LNS

Frequency plan mismatch

Check the frequency plan used by your server and ensure that all channels are correctly entered in the gateway UI.

FAQs

1. Can I use private channels with any network server?
Yes. RAK gateways in Packet Forwarder mode can work with any LoRaWAN network server that supports manually defined channel plans, such as The Things Stack (TTS), ChirpStack, and private LNS deployments

2. Will the network server automatically sync channels to the gateway?
No. Private channel configuration is entirely manual. The server will not push frequency plans to the gateway.
You must ensure full alignment between your gateway's private channels and the server's expected frequencies.

3. Do I need to configure anything on the node (end device)?
Yes. Your LoRaWAN end device must use the same uplink channel set as the gateway. If using a fixed Rx2 frequency, it must also match the gateway's configured downlink frequency.

4. Can I use both LoRa Concentrator 0 and 1?
Yes. Each concentrator (and its sub-radios) can monitor different frequency blocks. Use both if your channel plan spans a wide frequency range.

Changelog
  • Version 1 - How to Configure Private LoRaWAN® Channels on RAK Gateways
    • Date Published: 08/14/2025


 

Updated