Security
Default Open Ports
This section provides an overview of the system-level open ports on WisGateOS 2.
| Port | Protocol | Service | Description |
|---|---|---|---|
| 22 | TCP | SSH | Remote command-line management, typically used by administrators to securely log into the gateway. |
| 68 | UDP | DHCP Client | Used by the gateway as a DHCP client to receive IP lease and renewal responses from DHCP servers. Required for automatic IP address assignment and renewals. |
| 80 | TCP | HTTP | Standard WebUI access to the gateway (unencrypted). |
| 443 | TCP | HTTPS | Secure WebUI access to the gateway (encrypted). |
| 1883 | TCP | MQTT | MQTT transport, used for data exchange between the gateway and the LNS or external application platforms. |
| 8080 | TCP | HTTP | ChirpStack or internal service API/management interface, commonly used for backend integration or testing purposes. |
NOTE
- By default, port
8080is not enabled on all gateways. Currently, it is only available on RAK7437. - If you need to manage gateway ports, you can use the RAK Open/Close Port Extension.
For details, refer to the Open/Close Port documentation:
