Operating Manual

LTECube-CAT4NA2-WIFI
IoT 150Mbps CAT4 LTE Ethernet Gateway

LTECube-CAT4GL-WIFI
IoT 150Mbps CAT4 LTE Ethernet Gateway

Document Revision: v1.2.0

150 Country Hills Landing NW

Calgary, Alberta
Canada T3K 5P3

Phone: (403) 248-0028

Toll Free: 1-855-353-0028
www.microhardcorp.com
Important User Information

Warranty
Microhard Systems Inc. warrants that each product will be free of defects in material and workmanship for a
period of one (1) year for its products. The warranty commences on the date the product is shipped by Micro-
hard Systems Inc. Microhard Systems Inc.’s sole liability and responsibility under this warranty is to repair or
replace any product which is returned to it by the Buyer and which Microhard Systems Inc. determines does
not conform to the warranty. Product returned to Microhard Systems Inc. for warranty service will be shipped
to Microhard Systems Inc. at Buyer’s expense and will be returned to Buyer at Microhard Systems Inc.’s ex-
pense. In no event shall Microhard Systems Inc. be responsible under this warranty for any defect which is
caused by negligence, misuse or mistreatment of a product or for any unit which has been altered or modified
in any way. The warranty of replacement shall terminate with the warranty of the product.
Warranty Disclaims
Microhard Systems Inc. makes no warranties of any nature of kind, expressed or implied, with respect to the
hardware, software, and/or products and hereby disclaims any and all such warranties, including but not lim-
ited to warranty of non-infringement, implied warranties of merchantability for a particular purpose, any inter-
ruption or loss of the hardware, software, and/or product, any delay in providing the hardware, software, and/
or product or correcting any defect in the hardware, software, and/or product, or any other warranty. The Pur-
chaser represents and warrants that Microhard Systems Inc. has not made any such warranties to the Pur-
chaser or its agents MICROHARD SYSTEMS INC. EXPRESS WARRANTY TO BUYER CONSTITUTES MICROHARD
SYSTEMS INC. SOLE LIABILITY AND THE BUYER’S SOLE REMEDIES. EXCEPT AS THUS PROVIDED, MICROHARD
SYSTEMS INC. DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTY OF MER-
CHANTABILITY OR FITNESS FOR A PARTICULAR PROMISE.
MICROHARD SYSTEMS INC. PRODUCTS ARE NOT DESIGNED OR INTENDED TO BE USED IN
ANY LIFE SUPPORT RELATED DEVICE OR SYSTEM RELATED FUNCTIONS NOR AS PART OF
ANY OTHER CRITICAL SYSTEM AND ARE GRANTED NO FUNCTIONAL WARRANTY.
Indemnification
The Purchaser shall indemnify Microhard Systems Inc. and its respective directors, officers, employees, suc-
cessors and assigns including any subsidiaries, related corporations, or affiliates, shall be released and dis-
charged from any and all manner of action, causes of action, liability, losses, damages, suits, dues, sums of
money, expenses (including legal fees), general damages, special damages, including without limitation,
claims for personal injuries, death or property damage related to the products sold hereunder, costs and de-
mands of every and any kind and nature whatsoever at law.

IN NO EVENT WILL MICROHARD SYSTEMS INC. BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL,
INCIDENTAL, BUSINESS INTERRUPTION, CATASTROPHIC, PUNITIVE OR OTHER DAMAGES WHICH MAY BE
CLAIMED TO ARISE IN CONNECTION WITH THE HARDWARE, REGARDLESS OF THE LEGAL THEORY BEHIND
SUCH CLAIMS, WHETHER IN TORT, CONTRACT OR UNDER ANY APPLICABLE STATUTORY OR REGULATORY
LAWS, RULES, REGULATIONS, EXECUTIVE OR ADMINISTRATIVE ORDERS OR DECLARATIONS OR OTHERWISE,
EVEN IF MICROHARD SYSTEMS INC. HAS BEEN ADVISED OR OTHERWISE HAS KNOWLEDGE OF THE POSSIBIL-
ITY OF SUCH DAMAGES AND TAKES NO ACTION TO PREVENT OR MINIMIZE SUCH DAMAGES. IN THE EVENT
THAT REGARDLESS OF THE WARRANTY DISCLAIMERS AND HOLD HARMLESS PROVISIONS INCLUDED ABOVE
MICROHARD SYSTEMS INC. IS SOMEHOW HELD LIABLE OR RESPONSIBLE FOR ANY DAMAGE OR INJURY, MI-
CROHARD SYSTEMS INC.'S LIABILITY FOR ANYDAMAGES SHALL NOT EXCEED THE PROFIT REALIZED BY MI-
CROHARD SYSTEMS INC. ON THE SALE OR PROVISION OF THE HARDWARE TO THE CUSTOMER.
Proprietary Rights
The Buyer hereby acknowledges that Microhard Systems Inc. has a proprietary interest and intellectual prop-
erty rights in the Hardware, Software and/or Products. The Purchaser shall not (i) remove any copyright, trade
secret, trademark or other evidence of Microhard Systems Inc.’s ownership or proprietary interest or confiden-
tiality other proprietary notices contained on, or in, the Hardware, Software or Products, (ii) reproduce or modi-
fy any Hardware, Software or Products or make any copies thereof, (iii) reverse assemble, reverse engineer or
decompile any Software or copy thereof in whole or in part, (iv) sell, transfer or otherwise make available to
others the Hardware, Software, or Products or documentation thereof or any copy thereof, except in accord-
ance with this Agreement.

© Microhard 2
Important User Information (continued)

About This Manual

It is assumed that users of the products described herein have either system integration or
design experience, as well as an understanding of the fundamentals of radio communications.

Throughout this manual you will encounter not only illustrations (that further elaborate on the
accompanying text), but also several symbols which you should be attentive to:

Caution or Warning
Usually advises against some action which could result in undesired or
detrimental consequences.

Point to Remember
Highlights a key feature, point, or step which is noteworthy. Keeping
these in mind will simplify or enhance device usage.

Tip
An idea or suggestion to improve efficiency or enhance usefulness.

Information
Information regarding a particular technology or concept.

© Microhard 3
Important User Information (continued)

Regulatory Requirements / Exigences Réglementaires

To satisfy FCC RF exposure requirements for mobile transmitting devices, a separation distance of 23cm or more should be maintained
between the antenna of this device and persons during device operation. To ensure compliance, operations at closer than this distance is not
recommended. The antenna being used for this transmitter must not be co-located in conjunction with any other antenna or transmitter.

Pour satisfaire aux exigences de la FCC d'exposition RF pour les appareils mobiles de transmission, une distance de séparation de 23cm ou
WARNING plus doit être maintenue entre l'antenne de cet appareil et les personnes au cours de fonctionnement du dispositif. Pour assurer le respect,
les opérations de plus près que cette distance n'est pas recommandée. L'antenne utilisée pour ce transmetteur ne doit pas être co-localisés
en conjonction avec toute autre antenne ou transmetteur.

MAXIMUM EIRP
FCC Regulations allow up to 36dBm Effective Isotropic Radiated Power (EIRP). Therefore, the sum of the transmitted power (in dBm), the
cabling loss and the antenna gain cannot exceed 36dBm.

WARNING Réglementation de la FCC permettra à 36dBm Puissance isotrope rayonnée équivalente (EIRP). Par conséquent, la somme de la puissance
transmise (en dBm), la perte de câblage et le gain d'antenne ne peut pas dépasser 36dBm.

EQUIPMENT LABELING / ÉTIQUETAGE DE L'ÉQUIPEMENT

This device has been modularly approved. The manufacturer, product name, and FCC and Industry Canada identifiers of this product must
appear on the outside label of the end-user equipment.

Ce dispositif a été approuvé de façon modulaire. Le fabricant, le nom du produit, et la FCC et de l'Industrie du Canada identifiants de ce
WARNING produit doit figurer sur l'étiquette à l'extérieur de l'équipement de l'utilisateur final.

SAMPLE LABEL REQUIREMENT / EXIGENCE D'ÉTIQUETTE :

LTECube-CAT4NA2-WIFI: LTECube-CAT4GL-WIFI:

FCCID: XMR201808EC25AF FCCID: XMR201903EG25G

IC: 10224A-2018EC25AF IC: 10224A-201903EG25G

This device complies with Part 15 of the FCC Rules. This device complies with Part 15 of the FCC Rules.
Operation is subject to the following two conditions: Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, (1) this device may not cause harmful interference,
and (2) this device must accept any interference and (2) this device must accept any interference
received including interference that may cause received including interference that may cause
undesired operation. undesired operation.

FCCID: NS916PX2
IC: 3143A-16PX2

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.

Please Note: These are only sample labels; different products contain different identifiers. The actual identifiers should be seen on
your devices if applicable. S'il vous plaît noter: Ce sont des exemples d'étiquettes seulement; différents produits contiennent des
identifiants différents. Les identifiants réels devrait être vu sur vos périphériques le cas échéant.

© Microhard 4
Revision History

Revision Description Initials Date

1.0.0 First Release. (Based on firmware v1.3.0-r1058) PEH 01/2020
1.0.1 Updated FCC/IC ID PEH 09/2020
1.1.0 Updated to Firmware v1.3.0-r1080 PEH 06/2021
1.2.0 Updated to Firmware v1.3.0-r1086 PEH 01/2023

© Microhard 5
Table of Contents

1.0 Overview ......................................................................................................... 9

1.1 Performance Features ....................................................................................................... 9
1.2 Specifications ..................................................................................................................... 10

2.0 QUICK START ................................................................................................. 11

2.1 Installing the SIM Card ....................................................................................................... 11
2.2 Getting Started with Cellular .............................................................................................. 11

3.0 Hardware Features ......................................................................................... 15

3.1 Hardware Features............................................................................................................. 15
3.1.1 Mechanical Drawings ............................................................................................... 16
3.1.2 Connectors & Indicators ........................................................................................... 17
3.1.2.1 Front & Top ................................................................................................ 17
3.1.2.2 Rear & Side................................................................................................ 18

4.0 Configuration.................................................................................................. 20
4.0 Web User Interface ........................................................................................................... 20
4.0.1 Logon Window .......................................................................................................... 21
4.1 System ............................................................................................................................... 23
4.1.1 Summary .................................................................................................................. 23
4.1.2 Settings ..................................................................................................................... 23
Host Name................................................................................................................ 23
Console Timeout ...................................................................................................... 23
Date/Time ................................................................................................................. 24
NTP Server Settings ................................................................................................. 24
4.1.3 Services .................................................................................................................... 26
FTP ........................................................................................................................... 26
Telnet ........................................................................................................................ 26
HTTP/HTTPS ........................................................................................................... 26
4.1.4 Keepalive .................................................................................................................. 27
4.1.5 Maintenance ............................................................................................................. 29
Firmware Upgrade .................................................................................................... 29
Reset to Default ........................................................................................................ 29
Backup & Restore Configurations ............................................................................ 30
4.1.6 Reboot ...................................................................................................................... 31
4.2 Network ............................................................................................................................. 32
4.2.1 Status ....................................................................................................................... 32
4.2.2 LAN ........................................................................................................................... 33
4.2.3 DHCP (MAC Binding) ............................................................................................... 37
4.2.4 DDNS ....................................................................................................................... 38
4.2.5 Routes ...................................................................................................................... 40
4.2.6 VRRP (Virtual Router Redundancy Protocol) .......................................................... 42
4.2.7 Ports ......................................................................................................................... 43
4.2.8 Bandwidth (Throttling Control) .................................................................................. 44
4.2.9 Device List ................................................................................................................. 45
4.2.10 Cloud Filter (Content/Security Filter) ....................................................................... 46
4.2.11 MultiWAN ................................................................................................................ 47

© Microhard 6
Table of Contents

4.3 IPv6 .................................................................................................................................... 50

4.3.1 Status ....................................................................................................................... 50
4.3.2 Setup ........................................................................................................................ 51
4.3.3 Firewall6 ................................................................................................................... 55
4.3.4 Route6 ...................................................................................................................... 57
4.4 Carrier ................................................................................................................................ 58
4.4.1 Status ....................................................................................................................... 58
4.4.2 Settings ..................................................................................................................... 59
APN .......................................................................................................................... 61
4.4.3 SMS .......................................................................................................................... 63
4.4.4 SMS Config .............................................................................................................. 63
4.4.5 Data Usage ............................................................................................................... 65
Data Usage History .................................................................................................. 68
4.5 Wireless (802.11 WIFI) ..................................................................................................... 69
4.4.1 Status ....................................................................................................................... 69
4.4.2 Settings ..................................................................................................................... 70
4.4.3 Hotspot ..................................................................................................................... 76
4.6 Firewall ............................................................................................................................. 80
4.6.1 Summary .................................................................................................................. 80
4.6.2 General ..................................................................................................................... 81
4.6.3 Port Forwarding ........................................................................................................ 83
4.6.4 MAC-IP List .............................................................................................................. 86
4.6.5 Rules ........................................................................................................................ 88
4.6.6 Firewall Default ......................................................................................................... 90
4.7 VPN .................................................................................................................................. 91
4.7.1 Summary .................................................................................................................. 91
4.7.2 Gateway to Gateway ................................................................................................ 92
4.7.3 L2TP ......................................................................................................................... 98
4.7.3.1 L2TP Client ................................................................................................... 98
4.7.3.2 L2TP Server ................................................................................................. 100
4.7.4 OpenVPN ................................................................................................................. 102
OpenVPN Server ...................................................................................................... 102
OpenVPN Client ....................................................................................................... 106
4.7.5 GRE .......................................................................................................................... 108
4.7.6 VPN Users ................................................................................................................ 111
4.7.7 Certificate Management ........................................................................................... 112
4.8 Router ................................................................................................................................ 113
4.8.1 RIPv2 ....................................................................................................................... 113
4.8.2 OSPFv2 .................................................................................................................... 114
4.8.3 SMCRoute ................................................................................................................ 115
4.9 GPS .................................................................................................................................... 117
4.9.1 Location .................................................................................................................. 117
4.9.2 Settings ................................................................................................................... 118
4.9.3 Report ..................................................................................................................... 119
4.9.4 GpsGate ................................................................................................................. 122
4.9.5 UDPTracker ............................................................................................................ 125
4.9.6 Recorder ................................................................................................................. 127
4.9.7 Load Record ........................................................................................................... 129
4.9.8 TAIP ........................................................................................................................ 131

© Microhard 7
Table of Contents

4.10 Apps .................................................................................................................................. 133

4.10.1 Modbus ................................................................................................................... 133
4.10.1.1 TCP Modbus ............................................................................................. 133
4.10.1.2 Modbus Data Map ................................................................................... 135
4.10.2 Netflow Report ........................................................................................................ 136
4.10.3 Local Monitor .......................................................................................................... 138
4.10.4 IoT ........................................................................................................................... 139
4.10.5 SSL Management ................................................................................................... 141
4.10.6 Event Report ........................................................................................................... 142
4.10.6.1 Configuration ............................................................................................ 142
4.10.6.2 Message Structure ................................................................................... 143
4.10.6.3 Message Payload ..................................................................................... 144
4.10.7 Alert (SMS/Email Alerts) ......................................................................................... 142
4.11 Diag .................................................................................................................................... 149
4.11.1 Ping ......................................................................................................................... 149
4.11.2 Traceroute ............................................................................................................... 149
4.11.3 Iperf ......................................................................................................................... 150
4.11.4 Speedtest ................................................................................................................ 152
4.12 Admin ................................................................................................................................ 154
4.12.1 Users ....................................................................................................................... 154
4.12.2 NMS ........................................................................................................................ 156
4.12.3 SNMP ...................................................................................................................... 160
4.12.4 Discovery ................................................................................................................ 163
4.12.5 Logout ..................................................................................................................... 164

5.0 AT Command Line Interface .......................................................................... 165

5.1 AT Command Overview ................................................................................................... 165
5.2 AT Command Syntax ....................................................................................................... 166
5.3 Supported AT Commands ............................................................................................... 167

Appendices .......................................................................................................... 181

Appendix A: Port Forwarding Example ...................................................................................... 181
Appendix B: VPN (Site to Site) Example .................................................................................... 183
Appendix C: Firewall Rules Example ......................................................................................... 185
Appendix D: Troubleshooting ..................................................................................................... 187

© Microhard 8
1.0 Overview

The LTECube-4-WIFI was engineered specifically for the low cost, small size, low power re-
quirements of IoT and M2M applications. The LTECube-4-WIFI provides up to 150 Mbps
throughput of CAT4 LTE Cellular data. The LTECube-CAT-WIFI models feature a 10/100
Ethernet Port and high power 2.4 GHz 802.11 b/g/n WIFI.

The LTECube-CAT4-WIFI utilizes the cellular infrastructure to provide network access to

wired devices anywhere cellular coverage is supported by a cellular carrier. The LTECube
supports LTE connections with robust and reliable CAT4 speeds.

Providing reliable Cellular Ethernet bridge functionality as well gateway service for most
equipment types which employ a RJ45 Ethernet or WIFI interface, the LTECube Series can
be used in low bandwidth applications such as:

• IoT Applications • Point of Sale Systems

• M2M Applications • SCADA (PLC’s, Modbus,
• Remote Access Hart)
• Electronic Signs/Billboards • Utilities/Metering
• Traffic Signals • Sensor Data

1.1 Performance Features

Key performance features of the LTECube-CAT4-WIFI include:

• Robust & reliable connections to LTE Networks w/ Fallback

• Up to 150 Mbps Downloads and 50 Mbps Uploads.

• DMZ and Port Forwarding

• 10/100 Ethernet Port

• High Power 802.11 b/g/n 2.4 GHz WIFI

• User interface via local console, SSH, HTTP/HTTPS web browser

• Compatibility with virtually all ethernet based PLCs, RTUs.

• Local & remote wireless firmware upgradable

• User configurable Firewall with IP/MAC ACL

• IP/Sec secure VPN and GRE Tunneling

• IPv6 Addressing, Firewall, OpenVPN and Routing Capabilities

• Industrial Temperature Rating (-40°C to +85°C)

© Microhard 9
1.0 Overview

1.2 Specifications

Cellular

LTECube-CAT4NA2-WIFI Supported Bands: LTE FDD: B2,B4,B5,B12,B13,B14,B66,B71

WCDMA: B2,B4,B5

LTECube-CAT4NA2-WIFI Data Features: LTE FDD: Up to 150 Mbps DL, 50 Mbps UL

LTE TDD: Up to 130 Mbps DL, 35 Mbps UL
DC-HSPA+: Up to 42 Mbps DL, 5.7 Mbps UL
WCDMA: Up to 384 Kbps DL, 384 Kbps UL

LTECube-CAT4GL-WIFI Supported Bands: LTE FDD: B1,B2,B3,B4,B5,B7,B8,B12,B13,

B18,B19,B20,B26,B28
TDD: B38,B39,B40,B41
WCDMA: B1,B2,B4,B5,B8,B6,B19
GSM: B2/B3/B5/B8

LTECube-CAT4GL-WIFI Data Features: LTE FDD: Up to 150 Mbps DL, 50 Mbps UL

LTE TDD: Up to 130 Mbps DL, 35 Mbps UL
DC-HSPA+: Up to 42 Mbps DL, 5.7 Mbps UL
WCDMA: Up to 384 Kbps DL, 384 Kbps UL
EDGE: Up to 296 Kbps DL, 236.8 Kbps UL
GSM: Up to 107 Kbps DL, 85.6 Kbps UL
General
USB*: USB 2.0
(*Future)

Current Consumption: Typical: 120mA ~ 240mA

(@12VDC)

Ethernet: 10/100 BaseT, Auto - MDI/X, IEEE 802.3

SIM Card: Nano SIM 1.8 / 3.0V 4FF size

PPP Characteristics: Dial on Demand/Idle Time

Network Protocols: IPv4, IPv6, TCP, UDP, TCP/IP, TFTP, ARP, ICMP, DHCP, HTTP,
HTTPS, SSH, SNMP, FTP, DNS

Management: Telnet, WebUI, SNMP, FTP &

Wireless Upgrade, RADIUS authentication, IPsec VLAN

Diagnostics: Temperature, RSSI, remote diagnostics

Input Voltage: 5-30 VDC or Passive POE on LAN or USB Powered (5V @1.5A)

Environmental

Operation Temperature: -40oF(-40oC) to 185oF(850C)

Humidity: 5% to 95% non-condensing

Mechanical

Dimensions: 1.75” (45mm) X 3.25” (85mm) X 1.0” (25mm)

Weight: Approx. 135 grams

Connectors: Antenna(s): CELL, DIV: SMA Female, WIFI: RP-SMA Female

Data: Ethernet: RJ-45
PWR: Power: SMT: 4-Pin Micro MATE-N-LOK AMP 3-794618-4
Mating Connector: 4-Pin Micro MATE-N-LOK AMP 794617-4

© Microhard 10
2.0 Quick Start

This QUICK START guide will walk you through the setup and process required to access the
WebUI configuration window and to establish a basic wireless connection to your carrier.

Note that the units arrive from the factory with the Local Network setting configured as
‘Static’ (IP Address 192.168.168.1, Subnet Mask 255.255.255.0), in DHCP server mode.

2.1 Installing the SIM Card

✓ Before the LTECube can be used on a cellular network a valid SIM Card for your Wireless
Carrier must be installed. Insert the SIM Card into the SIM tray, use the included tool to
eject the tray, the SIM will only fit into the tray if installed properly.

To reset to factory SIM Card Tray

defaults, press and hold
the CFG button for 8
seconds with the LTECube
powered up. The LED’s
will flash quickly and the
modem will reboot with
factory defaults.

2.2 Getting Started with Cellular

✓ Connect the Antenna’s to the applicable ANTENNA jack’s of the LTECube.

Main & Diversity

Antennas

✓ Connect the power connector to the power adapter and apply power to the unit, once
fully booted, proceed to the next step.

Use the MHS-supplied

power adapter or an
equivalent power source.

5-30VDC

The LTECube-CAT4-WIFI can alternatively be powered via

passive PoE or by USB (5V, 1.5A)

© Microhard 11
2.0 Quick Start

✓ Connect A PC configured for DHCP directly to the LAN port of the LTECube, using an
Ethernet Cable. If the PC is configured for DHCP it will automatically acquire a IP Address
from the LTECube.

✓ Open a Browser Window and enter the IP address 192.168.168.1 into the address bar.

192.168.168.1
The factory default network
settings:

IP: 192.168.168.1
Subnet: 255.255.255.0
Gateway: 192.168.168.1
✓ The LTECube will then ask for a Username and Password. Enter the factory defaults listed
below.

The Factory default login:

User name: admin

Password: admin

You will be required to change the

default password when you login
for the first time.

The factory default login:

User name: admin

Subnet: admin

It is always a good idea to

change the default admin
login for future security.

© Microhard 12
2.0 Quick Start

✓ Once successfully logged in, the System Summary page will be displayed.

Auto APN: The LTECube will

attempt to detect the carrier
based on the SIM card
installed and cycle through a
list of commonly used APN’s
to provide quick network
connectivity.

✓ If the SIM card is installed, but an APN has not been specified. The LTECube will try to
use Auto APN (default) which may provide quick network connectivity, but may not work
with some carriers, or with private APN’s.

✓ To set or change the APN, click on the Carrier > Settings tab and enter the APN supplied
by your carrier in the APN field. Some carriers may also require a Username and Pass-
word.

© Microhard 13
2.0 Quick Start

✓ On the Carrier > Status Tab, verify that a WAN IP Address has been assigned by your
carrier. It may take a few minutes, so try refreshing the page if the WAN IP Address
doesn’t show up right away. The Activity Status should also show “Connected”.

✓ If you have set a static IP on your PC, you may need to add the DNS Servers shown in
the Carrier Status Menu to you PC to enable internet access.
Ensure the default
passwords are changed. ✓ Congratulations! Your LTECube is successfully connected to your Cellular Carrier.

✓ To access devices connected to LTECube remotely, one or more of the following must be
configured: Port Forwarding, DMZ or VPN Tunnel.

✓ Ensure that all default passwords are changed to limit access to the modem.

Set up appropriate firewall

rules to block unwanted ✓ For best practices and to limit data charges it is critical to properly set up the
incoming data. firewall. (Especially important for Public Static IP addresses.)

© Microhard 14
3.0 Hardware Features

3.1 LTECube-CAT4-WIFI
The LTECube is available in a enclosed version ready to be interfaced to external devices with standard
connectors as discussed below. A optional mounting bracket can be ordered to allow the enclosed version
of the LTECube to be mounted for fixed installations.

Image 3-1: LTECube-CAT4-WIFI

The LTECube-CAT4-WIFI Hardware Features Include:

• Standard Connectors for:

• 10/100 Ethernet Port (RJ45)
• 4-Pin: MATE-N-LOK Type Connector for Power
• 3x SMA Female Cellular Antenna Ports (Main + Diversity + GPS)
• 1x RP-SMA Female WIFI Antenna Port
• Status/Diagnostic LED’s for RSSI(x3), Tx/RX, GPS, Status
• Nano-SIM (4FF) Card Tray
• CFG Button for factory default / firmware recovery operations
• Micro USB Connector (Internal/Future Development, Optional Power (requires min 5V @1.5A))

© Microhard 15
3.0 Hardware Features

3.1.1 Mechanical Drawing

© Microhard 16
3.0 Hardware Features

3.1.2 Connectors and Indicators

3.1.2.1 Front & Top

On the front of the LTECube-CAT4-WIFI is the CFG Button, USB Port, Main/Diversity/GPS/WIFI Antenna
Connectors and the SIM Card Slot/tray. The top of the LTECube are the status indicators, RSSI, RF (TX/
RX), GPS and Status.

Drawing 3-6: LTECube-CAT4-WIFI Front & Top View

The USB port is for internal use and may be a future development to be available at a later date. The unit
can also be powered via the USB port, provided it can provide a minimum of 5V @1.5A.

The Main and Diversity antennas are required for the LTE connection to the cellular carrier.

The GPS antenna is required for a GPS connection to provide location based services.

The WIFI antenna is used for the optional 802.11 b/g/n WIFI available for the LTECube.

CFG (Button) - Holding this button while powering-up the LTECube will boot the unit into FLASH FILE
SYSTEM RECOVERY mode (factory use only). One the Statis LED starts to flash, hold for 1 second for
httpd recovery mode, 5 seconds for tftp recovery mode, or 10 seconds for master reset. If button is held for
longer than 15 seconds the button will be ignored.

If the unit has been powered-up for some time (>1 minute), depressing the CFG Button for ~10 seconds
(unit will reboot) will result in FACTORY DEFAULTS being restored, including the static factory IP address.
The factory default network This IP address is useable in a Web Browser for accessing the Web User Interface.
settings:

IP: 192.168.168.1 Receive Signal Strength Indicator (RSSI) - As the received signal strength increases, starting with the
Subnet: 255.255.255.0
Gateway: 192.168.168.1 furthest left, the number of active RSSI LEDs increases.

GPS - Indicates that the optional standalone GPS module Signal RSSI1 RSSI2 RSSI3
has synchronized and is ready for use. (dBm)

(-85, 0] ON ON ON
RF (Tx(Blue)/Rx(Green)) LED’s - The RF Tx/Rx LED’s
(-90, -85] ON ON FLASH
indicate carrier (cellular) traffic.
(-95, -90] ON ON OFF
Status/CPU LED (Blue) - The CPU LED indicates that
(-100, -95] ON FLASH OFF
power has been applied to the module.
(-105, -100] ON OFF OFF
SIM - This tray is used to install SIM card(s) provided by
(-109, -105] FLASH OFF OFF
the cellular carrier. Use the tool provided to eject the SIM
tray. The SIM will only sit properly if placed in the correct Other SCANNING SCANNING SCANNING
orientation.
Table 3-1: RSSI LED’s

© Microhard 17
3.0 Hardware Features

3.1.2.2 Rear & Side View

Located on the back of the LTECube are the Power and Ethernet interface.

Drawing 3-7: LTECube Rear & Side View

The LAN Port is a 10/100 Mbps RJ-45 interface used to connect Ethernet based field devices.

Vin+/Vin– is used to power the unit. The input Voltage range is 5-30 Vdc.

The LTE Cube can be powered via Passive PoE Injector or Active to Passive PoE Adapter with a with a
maximum output voltage of 30 VDC. Passive PoE Injectors and Active to Passive PoE Adapters are
available from Microhard for use with the LTE Cube.

The LTE Cube can also be powered from USB (5V @ 1.5A)
Caution: Using a power
supply that does not
provide proper voltage
may damage the modem.
Ethernet RJ45 Connector Pin Number

Source
1 2 3 4 5 6 7 8
Voltage

5 - 30 Vdc Data Data Data DC+ DC+ Data DC- DC-

Table 3-3: Ethernet PoE Connections

LTE Cube LTE Cube LTE Cube

LAN LAN LAN 9 - 30V
24V

PoE Passive
Adapter PoE
Injector
802.3AF/AT 802.3AF/AT
LAN Port
9—30V
PoE Switch PoE Switch Non PoE Switch/Device

© Microhard 18
3.0 Hardware Features

Microhard Active PoE Adapter

The LTE Cube cannot be directly powered by a Active PoE switch, and may be damaged by doing so.
The following Active PoE Adapter is available from Microhard to allow the LTE Cube to be connected to a
Active PoE switch.

Microhard Active PoE Adapter

24VDC

Active PoE Switch

802.3AF/AT

Microhard Passive PoE Injector

To use the Passive PoE feature of the LTE Cube, you must use a Passive PoE Injector with a maximum
output voltage of 30VDC. It is recommended to use the Passive PoE Injector available from Microhard.

Microhard Passive PoE Injector

24VDC

24VDC
Non-PoE Switch
or device

© Microhard 19
4.0 Configuration

4.0 Web User Interface

Image 4-0-1: WebUI

The factory default network Initial configuration of an LTECube using the Web User (Browser) Interface (Web UI) method involves the
settings:
following steps:
IP: 192.168.168.1
Subnet: 255.255.255.0
Gateway: 192.168.168.1
• configure a static IP Address on your PC to match the default subnet or if your PC is configured for
DHCP, simply connect a PC to a LAN port of the LTECube and it will be assigned a IP address
automatically.

• connect the LTECube (LAN) port to your PC using an Ethernet cable

• apply power to the LTECube and wait approximately 60 seconds for the system to load

• open a web browser and enter the factory default IP address(192.168.168.1) of the unit:

• logon window appears; log on using default Username: admin Password: admin

• use the web browser based user interface to configure the LTECube as required.

• refer to Section 2.0: Quick Start for step by step instructions.

In this section, all aspects of the Web Browser Interface, presented menus, and available configuration
options will be discussed.

© Microhard 20
4.0 Configuration

4.0.1 Logon Window

Upon successfully accessing the LTECube using a Web Browser, the Logon window will appear.

For security, do not allow the

web browser to remember the
User Name or Password.

Image 4-0-2: Logon Window

The factory default User Name is: admin

The default password is: admin

Note that the password is case sensitive. It should be changed (discussed further along in this section),
but once changed, if forgotten, may not be recovered.
It is advisable to change the
login Password. Do not
FORGET the new password When entered, the password appears as ’dots’ as shown in the image below. This display format prohibits
as it cannot be recovered. others from viewing the password.

The ‘Remember my password’ checkbox may be selected for purposes of convenience, however it is
recommended to ensure it is deselected - particularly once the unit is deployed in the field - for one
primary reason: security.

If the LTECube is restored to factory defaults the password is also restored to the original default
password.

It is required to change the password upon initial login, once the password is changed, it will be
required to login to the unit once again with the updated password.

© Microhard 21
4.0 Configuration

4.1 System
The main category tabs located at the top of the navigation bar separate the configuration of the LTECube
into different groups based on function. The System Tab contains the following sub menu’s:

• Summary - Status summary of entire radio including network settings,

version information, and radio connection status
• Settings - Host Name, System Log Settings, System Time/Date
• Services - Enable/Disable and configure port numbers for SSH, Telnet, HTTP
and HTTPS services
• Keepalive - Configure System keep alive to ensure network/internet access.
• Maintenance - Remote firmware Upgrades, reset to defaults, configuration backup
and restore.
• Reboot - Schedule reboots and/or immediately reboot the system.

4.1.1 System > Summary

The System Summary screen is displayed immediately after initial login, showing a summary and status of
all the functions of the LTECube in a single display. This includes information about the System, Carrier
(Cellular Carrier) and network status.

The System Summary page

will Auto Refresh, each time
this happens a small amount
of data is used. If viewing
over the Cellular Network this
data could add up to a
significant amount over a long
period of time.

Image 4-1-1: System Summary Window

© Microhard 22
4.0 Configuration

4.1.2 System > Settings

System Settings

Options available in the System Settings menu allow for the configuration of the Host Name, Description,
Console Timeout and System Log server settings.

Image 4-1-2: System Settings > System Settings

Host Name/Description
The Host Name is a convenient identifier for a specific LTECube unit. Values (characters)
This feature is most used when accessing units remotely: a convenient
cross-reference for the unit’s WAN/Carrier IP address. This name LTECube (varies)
appears when logged into a telnet session, or when the unit is
reporting into Microhard NMS System. up to 30 characters
The description provides an additional field for text characters, but is
not displayed anywhere but in this field.

Console Timeout (s)

This value determines when a console connection (made via Console Values (seconds)
Port or Telnet) will timeout after becoming inactive.
60
0-65535

CFG Reset to Default Button

Enabled by default, when the CFG button on the front of the LTECube Values (Selection)
is held down for 10s while the unit is powered up, the unit will reset
and all settings will be reset to factory defaults. When disabled the unit Enable
will reset, but the settings will not be overwritten. Disable

© Microhard 23
4.0 Configuration

System Syslog Server IP

The LTECube can report system level events to a third party Syslog server, IP Address
which can be used to monitor events reported by the LTECube.
0.0.0.0
The system syslog can also be viewed locally by using the following URL
and inserting the LTECube IP Address:

http://xxx.xxx.xxx.xxx/cgi-bin/webif/request.sh?syslog

System Syslog Server Port

Enter the UDP listening port of the Syslog Server. The default port number UDP Port
is generally 514, but could vary from Server to Server.
514

Time Settings

The LTECube can be set to use a local time source, thus keeping time on its own, or it can be configured
to synchronize the date and time via a NTP Server. The options and menus available will change
depending on the current setting of the Date and Time Setting Mode, as seen below.

Network Time Protocol (NTP)

can be used to synchronize the
time and date or computer
systems with a centralized,
referenced server. This can
help ensure all systems on a
network have the same time
and date.

Image 4-1-3: System Settings > Time Settings

Date and Time Setting Mode

Select the Date and Time Setting Mode required. If set for ‘Use Local Values (selection)
Time’ the unit will keep its own time and not attempt to synchronize
with a network server. If ‘Synchronize Date And Time Over Network’ is Use Local Time Source
selected, a NTP server can be defined. Synchronize Date And Time
Over Network

Date
The calendar date may be entered in this field. Note that the entered Values (yyyy-mm-dd)
value is lost should the LTECube lose power for some reason.
2015.04.01 (varies)

© Microhard 24
4.0 Configuration

Time
The time may be entered in this field. Note that the entered value is Values (hh:mm:ss)
lost should the LTECube lose power for some reason.
11:27:28 (varies)

Timezone
If connecting to a NTP time server, specify the timezone from the Values (selection)
dropdown list.
User Defined (or out of date)

POSIX TZ String
This displays the POSIX TZ String used by the unit as determined by Values (read only)
the timezone setting.
(varies)

NTP Server
Enter the IP Address or domain name of the desired NTP time server. Values (address)
pool.ntp.org

NTP Port
Enter the IP Address or domain name of the desired NTP time server. Values (port#)
123

NTP Client Interval

By default the modem only synchronizes the time and date during Values (seconds)
system boot up (default: 0), but it can be modified to synchronize at a
regular interval. This process does consume data and should be set 0
accordingly.

Local NTP Server / Port

When enabled the LTECube will act as a NTP Server for subtending Values (seconds)
local devices, the port used for the NTP Server is 123 (read only).
Enable / Disable

© Microhard 25
4.0 Configuration

4.1.3 System > Services

Services in the LTECube can be disabled/enabled as well as changing the default ports used for either
security considerations or resource considerations. The changes are applied after a reboot.

Image 4-1-4: System > Services

FTP
The FTP service can be enabled/disabled using the Services Status Values (selection)
Menu. The FTP service is used for firmware recovery operations.
Enable / Disable

Telnet
Using the Telnet Service Enable/Disable function, you can disable the Values (port)
Telnet service from running on the modem. The port used by the
Telnet service can also be modified. The default is 23. 23

SSH
Using the SSH Service Enable/Disable function, you can disable the Values (port)
SSH service (Port 22) from running on the modem. The port used by
the SSH service can also be modified. The default is 22. 22

Web UI
The default web server port for the web based configuration tools used Values (selection)
in the modem is port 80 (http) and port 443 (HTTPS).
HTTP/HTTPS
Change as required, but keep in mind that if a non standard port is HTTP
used, it must be specified in a internet browser to access the unit. HTTPS
(example: http://192.168.168.1:8080).

Microhard Sh
Reserved for factory/internal use. Values (selection)
Enable / Disable

© Microhard 26
4.0 Configuration

4.1.4 System > Keepalive

The Keep alive tab allows for the configuration of the keep alive features of the LTECube. The LTECube
can check for activity on the Wireless Interface, The CLI (Command Line Interface), The WEBUI, and
ensure that they are working as expected. In the event that the LTECube does not detect activity on a
interface it will reboot to attempt to resolve any issues that may have occurred.

Image 4-1-5: Carrier > Keepalive

Keepalive
Enable or Disable the keep alive functions of the modem. If it is Values (Selection)
disabled, the user can configure the Traffic Check separately. The unit
will monitor traffic on the Cell interface. Enable / Disable

Traffic Watchdog
The Traffic Watchdog is available when the keepalive option above is Values (Selection)
disabled. The Traffic Watchdog simply monitors that there is activity of
the cellular interface, regardless of whether there is network Enable / Disable
connectivity or not, and reboots at the specified interval if no activity is
detected.

Traffic Check
Monitors traffic on the Cell interface. If the LTECube detects that there Values (Selection)
is no activity it will attempt a ICMP, HTTP or DNS Lookup as
configured below to determine if service has been lost. Enable / Disable

CLI Activity
Monitors the activity of CLI. If the console isn't accessed within the Values (Selection)
certain period which is specified by Console Timeout in System-
Settings web page, the modem will send out the connection request. Enable / Disable

© Microhard 27
4.0 Configuration

Web UI Activity
Monitors the activity of Web UI. If the Web UI isn't accessed or Values (Selection)
refreshed within the certain period which is specified by Console
Timeout in System-Settings web page, the modem will send out the Enable / Disable
connection request.

Type
Once the connection is lost, the modem will send one of the requests Values (Selection)
to the remote host to determine the connection status. If the modem
fails to get the response, it will re-send the request within the seconds ICMP
specified by Keepalive Interval below: HTTP
DNS Lookup
ICMP: Send a "ping" request
HTTP: Send a "wget" request to a HTTP server
DNS Lookup: Send a "dslookup" request to a DNS server

Host Name
Specify a IP Address or Domain that is used to test the modems Values (IP or Domain)
connection. The modem will send out the connection requests to the
specified Host. 8.8.8.8

Keepalive Interval
The Interval value determines the frequency, or how often, the unit will Values (seconds)
send out PING messages to the Host. The LTECube will first attempt
to re-initialize the cellular model before performing a full system 300
reboot, thus the interval may be delayed by up to 120 seconds)

Keepalive Retry
The Keepalive Retry is the maximum number of connection failures Values (number)
such as “Host unreachable” the unit will attempt before the unit will
reboot itself to attempt to correct connection issues. The default 20
number is 20, and valid value is from 10 to 200.

© Microhard 28
4.0 Configuration

4.1.5 System > Maintenance

Firmware Upgrade

Occasional firmware updates may be released by Microhard Systems which may include fixes and/or new

Image 4-1-6: Maintenance > Firmware Upgrade

Erase Current Configuration

Check this box to erase the configuration of the LTECube unit during Values (check box)
the upgrade process. This will upgrade, and return the unit to factory
defaults, including the default IP Addresses and passwords. Not unchecked
checking the box will retain all settings during a firmware upgrade
procedure.

Firmware Image
Use the Browse button to find the firmware file supplied by Microhard Values (file)
Systems. Select “Upgrade Firmware” to start the upgrade process.
This can take several minutes. (no default)

Reset to Default

The LTECube may be set back to factory defaults by using the Reset to Default option under System >
Maintenance > Reset to Default. *Caution* - All settings will be lost!!!

© Microhard 29
4.0 Configuration

Backup & Restore Configuration

The configuration of the LTECube can be backed up to a file at any time using the Backup Configuration
feature. The file can the be restored using the Restore Configuration feature. It is always a good idea to
backup any configurations in case of unit replacement. The configuration files cannot be edited offline, they
are used strictly to backup and restore units.

Image 4-1-7: Maintenance > Reset to Default / Backup & Restore Configuration

Name this Configuration / Backup Configuration

Use this field to name the configuration file. The .config extension will automatically be added to the
configuration file.

Restore Configuration file / Check Restore File / Restore

Use the ‘Browse’ button to find the backup file that needs to be restored to the unit. Use the ‘Check
Restore File’ button to verify that the file is valid, and then the option to restore the configuration is
displayed, as seen above.

The Keep CARRIER Settings box can be selected before the restore process is started, if it is selected the
LTECube will retain the current carrier settings and not overwrite them with the settings contained in the
backup file.

The Keep IoT Settings box can be selected before the restore process is started, if it is selected the
LTECube will retain the current IoT settings and not overwrite them with the settings contained in the
backup file.

© Microhard 30
4.0 Configuration

4.1.6 System > Reboot

The LTECube can be remotely rebooted using the System > Reboot menu. As seen below a button
‘Reboot now’ is provided. Once pressed, the unit immediately reboots and starts its boot up procedure. The
LTECube can also be restarted on a regular basis by setting up a daily/weekly/monthly schedules.

Image 4-1-8: System > Reboot

Status
Use this option to enable or disabled schooled reboots. If enabled the Values (selection)
LTECube will reboot at the interval defined below.
Disable / Enable

Type
Schedule daily, weekly or monthly reboots. Setting up a reboot Values (selection)
schedule can help keep the modem connected to the cellular carrier
and prevent physically rebooting the modem if located at a remote Reboot Daily
destination. Reboot Weekly
Reboot Monthly

Days / Time
If set for weekly, days are counted from Sunday to Saturday (0 to 6), Values (selection)
and if set to monthly the days are counted 1 to 31. Multiple days can
be specified by separating with a comma ‘,’. 1,
Set the time of day (24hr clock) for which to reboot the device.

© Microhard 31
4.0 Configuration

4.2 Network

4.2.1 Network > Status

The Network Status display gives a overview of the currently configured network interfaces including the
Connection Type (Static/DHCP), IP Address, Net Mask, Default Gateway, DNS, and IPv4 Routing Table.

You can also view statistical information about the interfaces including Received (RX) and Transmitted
(TX) bytes and packets for each network interface.

Image 4-2-1: Network > Network Status

© Microhard 32
4.0 Configuration

4.2.2 Network > LAN

LAN Port Configuration

The LTECube features a RJ45 LAN port that can be used for connection of devices on a local network. By
default the LAN has a static IP Address assigned, 192.168.168.1. Also, by default the LAN is running a
DHCP server to provide IP Addresses to devices that are connected to the physical LAN port (directly or
via a switch).

Image 4-2-2: Network > Network LAN Configuration

LAN Add/Edit Interface

Network Interfaces can be added/edited. By default any additional interfaces added will automatically
assign IP addresses to connecting devices via DHCP.

DHCP: Dynamic Host

Configuration Protocol may
be used by networked
devices (Clients) to obtain
unique network addresses
from a DHCP server.

Advantage:
Ensures unique IP addresses
are assigned, from a central
point (DHCP server) within a
network.

Disadvantage: Image 4-2-3: Network > LAN Port Configuration

The address of a particular
device is not ‘known’ and is
also subject to change.
Spanning Tree (STP)
STATIC addresses must be
tracked (to avoid duplicate
use), yet they may be This option allows the LTE Cube to participate in the Spanning Tree Values (selection)
permanently assigned to a protocol with other devices to prevent local loops. By default this is
device. disabled. Off / On

Within any IP network, each

device must have its own
unique IP address.

© Microhard 33
4.0 Configuration

IGMP Snooping
This feature allows a network switch to listen in on the IGMP Values (selection)
conversation between hosts and routers. By listening to these
conversations the switch maintains a map of which links need which IP Enable
The factory default
multicast streams. Disable
network settings:

IP: 192.168.168.1 Connection Type

Subnet: 255.255.255.0
Gateway: 192.168.168.1 This selection determines if the LTECube will obtain an IP address Values (selection)
from a DHCP server on the attached network, or if a static IP address
will be entered. If a Static IP Address is chosen, the fields that follow DHCP
must also be populated. Static

IP Address
A SUBNET MASK is a bit
If ‘Static’ Connection Type is selected, a valid IPv4 Address for the Values (IP Address)
mask that separates the network being used must be entered in the field. If ‘DHCP’ is chosen
network and host (device) this field will not appear and it will be populated automatically from the 192.168.168.1
portions of an IP address. DHCP server.
The ‘unmasked’ portion
leaves available the
information required to
identify the various devices
on the subnet.
Netmask
If ‘Static’ Connection Type is selected, the Network Mask must be Values (IP Address)
entered for the Network. If ‘DHCP’ is chosen this field will not appear
and it will be populated automatically from the DHCP server. 255.255.255.0

DNS Mode
If the Connection Type is set to DHCP, you can use Auto for the DNS Values (selection)
Within any IP network, each
Mode and a DNS server will automatically be defined. If the connection
device must have its own type is set as static, DNS servers can be manually specified. Auto
unique IP address. Manual

Primary DNS / Secondary DNS

Set the primary and alternate DNS (Domain Name Server) for use by Values (selection)
devices on the LAN port, if required.
Auto
Manual

© Microhard 34
4.0 Configuration

LAN DHCP

A LTECube may be configured to provide dynamic host control protocol (DHCP) service to all attached
devices. By default the DHCP service is enabled, so devices that are connected to the physical Ethernet
LAN ports will be assigned an IP by the LTECube. The LAN DHCP service is available for each interface,
and is located in the add/edit interface menus.

Image 4-2-4: Network > DHCP Server

DHCP Server
The option is used to enable or disable the DHCP service for devices Values (selection)
connected to the LAN Port(s).
Prior to enabling this service, Enable / Disable
verify that there are no other
devices - either wired (e.g.
LAN) or wireless with an
active DHCP SERVER
Start IP Address
service. (The Server issues
IP address information at the
request of a DHCP Client,
Select the starting address DHCP assignable IP Addresses. The first Values (IP Address)
octets of the subnet will be pre-set based on the LAN IP configuration,
which receives the
information.) and can not be changed. 192.168.168.100

Number of Address
Set the maximum number of IP addresses that can be assigned by the Values (integer)
LTECube.
150

Lease Time
The DHCP lease time is the amount of time before a new request for a Values (minutes)
network address must be made to the DHCP Server.
720

Alternate Gateway
Specify an alternate gateway for DHCP assigned devices if the default Values (IP Address)
gateway is not to be used.
(IP Address)

© Microhard 35
4.0 Configuration

Preferred DNS Server

Specify a preferred DNS server address to be assigned to DHCP Values (IP Address)
devices.
DNS: Domain Name Service (IP Address)
is an Internet service that
translates easily-
remembered domain names
into their not-so-easily-
remembered IP addresses.
Alternate DNS Server
Being that the Internet is Specify the alternate DNS server address to be assigned to DHCP Values (IP Address)
based on IP addresses, devices.
without DNS, if one entered
the domain name (IP Address)
www.microhardcorp.com (for
example) into the URL line of
a web browser, the website
‘could not be found’).
WINS/NBNS Servers
Enter the address of the WINS/NBNS (NetBIOS) Server. The WINS Values (IP/Domain)
server will translate computers names into their IP addresses, similar
to how a DNS server translates domain names to IP addresses. (no default)

WINS/NBT Node Type

Select the method used to resolve computer names to IP addresses. Values (selection)
Four name resolution methods are available:
B-node: broadcast none
P-node: point-to-point b-node
M-node: mixed/modified p-node
H-node: hybrid m-node
h-node

© Microhard 36
4.0 Configuration

4.2.3 DHCP (MAC Binding)

In some applications it is important that specific devices always have a predetermined IP address. This
menu allows for MAC Address binding to a IP Address, so that whenever the device that has the specified
MAC address, will always get the selected IP address from the DHCP service. In this situation, all attached
(wired or wireless) devices can all be configured for DHCP, but still get a known IP address.

Image 4-2-5: Network > MAC Address Binding

Name
The name field is used to give the device a easily recognizable name. Values (characters)
(no default)

MAC Address
Enter in the MAC address of the device to be bound to a set IP Values (MAC Address)
address. Set the IP Address in the next field. Must use the format:
AB:CD:DF:12:34:D3. It is not case sensitive, but the colons must be (no default)
present.

IP Address
Enter the IP Address to be assign to the device specified by the MAC Values (IP Address)
address above.
(minutes)

Static Addresses
This section displays the IP address and MAC address currently assigned through the DCHP service, that
are bound by it’s MAC address. Also shown is the Name, and the ability to remove the binding by clicking
“Remove _______”.

Active DHCP Leases

This section displays the IP Addresses currently assigned through the DCHP service. Also shown is the
MAC Address, Name and Expiry time of the lease for reference. The ‘Release All’ button terminates all
active leased and requires all connected devices to request new network information (IP/Subnet/etc)

© Microhard 37
4.0 Configuration

4.2.4 Network > DDNS

Unless a carrier issues a Static IP address, it may be desirable to use a Dynamic DNS (DDNS) service to
track dynamic IP changes and automatically update DNS services. This allows the use of a constant
resolvable host name for the LTECube.

Image 4-2-6: Carrier > Traffic Watchdog

DDNS Status
This selection allows the use of a Dynamic Domain Name Server Values (Selection)
(DDNS), for the LTECube.
Enable
Disable

Network
If the LTECube is using a wired WAN (ISP) as well as a Cellular Values (Selection)
carrier, specific which will use the DNS service.
Auto
Carrier

Periodic Update
When the LTECube powers up and comes online it will report any IP Values (Selection)
Address changes to the selected DNS service. Additionally the
LTECube can periodically update the service as configured. 5 minutes
15 minutes
Some Dynamic DNS service providers do not allow periodic updates, 60 minutes
or updates for the same IP address. Please review your chosen 4 hours
service providers policy before enabling this feature. 8 hours
24 hours

Service
This is a list of supported Dynamic DNS service providers. Free and Values (selection)
premium services are offered, contact the specific providers for more
information. changeip ovh
dyndns regfish
eurodyndns tzo
Hn Zoneedit
Noip Customized
Ods DMSmadeEasy

© Microhard 38
4.0 Configuration

User Name / Password

Enter a valid user name and password for the DDNS service selected Values (characters)
above.
(none)

Host
This is the host or domain name for the LTECube as assigned by the Values (domain name)
DDNS provider. Use the provided button to query the server (if
configured correctly) (none)

URL
This field appears when “custom dns” is selected. Values (characters)
How to fill URL: (none)
Use placeholder ${user} for username; ${pwd} for password; ${host}
for hostname; ${ip} for IP address.
eg: http://${user}:${pwd}@exampleddns.com/update?
hostname=${host}&myip=${ip}

© Microhard 39
4.0 Configuration

4.2.5 Network > Routes

Static Routes Configuration

It may be desirable to have devices on different subnets to be able to talk to one another. This can be
accomplished by specifying a static route, telling the LTECube where to send data.

Image 4-2-7: Network > Routes

Name
Routes can be names for easy reference, or to describe the route Values (characters)
being added.
(no default)

Destination Subnet
Enter the network IP address for the destination subnet. Values (IP Address)
(192.168.168.0)

Gateway
Specify the Gateway used to reach the network specified above. Values (IP Address)
192.168.168.1

Netmask
Enter the Netmask for the destination network. Values (IP Address)
255.255.255.0

© Microhard 40
4.0 Configuration

Metric
In some cases there may be multiple routes to reach a destination. Values (Integer)
The Metric can be set to give certain routes priority, the lower the
metric is, the better the route. The more hops it takes to get to a 255.255.255.0
destination, the higher the metric.

Interface
Define the exit interface. Is the destination a device on the LAN, LAN1 Values (Selection)
(If physical WAN port is bridged as an independent LAN), 3G/4G
(cellular), USB or the WAN? LAN / Carrier / GRE / None

© Microhard 41
4.0 Configuration

4.2.6 Network > VRRP

The LTECube when paired with other VRRP enabled devices (another LTECube or compatible devices)
can provide redundant internet access for LAN devices by using VRRP (Virtual Router Redundancy
Protocol) as illustrated below. If a connected device needs to access the internet it will use whichever
virtual router has the highest priority, if that device is not available the next router with the higher priority
will router the traffic.

Internet

LTECube VRRP Router

LAN: 192.168.220.11 LAN: 192.168.220.12

Virtual Router IP:

192.168.220.211

PC/LAN Device
LAN: 192.168.220.50
Gateway: 192.168.220.211
Switch

Image 4-2-8: Network > VRRP

VRRP Status
Enable or disable the VRRP service on the LTECube. To change Values (Selection)
settings the VRRP service must be disabled (then submitted) and then
re-enabled. Enable / Disable

Virtual Router IP
This is the IP Address of the virtual router, this must be the same on all Values
devices participating in VRRP. This is the IP that any attached LAN
PC/device would use as its default gateway. 192.168.220.211

© Microhard 42
4.0 Configuration

Virtual Router ID
This is the Router ID. Each router/ participating in VRRP should have Values
a router ID to distinguish between them.
2

Router Priority
This is the Router priority. This number to assigned to each router to Values
determine which router(s) will be used first or as the primary. The
higher the ID, the higher the priority. 150

4.2.7 Network > Ports

The Network > Ports menu can be used to determine the characteristics of the physical Ethernet interfaces
on the LTECube. As seen below the Mode (Auto/Manual), Auto-Negotiation, Speed (10/100Mbit/s) and the
Duplex (Full/Half) can all be configured on the LTECube.

Image 4-2-9: Network > Ports

© Microhard 43
4.0 Configuration

4.2.8 Network > Bandwidth

The LTECube features Bandwidth Throttling, which allows the upload/download of connected networks/
users data speeds to be limited to a specified value. Network Bandwidth Throttling can be implemented by
each physical Ethernet interface as seen in the image below.

Image 4-2-10: Network > Bandwidth Throttling

Rule Name
The rule name is used as a reference to be able to help identify which Values (chars)
interface or network is attached to the affected network interface.
rule1

Network
Select the physical interface to be affected by the Bandwidth Throttling Values (selection)
as defined below.
(varies)

Upload Bandwidth Enable

Enable or disable uploading on the specified interface. This prevent Values (selection)
data from being uploaded to a server. (i.e uploading/sending videos or
other files to a server). Enable / Disable

Upload Bandwidth
Set the data limit (speed) for file uploads if uploads have been allowed Values (kbps)
using the Upload Bandwidth Enable.
10000

© Microhard 44
4.0 Configuration

Download Bandwidth Enable

Enable or disable downloading on the specified interface. This prevent Values (chars)
data from being downloaded from a server. (i.e downloading files,
internet browsing etc). Enable / Disable

