AN-25100108 Gateway userguide

Gateway Connection

Connecting to the Gateway's Wi-Fi via PC

1. Power on the gateway,Once the gateway is operating normally, the Wi-Fi will automatically turn on. The Wi-Fi defaults to AP mode, allowing users to connect via the Wi-Fi AP to view information or configure the gateway.
2. The gateway's Wi-Fi name is the gateway's DevEUI (obtained from the label on the side or back of the gateway), such as: "GDO518_b100000000000129". The default Wi-Fi password is: "wifi!0804". (See figure below)

3. The gateway's default configuration sets the static IP address of the RJ45 interface to 192.138.1.1/24. When unable to connect to the gateway through other methods, you can use an Ethernet cable to directly connect the gateway's RJ45 interface to the PC's RJ45 interface. Configure the PC's network card address to 192.138.1.2, subnet mask to 255.255.255.0, and default gateway to 192.138.1.1. Then, you can access the gateway via 192.138.1.1 using the Ethernet cable.

Logging into WebConfigure

1. Access the following address through a browser: [gateway's IP address] for example: 192.158.1.1
2. The default login password is: wifi!0804

3. If the page displays "Welcome to Your WebConfigure," the login is successful.

Modifying the WebConfigure Login Password

1. It is recommended to change the default password after successful login.
2. In Profile -> new password, enter the new password and click Submit.
3. Use the new password for subsequent logins.

Overview of Configuration Functions

Primary Menu		Secondary Menu	Function Description
State	Real-time operation status, data status	Statistics	Basic gateway operation information: Basic Info LoRa Status Heartbeat Info Server Connection Status
Network configuration	Network interface parameter configuration	WIFI	Wi-Fi Enable/Disable Wi-Fi AP SSID Wi-Fi Password NAT function for Wi-Fi interface
		Local network configuration	Related parameters for the RJ45 interface: DHCP, IP address, Default Gateway, etc. NetCheck: Periodically checks network connectivity.
		LTE	Enable bit, APN, Status view
		Net interfaces	IP addresses of network interfaces
		OpenVPN	OpenVPN related parameter configuration
Gateway configuration	Gateway parameter configuration	LoRaWAN Server	NS1 Configuration NS2 Configuration NMS Configuration
		Basic information	Basic information of the gateway
		System Time Config	NTP server, Time zone configuration
		Frequency Configuration	LoRa operating frequencies Heartbeat period Beacon parameters
		Professional Configuration	Advanced parameter configuration
		Back Up && Restore	Parameter backup and restoration
Other service	Start/Stop management for other internal gateway services	Npc ThinkOne NS bridge TKL	Npc: Used to enable reverse port mapping, requires NPS server support. ThinkOne: LoRaWAN NS Server. NS bridge: Can forward LoRa data to a second LoRaWAN NS. TKL: Built-in ThinkLink function.
Log	View logs	Run Log	Used to query partial gateway logs
Upgrade	Upgrade	Upgrade package	Upgrade gateway firmware.

State

Statistics

Displays the real-time gateway operation status and data status.

Basic information

Gateway model, hardware version, firmware version, GPS location, CPU and memory usage.

LoRa information

Statistics for LoRa data.

Heartbeat

Updates the gateway's network status and LoRa board status via the gateway heartbeat.

Profession

View more detailed status information.

Network configuration

WIFI

The Wi-Fi AP function and Wi-Fi BH function are mutually exclusive; only one can be selected at a time.

wifiAP

The gateway uses the Wi-Fi AP function by default when in AP mode. When Wi-Fi AP is enabled, it supports device configuration via Wi-Fi connection.

wifiBH

Select this function when using Wi-Fi as the gateway's uplink channel. After enabling, you can view surrounding Wi-Fi SSIDs by clicking the SSID dropdown box. Enter the wifiPassword and click Submit to connect to that Wi-Fi AP.

Note: Before connecting to a Wi-Fi router via Wi-Fi BH, ensure you can obtain the gateway's IP address through other means.

You can configure a static IP address via the RJ45 interface and connect to a PC via an Ethernet cable to access the gateway. Otherwise, if the gateway cannot obtain a new IP address after connecting to the Wi-Fi router, it may become unreachable.

wifieth

Configure the Wi-Fi MAC address and static IP address.

Note: Please keep the default configuration unchanged. This configuration parameter is used in special scenarios.

Local network configuration

mteth

Configure parameters related to the RJ45 network card.

enable: Enable/Disable

macAddr: Hardware address of the network card

DHCP: Enable to obtain IP address via DHCP

IP: Set static IP address

DNS: DNS server

netCheck

Configure the network watchdog function. When enabled, the gateway will monitor the connectivity status with the server address and the LoRaWAN NS address in real-time. If a network disconnection is detected, the gateway will select the network status according to the order configured in netSelect. When the netCheck function is disabled, the gateway automatically selects a connectable network interface.

enable: Network watchdog function, Enable/Disable

mode: Enter "ping"

server: Enter the NServer IP address or domain name. When the network checker is enabled, the watchdog program will check the connectivity of this address in real-time using "ping". If the connection fails, it will attempt to confirm network connectivity by pinging the LoRaWAN NS as a backup. If both addresses are unreachable, it determines that the gateway is disconnected from the network and attempts to switch the gateway's network connection method. If the gateway operates within a local area network (LAN) and cannot connect to the internet, this field must be filled with a LAN server address. Otherwise, the checker program may incorrectly judge the gateway to be continuously disconnected, leading to repeated switching of connection methods and periodic reboots, preventing the gateway from working normally.

switchTime: default as 3600 seconds. The waiting time before the network watchdog switches the connection method after judging a network disconnection. No modification is required; keep the default value.

rebootTime: default as 86400 seconds. The waiting time before the network watchdog reboots the gateway device if switching the connection method still fails to restore network connectivity after a disconnection. No modification is required; keep the default value.

netSelect

When netCheck is enabled and a network disconnection occurs, the gateway will sequentially search for a connectable network card according to the configured network order.

LTE

Parameter/Status	Type/Range	Description
Basic Parameters
APN	String	Normally no configuration is needed. If modification is required, enter the corresponding APN in the input field.
invalid	Boolean	false may indicate no 4G module detected or no SIM card found.
lteCCID	String	SIM card's CCID number. If empty, no SIM card is installed.
lteIMEI	String	Unique identifier of the 4G module.
lteRssi	Integer (dBm)	Signal strength (in dBm). Smaller negative values indicate weaker signals (e.g., -70dBm is better than -90dBm).
Registration Status
lteReg	0	Not registered: Device did not find any network or initiate registration.
	1	Registered (home network) : Successfully registered to the SIM's carrier.
	2	Not registered, searching: Actively scanning for available networks.
	3	Registration denied: Possible reasons include invalid SIM, unpaid balance, or network restrictions.
	4	Unknown: Typically indicates out-of-coverage areas.
	5	Registered (roaming) : Connected to a non-home carrier (may incur additional charges).

Net Interfaces

MAC addresses and IP addresses of different network cards.

eth*/usb*: LTE network card information

mteth0: RJ45 interface network card information

wlan0: Wi-Fi network card information

OpenVPN

Configure parameters related to the OpenVPN client. Certificate files must be obtained from the OpenVPN server provider.

Gateway configuration

LoRaWAN Server

NS1

nsLocal

When enabled, the gateway points to the internal NS server (i.e., uses the built-in NS), and the address configuration for other NS servers becomes invalid.

NS Server Information Configuration

nsProtocol: Communication protocol between the gateway and the LoRaWAN server.

1) "mqtt_mt": ManThink's MQTT-based gateway protocol, can only connect to ManThink's ThinkLink server.

nsBroker: tcp://thinklink.manthink.cn:1883

nsUsername: tkbroker

nsPassword: The password is not displayed here. The correct password must be entered when modifying it. If the input is empty and you click Submit, the parameter will not be modified.

Keep the certificate field empty.

2) "pkt_fwd": Generic Semtech UDP protocol.

nsAddress: Enter the NServer's IP address (or domain name). The default ManThink domain name is

thinklink.manthink.cn.

nsPort_up: Enter the ChirpStack uplink port number (ChirpStack or TTN usually defaults to 1700; ManThink defaults to 1770).

nsPort_down: Enter the ChirpStack downlink port number (ChirpStack or TTN usually defaults to 1700; ManThink defaults to 1770).

3) "mqtt_chirpstack": Connects to the ChirpStack server's MQTT interface.

sever: tcp://192.168.1.141:11883

Username: gateway

Password: The password is not displayed here. The correct password must be entered when modifying it. If the input is empty and you click Submit, the parameter will not be modified.

topic_prefix: Topic prefix. Can be used to define the gateway's region.

ca_cert: ChirpStack's CA certificate.

tls_cert: Public key file.

tls_key: Private key file.

4) "basicstation_lns": Connects to a server using the Basic Station standard LNS protocol.

uri: LNS server address

trust: LNS server's CA certificate

