X300 Series IoT Cellular Gateway
User Guide

Part Number PMD-00153
Revision C October 2023

Intellectual Property© 2023 Lantronix, Inc. All rights reserved. No part of the contents of this publication may betransmitted or reproduced in any form or by any means without the written permission of Lantronix.
Lantronix is a registered trademark of Lantronix, Inc. in the United States and other countries.
Patented: www.lantronix.com/legal/patents/. Additional patents pending.
Windows and Internet Explorer are registered trademarks of Microsoft Corporation. Firefox is a
registered trademark of the Mozilla Foundation. Chrome is a trademark of Google Inc. All othertrademarks and trade names are the property of their respective holders.

Warranty
For details on the Lantronix warranty policy, please go to our web site atwww.lantronix.com/technical-support/warranty/

Contacts
Lantronix, Inc.
48 Discovery, Suite 250
Irvine, CA 92618, USA
Toll Free:800-526-8766
Phone: 949-453-3990
Fax: 949-453-3995
Technical Support
Online: www.lantronix.com/technical-support/
Sales Offices
For a current list of our domestic and international sales offices, go to the Lantronix web site atwww.lantronix.com/about-us/contact/

Disclaimer
All information contained herein is provided “AS IS.” Lantronix undertakes no obligation to update
the information in this publication. Lantronix does not make, and specifically disclaims, allwarranties of any kind (express, implied or otherwise) regarding title, non-infringement, fitness,quality, accuracy, completeness, usefulness, suitability or performance of the information provided
herein. Lantronix shall have no liability whatsoever to any user for any damages, losses andcauses of action (whether in contract or in tort or otherwise) in connection with the user’s access or
usage of any of the information or content contained herein. The information and specifications
contained in this document are subject to change without notice.

X300 Series IoT Cellular Gateway User Guide

2

Revision History
Date

Rev.

Comments

July 2022

A

Initial document

January 2023

B

Updated for firmware version 1.9.0.0R26.
 Updated quick setup and status based on UI enhancements.
 Added X300 and updated X304 model descriptions.
 Updated package contents.

 Updated ConsoleFlow client configuration options.
 Added country code selection for Wi-Fi operation.

October 2023

C

Updated for firmware version 2.0.0.0.
 Updated quick setup and status based on UI enhancements.
 Added custom APN to cellular interface configuration.
 Added WireGuard VPN configuration.

 Added password prompt for backup and flash firmware.
 Added firmware upgrade from SD card/USB device.

 Added restoring installed IPKs after firmware upgrade.
 Updated router password requirements.

 Added support for default WLAN profile.

Updated for firmware version 2.1.0.0
 Renamed ConsoleFlow client to Percepxion and updated

configuration options for audit log and send dynamic update.

 Added support for switching between embedded andexternal SIMs.

 Added Running Commands details.

For the latest revision of this product document, please check our online documentation atwww.lantronix.com/support/documentation.

X300 Series IoT Cellular Gateway User Guide

3

Contents
1: About this Guide

16

Purpose _________________________________________________________________ 16
Summary of Chapters ______________________________________________________ 16
Additional Documentation ___________________________________________________ 18

2: Introduction

19

Key Features _____________________________________________________________ 19
InfiniShield™ Security __________________________________________________ 19
Software Features _____________________________________________________ 19
Lantronix Software Services ______________________________________________ 20
Applications ______________________________________________________________ 20
SKU Information __________________________________________________________ 20
Hardware Components _____________________________________________________ 22
General Specification ___________________________________________________ 22
Front Panel ___________________________________________________________ 23
Back Panel ___________________________________________________________ 25
LEDs ________________________________________________________________ 26
Cellular ______________________________________________________________ 27
SIM Slot _____________________________________________________________ 28
Antenna Connections ___________________________________________________ 28
Certified Antennas _____________________________________________________ 28
Ethernet Port (LAN) ____________________________________________________ 29
Serial Port ____________________________________________________________ 30
Power Input __________________________________________________________ 31
Power Consumption ____________________________________________________ 31
Reset Button __________________________________________________________ 31
Product Label _________________________________________________________ 32

3: Installation

33

Package Contents _________________________________________________________ 33
User Supplied Items _______________________________________________________ 33
Accessories ______________________________________________________________ 34
Preparing to Install ________________________________________________________ 35
Enabling DHCP Client on Your Computer ___________________________________ 35
SIM Card Management _____________________________________________________ 35
Physical Installation ________________________________________________________ 36
Insert SIM Card _______________________________________________________ 36
Connect the Antennas __________________________________________________ 38
Connect the AC Power __________________________________________________ 38
Connect the Gateway to a Computer _______________________________________ 39

X300 Series IoT Cellular Gateway User Guide

4

Default Configuration ______________________________________________________ 41
Web Admin Page ______________________________________________________ 41
Wireless Access Point SSID ______________________________________________ 41
Default Interface Configuration ____________________________________________ 41

4: Web Administration Interface

42

Logging In _______________________________________________________________ 43
Change Passwords After Initial Login _______________________________________ 44
Logging Out ______________________________________________________________ 45

5: Using Lantronix Provisioning Manager

46

Installing Lantronix Provisioning Manager ______________________________________ 46
Accessing the Gateway Using Lantronix Provisioning Manager ______________________ 46

6: Quick Setup

47

Quick Setup ______________________________________________________________ 47

7: Status

49

Overview (Page) __________________________________________________________ 49
System Status ________________________________________________________ 49
Percepxion Status _____________________________________________________ 50
Memory Status ________________________________________________________ 51
MWAN Interfaces Status ________________________________________________ 51
Firewall Status ____________________________________________________________ 51
Network Status ___________________________________________________________ 52
Cellular Status ________________________________________________________ 53
Network Status ________________________________________________________ 54
Active DHCP and DHCPv6 Leases Status ___________________________________ 54
Wireless Status ________________________________________________________ 55
Dynamic DNS Status ___________________________________________________ 55
Routes __________________________________________________________________ 56
System Log ______________________________________________________________ 57
Kernel Log _______________________________________________________________ 57
Processes _______________________________________________________________ 57
Realtime Graphs __________________________________________________________ 58
Load ________________________________________________________________ 58
Traffic _______________________________________________________________ 59
Wireless _____________________________________________________________ 59
Connection ___________________________________________________________ 60
WireGuard Status _________________________________________________________ 61
Load Balancing ___________________________________________________________ 62
Interface _____________________________________________________________ 62

X300 Series IoT Cellular Gateway User Guide

5

Detail _______________________________________________________________ 62
Diagnostics ___________________________________________________________ 62
Troubleshooting _______________________________________________________ 62

8: System

63

System _________________________________________________________________ 63
General Settings _______________________________________________________ 63
Logging ______________________________________________________________ 64
Time Synchronization ___________________________________________________ 65
Language and Style ____________________________________________________ 66
Administration ____________________________________________________________ 66
Router Password ______________________________________________________ 66
SSH Access __________________________________________________________ 67
SSH-Keys ____________________________________________________________ 67
Software ________________________________________________________________ 68
List the Packages ______________________________________________________ 69
Update the List of Packages ______________________________________________ 69
Install a Package ______________________________________________________ 69
Upgrade a Package ____________________________________________________ 70
Remove a Package ____________________________________________________ 71
Configure OPKG _______________________________________________________ 71
Startup __________________________________________________________________ 72
Initscripts ____________________________________________________________ 72
Local Startup _________________________________________________________ 73
Scheduled Tasks __________________________________________________________ 73
LED Configuration _________________________________________________________ 74
Backup / Flash Firmware ___________________________________________________ 75
Backup and Restore ____________________________________________________ 76
Reset to Defaults ______________________________________________________ 77
Firmware Upgrade _____________________________________________________ 78
Configuration _________________________________________________________ 79
Firmware and Configuration Upgrade from SD Card / USB Device ________________ 79
Custom Commands _______________________________________________________ 80
Write Custom Shell Command ____________________________________________ 80
Run Custom Shell Command _____________________________________________ 80
Reboot __________________________________________________________________ 81
Schedule a Reboot _____________________________________________________ 81

9: VPN82

IPsec (Internet Protocol Security) _____________________________________________ 82
OpenVPN _______________________________________________________________ 86
OpenVPN Instances ____________________________________________________ 86
Template-based Configuration ____________________________________________ 88

X300 Series IoT Cellular Gateway User Guide

6

OpenVPN Configuration File _____________________________________________ 88
WireGuard VPN __________________________________________________________ 89
Install WireGuard IPKs to the Device _______________________________________ 89
Generate Private and Public Keys for WireGuard _____________________________ 89
Create the WireGuard VPN Interface _______________________________________ 90
Configure a Firewall Rule to Allow WireGuard Traffic __________________________90
Monitor Status ________________________________________________________ 91
Create a WireGuard Interface on the Peer Device _____________________________ 91

10: Services

92

Agents __________________________________________________________________ 92
DOTA __________________________________________________________________ 93
Lantronix Server _______________________________________________________ 93
Custom Server ________________________________________________________ 93
Dynamic DNS ____________________________________________________________ 95
External Filesystems _______________________________________________________ 98
GPS ____________________________________________________________________99
Description of NMEA Messages __________________________________________ 100
GPGGA Format ______________________________________________________ 101
GPRMC Format ______________________________________________________ 102
GPGSV Format ______________________________________________________ 103
GPGSA Format ______________________________________________________ 104
GPVTG Format _______________________________________________________ 105
Keepalived _____________________________________________________________ 107
Keepalived Configuration _______________________________________________ 107
Logs Information _________________________________________________________ 110
Page Selector ___________________________________________________________ 110
Reporting Agent _________________________________________________________ 111
Sending Data ________________________________________________________ 112
Data Format _________________________________________________________ 113
Service Actions __________________________________________________________ 113
SMS __________________________________________________________________ 114
SMS Configuration ____________________________________________________ 114
SMS AT Commands ___________________________________________________ 114
Ethernet SMS ________________________________________________________ 117
Live Message ________________________________________________________ 118
SNMPD ________________________________________________________________ 119
SNMP Architecture ____________________________________________________ 119
SNMP Versions ______________________________________________________ 119
SNMP Configuration ___________________________________________________ 120
SNMPTRAPD ___________________________________________________________ 129
SNMP-TRAP Configuration _____________________________________________ 129
uHTTPd ________________________________________________________________ 132

X300 Series IoT Cellular Gateway User Guide

7

Web Server Configuration ______________________________________________132

11: Network

135

Interfaces ______________________________________________________________ 135
Interfaces Overview ___________________________________________________ 135
Interface Status ______________________________________________________ 137
Interface Protocols ____________________________________________________ 138
Protocol Descriptions __________________________________________________ 139
CELLULAR Interface __________________________________________________ 150
LAN Interface ________________________________________________________ 151
WWAN and WWAN6 Interface ___________________________________________ 153
Add Virtual Interface ___________________________________________________ 154
Wireless _______________________________________________________________ 158
Wireless Network Configuration __________________________________________ 159
Default Wireless Client Profile ___________________________________________ 162
DHCP and DNS _________________________________________________________ 163
General Settings ______________________________________________________ 163
Resolv and Host Files __________________________________________________ 164
TFTP Settings ________________________________________________________ 164
Advanced Settings ____________________________________________________ 165
Static Leases ________________________________________________________ 166
Hostnames _____________________________________________________________ 167
Static Routes ____________________________________________________________ 167
Static IPv4 Routes ____________________________________________________ 167
Static IPv6 Routes ____________________________________________________ 168
Diagnostics _____________________________________________________________ 170
Firewall ________________________________________________________________ 171
General Settings ______________________________________________________ 171
Port Forwards ________________________________________________________ 174
Traffic Rules _________________________________________________________ 175
Custom Rules ________________________________________________________ 177
QoS ___________________________________________________________________178
Load Balancing __________________________________________________________ 180
How it works _________________________________________________________ 180
Globals _____________________________________________________________ 180
Interfaces ___________________________________________________________ 181
Members ____________________________________________________________ 183
Policies _____________________________________________________________ 184
Rules ______________________________________________________________ 186
Notification __________________________________________________________ 187

12: Bluetooth

188

Bluetooth Settings ________________________________________________________ 188

X300 Series IoT Cellular Gateway User Guide8

Configure Bluetooth settings ____________________________________________ 188
Scan for and Pair a Device ______________________________________________188
Bluetooth SPP ___________________________________________________________ 189
Configure Bluetooth SPP Connection _____________________________________ 190
Configure Tunnel SPP Slave ____________________________________________ 190
Configure Tunnel SPP Master ___________________________________________ 190

13: Percepxion

192

Client __________________________________________________________________ 192
Percepxion Line _________________________________________________________ 193

14: Discovery

195

Query Port ______________________________________________________________ 195

15: Serial

196

Serial Line Statistics ______________________________________________________ 196
Serial Line Configuration ___________________________________________________ 196

16: SSL198

Credentials _____________________________________________________________ 198
Trusted Authorities _______________________________________________________ 199

17: Tunnel

201

Tunnel Statistics _________________________________________________________ 201
Tunnel Modbus RTU to Modbus TCP _________________________________________ 201
Tunnel Accept ___________________________________________________________ 202
Tunnel Connect __________________________________________________________ 205
Hosts ______________________________________________________________ 206
Connecting Multiple Hosts ______________________________________________207
Tunnel Disconnect _______________________________________________________ 208

A: Compliance Information

209

FCC Statement __________________________________________________________ 210
Federal Communication Commission Interference Statement ___________________ 210
ISED Statement _________________________________________________________ 211
EU Declaration of Conformity _______________________________________________ 212
EU Statements __________________________________________________________ 215
RF Output Power of X303F202S ____________________________________________ 221
RF Output Power of X304G002S ____________________________________________ 222

B: Power Cable Schematic

X300 Series IoT Cellular Gateway User Guide

223

9

Power Cable Schematic ___________________________________________________ 223

C: List of Acronyms and Protocols

224

D: Running Commands

227

Types of Commands ______________________________________________________ 227
Bash Commands _________________________________________________________ 227
Bash Command Examples ______________________________________________228
opkg Commands _________________________________________________________ 230
UCI Commands __________________________________________________________ 231

D: Lantronix Technical Support

X300 Series IoT Cellular Gateway User Guide

232

10

List of Figures
Figure 2-1 X300 model Front View __________________________________________________ 23
Figure 2-2 X303 model Front View __________________________________________________ 24
Figure 2-3 X304 model Front View __________________________________________________ 24
Figure 2-4 X300 model Back View ___________________________________________________ 25
Figure 2-5 X303 model Back View __________________________________________________ 25
Figure 2-6 X304 model Back View ___________________________________________________ 26
Figure 2-7 Ethernet Port ___________________________________________________________ 29
Figure 2-8 RJ45 Connector RS-232 / RS- 485 Interface __________________________________ 30
Figure 2-9 DC Input Interface _______________________________________________________ 31
Figure 2-10 Sample Product Label __________________________________________________ 32
Figure 4-1 Web Admin Interface ____________________________________________________ 42
Figure 4-2 Web Admin Login Page __________________________________________________ 44
Figure 7-1 IPv4 Firewall Status _____________________________________________________ 52
Figure 7-2 Realtime CPU Load Graph ________________________________________________ 58
Figure 7-3 Realtime Network Traffic Graph (eth1) _______________________________________ 59
Figure 7-4 Realtime Wireless Usage Graph (client) ______________________________________ 60
Figure 7-5 Realtime Connection Traffic Graph _________________________________________ 61
Figure 10-1 Reporting Agent Data Format (excerpt) ____________________________________ 113
Figure 10-2 Service Actions _______________________________________________________ 113
Figure 10-3 VACM Configuration Model _____________________________________________ 121
Figure 11-1 Interfaces Overview (partial view) _________________________________________ 136
Figure 11-2 WAN Interface Status __________________________________________________ 137
Figure 11-3 LAN Interface (Static Address) Configuration ________________________________ 152
Figure 11-4 WWAN Interface (DHCP client) Configuration _______________________________ 154
Figure 11-5 Network Add New Interface _____________________________________________ 155
Figure 11-6 Wireless Overview ____________________________________________________ 158
Figure A-1 X300 / X303 EU Declaration of Conformity __________________________________ 212
Figure A-2 X304 EU Declaration of Conformity ________________________________________ 213
Figure A-3 X304 UKCA Declaration of Conformity _____________________________________ 214
Figure B-1 3-pin Power Cable _____________________________________________________ 223

X300 Series IoT Cellular Gateway User Guide

11

List of Tables
Table 2-1 X300 Series Models ______________________________________________________ 20
Table 2-2 General Specification _____________________________________________________ 22
Table 2-3 Top Panel LEDs _________________________________________________________ 26
Table 2-4 X300 model Top Panel LEDs _______________________________________________27
Table 2-5 X303 / X304 Cellular Data Rates ____________________________________________ 27
Table 2-6 X303 / X304 Cellular Bands ________________________________________________ 27
Table 2-7 Certified Antennas _______________________________________________________ 28
Table 2-8 Ethernet RJ45 Connector Pin Assignment and LEDs ____________________________ 29
Table 2-9 Serial RJ45 Connector Pin Assignment and LEDs ______________________________ 30
Table 2-10 X300 Series Power Consumption __________________________________________ 31
Table 3-1 Lantronix Accessories ____________________________________________________ 34
Table 3-2 Default Web Admin Page Credentials ________________________________________ 41
Table 3-3 Default Wireless Access Point SSID _________________________________________ 41
Table 3-4 Default Network Interface Configuration ______________________________________ 41
Table 6-1 Quick Setup Network Configuration __________________________________________ 47
Table 7-1 System Status Overview __________________________________________________ 49
Table 7-2 System Status Overview __________________________________________________ 50
Table 7-3 Memory Status Overview __________________________________________________ 51
Table 7-4 Firewall Status __________________________________________________________ 52
Table 7-5 Cellular Status Overview __________________________________________________ 53
Table 7-6 Network Status Overview __________________________________________________ 54
Table 7-7 Active DHCP Leases Status Overview _______________________________________ 54
Table 7-8 Wireless Status Overview _________________________________________________ 55
Table 7-9 Routes Status __________________________________________________________ 56
Table 7-10 Processes Status _______________________________________________________ 57
Table 8-1 System General Settings __________________________________________________ 63
Table 8-2 Syslog Configuration _____________________________________________________ 64
Table 8-3 System Time Synchronization Configuration ___________________________________ 65
Table 8-4 Language and Style Configurations __________________________________________ 66
Table 8-5 SSH Access Configuration _________________________________________________ 67
Table 8-6 Software Page __________________________________________________________ 68
Table 8-7 OPKG Package Manager Configuration ______________________________________ 72
Table 8-8 Initscripts Actions ________________________________________________________ 72
Table 8-9 Cron Shortcuts _________________________________________________________ 73
Table 8-10 Trigger Descriptions _____________________________________________________ 74
Table 8-11 LED Configuration ______________________________________________________ 75

X300 Series IoT Cellular Gateway User Guide

12

Table 8-12 Backup and Restore / Flash Firmware Operations _____________________________ 76
Table 8-13 Custom Commands Configuration __________________________________________ 80
Table 8-14 Schedule Reboot Time Specification ________________________________________ 81
Table 9-1 IPsec General Settings ___________________________________________________ 82
Table 9-2 IPsec Advanced Settings __________________________________________________ 84
Table 10-1 Agent Configurations ____________________________________________________ 92
Table 10-2 DOTA using Lantronix Server _____________________________________________ 93
Table 10-3 DOTA Custom Server Configuration ________________________________________ 94
Table 10-4 Dynamic DNS Client Configuration _________________________________________ 95
Table 10-5 External Filesystems Configuration _________________________________________ 98
Table 10-6 GPS Service Configuration _______________________________________________99
Table 10-7 GGA Data Format _____________________________________________________ 101
Table 10-8 RMC Data Format _____________________________________________________ 102
Table 10-9 GPGSV Data Format ___________________________________________________ 103
Table 10-10 GSA Data Format ____________________________________________________ 104
Table 10-11 VTG Data Format _____________________________________________________ 105
Table 10-12 Keepalived Configuration _______________________________________________ 108
Table 10-13 Reporting Agent Configuration ___________________________________________ 111
Table 10-14 Reporting Agent Data Send Configuration __________________________________ 112
Table 10-15 SMS Service Configuration _____________________________________________ 114
Table 10-16 SMS AT Command Syntax _____________________________________________ 114
Table 10-17 Ethernet SMS Configuration ____________________________________________ 117
Table 10-18 SNMP Security Models and Levels _______________________________________ 120
Table 10-19 SNMP General Settings Configuration ____________________________________ 123
Table 10-20 SNMP v1/v2/USM VACM Settings ________________________________________ 125
Table 10-21 SNMP VACM Settings Engine ID Configuration _____________________________ 127
Table 10-22 SNMP VACM Settings SNMPv3-USM _____________________________________ 128
Table 10-23 SNMP Trap Settings Configuration _______________________________________ 128
Table 10-24 SNMP-Trap Receiver Configuration ______________________________________ 129
Table 10-25 uHTTPd Server Configuration ___________________________________________ 132
Table 10-26 uHTTPd Self-signed Certificate Configuration _______________________________ 134
Table 11-1 Network Interfaces Overview _____________________________________________ 136
Table 11-2 Wireless Overview and Associated Stations _________________________________ 137
Table 11-3 Network Interface Protocols ______________________________________________138
Table 11-4 Static Address Protocol Settings __________________________________________ 139
Table 11-5 DHCP Client Protocol Settings ___________________________________________ 141
Table 11-6 DHCPv6 Client Protocol Settings __________________________________________ 143
Table 11-7 PPPoE Protocol Settings ________________________________________________ 144

X300 Series IoT Cellular Gateway User Guide

13

Table 11-8 UMTS/GPRS/EV-DO Cellular Protocol Settings ______________________________ 145
Table 11-9 QMI Cellular Protocol Settings ____________________________________________ 147
Table 11-10 VPN Tunnel Protocols _________________________________________________ 155
Table 11-11 Wireless Overview and Associated Stations ________________________________ 158
Table 11-12 Wireless Device Configuration ___________________________________________ 159
Table 11-13 Wireless Interface Configuration _________________________________________ 160
Table 11-14 General Configuration of DHCP Server and DNS-Forwarder ___________________ 163
Table 11-15 Resolv and Host File Configuration for DHCP and DNS _______________________ 164
Table 11-16 TFTP Configuration for DHCP and DNS ___________________________________ 164
Table 11-17 Advanced Configuration for DHCP and DNS ________________________________ 165
Table 11-18 DHCP and DNS Static Leases ___________________________________________ 166
Table 11-19 Hostnames Configuration ______________________________________________167
Table 11-20 Static IPv4 Routes Configuration _________________________________________ 167
Table 11-21 Static IPv6 Routes Configuration _________________________________________ 168
Table 11-22 Diagnostics - Network Utilities ___________________________________________ 170
Table 11-23 Cable Diagnostics Status Messages ______________________________________ 170
Table 11-24 Firewall Global Settings ________________________________________________ 171
Table 11-25 Firewall Zones Configuration (LAN) _______________________________________ 173
Table 11-26 Firewall Port Forwards _________________________________________________ 174
Table 11-27 Port Forwarding Configuration for Firewall Zone _____________________________ 174
Table 11-28 Firewall Zone Traffic Rules _____________________________________________ 175
Table 11-29 Firewall Traffic Rule Configuration ________________________________________ 176
Table 11-30 QoS Configure Classes ________________________________________________ 178
Table 11-31 MWAN Globals Configuration ___________________________________________ 181
Table 11-32 MWAN Interface ______________________________________________________ 181
Table 11-33 MWAN Interface Configuration __________________________________________ 182
Table 11-34 MWAN Members _____________________________________________________ 183
Table 11-35 MWAN Members Configuration __________________________________________ 184
Table 11-36 MWAN Policy _______________________________________________________ 185
Table 11-37 MWAN Policy Configuration _____________________________________________ 185
Table 11-38 MWAN Rules ________________________________________________________ 186
Table 11-39 MWAN Rules Configuration _____________________________________________ 186
Table 12-1 Bluetooth Settings Configuration_________________________________________ 188

Table 12-2 Bluetooth Scan Results _________________________________________________ 189
Table 12-3 Bluetooth SPP Line Configuration _________________________________________ 190
Table 13-1 Percepxion Client Configuration __________________________________________ 192
Table 13-2 Percepxion Line _______________________________________________________ 194
Table 15-1 Serial Line Configuration ________________________________________________ 196

X300 Series IoT Cellular Gateway User Guide

14

Table 16-1 SSL Credentials - Upload Certificate _______________________________________ 198
Table 16-2 SSL Credentials - Create Self-Signed Certificate _____________________________ 199
Table 16-3 SSL Trusted Authority __________________________________________________ 200
Table 17-1 Tunnel for Modbus RTU to Modbus TCP ____________________________________ 201
Table 17-2 Tunnel Accept Mode Configuration ________________________________________ 202
Table 17-3 Tunnel Connect Mode Configuration _______________________________________ 205
Table 17-4 Host Configuration _____________________________________________________ 206
Table 17-5 Tunnel Disconnect Configuration __________________________________________ 208
Table A-1 Regional Certifications ___________________________________________________ 209
Table A-2 Country Transmitter IDs _________________________________________________ 209
Table A-3 EU Statements ________________________________________________________ 215

X300 Series IoT Cellular Gateway User Guide

15

1:

About this Guide

PurposeThis guide provides the information needed to install, configure, and use the Lantronix X300 series
IoT cellular gateways using the web interface. The X300 series gateways are designed for IoT
professionals for M2M and enterprise IoT applications requiring faultless connectivity.
The information in this document assumes the reader has knowledge of networking fundamentals
and routing concepts for data communication, control, and management functions.
For additional support and product resources, please visit the Lantronix Technical Support portal.

Summary of Chapters
The remaining chapters in this guide include:
Chapter

Description

Chapter 2: Introduction

Describes the main features of the product and theprotocols it supports.

Chapter 3: Installation

Instructions for installing the X300 series gateways.
List of accessories for the gateway.
Provides the default credentials for access to the webinterface and wireless access point.

Chapter 4: Web Administration Interface

Instructions for accessing the web administration interface
and using it to configure settings for the X300 series
gateways.
The configuration chapters (6 -17) provide detailed
instructions for using the web interface.

Chapter 5: Using Lantronix Provisioning
Manager

Instructions for using Lantronix Provisioning Manager tolocate and configure the gateway.

Chapter 6: Quick Setup

Instructions for configuring the Quick Setup.

Chapter 7: Status

Overview of the gateway status pages.

Chapter 8: System

Instructions for configuring the system features, including
clock, syslog, SSH access and keys, password, enabling
startup scripts, scheduling cron jobs, LED behavior, andexecuting custom shell commands.
Instructions for operations and maintenance, installing
software packages, firmware upgrades, configuration
backup, restoring configuration, reboot and factory reset.

Chapter 9: VPN

Instructions for configuring and enabling OpenVPN and
IPsec tunneling.

Chapter 10: Services

Instructions for configuring and enabling router andgateway services, and for starting and stopping services.
Instructions for configuring industrial protocol services.

X300 Series IoT Cellular Gateway User Guide16

1: About this Guide

Chapter

Description

Chapter 11: Network

Instructions for configuring and enabling the wired,wireless, and cellular network interfaces.
Instructions for configuring DHCP and DNS, static routes,
firewall, QoS, and load balancing.
Instructions for defining hostname and running network
diagnostic commands.

Chapter 12: Bluetooth

Instructions for configuring and enabling Bluetooth SPP for
serial data transmission.

Chapter 13: Percepxion

Instructions for configuring Percepxion client settings.

Chapter 14: Discovery

Instructions for enabling discovery on query port 0x77FE.

Chapter 15: Serial

Instructions for configuring serial settings on the RS-232
and RS-485 lines.

Chapter 16: SSL

Instructions for creating SSL credentials, uploading SSL
certificates and private keys from a CA or self-signed,
generating self-signed certificates, and uploading trusted
authority certificates.

Chapter 17: Tunnel

Instructions for configuring and enabling serial Tunnel
connections.

Appendix A: Compliance Information

Provides compliance information.

Appendix B: Power Cable Schematic

Provides information about accessories, cabling, andconnectors.

Appendix C: List of Acronyms and Protocols

Provides a glossary of relevant acronyms and protocols.

Appendix D: Lantronix Technical Support

Provides instructions for contacting Latronix TechnicalSupport.

X300 Series IoT Cellular Gateway User Guide17

1: About this Guide

Additional Documentation
Visit the Lantronix web site at https://www.lantronix.com/support/documentation for the latest
documentation for this product series.
Document

Description

X300 Series Quick Start Guides

Provides hardware installation instructions,directions to connect the X300 series gateway, andnetwork IP configuration information.

Using the X300 Series SDK Application Note

Describes how to use the SDK to create custom
packages and the Image Builder to build custom
firmware images.

X300 Series Product Brief

Provides X300 series gateway product overview
information and specifications.

X300 Series IoT Cellular Gateway User Guide

18

2:

Introduction
The X303 and X304 models offer LTE-M and LTE Cat 1 cellular communication, Wi-Fi, BLE,
Ethernet, and serial interface in a small, industrial-grade form factor. The X300 model offers Wi-Fi,
BLE, Ethernet, and serial interface in the same industrial-grade form factor. With built-in security tohelp prevent cyber-attacks, the X300 series gateway is a robust and reliable solution for missioncritical applications provided with Console Flow, extended warranty, and connectivity services.

Key Features
InfiniShield™ SecurityBuilt-in security framework for mission-critical applications



Secure boot, secure firmware updates, secure storage

Secure communications, secure network attach

Software FeaturesAdministration and network protocols

Web user interface, setup wizard, console log viewer, save/load configuration



NTP, SMS/OTA remote configuration, TR-069 capable, Lantronix Provisioning Manager

RedundancyResilience








Ethernet, Cellular, Wi-Fi (configurable as failover or load balancing)
Network connectivity watchdog (configurable), internal application watchdog

Wi-Fi


Client or Access point, multiple SSID



WPA, WPA-PSK/WPA2-PSK/WPA3-PSKEnterprise Security (WPA2-Enterprise/WPA3-Enterprise)EAP-TLS, EAP-TTLS (MS-CHAPv2), EAP-PEAPv0/EAP-MS-CHAPV2, EAP-PEAPv1,
EAP-FASTBluetooth and Wi-Fi coexistence

Routing features and protocols


DHCP, static routing, port forwarding, traffic routing, static/dynamic DNS, DNS proxy,
NAT, STP

VPN and tunneling protocols – PPTP client, L2TP, OpenVPN client/server/passthrough,GRE, IPsec up to 4 channels

Security – zone-based firewall, VLAN, DMZ, HTTPS local & remote connection, SIM PIN

Performance and Fault Management
Real time processor load and interface (WAN/LAN/Wi-Fi), traffic analysis, ICMP,
traceroute, NS lookup

X300 Series IoT Cellular Gateway User Guide19

2: IntroductionEssential IoT Applications
Serial and Bluetooth SPP to Network tunnels

Python runtime and packages available as IPKs for installation



Add your own IoT edge applications with the SDK and Image Builder

Lantronix Software Services


Lantronix Percepxion – Secure cloud platform to manage remote IoT gateways through asingle pane of glass.



Lantronix Connectivity Services – North American and global cellular data plans and VPN
security to manage your SIMs and services.



Lantronix LEVEL Technical Services – Provides dedicated technical support experts to assist
your team with technical challenges you may encounter.

Applications
The X300 series gateway is suitable for these application scenarios:Industry 4.0

Energy management

Smart farmingRemote asset management

SKU Information
Table 2-1 X300 Series Models
Lantronix Part Number

Description

X300F202SGATEWAY INCL. 3 YEARS DEVICE MANAGEMENT SERVICE. ROUTERS MULTI-MODE SERIAL PORT X1;
 1T1R WI-FI 5; BLUETOOTH 5.1;
 ETHERNET LAN PORT X1; E
 PACK SOFTWARE SUITE

X303F202SGATEWAY INCL. 3 YEARS DEVICE MANAGEMENT SERVICE. LTE-M
ROUTER MULTI-MODE SERIAL PORT X1;
 1T1R WI-FI 5; BLUETOOTH 5.1;
 ETHERNET LAN PORT X1;
 EPACK SOFTWARE SUITEX304G00ASGATEWAY INCL. 3 YEARS DEVICE MANAGEMENT SERVICE. LTE CAT. 1
ROUTER FOR THE USA, CANADA; MULTI-MODE SERIAL PORT X1;
 1T1R WI-FI 5; BLUETOOTH 5.1;
 ETHERNET LAN PORT X1;
 EPACK SOFTWARE SUITE

X300 Series IoT Cellular Gateway User Guide20

2: Introduction

Lantronix Part Number

Description

X304G002SGATEWAY INCL. 3 YEARS DEVICE MANAGEMENT SERVICE. LTE CAT. 1
ROUTER FOR EMEA, ASIA PACIFIC; MULTI-MODE SERIAL PORT X1;
 1T1R WI-FI 5; BLUETOOTH 5.1;
 ETHERNET LAN PORT X1;
 EPACK SOFTWARE SUITEX304G007SGATEWAY INCL. 3 YEARS DEVICE MANAGEMENT SERVICE. LTE CAT. 1
ROUTER FOR JAPAN, SOUTH KOREA;
 MULTI-MODE SERIAL PORT X1;
 1T1R WI-FI 5; BLUETOOTH 5.1;
 ETHERNET LAN PORT X1;
 EPACK SOFTWARE SUITEX304G00CSGATEWAY INCL. 3 YEARS DEVICE MANAGEMENT SERVICE. LTE CAT. 1
ROUTER FOR CHINA, THAILAND, INDONESIA, INDIA;
 MULTI-MODE SERIAL PORT X1;
 1T1R WI-FI 5; BLUETOOTH 5.1;
 ETHERNET LAN PORT X1;
 EPACK SOFTWARE SUITE

X300 Series IoT Cellular Gateway User Guide21

2: Introduction

Hardware Components
General Specification
Table 2-2 General Specification
Component

Specification

PhysicalCasingBrushed aluminum alloy

Dimensions (W x D x H)

79 x 79 x 23.5 mm

Weight

150 grams, approximately

Environmental
Operating temperature-30 °C ~ +70 °C, up to 95% RH

Storage temperature-40 °C ~ +85 °C, up to 95% RH

MemorySPI NOR Flash memory

8MB

Parallel NAND Flash memory

256MB

DDR2 SDRAM

128MB (factory option doubled to 256MB)

Power
Power

Input voltage: 9V - 30V DC
3-pin Nano-Fit™ header

Digital Input (Ignition)

One (1) digital input, on the middle pin of the 3-pin header
Input: 0 V DC ~ 2.5 V DC => ZERO; 3 V DC ~ 50 V DC => ONE

Interfaces
Ethernet

10/100 BASE-T
One (1) LAN port , via RJ-45 header
Two (2) LEDs (link, activity)

Wi-Fi

X303: IEEE 802.11ac/a/b/g/n 1T1R Wi-Fi 5 / Bluetooth 5.1, with

1 RP-SMA antenna connector
X300 and X304: IEEE 802.11ac/a/b/g/n 2x2 MIMO Wi-Fi 5 /Bluetooth 5.1, with 2 RP-SMA antenna connectors
Dual SIM operation

X303 / X304 only: Universal MFF SIM
Auxiliary (external) mini-SIM holder

GNSS

X304 only: Qualcomm’s IZatTM gen. 8C gpsOne; via a dedicated SMA
connector

User data storage

Internal: via the parallel NAND Flash memory
External: One (1) microSD card slot (microSD card not provided)

Serial operation

User selectable as 6 signal RS-232 (Rx, Tx, RTS, CTS, DSR, DTR) or
half-duplex RS-485, via RJ-45 header
Software configurable baud rate options from 2400 bps to 921600 bps

Digital Input

One (1), via the middle pin of the power header Input: 0 V dc ~ 2.5 V dc => ZERO; 3 V dc ~ 50 V dc => ONE

X300 Series IoT Cellular Gateway User Guide22

2: Introduction

Component

Specification

Status LEDs

X303 and X304: Seven (7) LEDs on top panel for network activity andstatus
X300: Four (4) LEDs on top panel for network activity and status

Reset button

Soft Reset (reboot): Short press more than one (1) second and lessthan 5 seconds
Hard Reset (factory reset): Long press more than 5 seconds and lessthan 20 seconds

Front Panel
Figure 2-1 X300 model Front View

7

1

2

3

4

5

6

ID

Connection NameID

Connection Name

1

Wi-Fi antenna

5

Serial RS-232/RS-485

2

Ethernet LAN

6

Wi-Fi / Bluetooth antenna

3

DC input

7

LEDs

4

Reset button

X300 Series IoT Cellular Gateway User Guide23

2: Introduction

Figure 2-2 X303 model Front View

7

1

2

4

3

5

6

ID

Connection NameID

Connection Name

1

Cellular antenna

5

Serial RS-232/RS-485

2

Ethernet LAN

6

Wi-Fi / Bluetooth antenna

3

DC input

7

LEDs

4

Reset button

Figure 2-3 X304 model Front View

1

2

4

3

5

6

ID

Connection NameID

Connection Name

1

Wi-Fi antenna

5

Serial RS-232/RS-485

2

Ethernet LAN

6

Wi-Fi / Bluetooth antenna

3

DC input

4

Reset button

X300 Series IoT Cellular Gateway User Guide

LEDs (on top, not shown here)24

2: Introduction

Back Panel
Figure 2-4 X300 model Back View

microSD card slot

Figure 2-5 X303 model Back View

1
ID

Connection Name

1

External SIM slot

2

microSD card slot

X300 Series IoT Cellular Gateway User Guide225

2: Introduction

Figure 2-6 X304 model Back View

1

2

4

3

ID

Connection NameID

Connection Name

1

Cellular antenna

4

microSD card slot

2

GNSS antenna

5

Cellular antenna

3

External SIM slot

5

LEDs
Table 2-3 describes the device status LEDs for X303 and X304 models, as shown in Figure 2-2.
Table 2-3 Top Panel LEDs
Name

Color

StatusDescription

Alert

Red

OFF

No alert, device is running smoothlyFlashing

Cellular module reboot, Linux kernel bootingON

Hardware fault

OFF

Cellular data service is not connectedFlashing

Data sent and received over cellular connection

ON

Cellular data service is connected

OFF

Device is not registered on a cellular network

Flashing

Registered on roaming cellular network

ON

Registered on home cellular networkOFF

No signal (CSQ=0 to 5, 97, 98, 99)Flashing

Weak signal (CSQ > 6 to 12)

ON

Strong signal (CSQ ≥ 6 to 12)

OFFSIM not in use

Flashing

External SIM is in use

ON

Embedded SIM is in use

OFF

Wi-Fi network is inactive

Flashing

Wi-Fi network connection trafficON

Wi-Fi network link is up and active

OFF

Power offON

Power onActivity

Network

Signal

SIM

Wi-Fi

Power

Amber

Amber

Amber

Blue

Blue

Green

X300 Series IoT Cellular Gateway User Guide26

2: Introduction

Table 2-4 describes the LEDs for the X300 model, as shown in Figure 2-1.
Table 2-4 X300 model Top Panel LEDs
Name

Color

StatusDescription

Alert

Red

OFF

No alert, device is running smoothlyFlashing

Cellular module reboot, Linux kernel bootingON

Hardware fault

User-defined

Amber

ON/OFF

User-programmable LED.

Wi-Fi

Blue

OFF

Wi-Fi network is inactive

Flashing

Wi-Fi network connection trafficON

Wi-Fi network link is up and active

OFF

Power offON

Power on

Power

Green

CellularTable 2-5 X303 / X304 Cellular Data Rates
Cellular Type

Uplink / Downlink Maximum Data Rate

2G

236.8 / 296 kbps

3G

5.76 / 42.2 Mbps

LTE-M

Cat M1 [NB1]: 375 / 300 [62.5 / 27.2] kbps
updated to Cat M2 [NB2]: 1,000 / 600 [140 / 120] kbps

LTE Cat 1

FDD: 5 / 10 Mbps
TDD: 3.1 / 8.96 Mbps

Table 2-6 X303 / X304 Cellular Bands
ModelPart Number

Cellular TypeBands1

Fallback Mode Bands1

X303

X303F202S

LTE Cat M1

85(12)/28/13/20/
27/26(18,5,19)/8/3/
66(4)/25(2)/1

2G

5/8/3/2

X304

X304G002S

LTE Cat 1

28/20/8/3/1/7

3G, 2G

8/1; 8/3

X304G00AS

LTE Cat 1

71/12(17)/13/14/26(5)/66(10,4)/25(2)––X304G007SLTE Cat 1

18/5(19)/8/21/3(9)/1/7––

X304G00CS

LTE Cat 1

3G, 2G

8/1; 8/3

2

5/8/3/1; TDD 40/41

1. Ranked by increasing frequency
2. More precisely, B41’s 2535 MHz ~ 2655 MHz subset, suited to China well

X300 Series IoT Cellular Gateway User Guide27

2: Introduction

SIM Slot
The X303 and X304 models provide one embedded SIM and one external SIM slot toaccommodate one mini SIM card (2FF), as shown in Figure 2-5 and Figure 2-6.

Antenna Connections
Wi-Fi / Bluetooth:

X300: Two (2) Wi-Fi / Bluetooth, RP-SMA connectors

X303: One (1) Wi-Fi / Bluetooth, RP-SMA connector

X304: Two (2) Wi-Fi / Bluetooth, RP-SMA connectors

Cellular / GNSS:

X300: not applicable

X303: One (1) cellular, SMA connector

X304: Two (2) cellular (main and diversity), SMA connectors and one (1) GNSS, SMA
connector

Certified Antennas
Table 2-7 lists the antennas that have been certified for the X300 series gateways.
Table 2-7 Certified Antennas
PurposeAntenna type

Description

Wi-Fi Antenna

Dipole, swivel typeantenna, with RPSMA(M) connector

Peak gain:

Lantronix Part
Number
9B

Approved Region
102B

A21H0

FCC, IC, EU, AUS/
NZS, JPN, China,
MexicoA33M0

N/A

2 dBi, 2.4 Ghz to
2.5 Ghz, 2 dBi,
5.15 Ghz to 5.85
Ghz
RoHS compliant

WWAN Antenna

Dipole, 4G, swivel
type blade antenna,
with SMA
connector, adhesive
mount

Performanceacross LTE
frequency bands
698-960, 17102170, 2500-2700
MHz
Gain: Up to 2 dBi
RoHS compliant

Note:

Antenna gain listed above excludes cable loss.

Antenna Selection
Use the following guidelines in Wi-Fi antenna selection:

Dipole, peak gain less than 3.8 dBi @ 2.4 GHz ~ 2.5 GHz

Use the same dipole antenna type as certified module and modem for FCC or externalantenna with length greater than 20 cm.

X300 Series IoT Cellular Gateway User Guide28

2: Introduction

Ethernet Port (LAN)Figure 2-7 Ethernet Port

Table 2-8 Ethernet RJ45 Connector Pin Assignment and LEDs
Pin

Signal Name
1

ETX+

2

ETX-

3

ERX+

4

-

5

-

6

ERX-

7

-

8

-

Left LED (Amber)

Link
On: link
Off: No link

Right LED (Green)

RX/TX Activity
Flashing on: Activity
Off: No activity

X300 Series IoT Cellular Gateway User Guide29

2: Introduction

Serial PortOne serial RJ45 connector for RS-232 or RS-485 protocol communication.
Figure 2-8 RJ45 Connector RS-232 / RS- 485 Interface

Table 2-9 Serial RJ45 Connector Pin Assignment and LEDs
Pin Number / LED

Signal Name for RS-232

Signal Name for RS-485

1

RTS out

TX+ (output from X300)

2

DTR out

Not used / do not connect

3

TX outTX- (output from X300)

4

GND

GND

5

GND

GND

6

RX in

RX+ (input from X300)

7

DSR inNot used / do not connect8

CTS inRX- (input to X300)

Left LED (Amber)

Receive Data activities (RXD)

Receive Data activities (RXD)

Right LED (Green)

Transmit Data activities (TXD)

Transmit Data activities (TXD)

X300 Series IoT Cellular Gateway User Guide30

2: Introduction

Power Input
The power input interface is shown in Figure 2-9.
For the power cable schematic, see Power Cable Schematic.
Figure 2-9 DC Input Interface

GroundPositive

Ignition

Power Consumption
Table 2-10 X300 Series Power Consumption
Device State

Input Voltage
10V

12V

24V

30V

Idle state (Wi-Fi, WWAN, WWAN6, LAN & 112 mA
Cellular off)

93 mA

52 mA

41 mA

LAN connected (Wi-Fi, WWAN, WWAN6, 148 mA& Cellular off)

110 mA

64 mA

48 mA

WWAN connected (Wi-Fi, LAN, WWAN6& Cellular off)

113 mA

95 mA

48 mA

40 mA

WWAN6 connected (Wi-Fi, LAN, WWAN
& Cellular off)

112 mA

96 mA

48 mA

42 mA

Wi-Fi on (WWAN, WWAN6, LAN, &Cellular off)

162 mA138 mA

70 mA

58 mA

WWAN, WWAN6, LAN connected, Wi-Fi
on, (Cellular standby)

174 mA144 mA

74 mA

60 mA

Cellular connected (Wi-Fi, LAN, WWAN & 164 mA
WWAN6 off)

144 mA

77 mA

54 mA

WWAN, WWAN6, LAN connected, Wi-Fi
on, Cellular connected

159 mA

83 mA

74 mA

204 mA

Reset Button
Using a paper clip or similar object to poke through the RESET hole, press the recessed Resetbutton as shown in Figure 2-2.
To reboot the unit, press and hold the reset button for more than 1 second and less than 5seconds.

To reset to factory settings, press and hold the reset button for more than 5 seconds and lessthan 20 seconds.

X300 Series IoT Cellular Gateway User Guide31

2: Introduction

Product Label
Figure 2-10 Sample Product Label

Model Name

Manufacturer Part Number
Product Revision
Country of Manufacturing Origin
Serial Number

QR CodeDevice ID

X300 Series IoT Cellular Gateway User Guide

32

3:

Installation

Package Contents

Gateway and accessories:
Component

X300

X303

X304

Gateway model

X300F202S

X303F202S

X304G000S, X304G002S,
X304G007S, X304G00AS,
X304G00CS

Power supply

ACC-520-165-00

ACC-520-165-00

ACC-520-165-00

Wi-Fi Bluetooth Antenna A21H0 x2

A21H0 x1

A21H0 x2

Cellular Antenna

A31M0

A33M0

N/A



X300, X303, or X304 Quick Start GuideSIM Insert (printed card with SIM APN and Lantronix Connectivity Services links)

The embedded SIM card is pre-activated by Lantronix and preloaded with an initial amount ofdata. For more details, see SIM Card Management on page 35.
Other accessories must be purchased separately.
Notes:
To reduce potential safety issues, only the power adapter provided with the product, areplacement power adapter provided by Lantronix or agency, or a power adapter
purchased as an accessory from Lantronix or agency should be used with the
product.



If Class I power adapter is used, the power supply cord shall be connected to asocket-outlet with earthing connection

User Supplied Items
The following items are supplied by the user, if needed. For details about purchasing Lantronix
accessories, see Accessories below.


Auxiliary SIM card (2FF), data plan activation requiredCat 5 Ethernet cable for wired LAN connectionSerial cable (RS-232 RJ45 connector)



microSD card for user data storage

The Ethernet cable, serial cable, and microSD card can be acquired from various vendors.

X300 Series IoT Cellular Gateway User Guide33

3: Installation

Accessories
Lantronix accessories are listed in Table 3-1 according to part number and application.
To buy Lantronix accessories, go to https://www.lantronix.com/about-us/contact/.
Table 3-1 Lantronix Accessories
Part Number

Description

Power Cords
ACC-500-0420-00

POWER CORD WITH 3-PIN NANO-FIT PLUG; 2.5 A FUSE; TWO 1METRE-LONG AWG20 STRIPPED WIRES (RED, BLACK) FOR
POWER

ACC-500-421-00

POWER CORD WITH 3-PIN NANO-FIT PLUG; 2.5 A FUSE; TWO 1METRE-LONG AWG20 STRIPPED WIRES (RED, BLACK) FOR
POWER; ONE 20-CENTIMETRE-LONG AWG20 WIRE (BLUE) FOR
IGNITION

Power Supply and Adapters
ACC-520-0165-00

WORLDWIDE. POWER SUPPLY, WALL CUBE, 12VDC 12W, 4 AC
PLUGS, LEVEL 6, WITH PSE, 2X2 3.0MM LATCHED CONN OUTPUT

ACC-520-0166-00

US. POWER SUPPLY, WALL CUBE, 12VDC 12W, US, LEVEL 6,
WITH PSE, 2X2 3.0MM LATCHED CONN OUTPUT

Wi-Fi Antenna
A21H0

2.4/5.8GHZ DIPOLE ANTENNA FOR ISM & WLAN, RP-SMA(M)HINGED (1 for X303, 2 for X304)

4G / GNSS Antenna
A33M0

THREE IN ONE LTE, 2*LTE+GPS/GLONASS/BD ANTENNA,
3*3000MM RG174 CABLE WITH 3*SMA MALE, ADHESIVE MOUNTA33H0

THREE IN ONE LTE, 2*LTE+GPS/GLONASS/BD/GALILEOANTENNA, 3*3000MM RG174 CABLE WITH 3*SMA MALE,
ADHESIVE MOUNT. while stocks last

A33H1

THREE IN ONE LTE, 2*LTE+GPS/GLONASS/BD/GALILEOANTENNA, 3*3000MM RG174 CABLE WITH 3*SMA MALE,
ADHESIVE MOUNT.

A32M0

TWO IN ONE LTE, 2*LTE ANTENNA, 2*3000MM RG174 CABLE,
SMA MALE. while stocks last

A32H0

TWO IN ONE LTE, 2*LTE ANTENNA, 2*3000MM CABLE, SMA MALE,
ADHESIVE MOUNT. while stocks last

A32H1

TWO IN ONE LTE, 2*LTE ANTENNA, 2*3000MM CABLE, SMA MALE,
ADHESIVE MOUNT.

A31M0SINGLE LTE ANTENNA, ADHESIVE REMOTE ANTENNA WITH
3000MM RG174 CABLE, SMA MALE. while stocks last

A31H0

SINGLE LTE ANTENNA,ULTRA WIDEBAND I-BAR ANTENNA,
3000MM CABLE WITH SMA MALE, ADHESIVE MOUNT. while stocks
last

A31H1

5G/4G ADHESIVE MOUNT ANTENNA 600-6000MHZ WIDEBANDOPERATION. IP67 RATED ENCLOSURE DIMENSIONS: 105 X 30 X
7.9MM CONNECTOR: SMA MALE STRAIGHT
CABLE: 1M OF RG-174 ROHS & REACH COMPLIANT

X300 Series IoT Cellular Gateway User Guide34

3: Installation

Preparing to Install
Before starting installation, gather the necessary hardware, accessories, and documentation.
Review and follow the safety information as described in the documentation.
Ensure that the computer used to access the web admin interface for gateway configuration isequipped with the following:

Ethernet port or Wi-Fi connectivity and Internet serviceWeb browser with recently updated version (Chrome, Safari, Firefox, Edge, Internet Explorer)



DHCP client is enabled on the computer

Enabling DHCP Client on Your Computer
The DHCP client must be enabled on your computer to obtain a valid IP address from thegateway.
To enable DHCP on Windows 8 or 10:
1. Go to Start > Control Panel > Network and Internet > Network and Sharing Center.
2. Click the active network connection. The Network Connection Status box appears.
3. Click Properties and then select IPv4 (TCP/IPv4) and click Properties. The Internet Protocol
Version 4 (TCP/IP) Properties will appear.
4. On the General tab, select the following options:

Obtain an IP address automaticallyObtain DNS server address automatically

5. Click OK to close the dialog.
To enable DHCP on Mac OS:
1. Launch System Preferences, and then choose Network.
2. Select Ethernet from the adapters list on the left.
3. Set the Configure IPv4 list to “Using DHCP.”SIM Card Management
The Lantronix Connectivity Services embedded SIM card comes pre-activated by Lantronix andpreloaded with an initial amount of data. A printed SIM Insert card with the SIM APN on one sideand Lantronix Connectivity Services links on the other side is provided. Keep this card for quickreference.
When the purchase order for the gateways is processed, Lantronix creates an account on theConnectivity Services SIM Management portal and enters the SIM cards into the account. A
confirmation email with account login details is sent to the contact person on record.
SIM Card Activation
The provided SIM card is pre-activated by Lantronix, but you may need to configure APN in the
X300 series software’s cellular network interface SIM settings. To configure the APN, go to Quick
Setup or Network > Interfaces and edit the cellular network interface’s SIM settings.

X300 Series IoT Cellular Gateway User Guide35

3: Installation
SIM Management Portal
To manage your Lantronix SIM cards, visit the Connectivity Services SIM Management portal at:https://connectivity.lantronix.com
Sign in by entering the user name and password provided by Lantronix.
Here you can view SIM status and usage, manage SIM data limits, manage the SIMs, and accessthe API documentation.
Before use, the SIM card status will be Pre-active on the SIM Management portal. After it starts
transferring data, the status will appear as Active.
Second SIM Card
You may purchase a second SIM card (region specific) from Lantronix Connectivity Services orfrom a cellular operator for use in the external SIM slot. Before using the SIM card, activate it
according to the instructions provided by the vendor.
Lantronix Connectivity Services Links
SIM Management Portal
Account
Email Support

https://connectivity.lantronix.com
https://shop.lantronix.com/accountsimhelp@lantronix.com

Physical Installation
Insert SIM Card
Use the embedded, pre-activated SIM card or purchase a SIM card to install in the external SIM
slot of the X303 or X304 model gateway. The SIM card must be activated according to vendor
instructions before use.
The figures below illustrate installing the SIM card on the X303 model.
To insert the optional SIM card in the external SIM slot:
1. Press the yellow button (using a pen or similar object) to eject the SIM tray.

Press the yellow button to eject the SIM tray.

X300 Series IoT Cellular Gateway User Guide36

3: Installation
2. Place the SIM card onto the SIM tray with the contact side up. Note that the tray has a small
notch in one of the corners, and the card will only fit one way.

3. Gently slide the SIM tray into the SIM slot and push it to lock it in place.

X300 Series IoT Cellular Gateway User Guide37

3: Installation

Connect the Antennas
Ensure that the antenna used is suitable for the cellular frequencies in use, for both the main andauxiliary connectors.
The number and location of the antenna connectors vary by gateway model. Be sure to attach theantennas to the correct antenna connectors according to the connector labels printed on thegateway.
To connect the antennas:
1. Attach the cellular antenna to its antenna connector and tighten it securely.
2. Attach the Wi-Fi / Bluetooth antenna to its antenna connector and tighten it securely.

Cellular

Wi-Fi / Bluetooth

The X303 model is shown above. The X300 model has one Wi-Fi and one Wi-Fi / Bluetoothantenna connector on the side shown above. The X304 model has two Wi-Fi / Bluetoothantenna connectors on the side shown above and two cellular connectors and one GNSS
antenna connector on the opposite side.

Connect the AC Power
To connect the AC power:
1. Connect the power cord to the power supply.

X300 Series IoT Cellular Gateway User Guide38

3: Installation
2. Attach the 3-pin connector end of the power cord to the DC input connector on the base unit.

DC input 3-pin connector
The X303 model is shown above. The power input connector
is the same for all models.
3.

Plug the AC plug on the power supply into a standard AC receptacle.

Connect the Gateway to a Computer
To log into the web administration interface, first connect to the gateway’s Wi-Fi access point orconnect an Ethernet cable from the gateway’s LAN Ethernet port to the computer’s LAN Ethernet
port.
Connect using Wi-Fi
To connect using Wi-Fi:
1. On your computer, open the Wireless settings and connect to the gateway’s Wi-Fi accesspoint. The default access point SSID is:Parameter

Details

SSID

Lantronix-<model>-<serial-number>

WPA/WPA2 TKIP Key

W1rele$$2. Open the web browser to 192.168.1.1. The login page appears.
3. Log into the web admin interface. The default username and password credentials are:
User

Default Password

admin

admin

root

L@ntr0n1x

4. You will be required to change the root and user passwords after the first login. After changing
the initial passwords, log in again to configure the network settings.
Connect using Ethernet
To connect using Ethernet:
1. Connect an RJ-45 terminated Ethernet cable between the LAN Ethernet port on the unit andthe LAN Ethernet port on the computer.

X300 Series IoT Cellular Gateway User Guide39

3: Installation
2. Open the web browser to 192.168.1.1. The login page appears.
3. Log into the web admin interface. The default username and password credentials are:
User

Default Password

admin

admin

root

L@ntr0n1x

4. You will be required to change the root and admin user passwords after the first login. Afterchanging the initial passwords, log in again to configure the network settings.

X300 Series IoT Cellular Gateway User Guide40

3: Installation

Default Configuration
All usernames and passwords are case sensitive.

Web Admin Page
Table 3-2 Default Web Admin Page Credentials
User

Default Password

admin

admin

root

L@ntr0n1x

Note: Upon first login, you are required to change the factory default passwords before
any other gateway configuration can be done. Both the admin and root passwords must
be changed.

Wireless Access Point SSID
Table 3-3 Default Wireless Access Point SSID
Parameter

Details

SSID

Lantronix-<model>-<serial-number>

WPA/WPA2 TKIP Key

W1rele$$Default Interface Configuration
Table 3-4 Default Network Interface Configuration
Interface

Details

WAN (Ethernet)

Automatic (DHCP client)
Priority source of Internet with cellular backup

LAN (Ethernet)

Active DHCP with starting IP address 192.168.1.100 with pool of
100 clients.

Cellular

No PAP/CHAP authentication

Wireless (LAN)Wi-Fi enabled as access point

X300 Series IoT Cellular Gateway User Guide

41

4:

Web Administration Interface
The web admin interface allows the administrator and other authorized users to configure andmanage the X300 series gateways using most web browsers (Firefox, Internet Explorer or Safari
web applications with the latest browser updates).
Figure 4-1 shows key components on the web admin interface:
Figure 4-1 Web Admin Interface

How to interact with the web interface:
Menu

The menu displays a list of options to configure and operate
the gateway.
Select a menu option to display the related status andconfiguration settings in the content pane.

Active content

The content pane displays status, configuration settings,
and options for interacting with the gateway.
It lets you view status, and configure settings on thegateway, or perform maintenance or other operations.

X300 Series IoT Cellular Gateway User Guide42

4: Web Administration Interface

Save Configuration

These actions let you save configuration changes or reset
unsaved changes on the active page Save & Apply - Applies and saves the changes on

the web page to the gateway (in NVRAM) so thatthe settings will persist when the gateway isrebooted. After clicking this button, wait for theconfiguration to be applied before closing thebrowser, otherwise the old configuration will be
restored.
 Apply Unchecked - Click the arrow on the Save & Apply

button to reveal this option. Applies and saves thechanges on the web page to the gateway (inNVRAM), but will not disrupt the active network
interface. Use this if you are changing the interface
parameters on which the session is active.
 Save - Saves the changes on the web page (toRAM) without committing the changes. All saved
configuration will be lost when the gateway isrebooted if they are not saved and applied.
 Reset - Discards the unsaved changes on the page.
Helper actions

These actions help you use the web interface.
 Help? - opens embedded help information for the active

page Auto Refresh on/off - lets you enable or disable the UI

auto refresh action
 Unsaved changes: <#> - shows the number of unsavedchanges and lets you save & apply the changes to thegateway’s configuration or revert the changes back to the
saved configuration.
 Logout - logs you out of the web administration interface.

Logging In
The admin user or root user can log into the web admin interface.
If your gateway is new, please inspect and set up the gateway as described in Chapter 3:
Installation.
To log into the web interface:
1. Open a web browser on the computer.
2. Enter the default LAN IP address 192.168.1.1. The login screen is displayed.

X300 Series IoT Cellular Gateway User Guide43

4: Web Administration Interface

Figure 4-2 Web Admin Login Page

3. Enter the username and password. If you are logging in for the first time after installation orafter factory reset, use the default credentials.
4. Click Login.

Change Passwords After Initial Login
After first login with a new device or after resetting the device to factory defaults, you are required
to change the factory default passwords for both the admin user and root user before any othergateway configuration can be done.
The password requirements are the following:Password must consist of at least 8 characters and include a minimum of the following:

1 uppercase character

1 lowercase character

1 numerical character (0-9)



1 special character

Note:

Log in as root user to change both admin and root password at the same time.

1. Log into the web admin interface as root user. This will allow you to change the passwords forboth the root user and the admin user.
2. For the root user, enter the new password and then re-enter it to confirm it.
3. For the admin user, enter the new password and then re-enter it to confirm it.
4. If the country code selection for Wi-Fi operation is displayed, select the country code where
the device is being used. This selection ensures that the device will only enable Wi-Fi radio
settings that conform with the country’s regulatory laws.
5. Click Save & Apply.

X300 Series IoT Cellular Gateway User Guide44

4: Web Administration Interface
This will log you out and return to the login page automatically.

Logging Out
To log out of the web admin interface:
1. Click the Logout button located in the upper right part of the web admin interface page. Whenlogout is complete, the login screen is displayed.

X300 Series IoT Cellular Gateway User Guide

45

5:

Using Lantronix Provisioning Manager
This chapter covers the steps for locating a device and viewing its properties and details. Lantronix
Provisioning Manager is a free utility program provided by Lantronix that discovers, configures,
upgrades, and manages Lantronix devices.
It can be downloaded from the Lantronix website at https://www.lantronix.com/products/lantronixprovisioning-manager/. For instructions on using the application, see the Lantronix Provisioning
Manager online help.

Installing Lantronix Provisioning Manager
1. Download the latest version of Lantronix Provisioning Manager from https://www.lantronix.com/products/lantronix-provisioning-manager/.
2. In most cases, you can simply extract Lantronix Provisioning Manager from the archive andrun the executable. For detailed instructions, see the Lantronix Provisioning Manager online
help.

Accessing the Gateway Using Lantronix Provisioning Manager
To discover a device on the local network:
1. Launch Lantronix Provisioning Manager.
2. If this is the first time you have launched Lantronix Provisioning Manager, you may need toproceed through an initial setup.
3. Locate the X300 series gateway in the device list. The device’s firmware version, serial
number, IP address, and MAC address will be shown. Additional information can be obtainedby clicking the three dot menu and clicking Get Device Info.
4. In order to perform operations on the X300 series gateway such as upgrading the firmware,
updating the configuration, or uploading to the file system, click the checkbox next to thedevice and select an operation at the top.

6:

Quick Setup
Quick Setup lets you configure the IP network port so that you can configure other gateway
settings. To bypass quick setup and directly configure the network interfaces using advanced
settings, go to the Network page (see Chapter 11: Network).

Quick Setup
Quick Setup > Quick Setup
To configure the network settings:
1. On the Quick Setup page, enter the network and basic configuration of the gateway. See
Table 6-1.
Table 6-1 Quick Setup Network Configuration
Parameters

Description

Local Area Network (LAN)IPv4-AddressEnter an IPv4 address for the LAN interface. This is the IP Address thatmust be used to access the gateway.
The default LAN IPv4 Address is 192.168.1.1.

IPv4-Netmask

Enter the IPv4 netmask of the LAN interface.
The default netmask is 255.255.255.0

Cellular
General Settings (tab)Select which SIM to use, embedded or external SIM.

Embedded SIM Settings (tab)Use Custom APN

Select this option to use a custom Access Point Name (APN) for thecellular network data connection.

APN

If Use Custom APN is selected, it displays the custom APN.

PIN

SIM card Personal Identification Number (PIN) is used to lock the card,
preventing people from making unauthorized phone call or accessing
cellular data services.
Enter the PIN of the SIM card.

Authentication Type None PAP
 CHAP

Enable roaming

Displays as Enabled if data roaming is enabled, or disabled otherwise.

External SIM Settings (tab)Use Custom APN

Select this option to use a custom Access Point Name (APN) for thecellular data connection.

APN

If Use Custom APN is selected, enter the APN used for the cellular data
connection.

PIN

SIM card Personal Identification Number (PIN) is used to lock the card,
preventing people from making unauthorized phone call or accessing
cellular data services.
Enter the PIN of the SIM card.

X300 Series IoT Cellular Gateway User Guide47

6: Quick Setup

Parameters

Description

Authentication TypeThe authentication method used for the cellular connection. If PAP,
PAP/CHAP, or CHAP are selected, enter the username and password.

UsernameEnter the PAP/CHAP username.

Password

Enter the PAP/CHAP password.

Enable roaming

Select to enable roaming.
Clear to disable roaming.

Wireless Network (LAN)DisableIf selected, the wireless interface is disabled.

Mode

Displays the wireless mode
ap - Access Point
client - wireless client

SSID

Displays the SSID of the wireless network. Edit the field to change the
SSID.

Encryption

Displays the Encryption type

Password

If encryption is enabled, the password field contains the SSID
password. Click the button to reveal the password value.

Percepxion Client
EnableSelect to enable or clear to disable the Percepxion client.
For more configuration options, go to Percepxion > Client.

Device ID

Read only. Displays the gateway’s Device ID. Device ID may beprovisioned through Lantronix Provisioning Manager.
Note: Device ID can only be provisioned once. It will persist acrossresets.

Serial Number

Read only. Displays the serial number of the device.

Connection 1
Host

Enter the host name or IP address of the Percepxion server, used toregister the device. It should start with “api.”

SSH Access
EnableSelect to enable or clear to disable SSH access.
To configure SSH access, go to System > Administration.

Time Synchronization
Enable NTP client

Select to enable the NTP client on the gateway to synchronize its
internal clock every 60 minutes from an NTP server.
Clear the check box to disable NTP client.
For more configuration options, go to System > System > Time
Synchronization.

NTP Server candidates

Enter the pool of NTP servers to poll the time from.

Timezone

Select the timezone of the gateway.

X300 Series IoT Cellular Gateway User Guide

48

7:

StatusThe Status pages provide a summary view of the vital configurations of the gateway. It includes
the following pages:
Overview (Page)



Firewall Status

Network Status

Routes

System Log



Kernel Log

Processes

Realtime Graphs



Load Balancing

Overview (Page)
Status > Overview
The Status Overview page provides a listing of important system parameters.
To view the Status Overview:
1. Go to Status > Overview.
2. Scroll the page to view the rest of the Status Overview sections. Click the following links fordetails about each of the Status Overview sections.


System Status

Percepxion Status



Memory Status



MWAN Interfaces Status

System Status
The System section provides the gateway's model and software related information.
Table 7-1 System Status Overview
Parameters

Description

Hostname

Name assigned to the gateway for addressing purposes

Model

Model number of the gateway

Part Number

Model part number

UbootVersion

U-Boot version number

Architecture

Architecture type

Firmware Version

Base firmware version number

X300 Series IoT Cellular Gateway User Guide49

7: Status

Parameters

Description

Module Firmware

Modem firmware version

Kernel Version

Linux Kernel version number

Router TimeDay of the week, month, date, time and year configured on the unit.
The format is Day Month Date hh:mm:ss Year.
The time is displayed in 24-hour clock format.

UptimeDisplays the elapsed time since the unit last rebooted.
The format is dd hh mm ss.

Load Average

Average CPU load time over periods of 1, 5, and 15 minute averages

Reboot Cause

Displays the last reboot cause and time whenever possible.

IMEI

15 digit IMEI number
An IMEI number (International Mobile Equipment Identity) is a 15 or 17
digit unique number to identify GSM or UMTS mobile devices. It is used
to prevent call initiation from a misplaced or stolen GSM or UTMS
device, even if someone swaps out the device’s SIM card.
Note: We recommend you record the IMEI number and secure it sothat it can be quickly accessed in the event of theft or loss of the unit.

Percepxion Status
This section describes the Percepxion client status.
Table 7-2 System Status Overview
Parameters

Description

Client State

Displays the current state of the Percepxion client.

Last Status Update

Displays the elapsed time since the Percepxion client sent its status to
the server.

Last Content Check

Displays the elapsed time since the Percepxion client requested
content check from the server.

Available Firmware Updates

Lists any available firmware updates.

Available Configuration Updates Lists any available configuration updates.

X300 Series IoT Cellular Gateway User Guide50

7: Status

Memory Status
The Memory section provides information about the available memory.
Table 7-3 Memory Status Overview
Parameters

Description

Total Available

Total available RAM memory. Total Memory is sum of used memory,
free memory, buffered memory and cached memory.

Free

Free RAM memory. The bar graph shows the amount of free memory
as a percentage of the total memory.

BufferedSize of buffered memory. The bar graph shows the amount of buffered
memory as a percentage of the total memory.

CachedSize of cached memory. The bar graph shows the amount of cachedmemory as a percentage of the total memory.

MWAN Interfaces Status
The MWAN Interface section shows the status of the available and connected WAN options. Theinterface is green when it is active (it can be online or offline), and red when it is disabled. Online
interfaces show tracking status and uptime. Offline interfaces show the downtime.

Firewall Status
Status > Firewall
The Firewall Status page provides a listing of the IPv4 firewall or IPv6 firewall rule chains in theFilter, NAT, Mangle, and Raw firewall tables.
You can hide or show empty chains in the firewall list, reset the counters, and restart the firewall.
Hide empty chains

Click to hide the chains that have no rules.

Show empty chains

Click to show all chains.

Reset Counters

Click to reset counters for number of packets and traffic.

Restart Firewall

Click to reload the existing firewall configuration of every interface.

Figure 7-1 shows a portion of the IPv4 Firewall status page, and Table 7-4 describes the firewall
details.

X300 Series IoT Cellular Gateway User Guide51

7: Status

Figure 7-1 IPv4 Firewall Status

Table 7-4 Firewall Status
Parameters

Description

Rule Chain name and details

Displays the rule chain name, type, and policy details

Pkts

Displays the number of accepted packets.

Traffic

Displays the amount of traffic captured by the filter.

TargetDisplays the target action for the traffic processed for a respective rule.

Prot.

Displays the protocols configured in the firewall rule.

In

Input interface.

Out

Output interface.

SourceDisplays the source IPv4/IPv6 address.

Destination

Displays the destination IPv4/IPv6 Address.

Options

Displays option details

Comment

Displays comment details

Network Status
Status > Network

X300 Series IoT Cellular Gateway User Guide52

7: Status

Cellular Status
The Cellular section provides the status of the SIM cards in the unit.
Table 7-5 Cellular Status Overview
Parameters

Description

Cellular Data

Displays the cellular data connection status.
 CONNECTED – Data communication is connected.
 DISCONNECTED – Data communication is not connected.

Signal Strength

Displays the current signal strength.
The signal strength range is 0 to 32.
 0: -113 dBm or less (none) 1: -111 dBm (poor) 2 to 30: -109 to -53 dBm (fair to good) 31: -51dBm or greater (excellent)

Note: Signal strength for a good cellular data connection must be 12
or above.
Network Status

Displays the registration status of the unit on the current cellular
network.
 Registered Not Registered Registering

Operator Name

Name of the cellular operator in use

Operator Number

Number of the cellular operator in use

Operator TypeOperator typeRoaming Status

The roaming status of the unit: Home Roaming
 N/A

SIM Status

Displays the availability of SIM card.
 No Sim detected – SIM card is not inserted.
 READY – SIM card is inserted.

Active SIM

Displays the active SIM, Embedded SIM or External SIM.

IMSI

Displays the International Subscriber Identity (IMSI) number. In case of
UMTS, it is read from the SIM card.
The IMSI is a 15 digit unique mobile number associated with thecellular network and used to acquire the details of the mobile for
identifying the user of a cellular network.

Configured BandThe configured radio frequency bands

Registered BandThe registered radio frequency band

Temperature

Internal temperature of the unit in degrees Celsius

ICCID

Integrated Circuit Card ID (ICCID) – unique serial number that identifies
the SIM card.

X300 Series IoT Cellular Gateway User Guide53

7: Status

Network Status
The Network section provides the IPv4 and IPv6 WAN status and the number of active
connections.
Table 7-6 Network Status Overview
Parameters

Description

IPv4 Upstream

Displays status of IPv4 WAN connections with following details:
 Protocol – Static (manually addressed) or DHCP client (dynamicallyaddressed)
 Address – IP address of the WAN interface.
 Gateway – IP address of the WAN interface gateway.
 DNS 1/2/3 – DNS IP addresses, in order of precedence.
 Connected: Duration since connection was established.
 Device: the physical interface, cellular, ethernet adapter and so on.

IPv6 Upstream

Displays status of IPv6 WAN connections with following details:
 Protocol – Static (manually addressed) or DHCPv6 client(dynamically addressed)
 Address – IPv6 addresses of the interface.
 Gateway – IP address of the gateway.
 DNS 1/2/3 – DNS IP addresses; in order of precedence.
 Connected: Duration since connection was established.
 Device: the physical interface, cellular, ethernet adapter and so on.

Active Connections

Displays the number of active connections

Active DHCP and DHCPv6 Leases Status
The Active DHCP Leases and DHCPv6 Leases shows information about the devices connected to
the gateway using a DHCP lease. This includes IPv4 and IPv6 connections.
Table 7-7 Active DHCP Leases Status Overview
Parameters

Description

Host Name

Name of the device (laptop, mobile, etc.) that is connected to thegateway and has been leased an IPv4 address or an IPv6 address by
the gateway’s DHCP server.

IPv4 Address/IPv6 Address

IPv4 address or IPv6 address assigned to the device.

MAC Address

Applies to IPv4. MAC address of the device.

DUID

Applies to IPv6. DUID (Device Unique Identifier) of the device
connected.

Leasetime remaining

The remaining time for which the device can use the DHCP serverleased IPv4 address.

X300 Series IoT Cellular Gateway User Guide54

7: Status

Wireless Status
The Wireless section describes the status of the Wi-Fi network used by the gateway and the Wi-Fi
associated stations.
Table 7-8 Wireless Status Overview
Parameters

Description

Connection Name

Name of the connection and the details:
 Type – The wireless radio chipset
 Channel – Wi-Fi channel
 Bitrate – Data transfer rate
 SSID –Service Set Identifier (SSID) that uniquely names a wireless

local area network (WLAN) Mode – Displays whether the WLAN interface is currently configured

as an access point (Master) or as a client of a higher order Wi-Fi
network.
Note: For Wi-Fi WAN (WWAN) operation, the connection mode
should be ‘Client’.
 BSSID – Displays Basic Service Set Identification (BSSID); 24 bit

MAC address of wireless device.
 Encryption – Displays the data encryption method.
 Associations – Displays the number of associated stations.

Associated Stations
Network

Mode and name of the network to which the device is connected

MAC Address

MAC address of the computers and/or devices that are connected

Host

Host name of the associated station

Signal/Noise

Signal strength/noise in dBm

RX Rate/Tx Rate

The receive (RX) and transmission (TX) data rates of the associatedclient.
Displays data transfer rate (Mbit/s), channel bandwidth (MHz),
Modulation and Coding Scheme index (MCS), and GI time (Guard
Interval, for TX rate).

Disconnect

Click to disconnect the associated station from the access point.

Dynamic DNS Status
The Dynamic DNS section shows the Dynamic DNS IPv4 and IPv6 configuration.

X300 Series IoT Cellular Gateway User Guide55

7: Status

RoutesStatus > Routes
The Routes status page displays the ARP table and active IPv4 and IPv6 routes.
Table 7-9 Routes Status
Parameters

Description

ARP
IPv4 Address

Displays the IPv4 address.

MAC Address

Displays MAC address of the peripheral device.

Interface

Displays the interface name connected to the peripheral device.

Active IPv4 Routes
Network

Displays the network type used by the active IPv4 routes.

TargetDisplays the destination IPv4 address.

IPv4 gateway

Displays the IPv4 address gateway used for traffic routing.

Metric

Displays the metric assigned to the interface.

Active IPv6 Routes
Network

Displays the network type used by the active IPv4 routes.

TargetDisplays the destination IPv6 address.

SourceDisplays the IPv6 address gateway used for traffic routing.

Metric

Displays the metric assigned to interface.

X300 Series IoT Cellular Gateway User Guide56

7: Status

System Log
Status > System Log
The System Log displays detailed system, traffic, and network activity log information.
Syslog events contain the date, severity, and event details. The format is shown in the following
example:Sep 15 22:33:38 Lantronix-X303-0080A36AA223user.info Eventsms: BAND :All supported bands
To configure the system logs, see System > System > Logging.

Kernel Log
Status > Kernel log
The Kernel log displays the Linux kernel log events. It shows information about hardware drivers,
kernel information and status during boot up and more.
It gets reset on every boot.

Processes
Status > Processes
The Processes log displays a list of active Linux system processes and their resource usage.
Table 7-10 Processes Status
Parameters

Description

PID

Displays the Process identifier (PID) number associated with theprocess.

Owner

Displays the task owner

Command

Displays the command nameCPU usage %The CPU usage of the process, displayed as a percentage of the total
available CPU resources.

Memory usage %The amount of the system's working physical memory that the process
is currently using, displayed as a percentage.

Actions

Hang up—Sends a hang up signal to terminate the process.
Terminate—Sends a terminate signal to terminate the process.
Kill—Sends a kill signal to immediately terminate the process. The
process will not perform any cleanup operations.

X300 Series IoT Cellular Gateway User Guide57

7: Status

Realtime Graphs
Status > Realtime Graphs
The Realtime graphs display the gateway’s activities over time for CPU load, WAN network traffic,
wireless usage, and connections.

Load
Status Realtime Graphs > Load
The Load graph shows the CPU load average and peak (y-axis, % utilization) over time (x-axis).
Averages are shown for 1-minute (red), 5-minute (orange), and 15-minute (yellow) load.
Figure 7-2 shows a CPU load graph.
Figure 7-2 Realtime CPU Load Graph

X300 Series IoT Cellular Gateway User Guide58

7: Status

Traffic
Status > Realtime Graphs > Traffic
The Traffic graph indicates the WAN-side incoming and outgoing traffic rate (y-axis) on the
different interfaces over time (x-axis). The graphs display the average and peak data transfer on
the following interfaces (if configured for WAN traffic): eth0, eth1, tun0, tun1, wwan0, can0,
erspan0, br-lan, and wlan1.
Average and peak rates are shown for inbound traffic (blue) and outbound traffic (green).
The WAN interface shows average and peak WAN and cellular traffic.
Figure 7-3 shows an example of network traffic for the eth1 interface:
Figure 7-3 Realtime Network Traffic Graph (eth1)

Wireless
Status > Realtime Graphs > Wireless
The Wireless graph indicates Wi-Fi usage including signal and noise levels (y-axis, dBm) andphysical data transfer rate (y-axis, Mbit/sec) over time (x-axis).
The top graph displays signal (blue) and noise (red) levels. The bottom graph displays the physicaldata transfer rate (green) irrespective of WI-Fi being used as an access point or client.
Figure 7-4 shows the wireless usage graph for a X300 series gateway configured as Wi-Fi client(STA) and connected to an external access point.

X300 Series IoT Cellular Gateway User Guide59

7: Status

Figure 7-4 Realtime Wireless Usage Graph (client)

Connection
Status > Realtime Graphs > Connection
The Connection graph indicates the number of active network connections (x-axis) over time (yaxis). It includes connections originating from the gateway and also connections originating fromthe LAN or WAN.
The graph displays UDP (blue), TCP (green) and other (red) connections. The table below thegraph displays connection details including IPv4/IPv6, protocol, source IP, destination IP, andamount of data transferred.
By default DNS lookup is disabled. You can enable it by clicking the link Enable DNS lookups
below the graph.

X300 Series IoT Cellular Gateway User Guide60

7: Status
Figure 7-5 shows a realtime connection graph for an idle gateway.
Figure 7-5 Realtime Connection Traffic Graph

WireGuard Status
This section displays the WireGuard VPN status, if it is configured and running.

X300 Series IoT Cellular Gateway User Guide61

7: Status

Load Balancing
Status > Load Balancing

Interface
Status > Load Balancing > Interface
The Interface page shows the MWAN interfaces, with active interfaces shown in green anddisabled interfaces shown in red. The uptime (hh:mm:ss) is displayed for active interfaces.

DetailStatus > Load Balancing > Detail
The Detail page shows MWAN interface (IPv4 and IPv6) details including interface status, current
policies, directly connected networks, and active user rules.

Diagnostics
Status > Load Balancing > Diagnostics
The Diagnostics page shows all configured MWAN interfaces and provides diagnostic commands
to check the health of the selected MWAN interface.
The following diagnostics commands are supported:Ping the default gateway

Ping tracking IPCheck IP rulesCheck routing tables



Hotplug ifupHotplug ifdown

To run a diagnostics command, select the interface and the task and click Execute.

Troubleshooting
Status > Load Balancing > Troubleshooting
The Troubleshooting page displays the output of the following IP commands:


ip a show

ip route show

ip route list table 1-250

iptables -L -t mangle -v -n

X300 Series IoT Cellular Gateway User Guide

62

8:

SystemThe System pages provide configuration for secure local and remote management of the gateway.
The System menu contains the following sections:

System

Administration

Software

Startup

Scheduled Tasks



LED Configuration

Backup / Flash Firmware

Custom Commands



RebootSystemSystem > System
This section contains settings that apply to the basic operation of the system, including thehostname, time zone, and system log configuration.

General Settings
System > System > General Settings
General settings let you configure local and router time, hostname, and time zone.
To configure general system settings:
1. Go to System > System > General Settings.
2. Enter the configuration settings. See Table 8-1.
3. Click Save & Apply.
Table 8-1 System General Settings
Parameters

Description

Local Time

Displays the local time of the user's computer. Sync the local time withbrowser or with an NTP server.
Click Sync with browser button to synchronize the gateway’s clockwith the local computer browser.
Click Sync with NTP-Server to synchronize the gateway’s clock withan NTP server.
Note: The displayed time is dependent on the configuration of yourlocal computer that is being used as an NTP server.

Router Time

Displays the current router time according to the configured time zone.

X300 Series IoT Cellular Gateway User Guide63

8: System

Parameters

Description

Hostname

Displays the hostname for this unit. Do not include the period character"." in the hostname as only the string before the period will be used as
the hostname.

Timezone

Select time zone according to the geographical region in which the unit
is deployed.
The default time zone is UTC.

Set Time Manually

Set the year, month, date, hour, minute and seconds.
Click Apply the time to save the information.

Logging
System > System > Logging
The system logger provides important debugging and monitoring capabilities. The system logs
capture traffic, system, and network activity. The logs are stored in RAM and are reset when thegateway is rebooted.
The system logs can be stored locally or sent to an external UDP or TCP syslog server for storage
and archival purposes.
To configure the system log settings:
1. Go to System > System > General Settings.
2. Enter the configuration settings (see Table 8-2).
3. Click Save & Apply.
Table 8-2 Syslog Configuration
Parameters

Description

System log buffer size

Enter the size of the buffer in Kilobytes (KB) to save logs and status
information details.
The default system log buffer size is 64 KB.
When the buffer is full, records will be overwritten on a first in, first out(FIFO) basis.

External system log serverEnter the IP address of an external syslog server to be used to save thereal time logs.
By default the logs are written to the local system.

External system log server port

Enter the UDP port number of the external syslog server.
The default port is 514.

External system log server
protocolProtocol of the external syslog server.

Write system log to file

File path and file name to write the log messages to.

UDP
If an external filesystem (SD card or USB flash drive) is mounted, add
the mount path and file name here. The logs display application (seeServices > Logs Information) will download the files written to this filepath.
Example: /mnt/usbdevice/log.txt

X300 Series IoT Cellular Gateway User Guide64

8: System

Parameters

Description

Log output level

Select the log severity output level. The level of severity progresses
from Info to Emergency. Lower severity levels are more verbose andwill include messages from all higher severity levels.
Log levels are listed in order of increasing severity: Debug – Provides debug messages used by the software developer

for debugging the application. These logs are typically not usefulduring operations.
 Info – Provides normal operational information messages that areused for general purposes like reporting.
 Notice – Provides alerts for peculiar events that are not an error.
These logs help to identify potential issues. Since these logs do notindicate errors, immediate action may/may not be necessary.
 Warning – Displays warning messages for a potential issue,
indicating to take an action. An error may occur if no action is taken
against the warning issued.
 Error – Displays the messages indicating an error condition.
 Critical – Indicates failure in secondary system and must be
corrected immediately.
 Alert – Problems which should be corrected immediately.
 Emergency – System is unusable.
Note: For help with log errors, contact Lantronix Technical Support.
Cron log level

Select the minimum level for cron messages to be logged to syslog.
 Debug – Helps to debug cron process which has failed duringruntime.
 Normal – Displays informational messages
 Warning – Indicates some issues can happen or error could be

generated in cron process.
Note: For help with Cron log warning messages, contact Lantronix

Technical Support.

Time Synchronization
System > System > Time Synchronization
Select the method that the gateway uses to synchronize its internal clock.
Note:
GSM.

If all three methods are enabled, the order of precedence is GPS, then NTP, thenTable 8-3 System Time Synchronization Configuration
Parameters

Description

GPS Time Synchronization

Select this option for the gateway to synchronize its internal clockusing GPS. To use this option, the gateway must support GPS.
Note: GPS antenna will be needed for GPS time sync.

Interval

The time in seconds to update time from the GPS frame.

Enable NTP client

This option enables the NTP client on the gateway to synchronize its
internal clock every 60 minutes from an NTP server. If enabled, enter
the NTP options as needed.
To use as NTP client, no change to the firewall is required.
Note: Enabling NTP Client consumes data.

X300 Series IoT Cellular Gateway User Guide65

8: System

Parameters

Description

Provide NTP serverThis option enables the NTP server on the gateway. The service will
respond to the local network with the time of the gateway.
To run as NTP server, open UDP port 123.
Disabled by default.

Use DHCP advertised servers

Enables or disables the use of DHCP-provided NTP servers.
Enabled by default.

NTP server candidates

Enter the pool of NTP servers to poll the time from.

GSM Time Synchronization

If enabled, the gateway will synchronize using GSM functionality.

Language and Style
System > System > Language and Style
The language and style settings are used to control the look and feel of the web interface.
Table 8-4 Language and Style Configurations
Parameters

Description

Language

Default value is auto.

DesignDefault design of user interface is Rosy.

Auto refresh default pollinterval Set the auto refresh polling interval between 5 and 50 seconds.
in seconds
Default is 5 seconds.
Note: Auto refresh can be turned on or off using the Auto Refresh
button on the UI.

Administration
System > Administration
The Administration page allows you to configure the unit’s password and SSH access to thedevice. You can configure various ports and login security.

Router Password
System > Administration > Router Password
This page allows you to change the login password of the current user. If you are logged in as
administrator, you can change the administrator password, and if you are logged in as root, you
can change the root password and the administrator password.
The password requirements are the following:Password must consist of at least 8 characters and include a minimum of the following:

1 uppercase character

1 lowercase character

1 numerical character (0-9)

X300 Series IoT Cellular Gateway User Guide66

8: System
1. Go to System > Administration > SSH-Keys.
2. Copy the public key from the host system and paste it in the input field. Alternatively, drag anddrop the SSH key file (.pub) into the input field.
3. Click Add key.

Software
System > Software
The software package manager lets you upgrade the system by installing, upgrading, or removing
software packages from package repositories that are local or on the Internet. The package
manager (opkg utility) attempts to resolve dependencies with packages in the repositories. If it
fails, it reports an error and aborts the installation of the package.
The software package manager is not used to upgrade system firmware (sysupgrade). For
firmware upgrade, see Backup / Flash Firmware.
The Software page displays the list of all packages or the packages that match the Filter criteria
according to the following categories (tabs).


Available - when selected, the table lists all packages that are available in the configured
repository. You can see if the package is installed, or if you have the option to install or
upgrade it.
Installed - when selected, the table lists the packages that are currently installed on thedevice. You can see the option to remove these packages.
Updates - when selected, lists the packages where an updated version is available, as longas you use a supported version of OpenWRT. If none are found, displays “No packages”.

The Software page is described in Table 8-6:
Table 8-6 Software Page
Parameters

Description

Free space

Indicates the available memory on the flash memory, as both apercentage and size in MB.
The darker line represents the portion of free space.

FilterFilters the package list. Type part or all of the package name in the filter
field.

Download and install package

Downloads and installs a package from the configured repository orfrom a custom feed. Enter the package name for a package in theconfigured repository or enter the URL for a package on a custom feed.

Actions
Update lists

Click to update the package list. The package manager needs thisinformation to install or upgrade packages or print information about
them. Run the the update command each time before you install a new
package.

Upload Package

Click to select the package to upload from the local machine.

Configure opkg

Click to modify the package manager configuration. See Configure
OPKG.

Package List

X300 Series IoT Cellular Gateway User Guide68

8: System

Parameters

Description

Package list

Displays the available, installed, or available for upgrade packages list.

Package name

Displays the name of package

Version

Displays the package version

Size (.ipk)

Displays the size of the installed package

Description

Displays the package description.

Installed (or action)

Displays “Installed” to indicate the package is installed, or displays therelevant action. The options are:Install - click to install the package
Upgrade - an upgrade package is available. Click to install the
package.
Remove - (on Installed tab). click to remove the package.

List the Packages
To view all packages in the configured repository:
1. Go to System > Software.
2. Click the Available tab. The packages are displayed. (Click the Installed tab to view the
installed packages only.)
3. Click the page back and page forward arrows (<< and >>) to view the list of packages.
To filter the package list by package name:
1. Go to System > Software.
2. Next to Filter, type part or all of the package name.
3. Click the Available, Installed or Updates tab. The packages that match the filter are displayed.
4. Click the page back and page forward arrows (<< and >>) to view the list of packages.

Update the List of Packages
The update command retrieves the list of packages. The package manager needs this information
to install or upgrade packages or print information about them. You should run the update
command before you install a new package.
To update the list of available packages:
1. Go to System > Software.
2. Click Update lists. The package manager updates the list of available packages.
3. Click Dismiss.
4. View the available packages.

Install a Package
To install a package:
1. Go to System > Software.
2. Click Update lists to refresh the list of available packages.

X300 Series IoT Cellular Gateway User Guide69

8: System
3. Do one of the following:Click the Available tab, select the package (or filter the list and select the package) andclick Install.
Under Download and install package, enter the package name for a package on thedownload server, or enter the URL for a package on a custom feed, and click OK.
Click Upload Package, to select the package from the local machine, and click Upload.

4. The package manager displays the package details including the following:version of the package

size of installed package

list of dependent packages, with installation status and size if not installed

package description

space required and the number of packages to install

A warning message is displayed if the installed packages are incompatible with therequired packages.
The option to Overwrite files from other package(s). By default, it is not selected.

5. Review the package details. Ensure the device has adequate space available to install therequired packages. If desired, select Overwrite files from other package(s).
6. Click Install.
7. The package manager displays the installation progress and error messages, if applicable.
Click Dismiss when finished.
8. Refresh the web page and view that the package is listed as “Installed” in the list of Available
packages. You may need to restart the device, depending on the package and its use.

Upgrade a Package
To upgrade a package:
1. Go to System > Software.
2. Click Update lists to refresh the list of packages.
3. Do one of the following:Click the Available tab, select the package (or filter the list and select the package) andclick Upgrade.
Under Download and install package, enter the package name for a package on thedownload server, or enter the URL for a package on a custom feed, and click OK.
Click Upload Package and browse to select the package from the local machine.

4. The package manager lists the package details including the following:version of the package

size of installed package

package description

space required and the number of packages to install

X300 Series IoT Cellular Gateway User Guide70

8: SystemA warning message is displayed if the installed packages are incompatible with therequired packages.

5. Review the package details. If desired, select Overwrite files from other package(s).
6. Click Install.
7. The package manager displays the installation progress and error messages, if applicable.
Click Dismiss when finished.
8. To verify, refresh the web page and view that the package is listed as “Installed” in the list of
Available packages. You may need to restart the device, depending on the package and its
use.

Remove a Package
To remove a package:
1. Go to System > Software.
2. Click the Installed tab, select the package (or filter the list and select the package) and click
Remove.
3. Review the package details, including the following:version of the package

size of installed package

description of the packageThe option to Automatically remove unused dependencies box (checked by default). To
keep all dependent packages, clear this box.

4. To continue, click Remove.
5. The package manager displays the progress and error messages, if applicable. Click Dismiss
to close the dialog.

Configure OPKGThe OPKG configuration files define the configuration and feed locations used by the OPKG
package manager. It includes the following configuration files:

opkg.conf – This configuration file sets the default folders.



opkg/customfeeds.conf – This file is used to add your custom package feeds (repositories).



opkg/distfeeds.conf – This file is used to set the feeds. By default, it provides the path to theLantronix package server.

To modify the OPKG configuration:
1. Go to System > Software.
2. Click the Configure opkg button.
3. Modify the OPKG configuration (see Table 8-7).
4. Click Save.

X300 Series IoT Cellular Gateway User Guide71

8: System
Table 8-7 OPKG Package Manager Configuration
Parameters

Description

opkg.conf

The default configuration is shown: dest root / dest ram /tmp

 lists_dir ext /var/opkg-lists

 option overlay_root /overlay option check_signature

The options can be left at the default value.
customfeeds.conf

Enter each custom package feed on its own line.
The feed can be on a remote server, in a version control system, on thelocal file system, or in any location addressable by a single name (path/
URL) over a protocol with a supported feed method.
An example format is provided:# src/gz example_feed_name http://www.example.com/path/to/files
Remove the “#” (hash symbol) at the start of the line.

distfeeds.conf

Displays the Lantronix package feeds repository.
The feed can be on a remote server, in a version control system, on thelocal file system, or in any location addressable by a single name (path/
URL) over a protocol with a supported feed method.

Startup
System > Startup

Initscripts

System > Startup > Initscripts
Init scripts are run to start required processes during the boot process. The web interface lets you
view and enable or disable installed init scripts. Reboot the gateway for the changes to take effect.
Note: Disabling an essential script such as a network script may cause your device tobecome inaccessible.
Enable and Disable actions enable or disable the initscript.

Start, Restart, and Stop actions perform the specified action on the process immediately.

Table 8-8 describes the initscripts.
Table 8-8 Initscripts Actions
Parameters

Description

Start priority

Displays the priority of when the initscript is run during startup. Order ofpriority is from 00 to 99.

Initscript

Displays the name of the initscript

Enable/Disable

Displays the current state as Enabled or Disabled. Click the button todisable or enable the initscript.

Start

Starts the initscript immediately

X300 Series IoT Cellular Gateway User Guide72

8: System

Parameters

Description

RestartRestarts the initscript immediately

Stop

Stops the initscript immediately

Local Startup

System > Startup > Local Startup
The local startup file (/etc/rc.local) contains custom commands that are run at the end of the bootprocess, after the system is initialized. By default, it is empty.
To configure the local startup file:
1. Go to System > Startup > Local Startup.
2. In the editor, type custom commands on any line before the line “exit 0”. Make sure that the fileends with the line “exit 0”.
3. Click Save.
Changes will take effect on the next reboot.

Scheduled Tasks
System > Scheduled Tasks
This feature lets you schedule cron jobs to run at a fixed time, date, or interval.
Enter each task on a separate line in the crontab file. Tasks are specified using the following
syntax:* * * * * command to execute- - - - | | | | •----day of the week (0-6) (Sunday=0)| | | •------month (1-12)| | •--------day of month (1-31)| •----------hour (0-23)•------------min (0-59)
To configure scheduled tasks:
1. Go to System > Scheduled Tasks.
Note: If the editor is empty, you must restart the cron service before creating ascheduled task. To restart the cron service, go to Services > Service Actions in the
web interface.
2. Enter the cron task according to the syntax described above. Table 8-9 lists available
shortcuts.
3. Click Save.
Table 8-9 Cron Shortcuts
ShortcutEquivalent

Description@reboot(none)

At system startup@yearly

0011*

Every year

X300 Series IoT Cellular Gateway User Guide73

8: System

Parameters

Description

RestartRestarts the initscript immediately

Stop

Stops the initscript immediately

Local Startup
System > Startup > Local Startup
The local startup file (/etc/rc.local) contains custom commands that are run at the end of the bootprocess, after the system is initialized. By default, it is empty.
To configure the local startup file:
1. Go to System > Startup > Local Startup.
2. In the editor, type custom commands on any line before the line “exit 0”. Make sure that the fileends with the line “exit 0”.
3. Click Save.
Changes will take effect on the next reboot.

Scheduled Tasks
System > Scheduled Tasks
This feature lets you schedule cron jobs to run at a fixed time, date, or interval.
Enter each task on a separate line in the crontab file. Tasks are specified using the following
syntax:* * * * * command to execute- - - - | | | | •----day of the week (0-6) (Sunday=0)| | | •------month (1-12)| | •--------day of month (1-31)| •----------hour (0-23)•------------min (0-59)
To configure scheduled tasks:
1. Go to System > Scheduled Tasks.
Note: If the editor is empty, you must restart the cron service before creating ascheduled task. To restart the cron service, go to Services > Service Actions in the
web interface.
2. Enter the cron task according to the syntax described above. Table 8-9 lists available
shortcuts.
3. Click Save.
Table 8-9 Cron Shortcuts
ShortcutEquivalent

Description@reboot(none)

At system startup@yearly

0011*

Every year

X300 Series IoT Cellular Gateway User Guide73

8: System

ShortcutEquivalent

Description@annually

0011*

Every year

@monthly

001**

Every month@weekly

00**0

Every week@daily00***

Every day@midnight

00***

Every day@hourly0****

Every hour

LED Configuration
System > LED Configuration
The X300 series gateway provides 7 LEDs to indicate status and activity. For a description of thedefault LED behaviors, see LEDs.
The LED can be controlled by various system events, which is selected by the trigger option.
Depending on the trigger, additional options must be specified. See Table 8-10 which lists sometrigger descriptions. The UI displays some triggers not listed in the table, but these are notrecommended to be used.
Note: LED configuration should be done by experienced personnel. Use care whenmodifying the LEDs as improper configuration may cause LED indicators to be misread or
missed.
Table 8-10 Trigger Descriptions
Trigger

Description

Examplesnone

The LED is always in the default state.
This is useful to declare an LED to bealways ON.

LED always on: LED name: any LED
 Default: On
 Trigger: nonetimer

The LED blinks with the configured On/
Off frequency.

LED is 100ms On / 200ms Off:

Options:

 Default: On On-state delay: time in milliseconds

 Trigger: timer

that the LED is On.
 Off-state delay: time in milliseconds

 LED name: any LED On-State Delay: 100
 Off-State Delay: 200

that the LED is Off.
defaulton

This trigger option is deprecated. Use
trigger = none and default = On instead.

heartbeat

The LED flashes to simulate actual
heartbeat thump-thump-pause. The
frequency is in direct proportion to 1minute average CPU load.

X300 Series IoT Cellular Gateway User Guide

LED blinks in heartbeat pattern: LED name: any LED
 Default: Off
 Trigger: heartbeat74

8: System

Trigger

Description

Examplesnetdev

Network Activity
The LED flashes with link status and/or
send and receive activity on theconfigured interface.

LED blinks when there is a link, transmit
or receive activity on the configured
network interface (WWAN, LAN,
cellular).

Options:

 LED name: X300-wwanactivity, X300-

 Device: name of the network interface

whose status will be indicated Mode: link, transmit, receive. One ormore can be selected

usbdev
usbportlanactivity, or X300-network
 Default: Off
 Trigger: netdev
 Device: select the configured interface(for example, “Ethernet adapter: eth1”
for WAN) Mode: Link, Transmit, Receive

The LED turns on if a USB device isconnected. It is recommended to use
usbport rather than usbdev.

LED turns on if USB device is connected.

Options for usbport:

 Trigger: usbport

 USB Port: select the configured USB

 USP Port: Portusb1-port2

 LED name: Default: Off

port
Options for usbdev:
 USB device: select the configured

USP device

To configure the user-programmable LED:
1. Go to System > LED Configuration.
2. Click Add LED action or click Edit next to the existing LED action that you want to modify.
3. Enter or modify the configuration settings. See Table 8-11.
4. Click Save.
5. Click Save & Apply.

Table 8-11 LED Configuration
Parameter

Description

Name

Displays the descriptive name of the LED.

LED Name

Displays the LED name by function.

Default state

Displays the default state of the LED before the trigger.
Options are On or Off.

Trigger

Displays the trigger event that will toggle the LED state. For
descriptions, see Table 8-10.

Backup / Flash Firmware
System > Backup / Flash Firmware

X300 Series IoT Cellular Gateway User Guide75

8: System
This page allows you to perform system operations such as backup and restore, reset, and flash
firmware (system upgrade) to keep the device healthy.
The system operations are described in Table 8-12.
Table 8-12 Backup and Restore / Flash Firmware Operations
Parameters

Description

Backup/Restore
Download Backup

Click Generate archive button to download an archive file of thecurrent configuration files.
Authentication  Confirm user password - enter the password of the logged in user.
 Set Password - enter a password to protect the backup archive.

Reset to defaults

Click Perform Reset button to reset the device to its initialconfiguration after flashing the firmware. This removes settings anduser-installed software packages, which are stored on the overlayfs
configuration partition. It works with any install with a squashfs /overlayfs setup.
Authentication  Confirm user password: enter the password of the logged in user.

Restore backup

Click Upload archive button to upload a previously generated backup
archive.
Authentication  Enter backup archive password - Enter the password that was

created to download the backup archive.
The validity of the backup archive is checked and the files in the backup
archive are listed. Review the list of files before you continue or cancel
the restore operation.
Flash image
Image

Click Flash image button to upload a sysupgrade compatible image forreplacing the running firmware.
Warning:

Do not power off the device during the update.

When the image file is uploaded, a file integrity check is done throughthe use of md5 algorithm. Verify the md5 value with the one given alongwith the firmware file.
Keep software packages, settings, and current configuration - Thisis selected by default. To retain installed software packages (IPKs),
settings, and current configuration, leave it selected. If you deselect it,
the device configuration will be reset to factory setting after updating to
the new firmware.
Warning:
Software packages are only restored from configured
repositories. The device will automatically reboot when packages
are restored.
Authentication  Confirm user password and continue - Enter the password of thelogged in user.

Backup and Restore

X300 Series IoT Cellular Gateway User Guide76

8: System
Download backups to keep the working configuration data. The backup consists of all policies andall other user related information.
Restore backups to restore configuration on the router or to configure a new router with the samesettings.
To generate a backup archive:
1. Go to System > Backup/Flash Firmware > Actions.
2. Click the Generate archive to download a backup file.
3. At Confirm user password, enter the password of the logged in user. Click Proceed.
4. At Set Password, enter a password to protect the backup file. Click Download.
5. The backup archive is generated and downloaded to the local download folder.
To restore a backup archive:
1. Go to System > Backup/Flash Firmware > Actions.
2. Click Upload archive to restore a backup archive.
3. At Enter backup archive password, enter the password that was created to secure the backup
archive. Click Proceed.
4. Select the backup archive file to upload. Click Upload.
5. The validity of the backup archive is checked and the files in the backup archive are listed.
Review the list of files. Click Continue to proceed.
The configuration is applied and the device reboots. If the restored configuration changes thecurrent LAN IP address, you may need to reconnect manually.

Reset to Defaults
A factory reset erases all user-installed packages and settings and returns the device to its initialstate after installing the firmware. The X300 series devices use a squashfs file system, as required
for this feature.
To reset the firmware:
1. Go to System > Backup/Flash Firmware > Actions.
2. Click Perform reset.
3. At the Authentication prompt, enter the password of the logged in user. Click Proceed. The
system erases the configuration partition and then reboots.
4. Access the device using the default configuration.
Factory Reset using Reset Button
The device has a physical reset button which can be used to reset the operating system to default
settings without serial or SSH access. The recessed Reset button is located below the power input
connector on the front panel of the device.
To reset the device using the reset button:
1. Using a paper clip or similar object to carefully poke through the RESET hole, press and holdthe reset button for more than 5 seconds and less than 20 seconds.
2. Release the button. The device will do a factory reset and then reboot. This operation may

X300 Series IoT Cellular Gateway User Guide77

8: Systemtake a few minutes to complete.
3. Connect to the device using the default configuration.
Note: To reboot the device using the reset button, press and hold the reset button
between 1 to 5 seconds.

Firmware Upgrade
Flash firmware (system upgrade) optionally saves specified configuration files, wipes the entire filesystem, installs the new version, and then restores the saved configuration files. Any parts of thefile system that are not specifically saved will be lost.
To retain the configuration, settings, and user-installed software packages, select “Keep software
packages, settings, and current configuration” when you flash the firmware. For more details, see
Restoring IPKs after Firmware Upgrade on the Device.
To do a firmware upgrade:
1. Go to System > Backup/Flash Firmware > Actions.
2. Click Flash image.
3. Select the file to upload and click Upload. The system confirms the upload and displays the
flash image size and checksum. Verify the firmware image checksum.
4. Keep software packages, settings, and current configuration - This is selected by default.
Leave it selected to retain installed software packages (IPKs), settings, and current
configuration. If you deselect it, the device configuration will be reset to factory setting anduser installed software packages will be removed after updating the firmware.
5. At the Authentication prompt, enter the user password.
6. Click Continue to proceed with flashing the image.
7. Do not power off the device while the upgrade is in progress. This may take a couple minutes.
After the upgrade completes, the device will reboot. You may need to renew the IP address inyour browser to reach the device again.
Restoring IPKs after Firmware Upgrade on the Device
To ensure that previously installed software packages and their configurations are retained whenupgrading the firmware, follow the flash firmware procedure and make sure that “Keep software
packages, settings, and current configuration” is selected.
The device will automatically reboot after packages are restored. To verify that the packages havebeen restored, go to System > Software > Installed to view the installed packages.
Note: Software packages are only restored from configured repositories. Repositories
can be configured from System > Software > Configuration. See Configure OPKG.

X300 Series IoT Cellular Gateway User Guide78

8: System

Configuration
System > Backup / Flash Firmware > Configuration
Add files and directories that should be preserved during a system upgrade to the backup file list.
Modified files in /etc/config/ directory and certain other configurations are automatically preserved.
To show the current backup file list, click Open list...
To modify the backup file list:
1. Go to System > Backup/Flash Firmware > Configuration.
2. In the editor, place the cursor below the last line.
3. Enter file path for each file or directory on a new line. The file path is relative to the top level
directory.
4. Click Save.

Firmware and Configuration Upgrade from SD Card / USB Device
The external file system (SD card / USB storage device) can be used to upgrade the firmware andapply the configuration when the device boots. This option can be useful for initial setup ofdevices.
During the device boot, the firmware on the SD card or USB device will be applied only if thefirmware in the external file system is newer than the current firmware in the device. If the firmware
upgrade is successful, the system looks for a configuration file. If the configuration file is present,
then the configuration will be applied. No version checks are done on the configuration file.
Note:
fail.

If the external file system has two firmware (.rom) files, the firmware upgrade will

Firmware FileUse a valid firmware image with .rom extension that is appropriate for the device model.
Use a released firmware image as provided (downloaded from the Lantronix Tech Support webstie) or an SDK built firmware image that adheres to the file name format below:
The file name format must be: ${devmodel}_<version>.rom<version> format: a.b.c.dRx
a is major version number
b is minor version number
c is OEM version number (Example: 0) - to denote a version built specifically for OEM purposesd is maintenance version number (Example: 0) - to denote a patch fix, no major or minor changes
to firmware
Rx is (R) is release candidate and x is a number up to 4 digits indicating the revision number of the
R build
Configuration File
The configuration file name format must be one of the following:
config-devicemodel-version.tar.gz
backup-devicemodel-version.tar.gz

X300 Series IoT Cellular Gateway User Guide79

8: System
The backup archive can be retrieved using the Generate Archive command on the System >Backup/Flash Firmware page. Note that the backup archive is password protected. If the backup
archive is used, the password protection must be removed from the archive because there is no
mechanism to supply or enter the password when upgrading from the SD card/USB device.
To upgrade the firmware and configuration file from the external file system:
1. Copy the firmware file (.rom) and configuration file (.tar.gz) onto the external file system (SDcard / USB).
2. Connect the external file system to the device.
3. Reboot the device to upgrade the firmware and configuration files.
4. After upgrading the firmware and/or configuration, the device will reboot automatically toindicate that the installation is complete. Remove the SD card/USB from the device.

Custom Commands
System > Custom Commands
Write and execute custom shell commands from the web interface.

Write Custom Shell Command
This page lets you add or delete custom shell commands.
To write a custom shell command:
1. Go to System > Custom Commands > Configure.
2. Click Add.
3. Enter the command details. See Table 8-13.
4. Click Save or Save & Apply.
The commands will be visible on the dashboard where you can run them.
Table 8-13 Custom Commands Configuration
Parameter

Description

Description

A short text description of the command.

Command

The command to execute on the shell terminal.
To specify a file to be executed, the file must be copied to the /usr/sbin
directory on the gateway. Files not in env PATH require the complete
file path and should be executable.

Custom arguments

Check the box to allow user to provide additional command line
arguments while running this command.

Public access

Check the box to allow the command to be executed and the output
downloaded without prior authentication.

Run Custom Shell Command
Run custom shell commands. You also have the option to download the results of the command.

X300 Series IoT Cellular Gateway User Guide80

8: System
To run a custom command:
1. Go to System > Custom Commands > Dashboard.
2. Select the command to be run and click Run.
The command, result, and return code are displayed in a box below the custom command.

RebootSystem > Reboot
Perform a reboot of the gateway. The gateway will restart and reload the configuration. Any
unsaved configuration will be lost when the gateway is rebooted.
To reboot the gateway:
1. Go to System > Reboot.
2. Click Perform Reboot.
The gateway will restart and reload the configuration. After the gateway reboots, the login page will
be displayed.

Schedule a Reboot
Schedule times when the gateway will reboot itself. You can set the frequency by time of day (hourand minute), day of week, and day of month.
The scheduled item must be enabled in order for the gateway to reboot itself.
To configure the reboot schedule:
1. Go to System > Reboot > Schedule Reboot.
2. Click Add.
3. Enter the schedule details (see Table 8-14).
4. Click Save.
Table 8-14 Schedule Reboot Time Specification
Parameter

Description

MinuteRange: 0-59

Hour

Range: 0-23
0 = midnight

Day of week

Range: 0-6
0 = Sunday

Date

1-31

Month

Range: 1-12

X300 Series IoT Cellular Gateway User Guide

81

9:

VPN
This chapter describes how to establish a VPN connection for the following VPN protocols:IPsec (Internet Protocol Security)



OpenVPN



WireGuard VPN

Note: The X300 series gateways support additional tunneling protocols. For L2TP,
PPtP, or GRE protocol configuration, see Add Virtual Interface.

IPsec (Internet Protocol Security)
VPN > IPsec
The IP Security (IPsec) suite of protocols are designed for cryptographically securecommunication at the IP layer. The gateway uses standard IPsec protocol to protect traffic. The
identity of communicating users is checked with the user authentication based on pre-shared keys
(PSK) or X.509 certificates.
The IPsec VPN instance can be started or stopped from the Web UI or by sending an SMS
AT+VPN command. See Table 10-16 SMS AT Command Syntax.
You can configure a router-to-router VPN connection.
To configure an IPsec instance:
1. Go to VPN > IPsec, and click Add.
2. Under Gateway to Gateway, click Add.
3. Enter the VPN configuration details on the General Settings (Table 9-1) and Advanced
Settings (Table 9-2) tabs.
Table 9-1 IPsec General Settings
Parameters

Description

Profile NameEnter the Profile Name to identify the router–to-router IPsec VPN
connection.

ProtoType

Gateway to Gateway is selected.

EnableCheck to enable the connection.

Remote IPsec routerEnter the remote WAN IP Address or domain name of the remote IPsec
router server.

Remote AddressEnter the remote LAN IP Address and subnet of the remote IPSEC
router server for use on the VPN connection.

Remote ID

Enter the ID of the remote network as configured on the remote IPsec
router server.

MethodSelect the interface used to establish the tunnel.
 Static – indicates that you will specify the interface to be used toestablish the tunnel
 Auto – uses the interface that is active from the Load Balancer(MWAN) policies

X300 Series IoT Cellular Gateway User Guide82

9: VPN

Parameters

Description

Route

Available if Static is selected in Method field.
Select the interface used to configure IPsec:
 Wifi Cellular

PolicyAvailable if Auto is selected in Method field.
Select the MWAN policy to use.

Interface

Displays the IP address of the interface used for the VPN connection.

Local AddressEnter the local network IP Address and subnet mask of the router foruse on the VPN connection.

Local IDEnter the ID of the local router as configured on the remote IPSEC
router server. Note: On the remote server, it may be displayed as"remote ID."

Key Mode

Select the type of Key mode in use for VPN connection:
 Pre shared Key X.509 certificate

Preshared-Key

This field is available if Pre shared Key is selected in the Key Mode
field.
Enter the key. The peer uses the key to authenticate each other fromInternet Key Exchange.

Cert.

This field is available if X.509 Certificate is selected in the Key Mode
field.
The certificate file must be uploaded to the /etc/ipsec.d/certs directory.
Click Select file... to browse the local drive and select the file.
Click Upload file... to upload the file.
After the file is uploaded, the Cert. field displays the file name and timestamp of the upload.
To delete a file, click Delete.

Key

This field is available if X.509 Certificate is selected in the Key Mode
field.
The key file must be uploaded to the /etc/ipsec.d/private directory.
Click Select file... to browse the local drive and select the file.
Click Upload file... to upload the file.
After the file is uploaded, the Key field displays the file name and timestamp of the upload.
To delete a file, click Delete.

CA Cert.

This field is available if X.509 Certificate is selected in the Key Mode
field.
The CA certificate file must be uploaded to the /etc/ipsec.d/cacerts
directory.
Click Select file... to browse the local drive and select the file.
Click Upload file... to upload the file.
After the file is uploaded, the CA Cert. field displays the file name andtime stamp of the upload.
To delete a file, click Delete.

X300 Series IoT Cellular Gateway User Guide83

9: VPN

Parameters

Description

Single hop IP for watchdog

Enter the IP address to be used for monitoring purposes. The
application will ping the IP defined here. If the ping fails, it will restartthe device. This could be the LAN IP address of the IPsec routerserver.

Monitor interface ping failure

Select Yes to ping the IP address defined in Single hop IP for
watchdog.
Select No if you don't want the monitor interface to ping the single hop
IP address.
The default is No.

Table 9-2 IPsec Advanced Settings
Parameters

Description

IKE Mode

Select the mode that Internet Key Exchange (IKE) protocol uses toauthenticate and/or encrypt the peers.
 Main Aggressive

Key Exchange

Select the mode of encryption key exchange between two
communicating peers:
 IKEV1
 IKEV2 The default mode is IKEV1.

IKE Encryption

Select the cipher type to use for the Internet Key Exchange (IKE):
 Any
 AES
 AES-128
 AES-192
 AES-256
 3DES DES

The default cipher type is “Any”.
IKE Hash

The IKE hash is used for authentication of packets for the key
exchange.
Select the IKE Hash type to use for VPN connection:
 Any
 MD5
 SHA1 SHA2 256
 SHA2 384
 SHA2 512

The default IKE hash type is “Any”.

X300 Series IoT Cellular Gateway User Guide84

9: VPN

Parameters

Description

IKE DH Group

Select the desired Diffie-Hellman group to use:
 Any
 Group 1 (768) Group 2 (1024)
 Group 5 (1536)
 Group 14 (2048)
 Group 15 (3072)
 Group 16 (4096)

Higher-numbered groups are more secure but also require longer togenerate the key.
The default group is “Any”.
IPsec Encryption

Select the type of IPsec encryption for VPN connection:
 Any
 AES
 AES-128
 AES-192
 AES-256
 3DES DES

The default cipher type is “Any”.
IPsec Hash

The IPsec hash is used for authentication of packets for the key
exchange.
Select the IPsec Hash type to use for VPN connection:
 Any
 MD5
 SHA1 SHA2 256
 SHA2-384
 SHA2-512

The default hash type is “Any”.
DH Group

Select the desired Diffie-Hellman group to use:
 Any
 Group 1 (768) Group 2 (1024)
 Group 5 (1536)
 Group 14 (2048)
 Group 15 (3072)
 Group 16 (4096)
 Group 17 (6144)
 Group 18 (8192)

Higher-numbered groups are more secure but also require longer togenerate the key.
The default group is “Any”.
DPD Keep Alive TimeEnter the time in seconds for interval between Dead Peer Detection
keep alive messages.

DPD Timeout

Enter the time in seconds of no response from peer before Dead Peer
Detection times out.

IKE Re-key TimeEnter the time in seconds between changes of the encryption key. To
disable changing the key, set it to 0.

SA Life TimeEnter the time in seconds for the security association lifetime.

X300 Series IoT Cellular Gateway User Guide85

9: VPN

Parameters

Description

DPD Action

Select the desired Dead Peer Detection action. This action must be
taken when a dead IKE peer is detected.

4. Click Save. The instance is saved and displayed on the IPsec page.
5. After configuring the profile, click Connect to start the IPsec connection for the first time.

OpenVPN
VPN > OpenVPN
OpenVPN is an open-source software application that implements virtual private network (VPN)
techniques for creating secure point-to-point or site-to-site connections. It uses the OpenSSL
library to provide encryption of both the data and control channels. OpenVPN can run over UDP or
TCP transports, multiplexing created SSL tunnels on a single TCP/UDP port.
OpenVPN fully supports IPv6 as the protocol of the virtual network inside a tunnel and the
OpenVPN applications can also establish connections via IPv6. It has the ability to work throughmost proxy servers (including HTTP) and is good at working through network address translation(NAT) and getting out through firewalls. The server configuration has the ability to push certain
network configuration options to the clients, including IP addresses, routing commands, and a few
connection options.
The X300 series gateways support OpenVPN client, server, and pass through.

OpenVPN Instances
The OpenVPN client will attach itself to the configured OpenVPN server over any available WAN,
LAN, or Cellular network interface. If the auto-connect function is enabled, OpenVPN will connect
over available WAN, switch between WAN connections when one WAN fails-over to another, andalso auto start on every reboot.
To create an OpenVPN instance:

X300 Series IoT Cellular Gateway User Guide86

9: VPN
1. Go to VPN > OpenVPN. The following page is displayed:

2. Under OpenVPN instances, select the method for the instance configuration:
Template based configuration – Select the instance name and the template (server orclient templates are provided). Click Add.



OVPN configuration file upload – Select the instance name and then choose the OVPN
configuration file. Click Upload.

3. The instance is added to the list under OpenVPN instances.
4. Choose from the following options:

To continue configuring the instance, click Edit. See Template-based Configuration or
OpenVPN Configuration File for details respective to the configuration method.

To enable the instance, select Enabled.

5. Click Save & Apply.
Note:

You must manually enter the DNS from Network > DHCP and DNS.

X300 Series IoT Cellular Gateway User Guide87

9: VPN

Template-based Configuration
Predefined templates
Use the following predefined server and client templates to create the initial configuration of the
OpenVPN instance:

Client configuration for an ethernet bridge VPNClient configuration for a routed multi-client VPN

Simple client configuration for a routed point-to-point VPNServer configuration for an ethernet bridge VPNServer configuration for a routed multi-client VPN

Simple server configuration for a routed point-to-point VPN

Note: This document does not cover OpenVPN client/server configuration. Please
consult your administrator for configuration details of your VPN or refer to the OpenVPN
online documentation for information on how to configure the VPN.
Edit the template-based configuration
After you add the template-based instance, you can edit the instance to configure the appropriate
fields and values for the particular VPN connection.
Note the following about editing the template-based instances:

Click the Switch to advanced configuration or Switch to basic configuration links at the
top of the form to switch the view between basic and advanced configuration.



Select Additional Field at the bottom of the form to select additional configuration fields to
add to the form.



Select Client to enable client mode, or leave it blank to enable server mode.

You should add your CA, certificates, and keys for the instance.



Click Save & Apply when you are finished.

OpenVPN Configuration FileIf you use an OVPN configuration file to configure the OpenVPN instance, the configuration fileshould contain settings for either a server configuration or a client configuration with .ovpn as thefile extension.
Note: This document does not cover how to create OpenVPN configuration files. Pleaserefer to the OpenVPN online documentation for sample server and client configuration
files and information on how to create configuration files.
Edit the OVPN Configuration File
After you upload the configuration file, you can use the OpenVPN configuration editor on the webinterface to modify the configuration. The editor window contains two sections: one to modify the
OVPN configuration file and one to add a user and password authentication file with yourcredentials.
Click Save to save changes to the configuration file and close the editor.

X300 Series IoT Cellular Gateway User Guide88

9: VPN

WireGuard VPN
The WireGuard® VPN feature is available as a software package (IPK), and is not part of thestandard firmware. Install it using the software package manager.
WireGuard is an open source software VPN protocol that can be deployed for many different
circumstances. It’s intended to be fast, secure, and easy to deploy. WireGuard securely
encapsulates IP packets over UDP. WireGuard relies on public key cryptography. It requires
generating a private and public key for each peer and exchanging only the public keys. WireGuardis time sensitive and can refuse to pass traffic if the peer’s clock is out of sync. It’s recommended
to rely on NTP for all peers.
Refer to the following procedures to establish a VPN connection using WireGuard VPN protocol.
On successful connection, the devices in the selected firewall zone can communicate with peer
devices using their WireGuard interface IP addresses.

Install WireGuard IPKs to the Device
Install the WireGuard VPN software packages (IPKs) using the software package manager.
To install the WireGuard VPN feature:
1. Go to System > Software.
2. Click Update lists to refresh the list of packages.
3. In the Filter field, type “wireguard”. The WireGuard packages are listed under Available
packages. The package names are as follows:

luci-app-wireguardluci-proto-wireguard



wireguard-tools

kmod-wireguard

4. Select “luci-app-wireguard” from the list and click Install.
5. The package manager displays the package details. Review the package details and ensurethat the device has adequate available memory to install the packages. Note that the other 3
WireGuard packages are listed under Dependencies as “not installed”. The package manager
will install all 4 packages.
6. Leave “Overwrite files from other package(s)” unchecked and click Install.
7. The package manager executes and displays the installation progress and results. Click
Dismiss when finished.
8. Restart the device.

Generate Private and Public Keys for WireGuard
Generate a pair of private and public keys for the WireGuard server.
To generate the private and public keys, SSH to the device and execute the commands:
root@Lantronix-<hostname>:~# umask go=
root@Lantronix-<hostname>:~# wg genkey | tee wgprivate | wg pubkey >wgpublicroot@Lantronix-<host-name>:~# cat wgprivate<output of wgprivate key>root@Lantronix-<host-name>:~# cat wgpublic

X300 Series IoT Cellular Gateway User Guide89

9: VPN<output of wgpublic key>
Use the wgprivate key file to configure the WireGuard interface on this device.
Use the wgpublic key file to configure peers that will connect to this device through the
WireGuard VPN.

Create the WireGuard VPN Interface
For details about configuring the WireGuard VPN protocol of the virtual interface, see Table 11-10,“VPN Tunnel Protocols,” on page 155.
To create the WireGuard VPN interface:
1. Go to Network > Interfaces. Click Add new interface.
2. Enter the following information on the General Settings tab:

Name: “wg0”Protocol: select WireGuard VPN, then click Create interface.

Private key: <private key of the device> (enter the value of wgprivate)Listen Port: 51820



IP Addresses: WireGuard interface IP addresses. (for example: 192.168.9.1/24)

3. Click the Firewall Settings tab. Enter the following information:Create/Assign Firewall zone: Select the “lan” zone to allow peer devices to communicate
with lan zone devices.

4. Click the Peers tab and click Add Peer. Enter the following information. (Repeat this step to
add multiple peers):Description: type “peer_1” (or a name you choose)

Public key: enter the public key of the peer device/hostAllowed IPs: “0.0.0.0/0”, “::/0”



Endpoint Host: IP address of the peer device/host (for example: 192.168.9.2/24)

Endpoint Port: 51820

Persistent Keep Alive: 25

5. To save the configuration, click Save and then click Save & Apply.

Configure a Firewall Rule to Allow WireGuard Traffic
The rule will allow access to the VPN server from the WAN zone.
To configure the firewall rule:
1. Go to Network > Firewall > Traffic Rules. Click Add.
2. Enter a name such as “allow_wireguard”.
3. Configure the rule to accept UDP traffic from any source address/port in the wan zone to UDP
port 51820 (any destination address) in the lan zone.
Protocol: UDP

Source zone: wan

Source Address: any

X300 Series IoT Cellular Gateway User Guide90

9: VPN



Source Port: anyDestination zone: lan wg0

Destination Address: anyDestination Port: 51820



Action: accept

4. To save the configuration, click Save and then click Save & Apply.

Monitor Status
To view information about the WireGuard VPN:
1. Go to Status > WireGuard Status.
2. View the client’s information and connectivity status.

Create a WireGuard Interface on the Peer Device
Create a WireGuard interface on the peer device by providing the public key (wgpublic) created in
Generate Private and Public Keys for WireGuard and the device’s WAN IP address.
Ensure that the WireGuard interface IP address of the device and the WireGuard interface IP
addresses of the peer devices are in the same subnet. (For example, IP of device is 192.168.9.1/
24 and IP of peer device is 192.168.9.2/24.)
Repeat this step for all peers that were added in Create the WireGuard VPN Interface.

X300 Series IoT Cellular Gateway User Guide9110: Services
The X300 series gateways are equipped with services that complement the routing features.
These services include:

Agents

Page Selector



DOTA



Reporting Agent

Dynamic DNSService Actions

External Filesystems



SMS



GPS*



SNMPD



Keepalived



SNMPTRAPD



Logs Information

uHTTPdAgentsServices > Agents
Agents are customized applications loaded on the gateway that communicate with a specificdevice or data management platform.
By default, the Lantronix Wireless Automation Server (MWAS) agent is loaded on the gateway,
which facilitates bi-directional data communication between devices/PLCs (Programmable Logic
Controllers) connected to the gateway and a centralized server through a Kalkitech-compatible
server.
[Device/SCADA <=> Kalkitech(sever)] <=> [MWAS(agent) <=> Device/PLC]
Table 10-1 Agent Configurations
Parameters

Description

AgentsSelect the Agent from the list:
 MWAS – Lantronix Wireless Acquisition System

EnableClick to enable the selected agent.

LAN IP/URLEnter the IP address of the field device (PLC).

LAN PORTEnter the port number of the field device (PLC).

WAN IP/URLEnter the IP address of the WAN server.

WAN PORTEnter the port number of the WAN server.

Enable WAN Backup IP

Click to enable the backup server. If enabled, enter the following: Backup WAN IP/URL – Enter the IP address of backup WAN server.
 Backup WAN Port – Enter the port number of backup WAN server.

X300 Series IoT Cellular Gateway User Guide9210: Services

DOTA
DOTA (download over the air) allows you to remotely update the gateway’s firmware using theLantronix server or your custom server.

Lantronix Server
Services > Dota > Lantronix ServerThis page allows you to update the gateway’s firmware using the Lantronix DOTA server.
To upgrade the firmware:
1. Go to Services > DOTA > Lantronix Server.
2. Select the channel and click Check for update to find available updates. See Table 10-2.
The results of the update check are displayed in the area below the action bar. If an update isavailable, the firmware file is displayed under Available Firmwares.
3. To update the device, select the firmware file under Available Firmwares and click Updatenow.
Do not power off the device during the update. After the firmware is updated, the device will
reboot.
Table 10-2 DOTA using Lantronix Server
Parameters

Description

ChannelSelect the channel on which to look for the firmware update files. The
options are Development, Beta, and Released.
The default channel option is Released.

Check for update

Click to check for available updates.

Available Firmware

Displays a list of firmware that is available on the server. Select the
firmware from this list and click Update now to upgrade or downgrade
the firmware.

Force Upgrade

Check this box for forceful upgrade or downgrade of the firmware
version.

Update now

Click Update now to download the firmware selected in the Available
Firmware list.

Custom Server
Services > Dota > Custom ServerThis page allows you to update the gateway’s firmware using a custom DOTA server.
To update firmware using a custom server:
1. Go to Services > DOTA > Custom Server.
2. Enter the server details. See Table 10-3.
3. Click Update now.

X300 Series IoT Cellular Gateway User Guide9310: Services

Table 10-3 DOTA Custom Server Configuration
Parameters

Description

Update now

After setting the Custom Server parameters, click Update now to
download the firmware pointed to by the URL and the filename below.

Custom Server Settings
Note: If the custom server is not configured, DOTA service will configure the Lantronix server.
ProtocolSelect HTTP or HTTPS as the protocol of the custom server.
Enter the configuration depending on the protocol you selected.

URL/IPEnter the URL or the IP address of the custom DOTA server. The URL,
if provided, must include http or https.

FilenameEnter the firmware file name to be accessed for the update.

Username

This field is displayed if the selected protocol was HTTP.
Enter the server login username.

Password

This field is displayed if the selected protocol was HTTP.
Enter the server login password.

Cert-typeThis field is displayed if the selected protocol was HTTPS.
Choose the type of certificate file. The options are PEM, DER, or ENG.

Cert

This field is displayed if the selected protocol was HTTPS.
Click the Select file... button to browse to the SSL certificate file to be
uploaded.

Key

This field is displayed if the selected protocol was HTTPS.
Click the Select file... button to browse to the key file to be uploaded.

Timeout in Minutes

Enter the period of time to wait for the download to complete.
The download process will be aborted after the timeout period expires.
The default value is 10 minutes.

RetriesEnter the number of retry attempts allowed to check and download thelatest firmware file from the server.
The default number of retries is 3.

Note: DOTA update can also be triggered using SMS by sending the SMS AT+DOTA
command after setting the custom server configuration from the Web UI (shown above) orby sending the AT+DOTASETTINGS command using SMS from a registered mobile
number. For command syntax, see Table 10-16 SMS AT Command Syntax.

X300 Series IoT Cellular Gateway User Guide9410: Services

Dynamic DNS
Services > Dynamic DNS
Dynamic Domain Name System (Dynamic DNS or DDNS) offers a method of keeping a static
domain/host name linked to a dynamically assigned public IP address allowing your server to be
more easily accessible from various locations on the Internet.
The DDNS page lets you configure your DDNS service so that the gateway automatically updates
its public IP to your DDNS provider. Before starting this configuration, you should already haveregistered a DNS name with a compatible DDNS service provider. For a list of compatible DDNS
providers, visit: https://openwrt.org/docs/guide-user/services/ddns/client.
To add a DDNS configuration:
1. Go to Services > Dynamic DNS.
2. At the bottom of the Overview section, type the DDNS configuration name and click Add.
To edit a DDNS configuration:
1. Go to Services > Dynamic DNS.
2. In the Overview section, select the DDNS configuration that you want to edit and click Edit.
3. Edit the configuration settings. See Table 10-4.
4. Click Save & Apply.

Table 10-4 Dynamic DNS Client Configuration
Parameters

Description

Basic Settings
Enabled

Select to enable Dynamic DNS.
Clear to disable Dynamic DNS.
Dynamic DNS allows the gateway to be reached with a fixed hostname
while having a dynamically changing IP Address.

Lookup Hostname

Name to identify the host that you want to use on DDNS server. This is
the domain name that you registered with your DDNS service provider.
The hostname is received from the dynamic DNS service provider.

IP address version

Select the IP address version – IPv4 or IPv6.

DDNS Service Provider [IPv4/
IPv6]

Select the DDNS service provider from the drop down list.

DomainThe domain that you want to update. Usually the same as the lookup
hostname.

Username

Username of DDNS account.
The username is received from the DDNS service provider.

Password

Password of DDNS account.
The password is received from DDNS service provider.

Use HTTP Secure

Select to use HTTPS with the DDNS provider.
Otherwise, leave it unchecked.

X300 Series IoT Cellular Gateway User Guide9510: Services

Parameters

Description

Path to CA-certificate

This field is visible if HTTPS is selected.
Enter the directory or file path of the ssl certs.
To run HTTPS without verification of server certificates (insecure),
enter IGNORE.

Advanced Settings
IP address source [IPv4/IPv6]

Select the IP Address source: Network, Interface, URL, or Script andenter the appropriate configuration details.
Network
 Network (IPv4) – Select the software interface to read systems IPv4

address from.
Interface Interface – Select the physical network interface from the options

URL URL to detect – Enter the URL to read systems IP address from. The

source IP Address by default is URL.
 Event Network (IPv4) – network on which the ddns-updater scripts

will be run Bind Network – leave as “default” or select the network to use forcommunication. Note that casual users should not change thissetting.
Script Script – Enter the script path and file name.
 Event Network (IPv4) – network on which the ddns-updater scripts

will be run
Force IP Version

Select if you want to force the usage of either IPv4 or IPv6 only. This
field is optional.

DNS-ServerEnter DNS server domain name or IP address if you want to override
the default DNS server to detect the registered IP.
Enter IP address or FQDN.

PROXY-ServerEnter the proxy server to use for detection and updates.
Format: [user:password@]proxyhost:port
IPv6 address must be given in square brackets: [2001:db8::1]:8080

Log to syslog

Select log level to write log messages to syslog. Critical errors arealways logged to syslog.
Available options include No logging, Info, Notice, Warning, Error.
The default setting is Notice.

Log to file

Select to allow the detailed messages to be written to log files. Log files
store up to 250 lines and then are automatically truncated.

Timer Settings
Check IntervalSpecify the time interval to check if the local IP has changed.
Values less than 5 minutes (300 seconds) are not supported.
Default is 10 minutes.

X300 Series IoT Cellular Gateway User Guide9610: Services

Parameters

Description

Force IntervalSpecify the time interval after which the DDNS server should force
update the IP address of your server even if no IP change was
detected.
The force interval should be greater than the check interval.
Enter 0 to force the script to only run once.
Default is 72 hours.

Error Retry Counter

The number of retries to attempt before the script stops execution.
Default setting is 0 which indicates infinite retries.

Error Retry Interval

If an error occurs on detecting, sending or updating, the script will retry
the relevant action according to the specified time interval.
Default is 60 seconds.

Log File Viewer
Read/Reread log file

Click to display the DDNS log file.

X300 Series IoT Cellular Gateway User Guide9710: Services

External Filesystems
Services > External Filesystems
The X300 series gateway supports an SD(HC)/MMC card or external USB flash drive for external
file storage. This page configures the mount settings for the external filesystem.
To configure the external filesystem:
1. Insert the SD card in the SD card slot or the USB flash drive in the USB slot on the gateway.
2. Go to Services > External Filesystems.
3. Configure the external device settings. See Table 10-5.
4. Click Save & Apply.
Table 10-5 External Filesystems Configuration
Parameters

Description

External device

Select the external device.

Mount point

Enter the mount point directory to the file system, relative to the top
level directory.
Example: /tmp/usbdevice

Auto mount

Select to mount the device automatically when the gateway boots.
If unselected, the device must be mounted manually.

Options

Enter the Linux mount options to be run when the device is mounted.
Separate each of the options with a comma.
Default mount option: rw, sync

X300 Series IoT Cellular Gateway User Guide9810: Services

GPS
Services > GPS
The built-in GPS receiver receives GPS data from GPS satellites for synchronizing the GPS timeand position data.
Note:

GPS is only available on certain X300 device models.

Enable GPS
To enable GPS receiver:
1. Go to Services > GPS.
2. Select GPS Enable.
3. Click Save & Apply.
The data will be displayed on the page (see Table 10-6). It may take some time (about a minute) toreceive and display the data.
Send GPS Data to an External Server
The GPS data can be sent in NMEA data format to an external TCP server on a real-time basis.
You can also configure the GPS data to be sent to a backup server.
To send the GPS data to an external server:
1. Go to Services > GPS.
2. Select Enable Data Send and enter the server settings (see Table 10-6).
3. Click Save & Apply.
Table 10-6 GPS Service Configuration
Parameters

Description

GPS Parameters
GPS Enable

Select GPS Enable check box to display current GPS data.

Time (GMT)Time in hh:mm:ss

Latitude (degree.mmsss)

Latitude in ddmm.mmmm

N/S-Indicator

N = North or S = South

Longitude (degree.mmsss)

Longitude in ddmm.mmmm

E/W-Indicator

E = East or W=West

Position-Fix-Indicator

Indicates the type of signal or technique used by the GPS receiver todetermine its location.
 0 – Fix not available or invalid
 1 – GPS SPS Mode, fix valid
 2 – Differential GPS, SPS Mode, fix valid
 3 to 5 – Not supported
 6 – Dead Reckoning Mode, fix valid

Number of Satellites Used

Number of satellites used to receive GPS signals.
The range for the number of satellite used is 0 to 12.

HDOP

Horizontal Dilution of Precision (HDOP) indicates the relative accuracyof the horizontal position

X300 Series IoT Cellular Gateway User Guide9910: Services

Parameters

Description

Altitude (in meters)

Altitude above mean sea level

Status

Displays the status.
A = Data valid
V = Data not valid

Speed

Speed over ground in knots

Course of Ground

Track, or intended direction of travel

ProtocolEnable Data Send

Select Enable Data Send check box to send data to the selectedserver. It sends the GPS information in NMEA format.

ProtocolSelect the TCP protocol only.

IP1/URL1

Enter the primary IP address.

Port1

Enter the port number.

Backup

Click to use a backup server, in case sending the data fails using
primary IP address.
 IP2/URL2 – Enter the backup IP address.
 Port2 – Enter the backup port number.

Polling Interval (in seconds)

The period of time between the end of the timeout period or thecompletion of the network request and the next request for data on the
network.

Send Interval (in seconds)

The period of time to wait between attempts to send GPS data using
the primary IP address or backup IP.

Description of NMEA Messages
The X300 series device receives NMEA sentences every second, depending on the configuration.
The identifiers for the NMEA messages are listed below. All messages are based on the NMEA
standard messages.

GPGGA
GPRMC
GPGSV
GPGSA
GPVTG

GPS Fix Data
Recommended Minimum Specific GPS Data
GPS Satellites in View
GPS DOP and Active Satellites
Course Over Ground and Ground Speed

A full description and definition of the listed messages above is provided in the next sections.

X300 Series IoT Cellular Gateway User Guide10010: Services

GPGGA Format
The $GPGGA message includes time, position, GPS quality and number of satellites in use.
Example: $GPGGA,120133.0,1907.469671,N,07250.544473,E,1,05,1.0,43.1,M,-64.0,M,,*42
Table 10-7 GGA Data Format
Parameters

Description

MID GGA Parameters
MID

GGA Protocol Header
Example – $GPGGAUTC Time

Time in hhmms.sss
Example – 120133.0

LatitudeLatitude in ddmm.mmmm
Example – 1907.469671

N/S-Indicator

N = North or S = South
Example – N

Longitude

Longitude in ddmm.mmmm
Example – 07250.544473

E/W-Indicator

E = East or W = West
Example – E

Position-Fix-Indicator

Indicates
 0 – Fix not available or invalid
 1 – GPS SPS Mode, fix valid
 2 – Differential GPS, SPS Mode, fix valid
 3 to 5 – Not supported
 6 – Dead Reckoning Mode, fix valid

Example – 1
Satellite-Used

Number of satellite used to receive GPS signals.
The range for the number of satellite used is 0 to 12.
Example – 05

HDOP

Horizontal Dilution of Precision
Example – 1.0

MSL Altitude

Altitude in meters.
Example – 43.1 meters

Units

Example – M meters

Geoid Seperation

Geoid-to-ellipsoid separation.
Ellipsoid altitude = MSL Altitude + Geoid Separation
Example: -64.0 meters

Units

Example: M meters

Age of Diff.Corr.

Null fields when DGPS is not used.4
The units is sec.

Diff. Ref.Station ID–

Checksum*42<CR><LF>

End of message termination

X300 Series IoT Cellular Gateway User Guide101

10: Services

GPRMC Format
The $GPRMC message includes time, date, position, course, and speed datea.
Example: $GPRMC,120133.0,A,1907.469671,N,07250.544473,E,0.0,0.0,150915,0.3,W,A*1E
Table 10-8 RMC Data Format
Parameters

Description

MID RMC Parameters
MID

RMC Protocol Header
Example – $GPRMC

UTC Time

Time in hhmmss.sss
Example – 120133.0

Status(1)A = Data valid
V = Data not valid
Example – A

LatitudeTime in ddmm.mmmm
Example – 1907.469671

N/S-Indicator

N = North or S = South
Example – N

Longitude

Longitude in ddmm.mmmm
Example – 07250.544473

E/W-Indicator

E = East or W = West
Example – E

Speed Over Ground

Measured in knots.
Example – 0.0

Course Over Ground

True.
Measured in degrees
Example – 0.0

Date

Date in ddmmyy
Example – 150915

Magnetic Variation(2)E = East or W = West
Measured in degrees
Example – 0.3

East/West Indicator(2)W = West
Example – W

ModeIndicates A – Autonomous D – DGPS E – DR
 N – Output Data Not Valid(3) (4) (5) R – Course Position S – Simulator

Example – A
Checksum*1E

X300 Series IoT Cellular Gateway User Guide102

10: Services

Parameters

Description<CR><LF>

End of message termination(1)
A valid status is derived from all the parameters set in the software. This includes the minimum number of satellites required, any DOP mask setting, presence of DGPS corrections, etc. If the default or current software setting requires that a factor is met, and then if that factor is not met the solution will bemarked as invalid.
(2) CSR Technology Inc. does not support magnetic declination. All courses over ground data are geodetic WGS84 directions relative to true North.
(3)
Position was calculated based on one or more of the SVs having their states derived from almanac
parameters, as opposed to ephemerides.
(4)This feature is supported in the GSD4e product only.
(5)This feature is supported in the GSD4e product, version 1.1.0 and later.

GPGSV Format
The $GPGSV includes the number of satellites in view, satellite ID numbers and their evaluation,
azimuth and signal-to-noise ratio.
Example: $GPGSV,4,1,16,21,50,358,38,22,28,272,37,29,53,164,36,18,51,319,31,*71E
IMEI number is added at the start of every frame.
Table 10-9 GPGSV Data Format
Parameters

Description

MID GSV Parameters
MID

GSV Protocol Header
Example – $GPGSV

Number of Messages(1)Total number of GSV messages to be sent in this group
Example – 4

Message Number(1)Message number in this group of GSV messages
Example – 1

Satellites in View(1)16Satellite ID

Channel (Range 1 – 32)
Example – 21

Elevation

Channel 1 (Maximum 90)
Example – 50 degrees

AzimuthChannel (True, Range 0 – 359)
Example – 358 degrees

SNR (C/N0)

Range 0 – 99, null when not tracking
Example – 38dBHz….

(Satellite ID, elevation, azimuth, and SNR repeated for each satellite inview)

Satellite ID

Channel 4 (Range 1 – 32)
Example – 18

X300 Series IoT Cellular Gateway User Guide103

10: Services

Parameters

Description

Elevation

Channel 4 (Maximum 90)
Example – 51 degrees

AzimuthChannel 4 (True, Range 0 - 359)
Example – 319 degrees

SNR (C/N0)

Range 0 – 99, null when not tracking
Example – 31 dBHz

Checksum*71<CR><LF>

End of message termination(1)

Depending on the number of satellites tracked, multiple messages of GSV data may be required. In
some software versions, the maximum number of satellites reported as visible is limited to 12, eventhough more may be visible.

GPGSA Format
The $GPGSA message includes the list of satellites being used.
Example: $GPGSA,A,3,18,20,21,22,29,,,,,,,,2.4,1.0,2.2*36
Table 10-10 GSA Data Format
Parameters

Description

MID GSA ParametersMID

GSA Protocol Header
Example – $GPGSA

Mode1

M – Manual: Forced to operate in 2D or 3D modeA – 2D Automatic: Allowed to automatically switch 2D/3D
Example – A

Mode2

1 – Fix not available
2 – 2D (<4 SVs used)3 – 3D (>3 SVs used)
Example – 3

Satellite Used(1)SV on Channel 1
Example – 18

Satellite Used(1)SV on Channel 2
Example – 20….

….

Satellite Used

SV on Channel 12PDOP(2)

Position Dilution of Precision
Example: 2.4

HDOP(2)

Horizontal Dilution of Precision
Example: 1.0

VDOP(2)

Vertical Dilution of Precision
Example: 2.2

X300 Series IoT Cellular Gateway User Guide10410: Services

Parameters

Description

Checksum*33<CR><LF>

End of message termination(1)

Satellite used in solution.

(2) Maximum DOP value reported is 50. When 50 is reported, the actual DOP may be much larger.

GPVTG Format
The $GPVTG message includes course over ground and ground speed.
Example: $GPVTG,0.0,T,0.3,M,0.0,N,0.0,K,A*20
Table 10-11 VTG Data Format
Parameters

Description

MID VTG ParametersMID

VTG Protocol Header
Example – $GPVTG

CourseMeasured heading
Example – 0.0 degrees

Reference

True
Example – T

CourseMeasured heading
Example – 0.3 degrees

Reference

Magnetic(1)Example – M

Speed

Measured horizontal speed
Example – 0.0 knots

Units

Knots
Example – N

Speed

Measured horizontal speed
Example – 0.0 km/hr

Units

Kilometers per hour
Example – K

ModeIndicates A – Autonomous D – DGPS E – DR
 N – Output Data Not Valid(2) (3) (4) R – Course Position S – Simulator

Example – A
Checksum*20

X300 Series IoT Cellular Gateway User Guide105

10: Services

Parameters

Description<CR><LF>

End of message termination(1)

CSR does not support magnetic declination. All “course over ground” data are geodetic WGS84 directions.
(2) Position was calculated based on one or more of the SVs having their states derived from almanac
parameters, as opposed to ephemerides.
(3)This feature is supported in the GSD4e product only.
(4)This feature is supported in the GSD4e product, version 1.1.0 and later.

X300 Series IoT Cellular Gateway User Guide106

10: Services

Keepalived
Services > Keepalived
The Keepalived service provides frameworks for load balancing and high availability of the servers
connected to the gateway. Keepalived uses Virtual Router Redundancy Protocol (VRRP) to checkthe health of load balanced routers and elect a router on the network that will serve a particular IP.
In a typical configuration, VRRP groups two or more routers into a virtual router, where one routeris the master (active) server and the other is the backup node. The master server has a higher
priority than the backup server. The master server transmits multicast VRRP advertisement
packets at regular intervals, and the backup servers listen for these advertisement packets. If the
backup servers fail to receive three consecutive VRRP advertisements, the backup router with thehighest priority becomes the new master router so that the system remains functional.
The configuration for the backup server will be similar to that of the master server, with the
exception of the values for priority, state, and interface, depending on the system hardware
configuration.

Keepalived Configuration
The Keepalived configuration on the web interface includes the following sections:

General – Keepalived log settingsGlobal – Keepalived global settingsTracking Scripts – create tracking script blocks that Keepalived will run to determine thehealth of the host and increase or decrease the priority of the router by the value of the weight.

Tracking Interfaces – configure which interfaces Keepalived will monitor. If a monitoredinterface fails, Keepalived will adjust the priority of the host according to the configured weightof the tracking interface.

Tracking Processes – create tracking process blocks that Keepalived can use to monitor thehealth of the router. If the monitored process stops running, Keepalived will adjust the priorityof the host according to the weight of the tracking process. After adding a process, you must
restart the Keepalived service.



Virtual IP – configure the Virtual IP address for the VRRP instance.



VRRP Instances – add VRRP instances to be run on interfaces that Keepalived is monitoring.
The VRRP instance is defined in the General and Advanced settings. The User Notify settings
allow Keepalived to run specified scripts when the router transitions between backup andmaster states.

To configure Keepalived settings:
1. Go to Services > Keepalived.
2. Edit the configuration settings. See Table 10-12.
3. Click Save & Apply when you are finished.

X300 Series IoT Cellular Gateway User Guide107

10: Services

Table 10-12 Keepalived Configuration
Parameters

Description

GeneralDetailed Log

Select to enable detailed keepalived general/common logs.

Syslog levelSet the log level from 0-4, with 4 being the most detailed.

Keepalived Global
Vrrp startup delay

Enter the time in seconds to delay before starting VRRP.

Global Router Id/nameEnter the global router ID/name. A default name is provided, but you
can modify it if you want. It doesn't have to be the hostname, but it must
be unique for each device in a pool.

Keepalived config file

Select the Keepalived configuration file.
Settings in the configuration file will supersede settings configured on
the Keepalived UI pages except for all scripts loaded in Tracking
Scripts, and the User Notify settings in VRRP Instances.
The name of the script should match the ones in the configuration filesettings.

Remove configuration for
Keepalived

Unlink the uploaded keepalived configuration so as to fill theconfigurations manually.

User

The user for script execution.

Enable Script Security

Select to prevent running any scripts that were configured to be run as
root if any part of the path is writable by a non-root user.

Enable dynamic interfaces

Select to enable dynamic interfaces. Once enabled, next to Dynamic
interfaces, select Allow or None

Tracking Scripts
Name of trackscript block

Enter the tracking script block name.

ScriptSelect the tracking script file to upload it to the router.
The file is uploaded to the /usr/sbin/ folder. The script name should
start with "keepalived_" and end with ".sh".

Remove script

Click to remove the tracking script.

TrackScript intervalEnter the time interval between script invocations in seconds.
Default is 1 second

WeightEnter the weight to adjust the priority if the tracking script fails.
Range is -253 to 253. Positive value will increase the priority. Negativevalue will decrease the priority. Setting it to zero (0) will ignore theweight, which means that any VRRP instance monitoring the script willtransition to the fault state after the fail count number of consecutive
failures of the script. A script returning 0 (zero) is success andeverything else is fail.

TrackScript pass countEnter the required number of successes for OK transition.

TrackScript fail countEnter the required number of fails for NOK transition.

Tracking Interfaces
Name of interface block

Enter the name of the tracking interface block

Interfaces

Select the interface to monitor for changing the state of the router ordecreasing the weight.

X300 Series IoT Cellular Gateway User Guide108

10: Services

Parameters

Description

WeightEnter the weight to adjust the priority if the interface is present orabsent.
Range is -253 to 253. Positive value will increase the priority. Negativevalue will decrease the priority. Default is 0 (zero), which means thatthe router will fail in case of the interface not running.

Tracking Processes
Name of process block

Enter the name of the process block.

Process

Enter the name of the process to monitor for running state.

WeightEnter the weight to adjust the priority if the process is not running.
Range is -253 to 253. Positive value will increase the priority. Negativevalue will decrease the priority. Default is 0 (zero), which means thatthe router will fail in case of the interface not running.

Virtual IP
Name of address block

Enter the name of the address block.

Virtual ipaddressEnter the Virtual IP address and netmask that will be used by the virtualrouter.

Physical device

Select the device used for the virtual IP.

Scope of the virtual ip

Select the scope. Options include: global, site, link, host, nowhere.

VRRP Instances
VRRP Instances > General Settings
EnableClick to enable the VRRP instance.
The VRRP instance defines and configures VRRP behavior to run on a
specific interface.

Name of InstanceEnter a name for the VRRP instance.

Virtual Router ID

Enter the router ID. This number should be the same for all routers on
the virtual router.
Unique number from 1 to 155.

Interface to look for

Select the interface that needs to be monitored for switching.

Virtual Router Priority

Enter the priority. The router with the highest priority will be the master.

DelayEnter the interval in seconds that VRRP will wait between sending
advertisement packets.
Default is 1 second.

DebugEnter the debug level, from 1 to 4.
Note: Debug level is not implemented yet by Keepalived.

Initial Virtual Router State

Select the initial virtual router state as MASTER or BACKUP.
This is for initial state only. As soon as the other routers in the virtualrouter group come up, an election will be held and the router with thehighest priority will become MASTER.

Enable Authentication

Select to enable authentication. Authentication type can be PASS
(suggested) or AH – IPsec (not recommended).
PASS is a simple text password. This should be the same value on allmachines in the virtual router. Only the first eight (8) characters areused.
Note: Authentication was removed from the VRRPv2 specification, anduse of the option is non-compliant and can cause problems.

X300 Series IoT Cellular Gateway User Guide109

10: Services

Parameters

Description

VRRP Instances > Advanced Settings
Virtual IPs

Enter the Virtual IP block. The router will assume this IP when it
becomes Master and release it when it changes to Backup. Add blocks
configured in Virtual IP.

Track Process

Enter the track process block that the VRRP instance will monitor. Add
blocks configured in Tracking Process.

Track interface

Enter the track interface block that the VRRP instance will monitor. Add
blocks configured in Tracking Interfaces.

Track Script

Enter the tracking script block that the VRRP instance will monitor. Add
blocks configured in Tracking Scripts.

VRRP Instances > User Notify Settings
Notify master Script

Select the notify master script which will be run when the router
becomes Master.

Remove master script

Remove the notify master script.

Notify backup Script

Select the notify backup script which will be run when the router
becomes Backup.

Remove backup script

Remove the notify backup script.

Logs Information
Services > Logs Information
Logs Information page lets you view the system log file and download them to the local computer.
The current log file and up to 3 historical log files may be saved.
The logs configuration is read from the system logging. In order to display and download the log
file, the system logging must be configured to write system log to file (see System > System >Logging).
To display or download logs:
1. Go to Services > Logs Information. The Logs page appears.
2. Select the log file. The file is displayed on the page.
3. Click Download. The log file is downloaded to the local computer.

Page Selector
This page allows a root user to hide certain pages from the admin user view.

X300 Series IoT Cellular Gateway User Guide11010: Services

Reporting Agent
Services > Reporting Agent
The reporting agent captures current device and interface information from the gateway on aperiodic basis and sends it to a generic device management server using TCP/UDP/HTTP/HTTPS
protocol.
To configure the reporting agent:
1. Go to Services > Reporting Agent.
2. Select Enable All to enable collection data on all settings for all interfaces.
3. Select the settings to report for each of the network interfaces (LAN, WAN, Cellular, Wi-Fi,
GPS). See Table 10-13.
4. Configure and enable the device info, reporting agent, and data send settings. See Table 1014.
5. Click Save & Apply.
Table 10-13 Reporting Agent Configuration
Parameters

Description

Enable All

Select check box to enable all settings for all interfaces.

Disable All

Select check box to disable all settings for all interfaces.

LAN Parameters
LAN

Select to enable reporting of individual LAN settings.
 Status
 Uptime
 IP
 Data usage

WAN Parameters
Select to enable individual WAN settings.
 Status
 Uptime
 IP
 Gateway DNS
 Data usage

Cellular Parameters
Select to enable individual Cellular settings.
 Status
 Uptime
 IP
 Gateway DNS
 Data usage
 RSSI Roaming Status
 Operator Name Network Status IMSI

X300 Series IoT Cellular Gateway User Guide111

10: Services

Parameters

Description

Wi-Fi Parameters
Select to enable individual Wi-Fi settings.
 Status
 Uptime
 IP
 Gateway DNS
 Data usage
 Wifi Client Info

GPS Parameters
Select to enable individual GPS settings.
 Time Latitude
 Longitude
 Altitude

Sending Data
Table 10-14 Reporting Agent Data Send Configuration
Parameters

Description

Device Info

Select to allow reporting agent to retrieve device IMEI information.

Reporting Agents

Select the reporting agent. Generic agent is the default selection.

Enable Data Send

Select to enable data send.

ProtocolSelect the protocol used in the data transmission.
Options are TCP, UDP, HTTP, or HTTPS. Depending on the protocolthat you selected, the server fields will vary.

Starting string of the frame

When TCP is selected, a start of frame sequence can be used toindicate the first frame of the data sent by the reporting agent.
This string must be less than 20 characters in length.

Ending string of the frame

When TCP is selected, a start of frame sequence can be used toindicate the first frame of the data sent by the reporting agent.
This string must be less than 20 characters in length.

IP1/URL1

Enter the IP address or the URL of the destination server.

Port1

Enter the port number (for TCP and UDP).

TCP Timeout

Enter the timeout in seconds to switch between primary and backup IP
in case of connectivity failure.
TCP user timeout value should be between 10 and 900 seconds.

BackupThis option is available when TCP protocol is selected. Select Backup
check box to configure the backup TCP server.
 IP2/URL2
 Port2

The backup IP will be used after 3 failed attempts to send data to
primary server. Reporting agent will continue to send data to backup
server until the backup server fails or the device reboots.
Send Interval in Second

The period of time between two data transmissions.

X300 Series IoT Cellular Gateway User Guide112

10: Services

Data Format
Figure 10-1 shows a portion of the reporting agent data format for a case where all settings wereselected.
Figure 10-1 Reporting Agent Data Format (excerpt)@IMEI=352948070039411,Lan Status=Connected,Lan
IP(IPv4)=192.168.1.1,Lan Uptime(Seconds)=329501,Lan TX
bytes=572260469,Lan RX bytes=117212098,Wan Status=Connected,Wan
IP(IPv4)=192.169.1.110,Wan Uptime(Seconds)=329389,Wan
gateway=192.169.1.1,Wan DNS=27.109.1.2 27.109.1.3,Wan TX
bytes=75455301,Wan RX bytes=344481735,Cellular
Status=Enabled,Cellular IP(IPv4)=,Cellular
uptime(Seconds)=,Cellular gateway=,Cellular DNS=,Cellular TX
bytes=208,Cellular RX bytes=0,RSSI(ASU)=99,Roaming Status=N/
A,Operator Name=N/A,Network Status=Not Registered,IMSI=ERROR,Wifi
Status=Enabled,Wifi IP(IPv4)=192.169.2.116,Wifi
Uptime(Seconds)=383,Wifi gateway=192.169.2.1,Wifi
DNS=192.169.2.1,Wifi TX bytes=14135074,Wifi RX bytes=34397774,Wifi
ClientService Actions
Services > Service Actions
This page displays a list of the available services and allows you to manage the system resources.
You can start, stop, reload, or restart the service; and enable or disable automatic startup of theservice when the device is rebooted.
Note: Use caution when changing the state of services as it may cause loss of network
connectivity and data. Some features may stop working and the device may become
unstable.
Figure 10-2 Service Actions

X300 Series IoT Cellular Gateway User Guide113

10: Services

SMS
Services > SMS
The SMS feature lets you send SMS messages to the gateway to request diagnostics information,
configure gateway settings, or initiate certain actions such as DOTA upgrade or starting andstopping the VPN.

SMS Configuration
Services > SMS > SMS Configuration
You can configure up to four administrator mobile numbers to receive SMS messages containing
gateway diagnostics information after a command is sent by SMS. The mobile number format is asfollows: +<countrycode><phonenumber>
You should include the preceding special character “plus (+)”. Example: +9198xxxxxxxx
Table 10-15 SMS Service Configuration
Parameters

Description

SMS Configuration
EnableEnable remote SMS configuration.

AT Enable

Enable remote AT commands using SMS

SMS Administrator

Displays up to four Administrators configured to receive the diagnostics
via SMS after an SMS command is sent.
Note: If no number is configured then the gateway will accept SMS
from any number.
For each administrator to be configured, enter the mobile number withcountry code.
The format of mobile number must be:+<countrycode><phonenumber> with a preceding special character“plus (+)”.
Example: +9198xxxxxxxx

SMS AT Commands
Table 10-16 describes the SMS AT commands in alphabetical order.
Table 10-16 SMS AT Command Syntax
Name

Command Syntax

AT Command

AT#ATCMD='<AT command string>',<Timeout>
Description: The command passed in the AT command string will be sent
directly to the internal GSM module.
Parameters:
 AT command string – AT command such as AT+CSQ (signal quality) or

AT+CREG? (to check the registration status of GSM module).
 Timeout – The timeout value should be an integer in seconds. If thetimeout value is set to 0, don't wait for a response. Issue the commandand leave it.
Example: AT#ATCMD=AT+CSQ,5 – check signal strength

X300 Series IoT Cellular Gateway User Guide114

10: Services

Name

Command Syntax

Cell Diagnostics

AT+CELLDIAG?
Description: Get cellular diagnostics

CELL Ping

AT+CELLPING=<IPA>
Description: Pings the cellular IP address
Parameter:
 IPA – IP address of the WAN interface to ping.

DOTA Action

AT+DOTA=<C/M>,<update/check>[,<released/beta/
development>,<filename>]
Description: Update firmware on gateway or check for available firmware
updates from configured server
Parameters:
 C/M – C for custom server, M for Lantronix server update/check – whether to update the gateway with the specified

filename or to check for available updates
 released/beta/development – the release channel on the Lantronix

download server
 filename – filename of the package to use for the update

DOTA Custom Settings

AT+DOTASETTINGS=<HTTP/HTTPS>,<Server URL>,<Filename>,<Username>,<Password>,<Timeout>,<Retry>
Description: Update firmware on gateway from a custom server
Parameters:
 HTTP/HTTPS – protocol of the custom server
 Server URL – server URL, must include http: or https:
 File name – the name of the file to be accessed for the update
 Username – server username
 Password – server password
 Timeout – period of time to wait for the download to complete (minutes)
 Retry Parameters – number of retry attempts for the download

Hardware Information

AT+HWI?
Description: Get hardware information

Cellular Settings

AT+IPGPRS=<1/2>,<Apn>,<Username>,<Password>,<AuthType>,<Data-Roam>
Description: Configure cellular SIM settings
Parameters:
 1/2 – SIM slot number Apn – access point name provided by the cellular network provider
 Username – username if auth type is pap, chap, or pap/chap Password – password if auth type is pap, chap, or pap/chap Auth-type – none, pap, pap/chap, or chap (auth-type parameter is casesensitive, must be all lowercase) Data-Roam – 0 for disabled or 1 for enabled

X300 Series IoT Cellular Gateway User Guide115

10: Services

Name

Command Syntax

Install / Update / Remove /Autoremove IPK

AT+IPKDOTA=<Name of IPK file>,<install/upgrade/remove/autoremove>,<For install/upgrade: 0-both default URL and custom URL, 1default URL, 2-custom URL>
Description: Install, update, remove or auto remove packages
Parameters: Name of IPK file – IPK file name that OPKG will install, upgrade, or

remove.
 install/upgrade/remove/autoremove – action that OPKG will run.
 location to check for the package for install or upgrade. This argument is

not required for remove or autoremove.
 0 – Both default server URL & custom URL. Both servers should berunning, otherwise it will return a failed response.
 1 – default server URL 2 – custom server URL
Lan Settings

AT+IPLAN=<IPv4 address>,<SubnetMask>
Description: Configure LAN IPv4 settings
Parameters:
 IPv4 address – The IP address of the LAN interface
 Subnet mask – Subnet mask of the LAN IP address

LAN Diagnostics

AT+LANDIAG?
Description: Get LAN diagnostics

LAN Ping

AT+LANPING=<IPA>
Description: Ping LAN IP address
Parameter:
 IPA – IP address of the LAN interface to ping

OPKG Configuration
Settings

AT+OPKGSETTINGS=<Server URL>
Description: Set OPKG server
Parameter:
 Server URL – URL of the package serverManage Digital Output

AT#OUT=<GPO1/GPO2>,<OPEN/CLOSE>
Description: Pull high or push low GPIO pins
Parameters:
 GPO1/GPO2 – the pin to be configured
 OPEN/CLOSE – Set OPEN for low, or CLOSE for high.

RebootAT+REBOOT=1
Description: Reboot the gateway

Enable Remote Access

AT+REMACC=<1/0>
Description: remote access
Parameter: 1/0 – Set 1 to enable, set 0 to disable remote access

Software Information

AT+SWI?
Description: Get software information

WAN Diagnostics

AT+WANDIAG?
Description: Get WAN diagnostics

X300 Series IoT Cellular Gateway User Guide116

10: Services

Name

Command Syntax

WAN Ping

AT+WANPING=<IPA>
Description: Ping WAN interface
Parameter:
 IPA – IP address of the WAN interface to ping.

WWAN Ping

AT+WWANPING=<IPA>
Description: Ping WWAN interface
Parameter:
 IPA– IP address of the WAN interface to ping.

Start/Stop VPN

AT+VPN=<VPN Type>,<VPN Name>,<start/stop>
Description: Start or stop the VPN instanceParameters:
 VPN type – pptp, l2tp, ipsec, openvpn
 VPN name – VPN instance name
 Start/stop – action to start or stop the VPN

Examples: AT+VPN=ipsec,IPSEC1,start AT+VPN=ipsec,IPSEC1,stop

Ethernet SMS
Services > SMS > Ethernet SMS
This service enables the device connected on LAN to initiate an SMS using Ethernet port.
Table 10-17 Ethernet SMS Configuration
Parameters

Description

EnableCheck to enable the Ethernet SMS.

PortEnter the port number. The port number range is from 0 to 65535.

To send an SMS you need to open a TCP client connection on the LAN IP and configured port.
Once the connection is created, issue the following commands:
To send an SMS
AT#SENDSMS=+<Mobile Number with Country Code><Message end with CTRL+D>
To read an incoming SMS
AT#READSMS=<ALL/SMS ID><Enter>To delete an SMS
AT#DELSMS=<ALL/SMS ID><Enter>
The internal SMS buffer is 10 messages – meaning, 11th incoming SMS will be over written on the
1st SMS.

X300 Series IoT Cellular Gateway User Guide117

10: Services

Live Message
Services > SMS > Live Message
Sends SMS from the web interface.
Notes:
To activate the Live Message feature, you must first enable the Ethernet SMS feature.

To send SMS, add a # symbol preceding the phone number instead of the + symbol.

To send SMS from the web interface:
1. Go to Services > SMS > Live Message.
2. Under Send SMS:, type #<mobile number with country code>.
3. Under Message Area: type the message. It can be update 159 characters.
4. Click SendSMS.
To read SMS:
On the Live Message page, select the message number (from 1-10 or All) and click ReadSms.
To delete an SMS:
On the Live Message page, select the message number (from 1-10 or All) and click DeleteSms.

X300 Series IoT Cellular Gateway User Guide118

10: Services

SNMPD
Services > SNMPDThe X300 series gateway uses Net-SNMP to implement SNMP v1, v2c, and v3 using both IPv4
and IPv6 to remotely manage and monitor network components and systems. The implementation
includes an SNMP agent for responding to SNMP requests or actions from the SNMP manager,an SNMP-TRAP application for receiving and processing SNMP notifications (or traps), andsupport for a number of applications to retrieve information from an SNMP capable device(snmpget, snmpgetnext, snmpwalk), retrieve statistics (snmpstatus) or write configuration on thedevice (snmpset).
The configuration of the SNMP agent and SNMP-TRAP application configuration files (mainly
snmpd.conf and snmptrapd.conf) are done using the web interface. Likewise, operations such as
enabling or disabling the agent and trap receiver are done using the web interface. Most
management operations and monitoring, however, will be done through the SNMP manager.
Prerequisites to use this feature include having knowledge of SNMP and having a network
management system (NMS) with which to monitor the network.
For more information about Net-SNMP or SNMP in general, please refer to the Net-SNMP web
site.
For information about using SNMP management systems, see the appropriate documentation foryour NMS application.

SNMP Architecture
A typical SNMP implementation includes the following components:
Network management system (NMS) – a combination of hardware devices and software(SNMP manager) used to monitor and administer a network. The manager polls the deviceson the network for information about network connectivity, activity, and events.

Managed device – any device on the network that is managed by the NMS.

SNMP agent – the SNMP process that resides on the managed device and communicateswith the SNMP manager. It responds to requests for information or actions from the manager
and generates SNMP notifications (traps). The agent also controls access to the agent’s MIB.

Management Information Base (MIB) – collection of objects that specify the information thatthe agent provides to the SNMP manager.

SNMP Versions
The X300 series software supports the following versions of SNMP: SNMPv1, SNMPv2c and
SNMPv3/USM.


SNMPv1 – Simple Network Management Protocol, defined in RFC 1157. Security is based oncommunity strings.



SNMPv2c – The community string-based Administrative Framework for SNMPv2. SNMPv2c isdefined in RFCs 1901, 1905, and 1906. Security is based on community strings.



SNMPv3/USM – SNMPv3 is defined in RFCs 3413-3415. It provides secure access to devices
by authenticating and encrypting packets over the network. SNMPv3 provides message
integrity, authentication, and encryption security features.

X300 Series IoT Cellular Gateway User Guide11910: Services

Table 10-18 SNMP Security Models and Levels
SNMP Model

Level

Authentication

Encryption

v1

noAuthNoPriv

Community String

No

v2c

noAuthNoPriv

Community StringNo

v3

noAuthNoPriv

UsernameNov3

authNoPriv

MD5 or SHA

No

v3

authPriv

MD5 or SHA

DES or AES

SNMP Configuration
The SNMP agent must be configured to use the version of SNMP that is supported by the
management station. An agent can communicate with multiple managers. You can configure the
SNMP agent to support communication with one management station using SNMPv1, one using
SNMPv2c, and one using SNMPv3.
The web interface allows you to configure the SNMP settings. The configuration specifies
directives in the following areas:agent behavior

access control to the agent (VACM)

system information and monitoring

active monitoring of the local system

Agent Behavior
The following directives control the behavior of SNMP network service.
agent address – the listening address on which to receive incoming SNMP requests. The
default behavior is to listen on UDP port 161 on all IPv4 interfacesEngineID – SNMPv3 only. SNMPv3 requires an SNMP agent to define a unique engine ID to
respond to SNMP requests.

For configuration details, see Table 10-19 on page 123.
View-based Access Control Model (VACM)
SNMP v1/v2c/v3-USM follow the VACM model. VACM determines whether to allow access to a
managed object in a local MIB by a remote principal. VACM makes use of a MIB that defines theaccess control policy for the agent and makes it possible to use remote configuration.
The SNMP service uses four keywords to set up VACM:


Com2sec – maps a v1 and v2c community string and a source IP or network to a security
name.



Group – maps a security name/security model pair to a group name.

View – maps an OID subtree family and bitstring value (mask-optional), or MIB view, to a view
name.



Access – maps a group name to a minimum access level (noauth, auth, or priv) and read/
write/notify scope for a specified security model (v1, v2c, v3/usm, or any).

In summary:

The Access and View keywords determine what access is being controlled.

X300 Series IoT Cellular Gateway User Guide120

10: Services



The Group and com2sec keywords determine who has this access.

Figure 10-3 shows how the fields map in the VACM configuration model.
Figure 10-3 VACM Configuration Model
secName

ipSource
default

communitygroupName

model
v1
v2c
usm

secNamegroupNamecontext
""

model
v1
v2c
usm
any

view

viewName

type
included
excluded

oidSubtree

SNMPv3 usm

userNamecom2sec

groupaccesslevel
noauthauthprivprefixexact
prefixreadScopeviewName
none

writeScope
viewNamenone

notifyScope
viewNamenone[mask]

Security levelauthprivacy

NoAuth,NoPriv
Auth,NoPriv
Auth,Priv

MD5
SHA

DES
AES

For SNMP v1/v2c/USM VACM configuration details, see Table 10-20 on page 125.
SNMPv3 with User-based Security Model (USM)
SNMPv3 with USM contains a private list of users and keys specific to the SNMPv3 protocol. To
use this model, the SNMPv3 USM users must be created and added to the VACM group table (assecurity name).
For SNMPv3 with USM user configuration details, see Table 10-22 on page 128.
System Information and Monitoring
System information includes system group information and monitoring information, which is
described below. The system group information, such as name, location, contact, and description,
are retrieved from the underlying network management system.
The agent is built with support for monitoring the local system. The following directives can be
specified:Process monitoring – provides information about individual processes running on the local
system

Disk usage monitoring – provides information about disk usage for specified disks or all disksSystem load monitoring – provides information about system load average and swap space

Log file monitoring – monitors the file size of specified log files

For system information and monitoring configuration details, see Table 10-19 on page 123.
Active Monitoring
The agent can be configured to generate trap notifications based on the following directives:

Authentication failure trap – generate authentication failure traps

X300 Series IoT Cellular Gateway User Guide121

10: Services

Default monitors – configure the Event MIB tables to monitor various UCD-SNMP-MIB tables
for problems

Link up/link down notifications – monitor for network interfaces being taken up or down andtriggering a linkUp or linkDown notification as appropriate

Where to send the trap notifications – determine where to send the notifications such as to the
localhost or to the SNMP manager.

For Trap sender configuration, see Table 10-23 on page 128.
Configure SNMPv1 or SNMPv2
To configure SNMPv1 or SNMPv2c:
1. Go to Services > SNMPD.
2. Enter the configuration settings as required according to the SNMP version (v1/v2c/v3-USM)
you have chosen. Click Save before moving between tabs on the SNMP page.
3. To configure SNMP general settings including agent behavior and system information/
monitoring, select the General Settings tab. See Table 10-19.
4. To configure VACM access control settings, select the VACM tab. See Table 10-20.
Note:

You do not need to configure the EngineID or SNMPv3 with USM settings.

5. To configure SNMP agent trap sender, select the Trap Settings tab. See Table 10-23.
Note:

To configure SNMP-TRAP application, see SNMPTRAPD on page 129.

6. On the General Settings tab, select Enable if it is not already selected.
7. Click Save & Apply.
Configure SNMPv3 with USM
To configure SNMPv3 with USM:
1. Go to Services > SNMPD.
2. Enter the configuration settings as required according to the SNMP version (v1/v2c/v3-USM)
you have chosen. Click Save before moving between tabs on the SNMP page.
3. To configure SNMP general settings including agent behavior and system information/
monitoring, select the General Settings tab. See Table 10-19.
4. To configure VACM access control settings, select the VACM tab. See Table 10-20.
5. To configure Engine ID settings for SNMPv3, select the VACM tab. See Table 10-21.
6. To create users for SNMPv3 with USM, select the VACM tab. See Table 10-22.
7. To configure SNMP agent trap sender, select the Trap Settings tab. See Table 10-23.
Note:

To configure SNMP-TRAP application, see SNMPTRAPD on page 129.

8. On the General Settings tab, select Enable if it is not already selected.
9. Click Save & Apply.

X300 Series IoT Cellular Gateway User Guide122

10: Services

Table 10-19 SNMP General Settings Configuration
Parameters

Description

EnableSelect to enable the SNMPD application.

EngineID

Displays the SNMP engine ID, which is required to respond to SNMPv3
requests. This value is auto-generated when the agent is first started.

agentaddress

Defines a list of listening addresses on which to receive incoming
SNMP requests.
The default agent behavior is listening on all interfaces on UDP port
161. This is equivalent to the following directive:
agentaddress udp:161 or simply agentaddress 161
To configure this field, specify one or more listening addresses using
the format: [<transport-specifier>:]<transport-address>
Examples: UDP:161, UDP6:161 – accept requests on all IPv4 and IPv6

interfaces on UDP port 161
 localhost:161 – accept requests on the local loopback interface on

UDP port 161
 127.0.0.1 – accept requests on the local loopback interface (UDP is

implied) UDP:161, UDP6:161, TCP:161, TCP6:161 – accept requests on all

IPv4 and IPv6 interfaces on UDP port 161 and TCP port 161
Other combinations are also valid.
System Information

Displays the system group information. System name, contact andlocation can be set through the SNMP Manager.
 sysName – default is Lantronix
 sysContact – default is root@localhost sysLocation – default is Unknown sysDescription – default ‘uname -s -n -r -v -m’ command output is

not writable using a set request.
Process Monitoring
Process Monitoring

Monitors the processes running on the local system and registers acommand that can be run to fix errors.
This table displays the processes that are being monitored andprovides options to add, edit or delete items from the monitoring table.
 Click Add to add an entry to the process monitoring table. Enter theprocess name and other details as shown below.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Process Name

Name of the process that is being counted.

Max Process

Maximum number of processes that should be running. Generates anerror flag if the number of processes detected is greater than the
maximum specified.

Min Process

Minimum number of processes that should be running. Generates anerror flag if the number is less than the minimum.

Enable Fix Action

Tells the agent to attempt to fix the problem by calling the operation
specified in the fix action.
The command will not be invoked automatically.

Program Name (Procfix action)

The command that gets run when the error is detected and the fix
action field is enabled.

Arguments

Arguments that support the command.

X300 Series IoT Cellular Gateway User Guide12310: Services

Parameters

Description

Disk Usage Monitoring
Disk Usage Monitoring

Monitors the minimum threshold specified in KB or as a percentage ofthe total disk space and registers an error if the available disk space isless than the minimum required space configured for it. Disk usage
monitoring section also allows for monitoring of all disks found on thesystem according to a specified percentage threshold. (See Include alldisks.)
This table displays the disks being monitored for disk usage andprovides options to add, edit, or delete items from the monitoring table.
 Click Add to add an entry to the disk usage monitoring table. Enterthe partition and space details as shown below.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Partition

Path where the disk is mounted.

Minimum Space

Minimum space or minimum percentage must be configured.
 Minimum space required on the disk in KB before the errors are

triggered.
 Minimum space required on the disk as a percentage of the total

disk space before the errors are triggered.
Include All disks

Enables monitoring of all disks found on the system.

Minimum Percent

Minimum space required as a percentage of total disk space of all disks
before the errors are triggered.
Note: The threshold for individual disks can be configured using thepartition directives above.

System Load Monitoring
Load Monitoring

Displays the system load monitoring details if configured.
Monitors the load average of the local system.

Enable Load Monitoring

Enables monitoring of system load averages

1 - Minute Max. Load

The one-minute maximum load average before errors are triggered.

5 - Minute Max. Load

The five-minute maximum load average before errors are triggered.

15 - Minute Max. Load

The fifteen-minute maximum load average before errors are triggered.

Swap Space Threshold (in KB)

Amount of swap space (in KB) available on the local system.
The default threshold is 16 MB and it is enabled by default. If theavailable swap space is less than 16 KB if not user-configured, or lessthan the configured value, and if Default Monitoring is enabled, it will
generate a notification to SNMP traps.

Log File Monitoring
Log File Monitoring

Monitors the size of the log files and registers an error if the size
exceeds the maximum size configured for it.
Limit: Up to 20 files can be monitored.
This table displays log files being monitored for file size limits andprovides options to add, edit or delete items from the monitoring table.
 Click Add to add an entry to the log file monitoring table. Enter thedetails as shown below.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

File Path

File path and name of the file to be monitored.

X300 Series IoT Cellular Gateway User Guide12410: Services

Parameters

Description

Maximum Size

Maximum file size in KB before errors are triggered.

Table 10-20 SNMP v1/v2/USM VACM Settings
Parameters

Description

Com2Sec Configuration
Com2Sec Configuration

The com2sec directive maps a v1/v2c community string and a source
IP or network address to a security name (username).
This table displays com2Sec entries and provides options to add, edit,
or delete items from the table.
 Click Add to add an entry to the com2sec table. Enter the details asshown below.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Security Name

Username specifies the security name to which this source andcommunity string are to be mapped.
Security name can contain alphanumeric characters, dash, underscore,or period. No spaces or other special characters allowed.

SourceSource can be one of the following: restricted source – a specific hostname or address subnet – represented as IP/Mask (10.10.10.10/255.255.255.0) or IP

in CIDR notation (10.10.10.10/8) or the IPv6 equivalents
 global – use “default”
 localhost – use “localhost” or 127.0.0.1

Community

Specifies the community (user credential) to use for SNMP requests.
The same community string can be specified in separate com2sec
directives.

Group Configuration
Group Configuration

The group directive maps a security name in the specified security
model (see Table 10-18 on page 120) into a named group.
This table displays groups and provides options to add, edit, or delete
items from the table.
 Click Add to add an entry to the group table. Enter the details asshown below.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Note: Several group directives can specify the same group name,allowing a single access setting to apply to several users and/or
community strings.
 All members of one group have the same access rights.
 A user cannot belong to more than one group for each of the
security models.
 Groups must be set up for the community-based models
separately. You would typically create two group directives for asingle com2sec directive, one for v1 and one for v2c.
Group NameGroup name can contain alphanumeric characters, dash, underscore,or period. No spaces or other special characters allowed.

X300 Series IoT Cellular Gateway User Guide12510: Services

Parameters

Description

Version

 v1
 v2c
 usm

Security Name

Security name should be one of the security names defined in thecom2sec configuration.

Access Configuration
Access Configuration

The access directive maps a group name to an access level (noauth,auth, or priv) and read/write/notify scope for a specified security model(v1, v2c, v3/usm, or any).
The table displays access entries and provides options to add, edit, ordelete items from the table.
 Click Add to add an entry to the access table. Enter the details asshown below.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Group NameGroup name should be one of the group names defined in Groupconfiguration.

Context

Default context is the empty string “”, which equates to “none”.
For v1 or v2c, context will be empty (“none”).

Version

 v1
 v2c
 usm
 any

This value should match the SNMP version of clients that will connect
to this agent.
Level noauth auth – (authNoPriv) use strong authentication
 priv – (authPriv) use strong authentication and encryption

For v1 or v2c, set the level to noauth.
For usm, set the level to at least the minimum level required. The
SNMPv3–USM security level must be configured to this level or higher.
MatchSpecifies how the context should be matched against the context of theincoming request.
 exact – context name must match exactly (default) prefix – only the first part of the context name must match

Read

Specifies the view to be used for GET requests.
 unspecified – if left unspecified, it will be treated as none - no access none – no access custom – name of the view from the view table

Write

Specifies the view to be used for SET requests.
 unspecified – if left unspecified, it will be treated as none - no access none – no access custom – name of the view from the view table

NotifySpecifies the view to be used for TRAP/INFORM requests.
 unspecified – if left unspecified, it will be treated as none - no access none – no access custom – name of the view from the view table

View

X300 Series IoT Cellular Gateway User Guide126

10: Services

Parameters

Description

View

Creates a named view, which determines what part of the MIB theaccess control is applied to.
The table displays view entries and provides options to add, edit, ordelete items from the table.
 Click Add to add an entry to the view table. Enter the details asshown below.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

View Name

View name can contain alphanumeric characters, dash, underscore, or
period. No spaces or other special characters allowed.

Type

Specifies whether to include or exclude the elements of the subtree
from the MIB view.
 included – the MIB view includes all the elements of the subtree excluded – the MIB view excludes all the elements of the subtree

OID

The OID defining the root of the subtree to include or exclude from thenamed view.

Mask (optional)

List of hex octets optionally separated by ‘.’ or ‘:’ with the set bits
indicating which subidentifiers in the view OID to match against.
Recommended to ignore this field.

Table 10-21 SNMP VACM Settings Engine ID Configuration
Parameters

Description

Engine ID Configuration

EngineID is required to respond to SNMPv3 requests. This ID isdetermined automatically, but can be configured manually. The string
must be consistent through time and should not change or conflict withanother agent’s engineID. For this reason, it is recommended that you
use the default values unless you know what you are doing.

EnableEnables the engineID.

engineID

Specifies that the engineID should be built from the given text string.
Default: lantronix

engineIDTypeSpecifies that the engineID should be built from given type.
Type 1 – IPv4 address
Type 2 – IPv6 address
Type 3 – MAC address (default)

engineIDNic

Specifies that the engineID should use the following interface when
determining the MAC address. Only required if engineIDType 3 is
specified.
Default: eth0

X300 Series IoT Cellular Gateway User Guide127

10: Services

Table 10-22 SNMP VACM Settings SNMPv3-USM
Parameters

Description

SNMPv3 with USM
Configuration

Create one or more SNMPv3 users.
The table displays SNMPv3 with USM users and provides options toadd, edit, or delete items from the table.
 Click Add to add an entry to the table. Enter the details as shown

below.
 Click Edit to modify an entry.
 Click Delete to delete an entry from the table.

User Name

Map the security name from the VACM com2sec table here.

Security Level

Security level can be: NoAuth,NoPriv – no authentication or privacy protocol
 Auth,NoPriv – has authentication (MD5|SHA), no privacy protocol
 Auth,Priv – has authentication (MD5|SHA), and has privacy protocol(DES|AES).
Auth Protocol

Select the authentication protocol.
 MD5
 SHA

SHA authentication requires SSL.
Auth Password

Enter the MD5 or SHA passphrase to use for authentication.
The passphrase must be at least 8 characters.

Priv Protocol

Select the privacy protocol.
 DES
 AES

DES and AES require SSL.
Priv Password

Enter the privacy protocol passphrase.
The passphrase must be at least 8 characters.

Table 10-23 SNMP Trap Settings Configuration
Parameters

Description

EnableAuthentication Failure Trap
EnableIf enabled, generates authentication failure traps. This is disabled bydefault.

Enable Default Monitors

Monitors the UCD-SNMP-MIB tables for problems. The monitored
events (process, load, disk usage, log file) should first be configured on
the General Settings page.
By default, the agent will check the default monitors once on startup
and then every 10 minutes.

Enable Link Up/Down
Notification

Monitors the ifTable for changes in network interfaces link status andgenerates linkUp or linkDown notifications as appropriate.

Trap Configuration
VersionSpecifies the SNMP version. Can be v1, v2c, or v3.
 For v1, community and host are required.
 For v2c, type, community, and host are required.
 For v3, type, username, security level, and host are required.

X300 Series IoT Cellular Gateway User Guide128

10: Services

Parameters

Description

Type

Select the type as trap or inform.
For information about SNMPv3 notification behavior and the difference
between traps and informs, see the following tutorial: http://www.net-

snmp.org/tutorial/tutorial-5/commands/snmptrap-v3.html
To use type inform, the SNMP manager must also support informmessages.
User Name

Username is the SNMP v3 security name, as defined in VACM settings.

Security Level

Security level can be: NoAuth,NoPriv – no authentication or privacy protocol
 Auth,NoPriv – has authentication (MD5|SHA), no privacy protocol
 Auth,Priv – has authentication (MD5|SHA), and has privacy protocol(DES|AES).
If Auth,NoPriv or Auth,Priv are selected, additionals fields will be
displayed. Enter the authentication and privacy protocol details as
needed.
Community

Defines the v1 or v2c community string to be used when sending traps.

Host

Defines the IP address and port that the trap should be sent to.
Typically, this could be localhost:162 or the IP and port of the SNMP
manager.
The well known SNMP Trap port is port 162.

SNMPTRAPD
Services > SNMPD TRAPD
The SNMP-TRAP application listens for incoming SNMP notifications. When it receives a
notification, it can log the notification, pass the details to a handler program, or forward the trap toanother notification receiver.

SNMP-TRAP Configuration
To configure SNMP-TRAP settings:
1. Go to Services > SNMPTRAPD.
2. Enter the configuration settings. See Table 10-24.


Logging – Notifications can be written to the syslog or to a file path on the gateway.



Notification processing – notifications can sent to a notification handler or to a notifications
receiver.

3. Under General, select Enable if it is not already selected.
4. Click Save & Apply.

Table 10-24 SNMP-Trap Receiver Configuration
Parameters

Description

General

X300 Series IoT Cellular Gateway User Guide129

10: Services

Parameters

Description

EnableEnables the SNMPTRAP application.

Ignore Authorization Failure

Select to ignore authentication failure traps.

SNMP-TRAP daemon configuration
VersionSpecifies the SNMP version. Can be v1, v2c, or v3.
 For v1, community and host are required.
 For v2c, type, community, and host are required.
 For v3, type, username, security level, and host are required.

Community

Specifies the community used for v1 and v2c authorization.
Notifications using the specified community will be allowed to beprocessed per the notification handling configuration.

User NameEnter the SNMP v3 username, as defined in VACM settings.

Type

Select the type as trap or inform.
For information about SNMPv3 notification behavior and the difference
between traps (unacknowledged) and informs (acknowledged), see thefollowing tutorial: http://www.net-snmp.org/tutorial/tutorial-5/

commands/snmptrap-v3.html
EngineID

Specifies the EngineID value. For use only with SNMPv3 traps.

Security Level

Security level can be: NoAuth,NoPriv – no authentication or privacy protocol
 Auth,NoPriv – has authentication (MD5|SHA), no privacy protocol
 Auth,Priv – has authentication (MD5|SHA), and has privacy protocol(DES|AES).
Enter the authentication and privacy protocol type and passphrase as
appropriate for the selection.
SourceUsed for v1 and v2c authorization. The source field specifies that theconfiguration should only apply to notifications received from the listed
sources.

OID

Specifies the OID defining the root of the subtree to add to or exclude
from the named view.

Logging Configuration
Log

Enables log.

Logging Location

Specifies where to log the notifications, either to a local file on thegateway or to the syslog. Select one: Specific file – enter the file path.
 syslog

Format1

Specify the format used to display SNMPv1 traps.
If no format is defined, the default Net-SNMP format will be provided.
For information about the format specification, see http://www.net-

snmp.org/docs/man/snmptrapd.html.
Format2

Specify the format used to display SNMPv2c and SNMPv3 traps.
SNMP v2c and v3 use the same PDU format.
If no format is defined, the default Net-SNMP format will be provided.
For information about the format specification, see http://www.net-

snmp.org/docs/man/snmptrapd.html.
Notifications Handling
ExecutePass the details of the trap to a specified handler program.

X300 Series IoT Cellular Gateway User Guide13010: Services

Parameters

Description

Execute OID

Invokes the specified program with the given arguments whenever anotification is received that matches the OID token.
For SNMPv2c and SNMPv3 notifications, this token will be comparedagainst the snmpTrapOID value taken from the notification.
For SNMPv1 traps, the generic and specific trap values and theenterprise OID will be converted to the equivalent OID per RFC 2576.
If the OID field is the token default then the program will be invoked forany notification not matching another OID-specific traphandle entry.

Program

Program name with path specified followed by a space separated
arguments if any. For example, /usr/bin/xyz 1 2 3Net

Forward the trap to another notification receiver
Note: Do not use this directive for SNMPv3.

Net OIDSee description for Execute OID above.

Destination

Forwards notifications that match the specified OID to another receiver.

X300 Series IoT Cellular Gateway User Guide131

10: Services

uHTTPdServices > uHTTPd
uHTTPd is the web server that runs the web interface. It supports multiple instances such as
multiple listening ports each with its own document root directory, TLS (SSL), and other web
server features.

Web Server Configuration
The web server configuration has two sections, one for server settings and the other for default
values for SSL certificates. The uHTTPd Main instance is provided by default and is used for
configuring the gateway.
To configure the HTTP/S server:
1. Go to Services > uhttpd.
2. Edit the configuration settings for the gateway. See Table 10-25.
3. If you upload a new X.509 certificate and private key in the general web server settings, youwill need to configure the uHTTPd Self-signed Certificate Parameters section. See Table 1026.
4. Click Save & Apply.
Note: If you want to create a new server instance, go to the bottom of the Main instance(on the General Settings tab), enter a name and click Add. For configuration details, see
Table 10-25.
Table 10-25 uHTTPd Server Configuration
Parameters

Description

General Settings
HTTP listeners (address:port)

Either HTTP listener or HTTPS listener is required.
Enter the ports and addresses to listen on for HTTP access.
Use 0.0.0.0/[::] to bind to all devices present. Enter a specific IP
address to restrict binding to a specific interface.

HTTPS listener (address: port)

Either HTTP listener or HTTPS listener is required.
Enter the ports and addresses to listen on for HTTPS access.
Use 0.0.0.0/[::] to bind to all devices present. Enter a specific IP
address to restrict binding to a specific interface.

Redirect all HTTP to HTTPS

Select this option to redirect all HTTP to HTTPS.

Ignore private IPs on public
interface

Select to ignore requests from private IP addresses (RFC1918)
directed to the server's public IPs.
The default setting is to ignore the requests from private IPs.

HTTPS Certificate (DER
Encoded)Upload the HTTPS cert file. Click the icon to expand the directory
structure (from root).

HTTPS Private Key (DER
Encoded)Upload the HTTPS private key file. Click the icon to expand the
directory structure (from root).

Remove old certificate and key

Click to remove old certificate and key files

Remove configuration forcertificate and key

Click to remove the cert, key, and configuration information.

X300 Series IoT Cellular Gateway User Guide132

10: Services

Parameters

Description

Full Web Server Settings
Index page(s)Enter the index file to use for directories. Usually index.html orindex.php.

CGI filetype handler

Enter the interpreter to associate with file endings in the cgi scripts
directory.

Do not follow symlinks outside
document root

If selected, the HTTP/HTTPS server will not follow symbolic links
outside the document root.

Do not generate directory
listings

If selected, the HTTP/HTTPS server will not generate directory listings.

Aliases

Maps URL to filesystem locations outside the document root.
The format should be /old/path=/new/pathRealm for Basic AuthEnter the realm for basic authentication when prompting the client for
credentials.
The default is "Lantronix", which is the local hostname.

Config file (e.g. for credentials
for Basic Auth)Enter the path of the configuration file for credentials for basic
authentication and additional settings.
The server will not use HTTP authentication if this field is blank.

404 ErrorEnter the virtual URL of file or CGI script to handle 404 (file not found)request. It must begin with a forward slash '/'.

Advanced Settings
Document root

Enter the directory path to the server document root. By default the
document root is /www.

Path prefix for CGI scripts

Enter the prefix for CGI scripts, relative to the document root. Leave it
blank to disable CGI support.

Virtual path prefix for Lua
scripts

Enter the prefix for sending requests to the embedded Lua interpreter,
relative to the document root. Leave it blank to disable Lua support.

Full real path to handler for Lua
scripts

Enter the full path to the Lua handler script to initialize Lua runtime onserver start. This field is required if Lua prefix is given, otherwise it's
optional.

Virtual path prefix for ubus via
JSON-RPC integration

Enter the URL prefix for ubus via JSON-RPC handler, relative to the
document root. Leave it blank to disable UBUS.

Override path for ubus socket

Enter the override ubus socket path

Enable JSON-RPC Cross-Origin Select to enable CORS HTTP headers on JSON-RPC API.
Resource Support
By default, this setting is disabled.
Disable JSON-RPC
authorization via ubus session
API

If selected, do not authenticate JSON-RPC requests against the UBUS
session API.
By default the requests are authenticated.

Maximum wait time for Lua, CGI, Enter the maximum wait time for CGI, Lua or ubus requests in seconds.
or ubus execution
If no output is generated within the timeout period, the requested
executables are terminated.
Default is 60 seconds.
Maximum wait time for network
activityEnter the maximum wait time for network activity. If no network activity
occurs within the timeout period, the requested executables are
terminated and the connection is shut down.
Default is 30 seconds.

Connection reuse

Sets the time limit for connection reuse.

X300 Series IoT Cellular Gateway User Guide133

10: Services

Parameters

Description

TCP Keepalive

Number of unanswered keep alive requests allowed.
Default: 1

Maximum number ofconnections

Enter the maximum number of concurrent connections allowed. If thelimit is reached, further TCP connection attempts are queued until thenumber of connections is below the limit.
Default: 100

Maximum number of script
requests

Enter the maximum number of concurrent requests. If the limit isreached, further requests are queued until the number of requests
drops below the limit.
Default: 6

Maximum wait time for rpc
Enter the maximum wait time for RPC timeout in seconds.
timeout in seconds per requests Default: 55

Self-Signed SSL Certificate Parameters
uHTTPd requires an X.509 certificate and private key. This has been configured for the Main
instance. You only need to configure this section if you choose to upload a new certificate andprivate key.
Table 10-26 uHTTPd Self-signed Certificate Configuration
Parameters

Description

uHTTPd Self-signed Certificate Parameters
Valid for # of Days

Enter the validity time (number of days) of the generated certificate.
Default: 730 days

Length of key in bits

Enter the length of the generated RSA key in bits
Default: 2048

Server hostnameEnter the server hostname covered by the certificate.
Default: Lantronix

CountryCountry of the certificate issuer

StateState of the certificate issuer

Location

Location/city of the certificate issuer

X300 Series IoT Cellular Gateway User Guide13411: Network
The software provides the administrator several options to customize the Network configuration
adhering to the organization’s requirements. The following sections are available to configure the
Network parameters:Interfaces

Wireless

DHCP and DNSHostnamesStatic Routes



Diagnostics



Firewall



QoS



Load Balancing

Interfaces
Network > Interfaces
The Interfaces section provides the overview and status of the network interfaces for LAN,
Cellular, and WWAN. It also provides the configuration parameters for each of these interfaces,
which allow you to configure or update the interface according to your requirements.
Additionally, you can add new virtual interfaces, such as GRE, L2TP, PPP, or PPtP VPN
instances.
The Network Interfaces section contains the following pre-configured interfaces:


CELLULAR Interface



LAN Interface



WWAN and WWAN6 Interface

Interfaces Overview
Network > Interfaces
Figure 11-1 shows a summary view of the network interfaces and interface status.

X300 Series IoT Cellular Gateway User Guide135

11: Network

Figure 11-1 Interfaces Overview (partial view)

Table 11-1 Network Interfaces Overview
Parameters

Description

Interfaces Overview
Network

Displays the network name and image representing the interface.
Note: When Wi-Fi is configured as Client, the WWAN interface will
become active.

Status

Displays the status of the interface. See Interface Status.

X300 Series IoT Cellular Gateway User Guide136

11: Network

Parameters

Description

Actions

Select the action to be taken for the interface.
 Restart – Connects the interface or reconnects the already started

interface.
 Stop – Stops the interface.
 Edit – Allows you to edit the interface settings.
 Delete – Deletes the interface.

Note: Default interfaces have predefined configurations and should
not be deleted.
Add new interface

Click Add new interface to add a virtual interface. See Add VirtualInterface.

Global Network Options
IPv6 ULA-Prefix

Displays the IPv6 Unique Local Address (ULA)-Prefix

Network Watchdog
EnableSelect this box to enable or clear the box to disable the network
watchdog.
The network watchdog monitors the connectivity of all WAN (external
network) interfaces. In the absence of connectivity resulting in Network
down, the gateway resets itself.
By default, the network watchdog is in enabled mode.

Time

If the network watchdog is enabled, enter the watchdog timeout inminutes.

Interface Status
Figure 11-2 WAN Interface Status

Table 11-2 Wireless Overview and Associated Stations
Parameters

Description

ProtocolProtocol assigned to the interface

UptimeAmount of time that the interface has been active since the lastreconnection.

MAC Address

MAC address of the physical interface.
Note: MAC address is displayed for LAN, WAN, WWAN, andOpenVPN interfaces.

RX

Number of received bytes over the interface for the current session.

TX

Number of transmitted bytes over the interface for the current session.

IPv4

IPv4 address

IPv6

IPv6 address

X300 Series IoT Cellular Gateway User Guide137

11: Network

Interface Protocols
The protocol assigned to each interface defines rules for exchanging information on the interface.
Table 11-3 shows the available protocol options for each of the interfaces. When configuring aninterface, please make sure that the protocol selection is appropriate for the interface.
Legend:  = protocol can be assigned  = protocol should not be assigned
Table 11-3 Network Interface Protocols
Interface

LAN

WWAN

Cellular

Static Address







DHCP client







DHCPv6 client







GRE







L2TP







WireGuard VPN







Unmanaged







PPP







PPPoE







PPtP







UMTS/GPRS/EV-DO







QMI Cellular







Relay Bridge







Protocols

The interface configuration involves selection or configuration of other settings such as default
gateway, gateway metric, DHCP server, and firewall zone to name a few. These settings may or
may not be used by the interface; the interface configuration depends on both the protocol
selected as well as the network requirements. For descriptions of the protocols used with the LAN,WWAN, and Cellular interfaces, see the next section, Protocol Descriptions.
GRE, L2TP, WireGuard VPN, and PPtP protocols listed in Table 11-3 are used for VPN
connections. For details about VPN protocol configuration, see Add Virtual Interface.
The interfaces can be set to Unmanaged, if no protocol is desired. This setting may be used toenumerate an interface for firewall purposes.

X300 Series IoT Cellular Gateway User Guide13811: Network

Protocol Descriptions
Static Address
Table 11-4 describes the Static Address protocol settings.
Table 11-4 Static Address Protocol Settings
Parameters

Description

General Settings
Protocol

Static Address – Static configuration with fixed address and netmask

Bring up on bootAllows the interface to be live after every reboot.
Bring up on boot is checked by default.

IPv4 AddressEnter the IPv4 Address. This IP Address must be used to access thegateway. The default LAN IP Address is 198.162.1.1.

IPv4 Netmask

Select the IPv4 Netmask.

IPv4 Gateway

Enter the IPv4 address for gateway.

IPv4 broadcast

Enter the IPv4 address for broadcast.

Use Custom DNS servers

Enter the IP address of the custom DNS server. Click the + button to
add more DNS servers.

IPv6 assignment length

Select the IPv6 assignment length.
Available Options
 64 or 60 – Assign a part of the given length of public IPv6-prefix tothis interface.
 disabled – do not assign part of the prefix to this interface
 --custom-- – Assign a part of the given length of public IPv6-prefix tothis interface.
IPv6 assignment length is disabled by default.
If assignment length is disabled, enter the following: IPv6 address – Enter the IPv6 Address.
 IPv6 gateway – Enter the IPv6 Address for Gateway.
 IPv6 routed prefix – Enter the public prefix to direct the client

distribution to the gateway.
If assignment length is 60, 64, or custom, enter the following: IPv6 assignment hint –Enter hexacimal subprefix ID for this instanceto assign prefix parts.
 IPv6 suffix – Enter the IPv6 suffix.

Advanced Settings
Use builtin IPv6 -management

Allows to use the built in IPv6 management configuration.

Force link

Select this option to assign interface properties regardless of the link
being active or not.
If not selected, items are assigned only after the link has become
active.
Default is not selected.

Override MAC address

Click to override the default MAC Address for the WAN Interface.
On factory reset, it will be set to default MAC address.

X300 Series IoT Cellular Gateway User Guide139

11: Network

Parameters

Description

Override MTUEnter the number of bytes indicating the largest physical packet sizethat the network can transmit.
The default MTU size is 1500 bytes. Blank value represents auto MTU
size

Use gateway metricEnter the gateway metric. It ensures a separate routing entry for therespective interface in the main routing table.
The default metric is 5.

Physical Settings
Bridge Interfaces

Click to enable creating a bridge over multiple interfaces.
 Enable STP – Check to enable the Spanning Tree Protocol over thebridge.
 Enable IGMP snooping – Check to enable IGMP snooping on thebridge.
Interface

Select the interface to be configured.
Select more than one interface, if parameter creating a bridge overmultiple interfaces is enabled.

Firewall Settings
Create/Assign firewall -zone

Select the firewall zone to be assigned to the interface.
Select unspecified – or – create to remove the interface or assign a
new zone to the interface respectively.
Enter the name of the new zone in the text box and click Save & Apply
button.

DHCP > General Setup
DHCP Server - DHCP Server is used only for LAN interfaces
Ignore Interface

Check to disable the DHCP interface.
Note: If DHCP server is disabled for the interface, all the LAN devices
connected to the gateway should have a static LAN IP configured.

Start

Lowest leased address as offset from the network address.
Note: If your LAN IP address is 192.168.1.1 and the parameter Start isconfigured as 100, then the starting IP Address of the leased IP
Address range is 192.168.1.100

Limit

Maximum number of leased addresses that can be configured.
Example If your LAN IP Address is 192.168.1.1, the parameter Start isconfigured as 100, and parameter Limit is configured as 150, then atotal of 150 devices are configured. Thus the leased IP Address
range is 192.168.1.100 to 192.168.1.249.
Lease time

Remaining time until the device can use the DHCP server leased IP
Address.
Note: IP address allocated by the gateway will disappear from the WiFi / Overview / Associated stations list only after individual lease timefor each IP expires.

DHCP > Advanced Settings
Dynamic DHCP

Check to allocate DHCP IP addresses dynamically to the clients.
When unchecked, service will be provided only to the clients having thestatic IP Address.

X300 Series IoT Cellular Gateway User Guide14011: Network

Parameters

Description

Force

Check to override the current configured Server and use DHCP server.

IPv4-Netmask

Enter the IPv4 netmask.
This netmask will override the netmask used by the clients. In normal
scenario netmask is calculated from the subnet.

DHCP-Options

Define additional DHCP options
Example: “6,192.168.2.1, 192.168.2.2" which advertises different DNS servers

to clients.
DHCP > IPv6 Settings
Router Advertisement-Service

Select the Router Advertisement-Service mode; disabled, server mode,
relay mode, hybrid mode.

DHCPv6-Service

Select the DHCPv6-Service mode; disabled, server mode, relay mode,
hybrid mode.

NDP-Proxy

Select the NDP mode; disabled, server mode, relay mode, hybrid
mode.

DHCPv6-Mode

Select the DHCPv6-Service mode: Stateless Stateful Stateless + Stateful Stateful only

Always announce default router Select to Announce as default router even if no public prefix isavailable.
Announced DNS servers

Add the DNS servers

Announced DNS domains

Add the DNS domains.

DHCP Client
Table 11-5 describes the DHCP Client protocol settings.
Table 11-5 DHCP Client Protocol Settings
Parameters

Description

General Settings
ProtocolDHCP client – Address and netmask are assigned by DHCP.

Bring up on bootAllows the interface to be live after every reboot.
Bring up on boot is checked by default.

Hostname to send whenrequesting DHCP

Hostname of the gateway

Advanced Settings
Use builtin IPv6 -management

Allows to use the built in IPv6 management configuration.

Force link

Select this option to assign interface properties regardless of the link
being active or not.
If not selected, items are assigned only after the link has become
active.
Default is not selected.

X300 Series IoT Cellular Gateway User Guide14111: Network

Parameters

Description

Use broadcast flag

Check to use the broadcast flag.
This flag is generally used by the ISP’s.

Use default gateway

Click to configure a default gateway route.
None of the gateway routes are configured by default.

Use DNS server advertised bypeer

Allows advertising the DNS server address.
Use DNS server advertised by peer for WAN interface is checked bydefault.
If unchecked, the advertised DNS server addresses are ignored.

Use gateway metricEnter the gateway metric.
The Load Balancer uses these Metric values to determine priority of a
WAN.
The default metric is 4.

Client ID to send whenrequesting DHCPEnter the Client ID that shall be sent when requesting DHCP.

Vendor Class to send whenrequesting DHCP

To allocate DHCP IP Addresses based on Vendor Class.

Override MAC address

Click to override the default MAC Address for the WAN Interface.
On factory reset, it will be set to default MAC address.

Override MTUEnter the number of bytes indicating the largest physical packet sizethat the network can transmit.
The default MTU size is 1500 bytes. Blank value represents auto MTU
size

Physical Settings
Bridge Interfaces

Click to enable creating a bridge over multiple interfaces.
Enable STP – Check to enable the Spanning Tree Protocol over thebridge.
Enable IGMP snooping – Check to enable IGMP snooping on thebridge.

Interface

Select the interface to be configured.
Select more than one interface if parameter creating a bridge overmultiple interfaces is enabled.

Firewall Settings
Create/Assign firewall -zone

Select the firewall zone to be assigned to the interface.
Select unspecified – or – create to remove the interface or assign a
new zone to the interface respectively.
Enter the name of the new zone in the text box and click Save & Apply
button.

X300 Series IoT Cellular Gateway User Guide14211: Network
DHCPv6 Client
Table 11-6 describes the DHCPv6 Client protocol settings.
Table 11-6 DHCPv6 Client Protocol Settings
Parameters

Description

General Settings
ProtocolDHCPv6 Client – Address and netmask are assigned by DHCP

Bring up on bootAllows the interface to be live after every reboot.
Bring up on boot is checked by default.

Request IPv6-addressEnter the behavior for requesting addresses. Options are try (default),
force, and disabled

Request IPv6-prefix of length

Enter the IPv6 address prefix length in bits. Options are:
 Unspecified
 Automatic(default)

 disabled – use if you want single IPv6 address for the AP without asubnet for routing
 48, 52, 56, 60, 64 –hinted prefix length custom – enter custom prefix length

Advanced Settings
Use builtin IPv6 -management

Allows to use the built in IPv6 management configuration.

Force link

Select this option to assign interface properties regardless of the link
being active or not.
If not selected, items are assigned only after the link has become
active.
Default is not selected.

Use default gateway

Click to configure a default gateway route.
None of the gateway routes are configured by default.

Custom delegated IPv6 prefix

Enter the custom IPv6 prefix to be used.

Use DNS server advertised bypeer

Allows advertising the DNS server address.
Use DNS server advertised by peer for WAN interface is checked bydefault.
If unchecked, the advertised DNS server addresses are ignored.

Client ID to send whenrequesting DHCPEnter the Client ID that shall be sent when requesting DHCP.

Override MAC address

Click to override the default MAC Address for the WAN Interface.
On factory reset, it will be set to default MAC address.

Override MTUEnter the number of bytes indicating the largest physical packet sizethat the network can transmit.
The default MTU size is 1500 bytes. Blank value means auto MTU size

Physical Settings
Bridge Interfaces

Click to enable creating a bridge over multiple interfaces.
 Enable STP – Check to enable the Spanning Tree Protocol over thebridge.
 Enable IGMP snooping – Check to enable IGMP snooping on thebridge.

X300 Series IoT Cellular Gateway User Guide14311: Network

Parameters

Description

Interface

Select the interface to be configured.
Select more than one interface, if parameter creating a bridge overmultiple interfaces is enabled.

Firewall Settings
Create/Assign firewall -zone

Select the firewall zone to be assigned to the interface.
Select unspecified – or – create to remove the interface or assign a
new zone to the interface respectively.
Enter the name of the new zone in the text box and click Save & Apply
button.

PPPoE
Table 11-7 describes the PPPoE protocol settings.
Table 11-7 PPPoE Protocol Settings
Parameters

Description

General Settings
ProtocolPPPoE – Point to Point Protocol over Ethernet

Bring up on bootAllows the interface to be live after every reboot.
Bring up on boot is checked by default.

PAP/CHAP usernameEnter the PAP/CHAP username. The default password is admin.

PAP/CHAP password

Enter the PAP/CHAP password.

Access Concentrator

Enter the access concentrator name.

Service NameEnter the service name.
Note: Access Concentrator name and Service Name gets auto
populated from the PPPoE Access Point router if they are not explicitly
provided

Advanced Settings
Use builtin IPv6 management

Allows to use the built in IPv6 management configuration

Force link

Select this option to assign interface properties regardless of the link
being active or not.
If not selected, items are assigned only after the link has become
active. This is the default.

Obtain IPv6-Address

Allow IPv6 negotiation on the PPP link

Use default gateway

Select to use the default gateway. If unselected, no default route will be
configured.

Use DNS servers advertised bypeer

Select to use DNS servers advertised by peer, otherwise ignore
advertised DNS servers.

Use gateway metricEnter gateway metric.

LCP echo failure threshold

Enter the number of LCP echo request failures allowed before
considering the peer dead. Set to zero (0) to ignore failures.

X300 Series IoT Cellular Gateway User Guide144

11: Network

Parameters

Description

LCP echo interval

The LCP echo interval in seconds. LCP echo failure threshold must be
set, otherwise this value is ignored.

Host-Uniq tag content

Enter the custom Host-Uniq tag to be used.

Inactivity timeout

Enter the inactivity timeout in seconds, Close the connection if thetimeout is reached or enter zero (0) to ignore inactivity timeout.

Override MTUEnter MTU size in bytes. The default is 1500 bytes.

Physical Settings
Bridge Interfaces

Click to enable creating a bridge over multiple interfaces.
 Enable STP – Check to enable the Spanning Tree Protocol over thebridge.
 Enable IGMP snooping – Check to enable IGMP snooping on thebridge.
Interface

Select the interface to be configured.
Select more than one interface, if parameter creating a bridge overmultiple interfaces is enabled.

Firewall Settings
Create/Assign firewall -zone

Select the firewall zone to be assigned to the interface.
Select unspecified – or – create to remove the interface or assign a
new zone to the interface respectively.
Enter the name of the new zone in the text box and click Save & Apply
button.

UMTS/GPRS/EV-DO Cellular
Table 11-8 describes the UMTS/GPRS/EV-DO Cellular protocol settings.
Table 11-8 UMTS/GPRS/EV-DO Cellular Protocol Settings
Parameters

Description

General Settings
ProtocolModems using the UMTS/GPRS/EV-DO protocols

Bring up on bootAllows the interface to be live after every reboot.
Bring up on boot is checked by default.

Modem device

Displays the modem device

SIM to use

Indicates which SIM to use, Embedded SIM or External SIM

Advanced Settings
Use builtin IPv6 -management

Allows to use the built in IPv6 management configuration.

Force link

Select this option to assign interface properties regardless of the link
being active or not.
If not selected, items are assigned only after the link has become
active.
Default is not selected.

Obtain IPv6-Address

Click to enable IPv6 negotiation on PPP link.

X300 Series IoT Cellular Gateway User Guide14511: Network

Parameters

Description

Modem init timeout

Enter the maximum wait time in seconds for the modem to become
ready.
The default modem initiation timeout 20 seconds.

Use default gateway

Click to configure a default gateway route.
If unchecked, no default route is configured.

Use gateway metricEnter the gateway metric.
Default is 5

Use DNS servers advertised bypeer

Click to enable, otherwise leave box unchecked to ignore theadvertised DNS servers.

LCP echo failure threshold

Enter the number of LCP echo failures after which the peer ispresumed to be dead.
Enter 0 to ignore failures.

LCP echo interval

Send LCP echo requests at the given interval in seconds. Failure
threshold must be configured for this to be effective.

Inactivity timeout

Number of seconds for inactivity timeout.
Enter 0 to persist the connection.

Physical Settings
Bridge Interfaces

Click to enable creating a bridge over multiple interfaces.
 Enable STP – Check to enable the Spanning Tree Protocol over thebridge.
 Enable IGMP snooping – Check to enable IGMP snooping on thebridge.
Interface

Select the interface to be configured.
Select more than one interface, if parameter creating a bridge overmultiple interfaces is enabled.

Firewall Settings
Create/Assign firewall -zone

Select the firewall zone to be assigned to the interface.
Select unspecified – or – custom to remove the interface or assign a
new zone to the interface respectively.
Enter the name of the new zone in the text box.

Embedded SIM / External SIM Settings
PDP Type

IP stack mode IPv4
 IPv6
 IPv4/IPv6

Service Type Automatic Cat M1
 GSM

Use Custom APN

Select to use and configure a custom APN. Enter the APN as provided
by the cellular network operator.
The embedded SIM custom APN is preset at data641003.
The external SIM custom APN can be configured.

PIN

Enter the PIN code to unlock the SIM card

PUKEnter the PUK (personal unblocking key) used to unblock the SIM card
if the PIN code has been repeatedly entered incorrectly

X300 Series IoT Cellular Gateway User Guide146

11: Network

Parameters

Description

Authentication TypeEnter the authentication method used for the cellular connection.
 PAP (requires username and password)
 CHAP (requires username and password) NoneEnable roaming

Enable data roaming on the cellular interface

CidEnter Cid value. It is usually okay to leave as the default value.

QMI Cellular
Table 11-9 describes the QMI Cellular protocol settings.
Table 11-9 QMI Cellular Protocol Settings
Parameters

Description

General Settings
ProtocolQMI Cellular – USB modems using QMI protocol

Bring up on bootAllows the interface to be live after every reboot.
Bring up on boot is checked by default.

Cellular Module

Displays the cellular module name

Modem device

Displays the modem device

PDP Type

Enter the IP stack mode as IPv4, IPv6, or IPv4/IPv6 (dual stack)Primary SIM

Indicates which SIM to use.
Embedded SIM or External SIM

RetriesNumber of attempts to re-establish the data link after it has been lost
Default: 5

Period after which the router will Force switch back to primary SIM after the specified number of minutes
try and return to the primary SIM Default: 60 minutes
Routine switch to secondarySIM

Switch to secondary SIM after the specified number of minutes

Advanced Settings
Use builtin IPv6 -management

Allows to use the built in IPv6 management configuration.

Force link

Select this option to assign interface properties regardless of the link
being active or not.
If not selected, items are assigned only after the link has become
active.
Default is not selected.

Enable IPv6 negotiation

Click to enable IPv6 negotiation on PPP link.

Modem init timeout

Enter the maximum wait time in seconds for the modem to become
ready.
The default modem initiation timeout 20 seconds.

Use default gateway

Click to configure a default gateway route.
If unchecked, no default route is configured.

X300 Series IoT Cellular Gateway User Guide14711: Network

Parameters

Description

Use gateway metricEnter the gateway metric.
Default is 5

Override MTUEnter the number of bytes indicating the largest physical packet sizethat the network can transmit.
The default MTU size is 1500 bytes, which is the maximum size. A
blank value means use auto MTU size.

Use DNS servers advertised bypeer

Click to use DNS servers advertised by peer.
If unchecked, the advertised DNS server addresses are ignored.

Physical Settings
Bridge Interfaces

Click to enable creating a bridge over multiple interfaces.
 Enable STP – Check to enable the Spanning Tree Protocol over thebridge.
 Enable IGMP snooping – Check to enable IGMP snooping on thebridge.
Interface

Select the interface to be configured.
Select more than one interface, if parameter creating a bridge overmultiple interfaces is enabled.

Firewall Settings
Create/Assign firewall -zone

Select the firewall zone to be assigned to the interface.
Select unspecified – or – custom to remove the interface or assign a
new zone to the interface respectively.
Enter the name of the new zone in the text box.

Embedded SIM
PDP Type

IP stack mode IPv4
 IPv6
 IPv4v6 (for dual-stack)

Service Type Automatic LTE Only

Use Custom APNEnter the Access Point Name provided by the cellular network
operator.

PIN

Enter the PIN code to unlock the SIM card

PUKEnter the PUK (personal unblocking key) used to unblock the SIM card
if the PIN code has been repeatedly entered incorrectly

Authentication TypeEnter the authentication method used for the cellular connection.
 PAP (requires username and password)
 CHAP (requires username and password) NoneEnable roaming

Enable data roaming on the cellular interface

External SIM
PDP Type

IP stack mode IPv4
 IPv6
 IPv4v6 (for dual-stack)

Service Type Automatic LTE Only

X300 Series IoT Cellular Gateway User Guide14811: Network

Parameters

Description

Use Custom APNEnter the Access Point Name provided by the cellular network
operator.

APN

If Use Custom APN is selected, enter the custom APN

PINEnter the PIN code to unlock the SIM card

PUKEnter the PUK (personal unblocking key) used to unblock the SIM card
if the PIN code has been repeatedly entered incorrectly

Authentication TypeEnter the authentication method used for the cellular connection.
 PAP (requires username and password)
 CHAP (requires username and password) NoneEnable roaming

Enable data roaming on the cellular interface

X300 Series IoT Cellular Gateway User Guide149

11: Network

CELLULAR Interface
Network > Interfaces > CELLULAR
This page allows you to configure the Cellular interface parameters. When the Cellular interface isfirst enabled or when the gateway is factory reset, the gateway detects the module and assigns
the appropriate protocol.
To edit the interface:
1. Go to Network > Interfaces, select CELLULAR and click Edit.

2. Configure the interface settings.
General Settings – Protocol should not be changed. If the cellular type is LTE CAT
M1, the configured protocol is UMTS/GPRS/EV-DO. If the cellular type is LTE CAT 1,
the configured protocol is QMI Cellular. For descriptions of the protocol settings, see
UMTS/GPRS/EV-DO Cellular and QMI Cellular.

Firewall Settings – Firewall zone should be set as WAN zone.

Embedded SIM / External SIM Settings – Configure the SIM settings according to the
SIM slot.

3. Click Save.
4. Click Save & Apply to save the configuration on the gateway.

X300 Series IoT Cellular Gateway User Guide15011: Network

LAN Interface
Network > Interface > LANThis page allows you to configure the LAN interface. The LAN interface should use Static Address.
Gateway may be used but is not required. DHCP server may be used to dynamically assign an IP
address to clients connecting to the LAN. If DHCP server is disabled for the interface, all the LAN
devices connected to the gateway should have a static LAN IP configured.

DHCP Server
The X300 series gateway can act as the DHCP server and assign IP addresses to devices
connecting to the LAN network. The DHCP server maintains a database of available IP addresses
and configuration information. When it receives a request from a client, the DHCP server
determines the network to which the DHCP client is connected, allocates an IP address or prefix
appropriate for the client, and sends configuration information appropriate for that client.
DHCP servers typically grant IP addresses to clients for a limited interval called a lease. DHCP
clients are responsible for renewing their IP address before that interval has expired, and muststop using the address once the interval has expired, if they have not been able to renew it. DHCP
is used for IPv4 and IPv6. While both versions serve the same purpose, the details of the protocol
for IPv4 and IPv6 are sufficiently different that they should be considered separate protocols.
Interface configuration settings are determined mainly by the protocol selection. For a descriptionof the protocol settings, see Static Address.
To edit the interface:
1. Go to Network > Interfaces, select LAN and click Edit.

X300 Series IoT Cellular Gateway User Guide15111: Network

Figure 11-3 LAN Interface (Static Address) Configuration

X300 Series IoT Cellular Gateway User Guide15211: Network

2. Configure the interface settings respective to the gateway model number.


For protocol settings, see Static Address.
Note:

General Settings – Protocol should be Static Address for the LAN interface. Gateway
is not required.



Physical Settings – By default, the LAN interface bridges the eth0.1 and wlan0
physical interfaces.



Firewall Settings – Firewall zone should be set as LAN zone.



DHCP Server – DHCP server can be used to assign IP address to clients connecting
to the LAN. To enable the DHCP server, make sure that the check box "Ignore
Interface" is not selected, and configure the other DHCP settings.

3. Click Save.
4. Click Save & Apply to save the configuration.

WWAN and WWAN6 Interface
Network > Interface > WWAN or WWAN6This page allows you to configure the WWAN and WWAN6 interface parameters. The WWAN
interface becomes active when the wireless interface is configured as lient. The wireless interface
is configured on the Network > Wireless page.
The WWAN interface supports IPv4 or dual mode IPv4/IPv6. WWAN6 interface supports IPv6
mode. Otherwise, the WWAN and WWAN6 interfaces provide similar functionality and are
configured in a similar manner.
The WWAN or WWAN6 interface will use either Static Address, DHCP client, or DHCPv6 client
protocol. On the WWAN interface, if you assign Static Address as the protocol, IPv4 gateway isrequired for external interface, but should not be used for internal use. DHCP server should bedisabled.
Interface configuration settings will vary depending on the assigned protocol. For descriptions of
the protocol settings, see Static Address, DHCP Client, or DHCPv6 Client.
To edit the interface:
1. Go to Network > Interfaces, select WWAN and click Edit.

X300 Series IoT Cellular Gateway User Guide15311: Network

Figure 11-4 WWAN Interface (DHCP client) Configuration

2. Configure the interface settings respective to the gateway.
For protocol settings, see Static Address or DHCP Client.

General Settings – To change the WWAN protocol, select the protocol and click the
Switch Protocol button. If Static IP address protocol is selected, IPv4 gateway is required
for external interface, but should not be used for internal use.



Advanced Settings – Similar to WAN DHCP settings, except the metric is fixed by default
for other features to work as per requirement.



Firewall Settings – Firewall zone should be set as WAN zone.



DHCP Server – DHCP server should be disabled.

3. Click Save.
4. Click Save & Apply to save the configuration.

Add Virtual Interface
The virtual network interface allows you to configure a new interface such as a VPN tunnel that
encapsulates data inside a transport protocol. The supported tunneling protocols include GRE,
L2TP, WireGuard VPN, PPP, and PPtP.
The virtual interface can be created for other reasons, such as to configure a relay bridge toextend the wireless network.
Note: Adding a virtual interface may require modifications to the load balancer
configuration. For load balancer configuration, see Load Balancing. For additional supportand knowledge base articles, please visit Lantronix Support.

X300 Series IoT Cellular Gateway User Guide15411: Network
To add a new interface:
1. Go to Network > Interfaces, scroll to the bottom of the list of interfaces and click Add newinterface.
Figure 11-5 Network Add New Interface

2. Enter the interface name. The name must include only alpha numeric characters and special
character underscore ( _ ).
3. Select the protocol to assign to the interface.
4. Click Create interface.
5. Configure the interface settings relative to the selected protocol.


The first field below the protocol selection is Bring up on boot. This is enabled by default
and will start the interface when the gateway is booted.



For the remaining configuration details, see Table 11-10.

6. Click Save to save the new interface.
7. Click Save & Apply to apply the configuration to the gateway.
Table 11-10 VPN Tunnel Protocols
ProtocolDescription

GRE

X300 Series IoT Cellular Gateway User Guide15511: Network

ProtocolDescription

GRE General Settings

 Bring up on boot – Start the interface when the device is booted.

Selected by default.
 Enable GRE tunnel – Enable the interface.
 GRE Server Address – Enter the WAN IP address or domain nameof the remote GRE server.
 Local Address – Enter the WAN IP address of the gateway
 Local Tunnel Address – Enter the local IP address of the gateway on

the GRE tunnel Remote Tunnel Address – Enter the remote IP address on the GRE

tunnel Keepalive Interval (in minutes) – The amount of time before sendinga keepalive probe packet to check the connection
 Keepalive Retries – The number of unanswered echo requests

before considering the peer dead
 Interface – Enter the interface to bind to GRE. GRE cannot movefrom one interface to another. It must be bound to a particularinterface.
GRE Advanced Settings

 Use builtin IPv6 management – Allows to use the built in IPv6

management configuration
 Force link – Select this option to assign interface properties

regardless of the link being active or not.
If not selected, items are assigned only after the link has become
active. This is the default.
GRE Firewall Settings

Select the WAN zone as the firewall zone.

L2TP
L2TP General Settings

 Bring up on boot – Start the interface when the device is booted.

Selected by default.
 L2TP Server – Enter the public IP address of the VPN server for

L2TP connection
 PAP/CHAP username – Enter the PAP/CHAP username. The

default password is admin.
 PAP/CHAP password – Enter the PAP/CHAP password.

L2TP Advanced Settings

Advanced settings are similar to those of PPPoE with a few exceptions
as noted below. For configuration details, see UMTS/GPRS/EV-DO
Cellular.
 Keepalive Requests is similar to LCP echo failure threshold.
 Checkup Interval is similar to Inactivity timeout.
 L2TP does not include fields for LCP echo interval or Host-Uniq tag

content.
L2TP Firewall Settings

Select the WAN zone as the firewall zone.

PPP
PPP General Settings

 Modem device – Select the modem device from the list.
 PAP/CHAP username – Enter the PAP/CHAP username. The

default password is admin.
 PAP/CHAP password – Enter the PAP/CHAP password.

PPP Advanced Settings

Advanced settings are similar to those of PPPoE. For configuration
details, see UMTS/GPRS/EV-DO Cellular.

PPP Firewall Settings

Select the WAN zone as the firewall zone.

PPtP

X300 Series IoT Cellular Gateway User Guide156

11: Network

ProtocolDescription

PPtP General Settings

Note: Enabling PPtP will also enable a 20 mins PPtP watchdog which
will reboot the gateway in absence of an active PPtP connection for aperiod of 20 mins.
 VPN Server – Enter the public IP Address or DNS name of theremote VPN Server for the PPTP connection.
 PAP/CHAP username – Enter the PAP/CHAP username.
 PAP/CHAP password – Enter the PAP/CHAP password. The default

password is admin.
 Interface – Select the interface that the device will use to initiate the

PPtP connection.
 Unspecified – use the active interface to make the connection.

PPtP Advanced Settings

Advanced settings are similar to those of PPPoE. For configuration
details, see UMTS/GPRS/EV-DO Cellular.
One additional setting is described below:
 Use mppe – Select to enable encryption if this setting is enabled on

the remote server.
PPtP Firewall Settings

 Select the WAN zone as the firewall zone.

WireGuard VPN
WireGuard VPN General
Settings

For details on how to configure a VPN connection using WireGuard
VPN, see WireGuard VPN on page 89.
 Bring up on boot – Start the interface when the device is booted.

Selected by default.
 Private Key – Enter the private key of the device.
 Listen Port – Optional. By default WireGuard uses UDP port 51820.
 IP Addresses – Recommended. Enter the IP addresses of the

WireGuard interface.
WireGuard VPN Advanced
Settings

 Use builtin IPv6 management – Allows to use the built in IPv6

management configuration
 Force link – Select this option to assign interface properties

regardless of the link being active or not.
If not selected, items are assigned only after the link has become
active. This is the default.
 Metric – Optional. Metric of the interface
 MTU – Optional. Maximum Transmission Unit of the tunnel interface
 Firewall Mark – Optional. Enter 32-bit mark for outgoing encrypted
packets. Enter value in hex, starting with 0x.
WireGuard VPN Firewall
Settings

Select the firewall zone.

WireGuard VPN Peers This page lets you add a WireGuard peer. For information about

WireGuard interfaces and peers, visit https://www.wireguard.com.

Relay Bridge
The Relay Bridge protocol provides an option to implement bridge behavior (on IPv4 only) toextend the wireless network. The virtual interface must have a local IPv4 address to access thebridge connection and relay between two networks.

X300 Series IoT Cellular Gateway User Guide157

11: Network

Wireless
Network > Wireless
The Wireless interface on the gateway can operate in two modes:

Client mode – The gateway will act as a Wi-Fi client to existing wireless networks. The
gateway will accept Internet access through wireless access provided by another service
provider and then distribute the access to the machines connected to the gateway on its LAN
interface.

Access point (Master) mode – The gateway will act as a wireless access point to provide awireless LAN network that wireless clients may join.

The gateway can act as Wi-Fi master and client at the same time provided that the gateway's
Wi-Fi client is connected to any AP.
Figure 11-6 and Table 11-11 describe the Wireless Overview and Associated Stations.
Figure 11-6 Wireless Overview

Table 11-11 Wireless Overview and Associated Stations
Parameters

Description

Wireless Overview

Displays status and details about the wireless radio and wirelessinstances.
The gateway provides the following interaction with the wireless radio: Restart – restart the radio Scan – scan for available wireless connections and join a network.

This also adds a new client instance.
 Add – add a new instanceThe gateway provides the following interaction on the wireless interface
instances: Disable/Enable – disable or enable the instance Edit – edit the instance configuration settings
 Remove – delete the instance

X300 Series IoT Cellular Gateway User Guide158

11: Network

Parameters

Description

Associated Stations

Displays details about associated wireless stations such as network,
MAC address, host, signal and Rx/Tx (rate).

Wireless Network Configuration
Note:

When Wi-Fi is configured as Client, the WWAN interface will become active.

Wi-Fi Client
To join a wireless network in client mode:
1. Go to Network > Wireless.
2. Click Scan to find available wireless networks. The scan results will display a list of networks.
3. Select the network that you want to connect to and click Join Network.
4. On the wireless configuration window, enter the settings to join the network based on the
network’s encryption method (WPA, WPA2, WPA3 SAE, mixed WPA/WPA2). The assigned
firewall zone should be WAN. If you select Replace wireless configuration, all existing
networks will be deleted from the radio. Click Submit.
5. Configure the wireless network client. For details, see Table 11-12 and Table 11-13.
6. Click Save.
The client instance is created and the access point to which it is associated appears under
Associated Stations.
7. Click Save & Apply.
Wireless Access Point
To configure the wireless instance as an access point:
1. Go to Network > Wireless.
2. If an access point exists and you want to edit it, click Edit.
3. If no access point exists, click Add to create an instance.
4. Configure the device and interface settings, selecting Access point as the Wi-Fi interface
mode. For configuration details, see Table 11-12 and Table 11-13.
5. Click Save.
6. The access point instance is created or modified.
7. Click Save & Apply.
Table 11-12 Wireless Device Configuration
Parameters

Description

General Setup

X300 Series IoT Cellular Gateway User Guide

159

11: Network

Parameters

Description

Status

Displays the following details:
 Mode – Master (access point) or Client SSID – Service Set Identifier (SSID) is a public identifier up to 32

characters that uniquely names a Wi-Fi connection.
 BSSID – Basic Service Set Identification (BSSID); 24 bit MAC

Address of Wireless Access Point Encryption – data encryption method
 Channel – wireless channel and frequency band
 Tx-Power – transmit power in dBm
 Signal/Bitrate – signal strength in dBm and bitrate in Mbit/sec
 Country – country code

Wireless network is enabled/
disabled

The field label displays the state of the wireless network as either
enabled or disabled.
Click Enable or Disable to update the network operation state.

Operating Band

By default, ‘auto’ lets the wireless device select the operating band touse. Alternatively, choose the band and channel.
Channels are defined in 5 MHz increments and are 20 MHz wide. It's
recommended to select 'auto' or to select channels that don't overlap
with channels used by other access points in the immediate area of theaccess point that you are configuring.

RoamingRoaming State

Enable or disable the roaming state, which allows the wireless client tomake roaming choices of which AP to associate to.

Level

Select preconfigured roaming settings or select Custom to configure
custom settings for the client.

Time interval for consecutivescans

The interval in seconds between scans.

RSSI Delta for 2.4G

The RSSI delta for 2.4G represents the roaming threshold at which theclient will roam to the target AP.

RSSI Delta for 5G

The RSSI delta for 5G represents the roaming threshold at which theclient will roam to the target AP.

Scan Threshold for 2.4G

The 2.4G scanning threshold in dbm, after which the client will scan forpotential target APs.

Scan Threshold for 5G

The 5G scanning threshold in dbm, after which the client will scan forpotential target APs.

Table 11-13 Wireless Interface Configuration
Parameters

Description

General Setup
Mode

Select the Wi-Fi Interface mode.
 Access Point – gateway will act as an access point (master mode) Client – gateway will act as a wireless client

The default mode is Access Point.
ESSID

Displays the device name assigned to the gateway.

X300 Series IoT Cellular Gateway User Guide160

11: Network

Parameters

Description

Priority

The order of preference in which the gateway will attempt to join theconfigured wireless networks. The range is from 1 to 8 with 1 being thehighest priority and 8 being the lowest priority.

BSSID

This field is displayed for Client only.
Basic Service Set Identifier (BSSID) – 48-bit MAC address for theaccess point of the BSS. This can be left blank.

Network

Select LAN for the Access Point or WWAN for Client Mode to configure
the gateway as LAN or WWAN respectively.

Hide ESSID

Select Hide ESSID, to hide ESSID when client machines scan foravailable Wi-Fi networks.

Wireless Security
Encryption

Select the Encryption mode for Wi-Fi network.
Available Options:
 WPA3 Transition Mode (strong security)
 WPA2-EAP (strong security)
 WPA3 SAE (strong security)
 WPA2-PSK/WPA-PSK Mixed mode (medium security)
 WPA-PSK (medium security)
 WPA-EAP (medium security) Open (no security)

The default encryption mode for access point configuration is WPA2PSK/WPA-PSK Mixed mode.
WPA3 only applies to the STA (client) interface
CipherFor all encryption modes except No Encryption.
Select the cipher suitable to the gateway.
Options:
 Auto Force CCMP (AES) Force TKIP Force TKIP and CCMP (AES)

The default cipher is auto mode.
Key

Enter the key respective to cipher type

Enable key reinstallation(KRACK) countermeasures

This setting is displayed only if the interface is an Access Point.
Select to enable KRACK countermeasures.
This setting is disabled by default.

MAC-Address Filter
MAC-Address Filter

Allows or blocks certain client MAC Addresses. Default is disabled.
This setting applies only to Access point mode.
Options:
 Disable Allow listed only – If this option is selected, choose the client MAC

Addresses to allow.
 Allow all except listed – If this option is selected, choose the client

MAC Addresses to block.

X300 Series IoT Cellular Gateway User Guide161

11: Network

Default Wireless Client Profile
The X300 series device includes a default WLAN client profile configured for AP with SSID
“Lantronix_Initial_Default_Infra” and “Open” security. The default profile is designed forprovisioning gateways connected to a Wi-Fi hotspot set as “Lantronix_Initial_Default_Infra” toallow initial configuration of multiple gateways via Lantronix Provisioning Manager (LPM) using
each device’s WAN interface.
Once the device connects to this SSID, it will automatically open the following firewall rules for
Lantronix Provisioning Manager to discover and configure the device:AcceptDiscoveryWan

AcceptSSHWan

AcceptWeb

AccessWanPS

AcceptWebAccessWanP

Configure the devices using LPM and then disconnect them from this SSID. When the device
disconnects from this SSID, it will automatically close the above firewall rules. Only the rules whichwere automatically opened are closed. No change is made if they were already opened by theuser.
It is the responsibility of the user to disable or delete the profile after the initial configuration.

X300 Series IoT Cellular Gateway User Guide162

11: Network

DHCP and DNS
Network > DHCP and DNS
Dynamic Host Configuration Protocol (DHCP) is a network protocol that is used to configure
network devices to communicate on an IP network. A DHCP client uses the DHCP protocol toacquire configuration information, such as an IP address, a default route, and one or more DNS
server addresses from a DHCP server. The DHCP client then uses this information to configure its
host. Once the configuration process is complete, the host is able to communicate on the network.
For details about basic setup of DHCP server on the LAN side see DHCP Server.
The DHCP and DNS page allows you to configure advanced options such as custom DNS
servers, custom lease files, advanced TFTP settings and MAC Address-based IP Address
allocation.
To configure:
1. Go to Network > DHCP and DNS.
2. Enter the configuration settings. See Table 11-14 to Table 11-18.
3. Click Save & Apply.

General Settings
Network > DHCP and DNS > General Settings
Table 11-14 General Configuration of DHCP Server and DNS-ForwarderParameters

Description

Server Settings
Domain required

Check to allow forwarding of DNS request only if they have domain
name.

Authoritative

Check to authorize the DHCP in the local network.

Local serverEnter the local server domain specification. These domain names are
only resolved using DHCP or host files.

Local domain

Enter the local domain suffix appended to DHCP names and host file
entries.

Log queries

Log the DNS request received in the syslog server.

DNS forwardingsEnter the DNS Server names to forward the received DNS requests.

Rebind protection

Check to discard upstream RFC1918 responses

Allow localhost

Check to allow upstream responses in the 127.0.0.0/8 range, e.g. for
RBL services

Domain whitelistEnter the list of domain name to allow RFC1918 responses.

Local Service Only

Select to accept DNS queries only from hosts whose address is on a
local subnet.

Non-wildcard

Select to bind only configured interface addresses, instead of thewildcard address.

Listen Interfaces

Restrict listening to the specified interfaces.

Exclude Interfaces

Prevent listening on the specified interfaces.

Active DHCP Leases

X300 Series IoT Cellular Gateway User Guide16311: Network

Parameters

Description

Hostname

Name of the device that is connected to the gateway and has beenleased an IP Address by DHCP server.

IPv4-Address

IPv4 Address assigned to the device connected to the gateway.

MAC-Address

MAC address of the device connected to the gateway.

Leasetime remaining

Remaining time until which the device can use the DHCP server leased
IP Address.

Active DHCPv6 Leases
Hostname

Name of the device that is connected to the gateway and has beenleased an IPv6 Address by DHCPv6 server.

IPv6-Address

IPv6 Address assigned to the device connected to the gateway.

DUID

DUID (Device Unique Identifier) of the device connected to the gateway

Leasetime remaining

Remaining time until which the device can use the DHCPv6 severleased IPv6 Address.

Static Leases
Hostname

Name of the device that is connected to the gateway and has been
assigned a static IP Address.

MAC-Address

MAC address of the device connected to the gateway.

IPv4-Address

IPv4 Address to be assigned to the device connected to the gateway.

IPv6-Suffix (hex)

IPv6 Address to be assigned to the device connected to the gateway.

Resolv and Host Files
Network > DHCP and DNS > Resolv and Host File
Table 11-15 Resolv and Host File Configuration for DHCP and DNSParameters

Description

Use /etc/ethers

Check to use /etc/ethers for configuring the DHCP-Server.

Leasefile

Enter the directory path name where given DHCP-leases will be stored.

Ignore resolve file

Check to ignore the resolved file.

Resolve file

Enter the local DNS file.

Ignore /etc/hosts

Check to ignore the hosts file.

Additional Hosts file

Enter the additional host files.

TFTP Settings
Network > DHCP and DNS > TFTP Settings
This page provides settings to configure the gateway as a Trivial File Transfer Protocol (TFTP)
server, which can be used to serve files for download to a remote TFTP client.
Table 11-16 TFTP Configuration for DHCP and DNSParameters

Description

Server Settings

X300 Series IoT Cellular Gateway User Guide16411: Network

Parameters

Description

Enable TFTP server

Check to enable TFTP server.
By default, the TFTP server is in disabled.
 TFTP server root – Enter the Root directory for the files served using

TFTP.
 Network boot image – Enter the Filename of the boot image which isadvertised to the clients.

Advanced Settings
Network > DHCP and DNS > Advanced Settings
Table 11-17 Advanced Configuration for DHCP and DNSParameters

Description

Server Settings
Suppress logging

Suppress logging of the routine operation of DHCP. Errors andproblems will still be logged.

Allocate IP Sequentially

Force DHCP server to allocate IP addresses sequentially, starting fromthe lowest available address.
In this mode, clients that allow a lease to expire are more likely to move
IP address.

Filter private

Check to deny the reverse lookups for local networks.

Filter uselessCheck to deny the requests that cannot be answered by public nameservers.
By default the request are forwarded.

Localize queries

Check to localize hostname depending on the requesting subnet if
multiple IP Addresses are available.

Expand hosts

Check to add local domain suffix to names served from hosts files.

No negative cache

Check to deny caching the negative replies, e.g. for non-existingdomains.

Additional Servers file

List of DNS servers to forward requests to.

Strict order

DNS servers will be queried in the order of the resolve file.

All Servers

Select to query all upstream DNS servers.

Bogus NX Domain OverrideEnter the hostname that supply bogus NX domain results.

DNS server port

Enter the listening port for inbound DNS queries.
The default DNS server port is 53.

DNS query port

Enter the fixed source port number for outbound DNS queries.
The default DNS query port is “any”

Max. DHCP leases

Enter the maximum number of allowed DHCP leases that are active.
By default unlimited DHCP leases are allowed.

Max. EDNS0 packet size

Enter the maximum allowed size of EDNS.0 UDP packets.
The default EDNS.0 UDP packet size is 1280.

Max. concurrent queries

Enter the maximum number of concurrent DNS queries allowed.
By default 150 concurrent DNS queries are allowed.

X300 Series IoT Cellular Gateway User Guide16511: Network

Parameters

Description

Size of DNS query cacheEnter the maximum number of cached DNS entries.
By default, 150 DNS entries are cached. Maximum is 10000. A value ofzero (0) means no caching.

Static Leases
Network > DHCP and DNS > Static leases
Table 11-18 DHCP and DNS Static Leases
Parameters

Description

Add

Click to add a static lease.

Active DHCP Leases
Hostname

Name of the device that is connected to the gateway and has beenleased an IP Address by DHCP server.

IPv4-Address

IPv4 Address assigned to the device connected to the gateway.

MAC-Address

MAC address of the device connected to the gateway.

Leasetime remaining

Remaining time until which the device can use the DHCP server leased
IP Address.

Active DHCP6 Leases
Hostname

Name of the device that is connected to the gateway and has beenleased an IPv6 Address by DHCPv6 server.

IPv6-Address

IPv6 Address assigned to the device connected to the gateway.

DUID

DUID (Device Unique Identifier) of the device connected to the gateway

Leasetime remaining

Remaining time until which the device can use the DHCPv6 severleased IPv6 Address.

Static Leases
Hostname

Name of the device that is connected to the gateway and has been
assigned a static IP Address.

MAC-Address

MAC address of the device connected to the gateway.

IPv4-Address

IPv4 Address to be assigned to the device connected to the gateway.

IPv6-Suffix (hex)

IPv6 Address to be assigned to the device connected to the gateway.

X300 Series IoT Cellular Gateway User Guide

166

11: Network

Hostnames
Network > Hostnames
Allows you to enter host names for the devices on the LAN.
To add a host name:
1. Go to Networks > Hostnames.
2. Click Add.
3. Enter the hostname and the IP address of the host. See Table 11-19.
4. Click Save.
5. Click Save & Apply.
Table 11-19 Hostnames Configuration
Parameters

Description

HostnameEnter the Hostname. The hostname can contain any combination ofalphabetic characters, numbers, dashes, and underscores. No otherspecial characters are allowed.

IP addressEnter the IP Address of the host.

Static Routes
Network > Static Routes
Configure static routes to define the explicit path between two different networks located in two
different domains. Static routes must be manually reconfigured when network changes occur.
To configure static routes:
1. Go to Networks > Static Routes.
2. Select IPv4 or IPv6 tab.
3. Click Add.
4. Enter the configuration settings. For IPv4 static routes, see Table 11-20 and for IPv6 static
routes, see Table 11-21.
5. Click Save.
6. Click Save & Apply.

Static IPv4 Routes
Table 11-20 Static IPv4 Routes Configuration
Parameters

Description

General Settings
Interface

Select the interface name of the parent interface this route belongs to.

TargetEnter the target host IPv4 Address or Network address if the target is a
network.

X300 Series IoT Cellular Gateway User Guide167

11: Network

Parameters

Description

IPv4-Netmask

Enter the IPv4 Netmask of the static route.

IPv4-Gateway

Enter the IPv4 gateway. If gateway is not entered, the gateway from theparent interface is used.

Advanced Settings
MetricEnter the metric of the static route.

MTU

Enter the number of bytes indicating the largest physical packet sizethat the network can transmit.
The default MTU size is 1500 bytes. A blank value represents auto
MTU size.

Route type

Select the route type.
Available options:
 unicast – route entry describes real paths to the destinations

covered by the route prefix.
 local – destinations are assigned by this host. Packets are loopedback and delivered locally.
 broadcast – destinations are broadcast addresses. Packets are sent

as link broadcasts.
 multicast – special type used for multicast routing.
 unreachable – these destinations are unreachable
 prohibit – these destinations are unreachable.
 blackhole – these destinations are unreachable. Packets are

discarded silently. Local senders get an ENVAL error.
 anycast – these destinations are anycast addresses assigned to thishost.
Route table

Define the table ID to use for the route. The table ID can be either anumeric table index ranging from 0 to 65535 or a symbolic alias
declared in /etc/iproute2/rt_tables. The following special aliases arealso recognized: local (255), main (254), default (253).

Source Address

Specify the preferred source address when sending to destinations
covered by the target.

On-Link route

If enabled, the gateway is on link even if the gateway doesn't match
any interface prefix.

Static IPv6 Routes
Table 11-21 Static IPv6 Routes Configuration
Parameters

Description

General Settings
Interface

Select the interface name of the parent interface this route belongs to.

TargetEnter the target host IPv6 Address or Network CIDR if the target is a
network.

IPv6-Gateway

Enter the IPv6 gateway for the static route. If gateway is not entered,
the gateway from the parent interface is used.

Advanced Settings
MetricEnter the metric of the static route.

X300 Series IoT Cellular Gateway User Guide16811: Network

Parameters

Description

MTU

Enter the number of bytes indicating the largest physical packet sizethat the network can transmit.
The default MTU size is 1500 bytes. Blank value represents auto MTU
size

Route type

Select the route type.
Available options:
 unicast – route entry describes real paths to the destinations

covered by the route prefix.
 local – destinations are assigned by this host. Packets are loopedback and delivered locally.
 broadcast – destinations are broadcast addresses. Packets are sent

as link broadcasts.
 multicast – special type used for multicast routing.
 unreachable – these destinations are unreachable
 prohibit – these destinations are unreachable.
 blackhole – these destinations are unreachable. Packets are

discarded silently. Local senders get an ENVAL error.
 anycast – these destinations are anycast addresses assigned to thishost.
Route table

Define the table ID to use for the route.

Source Address

Specify the preferred source address when sending to destinations
covered by the target.

On-Link route

If enabled, the gateway is on link even if the gateway doesn't match
any interface prefix.

X300 Series IoT Cellular Gateway User Guide16911: Network

Diagnostics
Network > Diagnostics
The diagnostics feature allows you to run network utilities and cable diagnostics commands fromthe web interface.
Table 11-22 describes each of the network utilities.
Table 11-23 describes the cable diagnostics status messages.
Note: The cable diagnostics command will bring down the Ethernet port link, which willtake more time to complete the test. Cable diagnostics is only accurate for cable lengths of
7 - 120 meters.
Table 11-22 Diagnostics - Network Utilities
Network Utility

Description

Ping

IP Address or fully qualified domain name to be pinged.
Ping determines network connection between gateway and host on the
network. The output shows if the response was received, packets
transmitted and received, and packet loss if any.

Traceroute

IP Address or fully qualified domain nameTraceroute displays all the routers present between the destination IP
address and the gateway. The output shows all the gateways throughwhich data packets pass on way to the destination system from thesource system, maximum hops and total time taken by the packet toreturn measured in milliseconds.

Nslookup

IP Address or fully qualified domain name that needs to be resolved.
Name lookup is used to query the Domain Name Service for
information about domain names and IP addresses. It sends a domainname query packet to a configured domain name system (DNS) server.
If you enter a domain name, you get back the IP address to which itcorresponds. If you enter an IP address, you get back the domainname to which it corresponds. A message stating “Unknown Host”
indicates that the Internet Name does not exist.

Table 11-23 Cable Diagnostics Status Messages
Status message

Description<interface name:> No cablefaults detected

The cable link is good.

<interface name:> Open circuit
detected in cable

There is no cable.

<interface name:> Open circuit
detected in cable Distance tocable fault is ~<disance>
meter(s).

Open ended cable.

<interface name:> Short circuit
detected in cable. Distance tocable fault is ~<distance>
meter(s).

There is an issue with the cable.

X300 Series IoT Cellular Gateway User Guide170

11: Network

Status message

Description<interface name:> Short cable(less than 10 meters) detected.

Short cable detected.

<interface name:> Cable
diagnostic test failed

The cable has failed the diagnostic test. Possible failure reasons
include: interface is busy, link partner is not configured for autonegotiation, or link partner is busy establishing the link.

Firewall
Network > Firewall
The firewall policy helps secure the network. The X300 series gateways follow a zone based
firewall concept. Every interface of the gateway, whether physical or virtual, needs to be assigned
to a firewall zone, and all traffic routed through that interface is bound by the assigned policy. At aminimum, there are two firewall zones, the LAN zone and WAN zone, with one or more interfaces
assigned to each zone.
By default, there is a minimal firewall configuration predefined in the gateway. The minimal
configuration consists of global firewall settings, and two zones, the LAN zone and WAN zone
which serve as a source or destination for port forwarding, rules, and redirects. This configuration
may be sufficient for your needs with little modification. Otherwise, you can use the web interface
to modify the firewall configuration.
This section assumes that the reader has knowledge of implementing firewall policies or willconsult their network administrator to set up the firewall policies.
Note:

Create a backup of the firewall configuration before making any changes.

General Settings
The General settings page consists of the global settings and zones. The global firewall settings
are default firewall settings that do not belong to any zone.
Firewall Global Settings
To configure firewall global settings:
1. Go to Network > Firewall.
2. In the top section of the General Settings page, if desired, modify global firewall settings. See
Table 11-24.
3. Click Save & Apply to save the changes and reload the firewall.

Table 11-24 Firewall Global Settings
Parameters

Description

General Settings
Enable SYN-flood protection

Check to enable SYN-flood protection. SYN-flood protection will enablespamming detection and block whenever there is a spam attack.

X300 Series IoT Cellular Gateway User Guide

17111: Network

Parameters

Description

Drop invalid packet

Check to drop the invalid packets that are not matching any active
connection.

Input

Select to accept or reject the inbound traffic to all the interfaces.

OutputSelect to accept or reject the outbound traffic from all the interfaces.

ForwardSelect to accept or reject the forwarded traffic from all the interfaces.

Firewall Zones
Two firewall zones, the LAN zone and WAN zone, are predefined in the gateway. All traffic from
LAN to WAN has no restrictions but all incoming traffic from WAN source is blocked unless a port
forwarding rule is set or unless a particular port is opened.
A zone section groups one or more interfaces and serves as source or destination for forwarding,rules, and redirects. A zone is defined by the following rules:

Masquerade (NAT) of outgoing traffic (WAN) is controlled on a per zone basis on the outgoinginterface.



INPUT rules describe what happens to traffic trying to reach the gateway through an interface
in that zone.



OUTPUT rules zone describe what happens to traffic originating from the gateway going
through an interface in that zone.



FORWARD rules describe what happens to traffic passing between different interfaces in thatzone.

Packet filtering actions


ACCEPT – traffic is allowed to pass as if there is no firewall in place. If the port at thedestination is closed, a response will be returned as if a Reject rule is in place.



DROP – the firewall discards the packet and sends no response back to the source host thatsent the packet. The source host will wait for a response until a timeout occurs and may
attempt to retry the connection after timeout occurs.



REJECT – the firewall discards the packet and sends a response back to the source host thatthe port is closed. Doing so can hint to the source that packet filtering firewall is in place.

In general, use REJECT to deny traffic from trusted hosts by gracefully informing them that traffic
is not allowed to pass. Use DROP to deny traffic from untrusted hosts or when you don’t want
expose information about the destination host.
To configure firewall zones:
1. Go to Network > Firewall.
2. To add and configure a new firewall zone, click Add.
3. To modify settings for an existing firewall zone, click Edit.
4. Enter or modify the firewall zone settings. See Table 11-25.
5. Click Save.

X300 Series IoT Cellular Gateway User Guide172

11: Network

Table 11-25 Firewall Zones Configuration (LAN)Parameters

Description

General Settings
Name

Enter the name of the zone.

Input

Select to accept, reject or drop the inbound traffic to all the configured
zones.

OutputSelect to accept, reject or drop the outbound traffic from all theconfigured zones.

ForwardSelect to accept, reject or drop the forwarded traffic from all theconfigured zones.

Masquerading

Check to allow IP Masquerading (NAT).

MSS clamping

Check to allow MSS clamping.

Covered networks

Select the network interfaces that must be included in the zone
configuration.

General Settings / Inter-Zone Forwarding
Allow forward to destination
zones

Select to allow or deny forwarding traffic to the configured destinationzone.

Allowed forward from source
zones

Select to allow or deny forwarding traffic from the configured source
zone.

Advanced Settings
Covered devices

List of raw network device names attached to this zone

Covered subnets

List of IP subnets attached to this zone.

Restrict to address family

Select IP Address family for configuring firewall for LAN zone fromavailable options.
Available Options
 IPv4
 IPv6
 IPv4 and IPv6

Restrict Masquerading to given
source subnets

Enter the source subnet to which the masquerading must be restricted.

Restricts Masquerading to given
destination subnets

Enter the destination subnet to which the masquerading must be
restricted.

Enable logging on this zone

Check to enable logging of all the activities on the Zone.

Conntrack Settings
Allow "invalid" traffic

Select to allow invalid traffic. More specifically, when selected, no rules
can be installed that reject forwarded traffic with conntrack state equal
to invalid.
Disabled by default.

Automatic helper assignment

Automatically assign conntrack helpers for the zone.

Conntrack Settings
Extra source arguments

Extra arguments passed directly to iptables for source classification
rules.

Extra destination arguments

Extra arguments passed directly to iptables for destination
classification rules

X300 Series IoT Cellular Gateway User Guide17311: Network

Port Forwards
Network > Firewall > Port Forwards
Port forwarding allows remote computers to connect to a specific host within the LAN by opening
the WAN port and redirecting the connection (and data) on that port to an internal LAN IP and port.
By default, all WAN side ports are closed.
To view port forwarding entries, go to Firewall > Port Forwards. See Table 11-26 for a description.
You can also edit, reorder or delete the entries from this view.
Table 11-26 Firewall Port Forwards
Parameters

Description

Match

Displays the WAN TCP/UDP ports for matching the conditions before
forwarding it to LAN device.

Forward to

Displays the destination IP Address to which the traffic must be
forwarded.

EnableCheck to enable the Port Forwarding rule.

Add Port Forwarding Rule
To add a port forwarding rule:
1. Go to Network > Firewall > Port Forwards.
2. At the bottom of the Port Forwards table, click Add.
3. Enter the configuration settings. See Table 11-27.
4. Click Save.
Table 11-27 Port Forwarding Configuration for Firewall Zone
Parameters

Description

Port Forwards General Settings
Name

Enter the name of the Port Forwarding rule.

ProtocolSelect the protocol.
Available options:
 TCP
 TCP + UDP
 UDP
 ICMP unspecified custom

Source Zone

Specify the traffic source zone. This must refer to one of the firewall
zones, usually WAN.

External PortEnter the WAN port of the external network.

Destination zone

Specify the traffic destination zone. This must refer to one of the firewall
zones, usually LAN.

Internal IP addressEnter the LAN IP address of the internal network.

Internal port

Enter the LAN port number of the internal network.

Port Forwards Advanced Settings

X300 Series IoT Cellular Gateway User Guide17411: Network

Parameters

Description

Source MAC Address

The rule will match incoming traffic from the specified source mac
address.

Source IP Address

The rule will match incoming traffic from the specified source IP
address.

Source port

The rule will match incoming traffic from the specified source port
number.

External IP AddressEnter the external IP address of the gateway.

Enable NAT Loopback

Enable NAT loopback to allow one machine on the LAN network toaccess another machine on the LAN through the external IP address ofthe gateway

Extra arguments

Passes additional arguments to iptables. Should be used with care.

Traffic Rules
Network > Firewall > Traffic Rules
Traffic rules are security policies that allow or restrict access to specific ports or hosts. Ruleactions can be configured to accept, drop, or reject traffic.
The following describes good practices for configuring traffic rules.


Block all traffic by default and explicitly enable specific traffic to known services.



Allow specific traffic, using the principle of least privilege.

Specify source IP address. It’s okay to specify “any” if the service should be accessible toeveryone on the Internet, otherwise, specify the source address.

Specify the destination IP address.

Specify the destination port. The value of the destination port should never be “any”.

Rule and zone matching
The source and destination zones are tied to the target action.


If source and destination are given, the rule matches forwarded traffic.



If only source is given, the rule matches incoming traffic.



If only destination is given, the rule matches outgoing traffic.



If neither source nor destination are given, the rule defaults to an outgoing traffic rule.

To view traffic rules, go to Network > Firewall > Traffic Rules. See Table 11-28 for a description.
You can also enable or disable the traffic rule from this page view.
Table 11-28 Firewall Zone Traffic Rules
Parameters

Description

Name

Displays the name of the traffic rule.

Match

Displays the details of the traffic rule configuration and the conditions inwhich the rule is applicable.

X300 Series IoT Cellular Gateway User Guide

17511: Network

Parameters

Description

ActionAction to be taken on the traffic when the rule conditions are satisfied.
Indicates whether the rule is for incoming, forwarded, or outgoingtraffic.

EnableSelect the box to enable the traffic rule.
If the rule is enabled, clear the box to disable the rule.

Edit

Click to edit the traffic rule settings.

DeleteClick to delete the traffic rule.

Add

Click to add a new traffic rule. This button appears at the bottom of the
Traffic Rules page.

Add Traffic Rule
To add a traffic rule:
1. Go to Network > Firewall > Traffic Rules.
2. At the bottom of the Traffic Rules table, click Add.
3. Enter the configuration settings. See Table 11-29.
4. Click Save.
Table 11-29 Firewall Traffic Rule Configuration
Parameters

Description

General Settings
Name

Enter the name of the traffic rule.

ProtocolSelect the protocol from the available options.
Available options
 TCP – Allows only TCP traffic to the open port
 UDP – Allows only UDP traffic to the open port
 TCP+UDP – Allows both TCP and UDP traffic to the open port

Source zone

Select the traffic source zone. This is usually WAN zone.

Source address

Match incoming traffic from the specified source IP address

Source port

Match incoming traffic from the specified source port

Destination zones

Select the destination firewall zone. If specified the rule applies toforwarded traffic, otherwise it is treated as an input rule.

Destination address

Match incoming traffic directed to the specified destination IP address.
If no destination zone is specified, the rule is treated as an input rule.

Destination port

Match incoming traffic directed to the specified destination port.

ActionSets the target parameter to indicate the firewall action.
Options include: Accept
 Reject Drop Mark Notrack.

Advanced Settings

X300 Series IoT Cellular Gateway User Guide

17611: Network

Parameters

Description

Restrict to address familyEnter the protocol family to generate iptables rules for.
Options include: ipv4, ipv6, or any.

Source MAC address

Match incoming traffic from the specified MAC address.

Extra arguments

Enter extra arguments to pass to iptables. This can be used to specify
additional match options.

Time Restrictions
Week Days

If specified, only match traffic during the given days of the week.

Month Days

If specified, only match traffic during the given days of the month.

Start Time (hh.mm.ss)

Specify a time to start matching traffic.

Stop Time (hh.mm.ss)

Specify a time to stop matching traffic.

Start Date (yyyy-mm-dd)

Specify a date to start matching traffic.

Stop Date (yyyy-mm-dd)

Specify a date to stop matching traffic.

Time in UTC

Select to interpret all time values as UTC time instead of local time.

Custom Rules
Network > Firewall > Custom Rules
The shell script allows you to add custom iptable commands that will be executed after the firewall
is restarted, immediately after the default ruleset has been loaded.
To configure custom rules:
1. Go to Network > Firewall > Custom Rules.
2. Enter the custom iptable rule command after the commented lines. Each rule should be on a
separate line.
3. Click Save.

X300 Series IoT Cellular Gateway User Guide17711: Network

QoS
Network > QoS
QoS allows you to prioritize specific flows in network traffic to manage handling and allocation of
network capacity. Assign traffic to target classes and allocate the amount of bandwidth that isgiven to those classes. QoS service provides the following functionality:Configure two to four predefined classes with rate, priority, and packet latency (delay) settingsConfigure one or more interfaces (WAN, WWAN, LAN, cellular, VPN) with global connection
characteristics such as upload and download speed limits. Each interface can have its own
buffer.



Configure classification rules to allocate packets to the configured classes (targets). Traffic
is differentiated by source and destination IP addresses, protocols, and ports.

You can configure up to four QoS classes, although you can achieve results by configuring as few
as two classes. The predefined classes to limit traffic are Priority, Normal, Express, and Bulk, aswell as classes to limit ingress traffic, which are appended with the _down suffix. If the classes tolimit ingress traffic are configured, then the original classes will limit egress traffic only. Otherwise,
if they are not configured, then Priority, Normal, Express, and Bulk will limit both ingress andegress traffic.
To enable QoS:
Enable QoS by interface. Go to Network > QoS > Interfaces.
To configure QoS:
1. Go to Network > QoS.
2. Enter the QoS configuration settings. See Table 11-30.
3. To enable QoS, go to the Interfaces tab and select Enable to apply QoS to the interface.
4. Click Save & Apply.
Table 11-30 QoS Configure Classes
Parameters

Description

Configure Classes
NameClass name.
 Priority
 Express
 Normal BulkWhen configured, these classes will limit both egress (outgoing fromthe host) and ingress (incoming to the host) traffic.
Classes to limit ingress traffic:
 Priority_down
 Normal_down
 Express_down
 Bulk_down

If Priority_down or Normal_down are configured, then Priority or
Normal will limit egress traffic only.
Packet Size

Maximum packet size in bytes, up to 1500 bytes.

X300 Series IoT Cellular Gateway User Guide178

11: Network

Parameters

Description

Average Minimum Rate

Average rate for this class, expressed as the percentage of bandwidth

Priority

Priority of the class, expressed as percentage. The sum priority of allclasses should not exceed 100.

Packet Delay in ms

The amount of time, in milliseconds, that the packet will wait in queue
before it is transmitted.

Max Rate in percentage

Maximum rate, expressed as percentage of total bandwidthInterfaces
Name

Displays the name of the interface that QoS will be configured on.
Click Add to add an interface to the list.

EnableSelect to enable or clear to disable QoS on the interface.

Classification GroupOne classification group “Default” is defined.

Calculate Overhead

Select to enable or clear to disable.
Decreases upload and download ratio to prevent link saturation.

Half-duplex

Limit the interface to half-duplex mode.

Download Speed (kbit/sec)Enter the download limit for the interface.

Upload Speed (kbit/sec)Enter the upload limit for the interface.

Classification Rules
TargetSelect the target class.
There can be one rule set for each class. If a target is deleted and you
want to configure it, click Add.

Source HostEnter the source IP address or IP and mask (CIDR notation). All
packets that match this source host value will be included in the QoStarget class.

Destination HostEnter the destination IP address or IP and mask (CIDR notation). All
packets that match this destination host value will be included in the
QoS target class.

ProtocolPackets matching this protocol will be included in the target class

Ports

Packets matching this port or range of ports will be included in thetarget class.

Number of bytes

Packets matching this will be included in the target class.

Comment

Description field.

X300 Series IoT Cellular Gateway User Guide17911: Network

Load Balancing
Network > Load Balancing
Load balancing is a mechanism that enables balancing traffic between various links. It distributes
traffic among various links, optimizing utilization of all the links to accelerate performance andreduce operating costs. Interfaces are assigned a priority by means of a metric.

How it works
Load balancing is determined by the load metric, in other words, the weight. Each link is assigned
a relative weight and the gateway distributes traffic across links in proportion to the ratio of weights
assigned to each individual link. This weight determines how much traffic will pass through aparticular link relative to the other links.
Weights can be selected based on:

Link capacity (for links with different bandwidth)Link/Bandwidth cost (for links with varying cost)

Note: The default configuration of the load balancer is in Failover Mode with the highest
priority given to WAN, then WWAN and then Cellular.
MWAN Concept
On X300 series gateways, one or more sources of Internet can be used at the same time. In
failover mode, the gateway uses one source of Internet and fails over to another according todefined priorities. Once the source with a higher priority is online, the same will be used as a
primary source of Internet.
Priority can be defined by setting the metric. The lower the metric, the higher the priority.
The decision of when to failover or rollback is dependent on which interfaces are online and which
ones are offline. Online and offline interface status is based on the PING responses to a particularserver at a particular time interval. You can speed up the failover by sending PING packets in ashorter interval and you can add reliability by adding multiple server candidates.
Load balancing is where two or more sources of Internet are used at the same time and the load issplit between the multiple interfaces in the ratio of their assigned weights.
The gateway supports a feature called WAN affinity whereby a particular source IP, Destination IP
or a data type can be bound to a particular interface. To accomplish this, you need to create
members which correspond to physical interfaces, assign the members in a particular policy,
create rules and assign a policy to the rules.
In summary:Members correspond to physical interfaces with an assigned metric and weight

Policy consists of a member or group of members



Rules specify which traffic will use a particular policy

Globals
Network > Load Balancing > Globals
To configure MWAN global settings:
1. Go to Network > Load Balancing > Globals.

X300 Series IoT Cellular Gateway User Guide180

11: Network
2. Enter or modify the settings. See Table 11-31.
3. Click Save & Apply.
Table 11-31 MWAN Globals Configuration
Parameters

Description

Firewall mask

Enter the firewall mask value in hexadecimal, starting with 0x.

Logging

Select to enable global firewall logging and select the log level.

Update IntervalEnter the update interval for the interface routing table.
Default is 5 seconds.

Routing table lookup

Enter an additional routing table to be scanned for connected networks

Interfaces
Network > Load Balancing > Interfaces
To view and add MWAN interfaces:
1. Go to Network > Load Balancing.
2. The MWAN Interfaces table is displayed. See Table 11-32.
3. Go to the bottom of the table, enter the interface name and click Add.
4. Enter the interface settings. See Table 11-33.
5. Click Save & Apply.
Note: Configuring a large number of tracking IP addresses, a high ping count, or a low
ping interval time will result in faster switchover but will consume more data.
Table 11-32 MWAN Interface
Parameters

Description

MWAN Interfaces

Displays the interfaces and provides options to add, edit, or delete
items from the table.
 Enter the interface name (must match an existing interface name)and click Add to add member.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Name

Name of the available Interface.

Enabled

Displays the Interface status.
Yes for enabled
No for disabled

Tracking method

Displays the method used to track the interface.

Tracking source

Displays the tracking source as address or interface.

Tracking reliability

Displays the number of tracking IP addresses. The acknowledgment/
responses from these tracking IP addresses are considered todetermine the interface as up or down.

Ping interval

Displays the time in seconds between sending two successive ping
packets.

X300 Series IoT Cellular Gateway User Guide181

11: Network

Parameters

Description

Interface down

Displays the number of consecutive failed attempts after which theinterface is declared offline.

Interface up

Displays the number of consecutive successful pings after which theinterface is declared online.

MetricMetric assigned to the interface.

Edit MWAN Interface
To edit MWAN interface settings:
1. Go to Network > Load Balancing > Interfaces.
2. To modify an interface, select the interface and click Edit.
3. Modify the settings. see Table 11-33.
4. Click Save & Apply.
Table 11-33 MWAN Interface Configuration
Parameters

Description

EnabledEnable the Interface.
 No – Interface do not participate in Load Balancing.
 Yes – Interface is enabled and can connect to Internet. Onceenabled it can be tracked using ping configuration.
Initial State

Offline – traffic goes via this interface only if the load balancer haschecked the connection first.
Online – the interface is marked as online immediately.
Default is Online

Internet Protocol

Displays the internet protocol of the interface as IPv4 or IPv6.

Tracking hostname or IP
address

IP Address to which the ping requests are sent from the interface todetermine if the interface is up or down.
Leave the field blank to assume the interface is always online.

Tracking method

Select the tracking method in use. Default is ping.

Tracking source

Select the tracking source to use. Options are Interface or Address

Tracking reliability

Enter the number of responses that must be received from tracking IP
Addresses to consider the Interface as up.

Ping countEnter the number of ping packets that will be sent.
The default ping count is 5.

Ping size

Size of the ping request in bytes.
Default value is 56.

Max TTL

Displays the Max Time to Live (Max TTL) timer value to be included in
the packets that tells the recipient how long to hold or use the packet
before expiring or discarding the packet or data.

Check link quality

Select to check link quality otherwise leave box unselected.

X300 Series IoT Cellular Gateway User Guide182

11: Network

Parameters

Description

Ping timeout

Enter the time to wait for a response to ping request sent before
declaring the interface unreachable. The wait time is in seconds.
The default value depends on the interface used. Cellular will havedifferent values to reduce data consumption.

Ping intervalSpecifies the time in seconds between sending ping packets.
The default ping interval is 5 seconds.

Interface down

The number of consecutive failed attempts after which the interface isdeclared down.
The default value depends on the interface used. Cellular will havedifferent values to reduce data consumption.

Interface up

The number of consecutive successful attempts to determine thereliability of the network connection through the interface.
The default value depends on the interface used. Cellular will havedifferent values to reduce data consumption.

Metric

Displays the Interface Metric.
The route with least metric is considered as best route.
The default metric assigned to the interface is 1.
For load balancing between two interfaces, both the interfaces musthave the same metric value on the Member configuration page.

Members
Network > Load Balancing > Members
MWAN Members are profiles corresponding to individual interfaces where you can set metric andweight.
To view and add MWAN members:
1. Go to Network > Load Balancing > Members.
2. The MWAN Members table is displayed. See Table 11-34.
3. To add a member profile, at the bottom of the table enter the name and click Add.
4. Enter the settings. See Table 11-35.
5. Click Save & Apply.
Table 11-34 MWAN Members
Parameters

Description

MWAN Members

Displays the members and provides options to add, edit, or delete
items from the table.
 Enter a name and click Add to add member.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.
 The buttons to the left of the Edit button can be used to reorder theitems in the list. This does not change the configuration.
Name

Displays the interface member notation number.

Interface

Displays the name of the interface associated with the member.

X300 Series IoT Cellular Gateway User Guide183

11: Network

Parameters

Description

Metric

Displays the metric assigned to the interface.
The interface with the lowest metric has the highest priority and all datais always routed through it.
Note: If two or more interfaces have same metric configured and thatmetric is lowest compared to other interfaces, then the data/load isbalanced and data/load is distributed among the two interfaces in theratio of the respective weight.

WeightDisplays the weight assigned to the interface. Members with the same
metric will distribute load based on the weight value.

Add

Enter the name of the new interface to be added.

Edit MWAN Member
To edit an MWAN member:
1. Go to Network > Load Balancing > Members.
2. Select the member and click Edit.
3. Modify the configuration settings. See Table 11-35.
4. Click Save & Apply.
Table 11-35 MWAN Members Configuration
Parameters

Description

Interface

Select the name of the interface.

MetricEnter the interface metric.
The route with lowest metric is considered as best route.
For load balancing between two interfaces, both the interfaces musthave the same metric value.

WeightEnter the interface weight.
The default weight assigned to the interface is 2.
For load balancing between two interfaces, both the interfaces musthave the same metric value. The route with higher weight carries more
traffic. Also the connections will be distributed amongst the interfaces
with the same weight and not the actual data traffic.

Policies
Network > Load Balancing > Policies
Policies define how traffic is routed through the different WAN interfaces. Policy consists of amember or group of members. If a policy has one member, traffic will only go out through thatmember. If a policy has more than one member, members within the policy with a lower metrichave precedence and are used first. Members with the same metric will be load balanced basedon the assigned weight values.
Policy can also be configured to use one member and then fail over to another.
To view and add MWAN policies:
1. Go to Network > Load Balancing > Policies.

X300 Series IoT Cellular Gateway User Guide184

11: Network
2. The MWAN Policies table is displayed. See Table 11-36.
3. To add a policy, at the bottom of the table enter the name and click Add.
4. Enter the settings. See Table 11-37.
5. Click Save & Apply.
Table 11-36 MWAN Policy
Parameters

Description

MWAN Policies

Displays the policies and provides options to add, edit, or delete items
from the table.
 Enter a name and click Add to add policy.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Name

Name of the policy.
The name must be 15 characters or less, and may contain characters
A-Z, a-z, 0-9, _ and no spaces.
Policies must not share the same name as configured interfaces,
members or rules.

Members assigned

Interface members to which the policy is applied.

Last resort

Displays the failover routing behavior when all WAN policy members
are offline.

Errors

Displays if an error has occurred during the Policy configuration.
Error messages are displayed as warnings.

Edit MWAN Policy
To edit MWAN policy:
1. Go to Network > Load Balancing > Policies.
2. Select the policy and click Edit.
3. Modify the configuration settings. See Table 11-37.
4. Click Save & Apply.
Table 11-37 MWAN Policy Configuration
Parameters

Description

Member used

Select the interface to apply the policy on for traffic passing through theinterface.

Last Resort

Select the failover routing behavior when all WAN policy members are
offline.
Available options: unreachable (reject) blackhole (drop) default (use main routing table)

X300 Series IoT Cellular Gateway User Guide185

11: Network

Rules
Network > Load Balancing > Rules
A rule specifies what traffic to match and what policy to assign for that traffic.
The MWAN Rules page displays the rules and provides options to add, edit, or delete items fromthe table. The Rules page also lists key points to consider when configuring rules.
To add MWAN rules:
1. Go to Network > Load Balancing > Rules.
2. The MWAN Policies table is displayed. See Table 11-38.
3. At the bottom of the Rules table, add a rule name and click Add.
4. Modify the configuration settings. See Table 11-39.
5. Click Save & Apply.
Table 11-38 MWAN Rules
Parameters

Description

MWAN Rules

Displays the rules and provides options to add, edit, or delete items
from the table.
 Enter a name and click Add to add rule.
 Click Edit to modify a table entry.
 Click Delete to delete an entry from the table.

Name

Displays the rule name.

Source address

Displays the Source IP address.

Source port

Displays the Source port number.

Destination address

Displays the Destination IP address.

Destination port

Displays the Destination port number.

ProtocolDisplays the protocols on which the rule is applicable.

Policy assigned

Policy to be applied to the rule.

Errors

Displays if an error has occurred during the rule configuration.
Error messages are displayed as warnings.

Edit MWAN Rule
To edit MWAN rules:
1. Go to Network > Load Balancing > Rules.
2. Select the rule name and click Edit.
3. Modify the configuration settings. See Table 11-39.
4. Click Save & Apply.
Table 11-39 MWAN Rules Configuration
Parameters

Description

Source addressEnter the Source IP Address.

X300 Series IoT Cellular Gateway User Guide186

11: Network

Parameters

Description

Source PortEnter the Source Port number.

Destination addressEnter the Destination IP Address.

Destination port

Enter the Destination Port number.

ProtocolSelect the protocols on which the rule is applicable.

StickySelect Yes to allow traffic from the same source IP address within thetimeout limit to use the same WAN interface as the previous session.
Otherwise, select No.

Sticky timeout

Enter the stickiness timeout value in seconds.
If no value is entered, this defaults to 600.

IPset

Enter the name of the IPset rule.
IPset lets you route traffic over WAN interfaces based on a set of IP
addresses. When the ipset option is configured, the rule will match
traffic directed at the given destination IP address to the ipset set.

Logging

Select Yes to enable firewall logging. The global load balancing logging
setting must also be enabled.
Otherwise, select No.

Policy assigned

Policy to be applied to the rule.

Notification
Network > Load Balancing > Notification
MWAN Notification lets you write custom MWAN actions, to be executed with each netifd hotplug
interface event on interfaces for which MWAN is enabled. The file is interpreted as a shell script,
and is preserved during sysupgrade.
The script must start with the line “#!/bin/sh” (without quotation marks).
Commented lines (starting with #) will not be executed.
Three main environment variables are passed to the script. They are described below:# $ACTION#<ifup>#<ifdown>#<connected>#

Is called by netifd and mwan3track
Is called by netifd and mwan3track
Is only called by mwan3track if tracking was
successful<disconnected> Is only called by mwan3track if tracking has failed# $INTERFACE

Name of the interface which went up or down(e.g. "wan" or "wwan")# $DEVICE

Physical device name which interface went up or down(e.g. "eth0" or "wwan0")

X300 Series IoT Cellular Gateway User Guide187

12: Bluetooth
The X300 series gateways support dual-mode Bluetooth BR/EDR (Classic Bluetooth) and BLE
wireless connectivity. The Serial Port Profile (SPP) is included for Bluetooth BR/EDR. Bluetooth
SPP allows two Bluetooth devices to connect and exchange serial data using the Bluetooth SPP
profile for tunneling.

Bluetooth Settings
The Bluetooth Settings page lets you configure Bluetooth settings and scan for and pair toBluetooth devices.

Configure Bluetooth settings
To configure Bluetooth settings:
1. Go to Bluetooth > Settings.
2. Next to Bluetooth State, select or clear the box to enable or disable Bluetooth.
3. Enter the configuration settings. See Table 12-1.
Table 12-1 Bluetooth Settings Configuration
Parameters

Description

Bluetooth State

Select to enable or clear to disable Bluetooth.

Device name

Displays the Bluetooth device name. The name can be edited.
Note: Changing the device name will disconnect any existing
Bluetooth SPP master or slave connections.

Device Address

Displays the Bluetooth device address.

Paired devices

Displays the paired devices.
Click Unpair to unpair the device.

Allow Discovery

Select to allow the gateway to be visible to other Bluetooth devices
during a scan.
Clear the box if you do not want the gateway to be visible to otherBluetooth devices during a scan.

Scan

Click Scan to scan for nearby discoverable Bluetooth devices. A device
must be discoverable in order to pair to it.

4. Click Save & Apply.

Scan for and Pair a Device
To scan for and pair to nearby devices:
1. On the Bluetooth Settings page under Scan, click Scan. The scan will take a few seconds tocomplete.
2. The Bluetooth Scan Result page shows the discovered devices and contains the following
details:

X300 Series IoT Cellular Gateway User Guide

188

12: Bluetooth

Table 12-2 Bluetooth Scan Results
Parameters

Description

Device Address

Displays the Bluetooth device address.

Device Name

Displays the Bluetooth device name.

Type

Displays the Bluetooth service type that the device advertises.
BR/EDR – the device advertises Bluetooth BR/EDR service type andsupports SPP.
BLE (Public or Random) – the device advertises BLE service type.

RSSI

Displays the signal strength of the Bluetooth device.

Pair

Click Pair to pair the device.
The device that initiates the pairing, in this case the X300 series
gateway, acts as the master device, and the paired device acts as theslave device.

RefreshClick Refresh to run the scan again.

Dismiss

Click Dismiss to close this page.

3. Click Pair.
The paired device appears under Paired devices.
To unpair a device:
1. On the Bluetooth Settings page under Paired Devices, view the paired devices.
2. In the row containing the device to be unpaired, click Unpair.

Bluetooth SPP
Bluetooth SPP page allows you to configure the Bluetooth SPP connection and tunnel.
To use Bluetooth SPP, the Bluetooth device and the gateway must first be paired. The masterdevice makes the RFCOMM connection. Once the Bluetooth connection is established, you
should configure a tunnel on the Bluetooth SPP line to enable serial data transmission.
Either device in the Bluetooth connection can be the master or the slave, and either can be thetunnel server or client.
The following describes the Bluetooth SPP roles:

Master – The master is the device that initiates the pairing with the other Bluetooth device. The
master device can:establish the RFCOMM connection with the paired devicedisconnect the RFCOMM connection

be configured in tunnel accept (server) or tunnel connect (client) mode

Slave – The slave is the device that is paired. The slave device can:

disconnect the RFCOMM connection

be configured in tunnel accept (server) or tunnel connect (client) mode

X300 Series IoT Cellular Gateway User Guide

189

12: Bluetooth

Configure Bluetooth SPP Connection
To configure the Bluetooth SPP connection:
1. Select the Master 1 or Slave tab depending on whether the gateway is the master or slave
device.
2. Enter the line configuration settings. See Table 12-3.
3. To establish the connection, click the RFCOMM Connect button. To end a connection, click
the Disconnect button.
Table 12-3 Bluetooth SPP Line Configuration
Parameters

Description

Name

Displays the line name. The name can be edited.

State

Select to enable or clear to disable the line.

ProtocolSelect the protocol.
 Tunnel – the line will use tunnel over Bluetooth SPP connection.

Tunnel will use the settings configured under the Server or Client tab
to select tunnel accept or tunnel connect mode.
 None – no protocol will be used.
Gap Timer

Set the number of milliseconds to delay from the last character
received before the driver forwards the received serial bytes. By
default, the delay is four character periods at the current baud rate(minimum 1 msec). Gap timer range is 1 to 5000 milliseconds (default
value is 4000 msec).

ThresholdEnter the number of threshold bytes which need to be received in orderfor the driver to forward received characters. Default value is 56 bytes.

RFCOMM

Click Connect to establish the connection or Disconnect to end theconnection. The master device can connect and disconnect, while theslave device can only disconnect.

Configure Tunnel SPP Slave
To configure the Tunnel SPP Slave:
1. Go to Tunnel > Tunnel SPP Slave.
2. Enter the Accept configuration if the connection attempt originates from the network (seeTable 17-2, “Tunnel Accept Mode Configuration,” on page 202), or enter the Connect
configuration if the connection attempt originates from the gateway (Table 17-3, “Tunnel
Connect Mode Configuration,” on page 205)
3. Click Save & Apply.
4. On the remote device, configure the tunnel server or client settings appropriate for theconnection.

Configure Tunnel SPP MasterTo configure the Tunnel SPP Master:
1. Go to Tunnel > Tunnel SPP Master.
2. Enter the Accept configuration if the connection attempt originates from the network (seeX300 Series IoT Cellular Gateway User Guide

190

12: Bluetooth
Table 17-2, “Tunnel Accept Mode Configuration,” on page 202), or enter the Connect
configuration if the connection attempt originates from the gateway (Table 17-3, “Tunnel
Connect Mode Configuration,” on page 205)
3. Click Save & Apply.
4. On the remote device, configure the tunnel server or client settings appropriate for theconnection.

X300 Series IoT Cellular Gateway User Guide

191

13: Percepxion
The X300 series gateways come integrated with Percepxion® cloud platform to allow for the
remote management of devices. To set up the Percepxion client, you need to configure thefollowing settings:
Percepxion Client – to connect to the Percepxion cloud platform.

Line 1 and Line 2 – to enable remote management and data access to your application or
device attached on the serial line.

ClientTo configure the Percepxion client:
1. Go to Percepxion > Line 1.
This page displays the configuration and status for the Percepxion client.
2. Enter the client and connection configuration information. See Table 13-1.
3. Click Save & Apply.
Table 13-1 Percepxion Client Configuration
Percepxion Client

Description

EnableSelect to enable or clear to disable the Percepxion client.

Device ID

Read only. Displays the gateway’s Device ID. Device ID may be provisioned
through Lantronix Provisioning Manager.
Note: Device ID can only be provisioned once. It will persist across resets.

Serial Number

Read only. Displays the serial number of the device.

Device NameEnter the Percepxion Device Name.

Device Description

Enter the Percepxion Device Description.

Status Update
Interval (in minutes)

Enter the frequency that the gateway updates the device status to Percepxion. The
valid range is between 1 minute and 1440 minutes (1 day).

Send dynamic
updatesIf selected, device agent will send updates for RSSI and Temperature. The fields
will be updated dynamically on the Percepxion Explore page.
This field is disabled by default.

Content Check
Interval (in hours)Enter the frequency that the gateway checks Percepxion for updates toconfiguration or firmware. The valid range is between 1 hour and 2160 hours (90days).

Apply Firmware
Updates

Select to allow firmware updates to be applied via Percepxion. Enabled by default.

Apply Configuration
Updates

Select the option to indicate when to apply configuration updates.

Reboot After Update

Automatically reboot device after configuration update.

Allow Remote
Connections

Select to allow remote connections or clear to disable.

 Always: signifying configuration updates will always apply.
 Never: never apply configuration updates.

Enabled by default.

X300 Series IoT Cellular Gateway User Guide

192

13: Percepxion

Percepxion Client

Description

Remote Access Local Local port for remote access connection
Port
Audit Log

If checked, client will send audit events such as user login, firmware update,configuration update, and CLI access to Percepxion server.

Active Connection

Select the connection instance to use when connecting to Percepxion. You canconfigure two connections. The configuration options for Connection 1 andConnection 2 are listed below.

Connection 1/Connection 2
Connect to

Select Cloud or On-premise connection.

Host

Enter the host name or IP address of the Percepxion server, used to register thedevice.

PortEnter the Percepxion port.
Default: 443

Secure Port

Select to enable or clear to disable the Percepxion client secure port 443.

Validate Certificates

Select to enable or clear to disable the validation of the Percepxion server
certificates. To validate certificates, both MQTT Security and Secure Port must be
enabled.

Local Port

Local port for Percepxion MQTT client. When configured, a total of 32 consecutive
ports will be reserved.

MQTT State

Select to enable or clear to disable MQTT.

MQTT PortEnter the port number of the Percepxion MQTT server. When configured, a total of
32 consecutive ports will be reserved.

MQTT Security

Select to enable SSL for MQTT.

MQTT Local Port

Local port for Percepxion MQTT client. When configured, a total of 32 consecutive
ports will be reserved.

Use Proxy

Select to enable the use of a proxy for this connection. If enabled, complete theproxy fields displayed under the Use Proxy field.
Disabled by default.

Proxy Type

Proxy server type. The supported type is SOCKS5.

Proxy Host

Hostname or IP address of the proxy server to be used.

Proxy Port

Port of the proxy server to be used. Default port is 80.

User Name

Username for the proxy server.

Password

Password for the proxy server.

Percepxion Line
Configure Percepxion Line settings to enable remote management and data access to yourapplication or device attached on the serial line. The gateway offers 1 (one) line for configuration.
To configure Percepxion Line settings:
1. Go to Percepxion > Line 1.
This page displays the configuration and status for Percepxion Line.

X300 Series IoT Cellular Gateway User Guide193

13: Percepxion
2. Enter the following information. See Table 13-2.
3. Click Save & Apply.
Note:

The Serial line mode should be configured as None or Tunnel.
Table 13-2 Percepxion Line

Percepxion Line

Description

EnableSelect to enable or clear to disable the Percepxion line client.

Project Tag

Enter the Percepxion project tag string, as provided by the Percepxion project
administrator.

Status Update
IntervalEnter the frequency in minutes that the gateway updates the device status to
Percepxion. The valid range is between 1 minute and 1440 minutes (1 day).

Content Check
IntervalEnter the frequency in hours that the gateway checks Percepxion for updates toconfiguration or firmware. The valid range is between 1 hour and 2160 hours (90days).

Command Delimiter

Enter the command delimiter for attached serial devices.
Note: Send delimiter before command and after response is received.

X300 Series IoT Cellular Gateway User Guide194

14: Discovery
Query port service running on the device allows network discovery of devices using Lantronix
Provisioning Manager. If enabled, the device responds to auto-discovery messages on port
0x77FE.

Query PortThis page displays the current query port statistics and the configuration option to enable ordisable discovery.
Query port is enabled by default.
To enable or disable query port discovery:
1. Go to Discovery > Query Port.
2. Under Configuration, select or clear Enable.
3. Click Save & Apply.

X300 Series IoT Cellular Gateway User Guide19515: Serial
The X300 series gateways offer one serial port that uses a standard RS-232 interface. Serial
settings such as baud rate, parity, data bits, stop bits, and flow control apply to this line.
For wiring configuration details for the RS-485 port in half-duplex mode, see B: Power Cable
Schematic.
The default serial settings:
Baud rate: 115200



Parity: None

Data bits: 8

Stop bits: 1

Flow control: None

Serial Line Statistics
View-only status information displays line statistics including information on bytes, queued bytes,
breaks, flow control, parity errors, framing errors, overrun errors, no Rx buffer errors, CTS input,
RTS output, DSR input, and DTR output.
To view line statistics, go to Serial and select Serial 1.

Serial Line Configuration
To configure Serial line settings:
1. Go to Serial > Serial 1.
2. Enter the line configuration settings. See Table 15-1.
3. Click Save & Apply.
Table 15-1 Serial Line Configuration
Parameters

Description

Name

Descriptive name.

Enabled

Select to enable the line on the serial port.

Interface RS232.
 RS485 Half-Duplex
 RS485 Full-Duplex

Termination

Termination of the RS485 bus, if available.
 Enabled Disabled

Is baudrate custom

If using a custom baud rate, select the box and add a value between
2400 bps and 921600 bps.

X300 Series IoT Cellular Gateway User Guide

196

15: Serial

Parameters

Description

Baud Rate

Select the desired baud rate from the drop-down list.
Baud rate options: 2400, 4800, 9600, 19200, 38400, 57600, 115200,
230400, 460800, 921600

ParitySelect parity from the drop-down list:
 None Even Odd

Data Bits

Select data bits from the drop-down list: 7
 8

Stop Bits

Select the stop bits from the drop-down list.
 1
 2

Flow Control

Select the flow control from the drop-down list.
 None Hardware
 Software

Gap Timer

Set the number of milliseconds to delay from the last character
received before the driver forwards the received serial bytes. By
default, the delay is four character periods at the current baud rate(minimum 1 msec). Gap timer range is 1 to 5000 milliseconds (default
value is 4000 msec).

ThresholdSet the number of threshold bytes which need to be received in orderfor the driver to forward received characters. Default value is 56 bytes.

Mode

Select the mode of serial communication:
 None – can be used if Percepxion line is configured Tunnel – (see Chapter 17: Tunnel ) Tunnel/Modbus RTU to Modbus TCP – (see Tunnel Modbus RTU to

Modbus TCP) Managed Device

X300 Series IoT Cellular Gateway User Guide197

16: SSL
Secure Sockets Layer (SSL) is a protocol that creates an encrypted connection between devices.
It also provides authentication and message integrity services. SSL is used widely for securecommunication to a Web server, and for wireless authentication.
SSL certificates identify the X300 series gateway to peers and are used with some methods ofwireless authentication. Provide a name at upload time to identify certificates on the gateway.
You can upload Certificate and Private key combinations, obtained from an external Certificate
Authority (CA), to the gateway. The gateway can also generate self-signed certificates withassociated private keys.

Credentials
The gateway can generate self-signed certificates and their associated keys for both RSA andDSA certificate formats. When you generate certificates, assign them a credential name to help
identify them on the gateway. After you create your credentials, configure them with the desired
certificates.
To configure a new credential:
1. Go to SSL > Credentials.
2. Type the name for your credential in the Credential Name field.
3. Enter the fields under Upload Certificate (see Table 16-1) or Create New Self-Signed
Certificate (see Table 16-2).
4. Click Save & Apply. The process to create a self-signed certificate can take up to 30 seconds,
depending on the length of the key.
The newly created credential is displayed at the top of the SSL Credentials page.
To view a credential:
1. Go to SSL > Credentials.
2. Under Current Credentials, click the name of the credential to view its details.
To delete a credential:
1. Go to SSL > Credentials.
2. Under Current Credentials, click the Delete button next to the name of the credential.

Table 16-1 SSL Credentials - Upload Certificate
Field

Description

SSL Certificate

Click the Select file... button to browse to the SSL certificate to be
uploaded. RSA or DSA certificates are allowed.

X300 Series IoT Cellular Gateway User Guide198

16: SSL

Field

Description

Certificate Type

Select the certificate type to upload:
 PEM
 PKCS7
 PKCS12

For PKCS certificates, enter a password.
Ensure that the certificate is formatted properly with a valid open andclose tag.
SSL Private Key

Click the Select file... button to browse to the SSL private key to be
uploaded. The key must belong to the entered certificate.
Ensure that the private key associated to the selected certificate andthat it is formatted properly with a valid open and close tag.

Key Type

Select the key type being uploaded:
 PEM
 Encrypted PEM
 PKCS12For encrypted PEM or PKCS12 key types, enter a password.

Table 16-2 SSL Credentials - Create Self-Signed Certificate
Field

Description

Country (2 Letter code)

Enter the 2 letter code for the country where the organization is located.
This is a two-letter ISO code (e.g., “US” for the United States).

State/ProvinceEnter the state or province where the organization is located.

Locality (City)Enter the city where the organization is located.

Organization

Enter the organization name to which the gateway belongs.

Organization UnitEnter the organization unit which specifies the department ororganization to which the gateway belongs.

Common NameEnter a network name for the gateway when installed in the user’s
network (usually the fully qualified domain name). It is identical to thename that is used to access the gateway with a web browser without
the prefix http://. In case the name given here and the actual
network name differ, the browser will pop up a security warning when
the gateway is accessed using HTTPS.

Expires

Type the date that the self-signed certificate expires in mm/dd/yyyy
format.

Type

Select RSA, DSA, or ECDSA.

Key length

Select the key length in bits.

Trusted Authorities
One or more authority certificates are used to verify the identity of a peer. Authority certificates areused with some wireless authentication methods. These certificates do not require a private key.
To upload an authority certificate:
1. Go to SSL > Trusted Authorities.

X300 Series IoT Cellular Gateway User Guide

199

16: SSL
2. Enter the Upload Certificate fields. See Table 16-3.
3. Click Save & Apply.
Table 16-3 SSL Trusted Authority
Field

Description

SSL Certificate

Click the Select file... button to browse to an existing SSL authority
certificate.
RSA or DSA certificates are allowed.
The format of the authority certificate can be PEM or PKCS7. PEM files
must start with “-----BEGIN CERTIFICATE-----” and end
with “-----END CERTIFICATE-----”. Some certificate
authorities add comments before and/or after these lines. Thosecomments must be deleted before upload.

Certificate Type

Select the certificate type through the drop-down list.
This field may automatically update, depending upon extension of thecertificate entered.

Clear

Click to clear the fields.

To delete an existing certificate authority:
1. Go to SSL > Trusted Authorities.
2. Under Current Certificate Authorities, click the Delete button next to the name of the authority.

X300 Series IoT Cellular Gateway User Guide200

17: Tunnel
Tunneling allows serial devices to communicate over a network without being aware of the devices
that establish the network connection between them. The Tunnel settings allow you to configure
how the serial network tunneling operates. Tunneling is available on the serial line.

Tunnel Statistics
Tunnel statistics contains data counters, error counters, connection time and connection
information. Statistics are available at each individual connection and aggregated across allconnections.
To view tunnel statistics, go to Tunnel and select Tunnel 1, Tunnel SPP Slave, or Tunnel SPP
Master.

Tunnel Modbus RTU to Modbus TCP
The gateway acts as a converter between a Modbus RTU and a Modbus TCP device. Modbus
RTU polls the data from the Modbus slave and sends it to Modbus Master using Modbus TCP.
To use this feature, configure the serial interface and TCP interface.
To configure the serial interface:
1. Go to Serial and select Serial 1.
2. Configure the serial port settings.
3. Select Mode as Tunnel/Modbus RTU to Modbus TCP.
4. Click Save & Apply.
To configure the TCP interface:
1. Go to Tunnel and select Tunnel 1.
2. Under Modbus RTU to Modbus TCP, select Enable and then enter the configuration settings.
See Table 17-1
3. Click Save & Apply.
Table 17-1 Tunnel for Modbus RTU to Modbus TCP
Field

Description

EnableSelect to enable and configure the Modbus RTU to Modbus TCP
settings.

ProtocolTCP option is selected.

Mode Server - the gateway acts as a server and listens for the TCP

connection from the external Modbus master. TCP Port number isrequired.
 Client - the gateway acts as a TCP client and sends the TCP
connection request to the external Modbus master. The IP address
and TCP port of the Modbus master is required.

X300 Series IoT Cellular Gateway User Guide201

17: Tunnel

Field

Description

IP

IP address of the external Modbus master on the LAN or WAN
interface.

Port

Modbus TCP port number that the server is listening on.
The default Modbus TCP port number is 502.

Backup Server EnableIf client mode is selected, select the box to configure a backup Modbus
master.
Enter the backup server’s IP address and port number.

Socket Timeout Enable

Select to configure socket timeout.
Enter the inactivity timeout period in seconds.

Tunnel Accept
In Accept mode, the gateway listens (waits) for incoming connections from the network.
A remote node on the network initiates the connection. The configurable local port is the port thatthe remote device connects to for this connection. There is no remote port or address. Serial data
can still be received while waiting for a network connection, keeping in mind serial data buffer
limitations.
To configure Accept mode:
1. Go to Tunnel > Tunnel 1, Tunnel SPP Slave, or Tunnel SPP Master.
2. Under Accept, enter the Accept mode configuration settings.
3. Click Save & Apply.

Table 17-2 Tunnel Accept Mode Configuration
Field

DescriptionMode

Set the method used to start a tunnel in Accept mode.
 Disable – do not accept an incoming connection.
 Always – accept an incoming connection (default).
 Any Character – start waiting for an incoming connection when any

character is read on the serial line.
 Start Character – start waiting for an incoming connection when the start

character for the selected tunnel is read on the serial line. Use the default
Start Character <control>B, or enter a custom start character. The Flush
Start Character setting flushes the start character when a new connection is
made.
Local Port

Set the port number for use as the network local port. The default local port
number correlates with the tunnel instance.
 Tunnel 1: 10001
 Tunnel SPP Slave: 10002
 Tunnel SPP Master: 10003

X300 Series IoT Cellular Gateway User Guide202

17: Tunnel

Field

Description

ProtocolSelect the desired security protocol:
 SSL
 TCP (default protocol)
 TCP AES Telnet

Configure the protocol fields as determined by the protocol selection.
Secure Protocols

When using SSL, select the secure protocols and the SSL credential. Thisconfiguration field becomes available when
Protocol options are:
 SSL3
 TLS1.0
 TLS1.1 (default selected)
 TLS1.2 (default selected)
 TLS1.3 (default selected)

TCP Keep Alive

The TCP keep alive time is the time in which probes are periodically sent to theother end of the connection to ensure the other side is still connected.
Enter the TCP Keep Alive time in milliseconds. Set to 0 to disable TCP Keep
Alive, and blank the field to restore the default.

TCP Keep Alive Interval Enter the time, in milliseconds, to wait between Keep Alive probes in order tokeep the TCP connection up during idle transfer periods. Blank the display field
to restore the default.
TCP Keep Alive Probes

Enter the number of TCP Keep Alive probes to send before closing theconnection if no response is received. The probes are sent after the initial TCP
Keep Alive probe is sent. Valid values are between 1 and 16. Blank the field torestore the default.

AES Encrypt Key

Enter the AES Encrypt Key.
This configuration field becomes available when the TCP AES protocol isselected.

AES Encrypt Key Type

Select Text or Hexadecimal to indicate format.
This configuration field becomes available when the TCP AES protocol isselected.

AES Decrypt Key

Enter the AES Decrypt Key.
This configuration field becomes available when the TCP AES protocol isselected.

AES Decrypt Key Type

Select Text or Hexadecimal to indicate format.
This configuration field becomes available when the TCP AES protocol isselected.

X300 Series IoT Cellular Gateway User Guide203

17: Tunnel

Field

Description

Initial Send

Enter the Initial Send data to be sent out the network upon connection
establishment before any data from the Line. It may contain one or more
Directives of the form %<char>.
The Initial Send string can be entered in Text or Binary form.
The Binary form allows square braces [] to enclose one or more character
designations separated by commas. Use straight decimal numbers up to 255 or
hexadecimal numbers prefixed with 0x up to 0xFF within the square braces.
To specify an open brace in binary mode, use two in a row.
Example The selection (in binary mode): AB[255,0xFF]C[[D]results in astring containing binary values where the dots appear: AB...C[D]Directives
 %i local IP address
 %m MAC address
 %n network interface name %p local port
 %s serial number
 %% %

Initial Send TypeThe format of the initial send data.
 Text Binary

Flush Serial

Set whether the serial line data buffer is flushed upon a new network
connection. Choices are:
 Enabled – serial data buffer is flushed on network connection
 Disabled – serial data buffer is not flushed on network connection (default)

Block Serial

Set whether Block Serial is enabled for debugging purposes. Choices are:
 Enabled – if Enabled, incoming characters from the serial line will not be

forwarded to the network. Instead, they will be buffered and will eventually
flow off the serial line if hardware or software flow control is configured.
 Disabled – this is the default setting; incoming characters from the serial line
are sent on into the network. Any buffered characters are sent first.
Block Network

Set whether Block Network is enabled for debugging purposes. Choices are:
 Enabled – if Enabled, incoming characters from the network will not be

forwarded to the serial line. Instead, they will be buffered and will eventually
flow off the network side.
 Disabled – this is the default setting; incoming characters from the network
are sent on into the serial line. Any buffered characters are sent first.
Password

The password can be up to 31 characters in length. Valid characters arealphanumeric characters and punctuation. When set, clients must send thecorrect password string to the device within 30 seconds from opening network
connection in order to enable data transmission.
The password sent to the device must be terminated with one of the following: 0A (Line Feed) 00 (Null) 0D 0A (Carriage Return/Line Feed) 0D 00 (Carriage Return/Null)

If, Prompt for Password is set to Enabled and a password is provided, theuser will be prompted for the password upon connection.

X300 Series IoT Cellular Gateway User Guide204

17: Tunnel

Tunnel Connect
In Connect Mode, the gateway continues to attempt an outgoing connection on the network until
established. If the connection attempt fails or the connection drops, then it retries after a timeout.
The remote node on the network must listen for the Connect Mode’s connection.
For Connect Mode to function, it must be enabled, have a remote station (node) configured, and aremote port configured (TCP or UDP). When established, Connect Mode is always on. Enter the
remote station as an IPv4 or IPv6 address or DNS name. The gateway will not make a connection
unless it can resolve the address. For Connect Mode using UDP, the gateway accepts packets
from any device on the network. It will send packets to the last device that sent it packets.
Note: The port in Connect Mode is not the same port configured in Accept Mode. The
TCP keep alive time is the time in which probes are periodically sent to the other end of
the connection. This ensures the other side is still connected.
To configure Tunnel Connect mode:
1. Go to Tunnel > Tunnel 1.
2. Under Connect, enter the connect mode configuration settings. See Table 17-3.
3. Under Connect Host, configure 1 to 4 Hosts. See Table 17-4 Host Configuration.
4. Click Save & Apply.
Table 17-3 Tunnel Connect Mode Configuration
Field

Description

Connect Mode

Set the method to be used to attempt a connection to a remote host or device.
Choices are:
 Disable – an outgoing connection is never attempted. (default)
 Always – a connection is attempted until one is made. If the connection gets

disconnected, the gateway retries until it makes a connection.
 Any Character – a connection is attempted when any character is read on

the serial line.
 Start Character – a connection is attempted when the start character for theselected tunnel is read on the serial line.
Host ModeIf more than one host is configured, set the method to be used to access
multiple hosts.
Sequential – A tunnel will connect to hosts in sequential order. Host 1 will be
attempted first. If that fails, it will proceed in order to Host 2, 3, and then 4.
When a connection drops, the cycle starts again with Host 1 and proceeds inorder. (default setting)
Simultaneous – A tunnel will connect to all hosts accepting a connection.
Simultaneous connections occur at the same time to all listed hosts. The
gateway supports a maximum of 4 host connections.

Local PortEnter an alternative local port. The local port is set to <Random> by default
but can be overridden. Blank the field to restore the default.

Reconnect Timer

Set the value of the reconnect timeout (in milliseconds) for outgoingconnections established by the gateway. Valid range is 1 to 65535 milliseconds.
Default is 15000.

X300 Series IoT Cellular Gateway User Guide205

17: Tunnel

Field (continued)

Description

Flush Serial

Set whether the serial line data buffer is flushed upon a new network
connection. Choices are:
 Enabled – serial data buffer is flushed on network connection
 Disabled – serial data buffer is not flushed on network connection (default)

Block Serial

Set whether Block Serial is enabled for debugging purposes. Choices are:Enabled – If Enabled, incoming characters from the serial line will not be
forwarded to the network. Instead, they will be buffered and will eventually
flow off the serial line if hardware or software flow control is configured.
 Disabled – this is the default setting; incoming characters from the serial line
are sent on into the network. Any buffered characters are sent first.


Block Network

Set whether Block Network is enabled for debugging purposes. Choices are:
 Enabled – If Enabled, incoming characters from the network will not be

forwarded to the serial line. Instead, they will be buffered and will eventually
flow off the network side.
 Disabled – this is the default setting; incoming characters from the network
are sent on into the serial line. Any buffered characters are sent first.

Hosts
The Connect mode supports up to 4 hosts. Hosts may be accessed sequentially or
simultaneously.
Notes:
Configure the keep alive timeout to be larger than the user timeout.


If the keep alive time expires, the user timeout is expired, and there are probes inflight, the connection will be reset. For this reason, it is recommended that if keep alive
is used in conjunction with the user timeout, the keep alive timeouts be larger than theuser timeout.



If it is smaller, what will typically be seen is that the initial probe will be sent, then at theinterval where the next probe would normally be sent, the connection will be reset,with no additional probes sent. Also note that in these cases: if the keep alive timer issignificantly smaller than the user timeout, probes will continue to be sent for an
unreachable host until the user timeout expires.

The user timeout will not be an exact limit; in practice, it will always take somewhat longer
for the connection to be closed.


If there is data in flight when the TCP retransmission timeout kicks in, the user timeout
is checked as a limiting condition only when the timer expirations would normally bechecked during RTO handling. The longer the user timeout is, the more likely it will
expire between exponentially slower retransmissions, and the connection will not
experience an error until the next retransmission timeout is checked.

The user timeout expiration during retransmission returns an error to the application; it
does not automatically reset the connection as happens with the keep alive timeout. It
is up to the application (e.g., tunneling) to close the connection (this happens almost
immediately with tunneling).
Table 17-4 Host Configuration

Host Field

Description

Address

Enter the destination IP address for the connection.

X300 Series IoT Cellular Gateway User Guide206

17: Tunnel

Host Field

Description

Port

Enter the TCP or UDP port number on the target host for the connection.

ProtocolSelect the desired security protocol.
 SSL
 TCP
 TCP AES Telnet
 UDP
 UDP AES

Configure the remaining protocol fields as determined by the protocol selection.
Secure Protocols

When using SSL, select the secure protocols and the SSL credential.
Protocol options are:
 SSL3
 TLS1.0
 TLS1.1 (default selected)
 TLS1.2 (default selected)
 TLS1.3 (default selected)

TCP Keep Alive

Enter the time, in milliseconds, the gateway waits during a silent TCP
connection before the first Keep Alive probe is sent to the remote host in orderto keep the TCP connection up during idle transfer periods. Set to 0 to disable
TCP Keep Alive, and blank the field to restore the default.

TCP Keep Alive IntervalEnter the time, in milliseconds, to wait between Keep Alive probes in order tokeep the TCP connection up during idle transfer periods. Blank the display field
to restore the default.

TCP Keep Alive Probes

Enter the number of TCP Keep Alive probes to send before closing theconnection if no response is received. The probes are sent after the initial TCP
Keep Alive probe is sent. Valid values are between 1 and 16. Blank the field torestore the default.

TCP User Timeout

Specify the amount of time the TCP segments will be retransmitted before theconnection is closed.

AES Encrypt Key

Enter the AES Encrypt Key. This configuration field becomes available when
the TCP AES or UDP AES protocol is selected.

AES Encrypt Key Type

Select Text or Hexadecimal to indicate format

AES Decrypt Key

Enter the AES Decrypt Key. This configuration field becomes available when
the TCP AES or UDP AES protocol is selected.

AES Decrypt Key Type

Select Text or Hexadecimal to indicate format

Initial Send

Enter the Initial Send character to be sent out the network upon connection
establishment before any data from the Line. It may contain one or more
Directives of the form %<char>. This configuration field becomes available
when the TCP, UDP, or UDP AES protocol is selected.

Initial Send Type

Select Text or Hexadecimal to indicate format.

Credentials

If SSL is the selected protocol, select an existing credential from the drop-downlist. Go to SSL > Credentials to create, view, or edit SSL credentials.
See Credentials on page 198.

Validate Certificate

Select to enable validation of the SSL certificate on the server. Thisconfiguration field becomes available when the SSL protocol is selected.

Connecting Multiple Hosts

X300 Series IoT Cellular Gateway User Guide207

17: Tunnel
The Connect Mode supports up to 4 hosts. Hosts may be accessed sequentially or
simultaneously.


Sequential – A tunnel will connect to hosts in sequential order. The host specified as Host 1
will be attempted first. If that fails, it will proceed to Host 2, 3, and 4. When a connection drops,
the cycle starts again with Host 1 and proceeds in order. Sequential is the default Host Mode.



Simultaneous – A tunnel will connect to all hosts accepting a connection. Simultaneousconnections occur at the same time to all listed hosts. The gateway can support a maximum of
4 connections.

Tunnel Disconnect
Disconnect specifies the optional conditions for disconnecting any tunnel connection that may beestablished. If any of these conditions are selected but do not occur and the network disconnects
from the gateway, a Connect mode connection will attempt to reconnect. However, if none of these
conditions are selected, a closure from the network is taken as a disconnected host.
To configure Disconnect settings:
1. Go to Tunnel > Tunnel 1, Tunnel SPP Slave, or Tunnel SPP Master.
2. Under Disconnect, enter the configuration settings.
3. Click Save & Apply.

Table 17-5 Tunnel Disconnect Configuration
Field

Description

Stop Character

Enter the Stop Character which, when received on the serial line, disconnects thetunnel. The Stop Character may be designated as a single printable character or as acontrol character. Control characters may be input in any of the following forms:<control>J or 0xA (hexadercimal) or \10 (decimal). To disable the Stop
Character, blank the field, which sets it to <None>.

Flush Stop
CharacterSet whether to flush the stop character when the tunnel is disconnected. Options: Enabled Disabled (default)

Timeout

Enter the number of milliseconds a tunnel may be idle before disconnection. To
disable the timeout, set the field to zero (0).

Flush Serial Data

Set whether to flush the Serial Line when the Tunnel is disconnected. Choices are:
 Enabled Disabled (default)

X300 Series IoT Cellular Gateway User Guide208

A: Compliance Information(According to ISO/IEC Guide and EN 45014)
Manufacturer’s Name & Address:
Lantronix, Inc. 48 Discovery, Suite 250, Irvine, CA 92618 USA
Product Family:
X300 Series
Conforms to the following standards or other normative documents:
Table A-1 Regional Certifications
Country /Specification

USA

FCC 47 CFR part 15 Subpart B
FCC 47 CFR part 15 Subpart 22H, 24E, 27 & 90
FCC 47 CFR Part 15 Subpart E

CanadaISED
RSS-130 Issue 2
RSS-132 Issue 3
RSS-133 Issue 6
RSS 139 Issue 3

EU

EU Declaration of Conformity

Australia, New Zealand

AS/NZS CISPR 32:2015

SafetyUL/EN 62368-1

See Figure A-1.

CAN/CSA C22.2 62368-1-14
Cellular Certification

PTCRB, AT&T

Table A-2 Country Transmitter IDs
Country

Specification

USA FCC ID

Cellular Module: X303F202S: R68X303
 X304G00AS: R68X304

Wi-Fi Module: TLZ-CM2XXNF
Canada IC ID

Cellular Module: X303F202S: 3867A-X303
 X304G00AS: 3867A-X304

Wi-Fi Module: 6100A-CM2XXNF

X300 Series IoT Cellular Gateway User Guide

209

FCC Statement
Federal Communication Commission Interference Statement
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions: (1) This device may not cause harmful interference, and (2) this device must accept
any interference received, including interference that may cause undesired operation.
This equipment has been tested and found to comply with the limits for a Class A digital device,pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. This equipment generates, uses, and canradiate radio frequency energy and, if not installed and used in accordance with the instructions,
may cause harmful interference to radio communications. However, there is no guarantee thatinterference will not occur in a particular installation. If this equipment does cause harmfulinterference to radio or television reception, which can be determined by turning the equipment off
and on, the user is encouraged to try to correct the interference by one of the following measures:Reorient or relocate the receiving antenna.

Increase the separation between the equipment and receiver.

Connect the equipment into an outlet on a circuit different from that to which the receiver isconnected.

Consult the dealer or an experienced radio/TV technician for help.

FCC Caution: Any changes or modifications not expressly approved by the party responsible forcompliance could void the user's authority to operate this equipment.
This transmitter must not be co-located or operating in conjunction with any other antenna ortransmitter.
Operations are restricted to indoor usage only.
Radiation Exposure Statement
This equipment complies with FCC radiation exposure limits set forth for an uncontrolledenvironment. This equipment should be installed and operated with minimum distance 20cm
between the radiator & your body.
Antenna Installation
1) The antenna must be installed such that 20 cm is maintained between the antenna and users,and2) The transmitter module may not be co-located with any other transmitter or antenna.

X300 Series IoT Cellular Gateway User Guide

210

ISED Statement
This device complies with RSS-247 of the Industry Canada Rules. Operation is subject to thefollowing two conditions: (1) This device may not cause harmful interference, and (2) this device
must accept any interference received, including interference that may cause undesired operation.
Ce dispositif est conforme à la norme CNR-247 d'Industrie Canada applicable aux appareils radio
exempts de licence. Son fonctionnement est sujet aux deux conditions suivantes: (1) le dispositif
ne doit pas produire de brouillage préjudiciable, et (2) ce dispositif doit accepter tout brouillage
reçu, y compris un brouillage susceptible de provoquer un fonctionnement indésirable.
Radiation Exposure Statement:This equipment complies with IC radiation exposure limits set forth for an uncontrolledenvironment. This equipment should be installed and operated with minimum distance 20cm
between the radiator & your body.
Déclaration d'exposition aux radiations:Cet équipement est conforme aux limites d'exposition aux rayonnements IC établies pour unenvironnement non contrôlé. Cet équipement doit être installé et utilisé avec un minimum de 20
cm de distance entre la source de rayonnement et votre corps.
This device is intended only for use under the following conditions:1) The antenna must be installed such that 20 cm is maintained between the antenna and users,and2) The transmitter module may not be co-located with any other transmitter or antenna.
Cet appareil est conçu uniquement pour les intégrateurs OEM dans les conditions
suivantes: (Pour utilisation de dispositive module)
1) L'antenne doit être installée de telle sorte qu'une distance de 20 cm est respectée entre
l'antenne et les utilisateurs, et2) Le module émetteur peut ne pas être coïmplanté avec un autre émetteur ou antenne.

X300 Series IoT Cellular Gateway User Guide211

EU Declaration of Conformity
Figure A-1 X300 / X303 EU Declaration of Conformity

EU DECLARATION OF CONFORMITY
EU-type examination certificate no.
Manufacturer’s Name:
Manufacturer’s Address:

LANTRONIX, INC.
7535 Irvine Center Drive, Suite 100, Irvine, CA. 92618. USA

Product Type:
Product Family:
Model name:Rated:
Intended use:
Modules:
Notified Body:
Notified Body number:

Gateway
X300 Series
X303F202S, X300F202S
9-30 VDC
Commercial installations, indoor use
B+C
Telefication B.V.
0560

Manufacturer’s Quality System:

ISO 9001:2015 Certificate No. 74 300 4282

TUV Rheinland

Applicable EU Directives:
Low Voltage Directive (2014/35/EU)yEN 62368-1:2014/A11:2017
EMC Directive (2014/30/EU)y
EN 301 489-1 V2.2.3 (2019-11)y
EN 301 489-17 V3.. (201-)yDraft EN 301 489-52 V1.1.2 (2020-12)y
EN 61000-3-2:2019yEN 61000-3-3:2013+A1:2019y
EN 55032:2015/A11:2020
RF Radio Directive (2014 / 53 / EU)y
EN 301 908-1 V13.1.1 (2019-11)y
EN 301 908-13 V13.1.1 (2019-11)y
EN 301 511 V12.5.1 (2017-03)
y
EN 300 328 V2.2.2 (2019-07)
y
EN 301 893 V2.1.1 (2017-05)
Healthy Directive (2014 / 53 / EU)yEN 62311:2020
RoHS1) 2011/65/EU Restriction of the use of Hazardous Substances in EEE (RoHS)
2) 2015/863/EU Change of Annex II from 2011/65/EU
3) Directive 2018/736/EU and 2018/741/EU
y
EN 63000-2018
Statement of Conformity: The product specified above complies with applicable EU directive referenced, including theapplication of sound engineering practice.
Signature: ______________________________________
_
_____
__
__
_
___
_

May 6, 2022
Date: _____________

Name: ____________ Fathi Hakam _________

Title: VP of Engineering

CERT-00XXX rev A

X300 Series IoT Cellular Gateway User Guide

212

Figure A-2 X304 EU Declaration of Conformity

EU DECLARATION OF CONFORMITY
Certificate no.222140460/AA/00
Manufacturer’s Name: LANTRONIX INC.
Manufacturer’s Address: 48 Discovery, Suite 250, Irvine, CA 92618 USA
Product Type: X300 Series IOT Cellular Gateway
Product Family: X304G002S, X304xxxxx (x can be any character or blank)
Rated:
9-30VDC
Intended use:
Commercial installations, indoor use Rated:
Intended use:
Commercial/Industrial installations, indoor use
Manufacturer’s Quality System:

10-48Vdc, 18.5W

ISO 9001:2015 Certificate No. 74 300 4282 TUV Rheinland
Category of Equipment: Class 3 (powered by SELV LPS or Class 2 Power Supply)
Applicable EU Directives:
Low Voltage Directive (2014/35/EU)• EN 62368-1:2020+A11:2020
EMC Directive (2014/53/EU)• EN 301 489-1 V2.2.3• EN 301 489-17 V3.2.4• EN 301 489-19 V2.2.0• EN 301 489-52 V1.2.1• EN 55032:2015+A11:2020 class A• EN 55035:2017+A11:2020• EN 61000-3-2:2014• EN 61000-3-3:2013• EN 61000-4-2:2009• EN 61000-4-3:2006+A1:2008+A2:2010• EN 61000-4-4:2012• EN 61000-4-5:2014+A1:2017• EN 61000-4-6:2014+AC:2015• EN 61000-4-11:2004+A1:2017
RF Radio Directive (2014 / 53 / EU)• EN 303 413 V1.2.1• EN 300 328 V2.2.2• EN 301 893 V2.1.1• EN 301 908-1 V15.1.1• EN 301 908-2 V11.1.1• EN 301 908-13 V11.1.1• EN 62311:2020

EU Directive 2011/65/EU for Restriction of Hazardous Substance (RoHS2) with
exemption 7(c)-I
1) 2011/65/EU Restriction of the use of Hazardous Substances in EEE (RoHS)
2) 2015/863/EU Change of Annex II from 2011/65/EU
3) Directive 2018/736/EU and 2018/741/EU
EN 6300-2018
Statement of Conformity: The product specified above complies with applicable EU directive referenced,
including the application of sound engineering practice.

_______
___
__
__
___
___
_____
Signature: ______________________________
F thi Hk
Name: _____________Fathi
Hakam

August 30, 2022
Date: ______________________ Title: VP of Engineering

CERT-DoC X304 rev A

X300 Series IoT Cellular Gateway User Guide

213

Figure A-3 X304 UKCA Declaration of Conformity

UKCA DECLARATION OF CONFORMITY

Intended use:

Manufacturer’s Name: LANTRONIX INC.
Manufacturer’s Address: 48 Discovery, Suite 250, Irvine, CA 92618 USA
Product Type: X300 Series IOT Cellular Gateway
Product Family: X304G002S, X304xxxxx (x can be any character or blank)
Rated:
9-30VDC
Intended use:
Commercial installations, indoor use:
Commercial/Industrial installations, indoor use
Manufacturer’s Quality System:

ISO 9001:2015 Certificate No. 74 300 4282
Category of Equipment: Class 3 (powered by SELV LPS or Class 2 Power Supply)
Safety• BS EN 62368-1:2020+A11:2020• EN 62368-1:2020+A11:2020
EMC• EN 301 489-1 V2.2.3• EN 301 489-17 V3.2.4• EN 301 489-19 V2.2.0• EN 301 489-52 V1.2.1• BS EN 55032:2015+A11:2020 class A• EN 55032:2015+A11:2020 class A• BS EN 55035:2017+A11:2020• EN 55035:2017+A11:2020• EN 61000-3-2:2014• EN 61000-3-3:2013

10-48Vdc, 18.5W

TUV Rheinland• EN 61000-4-2:2009• EN 61000-3:2006+A1:2008+A2:2010• EN 61000-4-4:2012• EN 61000-4-5:2014+A1:2017• EN 61000-4-6:2014+AC:2015• EN 61000-4-11:2004+A1:2017
RF• EN 303 413 V1.2.1• EN 300 328 V2.2.2• EN 301 893 V2.1.1• EN 301 908-1 V15.1.1• EN 301 908-2 V11.1.1• EN 301 908-13 V11.1.1• EN 62311:2020

UK SI 2012 No. 3032 for Restriction of Hazardous Substance (RoHS2) with exemption 7(c)-I and 6(c).
1) 2011/65/EU Restriction of the use of Hazardous Substances in EEE (RoHS)
2) 2015/863/EU Change of Annex II from 2011/65/EU
3) Directive 2018/736/EU[7(c)-I] and 2018/741/EU[6(c)]BS EN IEC 63000濣2018
Statement of Conformity: The product specified above meets the test requirements of the relevant legislation ofUnited Kingdom, including the application of sound engineering practice.

Signature: _______________________________________
__
__
___
_____
Name: _____________Fathi Hakam

August 29, 2022
Date: ______________________ Title: VP of Engineering

CERT-SLC 8000 ETH rev F

X300 Series IoT Cellular Gateway User Guide214

EU Statements
Table A-3 EU Statements
Code

Language

Statement

bg

Bulgarian

Lantronix, Inc., декларира, че този X300 Series отговаря наосновните изисквания и други приложими разпоредби наДиректива 2014/53 / ЕС.
Пълният текст на декларацията на ЕС за съответствие е достъпенна следния интернет адрес: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
Известие на ЕС за ограничения при употреба: Това устройство еограничено само за вътрешна употреба. Може да не се работи наоткрито.

csČesky [Czech]

Lantronix, Inc. tímto prohlašuje, že tento X300 Series je ve shodě sezákladními požadavky a dalšími příslušnými ustanoveními směrnice2014/53/EU.
Úplné znění ES prohlášení o shodě je k dispozici na této internetovéadrese: https://www.lantronix.com/products/lantronix-emg/#tab-docsdownloads
Oznámení EU o omezení používání: Toto zařízení je omezeno pouzena použití uvnitř. Nesmí být provozován venku.

daDansk [Danish]

Undertegnede Lantronix, Inc. erklærer herved, at følgende udstyr X300
Series overholder de væsentlige krav og øvrige relevante krav i direktiv
2014/53/EU.
Den fulde tekst til EU-overensstemmelseserklæringen er tilgængelig på
følgende internetadresse: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
EU-meddelelse om begrænsninger i brug: Denne enhed er kunbegrænset til indendørs brug. Det betjenes måske ikke udendørs.

deDeutsch [German]

Hiermit erklärt Lantronix, Inc., dass sich das Gerät X300 Series inÜbereinstimmung mit den grundlegenden Anforderungen und denübrigen einschlägigen Bestimmungen der Richtlinie 2014/53/EU
befindet.
Der vollständige Text der EU-Konformitätserklärung ist unter folgenderInternetadresse abrufbar: https://www.lantronix.com/products/lantronixemg/#tab-docs-downloads
EU-Hinweis zu Nutzungsbeschränkungen: Dieses Gerät darf nur inInnenräumen verwendet werden. Es darf nicht im Freien betrieben
werden.

X300 Series IoT Cellular Gateway User Guide

215

Code

Language

Statement

etEesti [Estonian]Käesolevaga kinnitab Lantronix, Inc. seadme X300 Series vastavust
direktiivi 2014/53/EU põhinõuetele ja nimetatud direktiivist tulenevatele
teistele asjakohastele sätetele.
EL-i vastavusdeklaratsiooni täielik tekst on saadaval järgmisel Internetiaadressil: https://www.lantronix.com/products/lantronix-emg/#tab-docsdownloads
EL-i teade kasutuspiirangute kohta: seda seadet saab kasutada ainult
siseruumides. Seda ei tohi õues kasutada.

en

EnglishHereby, Lantronix, Inc., declares that this X300 Series is in compliancewith the essential requirements and other relevant provisions of
Directive 2014/53/EU.
The full text of the EU declaration of conformity is available at thefollowing internet address: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
EU Notice of Restrictions on Use: This device is limited to indoor use
only. It may not be operated outdoors.

esEspañol [Spanish]

Por medio de la presente Lantronix, Inc. declara que el X300 Series
module cumple con los requisitos esenciales y cualesquiera otras
disposiciones aplicables o exigibles de la Directiva 2014/53/EU.
El texto completo de la declaración de conformidad de la UE está
disponible en la siguiente dirección de Internet: https://www.lantronix.com/products/lantronix-emg/#tab-docs-downloads
Aviso de restricciones de uso de la UE: este dispositivo está limitado
solo para uso en interiores. No puede ser operado al aire libre.

elΕλληνική [Greek]ΜΕ ΤΗΝ ΠΑΡΟΥΣΑ Lantronix, Inc. ΔΗΛΩΝΕΙ ΟΤΙ X300 SeriesΣΥΜΜΟΡΦΩΝΕΤΑΙ ΠΡΟΣ ΤΙΣ ΟΥΣΙΩΔΕΙΣ ΑΠΑΙΤΗΣΕΙΣ ΚΑΙ ΤΙΣΛΟΙΠΕΣ ΣΧΕΤΙΚΕΣ ΔΙΑΤΑΞΕΙΣ ΤΗΣ ΟΔΗΓΙΑΣ 2014/53/EU.
Το πλήρες κείμενο της δήλωσης συμμόρφωσης της ΕΕ διατίθεται στηνακόλουθη διεύθυνση διαδικτύου: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
Ειδοποίηση της ΕΕ για περιορισμούς χρήσης: Η συσκευή αυτήπεριορίζεται μόνο σε εσωτερικούς χώρους χρήσης. Μπορεί να μηνλειτουργεί σε εξωτερικούς χώρους.

X300 Series IoT Cellular Gateway User Guide

216

Code

Language

Statement

fr

Français [French]

Par la présente Lantronix, Inc. déclare que l'appareil X300 Series est
conforme aux exigences essentielles et aux autres dispositions
pertinentes de la directive 2014/53/EU.
Le texte complet de la déclaration de conformité UE est disponible àl'adresse Internet suivante : https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
Avis de restrictions d'utilisation de l'UE: Cet appareil est limité à une
utilisation en intérieur uniquement. Il ne doit pas être utilisé à
l'extérieur.

isIcelandic

Hér með lýsir Lantronix, Inc. því yfir að X300 Series sé í samræmi við
grunnkröfur og önnur viðeigandi ákvæði tilskipunar 2014/53 / ESB.
Í heildartexta ESB-samræmisyfirlýsingarinnar er að finna á eftirfarandiinternetfangi: https://www.lantronix.com/products/lantronix-emg/#tabdocs-downloads
Tilkynning ESB um takmarkanir á notkun: Þetta tæki er eingöngu
takmarkað við notkun innanhúss. Það má ekki nota það úti.

it

Italiano [Italian]

Con la presente Lantronix, Inc. dichiara che questo X300 Series è
conforme ai requisiti essenziali ed alle altre disposizioni pertinenti
stabilite dalla direttiva 2014/53/EU.
Il testo completo della dichiarazione di conformità UE è disponibile alseguente indirizzo Internet: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
Avviso di restrizioni d'uso dell'UE: questo dispositivo è limitato
esclusivamente all'uso in interni. Potrebbe non essere utilizzato
all'aperto.

lv

Latviski [Latvian]Ar šo Lantronix, Inc. deklarē, ka X300 Series atbilst Direktīvas 2014/53/
EU būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
Pilns ES atbilstības deklarācijas teksts ir pieejams šādā tīmekļa vietnē:
https://www.lantronix.com/products/lantronix-emg/#tab-docsdownloads
ES paziņojums par lietošanas ierobežojumiem: šo ierīci var izmantot
tikai iekštelpās. To nedrīkst darbināt ārpus telpām.

ltLietuvių [Lithuanian]Šiuo Lantronix, Inc. deklaruoja, kad šis X300 Series atitinka esminius
reikalavimus ir kitas 2014/53/EU Direktyvos nuostatas.
Visą ES atitikties deklaracijos tekstą galite rasti šiuo interneto adresu:
https://www.lantronix.com/products/lantronix-emg/#tab-docsdownloads
ES pranešimas apie naudojimo apribojimus: Šis prietaisas skirtas
naudoti tik patalpose. Jo negalima naudoti lauke.

X300 Series IoT Cellular Gateway User Guide

217

Code

Language

Statementnl

Nederlands [Dutch]

Hierbij verklaart Lantronix, Inc. dat het toestel X300 Series
overeenstemming is met de essentiële eisen en de andere relevante
bepalingen van richtlijn 2014/53/EU.
De volledige tekst van de EU-conformiteitsverklaring is beschikbaar op
het volgende internetadres: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
EU kennisgeving van gebruiksbeperkingen: dit apparaat is beperkt tot
gebruik binnenshuis. Het mag niet buitenshuis worden gebruikt.

mtMalti [Maltese]

Hawnhekk, Lantronix, Inc., jiddikjara li dan X300 Series jikkonformamalħtiġijiet essenzjali u ma provvedimenti oħrajn relevanti li hemm fidDirrettiva 2014/53/EU.
It-test sħiħ tad-dikjarazzjoni ta ’konformità tal-UE huwa disponibbli flindirizz tal-internet li ġej: https://www.lantronix.com/products/lantronixemg/#tab-docs-downloads
Avviż tal-UE dwar Restrizzjonijiet fuq l-Użu: Dan l-apparat huwa limitatgħal użu ġewwa biss. Ma jistax jitħaddem barra.

huMagyar [Hungarian]Alulírott, Lantronix, Inc. nyilatkozom, hogy a X300 Series megfelel avonatkozó alapvetõ követelményeknek és az 2014/53/EU irányelv
egyéb elõírásainak.
Az EU-megfelelőségi nyilatkozat teljes szövege a következő internetes
címen érhető el: https://www.lantronix.com/products/lantronix-emg/#tab-docs-downloads
EU értesítés a korlátozásokról: Ez az eszköz csak beltéri használatra
korlátozódik. Lehet, hogy szabadban nem üzemeltethető.

noNorwegian

Lantronix, Inc. erklærer herved at denne X300 Series er i samsvar med
de grunnleggende kravene og andre relevante bestemmelser i direktiv
2014/53 / EU.
Den fullstendige teksten til EU-samsvarserklæringen er tilgjengelig på
følgende internettadresse: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
EUs merknad om bruksbegrensninger: Denne enheten er barebegrenset til innendørs bruk. Det kan hende at den ikke brukes
utendørs.

X300 Series IoT Cellular Gateway User Guide

218

Code

Language

StatementplPolski [Polish]

Niniejszym Lantronix, Inc. oświadcza, że X300 Series jest zgodny zzasadniczymi wymogami oraz pozostałymi stosownymi
postanowieniami Dyrektywy 2014/53/EU.
Pełny tekst deklaracji zgodności UE jest dostępny pod następującym
adresem internetowym: https://www.lantronix.com/products/lantronixemg/#tab-docs-downloads
Zawiadomienie UE o ograniczeniach użytkowania: To urządzenie jest
przeznaczone wyłącznie do użytku w pomieszczeniach. Nie można go
obsługiwać na zewnątrz.

pt

Português [Portuguese]

Lantronix, Inc. declara que este X300 Series está conforme com osrequisitos essenciais e outras disposições da Directiva 2014/53/EU.
O texto completo da declaração UE de conformidade está disponível
no seguinte endereço na Internet: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
Aviso da UE de restrições de uso: Este dispositivo está limitado
apenas ao uso interno. Não pode ser operado ao ar livre.

ro

Romanian

Prin prezenta, Lantronix, Inc., declară că acest X300 Series respectă
cerințele esențiale și alte dispoziții relevante din Directiva 2014/53 / UE.
Textul complet al declarației de conformitate a UE este disponibil laurmătoarea adresă de internet: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
Notificarea UE privind restricțiile de utilizare: Acest dispozitiv este
limitat numai la uz interior. Este posibil să nu funcționeze în aer liber.

sr

SerbianОвиме, Лантроник, Инц., изјављује да је овај X300 Series у складуса суштинским захтевима и осталим релевантним одредбама
Директиве 2014/53 / ЕУ.
Комплетан текст ЕУ изјаве о усаглашености доступан је наследећој Интернет адреси: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
Обавештење ЕУ о ограничењима употребе: Овај уређај јеограничен само на унутрашњу употребу. Можда се не користи наотвореном.

sl

Slovensko [Slovenian]

Lantronix, Inc. izjavlja, da je ta X300 Series v skladu z bistvenimi
zahtevami in ostalimi relevantnimi določili direktive 2014/53/EU.
Celotno besedilo izjave EU o skladnosti je na voljo na naslednjem
spletnem naslovu: https://www.lantronix.com/products/lantronix-emg/#tab-docs-downloads
Obvestilo EU o omejitvah uporabe: Ta naprava je omejena samo na
notranjo uporabo. Morda ga ne uporabljate na prostem.

X300 Series IoT Cellular Gateway User Guide

219

Code

Language

Statementsk

Slovensky [Slovak]

Lantronix, Inc. týmto vyhlasuje, že X300 Series enterprise Wi-Fi IoT
module spĺňa základné požiadavky a všetky príslušné ustanovenia
Smernice 2014/53/EU.
Úplné znenie EÚ vyhlásenia o zhode je k dispozícii na tejto internetovej
adrese: https://www.lantronix.com/products/lantronix-emg/#tab-docsdownloads
Oznámenie EÚ o obmedzeniach pri používaní: Toto zariadenie jeobmedzené iba na použitie v interiéri. Nesmie sa používať vonku.

fiSuomi [Finnish]

Lantronix, Inc. vakuuttaa täten että X300 Series tyyppinen laite on
direktiivin 2014/53/EU oleellisten vaatimusten ja sitä koskevien
direktiivin muiden ehtojen mukainen.
EU-vaatimustenmukaisuusvakuutuksen koko teksti on saatavana
seuraavassa Internet-osoitteessa: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
EU: n ilmoitus käyttörajoituksista: Tämä laite on rajoitettu vainsisäkäyttöön. Sitä ei saa käyttää ulkona.

sv

Svenska [Swedish]Härmed intygar Lantronix, Inc. att denna X300 Series står Iöverensstämmelse med de väsentliga egenskapskrav och övriga
relevanta bestämmelser som framgår av direktiv 2014/53/EU.
Den fullständiga texten till EU-försäkran om överensstämmelse finnspå följande internetadress: https://www.lantronix.com/products/
lantronix-emg/#tab-docs-downloads
EU-meddelande om begränsningar för användning: Den här enheten
är endast begränsad till inomhusbruk. Det får inte användas utomhus.

Caution:This device operates in the 5150 – 5350 MHz
frequency range, and is restricted to indoor use only.
Outdoor operation in this range is prohibited.
RF Exposure warningThis equipment must be installed and operated inaccordance with provided instructions and the antenna(s)used for this transmitter must be installed to provide aseparation distance of at least 20 cm from all persons.
End-users and installers must be provided with antenna
installation instructions and transmitter operating
conditions for satisfying RF exposure compliance.

X300 Series IoT Cellular Gateway User Guide

220

RF Output Power of X303F202S

X300 Series IoT Cellular Gateway User Guide

221

RF Output Power of X304G002S

X300 Series IoT Cellular Gateway User Guide222

B: Power Cable SchematicPower Cable Schematic
3-pin power cable schematic
Figure B-1 3-pin Power Cable

X300 Series IoT Cellular Gateway User Guide

223

C: List of Acronyms and Protocols
AcronymDescription

2G

2nd Generation

3G

3rd Generation

AES

Advanced Encryption Standard

AP

Access Point (or wireless access point) is a device that provides wirelessservice for clients within its coverage area.

APN

Access Point Name is the name of an access point for the cellular network
data connection.

ASDU

Application Service Data Unit is the IEC-101/IEC-104 data structure that holds
application layer information to exchange between a control center and aremote terminal unit.

CHAP

Challenge handshake protocol is used by PPP to authenticate users and canbe used with many VPNs.

CSQ

Cellular Signal Strength (CSQ). It ranges from 0 to 32.

DHCP

Dynamic Host Configuration Protocol is a standardized networking protocol
used by hosts to dynamically discover and lease an IP address, and learn thecorrect subnet mask, default gateway, and DNS server IP address.

DIO

Digital Input/Output

DLMS

Device Language Message Specification is a set of standards for electricity
meter data exchange.

DMZ

Demilitarized Zone is a physical or logical sub network that contains andexposes an organization's external-facing services to a larger and un-trusted
network, usually the Internet.

DNP3

Distributed Network Protocol version 3 is a protocol used for automation andremote control communication with serial and TCP/IP capabilities used in
SCADA environments.

DNS

Domain Name System is an application layer protocol used throughout theInternet for translating hostnames into their associated IP addresses.

DynDNS, DDNS

Dynamic DNS is a method of automatically updating a name server in the
Domain Name System (DNS), often in real time, with the active DNS
configuration of its configured hostnames, addresses or other information.

EDGE

Enhanced Data rates for GSM Evolution (EDGE) is a backwards-compatible
extension of GSM that provides higher data transmission rates than GSM

GPRSGeneral packet radio service is a packet oriented mobile data standard on the2G and 3G cellular communication network’s GSM

GPSGlobal Positioning Satellite

GSM

Global system for mobile communications

HT Physical mode

High Throughput Physical Mode

IEC-101/IEC-104

IEC-101 (serial) and IEC-104 (TCP) are part of the IEC 60870-5 set ofstandards that define systems or methods used for telecontrol in electricalengineering and power system automation applications.

X300 Series IoT Cellular Gateway User Guide

224

Acronym

Description

ICMP

Internet Control Message Protocol (ICMP) is a TCP/IP network layer protocolthat reports errors and provides other information relevant to IP packet
processing.

IGMP

Internet Group Management Protocol is a communications protocol used byhosts and adjacent gateways on IP networks to establish multicast groupmemberships

IKEv1 and IKEv2

Internet Key Exchange (version 1 or version 2) is an encryption key exchange
mode used between two peers.

IPsec

Internet Protocol Security is a protocol suite for securing Internet Protocol (IP)communications by authenticating and encrypting each IP packet of acommunication session.

ISP

Internet service provider

L2TP

Layer Two Transport Protocol

LAN

Local Area Network

LED

Light emitting diode

M2M

Machine to machine

MAC address

Media Access Control address is a unique identifier (6 bytes) assigned to a
network interface for use as a network address.

MD5

MD5 is a message digest algorithm used as a checksum to verify data integrity

ModbusModbus is a data communication protocol used for connecting industrial
electronic devices.

MTU

Maximum transmission unit of a communications protocol of a layer is the size(in bytes) of the largest protocol data unit that the layer can pass onwards

MWAN

multiple WAN interface

NAT

Network Address Translation is a method of translating IP addresses that are
not globally unique into public addresses in the globally routable address
space.

NMS

Network Management System. Component in SNMP architecture that
includes SNMP manager.

NTP

Network Time Protocol is a networking protocol for clock synchronization
between computer systems over packet-switched, variable-latency data
networks

PAP

Password Authentication Protocol is a password based protocol used by PPP(point to point protocol) to authenticate users and can be used with many
VPNs. PAP is considered less secure than CHAP or some otherauthentication protocols.

PDU

Protocol Data Unit

PoE

Power over Ethernet describes standards for passing electric power and dataover Ethernet cabling between the Power Sourcing Equipment (PSE) and thePowered Device (PD).

PLC

Programmable Logic Controller

PPP

Point to Point Protocol

PPPoE

Point-to-Point Protocol over Ethernet

PPTP

Point-to-Point Tunneling Protocol

X300 Series IoT Cellular Gateway User Guide

225

Acronym

Description

PSK

Pre-shared key

QoS

Quality of Service

RFRadio Frequency

RTU

Remote terminal unit

Rx

Reception

SCP

Secure Copy Protocol

SHA1/SHA2

Secure Hash Algorithm is an encryption cipher type

SIM

Subscriber identity module

SMS

Short Message Service

SNMP

Simple Network Management Protocol

SPI

Serial Peripheral Interface

SSH

Secure Shell

SSID

Service Set Identifier

SSL/TLS

Secure Sockets Layer/Transport Layer Security are encryption-based security
protocols designed to provide data security for Internet communications.

STP

Spanning Tree Protocol is a network protocol that prevents loops whenswitches or bridges are interconnected through multiple paths.

TCP

Transmission Control Protocol

TKIP

Temporal Key Integrity Protocol

Tx

Transmission

UDP

User Datagram Protocol

VPN

Virtual private network

VRRP

Virtual Router Redundancy Protocol

WAN

Wide Area network

WPA/WPA2/WPA3

Wi-Fi Protected Access® (WPA) family of technologies are security protocols
for wireless networks.

X300 Series IoT Cellular Gateway User Guide226

D: Running Commands
Commands can be run on the X300 series gateway using the following methods:

SSH (login as root)
The user has full control and can run commands as described.

System/Custom commands
The user can run commands as described. It is not recommended to run a command or seriesof commands (in a series, commands are separated by semicolon) which take more than 60s
to complete or require additional user interaction. For example: vi.



Percepxion/CLI commands
The user can run commands as described. It is not recommended to run a command or seriesof commands which take more than 60s to complete or require additional user interaction. For
example: vi.

Types of Commands
The following types of commands are available:Bash commands



opkg commands



UCI commands

Bash Commands
Bash shell is distributed with Busybox which provides a stripped down implementation of commonLinux commands.
Usage
BusyBox is a multi-call binary. A multi-call binary is an executable program that performs the samejob as more than one utility program. That means there is just a single BusyBox binary, but thatsingle binary acts like a large number of utilities. This allows BusyBox to be smaller since all thebuilt-in utility programs can share code for many common operations.
Please refer to https://www.busybox.net/downloads/BusyBox.html for usage of these commands.
Note:

Some configuration and commands may not be available on the gateway.

Bash Command Examples
ls
List directory contents
ExampleX300 Series IoT Cellular Gateway User Guide227

To show current directory contents:
# ls
bin
sbin
dev
sys

etc
tmp
http
usr

lib
ltrx_uservar
ltrx_private mnt
wwwoverlay
proc

rom
root

ifconfig

Configure a network interface
ExampleTo show information for eth1 interface:# ifconfig eth1
eth1
Link encap:Ethernet HWaddr A4:AE:9A:04:84:24
inet addr:172.19.100.119 Bcast:172.19.255.255
Mask:255.255.0.0
inet6 addr: 2001:db80:ac13:d91e:a6ae:9aff:fe04:8424/64
Scope:Global
inet6 addr: fe80::a6ae:9aff:fe04:8424/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:102970 errors:0 dropped:0 overruns:0 frame:0
TX packets:8137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6833857 (6.5 MiB) TX bytes:1812823 (1.7 MiB)
Interrupt:32

ip

Replaces the older and now deprecated ifconfig command. The ip command can display andadminister the network configuration of a system. It is used to view, add, and delete network
interfaces, routing table entries, and IP addresses.
ExampleTo show current routing table:# ip routedefault via 172.19.0.1 dev eth1 proto static src 172.19.100.119 metric5default via 172.19.0.1 dev wlan0 proto static src 172.19.100.136 metric6default via 63.42.182.202 dev wwan0 proto static src 63.42.182.201
metric 763.42.182.200/30 dev wwan0 proto static scope link metric 7
172.19.0.0/16 dev eth1 proto static scope link metric 5
172.19.0.0/16 dev wlan0 proto static scope link metric 6
192.168.13.0/24 dev br-lan proto kernel scope link src 192.168.13.1

X300 Series IoT Cellular Gateway User Guide

228

cat

Displays the contents of a file
ExampleTo view contents of a file:# cat /etc/sysupgrade.conf## This file contains files and directories that should## be preserved during an upgrade.
# /etc/example.conf# /etc/openvpn//etc/confdone/etc/sysupgrade.conf/etc/hwinfo.json/ltrx_private/cfg//etc/board.json

logread

Displays logs for diagnostics and troubleshooting.
ExampleTo view syslogd diagnostic logs
# logreadOct 11 20:00:16 Lantronix-G526RP-A4AE9A048423 user.info Eventsms:
TEMPERATURE : 40.00 ºCelsius
Oct 11 20:00:16 Lantronix-G526RP-A4AE9A048423 user.info Eventsms:
CONF_BAND : LTE: [ B2 B4 B5 B13 B66 ]Oct 11 20:00:16 Lantronix-G526RP-A4AE9A048423 user.info Eventsms:
REG_BAND : B4
Oct 11 20:00:16 Lantronix-G526RP-A4AE9A048423 user.info Eventsms:
Operator : 311480
Oct 11 20:00:16 Lantronix-G526RP-A4AE9A048423 user.info Eventsms:
Operator : Verizon
Oct 11 20:00:16 Lantronix-G526RP-A4AE9A048423 user.info Eventsms:
OperatorType : LTE

X300 Series IoT Cellular Gateway User Guide229

opkg Commands
The functionality of the system can be upgraded by downloading and installing pre-madepackages from package repositories (built using the SDK or hosted on Lantronix site:
updates.d2sphere.com).

opkg update

Update the packages list

opkg install

Install software package

opkg remove

Remove software package
ExampleTo update package lists, install and remove zerotier package:# opkg update# opkg install zerotier
Installing zerotier (1.4.6-1) to root...
Downloading http://updates.d2sphere.com/G526RP/ipks/main/
zerotier_1.4.6-1_arm_arm926ej-s.ipk
Installing libminiupnpc (2.1.20190408-2) to root...
Downloading http://updates.d2sphere.com/G526RP/ipks/main/
libminiupnpc_2.1.20190408-2_arm_arm926ej-s.ipk
Installing libnatpmp (20150609-1) to root...
Downloading http://updates.d2sphere.com/G526RP/ipks/main/
libnatpmp_20150609-1_arm_arm926ej-s.ipk
Configuring libminiupnpc.
Configuring libnatpmp.
Configuring zerotier.
disabled in config# opkg remove zerotier
Removing package zerotier from root...

Please refer to: https://openwrt.org/docs/guide-user/additional-software/opkg for usage of the
opkg command.
Note: The System > Software menu on the Web GUI of the gateway provides methods
to configure repositories and install software packages. See Software on page 68.

X300 Series IoT Cellular Gateway User Guide

230

UCI Commands
Unified Configuration Interface (UCI) is a small utility written in C (a shell script-wrapper isavailable as well) and is intended to centralize the whole configuration of the router.
ExampleTo change Percepxion client status update interval:# uci get percepxion.Basic.Status_Update_Interval
1# uci set percepxion.Basic.Status_Update_Interval=5# uci commit percepxion# /etc/init.d/percepxion reload
Changed Status Update Interval to '5 minutes'.
Please refer to: https://openwrt.org/docs/guide-user/base-system/uci for usage of the UCI
commands.
Note:

Some configuration and commands may not be available on the router.

X300 Series IoT Cellular Gateway User Guide231

D: Lantronix Technical Support
Lantronix offers many resources to support our customers and products at
http://www.lantronix.com/support.
For example, you can browse the knowledge base, open a support issue, find firmware
downloads, view tutorials, and more. At this site you can also find FAQs, product bulletins,
warranty information, extended support services, and product documentation.
To submit a support request, please use the Lantronix Technical Support portal athttps://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/overview (registration required).
To contact Lantronix Sales, look up your local office at
https://www.lantronix.com/about-us/contact/.

X300 Series IoT Cellular Gateway User Guide

232