Download Bandwidth
Set the data limit (speed) for file downloads if downloads have been Values (kbps)
allowed using the Download Bandwidth Enable.
30000

4.2.9 Network > Device List

The Network > Device List shows the current ARP table for the network adapters. The MAC address and
IP address are shown, however not only DHCP assigned devices are listed in the device list, any devices,
even those statically assigned, that are connected through the local network interface (RJ45) are
displayed, including those connected through a hub or switch.

Image 4-2-11: Network > Device List

© Microhard 45
4.0 Configuration

4.2.10 Network > Cloud Filter

The LTECube provides Cloud based content filtering and security using the third-party service by Open
DNS. OpenDNS is a service which offers free or premium DNS services with added security, phishing
protection and optional, advanced content filtering. To get started with OpenDNS an account must first be
created and activated with OpenDNS by visiting their website.

Image 4-2-12: Network > Cloud Filtering

OpenDNS Cloud Filter

Enable or Disable the OpenDNS cloud based filtering & security. Values (selection)
Enable / Disable

Disable Bypassing OpenDNS

If enabled all clients connected through the LTECube will be forced to Values (selection)
use OpenDNS and is subject to any and all content filtering and
security, to prevent circumvention. Enable / Disable

Status
When Cloud Filter is enabled, this status will be refreshed every 30 Values (selection)
seconds, showing the OpenDNS status. For OpenDNS to be active,
the status must be green and show "Connected to OpenDNS". Enable / Disable

User Name / Password

Enter the user name and password for the OpenDNS account that was Values (selection)
specified during registration and setup of the service.
Enable / Disable

© Microhard 46
4.0 Configuration

4.2.13 Network > MultiWAN

MultiWAN is used to manage the primary data connection used by the LTECube. The LTECube can use
the WIFI connection, when configured in CLIENT mode, as the primary or secondary connection. The
LTECube can provide automatic failover services, switching the connection (or default route) used for
outside data.

Image 4-2-16: Network > MultiWAN

MultiWAN Enable
Enable or disable the MultiWAN service on the LTECube. To use Values (selection)
MultiWAN, the WIFI must be configured as a Client & bound to the
WIFI interface. Enable / Disable

Primary WAN
Define which connection is the primary network/internet connection for Values (selection)
the LTECube.
WIFI Client | Carrier Network

Second WAN
Select which WAN connection is the secondary connection. When a Values (selection)
failure of the main WAN occurs this will be the first alternative.
Generally this will be the cellular connection. WIFI Client | Carrier Network

© Microhard 47
4.0 Configuration

Health Monitor Interval

This is the frequency at which the LTECube will send ICMP packets to Values (seconds)
the defined host to determine if the interface has failed.
20

Switch Notification
It is possible for the LTECube to send out a notification when the Values (selection)
MultiWAN has switched its available connection and is routing data
through an alternate interface. Disable / Email / SMS / Both

Failover Settings (Same settings for WAN, WIFI Client and Carrier)

Type
Select the type of failover detection to be used. By default ICMP is Values (selection)
used to ping a specified address(s), a DNS Lookup can also be
selected. ICMP / DNS Lookup

Host Name
Up to three(3) reachable addresses can be specified to test for link Values (Address)
health at the frequency specified above for the Health Monitor Interval.
8.8.8.8
A test button is provided to ensure that reachable address have been 4.2.2.1
entered and that there are no errors. 208.67.222.222

Advanced+ (Only shown if selected)

Ping Mode
The Ping mode allows for the selected hosts to be pinged either Values (seconds)
Sequentially or Simultaneously. This option is only displayed when the
failover mode is set to ICMP. 3

ICMP Timeout
This is the amount of time the Health Monitor will wait for a response Values (seconds)
from the ICMP Host (when type is configured as ICMP).
3

Attempts Before Failover

This is the number of attempts the LTECube will attempt to reach the Values (selection)
IMCP host before going into failover and switching WAN interfaces.
1, 3, 5, 10, 15, 20

© Microhard 48
4.0 Configuration

Attempts Before Recovery

The LTECube will continue to monitor the failed interface, even after Values (selection)
failover has occurred. This defines the number of successful attempts
required before recovering the failed interface. 1, 2, 5, 10, 15, 20

Recovery Immediate Mode / Wait

Once the preferred connection is again deemed available, it can be Values (selection)
specified to wait a configurable amount of time before restoring the
connection.

© Microhard 49
4.0 Configuration

4.3 IPv6

4.3.1 IPv6 > Status

The IPv6 Status window provides complete overview information related to the IPv6 portion of the
LTECube. A variety of information can be found here, such as Network Status for interfaces configured for
IPv6. Information about the IPv6 DNS services, active DHCPv6 Leases and the current IPv6 Routing Table
can all be found on the IPv6 > Status window.

Image 4-3-1: IPv6 > Status

© Microhard 50
4.0 Configuration

4.3.2 IPv6 > Setup

The IPv6 setup windows provides the options required to setup IPv6 on the LTECube on the LAN
interface.

Image 4-3-2: IPv6 > Setup

IPv6 Status
Enable or Disable IPv6 on the LTECube. When enabled the Values (Selection)
configuration option appear below.
Enable / Disabled

Upstream Configuration: WAN6

Enable IPv6 on network

Select the physical interface of WAN6. Values (Selection)
Carrier

© Microhard 51
4.0 Configuration

WAN6 Connection Method

Select how and in what format the WAN6 interface defines the Values (Selection)
connection information.
DHCPv6 Client
Static Address

Local IPv6 Address for WAN6

When the WAN6 Connection Method is set to Static Address, here is Values (Address)
where the local WAN6 IP Address is defined.
(no default)

IPv6 Gateway Address

When the WAN6 Connection Method is set to Static Address, here is Values (Address)
where the IPv6 Gateway is defined.
(no default)

Primary Custom DNS Server

When the WAN6 Connection Method is set to Static Address, enter the Values (Address)
address for the primary custom DNS server.
(no default)

Secondary Custom DNS Server

When the WAN6 Connection Method is set to Static Address, Enter Values (Address)
the address for the secondary custom DNS server.
(no default)

Prefix for downstream network

IPv6 prefix for downstream

Prefix address for distribution to LAN downstream interface. If the Values (Address)
prefix length > 48 the subnet ID will be ignored for this prefix.
(no default)

IPv6 ULA-prefix
Modify the IPv6 ULA (Unique Local Address)-prefix here. If the prefix Values (Selection)
length > 48 the subnet ID will be ignored for this prefix.
Fd87:4588:5c48::/48

© Microhard 52
4.0 Configuration

LAN : Downstream Configuration

Prefix Length
Prefix size used for assigned prefix to the interface. For example 64 Values (length)
will assign /64-prefixes.
64

Subnet ID
Set the desired Subnet ID. If the Subnet ID is not set an arbitrary ID Values (characters)
will be chosen.
(no default)

RA & DHCPv6 Management Mode

Set the Router Advertisement & Management mode for the LAN. Values (selection)
SLAAC Only
SLAAC + DHCPv6
DHCPv6 Only

Router Advertisement-Service
Select the Router Advertisement-Service for the LAN. Values (selection)
Server Mode
Relay Mode

Override default route

Set the RA (Router Advertisements) Override for the default route. Values (selection)
Default
Ignore no public address
Ignore all

RA Lifetime
The amount of RA Lifetime given for the use of the IP address, from Values (seconds)
1800 to 9000 (seconds).
1800

DHCPv6 Service
Select the DHCPv6-Service mode for the LAN. Values (Selection)
Server Mode
Relay Mode

© Microhard 53
4.0 Configuration

Primary Announced DNS server

Set the announced primary DNS server details here. Values (Address)
(No default)

Secondary Announced DNS server

Set the announced secondary DNS server details here. Values (Address)
(No default)

NDP-Proxy
Select the NDP-Proxy mode for the LAN. Values (Selection)
Disabled
Relay Mode

© Microhard 54
4.0 Configuration

4.3.3 IPv6 > Firewall6

The IPv6 Firewall6 window allows the configuration of the firewall on the interfaces that are setup for IPv6.
The current Firewall for IPv6 can be viewed, changed and enabled/disabled under the Traffic Rules Status
summary of all current firewall rules.

Image 4-3-3: IPv6 > Firewall6

Traffic Rules Configuration

Rule Name
The rule name is simply a text identifier to label the corresponding rule Values (Characters)
for reference.
(varies)

Action
The Action is used to define how the rule handles the connection Values (Selection)
request.
Accept
ACCEPT will allow a connection, while REJECT (error) and DROP Drop
(quietly dropped), will refuse connections. Reject

Address family
Select if the rule applies only to IPv6. Values (Selection)
IPv6 only

© Microhard 55
4.0 Configuration

Protocol
The protocol field defines the transport protocol type controlled by the Values (Selection)
rule.
TCP
UDP
TCP+UDP
ICMP
Protocol 41
ALL

Enable
Enables the specified IPv6 Firewall Rule. Values (Checkbox)
Checked

Source Zone
Specify the source zone/interface. Values (Selection)
lan zone (Covered networks: LAN)
wan2 zone (Covered networks: Carrier)
any zone
none

Source Port
Specify the source port(s). Multiple ports can be specified as 80 443 Values (Port)
465. Port range can be specified as 100:200 format.

(no default)

Destination Zone
Specify the destination zone/interface. Values (Selection)
lan zone (Covered networks: LAN)
wan2 zone (Covered networks: Carrier)
any zone
this device (input)

Destination Port
Specify the destination port(s). Multiple ports can be specified as 80 Values (Port)
443 465. Port range can be specified as 100:200 format.

(no default)

© Microhard 56
4.0 Configuration

4.3.4 IPv6 > Route6

It may be desirable to have devices on different subnets to be able to talk to one another. This can be
accomplished by specifying a static route, telling the LTECube where to send data.

Image 4-3-4: IPv6 > Route6

Target
Enter the target IPv6 address or network CIDR. Values (IP Address)
(no default)

IPv6-Gateway
Specify the IPv6 Gateway used to reach the network specified above. Values (IP Address)
(no default)

Metric
Enter the metric for the static route. Values
0

Interface
Select the interface to which to send the data intended for the target Values (selection)
specified.
LAN
Carrier
none

© Microhard 57
4.0 Configuration

4.4 Carrier

4.4.1 Carrier > Status

The Carrier Status window provides complete overview information related to the Cellular Carrier portion of
the LTECube. A variety of information can be found here, such as Activity Status, Network (Name of
Wireless Carrier connected), Data Service Type (WCDMA/HSPA/HSPA+/LTE etc), Frequency band,
Phone Number etc.

Image 4-4-1: Carrier > Status

Not all statistics parameters displayed are applicable.

The Received and Transmitted bytes and packets indicate the respective amount of data which has been
moved through the radio.

The Error counts reflect those having occurred on the wireless link.

© Microhard 58
4.0 Configuration

4.4.2 Carrier > Settings

The parameters within the Carrier Configuration menu must be input properly; they are the most basic
requirement required by your cellular provider for network connectivity.

Image 4-4-2: Carrier > Settings

Carrier Status
Carrier Status is used to Enable or Disable the connection to the Values (Selection)
Cellular Carrier. By default this option is enabled.
Enable / Disable

MTU Size
Allows a user to specify the MTU size for custom applications. In most Values
cases this will be left blank and the system will determine the best
value. (blank)

© Microhard 59
4.0 Configuration

IP-Passthrough
IP pass-through allows the Carrier IP address to be assigned to the Values (Selection)
device connected to the LAN port. In this mode the LTECube is for the
most part transparent and forwards all traffic to the device connected Disable
to the selected Ethernet port except that listed below: Ethernet

• The WebUI port (Default Port:TCP 80), this port is retained for
remote management of the LTECube. This port can be changed to a
different port under the System > Services Menu.

• The SNMP Listening Port (Default Port: UDP 161).

The firewall/rules must be configured to allow traffic, all incoming

carrier traffic is blocked by default.

Lease Time
When IP-Passthrough is enabled, this field appears where you can Values (minutes)
adjust the DHCP lease time for IP-Passthrough.
2

Virtual IP Address
When in IP passthrough mode the local IP is not available, thus the Values (IP Address)
virtual IP can be used for local configuration.
192.168.10.1

© Microhard 60
4.0 Configuration

Settings

Data Roaming
This feature allows the disabling or enable of data roaming. When data Values (Selection)
roaming is enabled the modem will be allowed to use data when in
roaming status. It is not recommended to allow roaming unless the Enable / Disable
appropriate data plans are in place.

Carrier Operator
In some cases, a user may want to lock onto a certain carrier. There Values (Selection)
are four options to choose from: Auto, SIM based, Manual and Fixed.
Auto
• Auto will allow the unit to pick the carrier automatically. Data roaming is Based on SIM
permitted.
• SIM based will only allow the unit to connect to the network indicated by the Manual
SIM card used in the unit. Fixed
• Manual will scan for available carriers and allow a user to select from the
available carriers. It takes 2 to 3 minutes to complete a scan.
• Fixed allows a user to enter the carrier code (numerical) directly and then the
unit will only connect to that carrier.

Technologies Mode
Select the valid types of Carrier connections allowed. For example, If set Values (selection)
to UMTS only, the LTECube will only allow connections to 3G/HSPA
related technologies, and not allow the device to connect to LTE WCDMA Only
technologies. LTE Only
TD-SCDMA Only
UMTS Only
CDMA Only
HDR Only
CDMA and HDR Only

SIM Type
Select the SIM profile if your SIM Card is being used on one of the Values (Selection)
Carriers listed. Otherwise select the Auto Detect option.
Auto Detect
General/ATT Mode
Verizon Mode

APN (Access Point Name)

The APN is required by every Carrier in order to connect to their Values (characters)
networks. The APN defines the type of network the LTECube is
connected to and the service type. Most Carriers have more than one auto
APN, usually many, dependent on the types of service offered.

Auto APN (default) may allow the unit to quickly connect to a carrier, by cycling through a predetermined
list of common APN’s. Auto APN will not work for private APN’s or for all carriers.

© Microhard 61
4.0 Configuration

Advanced+

SIM Pin
The SIM Pin is required for some international carriers. If supplied and Values (characters)
required by the cellular carrier, enter the SIM Pin here.
(none)

Authentication
Sets the authentication type required to negotiate with peer. Values (Selection)
PAP - Password Authentication Protocol. PAP
CHAP - Challenge Handshake Authentication Protocol. CHAP
No Auth
Only required if the carrier requires a User Name and Password.

User Name

A User Name may be required for authentication to a remote peer. Values (characters)
Although usually not required for dynamically assigned IP addresses
from the wireless carrier. Varies by carrier. Carrier/peer dependent

Password
Enter the password for the user name above. May not be required by Values (characters)
some carriers, or APN’s
Carrier/peer dependent

Network+

PDP Type
IPv6 support is related to the LTECube’s configuration and carrier Values (selection)
network.
IPV4 and IPV6
IP

Use Remote DNS

If enabled the LTECube with use the DNS server as specified Values (selection)
automatically by the service provider.
Enable / Disable

Default Route
Use this interface as the default route for all outbound traffic unless Values (Selection)
specified in the Network > Routes table.
Yes / No

DNS-Passthrough
When enabled DNS-Passthrough will pass on the WAN assigned DNS Values (Selection)
information to the end device.
Enable / Disable

© Microhard 62
4.0 Configuration

4.4.3 Carrier > SMS

SMS Command History

The SMS menu allows a user to view the SMS Command History and view the SMS messages on the SIM
Card.

Image 4-4-3: SMS > SMS Command History

4.4.4 Carrier > SMS Config

SMS messages can be used to remotely reboot or trigger events in the LTECube. SMS alerts can be set
up to get SMS messages based on system events such as Roaming status, RSSI, Ethernet Link Status or
IO Status.

System SMS Command

Image 4-4-4: SMS > SMS Configuration

© Microhard 63
4.0 Configuration

Status
This option allows a user to enable or disable to use of the following Values (Selection)
SMS commands to reboot or trigger events in the LTECube:
Enable / Disable

MSC#REBOOT Reboot system MSC#EURD0 trigger event report0

MSC#NMS Send NMS UDP Report MSC#EURD1 trigger event report1
MSC#WEB Send web client inquiry MSC#EURD2 trigger event report2
MSC#APN=apn,username,password MSC#EURD3 trigger event report3

Set Phone Filter

If enabled, the LTECube will only accept and execute commands Values (Selection)
originating from the phone numbers in the Phone Filter List. Up to 6
numbers can be added. Enable / Disable

System SMS Forward

Image 4-4-5: SMS > System SMS Forward

Status
SMS Messages received by the LTECube can be forwarded to another Values (Selection)
number. Messages can be saved or deleted from the SIM after
forwarding. Disable / Enable

Forward Phone Number

Enter the number where SMS messages received by the LTECube will Values (Selection)
be forwarded.
(no default)

Matched Sender / Matched Prefix

Use the Matched Sender and Matched Prefix to filter messages to be Values (characters)
forwarded. Matched sender allows only messages received from
certain number(s). Matched prefix only passes on messages that (no default)
match a specific prefix (first part of message).

© Microhard 64
4.0 Configuration

4.4.5 Carrier > Data Usage

The Data Usage tool on the LTECube allows users to monitor the amount of cellular data consumed. Since
cellular devices are generally billed based on the amount of data used, alerts can be triggered by setting
daily and/or monthly limits. Notifications can be sent using SMS or Email, allowing a early warning if
configurable limits are about to be exceeded. The usage data reported by the Data Usage Monitor may not
match the data reported by the carrier, but it gives the users an idea of the bandwidth consumed by the
LTECube.

Image 4-4-7: Carrier > Data Usage

Status
If enabled the LTECube will track the amount of cellular data consumed. If Values (selection)
disabled, data is not recorded, even in the Current Data Usage display.
Disable
Enable

© Microhard 65
4.0 Configuration

Monthly/Daily Over Limit

Select the notification method used to send alerts when daily or monthly Values (selection)
thresholds are exceeded. If none is selected, notifications will not be sent,
but data usage will be recorded for reference purposes.
None
Send Notice SMS
Send Notice Email
Both SMS & Email

Image 4-4-8: Data Usage > SMS Config

Monthly/Daily Data Unit

Select the data unit to be used for data usage monitoring. Values (selection)
Bytes / K Bytes / M Bytes
G Bytes

Data Limit
Select the data limit for the day or month, used in connection with the data Values (1-65535)
unit is the previous field. If you want to set the limit to 250 Mbytes, select M
Bytes for the data unit, and 250 for the data limit.
500

Period Start Day

For Monthly tracking, select the day the billing/data cycles begins. On this Values (1-31)
day each month the LTECube will reset the data usage monitor numbers.
1 (Day of Month)

Additional Notice 1/2

Up to two (2) additional notices can be sent based on a percentage (10- Values (10-500%)
500%) of the threshold value.
(none)

Phone Number
If SMS is selected as the notification method, enter the phone number to Values (phone)
send any SMS messages generated when the data usage exceeds the
configured limits.
+1403

© Microhard 66
4.0 Configuration

Image 4-4-9: Data Usage > Email Config

Mail Subject
If Email is selected as the notification method, enter the desired email Values (string)
subject line for the notification email sent when daily and/or monthly usage
limits are exceeded. Daily/Monthly Data Usage
Notice

Mail Server(IP/Name)
If Email is selected as the notification method, enter the SMTP server Values (xxx:port)
details for the account used to send the Email notifications. Domain or IP
address with the associated port as shown.
smtp.gmail.com:465

Username
If Email is selected as the notification method, enter the username of the Values (username)
Email account used to send Emails.
@gmail.com

Password
If Email is selected as the notification method, enter the password of the Values (string)
Email account used to send Emails. Most email servers require
authentication on outgoing emails.
***

Authentication
If Email is selected as the notification method, enter the password of the Values (selection)
Email account used to send Emails. Most email servers require
authentication on outgoing emails.
None
SSL/TLS
STARTTLS
SSL/TLS + STARTTLS

Mail Recipient
Enter the email address of the individual or distribution list to send the Values (xx@xx.xx)
email notification to.
host@

© Microhard 67
4.0 Configuration

Data Usage History

The LTECube provides a Odometer that shows the total data used by the LTECube. You can also click on
the More link to get a data usage history summary as seen below.

Image 4-3-10: Data Usage > Data Usage Odometer

© Microhard 68
4.0 Configuration

4.5 Wireless (WIFI)

4.5.1 Wireless > Status

The LTECube-CAT4-WIFI has integrated 802.11 b/g/n WIFI capabilities. This is a high power (1W)
enterprise grade wireless feature, that can support up to 200 clients.

The Status window gives a summary of all radio or wireless related settings and connections.

The General Status section shows the Wireless MAC address of the current radio, the Operating Mode
(Access Point, Client), the SSID being used, frequency channel information and the type of security used.

Traffic Status shows statistics about the transmitted and received data.

The LTECube shows information about all Wireless connections in the Connection Info section. The
Wireless MAC address, Noise Floor, Signal to Noise ratio (SNR), Signal Strength (RSSI), The transmit and
receive Client Connection Quality (CCQ), TX and RX data rates, and a graphical representation of the
signal level or quality.

Image 4-5-1: Wireless > Status

© Microhard 69
4.0 Configuration

4.5.2 Wireless > Radio1

Radio1 Phy Configuration

The top section of the Wireless Configuration allows for the configuration of the physical radio module. You
can turn the radio on or off, and select the channel bandwidth and frequency as seen below.

Image 4-5-2: Wireless > Radio Configuration

Radio
This option is used to turn the radio module on or off. If turned off Values (selection)
Wireless connections can not be made. The default is On.
On / Off

Mode
The Mode defines which wireless standard to use for the wireless Values (selection)
network. The LTECube supports 802.11/b/g/n modes as seen here.
Select the appropriate operating mode from the list. 802.11B ONLY
802.11BG
The options below are dependent and vary on the operating mode 802.11NG
chosen here.

Channel Bandwidth
Only appears when using 802.11b or b/g modes. Lower channel Values (selection)
bandwidths may provide longer range and be less susceptible to noise
but at the trade off of data rates. Higher channel bandwidth may 20MHz Normal Rate
provide greater data rates but will be more susceptible to noise and
shorter distance potentials.

© Microhard 70
4.0 Configuration

High Throughput Mode

Select HT20 for a 20MHz channel, or HT40 for a 40 MHz Channel. Values (selection)
The 40MHz channel is comprised of 2 adjacent 20MHz channels and
the + and—designate to use the higher or lower of the adjacent HT20
channels. HT40-
HT40+
Force HT40-
Advanced Capabilities (Only shown if box is checked) Force HT40+

MPDU Aggregation (Enable/Disable) - Allows multiple data frames to be sent in a single transmission
block, allowing for acknowledging or retransmitting if errors occur.

Short GI (Enable/Disable) - GI (guard interval) is the time the receiver waits for any RF reflections to settle
before sampling data. Enabling a short GI (400ns) can increase throughput, but can also increase the error
rate in some installations.

HT Capabilities Info - TX-STBC RX-STBC1 DSSS_CCK-40

Maximum AMSDU (byte) - 3839
Maximum AMPDU (byte) - 65535

Channel-Freq
The Channel-Freq setting allows configuration of which channel to Values (selection)
operate on, auto can be chosen where the unit will automatically pick a
channel to operate. If a link cannot be established it will try another Auto
channel. Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz

TX Power
This setting establishes the transmit power level which will be Values (selection)
presented to the antenna connector at the rear of the LTECube.
Unless required, the Tx Power should be set not for maximum, but 7 dBm 19 dBm
rather for the minimum value required to maintain an adequate system 8 dBm 20 dBm
fade margin. 9 dBm 21 dBm
Refer to FCC (or as 10 dBm 22 dBm
otherwise applicable) 11 dBm 23 dBm
regulations to ascertain, 12 dBm 24 dBm
and not operate beyond,
the maximum allowable
13 dBm 25 dBm
transmitter output power 14 dBm 26 dBm
and effective isotropic 15 dBm 27 dBm
radiated power (EIRP). 16 dBm 28 dBm
17 dBm 29 dBm
18 dBm 30 dBm

© Microhard 71
4.0 Configuration

Wireless Distance
The Wireless Distance parameter allows a user to set the expected Values (meters)
distance the WiFi signal needs to travel. The default is 100m, so the
LTECube will assume that the signal may need to travel up to 100m so 100
it sets various internal timeouts to account for this travel time. Longer
distances will require a higher setting, and shorter distances may
perform better if the setting is reduced.

RTS Thr (256 ~ 2346)

Once the RTS Threshold defined packet size is reached, the system Values (selection)
will invoke RTS/CTS flow control. A large RTS Threshold will improve
bandwidth, while a smaller RTS Threshold will help the system recover On / OFF
from interference or collisions caused by obstructions.

Fragment Thr (256 ~ 2346)

The Fragmentation Threshold allows the system to change the Values (selection)
maximum RF packet size. Increasing the RF packet size reduces the
need to break packets into smaller fragments. Increasing the On / OFF
fragmentation threshold slightly may improve performance if a high
packet error rate is experienced.

© Microhard 72
4.0 Configuration

Radio1 Virtual Interface

The bottom section of the Wireless Configuration provides for the configuration of the Operating Mode of
the Wireless Interface, the TX power, Wireless Network information, and Wireless Encryption. The
LTECube can support multiple virtual interfaces. These interfaces provide different SSID’s for different
users, and can also be assigned to separate subnets (Network Interfaces) to prevent groups from
interacting.

Image 4-5-3: Wireless > Radio Configuration

Network
Choose between LAN or WAN for the Virtual Interface. If additional Values (selection)
Network Interfaces have been defined in the Network > LAN section,
the Interface name will also appear here. LAN
WAN
Etc..
(Additional Interfaces…)

Mode
Access Point - An Access Point may provide a wireless data Values (selection)
connection to many clients, such as stations, repeaters, or other
supported wireless devices such as laptops etc. Access Point
Client
If more than 1 Virtual Interface (more than 1 SSID) has been defined, Repeater
the LTECube can ONLY operate as a Access Point, and will be locked
into this mode.

Station/Client - A Station may sustain one wireless connection, i.e. to an Access Point.

Repeater - A Repeater can be connected to an Access Point to extend the range and provide a
wireless data connection to many clients, such as stations.

© Microhard 73
4.0 Configuration

TX bitrate
This setting determines the rate at which the data is to be wirelessly transferred.

The default is ‘Auto’ and, in this configuration, the unit will transfer data at the highest possible rate in
consideration of the receive signal strength (RSSI).

Setting a specific value of transmission rate has the benefit of ‘predictability’ of that rate, but if the RSSI
drops below the required minimum level to support that rate, communications will fail.

802.11 b/g 802.11n (HT20/HT40)

Auto Auto
1 Mbps (802.11b,g) mcs-0 (7.2/15) Mbps
2 Mbps (802.11b,g) mcs-1 (14.4/30.0) Mbps
5.5 Mbps (802.11b,g) mcs-2 (21.7/45.0) Mbps
11 Mbps (802.11b,g) mcs-3 (28.9/60.0) Mbps
6 Mbps (802.11g) mcs-4 (43.3/90.0) Mbps
9 Mbps (802.11g) mcs-5 (57.8/120.0) Mbps
12 Mbps (802.11g) mcs-6 (65.0/135.0) Mbps
18 Mbps (802.11g) mcs-7 (72.2/150.0) Mbps
24 Mbps (802.11g)
36 Mbps (802.11g)
48 Mbps (802.11g)
54 Mbps (802.11g)

ESSID Broadcast
Disabling the SSID broadcast helps secure the wireless network. Values (selection)
Enabling the broadcast of the SSID (Network Name) will permit others
to ‘see’ the wireless network and perhaps attempt to ‘join’ it. On / Off

AP Isolation
When AP Isolation is enabled wireless devices connected to this SSID Values (selection)
will not be able to communicate with each other. In other words if the
LTECube is being used as a Hot Spot for many wireless clients, AP On / Off
Isolation would provide security for those clients by not allowing
access to any other wireless device.