cert: LNS public key file

key: LNS private key file

Specific operations for basicstation_lns connecting to ChirpStack can be found in the following link:

\GW-AN08 Connection to ChirpStack Basic Station LNS Protocol (with TLS) Guide

Specific operations for basicstation_lns connecting to TTN can be found in the following link:

\GW-AN09 connect TTN by basicstation

5) "basicstation_cups": Connects to a server using the Basic Station standard CUPS protocol.

uri: CUPS server address

trust: CUPS server's CA certificate

cert: CUPS public key file

key: CUPS private key file

NS2 Configuration

The NS2 configuration is effective for 16-frequencies LoRaWAN gateways. A 16-frequencies gateway supports two LoRa board (PMC modules) , with each PMC module supporting 8 frequencies, allowing the dual-PMC configuration to support 16 concurrent channels.

1. Hardware Correspondence: The gateway's 16-frequencies capability is achieved through dual PMC modules. NS and NS2 in the configuration file correspond to the configurations of the two PMC modules, respectively.
2. Frequency Allocation: By default, the two PMC modules use two different groups of 8 frequencies (16 frequencies total). If the two PMC modules need to use the same 8 frequencies (for redundancy or special testing), the corresponding frequency configuration must be set in the gateway's LoRa configuration.
3. Single Gateway Logic: To report the 16 frequencies as a single logical entity (single Gateway EUI), the gweui and nsProtocol fields in the NS2 configuration must be set to an empty string "", so that it inherits the NS configuration.
4. Dual Gateway Logic: To divide the 16 frequencies into two logical gateways (two Gateway EUIs) for reporting, a different gweui must be configured for NS2, along with its independent connection parameters (nsProtocol, nsAddress, etc.) as needed.
5. Protocol Selection: nsProtocol supports pkt_fwd (traditional UDP protocol) and mqtt_mt (MQTT-based protocol). In a dual-Network Server scenario, the two PMC modules can use different protocols.

Core Configuration Scenarios

Based on business requirements, the 16-frequencies gateway can be flexibly configured into the following three main scenarios:

Scenario ID	Channel Group Allocation	Gateway EUI (gweui) Allocation	NS Connection	Applicable Scenario
1.1	Two PMC modules use different 8-frequencies	Single Gateway EUI	Single NS Server	Most common 16-frequencies configuration; all data aggregates to the same platform.
1.2	Two PMC modules use different 8-channel groups	Two independent Gateway EUIs	Single NS Server	Requires managing the 16 frequencies as two logically independent gateways on the same Network Server.
1.3	Two PMC modules use same 8-frequencies groups	Two independent Gateway EUIs	Two independent NS Servers	Two independent LoRa networks, mutually non-interfering, but sharing one gateway hardware.

