Search

how to connect rak gateways to chirpstack v4 via udp

This guide explains how to connect a RAK gateway running WisGateOS 2 (v2.2.x and above) to ChirpStack v4 via Semtech UDP protocol, enabling LoRaWAN packet forwarding in external network server deployments.

Prerequisites

Before configuring the connection, make sure the following conditions are met:

  • A deployed ChirpStack v4 Network Server.
  • Open the following ports on your ChirpStack server:
    • UDP 1700 for LoRaWAN packet forwarding
    • HTTP 8080 for ChirpStack Web UI access
  • A RAK Gateway with internet access.
  • Gateway running WisGateOS 2, version 2.2.x, or above.

Register the Gateway in ChirpStack v4

This section provides step-by-step instructions for registering a RAK gateway in ChirpStack v4. For detailed instructions, refer to: How to Register a RAK Gateway in ChirpStack v4

Configure the Gateway

  1. Log in to the gateway's Web UI.
WisGate Web UI Login Page
Figure 1: WisGate Web UI Login Page
  1. Go to LoRa > Configuration, and set Work Mode to Packet forwarder.
Setting Packet Forwarder Mode
Figure 2: Setting Packet Forwarder Mode
  1. In the Protocol field, click the dropdown. Then configure the following parameters.
Set Protocol Fields
Figure 3: Set Protocol Fields
  • Protocol: Select Semtech UDP GWMP (default).
  • Server address: Enter the public IP address of your ChirpStack server, for example: 18.156.176.220
  • Server port up/Server port down: 1700
  1. Click Save changes to apply the configuration.

Verify Gateway Status

Return to the ChirpStack Web UI and check the gateway status. If the configuration is correct, the status should change to Online within a few minutes.

Registered Gateway’s Online Status
Figure 4: Registered Gateway’s Online Status

Troubleshooting

ISSUE POSSIBLE CAUSE SOLUTION
Gateway Offline Incorrect Gateway EUI (EUI64) Double-check the EUI entered in ChirpStack matches the one from the gateway Web UI or device label.
Firewall blocked UDP port 1700 Ensure UDP port 1700 is open and reachable on the ChirpStack server.
Gateway not connected to the Internet Confirm the gateway has Internet access or can reach the server IP.
Server address misconfigured Verify the ChirpStack server IP is correctly set in the Packet Forwarder.
Region mismatch in ChirpStack config Check`chirpstack.toml` and ensure the region used by the gateway is listed in enabled_regions.
No data in Live Frames Stats interval too long or unset Set a reasonable value (e.g., 30–60 seconds) for the Stats interval field.

FAQs

  1. Can I use a private IP for server address?
    Yes, but only if the gateway and server are on the same LAN. Use a public IP for Internet-based deployment.
  2. What if my firmware is older than WisGateOS 2.2.x?
    Update to the latest WisGateOS 2 firmware before proceeding. You can check your current version and perform the upgrade via the gateway’s Web UI under System > Firmware. For detailed steps and download links, refer to the official upgrade guide: WisGateOS 2 Firmware Upgrade Documentation.
Changelog
  • Version 1.1 - Added UTM links
    • Date Published: 09/01/2025
  • Version 1 - How to Connect RAK Gateways to ChirpStack v4 via UDP
    • Date Published: 08/07/2025

Updated