WMM
WiFi Multimedia (WMM) is a feature that enhances the quality of Values (selection)
service on a network by prioritizing data packets according to data
type. (Video, Voice, Best Effort, Background). On / Off

© Microhard 74
4.0 Configuration

SSID
All devices connecting to the LTECube in a given network must use Values (string)
the SSID of the LTECube. This unique network address is not only a
security feature for a particular network, but also allows other networks (MAC Address)
- with their own unique network address - to operate in the same
SSID: Service Set Identifier. area without the possibility of undesired data exchange between
The ‘name’ of a wireless
network. In an open wireless networks.
network, the SSID is
broadcast; in a closed system
it is not. The SSID must be
known by a potential client for Encryption Type
it to be able to access the
wireless network. The encryption types defines the type of security used for the Wireless Values (selection)
Interface, to join a network a device must know the correct password/
passphrase/key. Disabled
WPA (PSK)
Security options are dependent on the version type. This section WPA2 (PSK)
describes all available options. Export versions may not have all WPA+WPA2 (PSK)
optional available to meet regulatory requirements set government WPA Enterprise (RADIUS)
policies. WPA2 Enterprise (RADIUS)
WPA+WPA2 Enterprise (RADIUS)
Change the default value for
the Network Name to
something unique for your
network. Do this for an
added measure of security
WPA PSK
and to differentiate your
network from others which This is the password, or preshared key that is required by any device Values (string)
may be operating nearby. to connect to the wireless interface of the LTECube. It is strongly
recommended to always have a password defined, and changed from (serial number)
the factory default.

Show Password
Check this box to show the currently configured password for WPA/ Values (selection)
WPA2 encryption passphrase.
unchecked

RADIUS IP Address
If using Enterprise (RADIUS) encryption, enter the IP Address of the Values (IP Address)
RADIUS authentication server here.
(no default)

RADIUS Port
If using Enterprise (RADIUS) encryption, enter the port number of the Values (port)
RADIUS authentication server here.
(no default)

RADIUS Server Key

This is the password, or preshared key that is required by any device Values (selection)
to connect to the wireless interface of the LTECube. It is strongly
recommended to always have a password defined, and changed from 0123456789
the factory default.

© Microhard 75
4.0 Configuration

4.5.3 Wireless > HotSpot

The Wireless Hotspot configuration is used when providing public hotspot services and it is required to use
a server or web based authentication service to verify users, provide terms of use or other information

Image 4-5-4: Wireless > Hotspot Network Configuration

Hotspot Mode
Use this option to enable or disable the hotspot authentication service. Values (selection)
There are three different options for the Hotspot Mode:
Disable
Simple Internal - Display a simple text based terms of use or Simple Internal
statement to connected users.
Simple External - Display an external webpage Simple External
RADIUS/UAM - Use a 3rd Party Authentication service to RADIUS/UAM
authenticate and/or prompt users to agree to terms of
service.

UAM Login URL

If the Hotspot Mode, RADIUS/UAM is chosen, specify the hotspot URL Values
as given by your service provider. The address of the UAM Server, the
authentication portal. https://
customer.hotspotsystem.com/
customer/hotspotlogin.php

UAM Secret
If the Hotspot Mode, RADIUS/UAM is chosen, this is a secret Values
password between the Redirect URL and the Hotspot given by the
hotspot provider. hotsys123

© Microhard 76
4.0 Configuration

Hotspot Network Configuration

Hotspot Network
This field is used to specify which configured network is bonded to the Values
hotspot. Sub networks can be created in the Network > LAN menu,
which are dedicated to the hotspot devices. Varies
*The DHCP service for the network used should be turned off as all IP
address assignments will be made by the hotspot service provider.*

Network IP Address
Specify the IP Address of the Hotspot application. All hotspot clients Values
will get an IP address in the same network as the Hotspot.
192.168.182.0

Network Netmask
Specify the Netmask of the Hotspot application. All hotspot clients will Values
get an IP address in the same network as the Hotspot.
255.255.255.0

DNS Domain
Provide your service providers 1st DNS Server domain. Values
Key.chillispot.info

Primary DNS
Specify the Primary DNS server to be used by devices connected to Values
the Hotspot network.
208.67.222.222

Secondary DNS
Specify the Secondary DNS server to be used by devices connected Values
to the Hotspot network.
208.67.222.220

DHCP Start
When devices connect to the LTECube Wifi and Hotspot is enabled, Values
the Hotspot will assign the IP addresses to the connected devices,
select the starting range here. 3

DHCP End
When devices connect to the LTECube Wifi and Hotspot is enabled, Values
the Hotspot will assign the IP addresses to the connected devices,
select the ending range here. 250

© Microhard 77
4.0 Configuration

Hotspot Radius Configuration

Image 4-5-5: Wireless > Hotspot Radius Configuration

Radius NAS ID
This is the RADIUS name of your Hotspot as given by your Hotspot Values
Service Provider.
Microhard_1

Radius Server 1
As assigned by the Hotspot Service Provider, the name or IP address Values
of the primary RADIUS Server.
radius.hotspotsystem.com

Radius Server 2
As assigned by the Hotspot Service Provider, the name or IP address Values
of the alternate RADIUS Server.
radius2.hotspotsystem.com

Radius Auth Port

The Radius Authentication Port Number. The default is 1812. This is Values
provided by your Hotspot service provider.
1812

Radius Acct Port

The Radius Account Port Number. The default is 1813. This is Values
provided by your Hotspot service provider.
1813

Radius Secret
Also called a shared key, this is the RADIUS password assigned by Values
you Hotspot provider.
hotsys123

© Microhard 78
4.0 Configuration

Radius CoA UDP Port

Specify the Radius CoA UDP Port here. This information is supplied by Values (port)
the hotspot service provider.
3799

Radius Session Timeout

Specify the Radius Session Timeout. In seconds, 0 = disabled. Values (seconds)
3600

Radius Idle Timeout

Specify the Radius Idle Timeout. In seconds, 0 = disabled. Values (seconds)
900

© Microhard 79
4.0 Configuration

4.6 Firewall

4.6.1 Firewall > Summary

The Firewall Summary allows a user to see detailed information about how the firewall is operating. The
All, Filter, Nat, Raw, and Mangle options can be used to view different aspects of the firewall.

Image 4-6-1: Firewall > Status

© Microhard 80
4.0 Configuration

4.6.2 Firewall > General

The General Firewall settings allow users to enable or disable the firewall, and to decide which areas of the
modem to protect. The Firewall can also be reset to factory defaults from this area of the WebUI.

In a cellular device such as this, it is highly recommended to configure the firewall to protect any devices
connected to the modem, and to control data usage. This is especially important with units set up with a
public IP address as the modem is effectively on the public internet and is susceptible to a wide range of
threats which may severely impact the data usage. This can be avoided by blocking all Cellular traffic and
setting up specific rules to either open only used ports, or even restrict access to specific IP/networks.

Image 4-6-2: Firewall > General

Remote Management
For best practices and to
control data usage it is
critical that the firewall be Allow (checked) remote management of the LTECube from the Cellular Values (checkbox)
configured properly. side of using the WebUI on port 80(HTTP), and 443 (HTTPS). If disabled,
the configuration can only be accessed from the LAN (or WAN if enabled).. (checked)
It is recommended to block
all incoming Cellular traffic
and create rules to open
specific ports and/or use
ACL lists to limit incoming
Remote Access
connections.
When Blocked (unchecked) all requests originating from the Cellular side Values (checkbox)
will be blocked, unless specified otherwise in the Access Rules, MAC List,
IP List configurations. Access to ports 80 (HTTP) and 443 (HTTPS-if (unchecked)
enabled), is still available unless disabled in the Remote Management
option.

LAN Outgoing
When Remote Access is set
to ‘Allow’ the modem is
Allows (checked) or Blocks (unchecked) traffic from the LAN accessing the Values (checkbox)
open to anyone, this is not
Cellular connection unless specified otherwise using the Access Rules,
recommended as it may MAC, and IP List configuration. (checked)
impact data usage from
unwanted sources.
Anti-Spoof
The Anti-Spoof protection is to create some firewall rules assigned to the Values
external interface (Cellular) of the firewall that examines the source
address of all packets crossing that interface coming from outside. If the Enable / Disable
address belongs to the internal network or the firewall itself, the packet is
dropped.

© Microhard 81
4.0 Configuration

Packet Normalization
Packet Normalization is the normalization of packets so there are no Values
ambiguities in interpretation by the ultimate destination of the packet. The
scrub directive also reassembled fragmented packets, protecting some Enable / Disable
operating systems from some forms of attack, and drops TCP packets that
have invalid flag combinations.

© Microhard 82
4.0 Configuration

4.6.3 Firewall > Port Forwarding

The LTECube can be used to provide remote access to connected devices. To access these devices a
user must define how incoming traffic is handled by the LTECube. If all incoming traffic is intended for a
specific connected device, DMZ could be used to simplify the process, as all incoming traffic can be
directed towards a specific IP address.

In the case where there is multiple devices, or only specific ports need to be passed, Port forwarding is
used to forward traffic coming in from the WAN (Cellular) to specific IP Addresses and Ports on the LAN.
Port forwarding can be used in combination with other firewall features, but the Firewall must be enabled
for Port forwarding to be in effect. If Remote Access is blocked on the General Tab, additional rules and/or
IP Lists must be set up to allow the port forwarding traffic to pass through the firewall.

Image 4-6-3: Firewall > Port Forwarding

If DMZ is enabled and an
exception port for the WebUI
is not specified, remote
management will not be
possible. The default port for
remote management is TCP
80.

© Microhard 83
4.0 Configuration

DMZ Mode
Enable or disable DMZ. DMZ can be used to forward all traffic to the DMZ Values (selection)
Server IP listed below.
Disable / Enable

DMZ Server IP
Enter the IP address of the device on the LAN side of the LTECube where Values (IP Address)
all the traffic will be forwarded to.
192.168.100.100