The following provides detailed configuration steps and key parameter descriptions for different scenarios. The configuration protocols use the common pkt_fwd and mqtt_mt as examples.

Scenario 1.1: Single Gateway EUI, Single Network Server (Recommended)

This is the most common 16-frequencies configuration, where the two PMC modules (16 frequencies) act as one logical gateway connected to the same Network Server.

Configuration Goal:

• NS (PMC 1) and NS2 (PMC 2) connect to the same Network Server.
• NS uses the gateway's default EUI.
• NS2's gweui is left empty, so it automatically inherits the NS's Gateway EUI.

Configuration Item	NS (PMC 1)	NS2 (PMC 2)	Description
gweui	Gateway EUI value (e.g., b100000000000118)	Empty	Leaving NS2 empty inherits the NS EUI, implementing single-gateway logic.
nsProtocol	pkt_fwd or mqtt_mt	Empty	Leaving NS2 empty inherits the NS protocol and connection information.
nsAddress	Network Server Address	Inherits from NS	Ensures data from both PMC modules is sent to the same server.
nsPort_up	Uplink Port	Inherits from NS	-
nsPort_down	Downlink Port	Inherits from NS	-

Scenario 1.2: Dual Gateway EUI, Single NS Server

In this scenario, the two PMC modules (16 frequencies) are treated as two independent gateways, but their data is reported to the same Network Server. Applicable for scenarios requiring logical isolation or testing dual-gateway functionality.

Configuration Goal:

• NS (PMC 1) and NS2 (PMC 2) connect to the same Network Server.
• NS and NS2 are configured with different gweuis.
• NS2's nsProtocol is left empty, so it inherits the NS's connection information.

Configuration Item	NS (PMC 1)	NS2 (PMC 2)	Description
gweui	Gateway EUI value A (e.g., b100000000000118)	Gateway EUI value B (e.g., b100000000000228)	Two different EUIs must be configured.
nsProtocol	pkt_fwd or mqtt_mt	Empty	Leaving NS2 empty inherits the NS protocol and connection information.
nsAddress	NS Server Address	Inherits from NS	Ensures data from both logical gateways is sent to the same server.

Scenario 1.3: Dual Gateway EUI, Dual Network Servers

In this scenario, the two PMC modules (16 frequencies) are treated as two independent gateways, each connecting to a separate Network Server. Applicable for scenarios requiring data from different channel groups to be routed to different platforms for processing.

Configuration Goal:

• NS (PMC 1) and NS2 (PMC 2) are configured with different gweuis.
• NS and NS2 are configured with different nsAddress and nsProtocol.

Configuration Item	NS (PMC 1)	NS2 (PMC 2)	Description
gweui	Gateway EUI value A (e.g., b100000000000118)	Gateway EUI value B (e.g., b100000000000228)	Two different EUIs must be configured.
nsProtocol	pkt_fwd or mqtt_mt	pkt_fwd or mqtt_mt	The protocols for the two PMC modules can be the same or different.
nsAddress	NS Server A Address	NS Server B Address	Two different NS Server addresses must be configured.

NMS Configuration

NMS (Network Management System) is the gateway's operation and maintenance server. It defaults to connecting to ThinkLink at tcp://thinklink.manthink.cn:1884. It is used for maintenance and management of the gateway via ThinkLink. The default ThinkLink address is

https://thinklink.manthink.cn.

nmsLocal

When enabled, the gateway connects directly to the internal broker, which is used when the built-in TKL is required for gateway maintenance and management.

NMS Broker

Configuration information for the NMS broker.

Basic Information

Basic information of the gateway. It usually does not need to be modified. In special cases, tenant and loraStandard need to be manually modified. Other information can be viewed but not modified.

When using local TKL and needing to maintain data consistency with the cloud-based ThinkLink, you need to manually modify the tenant to the cloud organization account.

System Time Config

You can configure the NTP server and time zone the gateway connects to. The NTP server is used for real-time time updates. If the gateway connects to a locally deployed independent server, the NTP server must be configured to the local NTP server.

Frequency Configuration

The gateway's frequency parameters are configured here.

Uplink Session Validation Duration:

keepalive_interval: Sets the interval (in seconds) for the gateway to send keep-alive messages to the Network Server. Default is 5s.

Stat_interval: Sets the interval (in seconds) for the gateway to send status (stat) messages to the Network Server. Default is 60s.

Beacon Configuration:

Beacon information needs to be modified according to different regional standards.

beaconBW: Beacon signal bandwidth. Default 500000 is 500kHZ bandwidth.

beaconFreq: Beacon signal frequency. Default 923300000 is 923.3MHZ frequency.

beaconSF: Beacon signal spreading factor. Default is 10.

beaconStep: Beacon signal frequency step.

beaconDatarate: Beacon transmission rate.

beaconPower: Beacon transmission power.

beaconInfodesc: Description of beacon information.

beaconFreqNb: Number of beacon frequencies.

Frequency Configuration:

Auto Fill Length: The number of channels supported by the gateway. Default is 8 under standard gateway configuration.

Step: The interval width between adjacent channels. Generally 0.2MHz.

Professional Configuration

This function carries a certain risk. Improper operation may cause the gateway to malfunction. It is recommended to contact ManThink technical support directly if this function is needed.

Back Up && Restore

Backup and restore configuration files.

Other Service

Npc

NPC is used to establish an SSH port mapping, primarily for system maintenance during abnormal situations. Establishing a connection requires cooperation from the server side (NPS). If you require the ManThink NPS server, please contact ManThink technical support to obtain the Server, vkey, and type information.

ThinkOne

ThinkOne is ManThink's LoRaWAN NS server. This menu provides instructions for configuring the internal NS of the gateway.

enable: Whether to enable the built-in NS service.

downEnable: Whether to allow the NS to support downlink control. This is used to allow only one NS to support downlink data when multiple NSs are running in parallel.

leafEnable: The leaf mode of the NS. In leaf mode, the NS pulls triple-element information from the Root NS as needed. The Root NS broker information needs to be configured in this menu.

rootEnable: Whether to enable rootEnable. The built-in NS does not support enabling root mode.

sigAutoDisable: Whether to allow automatic detection of DevEUI. Default is true.

generateEnable: Keep the default configuration.

AS Broker

Broker configuration for forwarding to the AS server. Defaults to forwarding to the internal Broker for TKL reception and processing.

AS2 Broker

The built-in NS support for sending to two MQTT Brokers. AS2 Broker is the configuration for forwarding to the second AS server. If the Broker address of AS is empty, no forwarding is performed. AS2 Broker does not support downlink data.

NS Root Broker

Broker parameters for the Root Broker, used to obtain key information on demand in leaf mode.

NS bridge

1. Target NS Broker
   • Description: The Broker configuration for forwarding data to the target Network Server (NS).
   • Requirement: Ensure correct Broker configuration details are entered.
2. Target NMS Broker
   • Description: Used for forwarding gateway management data.
3. Source NS Broker
   • Description: The Broker configuration for LoRa source data.
   • Requirement: Keep the default parameters unchanged.

Supported Protocol:\nThis feature only supports the mqtt_mt protocol format.

TKL

ThinkLink configuration item. Can be enabled or disabled. When enabled, it can be accessed via port 10100 at [ip]:10100.

For example, it can be accessed via http://gateway-b100000000000129.local:10100 or

http://192.158.1.1:10100.

Log: View Logs

Used to browse and query partial logs during gateway operation.

Run Log

Upgrade: Gateway Upgrade Function

Upgrade package

When the gateway needs an upgrade, first obtain the upgrade package from ManThink, and then import the upgrade via this interface.

If you have any questions, please contact ManThink technical support.

Click Upload package to upload the upgrade package, and click Submit after a successful upload.