Exception Ports
If the firewall is set to block
incoming traffic on the WAN Enter a exception port number(s) (range is XX:XX) that will NOT be Values (Port #)
and/or Carrier interfaces, forwarded to the DMZ server IP. Usually a configuration or remote
additional rules or IP/MAC
lists must be configured to
management port that is excluded to retain external control of the 0
allow desired traffic access.

Combined with Source NAT

Add an additional SNAT rule for port forwarding. It will modify the source IP Values (selection)
address of the incoming request to make the internal server respond to this
connection as a local request. No / Yes

Firewall Port Forwarding Configuration

Name
This is simply a field where a convenient reference or description is added Values (10 chars)
to the rule. Each Forward must have a unique rule name and can use up to
10 characters. Forward

Source
Select the source for the traffic. Values (selection)
Carrier

Protocol
Select the type of transport protocol used. For example Telnet uses TCP, Values (selection)
SNMP uses UDP, etc.
TCP / UDP / Both

External Ports
Port number(s) (for range format is start:stop) of the incoming request Values (Port #)
(from Cellular/WAN-side).
2000

© Microhard 84
4.0 Configuration

Internal Server IP
Enter the IP address of the intended internal (i.e. on LAN side of LTECube) Values (IP Address)
server. This is the IP address of the device you are forwarding traffic to.
192.168.168.2

Internal Ports
Target port number(s) (for range format is start:stop) of the internal server Values (Port #)
on the LAN IP entered above.
3000

Combined with Source NAT

Add an additional SNAT rule for port forwarding. It will modify the source IP Values (selection)
address of the incoming request to make the internal server respond to this
connection as a local request. No / Yes

© Microhard 85
4.0 Configuration

4.5.4 Firewall > MAC-IP List

MAC List configuration can be used to control which physical LAN devices can access the ports on the
LTECube, by restricting or allowing connections based on the MAC address. IP List configuration can be
used to define who or what can access the LTECube, by restricting or allowing connections based on the
IP Address/Subnet. MAC-IP List can be used alone or in combination with Remote Access Control to
provide secure access to the LTECube.

Image 4-5-4: Firewall > MAC-IP List

Firewall MAC List Configuration

Rule Name
The Rule Name field is required to give the rule a convenient name for Values (10 chars)
reference. Each rule must have a unique name, up to 10 characters in
length. mac1

Action
The Action is used to define how the rule handles the connection request. Values (selection)
ACCEPT will allow a connection, while REJECT (error) and DROP (quietly ACCEPT
dropped), will refuse connections. DROP
REJECT

© Microhard 86
4.0 Configuration

Network
Select the Network of the source device. For the LTECube this would be Values (selection)
either a device connected to the RJ45 LAN port or via WIFI.
LAN | WIFI

MAC Address
Specify the MAC Address to be added to the list. Must be entered in the Values (MAC Address)
correct format as seen above. Not case sensitive.
00:00:00:00:00:00

MAC Address Mask

Define the MAC Address bit mask if applicable. Operation AND will be Values (MAC Address)
applied to MAC Address and Mask.
(no default)

Target
Select the Target. Input is to access within the modem, while forward is to Values (selection)
access through the modem to another device.
Input | Forward | Both

Firewall IP List Configuration

Rule Name
The Rule Name field is required to give the rule a convenient name for Values (10 chars)
reference. Each rule must have a unique name, up to 10 characters in
length. ip1

Action
The Action is used to define how the rule handles the connection request. Values (selection)
ACCEPT will allow a connection, while REJECT (error) and DROP (quietly
dropped), will refuse connections. ACCEPT / DROP / REJECT

Source
Enter the specific zone that the IP List will apply to, Cellular, LAN, WAN or Values (Selection)
None (both).
LAN / Carrier

Source IP Address / Prefix

Match incoming traffic from the specified source subnet/prefix. An empty Values (IP Address)
prefix box indicates a single(/32) address.
0.0.0.0

© Microhard 87
4.0 Configuration

4.5.5 Firewall > Rules

Once the firewall is turned on, rules configuration can be used to define specific rules on how local and
remote devices access different ports and services. MAC List and IP List are used for general access, and
are applied before rules are processed.

It is highly recommended to block as much traffic as possible from the modem, especially when using a
public IP address. The best security would to be to allow traffic only from trusted IP addresses, and only
the specific ports being used, and block everything else. Not configuring the firewall and the firewall rules
correctly could result in unpredictable data charges from the cellular carrier.

Refer to Appendix D for an

example of how to set up a
firewall to block all
connections and then add
access to only specific IP’s
and Ports.

Appendix D: Firewall
Example

Image 4-5-5: Firewall > Rules

Rule Name
The rule name is used to identify the created rule. Each rule must have a Values (10 Chars)
unique name and up to 10 characters can be used.
rule1

Type
The type refers to the direction in terms of source and destination of the Values (selection)
traffic. The fields below will adjust accordingly.
Input
Output
Forward

Action
The Action is used to define how the rule handles the connection request. Values (selection)
ACCEPT will allow a connection, while REJECT (error) and DROP ACCEPT
(quietly dropped), will refuse connections. DROP
REJECT
This is configured based on how the Carrier Request and LAN to Carrier
Access Control are configured in the previous menus.

© Microhard 88
4.0 Configuration

Source
Select the zone which is to be the source of the data traffic. The LAN Values
refers to local connections on the LTECube.
LAN /Carrier / Any

Source IPs
Match incoming traffic from the specified source IP range. Boxes accept Values (IP Address)
single IP Addresses without network masks, example: 192.168.1.0 to
192.168.1.255 represents all IP Addresses in the 192.168.1.0/24 network. 192.168.0.0 to
(Put same IP in both boxes for a single IP match.) 192.168.0.0

Destination
Select the zone which is the intended destination of the data traffic. 3G/4G Values (selection)
applies to the wireless connection to the cellular carrier and the LAN,
LAN1, USB refers to local connections on the LTECube. LAN / Carrier / Any

Destination IPs
Match incoming traffic from the specified destination IP range. Boxes Values (IP Address)
accept single IP Addresses without network masks, example: 192.168.1.0
to 192.168.1.255 represents all IP Addresses in the 192.168.1.0/24 192.168.0.0 to
network. (Put same IP in both boxes for a single IP match.) 192.168.0.0

Destination Port
Match incoming traffic directed at the given destination port or port range. Values (port)
(To specify a port range use a From:To (100:200) format) 0

Protocol
The protocol field defines the transport protocol type controlled by the rule. Values
TCP
UDP
Both
ICMP
Protocol 41
GRE

© Microhard 89
4.0 Configuration

4.5.6 Firewall > Firewall Default

The Firewall Default option allows a user to return the modems firewall setting back to the default values
without having to reset the entire modem.

Image 4-5-6: Firewall > Firewall Default

© Microhard 90
4.0 Configuration

4.7 VPN

4.7.1 VPN > Summary

A Virtual Private Network (VPN) may be configured to enable a tunnel between the LTECube and a remote
network. The LTECube supports VPN IPsec Gateway to Gateway (site-to-site) tunneling, meaning you are
using the LTECube to create a tunnel to a network with VPN capabilities (Another LTECube or VPN
capable device).

Image 4-7-1: VPN > Summary

© Microhard 91
4.0 Configuration

4.7.2 VPN > Gateway To Gateway (Site-to-Site)

A Gateway to Gateway connection is used to create a tunnel between two VPN devices such as an
LTECube and another device (another LTECube or Cisco VPN Router or another vendor). The local and
remote group settings will need to be configured below to mirror those set on the other VPN device.

Image 4-7-2: VPN > Gateway to Gateway

Tunnel Name
Enter a name for the VPN Tunnel. Up to 16 different tunnels can be Values (chars)
created, each requiring a unique name.
(no default)

© Microhard 92
4.0 Configuration

Enable
Used to enable (checked) is disable (unchecked) the VPN tunnel. Values (checkbox)
Enable (Checked)

Interface
Select the WAN interface used for the Gateway to Gateway VPN. U Values (selection)
Carrier
WAN1
WAN2

Local Group Setup

Local Security Gateway Type

Specify the method for identifying the router to establish the VPN tunnel. Values (selection)
The Local Security Gateway is on this router; the Remote Security
Gateway is on the other router. At least one of the routers must have either IP Only
a static IP address or a dynamic IP with server id to make a connection. IP + Server ID
Dynamic IP + Server ID

IP Only: Choose this option if this router has a static WAN IP address. The WAN IP address appears
automatically. For the Remote Security Gateway Type, an extra field appears. If you know the IP address
of the remote VPN router, choose IP Address, and then enter the address.

IP + Server ID: Choose this option if this router has a static WAN IP address and a server id. The WAN IP
address appears automatically. For the Remote Security Gateway Type, an extra field appears. If you
know the IP address of the remote VPN router, choose IP Address, and then enter the address.

Dynamic IP + Server ID: Choose this option if this router has a dynamic IP address and a server id
(available such as @microhard.vpn). Enter the server id to use for authentication. The server id can be
used only for one tunnel connection.

Interface IP Address
Displays the IP address of the LTECube, which is the local VPN Gateway. Values (IP Address)
Current IP Address

Server ID
This option appears when the Local Security Gateway Type specifies that Values (characters)
the Server ID is required for the connection. The Server ID must be in the
format @name, where name can be anything. Both routers must know (no default)
each others names to establish a connection.

© Microhard 93
4.0 Configuration

Group Subnet IP / Mask -1

Specify the local subnet(s) by entering IP and mask of the local network. Values (IP Address)
(No default subnet IP)
255.255.255.0

Remote Group Setup

Remote Security Gateway Type

Specify the method for identifying the router to establish the VPN tunnel. Values (selection)
The Local Security Gateway is on this router; the Remote Security
Gateway is on the other router. At least one of the routers must have either IP Only
a static IP address or a dynamic IP with server id to make a connection. IP + Server ID
(See Local Group Setup for details) Dynamic IP + Server ID

Gateway IP Address
If the remote VPN router has a static IP address, enter the IP address of Values (IP Address)
the remote VPN Gateway here.
(no default)

Server ID
This option appears when the Remote Security Gateway Type specifies Values (IP Address)
that the Server ID is required for the connection. The Server ID must be in
the format @name, where name can be anything. Both routers must know (no default)
each others names to establish a connection.

Group Subnet IP / Mask -1

Define the remote network(s) by specifying the local subnet. Values (IP Address)
(No default subnet IP)
255.255.255.0

© Microhard 94
4.0 Configuration

IPsec Setup

Aggressive Mode
Check the box to enable aggressive mode for IPSec. In aggressive mode Values (checkbox)
the IKE SA negotiation is squeezed into 3 packets, resulting in faster
negotiation, but is less secure. (unchecked)

IKE Strict Mode

Check the box to enable IKE Strict Mode. Values (checkbox)
(unchecked)

IKE DH Group
Select the Diffie-Hellman public key type. Select between 1024, 1536 and Values (selection)
2048 bit. The values on each end of the tunnel must match.
modp1024
modp1536
modp2048

IKE Encryption
Select the IKE Encryption type used. Select the value to match the Phase 1 Values (selection)
Encryption type used by the remote VPN router.
3des
aes
aes128
aes256

IKE Authentication
Sets the IKE Authentication type. Select the value to match the Phase 1 Values (selection)
Authentication used by the remote VPN router accordingly.
md5
sha1

IKE SA Lifetime(s)
Sets the lifetime of the keys used to encrypt data, when the timers run out Values
the tunnel negotiates a new key. The default value is 28800 seconds (8
hours). 28800

Phase 2 Type
Select the type of security protocol to use for phase 2 of the IKE Values (selection)
negotiation. The options are ESP (Encapsulating Security Payload) and AH
(Authentication Header). Must match remote end of tunnel. ESP / AH

© Microhard 95
4.0 Configuration

Phase 2 Strict Mode

Check the box to enable IKE Strict Mode for phase 2. Values (checkbox)
(unchecked)

Phase 2 DH Group
Select value to match the values required by the remote VPN router. Values (selection)
modp1024
modp1536
modp2048

Phase 2 Encryption
Select value to match the Phase 1 Encryption type used by the remote Values (selection)
VPN router.
3des
aes
aes128
aes256

Phase 2 Authentication
Sets the IKE Authentication type. Select the value to match the Phase 2 Values (selection)
Authentication used by the remote VPN router accordingly.
md5
sha1

Phase 2 SA Lifetime(s)
Sets the lifetime of the keys used to encrypt data for phase 2, when the Values
timers run out the tunnel negotiates a new key. The default value is 3600
seconds (1 hour). 3600

Preshared Key
Set the Preshared Key required to authenticate with the remote VPN Values (characters)
router.
password

DPD Delay(s)
Dead Peer Detection is used to detect if there is a dead peer. Set the DPD Values (seconds)
Delay (seconds), as required.
32

DPD Timeout(s)
Set the DPD (Dead Peer Detection) Timeout (seconds), as required. Values (seconds)
122

© Microhard 96
4.0 Configuration

DPD Action
Controls the use of Dead Peer Detection (DPD) protocol, which is the Values (seconds)
method to detect the aliveness of a IPsec connection. When DPD is in use,
VPN device will send IPsec DPD packet to the peer and wait for the peer's Hold
acknowledgement. If there is no feedback from the peer, the tunnel is Clear
stopped and unrouted (clear), put in the (hold) state or (restarted). Restart
Backup

© Microhard 97
4.0 Configuration

4.7.3.1 VPN > L2TP Client

The LTECube cab be configured as a L2TP Server or Client. This section outlines the configuration of a
L2TP Client.

Image 4-7-3: VPN > L2TP Client

Tunnel Name
Enter a name for the VPN Tunnel. Up to 16 different tunnels can be Values (chars)
created, each requiring a unique name.
tunnel1

Enable
Used to enable (checked) is disable (unchecked) the VPN tunnel. Values (checkbox)
Enable (Checked)

© Microhard 98
4.0 Configuration

Local Interface IP Address

This will display the current LTECube WAN (Cellular) IP Address. Values (IP Address)
Current IP

Remote Gateway IP Address

Enter the IP Address of the Remote Gateway that you wish to establish a Values (IP Address)
connection with.
none

Remote Server ID
Some servers require that you know the Server ID as well as the IP Values
address. Enter the Server ID of the remote router here.
none

Remote Subnet IP
In order to communicate with the devices on the other side of the tunnel, Values (IP Address)
the LTECube must know which data to pass through the tunnel, to do this
enter the Remote Subnet network IP address here. none

Remote Subnet Mask

Enter the Remote Subnet Mask Values (IP Address)
none

Idle time before hanging up

Enter the Idle time (in seconds) to wait before giving up the PPP Values (seconds)
connection. The default is 0, which means the time is infinite. (0—65535)
0

Username
Enter the Username Values (chars)
0

Preshared Key
The preshared key is required to connect to the L2TP Server. Values (chars)
0

IPSec Setup - See previous sections for additional info.

© Microhard 99
4.0 Configuration

4.7.3.2 VPN > L2TP Server

The LTECube can operate as a L2TP Server, allowing VPN connections to be made with L2TP Clients.
The configuration for L2TP Server can be found on the VPN Summary Page. You can then select “Edit”.

Image 4-7-4: VPN > L2TP Server Configuration

Enable
Select the Enable check box to enable the L2TP Server and to view the Values (checkbox)
L2TP Server configuration parameters.
Disabled (unchecked)

IPsec
Use the IPsec checkbox to enable Ipsec on the L2TP Server. The different Values (checkbox)
IPsec parameters are covered in the IPsec section of Gateway-to-Gateway
VPN. Disabled (unchecked)

© Microhard 100
4.0 Configuration

Local Security Gateway Type

Select the Local Security Gateway type. When set to IP only, clients only Values (selection)
need to know the IP address of the L2TP Server in order to create a
session. In a IP + Server ID selection, the client would need to know the IP IP Only
and a specified ID. IP + Server ID

Server ID
As a extra measure of security a server ID can be specified and remote Values (characters)
client would need to know this ID before they can create a session and
begin authentication. none

Interface
The Interface parameter is a non changeable parameter that is shown to Values
indicate which interface the L2TP Server is listening for incoming
connections from clients. To use an alternate interface, you need to create/ 4G or WAN
edit a new connection from the VPN > Summary page.

Interface IP Address
The Interface IP Address is a non-changeable field that shows the current Values
WAN or 4G IP address (as defined in the Interface parameter above).
Clients would need this IP address to create a remote connection. xxx.xxx.xxx.xxx

Server IP Address
The Server IP Address is the local LAN IP of the Dragon-LTE. (The default Values (IP Address)
Local IP of the LTECube is 192.168.168.1)
none

IP Address Range Start

Enter the starting range of IP Addresses to be assigned to clients once Values (IP Address)
they successfully create a tunnel with the L2TP Server.
none

IP Address Range End

Enter the ending range of IP Addresses to be assigned to clients once they Values (IP Address)
successfully create a tunnel with the L2TP Server.
none

IPSec Setup - See previous sections for additional info.

© Microhard 101
4.0 Configuration

4.7.4 Network > OpenVPN

OpenVPN Server
The LTECube supports OpenVPN and can be configured as a Server or a Client. This section outlines the
configuration of a OpenVPN Server.

Image 4-7-5: VPN > OpenVPN Server

OpenVPN Mode
Enable/Disable the OpenVPN Mode by selecting the mode to operate in, Values (selection)
Client or Server. When the Server is enabled it will be listening for incoming
connection requests from OpenVPN Clients. Client / Server / Disable

Server Bridge Mode

In Server Bridge Mode the LTECube logically merges both Ethernet Values (checkbox)
networks, at both ends of the tunnel, as if they were a single Ethernet
subnet. unchecked

© Microhard 102
4.0 Configuration

Tunnel Protocol
Select the Tunnel Protocol to be used. The options are TCP and UDP, the Values (selection)
default is UDP.
TCP / UDP

Port
The TCP/UDP port which the server is listening on. Default is 1194 Values (port)
1194

MSSFIX/Fragment size
The maximum resulting UDP send packet size after the OpenVPN has Values (size)
fully encapsulated data. Packets exceeding this max value will be
fragmented. 1370

Root Certificate
The root certificate file (CA file) that all the server and clients must have in Values (chars)
common.
ca.crt

Public Server Certificate

The Public Server Certificate which is the certificate file that resides on only Values (chars)
the server.
server.crt

Private Server Key

The private Server Key, which should not be disclosed. Values (chars)
server.key

Certificate Revocation List

In PEM format, the Certificate Revocation List is a list of certificates that Values (chars)
have been revoked and should not be trusted.
crl.pem

TLS Auth Key

The server and each client must have a copy of this key to do TLS Values (chars)
authentication.
(no default)

© Microhard 103
4.0 Configuration

User/Password Authentication
Select the OpenVPN username as setup/defined in the VPN Users menu. Values (selection)
(no default)

Diffie hellman parameter

Select between 1024 bit and 2048 bit Diffie Hellman keys for security. Values (selection)
DH2048 / DH1024

Bridge Gateway IP Address

When set to Server Bridge Mode, the Bridge Gateway IP Address must be Values (IP Address)
specified.
(No default)

Bridge IP Address Range / Netmask

Specify the IP Address Range and Netmask that is used when the Values (IP Address)
OpenVPN Server is set to Server Bridge Mode.
(No default)

Server Virtual Subnet / Subnet Mask

The subnet and subnet mask that the server will create to assign address Values (IP Address)
to itself and the clients.
10.8.0.0

Push DNS to Client

If enabled (Auto) the server will push its DNS server information to the Values (selection)
client. Manual allows the DNS information to be manually entered.
NO / Auto / Manual

Client Isolation
When select yes, the clients will not see each other. Select no, it will allow Values (selection)
different clients to be able to "see" each other. By default, clients will only
see the server. No / Yes

Keep Alive Ping Interval

The keep alive directive causes ping-like messages to be sent back and Values (seconds)
forth over the link so that each side knows when the other side has gone
down. Default 10 seconds. 10

Keep Alive Ping Period

Default 120 seconds. Ping every 10 seconds, assume that remote peer is Values (seconds)
down if no ping received during a 120 second time period. (must be at least
twice the interval specified above) 120

© Microhard 104
4.0 Configuration

Cipher
Select a cryptographic cipher. Must be the same on Server and Client. Values (selection)
DES-CBC CAST5-CBC
RC2-CBC RC2-64-CBC
DES-EDE-CBC AES-128-CBC
DES-EDE3-CBC AES-192-CBC
DESX-CBC AES-256-CBC
BF-CBC SEED-CBC
RC2-40-CBC

Use LZO Compression

Enable/Disable LZO compression on the VPN link. Lempel–Ziv– Values (selection)
Oberhumer (LZO) is a lossless data compression algorithm.
Enable / Disable

OpenVPN Server Network Settings

OpenVPN supports multiple subnet behind the server/client. In order for the Values (selection)
vpn connection to reach the subnet behind, each subnet must be specified
for the data to be routed correctly. (no default)

© Microhard 105
4.0 Configuration

OpenVPN Client
The LTECube supports OpenVPN and can be configured as a Server or a Client. This section outlines the
configuration of a OpenVPN Client.

Image 4-7-6: VPN > OpenVPN Client

OpenVPN Mode
Enable/Disable the OpenVPN Mode by selecting the mode to operate in, Values (selection)
Client or Server. When the Server is enabled it will be listening for incoming
connection requests from OpenVPN Clients. Client / Server / Disable

Client Bridge Mode

Select the box to enable Client Bridge Mode. Values (selection)
(unchecked)

Tunnel Protocol
Select the Tunnel Protocol to be used. The options are TCP and UDP, the Values (selection)
default is UDP.
TCP / UDP

© Microhard 106
4.0 Configuration

MSSFIX/Fragment size
The maximum resulting UDP send packet size after the OpenVPN has Values (size)
fully encapsulated data. Packets exceeding this max value will be
fragmented. 1370

Server IP/Port
The IP Address and TCP/UDP port which the server is located. This is Values (IP/Port)
generally the Public IP Address of the router/modem where the Server is
running. (no default)

Root Certificate
The root certificate file (CA file) that all the server and clients must have in Values (chars)
common.
ca.crt

Cleint Certificate
The Client Certificate which is the certificate file that resides on only the Values (chars)
client.
client.crt

Client Key
The private Client Key, which should not be disclosed. Values (chars)
client.key

TLS Auth Key

The server and each client must have a copy of this key to do TLS Values (chars)
authentication.
(no default)

Cipher
Select a cryptographic cipher. Must be the same on Server and Values (selection)
Client.
DES-CBC RC2-40-CBC
RC2-CBC CAST5-CBC
DES-EDE-CBC RC2-64-CBC
DES-EDE3-CBC AES-128-CBC
DESX-CBC AES-192-CBC
BF-CBC AES-256-CBC
SEED-CBC

Use LZO Compression

Enable/Disable LZO compression on the VPN link. Lempel–Ziv– Values (selection)
Oberhumer (LZO) is a lossless data compression algorithm.
Enable / Disable

© Microhard 107
4.0 Configuration

4.7.5 VPN > GRE

GRE Configuration
The LTECube supports GRE (Generic Routing Encapsulation) Tunneling which can encapsulate a wide
variety of network layer protocols not supported by traditional VPN. This allows IP packets to travel from
one side of a GRE tunnel to the other without being parsed or treated like IP packets.

Image 4-7-7: VPN > Edit/Add GRE Tunnel

Name
Each GRE tunnel must have a unique name. Up to 10 GRE tunnels are Values (Chars(32))
supported by the LTECube.
gre

Enable
Enable / Disable the GRE Tunnel. Values (selection)
Disable / Enable

© Microhard 108
4.0 Configuration

Multicast
Enable / Disable Multicast support over the GRE tunnel. Values (selection)
Disable / Enable

TTL
Set the TTL (Time-to-live) value for packets traveling through the GRE Values (value)
tunnel.
1 - 255

Key
Enter a key is required, key must be the same for each end of the GRE Values (chars)
tunnel.
(none)

ARP
Enable / Disable ARP (Address Resolution Protocol) support over the GRE Values (selection)
tunnel.
Disable / Enable

Local Setup
The local setup refers to the local side of the GRE tunnel, as opposed to the remote end.

Gateway IP Address
This is the WAN IP Address of the Dragon-LTE, this field should be Values (IP Address)
populated with the current WAN IP address.
(varies)

Tunnel IP Address
This is the IP Address of the local tunnel. Values (IP Address)
(varies)

Netmask
Enter the subnet mask of the local tunnel IP address. Values (IP Address)
(varies)

Subnet IP Address
Enter the subnet address for the local network. Values (IP Address)
(varies)

© Microhard 109
4.0 Configuration

Subnet Mask
The subnet mask for the local network/subnet. Values (IP Address)
(varies)

Remote Setup
The remote setup tells the LTECube about the remote end, the IP address to create the tunnel to, and the
subnet that is accessible on the remote side of the tunnel.

Gateway IP Address
Enter the WAN IP Address of the Dragon-LTE or other GRE supported Values (IP Address)
device in which a tunnel is to be created with at the remote end.
(varies)

Subnet IP Address
The is the IP Address of the remote network, on the remote side of the Values (IP Address)
GRE Tunnel.
(varies)

Subnet Mask
The is the subnet mask for the remote network/subnet. Values (IP Address)
(varies)

IPsec Setup
Refer to the IPsec setup in the VPN Site to Site section of the manual for more information.

© Microhard 110
4.0 Configuration

4.7.6 VPN > VPN Users

For VPN L2TP & OpenVPN operation, users will be required to provide a username and password. Use
the VPN Users menu to set up the required users.

Image 4-7-8: VPN > VPN Client Access

Username
Enter a username for the user being set up. Values (characters)
(no default)

New Password
Enter a password for the use. Values (characters)
(no default)

Confirm New Password

Enter the password again, the LTECube will ensure that the password Values (IP Address)
match.
(no default)

© Microhard 111
4.0 Configuration

4.7.7 VPN > Certificate Management

When using the VPN features of the LTECube, it is possible to select X.509 for the Authentication Type. If
that is the case, the LTECube must use the required x.509 certificates in order to establish a secure tunnel
between other devices. Certificate Management allows the user a place to manage these certificates.

Image 4-7-9: VPN > Certificate Management

© Microhard 112
4.0 Configuration

4.8 Router

4.8.1 Router > RIPV2

The LTECube-CAT4 is capable of providing and participating in RIPv2 (Routing Information Protocol v2), to
exchange routing information from attached devices. Static routes can also be added in the Network >
Routes menu.

Image 4-8-1: Router > RIPv2

RIPV2 Status
Enable or disable RIPV2 routing on the LTECube. If enabled the device will Values (selection)
exchange routing information on the specified (interfaces) attached
networks. Enable / Disable

Passive Interface
Do not speak RIPV2 on the given interface. All received packets are Values (checkbox)
processed as normal and RIP does not send multicast or unicast RIP
packets on this interface. (unchecked)

Split Horizon
Split Horizon prevents a router from advertising a route back onto the Values (checkbox)
interface from which it was learned, preventing routing loops. Poison
Reverse, actively advertises routes as unreachable over the interface they On / Poison Reverse
were learned by setting the metric to infinite.

Authentication Type / Port / Key ID / Password

Enable MD5 authentication for the RIPV2 protocol. The Key ID identifies Values (selection)
the secret key used to create the message digest. This ID is part of the
protocol and must be consistent across all routers in a link. None
MD5

RIPV2 Network Announcement Configuration

Each attached network that is to participate with the RIPV2 exchange must Values (Subnet/Length))
be specified here. Once added they participating networks are shown in the
list. (no default)

© Microhard 113
4.0 Configuration

4.8.2 Router > OSPFv2

The LETCube-CAT4 is also capable of providing and participating in OSPFv2 (Open Shortest Path First),
to exchange routing information from attached devices. Static routes can also be added in the Network >
Routes menu.

Image 4-8-2: Router > OSPFv2

OSPFv2 Status
Enable or disable OSPF routing on the LTECube. If enabled the device will Values (selection)
exchange routing information on the specified (interfaces) attached
networks. Enable / Disable

Router ID
Set the router ID in the format used for OSPF. Values (selection)
Enable / Disable

Area
OSPF provides for the protocol is be broken up into multiple smaller and Values (selection)
independent link-state areas. The format can be A.B.C.D or any 32 bit
number. (no default)

Passive Interface
Do not speak OSPF on the given interface, but does advertise the interface Values (checkbox)
as a stub-link in the router LSA.
(unchecked)

Authentication Type / Key ID / Key

Enable MD5 authentication for the OSPF protocol. The Key ID identifies Values (selection)
the secret key used to create the message digest. This ID is part of the
protocol and must be consistent across all routers in a link. None
MD5

© Microhard 114
4.0 Configuration

4.8.3 Router > SMCRoute

Static Multicast routes can be specified on LTECube via the SMCRoute menu.

Image 4-8-3: Router > SMCRoute

Status
Enable or disable the static multicast routes. Values (selection)
Enable / Disable

TTL Increase
Check this box if the multicast source does not set the TTL correctly. The Values (checkbox)
TTL will be increased by 1 to make the multicast packets be routed through
the modem. (unchecked)

Multicast Group Address

Class D address, valid range is 224.0.0.0 to 239.255.255.255. The total Values (address)
number of multicast routes is limited to 10.
(no default)

Upstream Network
Select the upstream network interface used by the multicast static route. Values (selection)
LAN | Carrier
(varies, defined interfaces)

© Microhard 115
4.0 Configuration

Source IP (optional)
Specify the multicast source IP address. If any source is allowed, leave Values (address)
blank or use 0.0.0.0.
(no default)

Downstream network(s)
Hold CTRL (Windows) / Command (MAC) to select multiple windows. Values (checkbox)
(unchecked)

© Microhard 116
4.0 Configuration

4.9 GPS

4.9.1 GPS > Location

Location Map
The location map shows the location on the LTECube. The unit will attempt to get the GPS coordinates
from the built in GPS receiver, and if unsuccessful, will use the Cell ID location reported by the Cellular
Carrier.

Image 4-9-1: GPS > Location Map

If the unit had a GPS signal (GPS Module enabled and antenna attached), it will report the specific GPS
coordinates of the modem, otherwise only the estimated coordinates reported by the Carrier. To see the
device location in the Location Tab and via NMS, when using the carriers reported location, a Geolocation
API key must be obtained and set in the modem. Geolocation API keys can be obtained from services
such as Google. Click the “Set MapAPI key” link set the API key (see NMS section of this manual for
detailed instructions)

The maps can be viewed with either Bing or Openstreet maps by using the option located at the bottom,
right hand corner near the refresh option.

© Microhard 117
4.0 Configuration

4.9.2 GPS > Settings

The LTECube-CAT4 can be polled for GPS data via GPSD standards and/or provide customizable
reporting to up to 4 different hosts using UDP or Email Reporting. GPS is an optional feature of the
LTECube, and must be specified at the time of order and factory prepared. If the screen below are not
available on your unit, you do not have a GPS enabled model.

Image 4-9-2: GPS > Settings

GPS Status
Enable or disable the GPS polling function of the LTECube. Values (Selection)
Disable / Enable

GPS Source
The LTECube contains an standalone GPS module built into the unit. To Values (Selection)
use the GPS features of the LTECube an antenna must be connected to
the GPS Antenna Port. Standalone GPS

TCP Port
Specify the TCP port on the LTECube where the GPS service is running Values (1-65535)
and remote systems can connect and poll for GPSD data.
2947
Sample Output:

PS C:\nmap-7.91> .\ncat.exe 192.168.168.1 2947

r
GPSD,R=1
$GPGSV,4,1,14,02,06,090,19,05,34,056,31,07,00,021,,13,27,099,32*7D
$GPGSV,4,2,14,15,26,139,28,16,21,319,11,18,59,277,19,20,27,221,*7D
$GPGSV,4,3,14,23,22,215,23,25,05,195,14,26,32,281,22,29,64,153,32*76
$GPGSV,4,4,14,46,30,199,,51,31,171,30*7E
$GPGLL,5108.57324,N,11404.49045,W,152729.00,A,D*73
$GPZDA,152729.00,13,10,2020,00,00*6F
$GPRMC,152730.00,A,5108.57323,N,11404.49032,W,0.163,,131020,,,D*60
$GPVTG,,T,,M,0.163,N,0.301,K,D*20
$GPGGA,152730.00,5108.57323,N,11404.49032,W,2,11,0.59,1128.4,M,-17.5,M,,0000*53
$GPGSA,A,3,25,02,29,26,05,51,18,13,15,16,23,,1.18,0.59,1.02*07
$GPGSV,4,1,14,02,06,090,19,05,34,056,32,07,00,021,,13,27,099,33*7F

Antenna Mode
Set this parameter to match the type of GPS antenna connected to the Values (Selection)
GPS antenna port.
Passive Antenna
Active Antenna

© Microhard 118
4.0 Configuration

4.9.3 GPS > Report

The LTECube can provide customizable reporting to up to 4 hosts using UDP or Email Reporting.

Image 4-9-3: GPS > GPS Report

Report Define
Enable UDP and/or Email or disable GPS Reporting. Up to 4 reports can Values (selection)
be set up and configured independently.
Disable
UDP Report
Email Report

Time Interval
The interval timer specifies the frequency at which the GPS data is Values (seconds)
reported in seconds.
600

© Microhard 119
4.0 Configuration

Message 1-4
The Message field allows customization of up to 4 different GPS messages Values (selection)
to be sent to the specified host.
None
None - Message is not used, no data will be sent ALL NMEA
ALL - Sends all of the below GGA
GGA - GPS Fix Data GSA
GSA - Overall Satellite Data GSV
GSV - Detailed Satellite Data RMC
RMC - Recommended Min Data for GPS VTG
VTG - Vector Track & Ground Speed Latitude/Longitude
GPSGate - For use with GPSGate Tracking Software GPSGate UDP Protocol

Trigger Set
The trigger condition defines the conditions that must be met before a GPS Values (selection)
update is reported. If OR is chosen, the Repeater Timer OR the Distance
trigger conditions must be met before an update is sent. The AND Only Timer
condition, requires that both the Repeat timer AND the Distance trigger Timer AND Distance
conditions be met before an update is sent. Timer OR Distance

Distance Set
The distance parameter allows the GPS data to only be sent when a Values (meters)
specified distance has been traveled since the last report.
1000

UDP Remote IP / Port

This is the IP Address and port of the remote host in which the UDP Values (Address/Port)
packets are to be sent.
0.0.0.0 / 20175
Sample Output:
PS C:\nmap-7.91> .\ncat.exe -l -u 20175
$GPGSV,4,1,13,02,14,086,14,05,43,059,39,13,21,107,32,15,18,145,32*7C
$GPGSV,4,2,13,16,15,325,27,18,50,270,22,20,18,218,,23,14,213,21*71
$GPGSV,4,3,13,25,14,197,24,26,32,292,09,29,75,154,31,46,30,199,*79
$GPGSV,4,4,13,51,31,171,30*49
$GPGLL,5108.56925,N,11404.48891,W,150641.00,A,D*74
$GPZDA,150641.00,13,10,2020,00,00*62
$GPRMC,150642.00,A,5108.56928,N,11404.48892,W,0.049,,131020,,,D*6C
$GPVTG,,T,,M,0.049,N,0.090,K,D*22
$GPGGA,150642.00,5108.56928,N,11404.48892,W,2,11,0.71,1104.0,M,-17.5,M,,0000*56
$GPGSA,A,3,25,02,29,26,05,51,18,13,15,16,23,,1.41,0.71,1.21*00

$GPGSV,4,1,13,02,14,086,14,05,43,059,39,13,21,107,31,15,18,145,32*7F
$GPGSV,4,2,13,16,16,325,27,18,51,270,18,20,19,218,,23,14,213,21*7B
$GPGSV,4,3,13,25,13,197,22,26,32,292,12,29,75,154,30,46,30,199,*73
$GPGSV,4,4,13,51,31,171,30*49
$GPGLL,5108.56911,N,11404.48933,W,150651.00,A,D*7B
$GPZDA,150651.00,13,10,2020,00,00*63
$GPRMC,150652.00,A,5108.56905,N,11404.48934,W,0.179,,131020,,,D*6D
$GPVTG,,T,,M,0.179,N,0.331,K,D*28
$GPGGA,150652.00,5108.56905,N,11404.48934,W,2,11,0.73,1104.5,M,-17.5,M,,0000*52
$GPGSA,A,3,25,02,29,26,05,51,18,13,15,16,23,,1.40,0.73,1.20*02

© Microhard 120
4.0 Configuration

Mail Subject
If an Email report is chosen, the subject line of the Email can be defined Values (characters)
here.
1000

Mail Server
If an Email report is to be sent, the outgoing mail server must be defined, Values (Address:port)
and the port number.
smtp.gmail.com:465

Username / Password
Some outgoing mail servers required username and password to prevent Values (characters)
an account being used for spam. Enter the login credentials here.
Username / password

Mail Recipient
Some outgoing mail servers require a username and password to prevent Values (characters)
an account being used for spam. Enter the login credentials here.
host@email.com

© Microhard 121
4.0 Configuration

4.9.4 GPS > GpsGate

The LTECube is compatible with GpsGate - GPS Tracking Software, which is a 3rd party mapping solution
used for various GPS services including vehicle and asset tracking The LTECube can communicate with
GpsGate via Tracker Mode and TCP/IP. (UDP reporting can also send information to GpsGate, see the
GPS > Report - UDP Reports)

Image 4-9-4: GPS > GpsGate Tracker Mode

GpsGate - Tracker Mode

Mode Set
Enable GpsGate Tracker Mode or TCP modes. In tracker mode the Values (selection)
LTECube and GpsGate software will communicate via TCP/IP, however if
a connection is not available it will attempt to use SMS messaging. Disable
Enable Tracker Mode
Enable TCP Send Mode

Server Command Channel

By default the LTECube and GpsGate will use TCP and SMS to ensure Values (seconds)
communication between each other. It is also possible to specify TCP or
SMS communication only. Initial setup in Tracker mode must be via SMS. TCP and SMS
TCP Only
SMS Only

TCP Alive Mode / Alive Time Interval

TCP alive mode will keep TCP connection alive if tracker is not enabled or Values (seconds)
the tracker interval is too long. The default is 150 seconds.
150

© Microhard 122
4.0 Configuration

Setup Phone Filter

A phone number filter can be applied to prevent SMS commands not Values (selection)
intended for the LTECube from being processed.
Disable: Accept All
Enable Filter

Motion Trigger
Use this parameter to enable or disable the motion trigger in the LTECube. Values (selection)
Disable
Enable Motion Trigger

When GPS Invalid, Sending Data

Specify what happens when the GPS data is invalid, either use the last Values (selection)
valid position or do not use the last valid position.
Not Use Last Valid Position
Use Last Valid Position

GpsGate - TCP Mode

Image 4-9-5: GPS > GpsGate TCP Mode

© Microhard 123
4.0 Configuration

Mode Set
Enable GpsGate Tracker Mode or TCP modes. In TCP Mode the LTECube Values (selection)
will establish a connection with the GpsGate Server directly without the
SMS setup process. If the TCP connection is not available, the LTECube Disable
will continue to try to connect every few seconds. Enable Tracker Mode
Enable TCP Send Mode

Server Address / IP
Enter the IP Address of the server running the GpsGate application. Values (IP Address)
0.0.0.0

Server Port
Enter the TCP Port of the server running the GpsGate application. Values (Port)
Sample Output: 30175

PS C:\nmap-7.91> .\ncat.exe -l 30175

$FRCMD,863212033299816,_SendMessage,,5108.57124,N,11404.48785,W,1104.3,0.268,,131020,151117.00,1*6A
$FRCMD,863212033299816,_SendMessage,,5108.57114,N,11404.48801,W,1104.0,0.310,,131020,151127.00,1*64
$FRCMD,863212033299816,_SendMessage,,5108.57073,N,11404.48807,W,1103.1,0.105,,131020,151137.00,1*63

Server Interval
Define the interval at which the LTECube will send data to the GpsGate Values (seconds)
Server.
60

Motion Distance
Set the motion threshold in which the LTECube will be triggered to send Values (meters)
location data.
100

When GPS Invalid, Sending Data

Specify what happens when the GPS data is invalid, either use the last Values (selection)
valid position or do not use the last valid position.
Not Use Last Valid Position
Use Last Valid Position

© Microhard 124
4.0 Configuration

4.9.5 GPS > UDPTracker

The LTECube can be configured to send GPS information via UDP packets to a server based on a time
interval and/or motion trigger. The report can be sent to up to 4 servers.

Image 4-9-6: GPS > UDPTracker

Report No. Status

Use the Report No Status to enable or disable the reporting of UDP Values (selection)
packets to the specified servers.
Disable
Enable

Server Address/IP & Port

Set the server IP address and port number for which to send the Values (IP/port)
UDPTracker UDP packets.
0.0.0.0.0 / 30175

Send Interval
Set the interval for which to send UDPTracker UDP packets to the server. Values (seconds)
The default is 60 seconds.
60 (1-99999)

© Microhard 125
4.0 Configuration

Send WWAN’s RSSI

When sending the UDP packet at the defined interval or when triggered by Values (selection)
the Motion Trigger, also include the WWAN’s RSSI Status.
Disable
Send RSSI Status

Motion Trigger
Enable the Motion Trigger which is trigger a UDP update when the defined Values (selection)
distance threshold has been exceeded.
Disable
Enable Motion Trigger

Motion Trigger
Set the distance for which to travel before triggering the Motion Trigger. Values (meters)
500 (20-99999)

© Microhard 126
4.0 Configuration

4.9.6 GPS > Recorder

The LTECube can be configured to record events based on time intervals, and/or an event trigger and
store them in non-volatile memory. These events can then be viewed within the WebUI, on a map, or sent
to a remote server in a number of different formats.

Image 4-9-7: GPS > GPS Recorder Service

Status
Use the Status parameter to enable the GPS recording functionality of the Values (selection)
LTECube. The total number of records that can be recorded varies
between 16,000 and 36,000, depending on the number of GPS parameters Disable
that are recorded. Enable GPS Recorder

Time Interval
Define the interval at which the LTECube will record GPS data. If there is Values (seconds)
no valid data available at the specified time (i.e. no connected satellites),
the unit will wait until the next time valid information is received. 300

DI/DO Changed
The LTECube can detect and report the current GPS info when a digital Values (selection)
input or output status changes, regardless of the time interval setting.
Record / Don’t Record

© Microhard 127
4.0 Configuration

Speed
Select Record to include the current speed in the reported data. Values (selection)
Record / Don’t Record

Over Speed
Trigger a GPS record entry when the speed has exceeded the configured Values (Km/hr)
threshold. A minimum of 30 Km/hr is required.
120

Orientation
Select Record to record the current orientation when a GPS entry is Values (selection)
recorded. (Degree to North).
Record / Don’t Record

Orientation Changed
Record a GPS, regardless of the time interval, if the orientation of the unit Values (5 ~ 180)
changes. (5 ~ 180: 180 = Disable)
60

WWAN RSSI Level

Select Record to record the current LTE/Cellular RSSI level when a GPS Values (selection)
entry is recorded. (-dB).
Record / Don’t Record

Altitude
Select Record to record the current Altitude when a GPS entry is recorded Values (selection)
(meters).
Record / Don’t Record

© Microhard 128
4.0 Configuration

4.9.7 GPS > Load Record

Data that has been recorded and saved by the LTECube can then be viewed or sent to a remote server in
various formats. The data recorded can also be viewed directly by selecting “View Data” and the data can
be traced on a map (internet access required), by selecting “Trace Map”, or “Quick Trace”. The
screenshots below show the raw data that can be viewed and the Trace Map/Quick Trace output.

Image 4-9-8: GPS > GPS Load Record

© Microhard 129
4.0 Configuration

Record Time Range

Check the boxes next to the records listed above that are to be sent to the Values (selection)
server.
(no default)

Send Mode / Protocol

Specify the data format / protocol type for the data to be sent. Values (selection)
NMEA via UDP
NMEA via TCP
GpsGate via UDP
GpsGate via TCP
Plain Text via UDP
Plain Text via TCP

Server Address/IP
Enter the address or IP address of the remote server to which the data is to Values (IP)
be sent.
nms.microhardcorp.com

Server Port
Enter the UDP/TCP port number of the remote server to which the data is Values (Port)
to be sent.
30175

© Microhard 130
4.0 Configuration

4.9.8 GPS > TAIP

The LTECube has the ability to send GPS data in TAIP (Trimble ASCII Interface Protocol) format to up to 4
different TAIP servers. The following section describes the configuration parameters required to initialize
TAIP reporting.

Image 4-9-9: GPS > TAIP

TAIP service status

Enable or disable TAIP service on the modem. The unit can report TAIP to Values (selection)
up to 4 different hosts.
Enable / Disable

Remote TAIP Server

Enter the IP Address of the Remote TAIP Server. Values (IP Address)
0.0.0.0

Socket Type
Select the socket type that is used by the Remote TAIP server. Select TCP Values (selection)
or UDP, this will define how the connection (TCP) or data is sent (UDP) to
the server. UDP / TCP

Remote TAIP Port

Enter the TCP or UDP port number used on the Remote TAIP server. Values (TCP/UDP)
Example Output: UDP / TCP

PS C:\nmap-7.91> .\ncat.exe -l -k -C 21000

>RPV55141+5114285-1140748700000032;ID=0000;*75<>RPV55146+5114285-1140748800000032;ID=0000;*7D<

© Microhard 131
4.0 Configuration

Message Type
Select between RPV and RLN message types. Values (selection)
RPV - Position/Velocity RPV / RLN
RLN - Long Navigation Message

Interval
Set the frequency at which TAIP messages are reported to the remote Values (seconds)
server. The unit used is seconds, and the default value is 60 seconds.
60

Vehicle ID
Set the Vehicle ID using 4 alpha-numeric characters. Values (chars)
0000

© Microhard 132
4.0 Configuration

4.10 Apps

4.10.1 Apps > Modbus

4.10.1.1 Modbus > TCP Modbus

The LTECube can be configured to operate as a TCP/IP Modbus slave and respond to Modbus requests
and report various information as shown in the Data Map.

Image 4-10-1: Apps > Modbus

Status
Disable or enable the Modbus service on the LTECube. Values (selection)
Disable Service
Enable Service

TCP Mode Status

Disable or enable the Modbus TCP Connection Service on the LTECube. Values (selection)
Disable
Enable

Port
Specify the Port in which the Modbus TCP service is to listen and respond Values (Port #)
to polls.
502

Active Timeout(s)
Define the active timeout in seconds. Values (seconds)
30

© Microhard 133
4.0 Configuration

Slave ID
Each Modbus slave device must have a unique address, or Slave ID. Enter Values (value)
this value here as required by the Modbus Host System.
1

Coils Address Offset

Enter the Coils Address offset as required by the Master. Values (value)
0

Input Address Offset

Enter the Input Address offset as required by the Master. Values (value)
0

Register Address Offset

Enter the Register Address offset as required by the Master. Values (value)
0

Master IP Filter Set

It is possible to only accept connections from specific Modbus Master IP’s, Values (selection)
to use this feature enable the Master IP Filter and specify the IP Addresses
in the fields provided. Disable / Enable

© Microhard 134
4.0 Configuration

4.10.1.2 Modbus > Modbus Data Map

Image 4-10-2: Applications > Modbus Data Map

© Microhard 135
4.0 Configuration

4.10.2 Apps > Netflow Report

The LTECube can be configured to send Netflow reports to up to 3 remote systems. Netflow is a tool that
collects and reports IP traffic information, allowing a user to analyze network traffic on a per interface basis
to identity bandwidth issues and to understand data needs. Standard Netflow Filters can be applied to
narrow down results and target specific data requirements.

Image 4-10-3: Apps > Netflow Report

Status
Enable / Disable Netflow Reporting. Values (selection)
Disable / Enable

Source Address
The Source Address is the IP Address, of which data is to be collected and Values (IP Address)
analyzed. The default of 0.0.0.0 will collect and report information about all
addresses connected to the interface selected below.
0.0.0.0

Interface
Select between LAN, and Carrier interfaces, or capture data from all Values (selection)
interfaces.
LAN / Carrier / ALL

© Microhard 136
4.0 Configuration

Remote IP
The Remote IP is the IP Address of the NetFlow collector where the flow Values (IP Address)
reports are be sent.
0.0.0.0

Remote Port
Enter the Remote Port number. Values (IP Address)

Filter expression
Filter expression selects which packets will be captured. If no expression is Values (chars)
given, all packets will be captured. Otherwise, only packets for which
expression is `true' will be captured. Example: tcp&&port 80
(no default)
The “tcpdump” manual, available on the internet provides detailed expression syntax.

© Microhard 137
4.0 Configuration

4.10.3 Apps > Local Monitor

The Local Device Monitor allows the LTECube to monitor a local device connected locally to the Ethernet
port or to the locally attached network. If the LTECube cannot detect the specified IP or a DHCP assigned
IP, the unit will restart the DHCP service, and eventually restart the modem to attempt to recover the
connection.

Image 4-10-4: Apps > Local Monitor

Status
Enable or disable the local device monitoring service. Values (selection)
Disable / Enable

IP Mode
Select the IP mode. By selecting a fixed IP address the service will monitor Values (selection)
the connection to that specific IP. If auto detect is selected, the LTECube
will detect and monitor DHCP assigned IP address. Fixed local IP
Auto Detected IP

Local IP Setting
This field is only shown if Fixed Local IP is selected for the IP Mode. Enter Values (IP)
the static IP to be monitored in this field.
0.0.0.0

Status Timeout
The status timeout is the maximum time the LTECube will wait to detect the Values (seconds)
monitored device. At this time the LTECube will restart the DHCP service.
(5-65535 seconds) 10

Waiting DHCP Timeout

This field defines the amount of time the LTECube will wait to detect the Values (seconds)
monitored device before it will reboot the modem. (30-65535 seconds)
60

© Microhard 138
4.0 Configuration

4.10.4 Apps > IoT

The LTECube has the ability to join several types of IoT servers to provide statistics and information to
enable monitoring from Microhard (coming soon) and 3rd party IoT Servers. This section is currently in
development and additional details will be available as they become available.

Image 4-10-5: Apps > IoT

Profile Type
Select the IoT Server type you would like to connect to. The remaining Values (selection)
configuration parameters will changed based on the IoT Server type
selected. Microhard Data
Azure (SAS)
Azure (X509)
AWS
OTHER

Profile Name
This field is available to give your IoT Server profile a name. Values (characters)
(no default)

Host Address / Port

Supply the URL or IP Address of the IoT Server as well as the port number Values (characters)
to be used.
(no default)

Publish Interval
The frequency (in seconds) at which the values get published to the IoT Values (seconds)
server.
60
© Microhard 139
4.0 Configuration

Azure Specific Configuration

SAS Token
An SAS token is used to authenticate the device by the Azure hub. This Values (characters)
can be generated for each Client Id by using the "Device Explorer Twin"
application from Azure (or using the Portal). (No default)

Device ID
Enter the unique device identifier which is registered on the Azure IoT hub. Values (characters)
(No default)

Device Auth Token

Enter the device authentication token which is registered on the Azure IoT Values (characters)
hub.
(No default)

AWS Configuration Options

Subdomain
This is the endpoint sub domain provided by your AWS IoT. Values (characters)
(No default)

Account Number
Enter the AWS Account Number associated with AWS IoT. Values (characters)
(No default)

Device Name
This is the name of the Device (Thing) you created at the AWS IoT portal. Values (characters)
(No default)

Region
This is the Region provided by your AWS IoT. Values (selection)
US East(Ohio)

Publication Topic
Provide a name for the AWS publication topic as required by AWS IoT. Values (characters)
(no default)

© Microhard 140
4.0 Configuration

4.10.5 Apps > SSL Management

The SSL Management Menu is used to quickly configure devices to connect and communicate with the
Microhard IoT Portal (In Development). The IoT Portal requires a number of secure certificates to be
created and uploaded to each device. The SSL Management allows users to enter a Registration Code,
which then allows the certificates to be automatically created and uploaded to the device as required.

Image 4-10-6: Apps > SSL Management

Enable
Check the box to enable the SSL Management. In order for the SSL Values (checkbox)
Manager to create and upload certificates the NTP service must be
enabled in the System > Settings Tab. Enable (unchecked)

Host Address / Port

Supply the URL or IP Address of the SSL Management Server as well as Values (characters)
the port number to be used.
(no default)

Registration Code
Enter the registration code obtained by Microhard, or retrieved from your Values (seconds)
IoT Portal Domain. Upon applying the registration code and submitting the
changes, it can take several minutes to complete. (no default)
In order for the SSL Management feature to work, the NTP Service must
be enabled and available in System > Settings.

© Microhard 141
4.0 Configuration

4.10.6 Applications > Event Report

4.10.6.1 Event Report > Configuration

Event Reporting allows the LTECube to send periodic updates via UDP packets. These packets are
customizable and can be sent to up to 3 different hosts, and at a programmable interval. The event packet
can report information about the modem such as the hardware/ software versions, core temperature,
supply voltage, etc; carrier info such as signal strength (RSSI), phone number, Band; or about the WAN
such as if the assigned IP Address changes. All events are reported in binary.

Image 4-10-7: Applications > Event Report

Event Type
This box allows the selection of the type of event to be reported. The Values (selection)
default is disabled. If Modem_event is selected, additional options appear
to the right and allow for customization of the event reported via Messages. Modem_Event
If Management is selected, additional check boxes appear below to select SDP_Event
the interfaces to report to the Microhard NMS system. Management

Remote IP
Enter the IP Address of a reachable host to send the UDP packets Values (IP Address)
0.0.0.0

© Microhard 142
4.0 Configuration

Remote Port
Specify the UDP port number of the Remote IP Address. Values (Port #)
*Default Port Numbers for Microhard NMS (20100 for modem events, 20200 for 20200
Management)

Interval Time(s)
This is the interval time in seconds, that the LTECube will send the Values (seconds)
configured UDP message to the Remote IP and Port specified.
600

Message Info Type

When Modem_Event is selected, up to three different payloads can be Values (seconds)
selected.
Modem
Carrier
WAN

4.10.6.2 Event Report > Message Structure

Modem_event message structure

- fixed header (fixed size 20 bytes)

- Modem ID (uint64_t (8 bytes))
- Message type mask (uint8_t(1 byte))
- reserved
- packet length (uint16_t(2 bytes))
Note: packet length = length of fixed header + length of message payload.

Message type mask

Modem info - 2 bits

00 no
01 yes (0x1)
Carrier info - 2 bits
00 no
01 yes (0x4)
WAN Info - 2 bits
00 no
01 yes (0x10)

sdp_event message structure

- spd_cmd (1 byte(0x01))
- content length (1 byte)
- spd_package - same as spd response inquiry package format

© Microhard 143
4.0 Configuration

4.10.6.3 Event Report > Message Payload

Modem info:

Content length - 2 BYTES (UINT16_T)

Modem name - STRING (1-30 bytes)
Hardware version - STRING (1-30 bytes)
Software version - STRING (1-30 bytes)
Core temperature - STRING (1-30 bytes)
Supply voltage - STRING (1-30 bytes)
Local IP Address - 4 BYTES (UINT32_T)
Local IP Mask - 4 BYTES (UINT32_T)

Carrier info:

Content length - 2 BYTES (UINT16_T)

RSSI - 1 BYTE (UINT8_T)
RF Band - 2 BYTES (UINT16_T)
LTE_Network - STRING (1-30 Bytes)
Service type - STRING (1-30 Bytes)
Channel number - STRING (1-30 Bytes)
SIM card number - STRING (1-30 Bytes)
Phone number - STRING (1-30 Bytes)

WAN Info:

Content length - 2 BYTES (UINT16_T)

IP address - 4 BYTES (UINT32_T)
DNS1 - 4 BYTES (UINT32_T)
DNS2 - 4 BYTES (UINT32_T)

Message Order:

Messages will be ordered by message type number.

For example,

If message type mask = 0x15, the eurd package will be equipped by header+modem information+carrier
information+wanip information.

If message type mask = 0x4, the eurd package will be equipped by header+carrier information.

If message type mask = 0x11, the eurd package will be equipped by header+modem infomation+wanip
infomation.

a fixed message tail

content length --- 2 BYTES(UINT16_T)
product name --- STRING(1—64 bytes)
image name --- STRING(1—64 bytes)
domain name --- STRING(1—64 bytes)
domain password --- STRING(32 bytes) // MD5 encryption
module list --- 5 BYTES // radio, ethernet, carrier, usb, com

© Microhard 144
4.0 Configuration

4.10.7 Applications > Alert

The System Alert feature of the LTECube allows the device to send SMS and/or Email alerts triggered by
events such as RSSI thresholds, Ethernet Link Status and Carrier Roaming.

Image 4-10-8: Applications > Alerts

Status
Enable system alerts to be sent via SMS and/or Email. If disabled, the Values (Selection)
unit with not send SMS alerts.
Disable System Alert
Enable via SMS
Enable via Email
Enable via SMS and Email

© Microhard 145
4.0 Configuration

SMS Configuration

Received Phone Numbers

SMS Alerts can be sent to up to 6 different phone numbers that are Values (Selection)
listed here.
(no default)

Email Configuration

Mail Subject
If an Email report is chosen, the subject line of the Email can be defined Values (characters)
here.
System Alert Notice

Mail Server
If an Email report is to be sent, the outgoing mail server must be defined, Values (Address:port)
and the port number.
smtp.gmail.com:465

Username / Password
Some outgoing mail servers required username and password to prevent Values (characters)
an account being used for spam. Enter the login credentials here.
Username / password

Authentication
Select the authentication used by your Email service provider. Values (selection)
None
SSL/TLS
STARTTLS
SSL/TLS+STARTTLS

Mail Recipient
Some outgoing mail servers require a username and password to prevent Values (characters)
an account being used for spam. Enter the login credentials here.
host@email.com

© Microhard 146
4.0 Configuration

Alert Condition Settings

Image 4-10-9: SMS > SMS Alerts

Time Interval(s)
System Alerts, when active, will be sent out at the frequency defined Values (Seconds)
here.
300

Device Alias
The device Alias is text that is sent with the SMS/Email message to Values (30 chars)
provide additional information or help identify the source of the alert.
UserDevice

RSSI Check
Enable or disable the RSSI alerts. Values (Selection)
Disable RSSI check
Enable RSSI check

Low Threshold (dBm)

Set the threshold for RSSI alerts. When the signal strength drops Values (dBm)
below this threshold, an alert will be sent.
-99

Carrier Network
Enable or disable System Alerts for Roaming Status. Values (Selection)
Disable Roaming Check
Enable Roaming Check

© Microhard 147
4.0 Configuration

Home / Roaming Status

The LTECube can send alerts based on the roaming status. Data rates Values (Selection)
during roaming can be expensive and it is important to know when a
device has started roaming. In Roaming
Changed or In Roaming
Changed to Roaming

Ethernet
Enable or disable System Alerts for the Ethernet Link status of the Values (Selection)
LAN RJ45 port.
Disable Ethernet check
Enable Ethernet check

Ethernet Link Status

The status of the Ethernet Link of the LAN (RJ45) can be used to send Values (Selection)
an alerts. The link status may indicate an issue with the connected
device. Changed
In no-link
Changed or in no-link
Changed to no-link

© Microhard 148
4.0 Configuration

4.11 Diag

4.11.1 Diagnostics > Ping

The Ping feature provides a tool to test network connectivity from within the unit. A user can use the Ping
command by entering the IP address or host name of a destination device in the Ping Host Name field, use
Count for the number of ping messages to send, and the Packet Size to modify the size of the packets
sent.

Image 4-11-1: Diag > Ping

4.11.2 Diagnostics > Trace Route

The Traceroute feature can be used to provide connectivity data by providing information about the
number of hops, routers and the path taken to reach a particular destination.

Image 4-11-2: Diag > Traceroute

© Microhard 149
4.0 Configuration

4.11.3 Iperf
The LTECube features an integrated Iperf server/client to use to measure and analyze throughput of TCP/
UDP packets to and/or from the LTECube. Iperf is a 3rd party utility that can be loaded on any PC to
measure network performance. For additional information about Iperf, please visit the Iperf website.

The LTECube can be configured to operate as a Server, listening for an incoming connection from another
device (with Iperf), or PC running an Iperf client. If set to Iperf client, the LTECube will connect to or send
packets to a specified Iperf server.

Image 4-11-3: Diag > Iperf

Iperf Mode
Select between an Iperf Server (listens for incoming connections) and Values (selection)
client (initiates a connection with a server)
Server / Client

Server Status
If the Iperf mode to set to Server, this Server Status allows a user to Values (selection)
Enable or Disable the server.
Enable / Disable

Protocol
Select the type of packets to be sent to test the throughput. TCP packets Values (selection)
are connection oriented and require additional overhead for the
handshaking that occurs, while UDP is a connectionless, best effort TCP / UDP
oriented protocol.

© Microhard 150
4.0 Configuration

TCP Window Size

Set the TCP Window size for the Iperf Cleint/Server. The recommended Values (kbytes)
default is 85.3K, which can be set by entering 0.
0

TCP Maximum Segment Size

Set the TCP Max Segment Size for the Iperf Cleint/Server. Set to 0 for Values (string)
recommended settings.
0

Remote Server Address

When in Client mode, select the Iperf Server by entering its IP Address Values (IP Address)
here.
192.168.168.100

Duration
When in Client mode, select the duration of the test (in seconds). The Values (seconds)
default is 5.
5

Report Format
Select the format to display the bandwidth numbers in. Supported formats Values (selection)
are:
'Kbits' = Kbits/sec 'Kbytes' = KBytes/sec Kbits
'Mbits' = Mbits/sec 'M'bytes = MBytes/sec Mbits
Kbytes
Mbytes

© Microhard 151
4.0 Configuration

4.11.4 Speedtest
The LTECube features an integrated Netperf speedtest that can be used from either the WebUI or the
command line interface. You can use the list of preconfigured public servers or specify your own. Shown
below is a sample test run in both the WebUI and CLI interfaces.

The speedtest function does use a significant amount of cellular data to run over the LTE
connection. Consider this when running this test, especially when running over long durations.

Image 4-11-4: Diag > Speedtest

The CLI can be accessed from the console interface which can be accessed from the serial console port or
by telnet/ssh into the LTECube.

CLI Syntax:
UserDevice> status diagnostic speedtest --help
Usage: speedtest [ -s | -c ] [-4 | -6] [ -H netperf-server ] [ -t duration ] [ -p host-to-ping ] [ -P port-number ] [ -n
simultaneous-sessions ]

© Microhard 152
4.0 Configuration

Remote Server
Select the from the list of available netperf servers in Values (selection)
which to run the speedtest. You can also select to
manually enter the server details by selecting Customer netperf.bufferbloat.net
Server netperf-east.bufferbloat.net (East Coast US)
netperf-west.bufferbloat.net (California)
netperf-eu.bufferbloat.net (Denmark)
Customer Server

Server Address / Port

If using a custom server of your own, specify the netperf server address Values (Address)
here.
(no default) / 12865

Ping Server
Specify the Ping Server used during the speedtest. By default this is Values (IP Address)
8.8.8.8 which is the google DNS server. If using a custom speedtest server
you must set this to a reachable value. 8.8.8.8

Protocol
Select the type of packets to be sent to test the throughput. TCP packets Values (selection)
are connection oriented and require additional overhead for the
handshaking that occurs, while UDP is a connectionless, best effort TCP / UDP
oriented protocol.

© Microhard 153
4.0 Configuration

4.12 Admin

4.12.1 Admin > Users

Password Change

The Password Change menu allows the password of the user ‘admin’ to be changed. The ‘admin’
username cannot be deleted, but additional users can be defined and deleted as required as seen in the
Users menu below.

Image 4-12-1: Users > Password Change

New Password
Enter a new password for the ‘admin’ user. It must be at least 5 Values (characters)
characters in length. The default password for ‘admin’ is ‘admin’.
admin

Confirm Password
The exact password must be entered to confirm the password change, Values (characters)
if there is a mistake all changes will be discarded.
admin

© Microhard 154
4.0 Configuration

Add Users

Different users can be set up with customized access to the WebUI. Each menu or tab of the WebUI can
be disabled on a per user basis as seen below.

Image 4-12-2: Access Control > Users

Username
Enter the desired username. Minimum or 5 character and maximum of Values (characters)
32 character. Changes will not take effect until the system has been
restarted. (no default)
Min 5 characters
Max 32 characters

Password / Confirm Password

Passwords must be a minimum of 5 characters. The Password must Values (characters)
be re-entered exactly in the Confirm Password box as well.
(no default)
min 5 characters

© Microhard 155
4.0 Configuration

4.12.2 Admin > NMS Settings

The Microhard NMS is a no cost server based monitoring and management service offered by Microhard
Systems Inc. Using NMS you can monitor online/offline units, retrieve usage data, perform backups and
centralized upgrades, etc. The following section describes how to get started with NMS and how to
configure the LTECube to report to NMS.

Contact Microhard to get started with NMS. Once NMS has been configured, each LTECube must be
configured to report into NMS.

Image 4-12-3: NMS Settings

© Microhard 156
4.0 Configuration

Network Management System (NMS) Configuration

Default Settings
The default Settings link will reset the configuration form to the default factory values. The form still needs
to be submitted before any changes will occur.

NMS Server/IP
The default server address for NMS is nms.microhardcorp.com. The NMS Values (IP/Name)
can also be hosted privately, and if that is the case, enter the address here.
nms.microhardcorp.com

Domain Name / Password

This is the domain name and password that was registered on the NMS Values (chars)
website, it must be entered to enable reporting to the NMS system.
default

NMS Report Setting

Online Location
Enable or Disable location estimation via carrier connection. When Values (chars)
enabled, the LTECube will consume some data to retrieve location
information from the internet. Disable/Enable

Geolocation API Key

To display the unit on a map in the GPS > Location or on the NMS Values (chars)
platform, a Geolocation API key must be obtained from a 3rd party service
such as Google. Disable/Enable
General steps to obtain Google Geolocation API:

1. Login your google cloud account and search for "Geolocation API", click "MANAGE".
2. Select from menu item "APIs" to enable "Geolocation API"
3. View key from menu item "Credential" and copy it.
4. To activate key, click the edit (pencil) icon and then Restrict API > Geolocation API
4. Input above key to modem's form on webUI: Admin -> NMS ->Online Location
5. After submit, there will be a link to "check online" to check the status.
6. Location can be checked from webUI: GPS -> Location

Report Status
Enable or Disable UDP reporting of data to the NMS system. Values (chars)
Enable NMS Report
Disable NMS Report

© Microhard 157
4.0 Configuration

Remote Port
This is the port to which the UDP packets are sent, and the NMS system is Values (UDP Port#)
listening on. Ensure this matches what is configured on NMS. The default
is 20200. 20200

Interval(s)
The Interval defines how often data is reported to NMS. The more often Values (seconds)
data is reported, the more data is used, so this should be set according to a
user’s data plan. (0 to 65535 seconds) 300

Information Selection
The LTECube can report information about the different interfaces it has. Values (selection)
By default the LTECube is set to send information about the Carrier, such
as usage and RSSI. Statistical and usage data on the, Ethernet and WIFI Ethernet
(radio) interfaces can also be reported. Carrier
Radio
The more that is reported, the more data that is sent to the NMS system,
be aware of data plan constraints and related costs.

Webclient Setting

Status
The Web Service can be enabled or disabled. This service is used to Values (chars)
remotely control the LTECube. It can be used to schedule reboots,
firmware upgrade and backup tasks, etc. Disable/Enable

Server Type
Select between HTTPS (secure), or HTTP server type. Values (chars)
HTTPS/ HTTP

Server Port
This is the port where the service is installed and listening. This port should Values (Port#)
be open on any installed firewalls.
9998

Username / Password
This is the username and password used to authenticate the unit. This Values (seconds)
should not be changed from the default of admin/admin unless directed by
Microhard. admin/admin

Interval
The Interval defines how often the LTECube checks with the NMS System Values (min)
to determine if there are any tasks to be completed. Carrier data will be
consumed every time the device probes the NMS system. 30

© Microhard 158
4.0 Configuration

4.12.3 Admin > SNMP

The LTECube may be configured to operate as a Simple Network Management Protocol

(SNMP) agent. Network management is most important in larger networks, so as to be able to
manage resources and measure performance. SNMP may be used in several ways:

• configure remote devices

• monitor network performance
• detect faults
• audit network usage
SNMP: Simple Network • detect authentication failures
Management Protocol
provides a method of A SNMP management system (a PC running SNMP management software) is required for this
managing network service to operate. This system must have full access to the LTECube. Communications is in
devices from a single PC
running network the form of queries (information requested by the management system) or traps (information
management software. initiated at, and provided by, the SNMP agent in response to predefined events).
Managed networked Objects specific to the LTECube are hosted under private enterprise number 21703.
devices are referred to as
SNMP agents.
An object is a variable in the device and is defined by a Management Information Database
(MIB). Both the management system and the device have a copy of the MIB. The MIB in the
management system provides for identification and processing of the information sent by a
device (either responses to queries or device-sourced traps). The MIB in the device relates
subroutine addresses to objects in order to read data from, or write data to, variables in the
device.

An SNMPv1 agent accepts commands to retrieve an object, retrieve the next object, set and
object to a specified value, send a value in response to a received command, and send a value
in response to an event (trap).

SNMPv2c adds to the above the ability to retrieve a large number of objects in response to a
single request.

SNMPv3 adds strong security features including encryption; a shared password key is utilized.
Secure device monitoring over the Internet is possible. In addition to the commands noted as
supported above, there is a command to synchronize with a remote management station.

The pages that follow describe the different fields required to set up SNMP on the LTECube.
MIBS may be requested from Microhard Systems Inc.

The MIB file can be downloaded directly from the unit using the ‘Get MIB File’ button on the
Admin > SNMP menu.

© Microhard 159
4.0 Configuration

SNMP Settings

Image 4-12-4: Admin > SNMP

SNMP Agent Status

If disabled, an SNMP service is not provided from the device. Values (selection)
Enabled, the device - now an SNMP agent - can support SNMPv1, v2,
& v3. Enable / Disable

Read Only Community Name

Effectively a plain-text password mechanism used to weakly Values (string)
authenticate SNMP queries. Being part of the community allows the
SNMP agent to process SNMPv1 and SNMPv2c requests. This public
community name has only READ priority.

© Microhard 160
4.0 Configuration

Read Only Community Name

Also a plain-text password mechanism used to weakly authenticate Values (string)
SNMP queries. Being part of the community allows the SNMP agent to
process SNMPv1 and SNMPv2c requests. This community name has private
only READ/WRITE priority.

Listening Port
Set the UDP port used for the SNMP protocol. Values (UDP Port)
161

SNMP Version
Select the SNMP version used for Set/Get events and SNMP traps Values (selection)
events.
Version 1
Version 2
Version 3

SNMP V3 User Name

Defines the user name for SNMPv3. Values (string)
V3user

V3 User Read Write Limit

Defines accessibility of SNMPv3; If Read Only is selected, the Values (selection)
SNMPv3 user may only read information; if Read Write is selected, the
SNMPv3 user may read and write (set) variables. Read Only / Read Write

V3 User Authentication Level

Defines SNMPv3 user’s authentication level: Values (selection)
NoAuthNoPriv: No authentication, no encryption.
AuthNoPriv: Authentication, no encryption. NoAuthNoPriv
AuthPriv: Authentication, encryption. AuthNoPriv
AuthPriv

V3 Authentication Protocol
Set the SNMP V3 Authentication Protocol. Only valid when V3 User Values (selection)
Authentication Level set to AuthNoPriv or AuthPriv.
MD5
SHA

V3 User Authentication Password

SNMPv3 user’s authentication password. Only valid when V3 User Values (string)
Authentication Level set to AuthNoPriv or AuthPriv.
00000000

© Microhard 161
4.0 Configuration

V3 Privacy Protocol
Set the SNMP V3 Privacy Protocol. Only valid when V3 User Values (selection)
Authentication Level set to AuthPriv.
DES
AES

V3 User Privacy Password

SNMPv3 user’s encryption password. Only valid when V3 User Values (string)
Authentication Level set to AuthPriv (see above).
00000000

SNMP Trap Settings

SNMP Trap Status

Enable SNMP Traps to be set when SNMP trap events are triggered. Values (selection)
Disable / Enable

Trap Community Name

The community name which may receive traps. Values (string)
TrapUser

Trap Manage Host IP

Defines a host IP address where traps will be sent to (e.g. SNMP Values (IP Address)
management system PC IP address).
0.0.0.0

Auth Failure Traps

If enabled, an authentication failure trap will be generated upon Values (selection)
authentication failure.
Disable / Enable

Trap Selection
Enable/Select which SNMP traps that should be sent when the modem Values (varies)
detects an event:
RSSI Threshold: 90 (-dBm)
RSSI - Set the RSSI threshold and Interval of when to send traps. Interval: 90
Roaming - Send a trap when unit enters Roaming status. Roaming Interval: 90
WAN IP - Send SNMP trap when WAN IP is changed.

© Microhard 162
4.0 Configuration

4.12.4 Admin > Discovery

Microhard Radios employ a discovery service that can be used to detect other Microhard Radio’s on a
network. This can be done using a stand alone utility from Microhard System’s called ‘IP Discovery’ or from
the Admin > Discovery menu. The discovery service will report the MAC Address, IP Address, Description,
Product Name, Firmware Version, Operating Mode, and the SSID.

Image 4-12-5: Admin > Discovery Settings

Discovery Service Status

Use this option to disable or enable the discovery service. Values (selection)
Disable / Enable

Server Port Settings

Specify the port running the discovery service on the LTECube unit. Values (Port #)
20097

Network Discovery
The Network discovery tool allows the LTECube to send a broadcast to all Microhard Cellular units on the
same network. Other units on the network will respond to the broadcast and report their MAC address, IP
address (With a hyperlink to that units WebUI page), description, firmware version.

The discovery service can be a useful troubleshooting tool and can be used to quickly find and indentify
other units on the network.

© Microhard 163
4.0 Configuration

4.12.6 System > Logout

The logout function allows a user to end the current configuration session and prompt for a login
screen.

Image 4-12-6: System > logout

© Microhard 164
5.0 AT Command Line Interface

5.1 AT Command Overview

Telnet can be used to access the AT Command interface of the LTECube. The default port is TCP Port 23.
A telnet session can be made to the unit using any Telnet application (Windows Telnet, Tera Term,
ProComm etc). Once communication is established, a login is required to continue.

Telnet in Windows 7/10

may not installed by
default, to use Telnet, first
go to “Add/Remove
Windows Features” on
your PC and add the
Telnet Client. Image 5-1: Establishing a Telnet Session

A session can be made to the WAN IP Address (if allowed in the firewall settings) for remote configuration,
or to the local RJ45 interface.

Once a session is established a login is required to continue. The default login is admin, and the password
is admin. Once verified, the AT Command Line Interface menu is shown and AT Commands can now be
issued. (Type “?” or Help to list the commands).

The factory default

network settings:

IP: 192.168.168.1
Subnet: 255.255.255.0
Gateway: 192.168.168.1

Image 5-2: Telnet AT Command Session

© Microhard 165
5.0 AT Command Line Interface

5.2 AT Command Syntax

The follow syntax is used when issuing AT Commands on the LTECube

- All commands start with the AT characters and end with the <Enter> key
- Microhard Specific Commands start with +M
- Help will list top level commands (ATL will list ALL available AT Commands)
- To query syntax of a command: AT+<command_name>=?
- Syntax for commands that are used only to query a setting:
AT<command_name>
- Syntax for commands that can be used to query and set values:
AT<command_name>=parameter1,parameter2,… (Sets Values)
AT<command_name>? (Queries the setting)

Query Syntax:
AT+MSMNAME=? <Enter>
+MSMNAME: Command Syntax: AT+MSMNAME=<Modem_Name>
Parameter:
<Modem_Name> : 1 - 64 characters. Must be alphanumeric or dots(.), or dashes(-)
or underscores(_)
OK

Setting a value:
AT+MSMNAME=LTECube <Enter>
OK

Query a setting:
AT+MSMNAME? <Enter>
Host name:LTECube
OK

A screen capture of the above commands entered into a unit is shown below:

Image 5-3: AT Command Syntax

Once AT commands are entered, they must be saved into the file system to enable the changes.
AT&W Saves changes.
ATO or ATA Exits the AT Command Line Interface, if used before AT&W,
changes are discarded.

© Microhard 166
5.0 AT Command Line Interface

5.3 Supported AT Commands

Basic AT Commands
AT Command Description Syntax Effect
AT AT echo OK AT <enter> Immediate

ATE0 Disable echo ATE0 <enter> Immediate

ATE1 Enabled local echo ATE1 <enter> Immediate

ATH Show a list of previously run com- ATH <enter> Immediate

mands

ATL Show a list of all available AT Com- ATL <enter> Immediate

mands

AT&R Read modem profile to editable pro- AT&R <enter> Immediate

file. (Reserved)

AT&V Read modem active profile AT&V <enter> Immediate

AT&W Enable configuration changes that AT&W <enter> Immediate

have been entered

ATA Quit. Exits AT command session and ATA <enter> Immediate

returns to login prompt

ATO Quit. Exits AT command session and ATO <enter> Immediate

returns to login prompt

Administrative AT Commands
AT Command Description Syntax Effect
AT+MAEURD1 Get/Set Event UDP Report No.1 AT+MAEURD1[=<Mode>[,<Remote IP>,<Remote Port>,<Interval Time>[,<Interfaces>]]] AT&W
AT+MAEURD2 Get/Set Event UDP Report No.2 Mode : 0 Disable
AT+MAEURD3 Get/Set Event UDP Report No.3 1 Modem Event Report
2 SDP Event Report
3 Management Report
Remote IP : valid IP address
Remote Port : 0 to 65535
Interval Time: 0 to 65535 seconds
Interfaces : (optional) 0 Disable; 1 Enable
Modem, Carrier for Modem Event Report
Radio, Ethernet, Carrier and VPN for Management Report

AT+MANMSR Get/Set NMS Report AT+MANMSR[=<Mode>[,<NMS Server/IP>,<Remote Port>,<Interval Time> AT&W

[,<Interfaces>]]]
Mode : 0 Disable
1 Enable
NMS Server/IP: 1 to 63 characters
Remote Port : 0 to 65535
Interval Time: 0 to 65535 seconds
Interfaces : (optional) 0 Disable; 1 Enable
Radio, Ethernet, Carrier and VPN for Management Report

AT+MANMSSRV Get/Set NMS Server AT+MANMSSRV[=<Server>,<Name>,<Password>,<Confirm Password>] AT&W

<Server>:
NMS Server/IP. 1 to 63 characters
<Name>:
Domain Name. 1 to 63 characters
<Password>:
Domain Password. 5 to 64 characters
<Confirm Password>:
Same as <Password>. 5 to 64 characters

AT+MAWSCLIENT Get/Set Web Service Client AT+MAWSCLIENT[=<Mode>[,<ServerType>,<Port>,<UserName>,<Password>,<Interval>]] AT&W

<Mode>:
0 - Disable
1 - Enable
<ServerType>:
0 - https
1 - http
<Port>:
1 to 65535. Default is 9998
<UserName>:
1 to 63 characters
<Password>:
5 to 64 characters
<Interval>:
In minute. 1 to 65535 minutes.

© Microhard 167
5.0 AT Command Line Interface

Administrative AT Commands (Continued)

AT Command Description Syntax Effect
AT+MADISS Get/Set discovery service used by the AT+MADISS[=<Mode>[,<Port>]] AT&W
modem Mode:
0 - Disable
1 - Discoverable
Port:
1 to 65535. Default is 20097

AT+MASNMP Get/Set SNMP service AT+MASNMP[=<Mode>[,<ROCommunity>,<RWCommunity>,<Port>,<Version>]] AT&W

<Mode>:
0 - Disable
1 - Enable
<ROCommunity>: Read Only Community Name
1 to 32 characters
<RWCommunity>: Read Write Community Name
1 to 32 characters
<Port>: Listening Port
1 to 65535. Default is 161
<Version>: SNMP version
1 - Version 1
2 - Version 2
3 - Version 3 (Use AT+MASNMPV3 to set Authentication and Privacy parameters)

AT+MASNMPV3 Get/Set SNMP Version 3 AT+MASNMPV3=<UserName>,<RWLimit>,<AuthLevel>[,<Auth>,<AuthPassword> AT&W

[,<Privacy>, <PrivacyPassword>]]
<UserName> : V3 User Name
1 to 32 characters
<RWLimit> : V3 User Read Write Limit
0 - Read Only
1 - Read Write
<AuthLevel> : V3 User Authentication Level
0 - NoAuthNoPriv
1 - AuthNoPriv
2 - AuthPriv
<Auth> : V3 Authentication Protocol
0 - MD5
1 - SHA
<AuthPassword> : V3 Authentication Password
5 to 64 characters
<Privacy> : V3 Privacy Protocol
0 - DES
1 - AES
<PrivacyPassword>: V3 Privacy Password
5 to 64 characters
Usage:
NoAuthNoPriv : AT+MASNMPV3=<UserName>,<RWLimit>,0
AuthNoPriv : AT+MASNMPV3=<UserName>,<RWLimit>,1,<Auth>,<AuthPassword>
AuthPriv :
AT+MASNMPV3=<UserName>,<RWLimit>,2,<Auth>,<AuthPassword>,<Privacy>,
<PrivacyPassword>

AT+MASNMPTRAP Get/Set SNMP Trap AT+MASNMPTRAP[=<Mode>[,<Name>,<IP>[,<AuthFailureTraps>]] AT&W

<Mode>:
0 - Disable
1 - Enable
<Name>:
Trap Community Name. 1 to 32 characters
<IP>:
Trap Manage Host IP. Default 0.0.0.0 (Disable)
<AuthFailureTraps>:
0 - Disable
1 - Enable
Usage:
AT+MASNMPTRAP
AT+MASNMPTRAP=0
AT+MASNMPTRAP=1[,<Name>,<IP>[,<AuthFailureTraps>]]

AT+MAIOTSSL Get/Set IoT SSL Management AT+MAIOTSSL[=<Mode>[,<Host>,<Port>,<Registration Code>] AT&W

<Mode>: 0 - Disable, 1 - Enable
<Host>: 2 - 255 characters
<Port>: 1 - 65535
<Registration Code>: 1 - 250 characters

© Microhard 168
5.0 AT Command Line Interface

Firewall AT Commands
AT Command Description Syntax Effect
AT+MFGEN Get/Set firewall general configura- AT+MFGEN[=<Config>[,<Mode>]] AT&W
tion Parameters
Config : 3 - Anti-Spoof
4 - Packet Normalization
5 - Carrier Remote Management
6 - Carrier Request
7 - LAN to Carrier Access Control
Mode : 0 - Disable (Block)
1 - Enable (Allow)

AT+MFDMZ Get/Set firewall DMZ configuration AT+MFDMZ[=<DMZ Source>[,<DMZ Mode>[,<DMZ Server IP>,<Exception Port>,<SNAT>]]] AT&W
Parameters:
DMZ Source : 1 - Carrier
DMZ Mode : 0 - Disable
1 - Enable
DMZ Server IP : Valid IP address
Exception Port : 0 - 65535
Source NAT : 0 - No; 1 - Yes

AT+MFPORTFWD Get/Set firewall Port Forwarding rule AT+MFPORTFWD[=<Name>[,<Operation>[,<Source>,<Internal IP>,<Internal AT&W

Port>,<Protocol>,<External Port>,<SNAT>]]]
Parameters:
Name : Name of Port Forwarding rule, 1 - 64 characters
Operation : ADD - Add a rule
EDIT - Edit a rule
DEL - Delete a rule
Source : 0 - Carrier
1 - WIFI
2 - OpenVPN
Internal IP : Valid IP address
Internal Port : Valid port number, 0 - 65535. 0 - Reset
Protocol : 0 - TCP
1 - UDP
2 - TCPUDP
External Port : Valid port number, 1 - 65535
Source NAT : 0 - No; 1 - Yes
Usage:
AT+MFPORTFWD
AT+MFPORTFWD=<Name>
AT+MFPORTFWD=<Name>,DEL
AT+MFPORTFWD=<Name>,ADD,<Source>,<Internal IP>,<Internal Port>,<Protocol>,
<External Port>,<SNAT>
AT+MFPORTFWD=<Name>,EDIT,<Source>,<Internal IP>,<Internal Port>,<Protocol>,
<External Port>,<SNAT>

AT+MFMAC Get/Set firewall MAC list AT+MFMAC[=<Name>[,<Operation>[,<Action>,<Network>,<Mac Address>,<Mac Address AT&W

Mask>,<Target>]]]
Parameters:
Name : Name of firewall MAC list name, 1 - 64 characters
Operation : ADD - Add a firewall MAC list
EDIT - Edit a firewall MAC list
EDIT - Edit a firewall MAC list
Action : 0 - Accept
1 - Drop
2 - Reject
Network : The network of the source
2 - WIFI
3 - LAN
MAC Address : Valid MAC address
MAC Address Mask: Valid MAC address Mask, operation AND will be applied on
MAC
Address and Mask
Target : Valid MAC address Mask, operation AND will be applied on MAC
Addr
ess and Mask
0 - Input
1 - Forward
2 - Both
Usage:
AT+MFMAC
AT+MFMAC=<Name>
AT+MFMAC=<Name>,DEL
AT+MFMAC=<Name>,ADD,<Action>,<Network>,<Mac Address>,<Mac Address Mask>,
<Target>
AT+MFMAC=<Name>,EDIT,<Action>,<Network>,<Mac Address>,<Mac Address Mask>,
<Target>

© Microhard 169
5.0 AT Command Line Interface

Firewall AT Commands (Continued)

AT Command Description Syntax Effect
AT+MFIP Get/SET firewall IP list AT+MFIP[=<Name>[,<Operation>[,<Action>,<Source>,<IP Address>[,<Prefix>]]]] AT&W
Parameters:
Name : Name of firewall IP list name, 1 - 64 characters
Operation : ADD - Add a firewall IP list
EDIT - Edit a firewall IP list
DEL - Delete a firewall IP list
Action : 0 - Accept
1 - Drop
2 - Reject
Source : 0 - LAN
1 - Carrier
2 - WIFI
3 - OpenVPN
Source IP : Valid IP address
Prefix : 0 ~ 32. 32 (default) - single IP address
Usage:
AT+MFIP
AT+MFIP=<Name>
AT+MFIP=<Name>,DEL
AT+MFIP=<Name>,ADD,<Action>,<Source>,<IP Address>[,<Prefix>]
AT+MFIP=<Name>,EDIT,<Action>,<Source>,<IP Address>[,<Prefix>]

AT+MFRULE Get/Set firewall rule AT+MFRULE[=<Name>[,<Operation>[,<Type>,<Action>,<Source>,<Src IP Format>,<Src AT&W

IP From/Subnet>,<Src IP To/Prefix>,<Destination>,<Dest IP Format>,<Dest IP
From/Subnet>,<Dest IP To/Prefix>,<Dest Port>,<Protocol>]]]
Parameters:
Name : Name of firewall rule name, 1 - 64 characters
Operation : ADD - Add a firewall rule
EDIT - Edit a firewall rule
DEL - Delete a firewall rule
Type : 0 - Input
1 - Output
2 - Forward
Action : 0 - Accept
1 - Drop
2 - Reject
Source : (Must be "Any", if Type is Output)
0 - LAN
1 - Carrier
2 - WIFI
3 - OpenVPN
4 - Any
IP Format : 0 - IP Range
1 - Subnet / Prefix
IP From/Subnet: Valid IP address
IP To/Prefix : Valid IP address or 0 ~ 32 for Prefix
Destination : (Must be "Any", if Type is Input)
0 - LAN
1 - Carrier
2 - WIFI
3 - OpenVPN
4 - Any
IP Format : 0 - IP Range
1 - Subnet / Prefix
IP From/Subnet: Valid IP address
IP To/Prefix : Valid IP address or 0 ~ 32 for Prefix
Port/Range : Port 0 ~ 65535 or Port range specified as 100:200 format
Protocol : 0 - TCP
1 - UDP
2 - TCPUDP
3 - ICMP
4 - Protocol 41
5 - GRE

AT+MFRST Reset to default firewall AT+MFRST <enter> Immediate

© Microhard 170
5.0 AT Command Line Interface

Carrier/Modem AT Commands
AT Command Description Syntax Effect
AT+MMIMEI Get Modem’s IMEI AT+MMIMEI <enter> Immediate
+MMIMEI: 357188080005558

AT+MMIMSI Get Modem’s IMSI AT+MMIMSI <enter> Immediate

+MMIMSI: 302610020063458

AT+MMNETRSSI Get Modem’s RSSI AT+MMNETRSSI <enter> Immediate

+MMNETRSSI: -63

AT+MMBOARDTEMP Get Modem’s Temperature AT+MMBOARDTEMP <enter> Immediate

+MMBOARDTEMP: 47.99

AT+MMWANIP Get Modem’s WAN IP AT+MMWANIP <enter> Immediate

WANIP=10.94.114.117

AT+MMPIPP Get/Set IP-Passthrough AT+MMPIPP[=<Mode>[,<Lease Time>,<IP Address>]] AT&W

Parameters:
Mode: 0 Disable
1 Ethernet
Lease Time : IP-Passthrough DHCP lease time, 2 to 2880, in minutes
IP Address : A virtual IP address set to LAN in ippassthrough Ethernet mode

AT+MMNUM Get modem’s phone number AT+MMNUM <enter> Immediate

+MMNUM: 14034639685

AT+MMIMI Get modem’s IMEI and IMSI AT+MMIMI <enter> Immediate

+MMIMI: MMIMEI:866834040748928, MMIMSI:302610026807830

AT+MMCID Get modem’s SIM Card number AT+MMCID <enter> Immediate

+MMCID: 89302610103036289922

AT+MMAPN Get/Set APN AT+MMAPN[=[<APN>]] AT&W

<APN> : Max 255 characters

AT+MMMGS Send SMS AT+MMMGS=<Phone Number><CR> Immediate

<Phone Number>: Valid phone number
Text is entered and ended by <ctrl-Z/ESC>

AT+MMMGR Read SMS AT+MMMGR=<index> Immediate

<Index> : the index of the message

AT+MMMGL List SMSs AT+MMMGL <enter> Immediate

AT+MMMGD Delete SMSs AT+MMMGD=<index> Immediate

<Index> : the index of the message to be deleted

AT+MMSCMD Get/Set system sms command service AT+MMSCMD=<Mode>[,<Filter Mode>[,<No.1>[,<No.2>[,<No.3>[,<No.4>[,<No.5> AT&W

[<No.6>]]]]]]]
Mode: 0 - Disable
1 - Enable SMS Command
Filter Mode : 0 - Disable
1 - Enable Phone Filter
No.X: Phone Number, where X = [1, 6]

AT+MMSVRCELL Get Serving Cell Information AT+MMSVRCELL <enter> Immediate

+MMSRVCELL:
"servingcell","NOCONN","LTE","FDD",302,610,1B9FF2A,375,900,2,5,5,2BDD,-102,-
18,-61,7,-

AT+MMNEBCELL Get Neighbour Cell Information AT+MMNEBCELL <enter> Immediate

+MMNEBCELL:
"neighbourcell intra","LTE",900,375,-19,-102,-62,0,-,-,-,-,-
"neighbourcell intra","LTE",900,1,-20,-112,-75,0,-,-,-,-,-
"neighbourcell intra","LTE",900,242,-20,-106,-74,0,-,-,-,-,-

© Microhard 171
5.0 AT Command Line Interface

Network AT Commands
AT Command Description Syntax Effect
AT+MNLAN Show/Add/Edit/Delete the network LAN AT+MNLAN AT&W
interface AT+MNLAN=<LAN Name>
AT+MNLAN=<LAN Name>,DEL
AT+MNLAN=<LAN Name>,ADD/EDIT,<Protocol>[,<IP>,<Netmask>] Where <Protocol>=0
AT+MNLAN=<LAN Name>,ADD/EDIT,<Protocol> Where <Protocol>=1 or 3
AT+MNLAN=<LAN Name>,EDIT,<Protocol>[,<IP>,<Netmask>] Where <Protocol>=2 and
<LAN Name>="lan"
Parameters:
LAN Name : Name of Network LAN interface. System built-in one is "lan"
Operation : ADD - Add a new LAN interface
EDIT - Edit an exsiting LAN interface
DEL - Delete an existing LAN interface
Protocol : 0 - Static IP
1 - DHCP with LAN alias disabled
2 - DHCP with LAN alias enabled, only for "lan"
IP Address : Valid IP address
Netmask : Valid netmask

AT+MNLANDHCP Get/Set LAN DHCP server on LAN inter- AT+MNLANDHCP=<LAN Name>[,<Mode>[,<Start IP>,<Limit>,<Lease Time>[,<Alt. Gate- AT&W
face way>, <Pre. DNS>,<Alt. DNS>,<WINS/NBNS Servers>,<WINS/NBT
Node>]]]
Parameters:
LAN Name : Name of Network LAN interface
Mode : 0 - Disable DHCP Server
1 - Enable DHCP Server
Start IP : The starting address DHCP assignable IP Addresses
Limit : The maximum number of IP addresses. min=1 max=16777214
Lease Time : The DHCP lease time in minutes. 2~2147483647 minutes. 0
means'infinity'
Alt. Gateway : Alternate Gateway for DHCP assigned devices if the default
gateway is not to be used
Pre. DNS : Preferred DNS server address to be assigned to DHCP devices
Alt. DNS : Alternate DNS server address to be assigned to DHCP devices
WINS/NBNS Server : WINS/NBNS Servers
WINS/NBT Node : WINS/NBT Node Type
0 - none
1 - b-node
2 - p-node
3 - m-node
4 - h-node

AT+MNLANSTP Get/Set the network LAN inetrafce: AT+MNLANSTP=<LAN Name>[,<STP>] AT&W

Spanning Tree (STP) Parameters:
LAN Name : Name of Network LAN interface
Spanning Tree : 0 - Off
1 - On

AT+MNLANIGMP Get/Set the network LAN interface: AT+MNLANIGMP=<LAN Name>[,<IGMP Snooping>] AT&W
IGMP Snooping Parameters:
LAN Name : Name of Network LAN interface
IGMP Snooping : 0 - Off
1 - On

AT+MNLANDNS Get/Set the network LAN interface: AT+MNLANDNS=<LAN Name>[,<Mode>[,<Primary DNS>,<Secondary DNS>]] AT&W
DNS Usage:
AT+MNLANDNS=<LAN Name>
AT+MNLANDNS=<LAN Name>,<Mode> Where <Mode>=0
AT+MNLANDNS=<LAN Name>,<Mode>[,<Primary DNS>,<Secondary DNS>] Where <Mode>=1
Parameters:
LAN Name : Name of Network LAN interface
Mode : 0 - Auto
1 - Manual
Primary DNS : Valid IP Address or 0 (Reset)
Secondary DNS : Valid IP address or 0 (Reset)

© Microhard 172
5.0 AT Command Line Interface

Network AT Commands (Continued)

AT Command Description Syntax Effect
AT+MNIPMAC Show/Add/Delete/Release/ReleaseAll AT+MNIPMAC[=<Operation>[,<Name>[,<IP Address>,<MAC Address>]]] AT&W
the MAC-IP address binding Usage:
AT+MNIPMAC
AT+MNIPMAC=SHOW,<Name>
AT+MNIPMAC=ADD,<Name>,<IP Address>,<MAC Address>
AT+MNIPMAC=DEL,<NAME>
AT+MNIPMAC=RELEASE,<NAME>
AT+MNIPMAC=RELEASEALL
Parameters:
Operation : SHOW - Show the details of the MAC-IP address binding
ADD - Add a new MAC-IP address binding
DEL - Delete an existing MAC-IP address binding
RELEASE - Release the active DHCP lease
RELEASEALL - Release all active DHCP leases
Name : Name of the MAC-IP binding, 1-64 characters
IP Address : Valid IP address
MAC Address: The physical MAC address of the device or interface

AT+MNEMAC Get the MAC address of the local AT+MNEMAC <enter> Immediate
Ethernet interface Sample Output:
+MNEMAC: "00:0F:92:02:F9:0F"
OK

AT+MNPORT Get/Set the Ethernet port configura- AT+MNPORT[=<Ethernet Port>[,<Mode>[,<Auto Negotiation>,<Speed>,<Duplex>]]] AT&W
tion Parameters:
Ethernet Port : 0 - LAN
Mode : 0 - Auto
1 - Manual
Auto-Negotiation : 0 - Off
: 1 - On
Speed : 0 - 10 Mbit/s
1 - 100 Mbit/s
Duplex : 0 - Full
1 - Half

© Microhard 173
5.0 AT Command Line Interface

Network AT Commands (Continued)

AT Command Description Syntax Effect
AT+MNSTATUS Get the network status AT+MNSTATUS <enter> Immediate
LAN Port Status
General Status
IP Address : 192.168.168.1
Connection Type : static
Subnet Mask : 255.255.255.0
MAC Address : 00:0F:92:04:1B:2B
Traffic Status
Receive bytes : 193.121KB
Receive packets : 2317
Transmit bytes : 164.023KB
Transmit packets : 1209
4G Port Status
General Status
IP Address : 100.74.44.84
Connection Type : dhcp
Subnet Mask : 255.255.255.248
MAC Address : 00:0F:92:FE:00:01
Traffic Status
Receive bytes : 78.654KB
Receive packets : 554
Transmit bytes : 77.972KB
Transmit packets : 833

Kernel IP routing table

Destination Gateway Subnet Mask Flags Metric Ref Use Iface
0.0.0.0 100.74.44.81 0.0.0.0 UG 0 0 0 br-wan2
10.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 br-wan2
100.74.44.80 0.0.0.0 255.255.255.248 U 0 0 0 br-wan2
192.168.168.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan

AT+MNDDNSE Get/Set DDNS Mode AT+MNDDNSE=<Mode> AT&W

Parameter:
Mode: 0 - Disable
1 - Enable

AT+MNDDNS Get/Set DDNS Settings AT+MNDDNS=<Network>,<Periodic Update>,<Service>,<User Name>,<Password>,<Host> AT&W

or <Record Number>[,<Url>]
Parameters:
Network : 0 - Auto
1 - Carrier
Periodic Update : 0 - Disable
1 - 5 minutes
2 - 15 minutes
3 - 60 minutes
4 - 4 hours
5 - 8 hours
6 - 24 hours
Service Type : 0 - changeip
1 - dyndns
2 - eurodyndns
3 - hn
4 - noip
5 - ods
6 - ovh
7 - regfish
8 - tzo
9 - zoneedit
10 - customized_ddns
11 - DNSmadeEasy
User Name : 1 - 64 characters
Password : 1 - 64 characters
Host : 1 - 200 characters, for any services except DNSmadeEasy
Record Number : 1 - 200 characters, for DNSmadeEasy only
Url : 1 - 200 characters, for customized_ddns

AT+MNNETSP Get download and upload speed AT+MNNETSP[=<Netperf Server>[,<Duration(seconds)>] Immediate

AT+MNNETSP[=4,<Netperf Server Address>[,<Netperf Server Port>,<Duration
(seconds)>]
Parameters:
<NETPERF Server> : 0 - netperf.bufferbloat.net
1 - netperf-east.bufferbloat.net
2 - netperf-west.bufferbloat.net
3 - netperf-eu.bufferbloat.net
4 - customerserver
<Duration> : 1-60
<Netperf Server Address> : customer netperf server address
<Netperf Server Port> : 0-65535

AT+MNPINGTM Get ping time AT+MNPINGTM[=<Ping Server>[,<Ping Count>[,<Ping Size>]]] Immediate

Parameters:
<Ping Server> : Valid IP Address
<Ping Count> : > 0, integer count
<Ping Size> : 5-15000

© Microhard 174
5.0 AT Command Line Interface

System AT Commands
AT Command Description Syntax Effect
AT+MSCNTO Get/Set the console timeout AT+MSCNTO=<Timeout_s> AT&W
Parameter:
<Timeout_s> : 30 to 65535 in seconds, 0-Disable

AT+MSPWD Set password AT+MSPWD=<New Password>,<Confirm Password> AT&W

Parameters:
<New Password> : 5-64 characters except space
<Confirm Password> : Same as <New Password>

AT+MSGMI Get manufacturers identification AT+MSGMI <enter> Immediate

Sample Output:
+MSGMI: 2014-2022 Microhard Systems Inc.

AT+MSSYSI Get system summary information AT+MSSYSI <enter> Immediate

+MSSYSI:
Carrier:
MMIMEI : 866834040748928
SIMID : 89302720396936865893
MMIMSI : 302720393836878
Status : Connected
Network : ROGERS
RSSI : -59
MAC : 00:0F:92:FE:00:01
IP : 99.210.76.156
MASK : 255.255.255.255
LAN Port:
MAC : 00:0F:92:08:D3:07
IP : 192.168.168.1
MASK : 255.255.255.0
System:
Device : LTECube-CAT4-WIFI-MKT
Product : LTECube-CAT4-WIFI
Image : PWii
Hardware : Rev A
Software : v1.3.0 build 1086
Copyright : 2014-2022 Microhard Systems Inc.
System Time : Thu Feb 2 11:11:41 2023
Temperature : 53.00
Voltage(V) : N/A

AT+MSGMR Get modem Record information AT+MSGMR <enter> Immediate

+MSGMR:
Hardware Version : Rev A
Software Version : v1.3.0 build 1086
Copyright : 2014-2022 Microhard Systems Inc.
System Time : Thu Feb 2 11:12:09 2023

AT+MSIMG Get the image status for both active AT+MSIMG <enter> Immediate
and inactive images. Active Version : v1.3.0-r1086
Active Build Time : 2022-09-22 11:17:52
Inactive Version : v1.3.0-r1086
Inactive Build Time : 2022-09-22 11:17:52

AT+MSMNAME Get/Set modem Name setting AT+MSMNAME=<Modem_Name> AT&W

Parameter:
<Modem_Name> : 1 - 64 characters. Must be alphanumeric or dots(.), or dashes
(-) or underscores(_)

AT+MSRTF Reset the modem to the factory de- AT+MSRTF=<Action> AT&W

fault settings from non-volatile (NV) Parameter:
memory <Action>: 0 - Pre-set action
1 - Confirm action

AT+MSREB Reboot the modem AT+MSREB <enter> Immediate

Sample Output:
Rebooting...
OK

AT+MSNTP Get/Set NTP server AT+MSNTP[=<Mode>[,<Server>,<Port>,<Client Interval>]] AT&W

Parameters:
<Mode> : 0 - Local Time; 1 - NTP
<Server> : Valid IP Address or Name
<Port> : 1 to 65535. Default is 123
<Client Interval> : 15 to 65535 in seconds, 0-Disable

AT+MSNTPSVR Get/Set local NTP server AT+MSNTPSVR=<Mode> AT&W

Parameters:
<Mode> : 0 - Disable ; 1 - Enable

AT+MSSYSLOG Get/Set Syslog server settings AT+MSSYSLOG[=<Server>[,<Port>]] AT&W

Parameters:
<Server> : Valid IP Address or Name. 0.0.0.0 - Disable. 1 to 256 characters
<Port> : 1 to 65535. Default is 514

© Microhard 175
5.0 AT Command Line Interface

System AT Commands (Continued)

AT Command Description Syntax Effect
AT+MSSERVICE Get/Set service status and port AT+MSSERVICE[=<Service>[,<Mode>[,<Port>]]] Immediate
Parameters:
<Service>: 0 - FTP
1 - Telnet
2 - SSH
3 - Microhard Sh
<Mode>: 0 - Disable
1 - Enable
<Port>: 1 to 65535. For Telnet (23 by default) and SSH (22 by default) only
Note: Not require AT&W

AT+MSWEBUI Get/Set Web UI protocol and port AT+MSWEBUI[=<Mode>[,<HTTP Port>][,<HTTPS Port>]]] Immediate
Parameters:
<Mode>: 0 - HTTP/HTTPS
1 - HTTP
2 - HTTPS
3 - Disable
<HTTP Port>: 1 to 65535. 80 by default
<HTTPS Port>: 1 to 65535. 443 by default
Usages:
AT+MSWEBUI
AT+MSWEBUI=<Mode>[,<HTTP Port>,<HTTPS Port>] when <Mode>=0
AT+MSWEBUI=<Mode>[,<HTTP Port>] when <Mode>=1
AT+MSWEBUI=<Mode>[,<HTTPS Port>] when <Mode>=2
AT+MSWEBUI=<Mode> when <Mode>=3
Note: Not require AT&W

AT+MSKA Get/Set keep-alive mode AT+MSKA[=<Mode>[,<Traffic Check>,<CLI Activity>,<Web UI Activity>]] AT&W

Parameters:
Mode : 0 - Disable
1 - Enable
Traffic Check : 0 - Disable
1 - Enable
CLI Activity : 0 - Disable
1 - Enable
Web UI Activity: 0 - Disable
1 - Enable

AT+MSKAS Get/Set keep-alive settings AT+MSKAS[=<Type>,<Host Name>,<Interval>,<Retry>[,<HTTP Port>]] AT&W

Parameters:
Type : 0 - ICMP
1 - HTTP
2 - DNS Lookup
Host Name : Valid host name, 1 to 256 characters
Interval : Keepalive Interval in second, 60 to 60000
Retry : Keepalive Retry, 10 to 200
HTTP Port : Valid HTTP Port, 0 to 65535

AT+MSTR Get Traffic status on interfaces AT+MSTR[=<Interfaces>] Immediate

<Interfaces> :
1 - LAN
Sample Output:

AT+MSTR=1 <enter>
LAN
RX packets: 4454
RX bytes : 404312
TX packets: 3462
TX bytes : 834448

AT+MSOPTRST Reset to default configurations with AT+MSOPTRST=<Action>,<Keep Carrier Settings>,<Keep IoT Settings>,<Wipeout data Immediate
options: and logs>
1. Keep Carrier Settings Parameter:
2. Keep IoT Setting <Action>: 0 - Pre-set action and options
3. Wipeout data and logs 1 - Confirm action and options
<Keep Carrier Settings> : 0 - Disable; 1 - Enable
<Keep IoT Settings> : 0 - Disable; 1 - Enable
<Wipeout data and logs> : 0 - Disable; 1 - Enable

© Microhard 176
5.0 AT Command Line Interface

Wireless (Radio) AT Commands

AT Command Description Syntax Effect
AT+MWRADIO Get/Set radio status, On or Off AT+MWRADIO[=<Radio>] AT&W
<Radio>
0 - Off 1 - On

AT+MWMODE Get/Set Radio Mode AT+MWMODE[=<Mode>] AT&W

<Mode>
0 - 802.11B ONLY
1 - 802.11BG
2 - 802.11NG

AT+MWDISTANCE Get/Set radio Wireless Distance AT+MWDISTANCE[=<Distance>] AT&W

<Distance>
1 - 30000 in meter

AT+MWTXPOWER Get/Set radio Tx power AT+MWTXPOWER[=<Tx Power>] AT&W

<Tx Power>
7 - 7 dbm
8 - 8 dbm
9 - 9 dbm
10 - 10 dbm
11 - 11 dbm
12 - 12 dbm
13 - 13 dbm
14 - 14 dbm
15 - 15 dbm
16 - 16 dbm
17 - 17 dbm
18 - 18 dbm
19 - 19 dbm
20 - 20 dbm
21 - 21 dbm
22 - 22 dbm
23 - 23 dbm
24 - 24 dbm
25 - 25 dbm
26 - 26 dbm
27 - 27 dbm
28 - 28 dbm
29 - 29 dbm
30 - 30 dbm

AT+MWCHAN Get/Set radio channel (varies by AT+MWCHAN[=<Channel>] AT&W

mode) Available radio channels for mode 11ng and high throughput mode HT20:
0 - auto
1 - 1 (2412 MHz)
2 - 2 (2417 MHz)
3 - 3 (2422 MHz)
4 - 4 (2427 MHz)
5 - 5 (2432 MHz)
6 - 6 (2437 MHz)
7 - 7 (2442 MHz)
8 - 8 (2447 MHz)
9 - 9 (2452 MHz)
10 - 10 (2457 MHz)
11 - 11 (2462 MHz)

AT+MWHTMODE Get/Set radio high throughput mode AT+MWHTMODE[=<High Throughput Mode>] AT&W
<High Throughput Mode>
0 - HT20
1 - HT40-
2 - HT40+
3 - Force HT40-
4 - Force HT40+

AT+MWMPDUAGG Get/Set radio MPDU Aggregation AT+MWMPDUAGG[=<MPDU Aggregation>] AT&W

<MPDU Aggregation>
0 - Disable
1 - Enable

AT+MWSHORTGI Get/Set radio short GI AT+MWSHORTGI[=<Short GI>] AT&W

<Short GI>
0 - Disable
1 - Enable

AT+MWHTCAPAB Get/Set radio HT capabilities info AT+MWHTCAPAB <enter> Immediate

+MWHTCAPAB: HT Capabilities Info-SHORT-GI-20 SHORT-GI-40 RX-STBC1 DSSS_CCK-40

AT+MWAMSDU Get radio maximum AMSDU (byte) AT+MWAMSDU <enter> Immediate

+MWAMSDU: Maximum AMSDU (byte) - 3839

AT+MWAMPDU Get radio maximum AMPDU (byte) AT+MWAMPDU <enter> Immediate

+MWAMPDU: Maximum AMPDU (byte) - 65535

AT+MWRTSTHRESH Get/Set radio RTS Threshold AT+MWRTSTHRESH[=<RTS Threshold>] AT&W

<RTS Threshold>:
0 Disabled
256-2346 Enabled with the value

© Microhard 177
5.0 AT Command Line Interface

Wireless (Radio) AT Commands (Continued)

AT Command Description Syntax Effect
AT+MWFRAGTHRESH Get/set radio Fragment threshold AT+MWFRAGTHRESH[=<Fragmentation Threshold>] AT&W
<Fragmentation Threshold>:
0 Disabled
256-2346 Enabled with the value

AT+MWCCATHRESH Get/Set radio CCA Power Threshold AT+MWCCATHRESH[=<CCA Threshold>] AT&W

<CCA Threshold>:
Range of values: 4-127

AT+MWIFACE List/Add/Delete radio virtual inter- AT+MWIFACE=<Operation>[,<Index>] AT&W

face <Operation>
SHOW - List one or all radio virtual interface(s)
ADD - Add one radio virtual interface with default settings
DEL - Delete one radio virtual interface
<Index>
Radio Virtual Interface Index: 0-3
Usage:
AT+MWIFACE=SHOW[,<Index>]
AT+MWIFACE=ADD
AT+MWIFACE=DEL,<Index>

AT+MWNETWORK Get/Set radio virtual interface: AT+MWNETWORK[=<Index>[,<Network>]] AT&W

Network <Index>
Radio Virtual Interface Index: 0-3
<Network>
Radio Virtual Interface Network:
0 - LAN
1 - WAN
2 - WIFI

AT+MWSSID Get/Set radio virtual interface: SSID AT+MWSSID[=<Index>[,<SSID>]] AT&W

<Index>
Radio Virtual Interface Index: 0-3
<SSID>
Radio Virtual Interface SSID: 1-32 characters

AT+MWDEVICEMODE Get/Set virtual interface: Mode AT+MWDEVICEMODE[=<Index>[,<Device Mode>]] AT&W

<Index>
Radio Virtual Interface Index: 0-3
<Device Mode>
Radio Virtual Interface Mode:
0 - Access Point
1 - Client
2 - Repeater

AT+MWRATE Get/Set radio virtual interface: TX AT+MWRATE[=<Index>[,<TX bitrate>]] AT&W

bitrate <Index>
Radio Virtual Interface Index: 0-3
<TX bitrate>
Radio Virtual Interface TX bitrate for 802.11NG
0 - auto
1 - mcs-0
2 - mcs-1
3 - mcs-2
4 - mcs-3
5 - mcs-4
6 - mcs-5
7 - mcs-6
8 - mcs-7

AT+MWWDS Get/Set radio interface: WDS AT+MWWDS[=<Index>[,<WDS>]] AT&W

<Index>
Radio Virtual Interface Index: 0-3
<WDS>
0 - Off
1 - On

AT+MWSSIDBCAST Get/Set radio virtual interface: AT+MWSSIDBCAST[=<Index>[,<ESSID Broadcast>]] AT&W

ESSID Broadcast <Index>
Radio Virtual Interface Index: 0-3
<ESSID Broadcast>
Radio Virtual Interface ESSID Broadcast:
0 - Off
1 - On

AT+MWAPISOLATION Get/Set radio virtual interface: AP AT+MWAPISOLATION[=<Index>[,<AP Isolation>]] AT&W

Isolation <Index>
Radio Virtual Interface Index: 0-3
<AP Isolation>
Radio Virtual Interface AP Isolation:
0 - Off
1 - On

© Microhard 178
5.0 AT Command Line Interface

Wireless (Radio) AT Commands (Continued)

AT Command Description Syntax Effect
AT+MWENCRYPT Get/Set radio virtual interface: PSK: AT+MWENCRYPT[=<Index>[,<Encryption Type>[,<WPA PSK>]]] AT&W
Encryption Type RADIUS in Client: AT+MWENCRYPT[=<Index>[,<Encryption Type>[,<RADIUS Serv-
erKey>,<RADIUS Identity]]]
RADIUS in Access Point: AT+MWENCRYPT[=<Index>[,<Encryption Type>[,<RADIUS
ServerKey>, <RADIUS IP Address>, <RADIUS Port>]]]
Parameters:
<Index>: Radio Virtual Interface Index: 0-3
<Encryption Type>: 0 - Disabled
1 - WPA (PSK)
2 - WPA2 (PSK)
3 - WPA+WPA2 (PSK)
4 - WPA Enterprise (RADIUS)
5 - WPA2 Enterprise (RADIUS)
6 - WPA+WPA2 Enterprise (RADIUS)
<WPA PSK>: 8 ~ 64 characters
<RADIUS Server Key>: 4 ~ 63 characters
<RADIUS IP Address>: Valid IP address
<RADIUS Port>: Valid port, 0 to 65535
<RADIUS Identity>: 4 ~ 63 characters

AT+MWSCAN Get radio scanning information AT+MWSCAN <enter> AT&W

(client mode) Noise Floor: -93 dBm
1,"BP_AP_188",00:0F:92:FE:03:1F,11,2462,70/70,-32,Master,WPA2 PSK (CCMP)
2,"ASUS-WIFI",38:2C:4A:A1:44:E0,6,2437,70/70,-40,Master,WPA2 PSK (CCMP)
3,"BP-C",00:0F:92:FE:03:26,1,2412,57/70,-53,Master,WPA2 PSK (CCMP)
4,"Microguest",04:F0:21:19:85:CC,9,2452,55/70,-55,Master,WPA2 PSK (CCMP)
5,"BP_AP_178",00:0F:92:FA:38:1B,11,2462,70/70,-31,Master,WPA2 PSK (CCMP)
6,"SEC_LinkShare_253277",D0:66:7B:A3:72:EB,4,2427,51/70,-59,Master,WPA2 PSK
(CCMP)
7,"work2901",00:15:6D:68:3D:0C,4,2427,59/70,-51,Master,mixed WPA/WPA2 PSK
(TKIP, CCMP)
8,"testaaa2",00:0F:92:FF:FF:FF,8,2447,42/70,-68,Master,WPA2 PSK (CCMP)
9,"Bp170Wifi",02:0F:92:FF:FF:FF,5,2432,42/70,-68,Master,WPA2 PSK (CCMP)
10,"MyNetwork",04:F0:21:04:8D:69,1,2412,41/70,-69,Master,WPA2 PSK (CCMP)
11,"AndrewW",74:D0:2B:89:0B:50,6,2437,35/70,-75,Master,WPA2 PSK (CCMP)
12,"HPJ310a.4A61D8",02:2E:EE:7F:63:7F,6,2437,51/70,-59,Master,none
13,"Hanif's Wi-Fi Network",34:12:98:09:E9:86,6,2437,33/70,-77,Master,WPA2 PSK
(CCMP)
14,"Drug Shack",F8:E9:03:C0:EC:98,1,2412,26/70,-84,Master,mixed WPA/WPA2 PSK
(TKIP, CCMP)
15,"Bp170Wifi",00:0F:92:FA:38:F8,5,2432,36/70,-74,Master,WPA2 PSK (CCMP)
16,"SHAW-C31630",A8:4E:3F:C3:16:38,1,2412,30/70,-80,Master,WPA2 PSK (TKIP,
CCMP)
17,"SHAW-E14540",F0:F2:49:E1:45:48,1,2412,32/70,-78,Master,mixed WPA/WPA2 PSK
(TKIP, CCMP)

AT+MWRSSI Get radio RSSI AT+MWRSSI <enter> AT&W

192.168.168.161 8C:F5:A3:0F:0A:33 -31 dBm

© Microhard 179
5.0 AT Command Line Interface

GPS AT Commands
AT Command Description Syntax Effect
AT+MGPSSTA Get/Set GPS status AT+MGPSSTA[=<Mode>] AT&W
Parameters:
Mode: 0 Disable
1 Enable

AT+MGPSPORT Get/Set GPS port AT+MGPSPORT[=<Port Number>] AT&W

Parameters:
Port Number : 1-65535

AT+MGPSSRC Get/Set GPS status AT+MGPSSRC[=<GPS Source>] AT&W

Parameters:
GPS Source : 1 - Standalone GPS(Built-in)

AT+MGPSNMEA GPS Essential NMEA AT+MGPSNMEA <enter> Immediate

+MGPSNMEA:
$GPGGA,,,,,,0,,,,,,,,*66
$GPRMC,,V,,,,,,,,,,N*53

© Microhard 180
Appendix A: Port Forwarding Example (Page 1 of 2)

By completing the Quick Start process, a user should have been able to log in and set up the LTECube to
work with their cellular carrier. By completing this, the modem is ready to be used to access the internet
and provide mobile connectivity. However, one of the main applications of the LTECube is to access
connected devices remotely. In order to do this, the LTECube must be told how to deal with incoming
traffic, where to send it to.

In this section we will talk about port forwarding. Port forwarding is ideal when there are multiple devices
connected to the LTECube, or if other features of the LTECube are required (Firewall, etc). In port
forwarding, the LTECube looks at each incoming Ethernet packet on the WAN and by using the destination
port number, determines where it will send the data on the private LAN . The LTECube does this with each
and every incoming packet.

DMZ (a form of port forwarding) is useful for situations where there are multiple devices connected to the
LTECube, but all incoming traffic is destined for a single device. It is also popular to use DMZ in cases
where a single device is connected but several ports are forwarded.

Consider the following example. A user has a remote location that has several devices that need to be
accessed remotely. The User at PC1 can only see the LTECube directly using the public static IP assigned
by the wireless carrier, but not the devices behind it. In this case the LTECube is acting as a gateway
between the Cellular Network and the Local Area Network of its connected devices. Using port forwarding
we can map the way that data passes through the LTECube.

Wired or Wireless
Devices

Wireless Cellular PC2: 192.168.0.20

Connection Webserver on port 80
Cellular Network/
Internet

LTECube
WAN IP:
PC1: Connected to 74.198.186.193
internet. (Cellular Carrier)

LAN IP: 192.168.0.1 PLC/RTU: 192.168.0.30

Webserver on port 80
Modbus on port 502

IP Camera: 192.168.0.40
Webserver on Port 80

Step 1

Log into the LTECube (Refer to Quick Start), and ensure that the Firewall is configured. This can be found under
Firewall > General. Also ensure that that sufficient Rules or IP lists have been setup to allow specific traffic to pass
through the LTECube. See the Firewall Example in the next Appendix for information on how to allow connections from
an IP or to open ports. Once that is complete, remember to “Submit” the changes.

© Microhard 181
Appendix A: Port Forwarding Example (Page 2 of 2)

Step 2

Determine which external ports (Carrier) are mapped to which internal IP Addresses and Ports (LAN). It is important to
understand which port, accessible on the outside, is connected or mapped to which devices on the inside. For this
example we are going to use the following ports, in this case it is purely arbitrary which ports are assigned, some
systems may be configurable, other systems may require specific ports to be used.

Description WAN IP External Port Internal IP Internal Port

LTECube WebUI 74.198.186.193 80 192.168.0.1 80
PC2 Web Server 74.198.186.193 8080 192.168.0.20 80
PLC Web Server 74.198.186.193 8081 192.168.0.30 80
PLC Modbus 74.198.186.193 10502 192.168.0.30 502
Camera Web Server 74.198.186.193 8082 192.168.0.40 80

Notice that to the outside user, the IP Address for every device is the same, only the port number changes, but on the
LAN, each external port is mapped to an internal device and port number. Also notice that the port number used for the
configuration GUI for all the devices on the LAN is the same, this is fine because they are located on different IP
addresses, and the different external ports mapped by the LTECube (80, 8080, 8081, 8082), will send the data to the
intended destination.

Step 3

Create a rule for each of the lines above. A rules does not
need to be created for the first line, as that was listed simply to
show that the external port 80 was already used, by default, by
the LTECube itself. To create port forwarding rules, Navigate to
the Firewall > Port Forwarding menu. When creating rules,
each rules requires a unique name, this is only for reference
and can be anything desired by the user. Click on the “Add
Port Forwarding” button to add each rule to the LTECube.

Once all rules have been added, the LTECube configuration

should look something like what is illustrated in the screen shot
to the right. Be sure to “Submit” the Port Forwarding list to the
LTECube.

For best results, reboot the LTECube.

Step 4

Configure the static addresses on all attached devices. Port forwarding required that all the attached devices have static
IP addresses, this ensure that the port forwarding rules are always correct, as changing IP addresses on the attached
devices would render the configured rules useless and the system will not work.

Step 5

Test the system. The devices connected to the LTECube should be accessible remotely. To access the devices:

For the Web Server on the PC, use a browser to connect to 74.198.186:193:8080, the result should be as follows:

To access the other devices/services: For the PLC Web Server: 74.198.186.193:8081, for the Camera
74.198.186.193:8082, and for the Modbus on the PLC telnet to 74.198.186.193:10502 etc.

© Microhard 182
Appendix B: VPN Example (Page 1 of 2)

By completing the Quick Start process, a user should have been able to log in and set up the LTECube to
work with their cellular carrier. By completing this, the modem is ready to be used to access the internet
and provide mobile connectivity. However, one of the main applications of the LTECube is to access
connected devices remotely. In addition to Port Forwarding, the LTECube has several VPN capabilities,
creating a tunnel between two sites, allowing remote devices to be accessed directly.

VPN allows multiple devices to be connected to the LTECube without the need to individually map ports to
each device. Complete access to remote devices is available when using a VPN tunnel. A VPN tunnel can
be created by using two LTECube devices, each with a public IP address. At least one of the modems
require a static IP address. VPN tunnels can also be created using the LTECube to existing VPN capable
devices, such as Cisco or Firebox.

Example: LTECube to LTECube (Site-to-Site)

Step 1

Site A Site B

LTECube LTECube
WAN IP Carrier Assigned: WAN IP Carrier As-
A.B.C.D signed: E.F.G.H

Log into each LTECube (Refer to Quick Start) and ensure that the Firewall is configured. This can be found under
Firewall > General. Ensure that sufficient Rules or IP lists have been setup to allow specific traffic to pass through the
LTECube. Once that is complete, remember to “Apply” the changes.

Step 2

Configure the LAN IP and subnet for each LTECube. The subnets must be different and cannot overlap.

Site A Site B

© Microhard 183
Appendix B: VPN Example (Page 2 of 2)

Step 3

Add a VPN Gateway to Gateway tunnel on each LTECube.

Site A Site B

A.B.C.D E.F.G.H

Must Match!

© Microhard 184
Appendix C: Firewall Example (Page 1 of 2)

By completing the Quick Start process, a user should have been able to log in and set up the LTECube to
work with their cellular carrier. By completing this, the modem is ready to be used to access the internet
and provide mobile connectivity. However, one of the main applications of the LTECube is to access
connected devices remotely. Security plays an important role in M2M deployments as in most cases the
modem is publicly available on the internet. Limiting access to the LTECube is paramount for a secure
deployment. The firewall features of the LTECube allow a user to limit access to the LTECube and the
devices connected to it by the following means

- Customizable Rules
- MAC and/or IP List
- ACL (Access Control List) or Blacklist using the above tools.

Consider the following example. An LTECube is deployed at a remote site. It is required that only a specific
host (Host A) have access to the deployed LTECube including the remote management features.

Host B:
84.53.23.12

Host A:
184.71.46.126
LTECube
Cell IP: 74.198.186.193

Firewall

Host C:
186.41.57.101

Step 1

Log into the LTECube (Refer to Quick Start). Navigate to the Firewall > General tab as shown below and block all
Carrier traffic by unchecking the Remote Access, and uncheck Remote Management . Be sure to Apply the settings.
At this point it should be impossible to access the LTECube from the Cellular (Carrier) Connection.

© Microhard 185
Appendix C: Firewall Example (Page 2 of 2)

Step 2

Under the Rules tab we need to create a new rule to enable Host A access to the Remote Management Port (TCP Port
80).

Rule

After the rule is created be sure to click the ADD Rule button, and then select the Submit button to write the rule to the
LTECube. The Firewall Rules Summary should look like what is shown below.

Step 3

Test the connection. The LTECube should only allow a connection from the Host A. An alternate means to limit
connections to the LTECube to a specific IP would have been to use the MAC-IP List Tool. By using Rules, we can not
only limit specific IP’s, but we can also specify ports that can be used by an allowed IP address.

© Microhard 186
Appendix D: Troubleshooting

Below is a number of the common support questions that are asked about the LTECube. The purpose of
the section is to provide answers and/or direction on how to solve common problems with the LTECube.
__________________________________________________________________

Question: Why can’t I connect to the internet/network?

Answer: To connect to the internet a SIM card issued by the Wireless Carrier must be installed and the
APN programmed into the Carrier Configuration of the LTECube. For instructions of how to log
into the LTECube refer to the Quick Start.
__________________________________________________________________

Question: What is the default IP Address of the LTECube?

Answer: The default IP address for the LAN (RJ45 connector) is 192.168.168.1.
__________________________________________________________________

Question: What is the default login for the LTECube?

Answer: The default username is admin, the default password is admin.

__________________________________________________________________

Question: What information do I need to get from my wireless carrier to set up the LTECube?

Answer: The APN is required to configure the LTECube to communicate with a wireless carrier. Some
carriers also require a username and password. The APN, username and password are only
available from your wireless carrier.

Newer units may support an AUTO APN feature, which will attempt to determine the APN from a
preconfigured list of carriers and commonly used APN’s. This is designed to provide quick
network connectivity, but will not work with private APN’s. Success with AUTO APN will vary by
carrier.
________________________________________________________________

Question: How do I reset my modem to factory default settings?

Answer: If you are logged into the LTECube navigate to the System > Maintenance Tab. If you cannot log
in, power on the LTECube and wait until the status LED in on solid (not flashing). Press and hold
the CONFIG button until the unit reboots (about 8-10 seconds).
_________________________________________________________________

Question: I can connect the Carrier, but I can’t access the Internet/WAN/network from a connected PC?

Answer: Ensure that you have DHCP enabled or manually set up a valid IP, Subnet, Gateway and DNS
set on the local device.
__________________________________________________________________

© Microhard 187
Appendix D: Troubleshooting

__________________________________________________________________

Question: How do I access the devices behind the modem remotely?

Answer: To access devices behind the LTECube remotely, several methods can be used:

A. Port Forwarding/DMZ - Individual external WAN ports are mapped to internal LAN IP’s and
Ports. See the Port-Forwarding Appendix for a detailed example.
B. VPN - A tunnel can be created and full access to remote devices can be obtained. Required
the use of multiple modems or VPN routers. See the VPN Appendix on an example of how to set
up a VPN.

_________________________________________________________________

Question: I have Internet/Carrier access but I cannot ping the device remotely?

Answer: Ensure that appropriates Rules have been created in the Firewall to allow traffic.

_________________________________________________________________

Question: Why does my modem reset every 10 minutes (or other time)?

Answer: There are a number of processes in the LTECube that ensure that the unit is communicating at
all times, and if a problem is detected will reboot the modem to attempt to resolve any issues:

1. Keepalive - Attempts to contact a configured host on a defined basis. Will reboot modem if
host is unreachable. Enabled by default to attempt to ping 8.8.8.8. May need to disable on
private networks, or provide a reachable address to check. Access via System > Keepalive.
3. Local Device Monitor - The LTECube will monitor a local device, if that device is not present
the LTECube may reboot. Apps > LocalMonitor.
__________________________________________________________________

Question: How do I set up VPN?

Answer: Refer to the VPN Appendix for an example of how to set up a Gateway to Gateway VPN with a
pair of LTECube modems.

© Microhard 188
 150 Country Hills Landing NW
Calgary, Alberta
Canada T3K 5P3

Phone: (403) 248-0028

Toll Free: 1-855-353-0028
www.microhardcorp.com

© Microhard 189