Digi Ex50 Ug
Digi Ex50 Ug
User Guide
Firmware version 21.8
Revision history—90002435
Disclaimers
Information in this document is subject to change without notice and does not represent a commitment on
the part of Digi International. Digi provides this document “as is,” without warranty of any kind, expressed or
implied, including, but not limited to, the implied warranties of fitness or merchantability for a particular
purpose. Digi may make improvements and/or changes in this manual or in the product(s) and/or the program
(s) described in this manual at any time.
User Guide
Warranty
To view product warranty information, go to the following website:
www.digi.com/howtobuy/terms
Customer support
Gather support information: Before contacting Digi technical support for help, gather the following
information:
Product name and model
Product serial number (s)
Firmware version
Operating system/browser (if applicable)
Logs (from time of reported issue)
Trace (if possible)
Description of issue
Steps to reproduce
Contact Digi technical support: Digi offers multiple technical support plans and service packages.
Contact us at +1 952.912.3444 or visit us at www.digi.com/support.
Feedback
To provide feedback on this document, email your comments to
[email protected]
Include the document title and part number (Digi EX50 User Guide, 90002435 A) in the subject line of
your email.
Revision history—90002435 1
Hardware setup
Site survey 25
Site survey troubleshooting 25
EX50 power installation 25
Connecting to the site network with local power 25
Connecting to the site network with remote power 26
Install SIM cards 26
SIM removal 27
Connect data cables 27
Mount the EX50 device 28
Interfaces
Wide Area Networks (WANs) 42
Wide Area Networks (WANs) and Wireless Wide Area Networks (WWANs) 43
Configure WAN/WWAN priority and default route metrics 43
WAN/WWAN failover 46
Configure SureLink active recovery to detect WAN/WWAN failures 47
Configure the device to reboot when a failure is detected 55
Disable SureLink 64
Example: Use a ping test for WAN failover from Ethernet to cellular 68
Using Ethernet devices in a WAN 71
Using cellular modems in a Wireless WAN (WWAN) 71
Configure a Wide Area Network (WAN) 96
Configure a Wireless Wide Area Network (WWAN) 103
Show WAN and WWAN status and statistics 114
Delete a WAN or WWAN 115
Default outbound WAN/WWAN ports 117
Local Area Networks (LANs) 118
About Local Area Networks (LANs) 119
Configure a LAN 119
Example: Configure two LANs 126
Show LAN status and statistics 135
Delete a LAN 137
DHCP servers 138
Create a Virtual LAN (VLAN) route 154
Default services listening on LAN ports 157
Bridging 158
Edit the preconfigured LAN bridge 159
Configure a bridge 162
Serial port
Configure the serial port 166
Configure UDP serial mode 177
Show serial status and statistics 180
Log serial port messages 180
Wi-Fi
Wi-Fi configuration 183
Routing
IP routing 235
Configure a static route 236
Delete a static route 239
Policy-based routing 241
Configure a routing policy 241
Example: Dual WAN policy-based routing 250
Example: Route traffic to a specific WAN interface based on the client MAC address 253
Routing services 258
Configure routing services 259
Show the routing table 262
Dynamic DNS 263
Configure dynamic DNS 263
Virtual Router Redundancy Protocol (VRRP) 269
VRRP+ 269
Configure VRRP 270
Configure VRRP+ 273
Example: VRRP/VRRP+ configuration 281
Configure device one (master device) 282
Configure device two (backup device) 286
Show VRRP status and statistics 292
Services
Allow remote access for web administration and SSH 414
Configure the web administration service 418
Configure SSH access 427
Use SSH with key authentication 434
Generating SSH key pairs 434
Configure telnet access 437
Configure DNS 442
Show DNS server 447
Simple Network Management Protocol (SNMP) 449
SNMP Security 449
Configure Simple Network Management Protocol (SNMP) 449
Download MIBs 454
Location information 455
Configure the location service 456
Configure the device to use a user-defined static location 458
Configure the device to accept location messages from external sources 460
Forward location information to a remote host 464
Configure geofencing 470
Show location information 482
Modbus gateway 483
Configure the Modbus gateway 484
Show Modbus gateway status and statistics 497
System time 500
Configure the system time 500
Manually set the system date and time 504
Network Time Protocol 504
Configure the device as an NTP server 505
Show status and statistics of the NTP server 510
Configure a multicast route 510
Ethernet network bonding 514
Enable service discovery (mDNS) 516
Use the iPerf service 520
Example performance test using iPerf3 524
Configure the ping responder service 524
Applications
Configure scripts to run automatically 530
Task one: Upload the application 530
Task two: Configure the application to run automatically 532
Configure scripts to run manually 536
Task one: Upload the application 537
Task two: Configure the application to run automatically 538
Start a manual script 541
Stop a script that is currently running 542
Show script information 543
Run a Python application at the shell prompt 544
Start an interactive Python session 546
Digidevice module 548
Use digidevice.cli to execute CLI commands 549
Use digidevice.datapoint to upload custom datapoints to Digi Remote Manager 550
Use digidevice.config for device configuration 553
Use Python to respond to Digi Remote Manager SCI requests 555
Use digidevice runtime to access the runtime database 564
Use Python to upload the device name to Digi Remote Manager 566
Use Python to access the device location data 568
Use Python to set the maintenance window 572
Use Python to send and receive SMS messages 574
Use Python to access serial ports 576
Use the Paho MQTT python library 577
Use the local REST API to configure the EX50 device 581
Use the GET method to return device configuration information 581
Use the POST method to modify device configuration parameters and list arrays 583
Use the DELETE method to remove items from a list array 584
User authentication
EX50 user authentication 586
User authentication methods 586
Add a new authentication method 588
Delete an authentication method 590
Rearrange the position of authentication methods 592
Authentication groups 594
Change the access rights for a predefined group 595
Add an authentication group 597
Delete an authentication group 601
Local users 604
Change a local user's password 605
Configure a local user 607
Delete a local user 614
Terminal Access Controller Access-Control System Plus (TACACS+) 617
TACACS+ user configuration 618
TACACS+ server failover and fallback to local authentication 619
Configure your EX50 device to use a TACACS+ server 619
Remote Authentication Dial-In User Service (RADIUS) 623
RADIUS user configuration 624
RADIUS server failover and fallback to local configuration 624
Firewall
Firewall configuration 653
Create a custom firewall zone 653
Configure the firewall zone for a network interface 655
Delete a custom firewall zone 657
Port forwarding rules 658
Configure port forwarding 658
Delete a port forwarding rule 663
Packet filtering 666
Configure packet filtering 666
Enable or disable a packet filtering rule 670
Delete a packet filtering rule 672
Configure custom firewall rules 674
Configure Quality of Service options 675
Containers
Upload a new LXC container 687
Configure a container 688
Starting and stopping the container 691
Starting the container 691
Stopping the container 692
View the status of containers 692
Schedule a script to run in the container 693
Create a custom container 696
Create the custom container file 696
Test the custom container file 697
System administration
Review device status 699
Configure system information 700
Update system firmware 702
Manage firmware updates using Digi Remote Manager 702
Certificate management for firmware images 703
Downgrading 703
Dual boot behavior 706
Update cellular module firmware 708
Update modem firmware over the air (OTA) 708
Update modem firmware by using a local firmware file 710
Monitoring
intelliFlow 737
Enable intelliFlow 737
Use intelliFlow to display average CPU and RAM usage 740
Use intelliFlow to display top data usage information 741
Use intelliFlow to display data usage by host over time 743
Configure NetFlow Probe 744
Central management
Digi Remote Manager support 750
Configure Digi Remote Manager 750
Collect device health data and set the sample interval 757
Enable event log upload to Digi Remote Manager 760
Log into Digi Remote Manager 762
Use Digi Remote Manager to view and manage your device 763
Add a device to Digi Remote Manager 764
View Digi Remote Manager connection status 764
Configure multiple devices using profiles 766
Learn more 766
File system
The EX50 local file system 768
Display directory contents 768
Create a directory 769
Display file contents 770
Copy a file or directory 770
Move or rename a file or directory 771
Delete a file or directory 772
Upload and download files 773
Upload and download files by using the WebUI 773
Upload and download files by using the Secure Copy command 774
Upload and download files using SFTP 775
Safety warnings
English 816
Bulgarian--бъ л га рс ки 817
Croatian--Hrvatski 818
French--Français 819
Greek--Ε λλην ικά 820
Hungarian--Magyar 821
Italian--Italiano 822
Latvian--Latvietis 823
Lithuanian--Lietuvis 824
Polish--Polskie 825
Portuguese--Português 826
Slovak--Slovák 827
Slovenian--Esloveno 828
Spanish--Español 829
b. Insert the SIM card(s) into the SIM sockets. Insert the end of each SIM card with the
chamfered corner positioned as indicated. Push the SIM in until it clicks into place.
c. After SIM cards are installed, replace the SIM slot cover.
2. Attach cellular antennas.
Securely finger tighten each antenna to the threaded barrel using the nut at the base of the
antenna.
3. Use an Ethernet cable connect the EX50's 1/WAN port to the internet, such as a home internet
router or LAN Ethernet port in an office environment.
You can also use the 2/PoE+ to power the device using active Power over Ethernet (PoE+).
2. If newer firmware is available, Remote Manager will prompt you to update the device. Click
Update to update the firmware. Remote Manager will perform the update in the background
and let you know when the device is up to date.
1. Navigate to the Settings tab in the Remote Manager Device Details view.
2. Expand the Config menu item and click on the Network settings menu.
3. Expand Interfaces > Modem > modem > APN list > APN list 1.
4. For APN, enter the custom APN provided by your cellular provider.
5. Click Apply.
6. Navigate back to the Details tab and watch for confirmation of cellular connectivity.
Hardware features
1. 1/WAN
n 2.5 Gigabit RJ45 Ethernet port.
n Configured by default for WAN connectivity.
n Requires Cat 5e or better Ethernet cable. A black, two meter Cat 6 cable is included with
the device.
n Configured by default as a DHCP client.
2. 2/PoE+
n 2.5 Gigabit RJ45 Ethernet port.
n Configured by default for LAN connectivity.
n Requires Cat 5e or better Ethernet cable. A black, two meter Cat 6 cable is included with
the device.
n Includes active Power over Ethernet (PoE+ IEEE 802.3at Type 2) power input.
l 25.5 W
l DC IN power supply has priority over PoE+.
l Seamless switchover between power supply and PoE+ in the event of power outage.
n DHCP server enabled by default with an IPv4 address of 192.168.2.1/24.
3. SERIAL RJ45 port
n Uses RS-232-level voltages.
n A blue, three meter straight-through RJ-45 cable provided with device allows direct
connection to many switch and router console ports for out-of-band management.
n See Serial port pinout and use for pinout details.
4. SIM button
n The SIM button is used to manually toggle between the two SIM slots.
5. ERASE button
n The ERASE button is used to perform a device reset, and it has three modes:
a. Configuration reset: Pressing the ERASE button one time will reset the device
configurations to the factory default. It will not remove any automatically
generated certificates and keys.
b. Full device reset: After the device reboots from the first button press, press the
ERASE button again before the device is connected to the internet to also remove
generated certificates/keys.
c. Firmware reversion: Press and hold the ERASE button and then power on the
device to boot to the version of firmware that was used prior to the current version.
Continue holding the button until the cellular service LED starts flashing.
6. DC IN power socket.
n 19 V, 2.63 A, 50 W power supply included with the device.
Solid green
Connected to DC IN power socket.
Solid blue
Connected to PoE+ power.
Solid red
Running in reduced power mode because it is
powered by PoE+ at 25.5 W.
Off
No connection.
Solid green
Connected.
Flashing green
Activity.
Off
No connection.
Solid green
Connected.
Flashing green
Activity.
Off
No access point or Wi-Fi client enabled.
Solid green
At least one access point or Wi-Fi client is enabled.
n Wi-Fi radio has internal antenna and supports Wi-Fi 6 and WPA3.
Off
No access point or Wi-Fi client enabled.
Solid green
At least one access point or Wi-Fi client is enabled.
n Wi-Fi radio has internal antenna and supports Wi-Fi 6 and WPA3.
15. Cloud connection indicator.
Off
Device is not connected to Digi Remote Manager.
Solid green
Device is connected to Digi Remote Manager.
For a detailed list of EX50 hardware specifications, see Digi EX50 specifications.
The weighted dBm measurements are negative numbers, meaning values closer to zero denote a
larger number. For example, a -85 is a better signal than -90.
Note See Signal quality bars explained for more information regarding how signal strength is
calculated and subsequently displayed via the LED indicators.
4G LTE algorithms
For 4G LTE, the EX50 device determines the RSRP, SNR, and RSSI values separately and uses the
following algorithms to display the signal quality:
If RSRP <= -199, the device uses the RSSI as the value with the same algorithm:
Once the snr_bars and rsrp_bars values are determined, the device uses the lesser of the two as the
reported signal a bars.
3G algorithm
For 3G, the EX50 determines RSSI signal strength:
2G algorithm
For 2G, the EX50 determines RSSI signal strength:
Note Ring indicate (RI) and data set ready (DSR) are not implemented.
The serial port uses a female RJ45 jack to enable connection using UTP Ethernet cabling.
Site survey 25
EX50 power installation 25
Install SIM cards 26
Connect data cables 27
Mount the EX50 device 28
Site survey
A cellular site survey is not necessary if your anticipated installation location is known to have strong
cellular signal strength. If you are unsure of available cellular signal strength or are choosing between
several installation locations, follow the below instructions to perform a site survey to determine your
best possible installation location. After the optimal location has been determined, set up the EX50
with either the power supply unit or an Ethernet cable connected to a PoE+ (802.3at) sourcing
Ethernet port.
1. LTE and 5G require at least two antennas. Digi recommends using all four antennas.
2. Move the EX50 to different locations within your site to determine the best compromise
between signal strength and installation constraints. Since cellular signal strength may
fluctuate, it is important to wait at each location for 1 minute while observing the signal
strength indicator on the front of the device. Minimum cellular signal strength for proper
operation is 2 bars.
3. Because the EX50 device has internal Wi-Fi antennas, the device should be positioned to
maximize the Wi-Fi signal as well. Do not install the device between metal plates, near metal
air ducts, or other obstructions.
4. After the optimal location has been determined, connect either the main power supply unit or
a PoE+ Ethernet cable (see EX50 power installation).
n Verify your SIM has been activated with your cellular operator.
n If you do not get a cellular signal when the EX50 is located indoors, then take the device
outdoors to verify that your cellular network operator has coverage in your location.
n If the outdoor cellular signal strength is less than 2 bars, it may be necessary to connect using
a different cellular network operator. This requires an activated SIM from the alternate cellular
network operator.
n Try the device/antennas in different orientations and away from other nearby electronic
equipment at each test location.
Note LTE and 5G require at least two antennas. Digi recommends using all four antennas.
Antennas will usually give better performance when vertical.
n Refer to Cellular signal strength LEDs to use the EX50 indicator lights to aid in diagnosis.
Note If the Power indicator LED is a solid red color, this indicates that the EX50 is running in reduced
power mode because it is powered by PoE+ at 25.5 W.
2. For high-vibration environments, apply a thin layer of dielectric grease to the SIM contacts.
Note If the EX50 device is used in an environment with high vibration levels, SIM card contact
fretting may cause unexpected SIM card failures. To protect the SIM cards, Digi strongly
recommends that you apply a thin layer of dielectric grease to the SIM contacts prior to
installing the SIM cards.
3. Insert the SIM card(s) into the SIM sockets. Insert the end of each SIM card with the chamfered
corner positioned as indicated. Push the SIM in until it clicks into place.
4. After SIM cards are installed, replace the SIM slot cover.
SIM removal
The EX50 has a PUSH-PUSH SIM connector. To insert, push each SIM in until it clicks, and repeat for
removal. When you push to eject, the SIM ejects back out about 1/8 inch.
n Serial (RJ-45): Use a serial cable with an RJ45 connector to connect to the EX50 device. Allows
direct connection to many switch and router console ports for out-of-band management. See
Serial port pinout and use for pinout information.
1. Attach the mounting bracket to a surface by using four drywall anchors and screws.
2. Insert the bottom tabs on bracket with the bottom tab slots on the device.
3. Attach the device to the mounting bracket by pushing the device into place until the front tab
on the bracket snaps into the front tab slot on the bottom of the device.
4. After mounting the device, verify that it is securely locked into place.
Local WebUI
1. Log into the EX50 WebUI as a user with Admin access. See Using the web interface for details.
2. On the menu, click System > Device Configuration.
Interface
type Preconfigured interfaces Devices Default configuration
Wide Area n WAN n Ethernet: n Firewall zone:
Network WAN External
(WAN) n WAN priority:
Metric=1
n IP Address: DHCP
client
n Digi SureLinkTM
enabled for IPv4
Wireless n Modem n Modem n Firewall zone:
Wide Area External
Network n WAN priority:
(WWAN) Metric=3
n SIM failover after 5
attempts
n SureLink enabled for
IPv4
Interface
type Preconfigured interfaces Devices Default configuration
Local Area n LAN n Ethernet: n Firewall zone:
Network LAN Internal
(LAN) n IP address:
192.168.2.1/24
n DHCP server
enabled
n LAN priority:
Metric=5
n Surelink disabled
Interface
type Preconfigured interfaces Devices Default configuration
n Hotspot access point: Digi Hotspot AP n Wi-Fi1 n Disabled
(Wi-Fi1) radio n SSID: Digi Hotspot
n Encryption: Open
(Unencrypted)
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Set a new password for the admin user. The password must be at least eight characters long
and must contain at least one uppercase letter, one lowercase letter, one number, and one
special character.
(config)> save
Configuration saved.
>
n Enabled
n SSID: Digi-EX50-serial_number
n Encryption: WAP2 Personal (PSK)
n Pre-shared key: The unique password printed on the bottom label of the device.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. Set a new SSID and pre-shared key for the digi_ap2 access point:
(config)> save
Configuration saved.
>
Configuration methods
There are two primary methods for configuring your EX50 device:
n Web interface.
The web interface can be accessed in two ways:
l Central management using the Digi Remote Manager, a cloud-based device management
and data enablement platform that allows you to connect any device to any application,
anywhere. With the Remote Manager, you can configure your EX50 device and use the
configuration as a basis for a profile which can be applied to other similar devices. See
Using Digi Remote Manager for more information about using the Remote Manager to
manage and configure your EX50 device.
l The local web interface. See Using the web interface for more information about using the
local web interface to manage and configure your EX50 device.
Note Changes made to the device's configuration by using the local web interface will not
be automatically reflected in Digi Remote Manager. You must manually refresh Remote
Manager for the changes to be displayed.
Web-based instructions in this guide are applicable to both the Remote Manager and the local
web interface.
n Command line.
A robust command line allows you to perform all configuration and management tasks from
within a command shell. Both the Remote Manager and the local web interface also have the
option to open a terminal emulator for executing commands on your EX50 device. See Using
the command line for more information about using the command line to manage and
configure your EX50 device.
In this guide, task topics show how to perform tasks:
WebUI
Shows how to perform a task by using the local web interface.
Command line
Shows how to perform a task by using the command line interface.
1. If you have not already done so, go to https://myaccount.digi.com/ to sign up for a Digi
Remote Manager account.
Check your email for Digi Remote Manager login instructions.
2. Go to remotemanager.digi.com.
1. Enter your username and password.
The Digi Remote Manager Dashboard appears.
1. Use an Ethernet cable to connect the EX50's 2/PoE+ port to a laptop or PC.
2. Open a browser and go to 192.168.210.1.
3. Log into the device using a configured user name and password.
The default user name is admin and the default password is the unique password printed on
the label packaged with your device.
After logging in, the local web admin dashboard is displayed.
Dashboard
area Description
Network Summarizes network statistics: the total number of bytes sent and received over all
activity configured bridges and Ethernet devices.
Dashboard
area Description
Digi Remote Displays the device connection status for Digi Remote Manager, the amount of time
Manager the connection has been up, and the Digi Remote Manager device ID.
See Using Digi Remote Manager.
Device Displays the EX50 device's status, statistics, and identifying information.
Network Displays the status of the network interfaces configured on the device.
Interfaces
Modems Provides information about the signal strength and technology of the cellular
modem(s).
Command line
1. Connect to the EX50 device by using a serial connection, SSH or telnet, or the Terminal in the
WebUI or the Console in the Digi Remote Manager. See Access the command line interface for
more information.
n For serial connections, the default configuration is:
l 115200 baud rate
l 8 data bits
l no parity
l 1 stop bit
l no flow control
n For SSH and telnet connections, the default IP address of the device is192.168.210.1 on
the .
2. At the login prompt, enter the username and password of a user with Admin access:
login: admin
Password: **********
The default username is admin. The default unique password for your device is printed on the
device label.
3. Depending on the device configuration, you may be presented with another menu, for
example:
a: Admin CLI
s: Shell
q: Quit
Connecting now...
Press Tab to autocomplete commands
Press '?' for a list of commands and details
Type 'help' for details on navigating the CLI
Type 'exit' to disconnect from the Admin CLI
>
See Command line interface for detailed instructions on using the command line interface.
Command line
1. At the command prompt, type exit.
> exit
2. Depending on the device configuration, you may be presented with another menu, for
example:
a: Admin CLI
s: Shell
q: Quit
Default
Interface type Preconfigured interfaces Devices configuration
Wide Area n WAN n Ethernet: n Firewall
Network (WAN) WAN zone:
External
n WAN priority:
Metric=1
n IP Address:
DHCP client
n Digi
SureLinkTM
enabled for
IPv4
Wireless Wide n Modem n Modem n Firewall
Area Network zone:
(WWAN) External
n WAN priority:
Metric=3
n SIM failover
after 5
attempts
n SureLink
enabled for
IPv4
You can modify configuration settings for the existing WAN and WWANs, and you can create new WANs
and WWANs.
This section contains the following topics:
Wide Area Networks (WANs) and Wireless Wide Area Networks (WWANs) 43
Configure WAN/WWAN priority and default route metrics 43
WAN/WWAN failover 46
Configure SureLink active recovery to detect WAN/WWAN failures 47
Configure the device to reboot when a failure is detected 55
Disable SureLink 64
Example: Use a ping test for WAN failover from Ethernet to cellular 68
Using Ethernet devices in a WAN 71
Using cellular modems in a Wireless WAN (WWAN) 71
Configure a Wide Area Network (WAN) 96
Configure a Wireless Wide Area Network (WWAN) 103
Show WAN and WWAN status and statistics 114
Delete a WAN or WWAN 115
Default outbound WAN/WWAN ports 117
Example: Configure cellular connection as the primary WAN, and the Ethernet
connection as backup
n Configured WAN and WWAN interfaces. This example uses the preconfigured WAN and Modem
interfaces.
n The metric for each WAN.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
c. Click IPv6.
d. For Metric, type 2.
The EX50 device is now configured to use the cellular modem WWAN, Modem, as its highest priority
WAN, and its Ethernet WAN, WAN, as its secondary WAN.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
WAN/WWAN failover
If a connection to a WAN interface is lost for any reason, the EX50 device will immediately fail over to
the next WAN or WWAN interface, based on WAN priority. See Configure WAN/WWAN priority and
default route metrics for more information about WAN priority.
n Active detection uses Digi SureLinkTM technology to send probe tests to a target host or to test
the status of the interface. The WAN/WWAN is considered to be down if there are no responses
for a configured amount of time. See Configure SureLink active recovery to detect WAN/WWAN
failures for more information about active failure detection.
n Passive detection involves detecting the WAN going down by monitoring its link status by some
means other than active detection. For example, if an Ethernet cable is disconnected or the
state of a cellular interface changes from on to off, the WAN is down.
n Interface connectivity.
n DNS query to the DNS servers for interface's the network connection.
DNS servers are typically received as part of the interface's DHCP client connection, although
you can manually configure the DNS servers that will be used by SureLink.
Note If your device is operating on a private APN or on wired network with firewall restrictions,
ensure that the DNS servers on your private network allow DNS lookups for
my.devicecloud.com; otherwise, the SureLink DNS query test will fail and the EX50 device will
determine that the interface is down.
By default, these tests will be performed every 15 minutes, with a response timeout of 15 seconds. If
the tests fail three consecutive times, the device will reset the network interface to attempt to recover
the connection.
n Enable SureLink.
SureLink can be enabled for both IPv4 and IPv6 configurations. By default, SureLink is enabled
for IPv4 for the preconfigured WAN (WAN) and WWAN (Modem). It is disabled for IPv6.
When SureLink is configured for Wireless WANs, SureLink tests are only run if the cellular
modem is connected and has an IP address. Use the SIM failover options to configure the
EX50 device to automatically recover the modem in the event that it cannot obtain an IP
address. See Configure a Wireless Wide Area Network (WWAN) for details about SIM failover.
n The type of probe test to be performed, either:
l Ping: Requires the hostname or IP address of the host to be pinged.
l DNS query: You can perform a DNS query to a named DNS server, or to the DNS servers
configured for the WAN.
l HTTP or HTTPS test: Requires the URL of the host to be tested.
l Interface status: Determines if the interface has an IP address assigned to it, that the
physical link is up, and that a route is present to send traffic out of the network interface.
The preconfigured WAN is configured by default to use SureLink to both test the interface
status and perform a test DNS query.
WebUI
SureLink can be configured for both IPv4 and IPv6.
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
5. After creating or selecting the WAN or WWAN, click IPv4 (or IPv6) > SureLink.
6. Enable SureLink.
SureLink can be enabled for both IPv4 and IPv6 configurations. By default, SureLink is enabled
for IPv4 for the preconfigured WAN (WAN) and WWAN (Modem). It is disabled for IPv6.
When SureLink is configured for Wireless WANs, SureLink tests are only run if the cellular
modem is connected and has an IP address. Use the SIM failover options to configure the
EX50 device to automatically recover the modem in the event that it cannot obtain an IP
address. See Configure a Wireless Wide Area Network (WWAN) for details about SIM failover.
7. Click to expand Test targets.
8. For Add Test Target, click .
n Test the interface status: The interface is considered to be down based on:
l Down time: The amount of time that the interface can be down before this test is
considered to have failed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and
take the format number{w|d|h|m|s}.
For example, to set Down time to ten minutes, enter 10m or 600s.
The default is 60 seconds.
l Initial connection time: The amount of time to wait for an initial connection to the
interface before this test is considered to have failed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and
take the format number{w|d|h|m|s}.
For example, to set Initial connection time to ten minutes, enter 10m or 600s.
The default is 60 seconds.
10. Optional active recovery configuration parameters:
a. For Restart interface, enable to configure the device to restart the interface when its
connection is considered to have failed. This is useful for interfaces that may regain
connectivity after restarting, such as a cellular modem.
b. If Restart interface is enabled, for Restart fail count, type or select the number of times
that the Surelink test must fail before the interface is restarted. The default is 1.
c. For Reboot device, enable to instruct the device to reboot when the WAN connection is
considered to have failed.
Note If both the Restart interface and Reboot device parameters are enabled, the
Reboot device parameter takes precedence.
d. If Reboot device is enabled, for Reboot fail count, type or select the number of times that
the Surelink test must fail before the device is rebooted. The default is 1.
e. Change the Interval between connectivity tests.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Interval to ten minutes, enter 10m or 600s.
The default is 15 minutes.
f. If more than one test target is configured, for Success condition, determine whether the
interface should fail over based on the failure of one of the test targets, or all of the test
targets.
g. For Pass threshold, type or select the number of times that the test must pass after
failure, before the interface is determined to be working and is reinstated.
h. For Failed attempts, type the number of probe attempts before the WAN is considered to
have failed.
i. For Response timeout, type the amount of time that the device should wait for a response
to a probe attempt before considering it to have failed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Response timeout to ten minutes, enter 10m or 600s.
Command line
Active recovery can be configured for both IPv4 and IPv6. These instructions are for IPv4; to configure
IPv6 active recovery, replace ipv4 in the command line with ipv6.
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Enable SureLink.
SureLink can be enabled for both IPv4 and IPv6 configurations. By default, SureLink is enabled
for IPv4 for the preconfigured WAN (wan) and WWAN (modemwwan2). It is disabled for IPv6.
When SureLink is configured for Wireless WANs, SureLink tests are only run if the cellular
modem is connected and has an IP address. Use the SIM failover options to configure the
EX50 device to automatically recover the modem in the event that it cannot obtain an IP
address. See Configure a Wireless Wide Area Network (WWAN) for details about SIM failover.
(config network interface my_wan ipv4 surelink target 0)> test value
(config network interface my_wan ipv4 surelink target 0)>
n dns: Tests connectivity by sending a DNS query to the specified DNS server.
l Specify the DNS server. Allowed value is the IP address of the DNS server.
where value is any number of weeks, days, hours, minutes, or seconds, and takes
the format number{w|d|h|m|s}.
For example, to set interface_down_time to ten minutes, enter either 10m or 600s:
where value is any number of weeks, days, hours, minutes, or seconds, and takes
the format number{w|d|h|m|s}.
For example, to set interface_timeout to ten minutes, enter either 10m or 600s:
If other is set:
o Set the alternate interface to be tested:
i. Use the ? to determine available interfaces:
o Set the alternate interface's IP version. This allows you to determine the
alternate interface's status for a particular IP version.
b. To configure the device to restart the interface when its connection is considered to have
failed:
This is useful for interfaces that may regain connectivity after restarting, such as a cellular
modem.
c. To configure the device to reboot when the interface is considered to have failed:
Note If both the restart and reboot parameters are enabled, the reboot parameter takes
precedence.
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set interval to ten minutes, enter either 10m or 600s:
The default is 3.
g. Set the amount of time that the device should wait for a response to a probe attempt
before considering it to have failed:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set timeout to ten minutes, enter either 10m or 600s:
n Enable SureLink.
SureLink can be enabled for both IPv4 and IPv6 configurations. By default, SureLink is enabled
for IPv4 for the preconfigured WAN (WAN) and WWAN (Modem). It is disabled for IPv6.
When SureLink is configured for Wireless WANs, SureLink tests are only run if the cellular
modem is connected and has an IP address. Use the SIM failover options to configure the
EX50 device to automatically recover the modem in the event that it cannot obtain an IP
address. See Configure a Wireless Wide Area Network (WWAN) for details about SIM failover.
n Enable device reboot upon interface failure.
n The type of probe test to be performed, either:
l Ping: Requires the hostname or IP address of the host to be pinged.
l DNS query: You can perform a DNS query to a named DNS server, or to the DNS servers
configured for the WAN.
l HTTP or HTTPS test: Requires the URL of the host to be tested.
l Interface status: Determines if the interface has an IP address assigned to it, that the
physical link is up, and that a route is present to send traffic out of the network interface.
n See Configure SureLink active recovery to detect WAN/WWAN failures for optional SureLink
configuration parameters.
WebUI
SureLink can be configured for both IPv4 and IPv6.
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
6. Enable SureLink.
SureLink can be enabled for both IPv4 and IPv6 configurations. By default, SureLink is enabled
for IPv4 for the preconfigured WAN (WAN) and WWAN (Modem). It is disabled for IPv6.
When SureLink is configured for Wireless WANs, SureLink tests are only run if the cellular
modem is connected and has an IP address. Use the SIM failover options to configure the
EX50 device to automatically recover the modem in the event that it cannot obtain an IP
address. See Configure a Wireless Wide Area Network (WWAN) for details about SIM failover.
7. Enable Reboot device.
Note If both the Restart interface and Reboot device parameters are enabled, the Reboot
device parameter takes precedence.
8. (Optional) For Reboot fail count, type or select the number of times that the Surelink test
must fail before the device is rebooted. The default is 1.
9. Click to expand Test targets.
10. For Add Test Target, click .
Allowed values are any number of weeks, days, hours, minutes, or seconds, and
take the format number{w|d|h|m|s}.
For example, to set Initial connection time to ten minutes, enter 10m or 600s.
The default is 60 seconds.
12. Optional active recovery configuration parameters:
a. If Reboot device is enabled, for Reboot fail count, type or select the number of times that
the Surelink test must fail before the device is rebooted. The default is 1.
b. Change the Interval between connectivity tests.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Interval to ten minutes, enter 10m or 600s.
The default is 15 minutes.
c. If more than one test target is configured, for Success condition, determine whether the
interface should fail over based on the failure of one of the test targets, or all of the test
targets.
d. For Pass threshold, type or select the number of times that the test must pass after
failure, before the interface is determined to be working and is reinstated.
e. For Failed attempts, type the number of probe attempts before the WAN is considered to
have failed.
f. For Response timeout, type the amount of time that the device should wait for a response
to a probe attempt before considering it to have failed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Response timeout to ten minutes, enter 10m or 600s.
The default is 15 seconds.
13. (Optional) Repeat this procedure for IPv6.
14. Click Apply to save the configuration and apply the change.
Command line
Active recovery can be configured for both IPv4 and IPv6. These instructions are for IPv4; to configure
IPv6 active recovery, replace ipv4 in the command line with ipv6.
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Enable SureLink.
SureLink can be enabled for both IPv4 and IPv6 configurations. By default, SureLink is enabled
for IPv4 for the preconfigured WAN (wan) and WWAN (modemwwan2). It is disabled for IPv6.
When SureLink is configured for Wireless WANs, SureLink tests are only run if the cellular
modem is connected and has an IP address. Use the SIM failover options to configure the
EX50 device to automatically recover the modem in the event that it cannot obtain an IP
address. See Configure a Wireless Wide Area Network (WWAN) for details about SIM failover.
5. Set the device to reboot when the interface is considered to have failed:
Note If both the restart and reboot parameters are enabled, the reboot parameter takes
precedence.
6. (Optional) Set the number of times that the Surelink test must fail before the device is
rebooted:
(config network interface my_wan ipv4 surelink target 0)> test value
(config network interface my_wan ipv4 surelink target 0)>
n dns: Tests connectivity by sending a DNS query to the specified DNS server.
l Specify the DNS server. Allowed value is the IP address of the DNS server.
where value is any number of weeks, days, hours, minutes, or seconds, and takes
the format number{w|d|h|m|s}.
For example, to set interface_down_time to ten minutes, enter either 10m or 600s:
where value is any number of weeks, days, hours, minutes, or seconds, and takes
the format number{w|d|h|m|s}.
For example, to set interface_timeout to ten minutes, enter either 10m or 600s:
If other is set:
o Set the alternate interface to be tested:
i. Use the ? to determine available interfaces:
o Set the alternate interface's IP version. This allows you to determine the
alternate interface's status for a particular IP version.
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set interval to ten minutes, enter either 10m or 600s:
The default is 3.
e. Set the amount of time that the device should wait for a response to a probe attempt
before considering it to have failed:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set timeout to ten minutes, enter either 10m or 600s:
Disable SureLink
If your device uses a private APN with no Internet access, or your device has a restricted wired WAN
connection that doesn't allow DNS resolution, follow this procedure to disable the default SureLink
connectivity tests. You can also disable DNS lookup or other internet activity, while retaining the
SureLink interface test.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Change to the WAN or WWAN's node in the configuration schema. For example, to disable
SureLink for the Modem interface:
4. Disable SureLink:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
8. Click the menu icon (...) next to the target and select Delete.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Change to WAN or WWAN's node in the configuration schema. For example, to disable SureLink
for an interface named my_wan:
Example: Use a ping test for WAN failover from Ethernet to cellular
In this example configuration, the WAN interface serves as the primary WAN, while the cellular Modem
interface serves as the backup WAN.
In this example configuration, SureLink is used over for the WAN interface to send a probe packet of
size 256 bytes to the IP host 43.66.93.111 every 10 seconds. If there are three consecutive failed
responses, the EX50 device brings the WAN interface down and starts using the Modem interface. It
continues to regularly test the connection to WAN, and when tests on WAN succeed, the device falls
back to ETH1.
To achieve this WAN failover from the WAN to the Modem interface, the WAN failover configuration is:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
4. Repeat the above step for Modem to enable SureLink on that interface.
5. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config network interface wan ipv4 surelink target 0)> test ping
(config network interface wan ipv4 surelink target 0)>
(config network interface wan ipv4 surelink target 0)> ping_size 256
(config network interface wan ipv4 surelink target 0)>
1. Repeat the above step for the cellular Modem (modem) interface to enable SureLink on that
interface.
4. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
By default, the 1/WAN Ethernet device is configured as a WAN, named WAN, with both DHCP and NAT
enabled and using the External firewall zone. This means you should be able to connect to the
Internet by connecting the 1/WAN Ethernet port to another device that already has an internet
connection.
The 2/PoE+ device is configured as a LAN interface, named LAN, which uses the Internal firewall
zone.
n If Active SIM slot is set to Any, determine the preferred SIM slot.
In the event of a failover to a non-preferred SIM, or if manual SIM switching is used to switch to
a non-preferred SIM, the modem will attempt to reconnect to the SIM in the preferred SIM slot.
The Digi EX50 cellular modem supports 5G technology. In order to take advantage of the 5G
capabilities of the device, you must use a SIM that has been provisioned for 5G support.
To configure the modem:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the matching criteria used to determine if this modem configuration applies to the
currently attached modem:
8. Carrier switching allows the modem to automatically match the carrier for the active SIM.
Carrier switching is enabled by default. To disable:
9. Set the type of cellular technology that this modem should use to access the cellular network:
Available options for value vary depending on the modem type. To determine available
options:
Access technology: The cellular network technology that the modem may
use.
Format:
2G
3G
4G
4GM
4GT
5G
all
Default value: all
Current value: all
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
3. Click Network > Interfaces > Modem > APN list > APN.
4. For APN, type the Access Point Name (APN) to be used when connecting to the cellular carrier.
5. (Optional) IP version:
For IP version, select one of the following:
n Automatic: Requests both IPv4 and IPv6 address.
n IPv4: Requests only an IPv4 address.
n IPv6: Requests only an IPv6 address.
The default is Automatic.
6. (Optional) Authentication method:
For Authentication method, select one of the following:
n None: No authentication is required.
n Automatic: The device will attempt to connect using CHAP first, and then PAP.
n CHAP: Uses the Challenge Handshake Authentication Profile (CHAP) to authenticate.
n PAP: Uses the Password Authentication Profile (PAP) to authenticate.
If Automatic, CHAP, or PAP is selected, enter the Username and Password required to
authenticate.
The default is None.
7. To add additional APNs, for Add APN, click and repeat the preceding instructions.
8. (Optional) To configure the device to bypass its preconfigured APN list and only use the
configured APNs, enable APN list only.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
n Segregating public and private traffic, including policy-based routes to ensure that your
internal network traffic always goes through the private connection.
To accomplish this, we will create separate WWAN interfaces that use the same modem but use
different APNs, and then use routing roles to forward traffic to the appropriate WWAN interface.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
5. Create the routing policies. For example, to route all traffic from LAN1 through the public APN,
and LAN2 through the private APN:
a. Click Network > Routes > Policy-based routing.
b. Click the to add a new route policy.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
d. (Optional): Set the public APN. If the public APN is not configured, the EX50 will attempt to
determine the APN.
5. Create the routing policies. For example, to route all traffic from LAN1 through the public APN,
and LAN2 through the private APN:
a. Add a new routing policy:
b. Set the label that will be used to identify this route policy:
(config network route policy 0)> label "Route through public apn"
(config network route policy 0)>
h. Set the label that will be used to identify this route policy:
(config network route policy 1)> label "Route through private apn"
(config network route policy 1)>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note You can use the modem scan command at the Admin CLI to scan for available carriers
and determine their PLMN ID. See Scan for available cellular carriers for details.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n manual—The device will only connect to the carrier identified in the Network PLMN ID.
If the carrier is not available, no cellular connection will be established.
n manual_automatic—The device will attempt to connect to the carrier identified in the
Network PLMN ID. If the carrier is not available, the device will fall back to using
automatic carrier selection.
4. If carrier section mode is set to manual or manual_automatic, set the network PLMN ID:
Note You can use the modem scan command at the Admin CLI to scan for available carriers
and determine their PLMN ID. See Scan for available cellular carriers for details.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. From the main menu, click Status > Modems.
3. For the appropriate modem, scroll to the Connection Status section and click SCAN.
4. When the Carrier Scan window opens, the results of the most recent previous scan are
displayed. If there is no previous scan available, or to refresh the list, click SCAN.
5. The current carrier is highlighted in green. To switch to a different carrier:
a. Highlight the appropriate carrier and click SELECT.
The Carrier selection dialog opens.
Note If Manual is selected, your modem must support the Network technology or
the modem will lose cellular connectivity. If you are using a cellular connection to
perform this procedure, you may lose your connection and the device will no longer
be accessible.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type:
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click Status.
3. Under Connections, click Modems.
The modem status window is displayed
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the show modem command:
n To view a status summary for the modem:
>
n To view detailed status and statistics, use the show modem name name command:
Status
------
State : connected
Signal Strength : Good (-85 dBm)
Bars : 2/5
Access Mode : 5G
Network Technology (CNTI): NR5G-NSA
Temperature : 34C
wwan1 Interface
---------------
APN : 1234
IPv4 surelink : passing
IPv4 address : 189.232.229.47
IPv4 gateway : 189.232.229.1
IPv4 MTU : 1500
IPv4 DNS server(s) : 245.144.162.207, 245.144.162.208
TX bytes : 127941
RX bytes : 61026
Uptime : 10 hrs, 56 mins (39360s)
SIM
---
SIM Slot : 1
SIM Status : ready
IMSI : 61582122197895
ICCID : 26587628655003992180
SIM Provider : AT&T
4G
--
Band : B66
RSRQ : Fair to Poor (-14.0 dB)
RSRP : Excellent (-69.0 dBm)
RSSI : Excellent (-51.0 dBm)
5G
--
RRC State : Connected
Bars : 2/5
Band : n71
RSRQ : Poor (-14 dB)
RSRP : Good (-78 dBm)
SINR : Poor (4.5 dB)
>
Command line
To unlock a SIM card:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, use the modem command to set a new PIN for the SIM card:
For example, to unlock a SIM card in the modem named modem with PUK code 12345678,
and set the new SIM PIN to 1234:
Note If the SIM remains in a locked state after using the unlock command, contact your cellular
carrier.
AT command access
To run AT commands from the EX50 command line:
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type modem at-interactive and press Enter. Type n if you do not
want exclusive access. This allows you to send AT commands to the device while still allowing
the device to connect, disconnect, and/or reconnect to the cellular network.
3. At the Admin CLI prompt, use the modem command to begin an interactive AT command
session:
4. Type n if you do not want exclusive access. This allows you to send AT commands to the
device while still allowing the device to connect, disconnect, and/or reconnect to the cellular
network.
The following is an example interactive AT command:
To quit enter '~.' ('~~.' if using an ssh client) and press ENTER
Connected
ati
Manufacturer: Sierra Wireless, Incorporated
Model: MC7455
Revision: SWI9X30C_02.24.03.00 r6978 CARMD-EV-FRMWR2 2017/03/02 13:36:45
MEID: 35907206045169
IMEI: 359072060451693
IMEI SV: 9
FSN: LQ650551070110
+GCAP: +CGSM
OK
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
8. (Optional) Click to expand 802.1x to configure 802.1x port based network access control:
a. Click to expand Authentication.
b. Click Enable server to enable a 802.1x authentication server.
c. Set the Reauth period.
9. Configure IPv4 settings:
a. Click to expand IPv4.
IPv4 support is enabled by default.
b. For Type, select DHCP address.
c. Optional IPv4 configuration items:
i. Set the Metric.
See Configure WAN/WWAN priority and default route metrics for further information
about metrics.
ii. For Weight, type the relative weight for default routes associated with this interface.
For multiple active interfaces with the same metric, Weight is used to load balance
traffic to the interfaces.
iii. Set the Management priority. This determines which interface will have priority for
central management activity. The interface with the highest number will be used.
iv. Set the MTU.
v. For Use DNS, select one of the following:
n Always: DNS will always be used for this WAN; when multiple interfaces have
the same DNS server, the interface with the lowest metric will be used for DNS
requests.
n When primary default route: Only use the DNS servers provided for this
interface when the interface is the primary route.
n Never: Never use DNS servers for this interface.
vi. Enable DHCP Hostname to instruct the EX50 device to include the device's system
name with DHCP requests as the Client FQDN option. The DHCP server can then be
configured to register the device's hostname and IP address with an associated DNS
server.
n See RFC4702 for further information about DHCP server support for the Client
FQDN option.
n See Configure system information for information about setting the EX50
device's system name.
d. See Configure SureLink active recovery to detect WAN/WWAN failures for information
about configuring Active recovery.
10. (Optional) Configure IPv6 settings:
a. Click to expand IPv6.
b. Enable IPv6 support.
c. For Type, select DHCPv6 address.
d. For Prefix length, type the minimum length of the prefix to assign to this LAN. If the
minimum length is not available, then a longer prefix will be used.
e. For Prefix ID, type the identifier used to extend the prefix to the assigned length. Leave
blank to use a random identifier.
f. Set the Metric.
See Configure WAN/WWAN priority and default route metrics for further information about
metrics.
g. For Weight, type the relative weight for default routes associated with this interface. For
multiple active interfaces with the same metric, Weight is used to load balance traffic to
the interfaces.
h. Set the Management priority. This determines which interface will have priority for
central management activity. The interface with the highest number will be used.
i. Set the MTU.
j. For Use DNS:
n Always: DNS will always be used for this WAN; when multiple interfaces have the
same DNS server, the interface with the lowest metric will be used for DNS
requests.
n When primary default route: Only use the DNS servers provided for this interface
when the interface is the primary route.
n Never: Never use DNS servers for this interface.
k. Enable DHCP Hostname to instruct the EX50 device to include the device's system name
with DHCP requests as the Client FQDN option. The DHCP server can then be configured to
register the device's hostname and IP address with an associated DNS server.
n See RFC4702 for further information about DHCP server support for the Client
FQDN option.
n See Configure system information for information about setting the EX50 device's
system name.
11. (Optional) Click to expand MAC address denylist.
Incoming packets will be dropped from any devices whose MAC addresses is included in the
MAC address denylist.
a. Click to expand MAC address denylist.
b. For Add MAC address, click .
c. Type the MAC address.
12. (Optional) Click to expand MAC address allowlist.
If there allowlist entries are specified, incoming packets will only be accepted from the listed
MAC addresses.
a. Click to expand MAC address allowlist.
b. For Add MAC address, click .
c. Type the MAC address.
13. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n To edit an existing WAN named my_wan, change to the my_wan node in the
configuration schema:
See Configure WAN/WWAN priority and default route metrics for further information
about metrics.
ii. Set the relative weight for default routes associated with this interface. For multiple
active interfaces with the same metric, the weight is used to load balance traffic to
the interfaces.
iii. Set the management priority. This determines which interface will have priority for
central management activity. The interface with the highest number will be used.
vi. Enable DHCP Hostname to instruct the EX50 device to include the device's system
name with DHCP requests as the Client FQDN option. The DHCP server can then be
configured to register the device's hostname and IP address with an associated DNS
server.
n See RFC4702 for further information about DHCP server support for the Client
FQDN option.
n See Configure system information for information about setting the EX50
device's system name.
b. See Configure SureLink active recovery to detect WAN/WWAN failures for information
about configuring active recovery.
7. (Optional) Configure IPv6 settings:
a. Enable IPv6 support:
c. Generally, the default settings for IPv6 support are sufficient. You can view the default IPv6
settings by using the question mark (?):
IPv6
Additional Configuration
---------------------------------------------------------------------
----------
connection_monitor Active recovery
d. Modify any of the remaining default settings as appropriate. For example, to change the
metric:
If the minimum length is not available, then a longer prefix will be used.
See Configure WAN/WWAN priority and default route metrics for further information about
metrics.
(Optional) Configure the MAC address deny list.
Incoming packets will be dropped from any devices whose MAC addresses is included in the
MAC address denylist.
a. Add a MAC address to the denylist:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
6. The WWAN is enabled by default. Click Enable to disable, or to enable if it has been disabled.
7. Interface type defaults to Modem.
8. For Zone, select External.
9. For Device, select the cellular modem.
10. For Match SIM by, select a SIM matching criteria to determine when this WWAN should be
used:
n If SIM slot is selected, for Match SIM slot, select which SIM slot must be in active for
this WWAN to be used.
n If Carrier is selected, for Match SIM carrier, select which cellular carrier must be in
active for this WWAN to be used.
n If PLMN identifier is selected, for Match PLMN identifier, type the PLMN id that must
be in active for this WWAN to be used.
n If IMSI is selected, for Match IMSI, type the International Mobile Subscriber Identity
(IMSI) that must be in active for this WWAN to be used.
n If ICCID is selected, for Match ICCID, type the unique SIM card ICCID that must be in
active for this WWAN to be used.
11. Type the PIN for the SIM. Leave blank if no PIN is required.
12. Type the Phone number for the SIM, for SMS connections.
Normally, this should be left blank. It is only necessary to complete this field if the SIM does
not have a phone number or if the phone number is incorrect.
13. Roaming is enabled by default. Click to disable.
14. For Carrier selection mode, select one of the following:
n Automatic: The cellular carrier is selected automatically by the device.
n Manual: The cellular carrier must be manually configured. If the configured network is
not available, no cellular connection will be established.
n Manual/Automatic: The carrier is manually configured. If the configured network is not
available, automatic carrier selection is used.
If Manual or Manual/Automatic is selected:
a. For Network PLMN ID, type the PLMN ID for the cellular network.
b. For Network technology, select the technology that should be used. The default is All
technologies, which means that the best available technology will be used.
Note If Manual is configured for Carrier selection mode and a specific network
technology is selected for the Network technology, your modem must support the
selected technology or no cellular connection will be established. If you are using a cellular
connection to perform this procedure, you may lose your connection and the device will
no longer be accessible.
15. SIM failover is enabled by default, which means that the modem will automatically fail over
from the active SIM to the next available SIM when the active SIM fails to connect. If enabled:
a. For Connection attempts before SIM failover, type the number of times that the device
should attempt to connect to the active SIM before failing over to the next available SIM.
b. For SIM failover alternative, configure how SIM failover will function if automatic SIM
switching is unavailable:
n None: The device will perform no alternative action if automatic SIM switching is
unavailable.
n Reset modem: The device will reset the modem if automatic SIM switching is
unavailable.
n Reboot device: The device will reboot if automatic SIM switching is unavailable.
16. For APN list and APN list only, the EX50 device uses a preconfigured list of Access Point
Names (APNs) when attempting to connect to a cellular carrier for the first time. After the
device has successfully connected, it will remember the correct APN. As a result, it is generally
not necessary to configure APNs. See Configure cellular modem APNs for further information
and instructions for setting an APN.
17. (Optional) To configure the IP address of a custom gateway or a custom netmask:
a. Click Custom gateway to expand.
b. Click Enable.
c. For Gateway/Netmask, enter the IP address and netmask of the custom gateway. To
override only the gateway netmask, but not the gateway IP address, use all zeros for the IP
address. For example, 0.0.0.0./32 will use the network-provided gateway, but with a /32
netmask.
18. Optional IPv4 configuration items:
a. Click IPv4 to expand.
b. IPv4 support is Enabled by default. Click to disable.
c. Set the Metric.
See Configure WAN/WWAN priority and default route metrics for further information about
metrics.
d. For Weight, type the relative weight for default routes associated with this interface. For
multiple active interfaces with the same metric, Weight is used to load balance traffic to
the interfaces.
e. Set the Management priority. This determines which interface will have priority for
central management activity. The interface with the highest number will be used.
f. Set the MTU.
g. For Use DNS:
n Always: DNS will always be used for this WWAN; when multiple interfaces have the
same DNS server, the interface with the lowest metric will be used for DNS
requests.
n When primary default route: Only use the DNS servers provided for this WWAN
when the WWAN is the primary route.
n Never: Never use DNS servers for this WWAN.
The default setting is When primary default route.
19. Optional IPv6 configuration items:
a. Click IPv6 to expand.
b. IPv6 support is Enabled by default. Click to disable.
c. Set the Metric.
See Configure WAN/WWAN priority and default route metrics for further information about
metrics.
d. For Weight, type the relative weight for default routes associated with this interface. For
multiple active interfaces with the same metric, Weight is used to load balance traffic to
the interfaces.
e. Set the Management priority. This determines which interface will have priority for
central management activity. The interface with the highest number will be used.
f. Set the MTU.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n To edit an existing WWAN named my_wwan, change to the my_wwan node in the
configuration schema:
6. Set theSIM matching criteria to determine when this WWAN should be used:
n iccid
Set the unique SIM card ICCID that must be in active for this WWAN to be used:
n imsi
Set the International Mobile Subscriber Identity (IMSI) that must be in active for this
WWAN to be used:
n plmn_id
Set the PLMN id that must be in active for this WWAN to be used:
n sim_slot
Set which SIM slot must be in active for this WWAN to be used:
8. Set the phone number for the SIM, for SMS connections:
Normally, this should be left blank. It is only necessary to complete this field if the SIM does
not have a phone number or if the phone number is incorrect.
9. Roaming is enabled by default. To disable:
Note If manual is configured forthe carrier selection mode and a specific network
technology is selected for the cellular network technology, your modem must support the
selected technology or no cellular connection will be established. If you are using a cellular
connection to perform this procedure, you may lose your connection and the device will
no longer be accessible.
11. SIM failover is enabled by default, which means that the modem will automatically fail over
from the active SIM to the next available SIM when the active SIM fails to connect. To disable:
If enabled:
a. Set the number of times that the device should attempt to connect to the active SIM
before failing over to the next available SIM:
12. The EX50 device uses a preconfigured list of Access Point Names (APNs) when attempting to
connect to a cellular carrier for the first time. After the device has successfully connected, it
will remember the correct APN. As a result, it is generally not necessary to configure APNs. See
Configure cellular modem APNs for further information and instructions for setting an APN.
13. (Optional) To configure the IP address of a custom gateway or a custom netmask:
a. Enable the custom gateway:
To override only the gateway netmask, but not the gateway IP address, use all zeros for
the IP address. For example, 0.0.0.0./32 will use the network-provided gateway, but with a
/32 netmask.
14. Optional IPv4 configuration items:
a. IPv4 support is enabled by default. To disable:
See Configure WAN/WWAN priority and default route metrics for further information about
metrics.
c. Set the relative weight for default routes associated with this interface. For multiple active
interfaces with the same metric, the weight is used to load balance traffic to the interfaces.
d. Set the management priority. This determines which interface will have priority for central
management activity. The interface with the highest number will be used.
See Configure WAN/WWAN priority and default route metrics for further information about
metrics.
c. Set the relative weight for default routes associated with this interface. For multiple active
interfaces with the same metric, the weight is used to load balance traffic to the interfaces.
d. Set the management priority. This determines which interface will have priority for central
management activity. The interface with the highest number will be used.
n always: DNS will always be used for this WWAN; when multiple interfaces have the
same DNS server, the interface with the lowest metric will be used for DNS
requests.
n never: Never use DNS servers for this WWAN.
n primary: Only use the DNS servers provided for this WWAN when the WWAN is the
primary route.
The default setting is primary.
g. See Configure SureLink active recovery to detect WAN/WWAN failures for information
about configuring active recovery.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. From the menu, click Status.
3. Under Networking, click Interfaces.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Enter the show network command at the Admin CLI prompt:
>
3. Additional information can be displayed by using the show network verbose command:
----
defaultip IPv4 up static setup lan 10 10
defaultlinklocal IPv4 up static setup lan 0 10
lan IPv4 up static internal lan 5 10
lan IPv6 up static internal lan 5 10
loopback IPv4 up static loopback loopback 0 10
wan IPv4 up dhcp external wan 1 10
wan IPv6 up dhcp external wan 1 10
modem IPv4 up modem external wwan1 3 10
modem IPv6 down modem external wwan1 3 10
>
4. Enter show network interface name at the Admin CLI prompt to display additional
information about a specific WAN. For example, to display information about WAN, enter show
network interface wan:
IPv4 Status : up
IPv4 Type : dhcp
IPv4 Address(es) : 10.10.10.10/24
IPv4 Gateway : 10.10.10.1
IPv4 MTU : 1500
IPv4 Metric : 1
IPv4 Weight : 10
IPv4 DNS Server(s) : 10.10.10.2, 10.10.10.3
IPv6 Status : up
IPv6 Type : dhcpv6
IPv6 Address(es) : fe00:2404::240:f4ff:fe80:120/64
IPv6 Gateway : ff80::234:f3ff:ff0e:4320
IPv6 MTU : 1500
IPv6 Metric : 1
IPv6 Weight : 10
IPv6 DNS Server(s) : fd00:244::1, fe80::234:f3f4:fe0e:4320
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Use the del command to delete the WAN or WWAN. For example, to delete a WWAN named
my_wwan:
(config)> save
Configuration saved.
>
Interface
type Preconfigured interfaces Devices Default configuration
Local Area n LAN n Ethernet: n Firewall zone:
Network LAN Internal
(LAN) n IP address:
192.168.2.1/24
n DHCP server
enabled
n LAN priority:
Metric=5
n Surelink disabled
You can modify configuration settings for LAN, and you can create new LANs.
This section contains the following topics:
Configure a LAN
Configuring a Local Area Network (LAN) involves configuring the following items:
Note By default, LAN is set to an IP address of 192.168.2.1 and uses the IP subnet of
192.168.2.0/24. If the 1/WAN Ethernet device is being used by a WAN with the same IP subnet,
you should change the default IP address and subnet of LAN1.
n IPv6 configuration:
l The metric for IPv6 routes associated with the LAN.
l The relative weight for IPv6 routes associated with the LAN.
l The IPv6 management priority of the LAN. The active interface with the highest
management priority will have its address reported as the preferred contact address for
central management and direct device access.
l The IPv6 Maximum Transmission Unit (MTU) of the LAN.
l When to use DNS: always, never, or only when this interface is the primary default route.
l The IPv6 prefix length and ID.
l IPv6 DHCP server configuration. See DHCP servers for more information.
n MAC address denylist and allowlist.
To create a new LAN or edit an existing LAN:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
d. For Prefix length, type the minimum length of the prefix to assign to this LAN. If the
minimum length is not available, then a longer prefix will be used.
e. For Prefix ID, type the identifier used to extend the prefix to the assigned length. Leave
blank to use a random identifier.
f. Set the Metric.
g. For Weight, type the relative weight for default routes associated with this interface. For
multiple active interfaces with the same metric, Weight is used to load balance traffic to
the interfaces.
h. Set the Management priority. This determines which interface will have priority for
central management activity. The interface with the highest number will be used.
i. Set the MTU.
12. (Optional) Click to expand MAC address denylist.
Incoming packets will be dropped from any devices whose MAC addresses is included in the
MAC address denylist.
a. Click to expand MAC address denylist.
b. For Add MAC address, click .
c. Type the MAC address.
13. (Optional) Click to expand MAC address allowlist.
If there allowlist entries are specified, incoming packets will only be accepted from the listed
MAC addresses.
a. Click to expand MAC address allowlist.
b. For Add MAC address, click .
c. Type the MAC address.
14. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n To edit an existing LAN named my_lan, change to the my_lan node in the configuration
schema:
n The LAN is configured by default to use a static IP address for its IPv4 configuration. To
configure the LAN to be a DHCP client, rather than using a static IP addres:
These instructions assume that the LAN will use a static IP address for its IPv4
configuration.
a. Set the IPv4 address and subnet of the LAN interface. Use the format IPv4_
address/netmask, for example, 192.168.2.1/24.
ii. Set the relative weight for default routes associated with this interface. For multiple
active interfaces with the same metric, the weight is used to load balance traffic to
the interfaces.
iii. Set the management priority. This determines which interface will have priority for
central management activity. The interface with the highest number will be used.
See DHCP servers for information about configuring the DHCP server.
7. (Optional) Configure IPv6 settings:
a. Enable IPv6 support:
c. Generally, the default settings for IPv6 support are sufficient. You can view the default IPv6
settings by using the question mark (?):
IPv6
----------
enable true Enable
metric 0 Metric
mgmt 0 Management priority
mtu 1500 MTU
prefix_id 1 Prefix ID
prefix_length 48 Prefix length
type prefix_delegation Type
weight 10 Weight
Additional Configuration
---------------------------------------------------------------------
----------
connection_monitor Active recovery
dhcpv6_server DHCPv6 server
DHCPv6 server: The DHCPv6 server settings for this network interface.
d. Modify any of the remaining default settings as appropriate. For example, to change the
minimum length of the prefix:
If the minimum length is not available, then a longer prefix will be used.
See Configure WAN/WWAN priority and default route metrics for further information about
metrics.
(Optional) Configure the MAC address deny list.
Incoming packets will be dropped from any devices whose MAC addresses is included in the
MAC address denylist.
a. Add a MAC address to the denylist:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
6. Set the password that clients will use when connecting to the access point:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
b. Set the number of seconds that the device will spend in each of the listening and learning
states before the bridge begins forwarding data:
3. Create LAN1:
a. Click Network > Interfaces.
b. For Add Interface:, type LAN1 and click .
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. From the menu, click Status.
3. Under Networking, click Interfaces.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Enter the show network command at the Admin CLI prompt:
>
3. Additional information can be displayed by using the show network verbose command:
>
4. Enter show network interface name at the Admin CLI prompt to display additional
information about a specific LAN. For example, to display information about LAN, enter show
network interface lan:
IPv4 Status : up
IPv4 Type : static
IPv4 Address(es) : 192.168.2.1/24
IPv4 Gateway :
IPv4 MTU : 1500
IPv4 Metric : 5
IPv4 Weight : 10
IPv4 DNS Server(s) :
IPv6 Status : up
IPv6 Type : prefix
IPv6 Address(es) : fd00:2704::1/48
IPv6 Gateway :
IPv6 MTU : 1500
IPv6 Metric : 5
IPv6 Weight : 10
IPv6 DNS Server(s) :
>
Delete a LAN
Follow this procedure to delete any LANs that have been added to the system. You cannot delete the
preconfigured LAN, LAN1.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Use the del command to delete the LAN. For example, to delete a LAN named my_lan:
(config)> save
Configuration saved.
>
DHCP servers
You can enable DHCP on your EX50 device to assign IP addresses to clients, using either:
n The DHCP server for the device's local network, which assigns IP addresses to clients on the
device's local network. Addresses are assigned from a specified pool of IP addresses. For a
local network, the device uses the DHCP server that has the IP address pool in the same
IP subnet as the local network.
When a host receives an IP configuration, the configuration is valid for a particular amount of
time, known as the lease time. After this lease time expires, the configuration must be
renewed. The host renews the lease time automatically.
n A DHCP relay server, which forwards DHCP requests from clients to a DHCP server that is
running on a separate device.
Note These instructions assume you are configuring the device to use its local DHCP server. For
instructions about configuring the device to use a DHCP relay server, see Configure DHCP relay.
n The lease address pool: the range of IP addresses issued by the DHCP server to clients.
n Lease time: The length, in minutes, of the leases issued by the DHCP server.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
address (the final triplet in an IPv4 address, for example, 192.168.2.xxx). The remainder of the
IP address will be based on the LAN's static IP address as defined in the Address field.
Allowed values are between 1 and 254, and the default is 100 for Lease range start and 250
for Lease range end.
9. Optional DHCP server settings:
a. Click to expand Advanced settings.
b. For Gateway, select either:
n None: No gateway is broadcast by the DHCP server. Client destinations must be
resolvable without a gateway.
n Automatic: Broadcasts the EX50 device's gateway.
n Custom: Allows you to identify the IP address of a Custom gateway to be
broadcast.
The default is Automatic.
c. For MTU,
n None: An MTU of length 0 is broadcast. This is not recommended.
n Automatic: No MTU is broadcast and clients will determine their own MTU.
n Custom: Allows you to identify a Custom MTU to be broadcast.
The default is Automatic.
d. For Domain name suffix, type the domain name that should be appended to host names.
e. For Primary and Secondary DNS, Primary and Secondary NTP server, and Primary and
Secondary WINS server, select either:
n None: No server is broadcast.
n Automatic: Broadcasts the EX50 device's server.
n Custom: Allows you to identify the IP address of the server.
f. For Bootfile name, type the relative path and file name of the bootfile on the TFTP server.
g. For TFTP server name, type the IP address or host name of the TFTP server.
10. See Configure DHCP options for information about Custom DHCP options.
11. See Map static IP addresses to hosts for information about Static leases.
12. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
3. Enable the DHCP server for an existing LAN. For example, to enable the DHCP server for a LAN
named my_lan:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set network interface my_lan ipv4 dhcp_server lease_time to ten minutes,
enter either 10m or 600s:
5. (Optional) Set the lowest IP address that the DHCP server will assign to a client. This value
represents the low order byte of the address (the final triplet in an IPv4 address, for example,
192.168.2.xxx). The remainder of the IP address will be based on the LAN's static IP address as
defined in the address parameter.
Allowed values are between 1 and 254, and the default is 100.
6. (Optional) Set the highest IP address that the DHCP server will assign to a client:
Allowed values are between 1 and 254, and the default is 250.
7. Optional DHCP server settings:
a. Click to expand Advanced settings.
b. Determine how the DHCP server should broadcast the gateway server:
e. Set the IP address or host name of the primary and secondary DNS, the primary and
secondary NTP server, and the primary and secondary WINS servers:
n custom: Allows you to identify the IP address of the server. For example:
g. Set the relative path and file name of the bootfile on the TFTP server:
8. See Configure DHCP options for information about custom DHCP options.
9. See Map static IP addresses to hosts for information about static leases.
10. Save the configuration and apply the change:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note The IP address here should be outside of the DHCP server's configured lease range. See
Configure a DHCP server for further information about the lease range.
9. (Optional) For Hostname, type a label for the static lease. This does not have to be the
device's actual hostname.
10. Repeat for each additional DHCP static lease.
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
3. Add a static lease to the DHCP server configuration for an existing LAN. For example, to add
static lease to a LAN named my_lan:
Note The IP address here should be outside of the DHCP server's configured lease range. See
Configure a DHCP server for further information about the lease range.
WebUI
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Show the static lease configuration. For example, to show the static leases for a lan named
my_lan:
(config)> cancel
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Show the static lease configuration. For example, to show the static leases for a lan named
my_lan:
mac E3:C1:1F:65:C3:0E
no name
(config)>
4. Use the del index_number command to delete a static lease. For example, to delete the static
lease for the device listed in the above output with a mac address of BF:C3:46:24:0E:D9 (index
number 0):
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a custom DHCP option to the DHCP server configuration for an existing LAN. For example,
to add static lease to a LAN named my_lan:
8. (Optional) To force the DHCP option to always be sent to the client, even if the client does not
ask for it:
If the incorrect data type is selected, the device will send the value as a string.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a DHCP relay server to an existing LAN. For example, to add a server to a LAN named my_
lan:
WebUI
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Enter the show dhcp-lease command at the Admn CLI prompt:
>
3. Additional information can be returned by using the show dhcp-lease verbose command:
>
To create a VLAN:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Bridging
Bridging is a mechanism to create a single network consisting of multiple devices, such as Ethernet
devices and wireless access points.
By default, the EX50 has the following preconfigured bridges:
Interface Default
type Preconfigured interfaces Devices configuration
Bridges n Bridge: LAN n Ethernet: LAN n Enabled
n Wi-Fi access
point: Digi AP
(Wi-Fi1)
n Wi-Fi access
point: Digi AP
(Wi-Fi2)
You can modify configuration settings for the existing bridge, and you can create new bridges.
This section contains the following topics:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note The MAC address of the bridge is taken from the first available device in the list.
a. To delete a device from the bridge, click the down arrow () next to the field label and
select Delete.
b. To add a device, for Add device, click and select the Device.
6. (Optional) Enable Spanning Tree Protocol (STP).
STP is used when using multiple LANs on the same device, to prevent bridge loops and other
routing conflicts.
a. Click STP.
b. Click Enable.
c. For Forwarding delay, enter the number of seconds that the device will spend in each of
the listening and learning states before the bridge begins forwarding data. The default is 2
seconds.
7. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Modify the list of devices that are a part of the bridge. By default, the LAN bridge includes the
following devices:
n Ethernet: LAN
n Wi-Fi access point: Digi AP (Wi-Fi1)
n Wi-Fi access point: Digi AP (Wi-Fi2)
Note The MAC address of the bridge is taken from the first available device in the list.
ii. Use the index number to delete the appropriate device. For example, to delete the
Digi AP (Wi-Fi1) Wi-Fi access point from the bridge:
Note If you are deleting multiple devices from the bridge, the device index may be
reordered after each deletion. As a result, best practice is to perform a show network
bridge lan1 device command after each device is deleted to determine the new index
numbering.
ii. Add the appropriate device. For example, to add the Digi AP (Wi-Fi1) Wi-Fi access
point:
b. Set the number of seconds that the device will spend in each of the listening and learning
states before the bridge begins forwarding data:
(config)> save
Configuration saved.
>
Configure a bridge
Required configuration items
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note The MAC address of the bridge is taken from the first available device in the list.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
b. Add the appropriate device. For example, to add the Digi AP (Wi-Fi1) Wi-Fi access point:
Note The MAC address of the bridge is taken from the first available device in the list.
b. Set the number of seconds that the device will spend in each of the listening and learning
states before the bridge begins forwarding data:
(config)> save
Configuration saved.
>
n Enabled
n Serial mode: Login
n Label: None
n Baud rate: 9600
n Data bits: 8
n Parity: None
n Stop bits: 1
n Flow control: None
n Enabled
n Serial mode: Login
n Label: None
n Baud rate: 9600
n Data bits: 8
n Parity: None
n Stop bits: 1
n Flow control: None
To change the configuration to match the serial configuration of the device to which you want to
connect:
WebUI
3. Note You can also configure the serial port by using Device Configuration > Serial. Changes
made by using either Device Configuration or Serial Configuration will be reflected in both.
b. For Baud rate, select the baud rate used by the device to which you want to connect.
c. For Data bits, select the number of data bits used by the device to which you want to
connect.
d. For Parity, select the type of parity used by the device to which you want to connect.
e. For Stop bits, select the number of stop bits used by the device to which you want to
connect.
f. For Flow control, select the type of flow control used by the device to which you want to
connect.
8. (Optional) If Remote Access is selected for Mode:
a. Click to expand Service Settings.
All service settings are disabled by default. Click available options to toggle them to
enabled, and set the IP ports as appropriate.
b. Click to expand Session Settings.
c. Enable Exclusive access to limit access to the serial port to a single active session.
d. For Escape sequence, type the characters used to start an escape sequence. If no
characters are defined, the escape sequence is disabled. The default is ~b.
e. For History size, type or select the number of bytes of output from the serial port that are
written to buffer. These bytes are redisplayed when a user connects to the serial port. The
default is 4000 bytes.
f. For Idle timeout, type the amount of time to wait before disconnecting due to user
inactivity.
1. Click to expand Monitor Settings.
a. For Copy Port 1 configuration to these ports:, type the names of the ports that the
configuration should be copied to.
b. For Copy these settings, select the types of settings that should be copied to the selected
ports.
c. Click Copy.
10. Click Apply to save the configuration and apply the change.
The Apply button is located at the top of the WebUI page. You may need to scroll to the top of
the page to locate it.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
b. Set the number of data bits used by the device to which you want to connect:
c. Set the type of parity used by the device to which you want to connect:
e. Set the type of flow control used by the device to which you want to connect:
If no characters are defined, the escape sequence is disabled. The default is ~b.
b. Limit access to the serial port to a single active session:
c. Set the number of bytes of output from the serial port that are written to buffer. These
bytes are redisplayed when a user connects to the serial port.
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set idle_timeout to ten minutes, enter either 10m or 600s:
f. (Optional) Enable monitoring of DCD (Data Carrier Detect) changes on this port:
iv. (Optional) Configure the access control list to limit access to the TCP connection:
n To limit access to specified IPv4 addresses and networks:
(config serial USB_port)> add service tcp acl zone end value
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
-------------------------------------------------
------------------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
iii. (Optional) Configure the access control list to limit access to the telnet connection:
n To limit access to specified IPv4 addresses and networks:
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
-------------------------------------------------
------------------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
iii. (Optional) Configure the access control list to limit access to the ssh connection:
(config serial USB_port)> add service ssh acl zone end value
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
-------------------------------------------------
------------------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)> save
Configuration saved.
>
Note You can also configure the serial port by using Device Configuration > Serial. Changes
made by using either Device Configuration or Serial Configuration will be reflected in both.
3. Click to expand the port that you want to configure for UDP serial mode.
a. For Baud rate, select the baud rate used by the device to which you want to connect.
b. For Data bits, select the number of data bits used by the device to which you want to
connect.
c. For Parity, select the type of parity used by the device to which you want to connect.
d. For Stop bits, select the number of stop bits used by the device to which you want to
connect.
e. For Flow control, select the type of flow control used by the device to which you want to
connect.
a. For Local port, enter the UDP port. The default is 4001 or serial port 1, 4002 for serial port
2, etc.
b. (Optional) For Socket String ID, enter a string that should be added at the beginning of
each packet.
c. For Destinations, you can configure the remote sites to which you want to send data. If
you do not specify any destinations, the EX50 send new data to the last hostname and
port from which data was received. To add a destination:
i. Click Add Destination. A destination row is added.
ii. (Optional) For Description, enter a description of the destination.
iii. For Hostname, enter the host name or IP address of the remote site to which data
should be sent.
iv. For Port, enter the port number of the remote site to which data should be sent.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click Status
3. Under Connections, click Serial.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the show serial command:
WebUI
Wi-Fi configuration
EX50 device has two Wi-Fi radios. You can configure the Wi-Fi radios for Wi-Fi access point mode or
Wi-Fi client mode. By default, the EX50 radios are configured to use access point mode.
n Radios:
n Access points:
n 2.4 GHz band—Channels 1 to 11 are supported. Channels 12, 13, and 14 are not supported.
n 5 GHz band—By default, only non-Dynamic Frequency Selection (DFS) channels are supported.
You can also enable support for DFS channels in client mode. See Configure the Wi-Fi radio to
support DFS channels in client mode for information about enabling DFS support.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
5. For Channel, select the channel. Only channels appropriate for the band are displayed.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
---------------------------------------------------------------------
----------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
(config)> save
Configuration saved.
>
Note If DFS functionality is enabled, any access points enabled on the EX50 device will not be started.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note When DFS Client Support is enabled, any enabled access points that use this radio will
not be started and cannot be used as access points.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
---------------------------------------------------------------------
----------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
Note When DFS client support is enabled, any enabled access points that use this radio
will not be started and cannot be used as access points.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
----------------------------------------------------------------------
---------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
----------------------------------------------------------------------
---------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
where value is any integer between 1 and 100 and represents the percentage of transmit
power that the Wi-Fi module should use.
4. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note Only select WPA3 Enhanced Open (OWE) if you know that all Wi-Fi clients
connecting to this device will have WPA3 capabilities.
11. (Optional) For Group rekey interval, type the amount of time to wait before changing the
group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
Allowed values are any number of days, hours, minutes, or seconds, and take the format
number{d|h|m|s}.
For example, to set Group rekey interval to ten minutes, enter 10m or 600s.
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
12. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
13. Click Apply to save the configuration and apply the change.
Command line
Configure a new Access point
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. Set the SSID for the Wi-Fi access point. Up to 32 characters are allowed.
Note Only select owe if you know that all Wi-Fi clients connecting to this device will
have WPA3 capabilities.
7. (Optional) Determine whether to prevent clients that are connected to this access point from
communicating with each other:
See Isolate Wi-Fi clients for information about how to prevent clients connected to different
access points from communicating with each other.
8. (Optional) Set the amount of time to wait before changing the group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
where value is any number of days, hours, minutes, or seconds, and takes the format number
{d|h|m|s}.
For example, to set group rekey interval to ten minutes, enter either 10m or 600s:
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
1. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
2. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
------------------------------------------------------------------------
-------
digi_ap1 Digi AP (Wi-Fi1)
digi_ap2 Digi AP (Wi-Fi2)
(config)>
5. SSID broadcasting is enabled by default for the preconfigured access points. If SSID
broadcasting is disabled:
6. Set the security for the access point to an open security method:
Note Only select owe if you know that all Wi-Fi clients connecting to this device will
have WPA3 capabilities.
7. (Optional) Determine whether to prevent clients that are connected to this access point from
communicating with each other:
See Isolate Wi-Fi clients for information about how to prevent clients connected to different
access points from communicating with each other.
8. (Optional) Change the Wi-Fi radio for the access point:
a. Show available radios:
Additional Configuration
---------------------------------------------------------------------
----------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
(config)>
9. (Optional) Set the amount of time to wait before changing the group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
where value is any number of days, hours, minutes, or seconds, and takes the format number
{d|h|m|s}.
For example, to set group rekey interval to ten minutes, enter either 10m or 600s:
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
1. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
2. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note Only select Personal (SAE) if you know that all Wi-Fi clients connecting to this
device will have WPA3 capabilities.
11. For Pre-shared key, enter the password that clients will use when connecting to the access
point.
12. (Optional) For Group rekey interval, type the amount of time to wait before changing the
group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
Allowed values are any number of days, hours, minutes, or seconds, and take the format
number{d|h|m|s}.
For example, to set Group rekey interval to ten minutes, enter 10m or 600s.
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
13. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
14. Click Apply to save the configuration and apply the change.
Command line
Configure a new Access point
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
5. Set the SSID for the Wi-Fi access point. Up to 32 characters are allowed.
7. (Optional) Determine whether to prevent clients that are connected to this access point from
communicating with each other:
See Isolate Wi-Fi clients for information about how to prevent clients connected to different
access points from communicating with each other.
8. Set the password that clients will use when connecting to the access point:
where key_type varies depending on the selection for encryption type, above:
n If type is set to psk, key_type is key_psk.
n If type is set to mixedpsk, key_type is key_mixedpsk.
n If type is set to psk2, key_type is key_psk2.
n If type is set to psk2sae, key_type is key_psk2sae.
n If type is set to sae, key_type is key_sae.
For example, if type is set to psk2sae, set key_psk2sae to the appropriate password:
Note The encryption key type must correspond to the configured encryption type. If you set an
encyrption key type that does not correspond to the configured encryption type, you will not
be able to save the configuration.
9. (Optional) Set the amount of time to wait before changing the group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
where value is any number of days, hours, minutes, or seconds, and takes the format number
{d|h|m|s}.
For example, to set group rekey interval to ten minutes, enter either 10m or 600s:
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
1. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
2. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
> config
(config)>
Additional Configuration
------------------------------------------------------------------------
-------
digi_ap1 Digi AP (Wi-Fi1)
digi_ap2 Digi AP (Wi-Fi2)
(config)>
5. SSID broadcasting is enabled by default for the preconfigured access points. If SSID
broadcasting is disabled:
6. Set the security for the access point to a personal security option:
7. (Optional) Determine whether to prevent clients that are connected to this access point from
communicating with each other:
See Isolate Wi-Fi clients for information about how to prevent clients connected to different
access points from communicating with each other.
8. Set the password that clients will use when connecting to the access point:
Additional Configuration
---------------------------------------------------------------------
----------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
(config)>
10. (Optional) Set the amount of time to wait before changing the group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
where value is any number of days, hours, minutes, or seconds, and takes the format number
{d|h|m|s}.
For example, to set group rekey interval to ten minutes, enter either 10m or 600s:
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
1. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
2. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
n Configure security for the access point to WPA2 enterprise or WPA3 enterprise.
Note Only select WPA3 Enterprise if you know that all Wi-Fi clients connecting to this device
will have WPA3 capabilities.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note Only select WPA3 Enterprise if you know that all Wi-Fi clients connecting to this
device will have WPA3 capabilities.
e. For RADIUS secret key, type the secret key as configured on the RADIUS server.
12. (Optional) For Group rekey interval, type the amount of time to wait before changing the
group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
Allowed values are any number of days, hours, minutes, or seconds, and take the format
number{d|h|m|s}.
For example, to set Group rekey interval to ten minutes, enter 10m or 600s.
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
13. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
14. Click Apply to save the configuration and apply the change.
Command line
Configure a new Access point
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
5. Set the SSID for the Wi-Fi access point. Up to 32 characters are allowed.
Note Only select wpa3 if you know that all Wi-Fi clients connecting to this device will
have WPA3 capabilities.
7. (Optional) Determine whether to prevent clients that are connected to this access point from
communicating with each other:
See Isolate Wi-Fi clients for information about how to prevent clients connected to different
access points from communicating with each other.
8. Configure one or more RADIUS servers:
a. Set the IP address of the RADIUS server:
ii. Configure the new server as described above. For example, set the server IP address:
where value is any number of days, hours, minutes, or seconds, and takes the format number
{d|h|m|s}.
For example, to set group rekey interval to ten minutes, enter either 10m or 600s:
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
1. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
2. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
> config
(config)>
Additional Configuration
------------------------------------------------------------------------
-------
digi_ap1 Digi AP (Wi-Fi1)
digi_ap2 Digi AP (Wi-Fi2)
(config)>
5. SSID broadcasting is enabled by default for the preconfigured access points. If SSID
broadcasting is disabled:
6. Set the security for the access point to an enterprise security option:
Note Only select wpa3 if you know that all Wi-Fi clients connecting to this device will
have WPA3 capabilities.
7. (Optional) Determine whether to prevent clients that are connected to this access point from
communicating with each other:
See Isolate Wi-Fi clients for information about how to prevent clients connected to different
access points from communicating with each other.
8. Set the IP address or hostname of the RADIUS server:
10. (Optional) Set the RADIUS server's port. The default is 1812.
11. (Optional) Change the Wi-Fi radio for the access point:
a. Show available radios:
Additional Configuration
---------------------------------------------------------------------
----------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
(config)>
12. (Optional) Set the amount of time to wait before changing the group key.
The group key is shared by all in clients of the access point, and after a client has
disconnected, it will be able to use the group key to decrypt broadcast packets until the key is
changed.
where value is any number of days, hours, minutes, or seconds, and takes the format number
{d|h|m|s}.
For example, to set group rekey interval to ten minutes, enter either 10m or 600s:
Increasing the time between rekeys can improve connectivity issues in noisy environments. To
disable group rekeys, set to 0. This will allow any client that has previously connected see all
broadcast traffic on the wireless network until the Wi-Fi radio is restarted. The default is 10
minutes.
1. Assign the Wi-Fi access point to a LAN interface or to a bridge. See Configure a LAN and
Configure a bridge for more information.
The access point must be assigned to an active LAN, or a bridge that is assigned to an active
LAN.
2. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Create a new access point or modify an existing access point. See Configure an open Wi-Fi
access point, Configure a Wi-Fi access point with personal security, or Configure a Wi-Fi access
point with enterprise security.
4. (Optional) Set the client isolation:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
d. Create a firewall filter to drop traffic from the Internal zone (used by the LAN1 interface)
to the LAN2_isolation_zone:
i. Click Firewall > Packet filtering.
ii. For Add packet filter, click .
iii. For Label, type Drop traffic from Internal to LAN2_isolation_zone.
iv. For Action, select Drop.
v. For Source zone, select Internal.
vi. For Destination zone, select LAN2_isolation_zone.
5. Remove the Digi AP (Wi-Fi2) access point from the LAN1 bridge:
a. Click Network > Bridges > LAN1.
b. Click the down arrow () next to the the Digi AP (Wi-Fi2) access point and select Delete.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
c. Set the SSID for the Wi-Fi access point. Up to 32 characters are allowed.
b. Add a new firewall zone named LAN2_isolation_zone. We will be creating LAN2 later in
the procedure.
d. Create a firewall filter to drop traffic from the Internal zone (used by the LAN1 interface)
to the LAN2_isolation_zone:
Firewall filters are applied in the order that they are listed. As a result, in order to drop
traffic from the Internal zone to the LAN2_isolation_zone, this filter must be added
before the Allow all outgoing traffic filter, which allows the Internal zone to have access
to any zone. In this example, we will add the new to the first position in the list (index
position 0).
i. Add the new packet filter:
access point; in the next step, we will remove the Digi AP (Wi-Fi2) access point from the
default bridge (and thus from the default LAN).
a. Return to the root config prompt by typing three periods (...):
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
New Wi-Fi clients are enabled by default. To disable, or to enable a client if it has been
disabled, click Enable.
5. For Radio, select the appropriate Wi-Fi radio.
6. Configure the Wi-Fi network that the client will use:
a. Click to expand SSID list.
b. Enter the SSID of the access point that the client will use to connect to the Wi-Fi network.
c. Select the type of Encryption used by the access point.
n If a personal or mixed mode is selected, for Pre-shared key, enter the password
that the client will use to connect to the access point.
n If WPA2 Enterprise or WPA3 Enterprise is selected as the type of Encryption,
enter the Username and Password that the client will use to connect to the access
point.
7. (Optional) Configure Background scanning.
Background scanning allows the device to scan for nearby access points and to move between
access points that have the same SSID that is configured for the client connection, based on
the signal strength of the access points.
a. Click to expand Background scanning.
h. To add a channel, click Add Scan frequency and select the appropriate channel.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
---------------------------------------------------------------------
----------
wifi1 Wi-Fi1 radio
wifi2 Wi-Fi2 radio
where value is the type of encryption used by the access point. Allowed values are:
n none: no encryption.
n owe: WPA3 Enhanced Open, which uses Opportunistic Wireless Encryption (OWE)
technology to provide encryption for Wi-Fi networks that do not use password
protection.
n psk: WPA personal encryption.
n mixedpsk: Uses both WPA and WPA2 personal encryption.
n psk2: WPA2 personal encryption.
n psk2sae: Uses WPA2-PSK/WPA3-AES mixed mode.
n sae: Uses WPA3 Personal mode.
n wpa2: WPA2 enterprise encryption.
n wpa3: WPA3 enterprise encryption.
c. If the type of encryption is set to:
n psk, mixedpak, psk2, psk2sae, or sae, set the password that the client will use to
connect to the access point:
n wpa2 or wpa3:
i. Set the username that the client will use to connect to the access point:
ii. Set the password that the client will use to connect to the access point:
b. Set the scan threshold (bgscan_strength), in dB, that is used to determine the scanning
frequency.
n 2412 MHz
n 2437 MHz
n 2462 MHz
You can delete the preconfigured frequencies and add additional frequencies. At least one
frequencies is required.
f. To delete a preconfigured frequencies:
i. Use the show command to determine the index number of the channel to be deleted:
ii. Use the appropriate index number to delete the channel. For example, to delete the
2412 frequency:
g. To add a frequency:
i. Use the ? with an existing index number to determine the allowed values for
frequencies:
ii. Add the appropriate frequency. For example, to add the 2457 frequency to the end of
the list:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click Status.
3. Under Connections, click Wi-Fi > Access Points.
Command line
Show summary of Wi-Fi access points
To show the status and statistics for Wi-Fi access points, use the show wifi command.
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type show wifi ap:
>
3. To view information about both active and inactive access points, include the all parameter:
>
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type show wifi ap name name:
SSID : my_AP
Security : none
Channel :
Channel Width :
Radio : wifi1
BSSID : 01:41:D1:14:36:37
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click Status.
3. Under Connections, click Wi-Fi > Clients.
Command line
Show summary of Wi-Fi clients
To show the status and statistics for Wi-Fi client, use the show wifi command.
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type show wifi client:
>
3. To view information about both active and inactive clients, include the all parameter:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type show wifi cleint name name:
Client : my_client
Enabled : true
SSID : my_SSID
Status : up
Signal : -43
MAC Address : 91:fe:86:d1:0e:81
Channel : 48
Radio : wifi1
TX Power : 23
Link Quality : 67/70
BSSID : 6D:B9:DD:BD:EE:C4
>
IP routing 235
Show the routing table 262
Dynamic DNS 263
Virtual Router Redundancy Protocol (VRRP) 269
IP routing
The EX50 device uses IP routes to decide where to send a packet it receives for a remote network. The
process for deciding on a route to send the packet is as follows:
1. The device examines the destination IP address in the IP packet, and looks through the IP
routing table to find a match for it.
2. If it finds a route for the destination, it forwards the IP packet to the configured IP gateway or
interface.
3. If it cannot find a route for the destination, it uses a default route.
4. If there are two or more routes to a destination, the device uses the route with the longest
mask.
5. If there are two or more routes to a destination with the same mask, the device uses the route
with the lowest metric.
This section contains the following topics:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
New static route configurations are enabled by default. To disable, click to toggle Enable to
off.
5. (Optional) For Label, type a label that will be used to identify this route.
6. For Destination, type the IP address or network of the destination of this route.
For example, to route traffic to the 192.168.47.0 network that uses a subnet mask of
255.255.255.0, type 192.168.47.0/24. The any keyword can also be used to route packets to
any destination with this static route.
7. For Interface, select the interface on the EX50 device that will be used with this static route.
8. (Optional) For Gateway, type the IPv4 address of the gateway used to reach the destination.
Set to blank if the destination can be accessed without a gateway.
9. (Optional) For Metric, type the metric for the route. When multiple routes are available to
reach the same destination, the route with the lowest metric is used.
10. (Optional) For MTU, type the Maximum Transmission Units (MTU) of network packets using this
route.
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. (Optional) set a label that will be used to identify this route. For example:
5. Set the IP address or network of the destination of this route. For example:
For example, to route traffic to the 192.168.47.0 network that uses a subnet mask of
255.255.255.0:
The any keyword can also be used to route packets to any destination with this static route.
6. Set the interface on the EX50 device that will be used with this static route:
a. Use the ? to determine available interfaces:
7. (Optional) Set the IPv4 address of the gateway used to reach the destination. Set to blank if
the destination can be accessed without a gateway.
8. (Optional) Set the metric for the route. When multiple routes are available to reach the same
destination, the route with the lowest metric is used.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
Policy-based routing
Normally, a routing device determines how to route a network packet based on its destination
address. However, you can use policy-based routing to forward the packet based on other criteria,
such as the source of the packet. For example, you can configure the EX50 device so that high-priority
traffic is routed through the cellular connection, while all other traffic is routed through an Ethernet
(WAN) connection.
Policy-based routing for the EX50 device uses the following criteria to determine how to route traffic:
n Firewall zone (for example, internal/outbound traffic, external/inbound traffic, or IPSec tunnel
traffic).
n Network interface (for example, the cellular connection, the WAN, or the LAN).
n IPv4 address.
n IPv6 address.
n MAC address.
n Domain.
n Protocol type (TCP, UDP, ICMP, or all).
The order of the policies is important. Routing policies are processed sequentially; as a result, if a
packet matches an earlier policy, it will be routed using that policy’s rules. It will not be processed by
any subsequent rules.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. (Optional) Set the label that will be used to identify this route policy:
5. Set the interface on the EX50 device that will be used with this route policy:
a. Use the ? to determine available interfaces:
6. (Optional) Enable exclusive to configure the policy to drop packets that match the policy when
the gateway interface is disconnected, rather than forwarded through other interfaces:
where value is the port number, or the keyword any to match any port as the
source port.
b. Set the destination port:
where value is the port number, or the keyword any to match any port as the
destination port.
n upd: Source and destination ports are matched:
a. Set the source port:
where value is the port number, or the keyword any to match any port as the
source port.
where value is the port number, or the keyword any to match any port as the
destination port.
n icmp: The ICMP protocol is matched. Identify the ICMP type:
where value is the ICMP type and optional code, or set to any to match for any ICMP
type.
9. Set the source address type:
n address: Matches the source IPv4 address to the specified IP address or network. Set
the address that will be matched:
where value uses the format IPv4_address[/netmask], or any to match any IPv4
address.
n address6: Matches the source IPv6 address to the specified IP address or network. Set
the address that will be matched:
where value uses the format IPv6_address[/prefix_length], or any to match any IPv6
address.
n mac: Matches the source MAC address to the specified MAC address. Set the MAC
address to be matched:
n address: Matches the destination IPv4 address to the specified IP address or network.
Set the address that will be matched:
where value uses the format IPv4_address[/netmask], or any to match any IPv4
address.
n address6: Matches the destination IPv6 address to the specified IP address or network.
Set the address that will be matched:
where value uses the format IPv6_address[/prefix_length], or any to match any IPv6
address.
n mac: Matches the destination MAC address to the specified MAC address. Set the MAC
address to be matched:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
b. Set the label that will be used to identify this route policy:
ii. Set the IP address that will be the destination for outgoing traffic routed through the
WWAN interface. In the above example, this is 241.236.162.59.
(config)> save
Configuration saved.
>
b. Create second firewall zone named EthernetWAN with Source NAT enabled:
i. For Add Zone, type EthernetWAN and click .
ii. Enable Source NAT.
4. Configure the WAN interfaces to use the new zones:
a. Configure the cellular WAN interface:
i. Click Network > Interfaces > .
ii. For Zone, select CellularWAN.
6. Create a packet filtering rule that rejects all other LAN packets on the cellular WAN interface.
a. Click Firewall > Packet filtering.
b. Click the to add a new packet filtering rule.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
b. Create second firewall zone named EthernetWAN with Source NAT enabled:
i. Type .. to move back one node in the configuration:
5. Configure the policy-based route for traffic from the client device that will be sent over the
cellular WAN:
b. Set the label that will be used to identify this route policy:
ii. Set the MAC address to the MAC address of the VoIP phone:
6. Create a packet filtering rule that rejects all other LAN packets on the cellular WAN interface:
a. Create a new packet filtering rule:
i. Type ... to move to the root of the configuration:
(config firewall filter 2)> label "Reject LAN traffic to cellular WAN"
(config firewall filter 2)>
Routing services
Your EX50 includes support for dynamic routing services and protocols. The following routing services
are supported:
Service or
protocol Information
RIP The IPv4 Routing Information Protocol (RIP) service supports RIPv2 (RFC2453)
and RIPv1 (RFC1058).
RIPng The IPv6 Routing Information Protocol (RIP) service supports RIPng (RFC2080).
OSPFv2 The IPv4 Open Shortest Path First (OSPF) service supports OSPFv2 (RFC2328).
OSPFv3 The IPv6 Open Shortest Path First (OSPF) service supports OSPFv3 (RFC2740).
BGP The Border Gateway Protocol (BGP) service supports BGP-4 (RFC1771).
IS-IS The IPv4 and IPv6 Intermediate System to Intermediate System (IS-IS) service.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
The default firewall zone setting, Dynamic routes, is specifically designed to work with routing
services and should be left as the default.
5. Configure the routing services that will be used:
a. Click to expand a routing service.
b. Enable the routing service.
c. Complete the configuration of the routing service.
6. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
---------------------------------------------------------------------
----------
bgp BGP
isis IS-IS
ospfv2 OSPFv2
ospfv3 OSPFv3
rip RIP
ripng RIPng
(config)>
b. Enable a routing service that will be used. For example, to enable the RIP service:
c. Complete the configuration of the routing service. For example, use the ? to view the
available parameters for the RIP service:
Additional Configuration
---------------------------------------------------------------------
----------
interface Interfaces
neighbour Neighbours
redis Route redistribution
timer Timers
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type show route:
You can limit the display to only IPv4 entries by using show route ipv4, or to IPv6 entries by
using show route ipv6. You can also display more information by adding the verbose option
to the show route and show route ip_type commands.
3. Type exit to exit the Admin CLI.
Depending on your device configuration, you may be presented with an Access selection
menu. Type quit to disconnect from the device.
Dynamic DNS
The Domain Name System (DNS) uses name servers to provide a mapping between computer-
readable IP addresses and human-readable hostnames. This allows users to access websites and
personal networks with easy-to-remember URLs. Unfortunately, IP addresses change frequently,
invalidating these mappings when they do. Dynamic DNS has become the standard method of
addressing this problem, allowing devices to update name servers with their new IP addresses.
By providing the EX50 device with the domain name and credentials obtained from a dynamic DNS
provider, the router can automatically update the remote nameserver whenever your WAN or public
IP address changes.
Your EX50 device supports a number of Dynamic DNS providers as well as the ability to provide a
custom provider that is not included on the list of providers.
n If the Dynamic DNS service provider is set to custom, identify the URL that should be used to
update the IP address with the Dynamic DNS provider.
n The amount of time to wait to check if the interface's IP address needs to be updated.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
New Dynamic DNS configurations are enabled by default. To disable, click to toggle Enable to
off.
5. For Interface, select the interface that has its IP address registered with the Dynamic DNS
provider.
6. For Service, select the Dynamic DNS provider, or select custom to enter a custom URL for the
Dynamic DNS provider.
7. If custom is selected for Service, type the Custom URL that should be used to update the IP
address with the Dynamic DNS provider.
8. Type the Domain name that is linked to the interface's IP address.
9. Type the Username and Password used to authenticate with the Dynamic DNS provider.
10. (Optional) For Check Interval, type the amount of time to wait to check if the interface's IP
address needs to be updated.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Check interval to ten minutes, enter 10m or 600s.
11. (Optional) For Forced update interval, type the amount of time to wait to force an update of
the interface's IP address.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Forced update interval to ten minutes, enter 10m or 600s.
The setting for Forced update interval must be larger than the setting for Check Interval.
12. (Optional) For Retry interval, type the amount of time to wait for an IP address update to
succeed before retrying the update.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Retry interval to ten minutes, enter 10m or 600s.
13. (Optional) For Retry count, type the number of times to retry a failed IP address update.
14. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a new Dynamic DNS instance. For example, to add an instance named new_ddns_
instance:
6. If custom is configured for service, set the custom URL that should be used to update the IP
address with the Dynamic DNS provider:
10. (Optional) Set the amount of time to wait to check if the interface's IP address needs to be
updated:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set check_interval to ten minutes, enter either 10m or 600s:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set force_interval to ten minutes, enter either 10m or 600s:
12. (Optional) Set the amount of time to wait for an IP address update to succeed before retrying
the update:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set retry_interval to ten minutes, enter either 10m or 600s:
(config)> save
Configuration saved.
>
VRRP+
VRRP+ is an extension to the VRRP standard that uses network probing to monitor connections
through VRRP-enabled devices and can dynamically change the priority of the devices, including
changing devices from master to backup, and from backup to master, even if the device has not
failed. For example, if a host becomes unreachable on the far end of a network link, then the physical
default gateway can be changed by adjusting the VRRP priority of the EX50 device connected to the
failing link. This provides failover capabilities based on the status of connections behind the router, in
addition to the basic VRRP device failover. For EX50 devices, SureLink is used to probe network
connections.
VRRP+ can be configured to probe a specified IP address by either sending an ICMP echo request
(ping) or attempting to open a TCP socket to the IP address.
Configure VRRP
This section describes how to configure VRRP on a EX50 device.
n Enable VRRP.
n The interface used by VRRP.
n The Router ID that identifies the virtual router instance. The Router ID must be the same on all
VRRP devices that participate in the same VRRP device pool.
n The VRRP priority of this device.
n The shared virtual IP address for the VRRP virtual router. Devices connected to the LAN will use
this virtual IP address as their default gateway.
See Configure VRRP+ for information about configuring VRRP+, an extension to VRRP that uses
network probing to monitor connections through VRRP-enabled devices and dynamically change the
VRRP priorty of devices based on the status of their network connectivity.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
4. For Add VRRP instance, type a name for the VRRP instance and click .
5. Click Enable.
6. For Interface, select the interface on which this VRRP instance should run.
7. For Router ID field, type the ID of the virtual router instance. The Router ID must be the same
on all VRRP devices that participate in the same VRRP device pool. Allowed values are from 1
and 255, and it is configured to 50 by default.
8. For Priority, type the priority for this router in the group. The router with the highest priority
will be used as the master router. If the master router fails, then the IP address of the virtual
router is mapped to the backup device with the next highest priority. If this device's actual IP
address is being used as the virtual IP address of the VRRP pool, then the priority of this device
should be set to 255 . Allowed values are from 1 and 255, and it is configured to 100 by
default.
9. (Optional) For Password, type a password that will be used to authenticate this VRRP router
with VRRP peers. If the password length exceeds 8 characters, it will be truncated to 8
characters.
10. Configure the virtual IP addresses associated with this VRRP instance:
a. Click to expand Virtual IP addresses.
b. Click to add a virtual IP address.
c. For Virtual IP, type the IPv4 or IPv6 address for a virtual IP of this VRRP instance.
d. (Optional) Repeat to add additional virtual IPs.
11. See Configure VRRP+ for information about configuring VRRP+.
12. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
default.
7. Set the priority for this router in the group. The router with the highest priority will be used as
the master router. If the master router fails, then the IP address of the virtual router is mapped
to the backup device with the next highest priority. If this device's actual IP address is being
used as the virtual IP address of the VRRP pool, then the priority of this device should be set to
255 . Allowed values are from 1 and 255, and it is configured to 100 by default.
8. (Optional) Set a password that will be used to authenticate this VRRP router with VRRP peers.
If the password length exceeds 8 characters, it will be truncated to 8 characters.
9. Add a virtual IP address associated with this VRRP instance. This can be an IPv4 or IPv6
address.
Additional virtual IP addresses can be added by repeating this step with different values for ip_
address.
10. Save the configuration and apply the change:
Configure VRRP+
VRRP+ is an extension to the VRRP standard that uses SureLink network probing to monitor
connections through VRRP-enabled devices and adjust devices' VRRP priority based on the status of
the SureLink tests.
This section describes how to configure VRRP+ on a EX50 device.
Note SureLink is enabled by default on all WAN interfaces, and should not be disabled on
the WAN interfaces that are being monitored by VRRP+.
If multiple WAN interfaces are being monitored on the same device, the VRRP priority will
be adjusted only if all WAN interfaces fail SureLink tests.
l The amount that the VRRP priority will be modified when SureLink determines that the
VRRP interface is not functioning correctly.
l Configure the VRRP interface's DHCP server to use a custom gateway that corresponds to
one of the VRRP virtual IP addresses.
n Backup devices only:
l Enable and configure SureLink on the VRRP interface.
l Set the IP gateway to the IP address of the VRRP interface on the master device.
n For backup VRRP devices, enable the ability to monitor the VRRP master, so that a backup
device can increase its priority when the master device fails SureLink tests.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
6. Click Enable.
7. Add interfaces to monitor:
a. Click to expand Monitor interfaces.
b. Click to add an interface for monitoring.
c. For Interface, select the local interface to monitor. Generally, this will be a cellular or WAN
interface.
d. (Optional) Click again to add additional interfaces.
8. (Optional) For backup devices, click to enable Monitor VRRP+ master.
This parameter allows a backup VRRP device to monitor the master device, and increase its
priority when the master device is failing SureLink tests. This can allow a device functioning as
a backup device to promote itself to master.
9. For Priority modifier, type or select the amount that the device's priority should be decreased
due to SureLink connectivity failure, and increased when SureLink succeeds again.
Along with the priority settings for devices in this VRRP pool, the amount entered here should
be large enough to automatically demote a master device when SureLink connectivity fails. For
example, if the VRRP master device has a priority of 100 and the backup device has a priority
of 80, then the Priority modifier should be set to an amount greater than 20 so that if
SureLink fails on the master, it will lower its priority to below 80, and the backup device will
assume the master role.
10. Configure the VRRP interface. The VRRP interface is defined in the Interface parameter of the
VRRP configuration, and generally should be a LAN interface:
d. Configure the VRRP interface's DHCP server to use a custom gateway that corresponds to
one of the VRRP virtual IP addresses:
i. Click to expand DHCP Server > Advanced settings.
ii. For Gateway, select Custom.
iii. For Custom gateway, enter the IP address of one of the virtual IPs used by this VRRP
instance.
e. For backup devices, enable and configure SureLink on the VRRP interface. Generally, this
should be a LAN interface; VRRP+ will then monitor the LAN using SureLink to determine if
the interface has network connectivity and promote a backup to master if SureLink fails.
i. Click to expand IPv4 > SureLink.
ii. Click Enable.
iii. For Interval, type a the amount of time to wait between connectivity tests. To
guarantee seamless internet access for VRRP+ purposes, SureLink tests should occur
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Create a new VRRP instance, or edit an existing one. See Configure VRRP for information about
creating a new VRRP instance.
4. Enable VRRP+:
Format:
/network/interface/defaultip
/network/interface/defaultlinklocal
/network/interface/lan
/network/interface/loopback
/network/interface/modem
/network/interface/wan
Current value:
(config)>
iii. Set the custom gateway to one of the VRRP virtual IP addresses. For example:
b. For backup devices, set the default gateway to the IP address of the VRRP interface on the
master device. For example:
c. For backup devices, enable and configure SureLink on the VRRP interface.
i. Determine the VRRP interface. Generally, this should be a LAN interface; VRRP+ will
then monitor the LAN using SureLink to determine if the interface has network
connectivity and promote a backup to master if SureLink fails.
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set interval to ten minutes, enter 5s:
(config network interface lan ipv4 surelink target 0)> test value
(config network interface lan ipv4 surelink target 0)>
n dns: Tests connectivity by sending a DNS query to the specified DNS server.
l Specify the DNS server. Allowed value is the IP address of the DNS server.
where value is any number of weeks, days, hours, minutes, or seconds, and
takes the format number{w|d|h|m|s}.
where value is any number of weeks, days, hours, minutes, or seconds, and
takes the format number{w|d|h|m|s}.
For example, to set interface_timeout to ten minutes, enter either 10m or
600s:
(config)> save
Configuration saved.
>
4. For Add VRRP instance, type a name for the VRRP instance and click .
5. Click Enable.
6. For Interface, select Interface: LAN.
7. For Router ID, leave at the default setting of 50.
8. For Priority, leave at the default setting of 100.
9. Click to expand Virtual IP addresses.
10. Click to add a virtual IP address.
Task 3: Configure the IP address for the VRRP interface, LAN, on device one
1. Click Network > Interfaces > LAN > IPv4
2. For Address, type 192.168.3.1/24.
Command line
> config
(config)>
3. Set the amount that the device's priority should be decreased or increased due to SureLink
connectivity failure or success to 30:
(config network vrrp VRRP_test )> network vrrp VRRP_test vrrp_plus weight
30
(config network vrrp VRRP_test )>
Task 3: Configure the IP address for the VRRP interface, LAN, on device one
1. Type ... to return to the root of the config prompt:
(config)> save
Configuration saved.
>
5. Click Enable.
6. For Interface, select Interface: LAN.
7. For Router ID, leave at the default setting of 50.
8. For Priority, type 80.
9. Click to expand Virtual IP addresses.
10. Click to add a virtual IP address.
Task 3: Configure the IP address for the VRRP interface, LAN, on device two
1. Click Network > Interfaces > LAN > IPv4
2. For Address, type 192.168.3.2/24.
3. For Default gateway, type the IP address of the VRRP interface on the master device,
configured above in Task 3, step 2 (192.168.3.1).
Command line
> config
(config)>
4. Set the amount that the device's priority should be decreased or increased due to SureLink
connectivity failure or success to 30:
(config network vrrp VRRP_test )> network vrrp VRRP_test vrrp_plus weight
30
(config network vrrp VRRP_test )>
Task 3: Configure the IP address for the VRRP interface, LAN, on device two
1. Type ... to return to the root of the config prompt:
3. Set the default gateway to the IP address of the VRRP interface on the master device,
configured above in Task 3, step 2 (192.168.3.1).
(config network interface lan ipv4 surelink target 0)> test ping
(config network interface lan ipv4 surelink target 0)>
2. Set the start and end addresses of the DHCP pool to use to assign DHCP addresses to clients:
a. Set the start address to 200:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type show vrrp:
3. To display additional information about a specific VRRP instance, at the Admin CLI prompt,
type show vrrp name name:
IPv4
----
Virtual IP address(es) : 10.10.10.1, 100.100.100.1
Current State : Master
Current Priority : 100
Last Transition : Tue Jan 1 00:00:39 2019
Became Master : 1
Released Master : 0
Adverts Sent : 71
Adverts Received : 4
Priority Zero Sent : 0
Priority zero Received : 0
>
IPsec 296
OpenVPN 345
Generic Routing Encapsulation (GRE) 377
NEMO 398
L2TPv3 406
IPsec
IPsec is a suite of protocols for creating a secure communication link—an IPsec tunnel—between a
host and a remote IP network or between two IP networks across a public network such as the
Internet.
IPsec modes
IPsec can run in two different modes: Tunnel and Transport.
Tunnel
The entire IP packet is encrypted and/or authenticated and then encapsulated as the payload in a
new IP packet.
Transport
Only the payload of the IP packet is encrypted and/or authenticated. The IP header is left
untouched. This mode has limitations when using an authentication header, because the IP
addresses in the IP header cannot be translated (for example, with Network Address Translation
(NAT), as it would invalidate the authentication hash value.
Phase 1
In phase 1, IKE creates a secure authenticated communication channel between the device and the
peer (the remote device which is at the other end of the IPsec tunnel) using the configured pre-shared
key and the Diffie-Hellman key exchange. This creates the IKE SAs that are used to encrypt further IKE
communications.
For IKEv1, there are two modes for the phase 1 negotiation: Main mode and Aggressive mode. IKEv2
does not use these modes.
Main mode
Main mode is the default mode. It is slower than aggressive mode, but more secure, in that all
sensitive information sent between the device and its peer is encrypted.
Aggressive mode
Aggressive mode is faster than main mode, but is not as secure as main mode, because the device
and its peer exchange their IDs and hash information in clear text instead of being encrypted.
Aggressive mode is usually used when one or both of the devices have a dynamic external IP
address.
Phase 2
In phase 2, IKE negotiates the SAs for IPsec. This creates two unidirectional SAs, one for each
direction. Once the phase 2 negotiation is complete, the IPsec tunnel should be fully functional.
Authentication
Client authenticaton
XAUTH (extended authentication) pre-shared key authentication mode provides additional security by
using client authentication credentials in addition to the standard pre-shared key. The EX50 device
can be configured to authenticate with the remote peer as an XAUTH client.
RSA Signatures
With RSA signatures authentication, the EX50 device uses a private RSA key to authenticate with a
remote peer that is using a corresponding public key.
Certificate-based Authentication
X.509 certificate-based authentication makes use of private keys on both the server and client which
are secured and never shared. Both the server and client have a certificate which is generated with
their respective private key and signed by a Certificate Authority (CA).
The EX50 implementation of IPsec can be configured to use X.509 certificate-based authentication
using the private keys and certificates, along with a root CA certificate from the signing authority and,
if available, a Certificate Revocation List (CRL).
If SCEP certificates will be selected as the Authentication type, create the SCEP client prior
to configuring the IPsec tunnel. See Configure a Simple Certificate Enrollment Protocol
client for instructions.
l The local endpoint type and ID values, and the remote endpoint host and ID values.
n IKE configuration items
l The IKE version, either IKEv1 or IKEv2.
l Whether to initiate a key exchange or wait for an incoming request.
l The IKE mode, either main aggressive.
l The IKE authentication protocol to use for the IPsec tunnel negotiation during phase 1 and
phase 2.
l The IKE encryption protocol to use for the IPsec tunnel negotiation during phase 1 and
phase 2.
l The IKE Diffie-Hellman group to use for the IPsec tunnel negotiation during phase 1 and
phase 2.
n Enable dead peer detection and configure the delay and timeout.
n Destination networks that require source NAT.
n Active recovery configuration. See Configure SureLink active recovery for IPsec for information
about IPsec active recovery.
n Determine whether the device should use UDP encapsulation even when it does not detect
that NAT is being used.
n If using IPsec failover, identify the primary tunnel during configuration of the backup tunnel.
n The Network Address Translation (NAT) keep alive time.
n The protocol, either Encapsulating Security Payload (ESP) or Authentication Header (AH).
n The management priority for the IPsec tunnel interface. The active interface with the highest
management priority will have its address reported as the preferred contact address for
central management and direct device access.
n Enable XAUTH client authentication, and the username and password to be used to
authenticate with the remote peer.
n Enable Mode-configuration (MODECFG) to receive configuration information, such as the
private IP address, from the remote peer.
n Disable the padding of IKE packets. This should normally not be done except for compatibility
purposes.
n Destination networks that require source NAT.
n Depending on your network and firewall configuration, you may need to add a packet filtering
rule to allow incoming IPsec traffic.
n Tunnel and key renegotiating
l The lifetime of the IPsec tunnel before it is renegotiated.
l The amount of time before the IKE phase 1 lifetime expires.
Note if the remote networks for an IPsec tunnel overlap with the networks for a WAN internet
connection (wired, cellular, or otherwise), you must configure a static route to direct the traffic either
through the IPsec tunnel, or through the WAN (outside of the IPsec tunnel). See Configure a static
route for information about configuring a static route.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note Depending on your network configuration, you may need to add a packet filtering rule to
allow incoming traffic. For example, for the IPsec zone:
a. Click to expand Firewall > Packet filtering.
b. For Add packet filter, click .
c. For Label, type Allow incoming IPsec traffic.
d. For Source zone, select IPsec.
Leave all other fields at their default settings.
10. For Metric, enter or select the priority of routes associated with this IPsec tunnel. When more
than one active route matches a destination, the route with the lowest metric is used.
The metric can also be used in tandem with SureLink to configure IPsec failover behavior. See
Configure IPsec failover for more information.
b. Click Enable.
c. Type the Username and Password that the device will use to authenticate as an
XAUTH client with the peer.
16. (Optional) Click Enable MODECFG client to receive configuration information, such as the
private IP address, from the remote peer.
17. Click to expand Local endpoint.
a. For Type, select either:
n Default route: Uses the same network interface as the default route.
n Interface: Select the Interface to be used as the local endpoint.
b. Click to expand ID.
i. Select the ID type:
n Auto: The ID will be automatically determined from the value of the tunnels
endpoints.
n Raw: Enter an ID and have it passed unmodified to the underlying IPsec stack.
For Raw ID value, type the ID that will be passed.
n Any: Any ID will be accepted.
n IPv4: The ID will be interpreted as an IP address and sent as an ID_IPV4_ADDR
IKE identity.
For IPv4 ID value, type an IPv4 formatted ID. This can be a fully-qualified
domain name or an IPv4 address.
n IPv6: The ID will be interpreted as an IP address and sent as an ID_IPV6_ADDR
IKE identity.
For IPv6 ID value, type an IPv6 formatted ID. This can be a fully-qualified
domain name or an IPv6 address.
n RFC822/Email: The ID will be interpreted as an RFC822 (email address).
For RFC822 ID value, type the ID in internet email address format.
n FQDN: The ID will be interpreted as FQDN (Fully Qualified Domain Name) and
sent as an ID_FQDN IKE identity.
For FQDN ID value, type the ID as an FQDN.
n KeyID: The ID will be interpreted as a Key ID and sent as an ID_KEY_ID IKE
identity.
For KEYID ID value, type the key ID.
n MAC address: The device's primary MAC address will be used as the ID and
sent as a ID_KEY_ID IKE identity.
n Serial number: The device's serial number will be used as the ID and sent as a
ID_KEY_ID IKE identity.
18. Click to expand Remote endpoint.
a. For IP version, select either IPv4 or IPv6.
b. For Hostname list selection, select one of the following:
n Round robin: Attempts to connect to hostnames sequentially based on the list
order.
n Random: Randomly selects an IPsec peer to connect to from the hostname list.
n Priority ordered: Selects the first hostname in the list that is resolvable.
c. Click to expand Hostname.
i. Click next to Add Hostname.
ii. For Hostname, type a hostname or IPv4 address. If your device is not configured to
initiate the IPsec connection (see IKE > Initiate connection), you can also use the
keyword any, which means that the hostname is dynamic or unknown.
iii. Click again to add additional hostnames.
d. Click to expand ID.
i. Select the ID type:
n Auto: The ID will be automatically determined from the value of the tunnels
endpoints.
n Raw: Enter an ID and have it passed unmodified to the underlying IPsec stack.
For Raw ID value, type the ID that will be passed.
n Any: Any ID will be accepted.
n IPv4: The ID will be interpreted as an IPv4 address and sent as an ID_IPV4_
ADDR IKE identity.
For IPv4 ID value, type an IPv4 formatted ID. This can be a fully-qualified
domain name or an IPv4 address.
n IPv6: The ID will be interpreted as an IPv6 address and sent as an ID_IPV6_
ADDR IKE identity.
For IPv6 ID value, type an IPv6 formatted ID. This can be a fully-qualified
domain name or an IPv6 address.
n RFC822/Email: The ID will be interpreted as an RFC822 (email address).
For RFC822 ID value, type the ID in internet email address format.
n FQDN: The ID will be interpreted as FQDN (Fully Qualified Domain Name) and
sent as an ID_FQDN IKE identity.
a. For IKE version, select either IKEv1 or IKEv2. This setting must match the peer's IKE
version.
b. Initiate connection instructs the device to initiate the key exchange, rather than waiting
for an incoming request. This must be disabled if Remote endpoint > Hostname is set to
any.
c. For Mode, select either Main mode or Aggressive mode.
d. For IKE fragmentation, select one of the following:
n If supported by the peer: Send oversized IKE messages in fragments, if the peer
supports receiving them.
n Always: Always send IKEv1 messages in fragments. For IKEv2, this option is
equivalent to If supported by the peer.
n Never: Do not send oversized IKE messages in fragments.
n Accept: Do not send oversized IKE messages in fragments, but announce support
for fragmentation to the peer.
The default is Always.
e. For Enable padding, click to disable the padding of IKE packets. This should normally not
be disabled except for compatibility purposes.
f. For Phase 1 lifetime, enter the amount of time that the IKE security association expires
after a successful negotiation and must be re-authenticated.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Phase 1 lifetime to ten minutes, enter 10m or 600s.
g. For Phase 2 lifetime, enter the amount of time that the IKE security association expires
after a successful negotiation and must be rekeyed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Phase 2 lifetime to ten minutes, enter 10m or 600s.
h. For Lifetime margin, enter a randomizing amount of time before the IPsec tunnel is
renegotiated.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Lifetime margin to ten minutes, enter 10m or 600s.
i. Click to expand Phase 1 Proposals.
i. Click to create a new phase 1 proposal.
ii. For Cipher, select the type of encryption.
iii. For Hash, select the type of hash to use to verify communication integrity.
iv. For Diffie-Hellman group, select the type of Diffie-Hellman group to use for key
exchange.
v. You can add additional Phase 1 proposals by clicking next to Add Phase 1
Proposal.
j. Click to expand Phase 2 Proposals.
i. Click to create a new phase 2 proposal.
ii. For Cipher, select the type of encryption.
iii. For Hash, select the type of hash to use to verify communication integrity.
iv. For Diffie-Hellman group, select the type of Diffie-Hellman group to use for key
exchange.
v. You can add additional Phase 2 proposals by clicking next to Add Phase 2
Proposal.
21. (Optional) Click to expand Dead peer detection. Dead peer detection is enabled by default.
Dead peer detection uses periodic IKE transmissions to the remote endpoint to detect whether
tunnel communications have failed, allowing the tunnel to be automatically restarted when
failure occurs.
a. To enable or disable dead peer detection, click Enable.
b. For Delay, type the number of seconds between transmissions of dead peer packets. Dead
peer packets are only sent when the tunnel is idle.
c. For Timeout, type the number of seconds to wait for a response from a dead peer packet
before assuming the tunnel has failed.
22. (Optional) Click to expand NAT to create a list of destination networks that require source NAT.
a. Click next to Add NAT destination.
b. For Destination network, type the IPv4 address and optional netmask of a destination
network that requires source NAT. You can also use any, meaning that any destination
network connected to the tunnel will use source NAT.
23. See Configure SureLink active recovery for IPsec for information about IPsec Active recovery.
24. (Optional) Click Advanced to set various IPsec-related time out, keep alive, and related values.
25. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add an IPsec tunnel. For example, to add an IPsec tunnel named ipsec_example:
4. (Optional) Set the tunnel to use UDP encapsulation even when it does not detect that NAT is
being used:
5. Set the firewall zone for the IPsec tunnel. Generally this should be left at the default of ipsec.
Zone: The firewall zone assigned to this IPsec tunnel. This can be used
by packet filtering rules
and access control lists to restrict network traffic on this tunnel.
Format:
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
Default value: ipsec
Current value: ipsec
Note Depending on your network configuration, you may need to add a packet filtering rule to
allow incoming traffic. For example, for the IPsec zone:
a. Type ... to move to the root of the configuration:
6. Set the metric for the IPsec tunnel. When more than one active route matches a destination,
the route with the lowest metric is used. The metric can also be used in tandem with SureLink
to configure IPsec failover behavior. See Configure IPsec failover for more information.
b. Set the remote pre-shared key. This must be the same as the local key on the
remote host.:
n rsasig: Uses a private RSA key to authenticate with the remote peer.
a. For the private_key parameter, paste the device's private RSA key in PEM format:
b. Set the private key passphrase that is used to decrypt the private key. Leave blank
if the private key is not encrypted.
c. For the peer_public_key parameter, paste the peer's public RSA key in PEM
format:
n x509: Uses private key and X.509 certificates to authenticate with the remote peer.
a. For the private_key parameter, paste the device's private RSA key in PEM format:
b. Set the private key passphrase that is used to decrypt the private key. Leave blank
if the private key is not encrypted.
c. For the cert parameter, paste the local X.509 certificate in PEM format:
11. (Optional) Configure the device to connect to its remote peer as an XAUTH client:
a. Enable XAUTH client functionality:
n fqdn: The ID will be interpreted as FQDN (Fully Qualified Domain Name) and sent as
an ID_FQDN IKE identity.
n keyid: The ID will be interpreted as a Key ID and sent as an ID_KEY_ID IKE identity.
Set the key ID:
n mac_address: The device's MAC address will be used for the Key ID and sent as an
ID_KEY_ID IKE identity.
n serial_number: The ID device's serial number will be used for the Key ID and sent
as an ID_KEY_ID IKE identity.
14. Configure the remote endpoint:
a. Add a remote hostname:
(config vpn ipsec tunnel ipsec_example)> add remote hostname end value
(config vpn ipsec tunnel ipsec_example)>
where value is the hostname or IPv4 address of the IPsec peer. If your device is not
configured to initiate the IPsec connection (see ike initiate), you can also use the keyword
any, which means that the hostname is dynamic or unknown.
Repeat for additional hostnames.
b. Set the hostname selection type:
n fqdn: The ID will be interpreted as FQDN (Fully Qualified Domain Name) and sent as
an ID_FQDN IKE identity.
n keyid: The ID will be interpreted as a Key ID and sent as an ID_KEY_ID IKE identity.
Set the key ID:
n mac_address: The device's MAC address will be used for the Key ID and sent as an
ID_KEY_ID IKE identity.
n serial_number: The ID device's serial number will be used for the Key ID and sent
as an ID_KEY_ID IKE identity.
15. Configure IKE settings:
a. Set the IKE version:
where value is either ikev1 or ikev2. This setting must match the peer's IKE version.
b. Determine whether the device should initiate the key exchange, rather than waiting for an
incoming request. By default, the device will initiate the key exchange. This must be
disabled if remote hostname is set to any. To disable:
f. Set the amount of time that the IKE security association expires after a successful
negotiation and must be re-authenticated:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set phase1_lifetime to ten minutes, enter either 10m or 600s:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set phase2_lifetime to ten minutes, enter either 10m or 600s:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set lifetime_margin to ten minutes, enter either 10m or 600s:
where value is one of 3des, aes128, aes192, aes256, or null. The default is 3des.
iii. Set the type of hash to use during phase 1 to verify communication integrity:
where value is one of md5, sha1, sha256, sha384, or sha512. The default is sha1.
iv. Set the type of Diffie-Hellman group to use for key exchange during phase 1:
Repeat the above steps to set the type of encryption, hash, and Diffie-Hellman
group for the additional proposal.
iii. Repeat to add more phase 1 proposals.
j. Configure the types of encryption, hash, and Diffie-Hellman group to use during phase 2:
i. Move back two levels in the schema:
where value is one of 3des, aes128, aes192, aes256, or null. The default is 3des.
iv. Set the type of hash to use during phase 2 to verify communication integrity:
where value is one of md5, sha1, sha256, sha384, or sha512. The default is sha1.
v. Set the type of Diffie-Hellman group to use for key exchange during phase 2:
Repeat the above steps to set the type of encryption, hash, and Diffie-Hellman
group for the additional proposal.
iii. Repeat to add more phase 2 proposals.
16. (Optional) Configure dead peer detection:
Dead peer detection is enabled by default. Dead peer detection uses periodic IKE
transmissions to the remote endpoint to detect whether tunnel communications have failed,
allowing the tunnel to be automatically restarted when failure occurs.
a. Change to the root of the configuration schema:
c. Set the number of seconds between transmissions of dead peer packets. Dead peer
packets are only sent when the tunnel is idle. The default is 60.
d. Set the number of seconds to wait for a response from a dead peer packet before
assuming the tunnel has failed. The default is 90.
17. (Optional) Create a list of destination networks that require source NAT:
a. Add a destination network:
b. Set the IPv4 address and optional netmask of a destination network that requires source
NAT. You can also use any, meaning that any destination network connected to the tunnel
will use source NAT.
18. Configure policies that define the network traffic that will be encapsulated by this tunnel:
a. Change to the root of the configuration schema:
b. Add a policy:
(config vpn ipsec tunnel ipsec_example policy 0)> local type value
(config vpn ipsec tunnel ipsec_example policy 0)>
where value is the IPv4 address and optional netmask. The keyword any can also
be used.
n request: Requests a network from the remote peer.
d. Set the IP address and optional netmask of the remote network. The keyword any can also
be used.
(config vpn ipsec tunnel ipsec_example policy 0)> remote network value
(config vpn ipsec tunnel ipsec_example policy 0)>
19. (Optional) You can also configure various IPsec related time out, keep alive, and related values:
a. Change to the root of the configuration schema:
b.
(config)> vpn ipsec advanced ?
Additional Configuration
---------------------------------------------------------------------
----------
connection_retry_timeout Connection retry timeout
connection_try_interval Connection try interval
ike_timeout IKE timeout
(config)>
(config)> save
Configuration saved.
>
n SureLink active recovery—You can use SureLink along with the IPsec tunnel's metric to
configure two or more tunnels so that when the primary tunnel is determined to be inactive by
SureLink, a secondary tunnel can begin serving traffic that the primary tunnel was serving.
n Preferred tunnel—When multiple IPsec tunnels are configured, one tunnel can be configured
as a backup to another tunnel by defining a preferred tunnel for the backup device.
n Two or more configured IPsec tunnels: The primary tunnel, and one or more backup tunnels.
n Either:
l SureLink configured on the primary tunnel with Restart Interface enabled, and the metric
for all tunnels set appropriately to determine which IPsec tunnel has priority. With this
failover configuration, both tunnels are active simultaneously, and there is minimal
downtime due to failover.
l Identify the preferred tunnel during configuration of the backup tunnel. In this scenario,
the backup tunnel is not active until the preferred tunnel fails.
1. SureLink will shut down the tunnel and renegotiate its IPsec connection.
2. While the tunnel with the lower metric is down, traffic addressed to the remote endpoint will
be routed through the tunnel with the higher metric.
For example:
n Tunnel_1:
l Metric: 10
l Local endpoint > Interface: LAN
l Remote endpoint > Hostname: 192.168.10.1
l SureLink configuration:
o Restart Interface enabled
o Test target:
o Test type: Ping test
o Ping host: 192.168.10.2
n Tunnel_2:
l Metric: 20
l Local endpoint > Interface: LAN
l Remote endpoint > Hostname: 192.168.10.1
In this configuration:
1. Tunnel_1 will normally be used for traffic destined for the 192.168.10.1 endpoint.
2. If pings to 192.168.10.2 fail, SureLink will shut down the tunnel and renegotiate its IPsec
connection.
3. While Tunnel_1 is down, Tunnel_2 will be used for traffic destined for the 192.168.10.1
endpoint.
WebUI
1. Configure the primary IPsec tunnel. See Configure an IPsec tunnel for instructions.
n During configuration of the IPsec tunnel, set the metric to a low value (for example, 10).
n Configure SureLink for the primary IPsec tunnel and enable Restart interface. See
Configure SureLink active recovery for IPsec for instructions.
2. Create a backup IPsec tunnel. Configure this tunnel to use the same local and remote
endpoints as the primary tunnel. See Configure an IPsec tunnel for instructions.
n During configuration of the IPsec tunnel, set the metric to a value that is higher than the
metric of the primary tunnel (for example, 20).
Command line
1. Configure the primary IPsec tunnel. See Configure an IPsec tunnel for instructions.
n During configuration of the IPsec tunnel, set the metric to a low value (for example, 10):
n Configure SureLink for the primary IPsec tunnel and enable Restart interface. See
Configure SureLink active recovery for IPsec for instructions.
2. Create a backup IPsec tunnel. Configure this tunnel to use the same local and remote
endpoints as the primary tunnel. See Configure an IPsec tunnel for instructions.
n During configuration of the IPsec tunnel, set the metric to a value that is higher than the
metric of the primary tunnel (for example, 20):
WebUI
1. Configure the primary IPsec tunnel. See Configure an IPsec tunnel for instructions.
2. Create a backup IPsec tunnel. See Configure an IPsec tunnel for instructions.
3. During configuration of the backup IPsec tunnel, identify the primary IPsec tunnel in the
Preferred tunnel parameter:
Command line
1. Configure the primary IPsec tunnel. See Configure an IPsec tunnel for instructions.
2. Create a backup IPsec tunnel. See Configure an IPsec tunnel for instructions.
3. During configuration of the backup IPsec tunnel, identify the primary IPsec tunnel:
a. Use the ? to view a list of available tunnels:
Preferred tunnel: This tunnel will not start until the preferred
tunnel has failed. It will continue
to operate until the preferred tunnel returns to full operation
status.
Format:
primary_ipsec_tunnel
backup_ipsec_tunnel
Optional: yes
Current value:
n A valid IPsec configuration. See Configure an IPsec tunnel for configuration instructions.
n Enable IPsec active recovery.
n The behavior of the EX50 device upon IPsec failure: either
l Restart the IPsec interface
l Reboot the device.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
7. For Restart interface, enable to configure the device to restart the interface when its
connection is considered to have failed. This is useful for interfaces that may regain
connectivity after restarting, such as a cellular modem.
8. For Reboot device, enable to instruct the device to reboot when the WAN connection is
considered to have failed.
9. Change the Interval between connectivity tests.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Interval to ten minutes, enter 10m or 600s.
The default is 15 minutes.
10. For Success condition, determine whether the interface should fail over based on the failure
of one of the test targets, or all of the test targets.
11. For Attempts, type the number of probe attempts before the WAN is considered to have failed.
12. For Response timeout, type the amount of time that the device should wait for a response to
a probe attempt before considering it to have failed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Response timeout to ten minutes, enter 10m or 600s.
The default is 15 seconds.
13. Add a test target:
a. Click to expand Test targets.
n HTTP test HTTP test (IPv6): Tests connectivity by sending an HTTP or HTTPS GET
request to the URL specified in Web servers. The URL should take the format of
http[s]://hostname/[path].
n Test DNS servers configured for this interface or Test DNS servers configured
for this interface (IPv6): Tests connectivity by sending a DNS query to the DNS
servers configured for this interface.
n Test the interface status or Test the interface status IPv6: The interface is
considered to be down based on:
l Down time: The amount of time that the interface can be down before this test
is considered to have failed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and
take the format number{w|d|h|m|s}.
For example, to set Down time to ten minutes, enter 10m or 600s.
The default is 60 seconds.
l Initial connection time: The amount of time to wait for an initial connection to
the interface before this test is considered to have failed.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and
take the format number{w|d|h|m|s}.
For example, to set Initial connection time to ten minutes, enter 10m or 600s.
The default is 60 seconds.
14. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. To configure the device to restart the interface when its connection is considered to have
failed:
This is useful for interfaces that may regain connectivity after restarting, such as a cellular
modem.
6. To configure the device to reboot when the interface is considered to have failed:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set interval to ten minutes, enter either 10m or 600s:
The default is 3.
10. Set the amount of time that the device should wait for a response to a probe attempt before
considering it to have failed:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set timeout to ten minutes, enter either 10m or 600s:
l (Optional) Set the size, in bytes, of the ping packet by using ping_size or ping_
size6:
n dns (IPv4) or dns6 (IPv6): Tests connectivity by sending a DNS query to the
specified DNS server.
l Specify the DNS server. Allowed value is the IP address of the DNS server.
n http (IPv4) or http6 (IPv6): Tests connectivity by sending an HTTP or HTTPS GET
request to the specified URL.
l Specify the url. Allowed value uses the format http[s]://hostname/[path].
where value is any number of weeks, days, hours, minutes, or seconds, and
takes the format number{w|d|h|m|s}.
For example, to set interface_down_time to ten minutes, enter either 10m or
600s:
where value is any number of weeks, days, hours, minutes, or seconds, and
takes the format number{w|d|h|m|s}.
For example, to set interface_timeout to ten minutes, enter either 10m or
600s:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, select Status > IPsec.
The IPsec page appears.
3. To view configuration details about an IPsec tunnel, click the (configuration) icon in the
upper right of the tunnel's status pane.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. To display details about all configured IPsec tunnels, type the following at the prompt:
>
Tunnel : ipsec1
Enable : true
Status : pending
Hostname : 192.168.2.1
Zone : ipsec
Mode : tunnel
Type : esp
>
n From the Admin CLI—Sets the debug level to 1 (basic debugging information only).
n From the interactive shell—Allows for more detailed debug information.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
n -1 — (Default) No debug information is written. This is the equivalent of turning off debug
messages for IPsec.
n 0 — Basic auditing logs, (for example, SA up/SA down).
n 1 — Generic control flow with errors. Select this for basic debugging information.
n 2 — More detailed debugging control flow.
n 3 — Includes RAW data dumps in hexadecimal format.
n 4 — Also includes sensitive material in dumps (for example, encryption keys).
To access the shell menu option, you must have shell access enabled. See Authentication groups for
information about configuring authentication groups that include shell access.
Command line
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, execute the following command:
Required configuration
n Enable the SCEP client.
n The fully-qualified domain name of the SCEP server to be used for certificate requests.
n The challenge password provided by the SCEP server that the SCEP client will use when
making SCEP requests.
Additional configuration
n The number of days that the certificate enrollment can be renewed, prior to the request
expiring.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
6. For Renewable Time, type the number of days that the certificate enrollment can be renewed,
prior to the request expiring. This value is configured on the SCEP server, and is used by the
EX50 device to determine when to start attempting to auto-renew an existing certificate. The
default is 7.
7. (Optional) For CRL file name, type the filename of the Certificate Revocation List (CRL) from the
CA.
The CRL is stored on the EX50 device in the /etc/config/scep_client/client_name directory.
8. Click to expand SCEP server.
9. For FQDN, type the fully qualified domain name or IP address of the SCEP server.
10. For Password, type the challenge password as configured on the SCEP server.
11. Click to expand Distinguished Name.
12. Type the value for each appropriate Distinguished Name attribute.
13. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
5. Set the url parameter to the fully qualified domain name or IP address of the SCEP server:
8. Set the number of days that the certificate enrollment can be renewed, prior to the request
expiring. This value is configured on the SCEP server, and is used by the EX50 device to
determine when to start attempting to auto-renew an existing certificate. The default is 7.
9. (Optional) Set the filename of the Certificate Revocation List (CRL) from the CA.
The CRL is stored on the EX50 device in the /etc/config/scep_client/client_name directory.
Fortinet configuration
On the Fortinet server:
EX50 configuration
On the EX50 device:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
9. For FQDN, type the fully qualified domain name or IP address of the Fortinet server.
10. For Password, type the challenge password. This corresponds to the Default enrollment
password on the Fortinet server.
11. Click to expand Distinguished Name.
12. Type the value for each appropriate Distinguished Name attribute. The values entered here
must correspond to the DN attributes in the Enrollment Request on the Fortinet server.
13. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. Set the url parameter to the fully qualified domain name or IP address of the SCEP server:
6. Set the challenge password as configured on the SCEP server. This corresponds to the Default
enrollment password on the Fortinet server.
7. Set Distinguished Name attributes. The values entered here must correspond to the DN
attributes in the Enrollment Request on the Fortinet server.
a. Set the Domain Component:
8. Set the number of days that the certificate enrollment can be renewed, prior to the request
expiring. This value must match the setting of the Allow renewal x days before the certified
is expired option on the Fortinet server.
9. (Optional) Set the filename of the Certificate Revocation List (CRL) from the CA.
The CRL is stored on the EX50 device in the /etc/config/scep_client/client_name directory.
OpenVPN
OpenVPN is an open-source Virtual Private Network (VPN) technology that creates secure point-to-
point or site-to-site connections in routed or bridged configurations. OpenVPN uses a custom security
protocol that is Secure Socket Layer (SSL) / Transport Layer Security (TLS) for key exchange. It uses
standard encryption and authentication algorithms for data privacy and authentication over TCP or
UDP.
The OpenVPN server can push the network configuration, such as the topology and IP routes, to
OpenVPN clients. This makes OpenVPN simpler to configure as it reduces the chances of a
configuration mismatch between the client and server. OpenVPN also supports cipher negotiation
between the client and server. This means you can configure the OpenVPN server and clients with a
range of different cipher options and the server will negotiate with the client on the cipher to use for
the connection.
For more information on OpenVPN, see www.openvpn.net.
OpenVPN modes:
There are two modes for running OpenVPN:
n OpenVPN managed—The EX50 device creates the interface and then uses its standard
configuration to set up the connection (for example, its standard DHCP server configuration).
n Device only—IP addressing is controlled by the system, not by OpenVPN.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
b. Paste the contents of the CA certificate (usually in a ca.crt file), the Public key (for
example, server.crt), the Private key (for example, server.key), and the Diffie Hellman
key (usually in dh2048.pem) into their respective fields. The contents will be hidden when
the configuration is saved.
10. (Optional) Click to expand Access control list to restrict access to the OpenVPN server:
n To limit access to specified IPv4 addresses and networks:
a. Click IPv4 Addresses.
b. For Add Address, click .
c. For Address, enter the IPv4 address or network that can access the device's
service-type. Allowed values are:
l A single IP address or host name.
l A network designation in CIDR notation, for example, 192.168.1.0/24.
l any: No limit to IPv4 addresses that can access the service-type.
d. Click again to list additional IP addresses or networks.
n To limit access to specified IPv6 addresses and networks:
a. Click IPv6 Addresses.
b. For Add Address, click .
c. For Address, enter the IPv6 address or network that can access the device's
service-type. Allowed values are:
l A single IP address or host name.
l A network designation in CIDR notation, for example, 2001:db8::/48.
l any: No limit to IPv6 addresses that can access the service-type.
d. Click again to list additional IP addresses or networks.
n To limit access to hosts connected through a specified interface on the EX50 device:
a. Click Interfaces.
b. For Add Interface, click .
c. For Interface, select the appropriate interface from the dropdown.
d. Click again to allow access through additional interfaces.
n To limit access based on firewall zones:
a. Click Zones.
b. For Add Zone, click .
c. For Zone, select the appropriate firewall zone from the dropdown.
See Firewall configuration for information about firewall zones.
d. Click again to allow access through additional firewall zones.
11. (Optional) Click to expand Advanced Options to manually set additional OpenVPN
parameters.
a. Click Enable to enable the use of additional OpenVPN parameters.
b. Click Override if the additional OpenVPN parameters should override default options.
c. For OpenVPN parameters, type the additional OpenVPN parameters.
12. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
b. Set the firewall zone for the OpenVPN server. For TUN device types, this should be set to
internal to treat clients as LAN devices.
Zone: The zone for the local TUN interface. To treat clients as LAN
devices this would usually be
set to internal.
Format:
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
Current value:
c. (Optional) Set the route metric for the OpenVPN server. If multiple active routes match a
destination, the route with the lowest metric will be used.
where value is a number between 1 and 255. The number entered here will represent
the first client IP address. For example, if address is set to 192.168.1.1/24 and
server_first_ip is set to 80, the first client IP address will be 192.168.1.80.
The default is from 80.
ii. Set the last address in the range limit:
where value is a number between 1 and 255. The number entered here will represent
the last client IP address. For example, if address is set to 192.168.1.1/24 and
server_last_ip is set to 99, the last client IP address will be 192.168.1.80.
The default is from 80.
6. (Optional) Set the port that the OpenVPN server will use:
iii. Paste the contents of the public key (for example, server.crt) into the value of the
server_cert parameter:
iv. Paste the contents of the private key (for example, server.key) into the value of the
server_key parameter:
v. Paste the contents of the Diffie Hellman key (usually in dh2048.pem) into the value of
the diffie parameter:
8. (Optional) Set the access control list to restrict access to the OpenVPN server:
n To limit access to specified IPv4 addresses and networks:
(config vpn openvpn server name)> add acl address end value
(config vpn openvpn server name)>
(config vpn openvpn server name)> add acl address6 end value
(config vpn openvpn server name)>
(config vpn openvpn server name)> add acl interface end value
(config vpn openvpn server name)>
(config vpn openvpn server name)> add acl zone end value
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
b. Configure whether the additional OpenVPN parameters should override default options:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
c. Click OpenVPN access to enable OpenVPN access rights for users of this group.
d. Click to expand the OpenVPN node.
e. Click to add a tunnel.
f. For Tunnel, select an OpenVPN tunnel to which users of this group will have access.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Use the add auth group command to add a new authentication. For example, to add a group
named OpenVPN_Group:
5. Add an OpenVPN tunnel to which users of this group will have access:
a. Determine available tunnels:
Additional Configuration
---------------------------------------------------------------------
----------
OpenVPN_server1 OpenVPN server
b. Add a tunnel:
(config auth group OpenVPN_Group)> add auth group test acl openvpn
tunnels end /vpn/openvpn/server/OpenVPN_server1
(config auth group OpenVPN_Group)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. (Optional) Set the route metric for the OpenVPN server. If multiple active routes match a
destination, the route with the lowest metric will be used.
7. Paste the content of the client.ovpn file into the value of the config_file parameter:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
8. For Zone, select the firewall zone for the OpenVPN client.
9. (Optional) Select the Metric for the OpenVPN client. If multiple active routes match a
destination, the route with the lowest metric will be used.
10. (Optional) For Username and Password, type the login credentials as configured on the
OpenVPN server.
11. For VPN server IP, type the IP address of the OpenVPN server.
12. (Optional) Set the VPN port used by the OpenVPN server. The default is 1194.
13. Paste the contents of the CA certificate (usually in a ca.crt file), the Public key (for example,
client.crt), and the Private key (for example, client.key) into their respective fields. The
contents will be hidden when the configuration is saved.
14. (Optional) Click to expand Advanced Options to manually set additional OpenVPN
parameters.
a. Click Enable to enable the use of additional OpenVPN parameters.
b. Click Override if the additional OpenVPN parameters should override default options.
c. For OpenVPN parameters, type the additional OpenVPN parameters. For example, to
override the configuration by using a configuration file, enter --config filename, for
example, --config /etc/config/openvpn_config.
15. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. The default behavior is to use an OVPN file for client configuration. To disable this behavior
and configure the client manually:
7. (Optional) Set the route metric for the OpenVPN server. If multiple active routes match a
destination, the route with the lowest metric will be used.
12. Paste the contents of the public key (for example, client.crt) into the value of the public_cert
parameter:
13. Paste the contents of the private key (for example, client.key) into the value of the private_key
parameter:
b. Configure whether the additional OpenVPN parameters should override default options:
(config)> save
Configuration saved.
>
n A valid OpenVPN client configuration. See Configure an OpenVPN client by using an .ovpn file
or Configure an OpenVPN client without using an .ovpn file for configuration instructions.
n Enable OpenVPN active recovery.
n The behavior of the EX50 device upon OpenVPN failure: either
l Restart the OpenVPN interface
l Reboot the device.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
14. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. To configure the device to restart the interface when its connection is considered to have
failed:
This is useful for interfaces that may regain connectivity after restarting, such as a cellular
modem.
6. To configure the device to reboot when the interface is considered to have failed:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set interval to ten minutes, enter either 10m or 600s:
The default is 3.
10. Set the amount of time that the device should wait for a response to a probe attempt before
considering it to have failed:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set timeout to ten minutes, enter either 10m or 600s:
l (Optional) Set the size, in bytes, of the ping packet by using ping_size or ping_
size6:
n dns (IPv4) or dns6 (IPv6): Tests connectivity by sending a DNS query to the
specified DNS server.
l Specify the DNS server. Allowed value is the IP address of the DNS server.
where value is any number of weeks, days, hours, minutes, or seconds, and
takes the format number{w|d|h|m|s}.
For example, to set interface_down_time to ten minutes, enter either 10m or
600s:
where value is any number of weeks, days, hours, minutes, or seconds, and
takes the format number{w|d|h|m|s}.
For example, to set interface_timeout to ten minutes, enter either 10m or
600s:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, select Status > OpenVPN > Servers.
The OpenVPN Servers page appears.
3. To view configuration details about an OpenVPN server, click the (configuration) icon in the
upper right of the OpenVPN server's status pane.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. To display details about all configured OpenVPN servers, type the following at the prompt:
>
Server : OpenVPN_server1
Enable : true
Type : tun
Zone : internal
IP Address : 192.168.30.1/24
Port : 1194
Use File : true
Metric : 0
Protocol : udp
First IP : 80
Last IP : 99
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, select Status > OpenVPN > Clients.
The OpenVPN Clients page appears.
3. To view configuration details about an OpenVPN client, click the (configuration) icon in the
upper right of the OpenVPN client's status pane.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. To display details about all configured OpenVPN clients, type the following at the prompt:
>
Client : OpenVPN_client1
Enable : true
Status : up
Username : user1
IP address : 123.122.121.120
Remote : 120.121.122.123
MTU : 1492
Zone : internal
IP Address : 192.168.30.1/24
Port : 1194
>
n A GRE key.
n Enable the device to respond to keepalive packets.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add the GRE endpoint interface. For example, to add an interface named gre_endpoint:
6. Set the IP address and subnet mask of the local GRE endpoint. For example, to set the local
GRE endpoint's IP address and subnet mask to 10.10.1.1/24:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add the GRE endpoint tunnel. For example, to add a tunnel named gre_example:
4. Set the local endpoint to the GRE endpoint interface created in Task One, for example:
6. (Optional) Set a key that will be inserted in GRE packets created by this tunnel.
The key must match the key set by the remote endpoint.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click Status > IP tunnels.
The IP Tunnelspage appears.
3. To view configuration details about a GRE tunnel, click the (configuration) icon in the upper
right of the tunnel's status pane.
Configuration procedures
15. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
6. Add a policy:
(config vpn ipsec tunnel ipsec_gre1 policy 0)> local type custom
(config vpn ipsec tunnel ipsec_gre1 policy 0)>
8. Set the local network address to the IP address and subnet of the local GRE tunnel,
172.30.0.1/32:
(config vpn ipsec tunnel ipsec_gre1 policy 0)> local custom 172.30.0.1/32
(config vpn ipsec tunnel ipsec_gre1 policy 0)>
9. Set the remote network address to the IP address and subnet of the remote GRE tunnel,
172.30.0.2/32:
Command line
1. At the command line, type config to enter configuration mode:
> config
(config)>
5. Set the IPv4 address to the IP address of the local GRE tunnel, 172.30.0.1/32:
3. For Local endpoint, select the IPsec endpoint interface created in Task two (Interface: ipsec_
endpoint1).
4. For Remote endpoint, type the IP address of the GRE tunnel on EX50-2, 172.30.0.2.
Command line
1. At the command line, type config to enter configuration mode:
> config
(config)>
3. Set the local endpoint to the IPsec endpoint interface created in Task two
(/network/interface/ipsec_endpoint1):
4. Set the remote endpoint to the IP address of the GRE tunnel on EX50-2, 172.30.0.2:
Command line
1. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the device to the GRE tunnel created in Task three (/vpn/iptunnel/gre_tunnel1):
15. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the pre-shared key to the same pre-shared key that was configured for the EX50-1
(testkey):
6. Add a policy:
(config vpn ipsec tunnel ipsec_gre2 policy 0)> local type custom
(config vpn ipsec tunnel ipsec_gre2 policy 0)>
8. Set the local network address to the IP address and subnet of the local GRE tunnel,
172.30.0.2/32:
(config vpn ipsec tunnel ipsec_gre2 policy 0)> local custom 172.30.0.2/32
(config vpn ipsec tunnel ipsec_gre2 policy 0)>
9. Set the remote network address to the IP address and subnet of the remote GRE tunnel,
172.30.0.1/32:
6. For Address, type the IP address of the local GRE tunnel, 172.30.0.2/32.
Command line
1. At the command line, type config to enter configuration mode:
> config
(config)>
5. Set the IPv4 address to the IP address of the local GRE tunnel, 172.30.0.2/32:
3. For Local endpoint, select the IPsec endpoint interface created in Task two (Interface: ipsec_
endpoint2).
4. For Remote endpoint, type the IP address of the GRE tunnel on EX50-1, 172.30.0.1.
Command line
1. At the command line, type config to enter configuration mode:
> config
(config)>
3. Set the local endpoint to the IPsec endpoint interface created in Task two
(/network/interface/ipsec_endpoint2):
4. Set the remote endpoint to the IP address of the GRE tunnel on EX50-1, 172.30.0.1:
Command line
1. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the device to the GRE tunnel created in Task three (/vpn/iptunnel/gre_tunnel2):
NEMO
Network Mobility (NEMO) is a mobile networking technology that provides access to one or more
Local Area Networks (LANs) on your device. NEMO creates a tunnel between the home agent on the
mobile private network and the EX50 device, isolating the connection from internet traffic and
advertising the IP subnets of the LANs for remote access and device management.
Dynamic Mobile Network Routing (DMNR) is the implementation of NEMO for Verizon Wireless Private
Networks. DMNR support requires the use of Verizon SIM cards that have DMNR enabled.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
b. For Interface, select the local interface to use as a virtual NEMO network interface.
Generally, this will be the a Local Area Network (LAN).
c. (Optional) Repeat for additional interfaces.
14. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a NEMO tunnel. For example, to add a NEMO tunnel named nemo_example:
5. Set the IPv4 address of the NEMO home agent. This is provided by your cellular carrier.
6. Set the key used to authenticate to the home agent. This is provided by your cellular carrier.
7. Set the the number of seconds number of seconds until the authorization key expires. This is
provided by your cellular carrier.
If disabled, set the MTU size. The default MTU size for LANs on the EX50 device is 1500. The
MTU size of the NEMO tunnel will be smaller, to take into account the required headers.
Zone: The firewall zone assigned to this network interface. This can be
used by
packet filtering rules and access control lists to restrict network
traffic on
this interface.
Format:
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
Current value:
11. Configure the Care-of-Address, the local WAN interface of the internet facing network.
a. Set the method to determine the Care-of-Address:
n ip
If ip is used, set the IP address:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, select Status > NEMO.
The NEMO page appears.
3. To view configuration details about an NEMO tunnel, click the (configuration) icon in the
upper right of the tunnel's status pane.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. To display details about all configured NEMO tunnels, type the following at the prompt:
>
MTU : 1476
Lifetime (Actual) : 600
>
L2TPv3
Your EX50 device supports Layer 2 Tunnelling Protocol Version 3 (L2TPv3) static unmanaged Ethernet
tunnels.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
g. For Sequence numbering control, determine the sequence number control to prevent or
detect out of order packets. Allowed values are:
n None: No sequence numbering.
n Send: Add a sequence number to each outgoing packet.
n Receive: Reorder packets if they are received out of order.
n Both: Add a sequence number to each outgoing packet, and reorder packets if they
are received out of order.
The default is None.
h. Repeat for additional sessions.
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a L2TPv3 Ethernet tunnel. For example, to add a tunnel named L2TPv3_example:
/network/interface/defaultip
/network/interface/defaultlinklocal
/network/interface/lan
/network/interface/loopback
/network/interface/modem
/network/interface/wan
Current value:
6. Set the tunnel identifier for this tunnel. This must match the value for peer tunnel ID on the
remote peer.
10. Set the session identifier for this session. This must match the value for peer session ID on the
remote peer.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, select Status. Under VPN, select L2TPv3 Ethernet.
The L2TPv3 Ethernet page appears.
3. To view configuration details about an NEMO tunnel, click the (configuration) icon in the
upper right of the tunnel's status pane.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. To display details about all configured L2TPv3 Ethernet tunnels, type the following at the
prompt:
>
Local IP : 4.3.2.1
Remote IP : 10.10.10.1
Tunnel ID : modem
Device : le_test_test
RX Packets : 2,102
RX Bytes : 462
TX Packets : 2,787
TX Byptes : 3,120
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
3. Click Services > Web administration > Access Control List > Zones.
5. Select External.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
3. Click Configuration > Services > SSH > Access Control List > Zones.
4. For Add Zone, click .
5. Select External.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
l ECDH
Example:
a. Generate the SSL certificate and private key, for example:
# openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365
-out certificate.pem
b. Paste the contents of certificate.pem and key.pem into the SSL certificate field. The
contents of the certificate.pem must be first. For example:
8. For Allow legacy encryption protocols, enable this option to allow clients to connect to the
HTTPS session by using encryption protocols older than TLS 1.2, in addition to TLS 1.2 and
later protocols. This option is disabled by default, which means that only TLS 1.2 and later
encryption protocols are allowed with HTTPS connections.
9. View is set to Auto by default and normally should not be changed.
10. Legacy port redirection is used to redirect client HTTP requests to the HTTPS service. Legacy
port redirection is enabled by default, and normally these settings should not be changed. To
disable legacy port redirection, click to expand Legacy port redirection and deselect Enable.
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
Where value is a firewall zone defined on your device, or the any keyword.
referred to by packet
filtering rules and access control lists.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
Example
a. Generate the SSL certificate and private key, for example:
# openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365
-out certificate.pem
b. Paste the contents of certificate.pem and key.pem into the service web_admin cert
command. Enclose the contents of certificate.pem and key.pem in quotes. For example:
b2hhMRMwEQYDVQQKDApNY0JhbmUgSW5jMRAwDgYDVQQLDAdTdXBwb3J0MQ8wDQYD
VQQDDAZtY2JhbmUxHzAdBgkqhkiG9w0BCQEWEGptY2JhbmVAZGlnaS5jb20wHhcN
MjAwOTIyMTY1OTUyWhcNMjEwOTIyMTY1OTUyWjCBhzELMAkGA1UEBhMCVVMxDzAN
BgNVBAgMBk9yZWdvbjEOMAwGA1UEBwwFQWxvaGExEzARBgNVBAoMCk1jQmFuZSBJ
bmMxEDAOBgNVBAsMB1N1cHBvcnQxDzANBgNVBAMMBm1jYmFuZTEfMB0GCSqGSIb3
DQEJARYQam1jYmFuZUBkaWdpLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAOBn19AX01LO9plYtfRZq0bETwNwSCYGeEIOGJ7gHt/rihLVBJS1woYv
u1Oq1ohYxIawBY1iIPBD2GtzyEJXzBZdQRhwi/dRyRi4vr7EkjGDr0Vb/NVT0L5w
UzcMeT+71DYvKYm6GpcWx+LoKqFTjbMFBIze5pbBfru+SicId6joCHIuYq8Ehflx
6sy6s4MDbyTUAEN2YhsBaOljej64LNzcsHeISbAWibXWjOSsK+N1MivQq5uwIYw/
1fsnD8KDS43Wg57+far9fQ2MIHsgnoAGz+w6PIKJR594y/MfqQffDFNCh2lJY49F
hOqEtA5B9TyXRKwoa3j/lIC/t5cpIBcCAwEAAaNTMFEwHQYDVR0OBBYEFDVtrWBH
E1ZcBg9TRRxMn7chKYjXMB8GA1UdIwQYMBaAFDVtrWBHE1ZcBg9TRRxMn7chKYjX
MA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEBALj/mrgaKDNTspv9
ThyZTBlRQ59wIzwRWRYRxUmkVcR8eBcjwdBTWjSBLnFlD2WFOEEEnVz2Dzcixmj4
/Fw7GQNcYIKj+aIGJzbcKgox10mZB3VKYRmPpnpzHCkvFi4o81+bC8HJQfK9U80e
vDV0/vA5OB2j/DrjvlOrapCTkuyA0TVyGvgTASx2ATu9U45KZofm4odThQs/9FRQ
+cwSTb5v47KYffeyY+g3dyJw1/KgMJGpBUYNJDIsFQC9RfzPjKE2kz41hx4VksT/
q81WGstDXH++QTu2sj7vWkFJH5xPFt80HjtWKKpIfeOIlBPGeRHvdH2PQibx0OOt
Sa+P5O8=
-----END CERTIFICATE-----
-----BEGIN PRIVATE KEY-----
MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDgZ9fQF9NSzvaZ
WLX0WatGxE8DcEgmBnhCDhie4B7f64oS1QSUtcKGL7tTqtaIWMSGsAWNYiDwQ9hr
c8hCV8wWXUEYcIv3UckYuL6+xJIxg69FW/zVU9C+cFM3DHk/u9Q2LymJuhqXFsfi
6CqhU42zBQSM3uaWwX67vkonCHeo6AhyLmKvBIX5cerMurODA28k1ABDdmIbAWjp
Y3o+uCzc3LB3iEmwFom11ozkrCvjdTIr0KubsCGMP9X7Jw/Cg0uN1oOe/n2q/X0N
jCB7D56ABs/sOjyCiUefeMvzH6kH3wxTQodpSWOPRYTqhLQOQfU8l0SsKGt4/5SA
v7eXKSAXAgMBAAECggEBAMDKdi7hSTyrclDsVeZH4044+WkK3fFNPaQCWESmZ+AY
i9cCC513SlfeSiHnc8hP+wd70klVNNc2coheQH4+z6enFnXYu2cPbKVAkx9x4eeI
Ktx72wurpnr2JYf1v3Vx+S9T9WvN52pGuBPJQla3YdWbSf18wr5iHm9NXIeMTsFc
esdjEW07JRnxQEMZ1GPWT+YtH1+FzQ3+W9rFsFFzt0vcp5Lh1RGg0huzL2NQ5EcF
3brzIZjNAavMsdBFzdc2hcbYnbv7o1uGLujbtZ7WurNy7+Tc54gu2Ds25J0/0mgf
OxmqFevIqVkqp2wOmeLtI4o77y6uCbhfA6I+GWTZEYECgYEA/uDzlbPMRcWuUig0
CymOKlhEpx9qxid2Ike0G57ykFaEsKxVMKHkv/yvAEHwazIEzlc2kcQrbLWnDQYx
oKmXf87Y1T5AXs+ml1PlepXgveKpKrWwORsdDBd+OS34lyNJ0KCqqIzwAaf8lcSW
tyShAZzvuH9GW9WlCc8g3ifp9WUCgYEA4WSSfqFkQLA09sI76VLvUqMbb31bNgOk
ZuPg7uxuDk3yNY58LGQCoV8tUZuHtBJdrBDCtcJa5sasJZQrWUlZ8y/5zgCZmqQn
MzTD062xaqTenL0jKgKQrWig4DpUUhfc4BFJmHyeitosDPG98oCxuh6HfuMOeM1v
Xag6Z391VcsCgYBgBnpfFU1JoC+L7m+lIPPZykWbPT/qBeYBBki5+0lhzebR9Stn
VicrmROjojQk/sRGxR7fDixaGZolUwcRg7N7SH/y3zA7SDp4WvhjFeKFR8b6O1d4
PFnWO2envUUiE/50ZoPFWsv1o8eK2XT67Qbn56t9NB5a7QPvzSSR7jG77QKBgD/w
BrqTT9wl4DBrsxEiLK+1g0/iMKCm8dkaJbHBMgsuw1m7/K+fAzwBwtpWk21alGX+
Ly3eX2j9zNGwMYfXjgO1hViRxQEgNdqJyk9fA2gsMtYltTbymVYHyzMweMD88fRC
Ey2FlHfxIfPeE7MaHNCeXnN5N56/MCtSUJcRihh3AoGAey0BGi4xLqSJESqZZ58p
e71JHg4M46rLlrxi+4FXaop64LCxM8kPpROfasJJu5nlPpYHye959BBQnYcAheZZ
0siGswIauBd8BrZMIWf8JBUIC5EGkMiIyNpLJqPbGEImMUXk4Zane/cL7e06U8ft
BUtOtMefbBDDxpP+E+iIiuM=
-----END PRIVATE KEY-----"
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
b. To override the standard SSH configuration and only use the config_file parameter:
n If override is set to true, entries in Configuration file will be used in place of the
standard SSH configuration.
n If override is set to false, entries in Configuration file will be added to the
standard SSH configuration.
The default is false.
c. Set the configuration settings:
where value is one or more entires in the form of an OpenSSH sshd_config file. For
example, to enable the diffie-helman-group-sha-14 key exchange algorithm:
(config)> save
Configuration saved.
>
n Security: Using SSH keys for authentication is more secure than using passwords. Unlike a
password that can be guessed by an unauthorized user, SSH key pairs provide more
sophisticated security. A public key configured on the EX50 device is paired with a private key
on the user's PC. The private key, once generated, remains on the user’s PC.
n Scalability: SSH keys can be used on more than one EX50 device.
The private key file is named id_rsa and the public key file is named id_rsa.pub. (The .pub extension
is automatically appended to the name specified for the private key output file.)
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
You can add configure passwordless SSH login for an existing user or include the support when
creating a new user. See User authentication for information about creating a new user. These
instructions assume an existing user named temp_user.
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add an SSH key for the user by using the ssh_key command and pasting or typing a public
encryption key:
where:
(config)> save
Configuration saved.
>
Note Telnet is an insecure protocol and should only be used for backward-compatibility reasons, and
only if the network connection is otherwise secured.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
c. For Zone, select the appropriate firewall zone from the dropdown.
See Firewall configuration for information about firewall zones.
d. Click again to allow access through additional firewall zones.
6. Multicast DNS (mDNS) is disabled by default. mDNS is a protocol that resolves host names in
small networks that do not have a DNS server. To enable mDNS, click Enable mDNS.
7. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
(config)> save
Configuration saved.
>
Configure DNS
The EX50 device includes a caching DNS server which forwards queries to the DNS servers that are
associated with the network interfaces, and caches the results. This server is used within the device,
and cannot be disabled. Use the access control list to restrict external access to this server.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
c. For Zone, select the appropriate firewall zone from the dropdown.
See Firewall configuration for information about firewall zones.
d. Click again to allow access through additional firewall zones.
5. (Optional) Cache negative responses is enabled by default. Disabling this option may improve
performance on networks with transient DNS results, when one or more DNS servers may have
positive results. To disable, click Cache negative responses.
6. (Optional) Query all servers is enabled by default. This option is useful when only some DNS
servers will be able to resolve hostnames. To disable, click Query all servers.
7. (Optional) Rebind protection, if enabled, prevents upstream DNS servers from returning
private IP addresses. To enable, click Rebind protection.
8. (Optional) Allow localhost rebinding is enabled by default if Rebind protection is enabled.
This is useful for Real-time Black List (RBL) servers.
9. (Optional) To add additional DNS servers:
a. Click DNS servers.
b. For Add Server, click .
c. (Optional) Enter a label for the DNS server.
d. For DNS server, enter the IP address of the DNS server.
e. Domain restricts the device's use of this DNS server based on the domain. If no domain
are listed, then all queries may be sent to this server.
10. (Optional) To add host names and their IP addresses that the device's DNS server will resolve:
a. Click Additional DNS hostnames.
b. For Add Host, click .
c. Type the IP address of the host.
d. For Name, type the hostname.
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
c. To restrict the device's use of this DNS server based on the domain, use the domain
command. If no domain are listed, then all queries may be sent to this server.
9. (Optional) Add host names and their IP addresses that the device's DNS server will resolve
a. Add a host:
(config)> save
Configuration saved.
>
Command line
>
SNMP Security
By default, the EX50 device automatically blocks SNMP packets from being received over WAN and
LAN interfaces. As a result, if you want a EX50 device to receive SNMP packets, you must configure the
SNMP access control list to allow the device to receive the packets. See Configure Simple Network
Management Protocol (SNMP).
n Enable SNMP.
n Firewall configuration using access control to allow remote connections to the SNMP agent.
n The user name and password used to connect to the SNMP agent.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
c. For Zone, select the appropriate firewall zone from the dropdown.
See Firewall configuration for information about firewall zones.
d. Click again to allow access through additional firewall zones.
6. Type the Username used to connect to the SNMP agent.
7. Type the Password used to connect to the SNMP agent.
8. (Optional) For Port, type the port number. The default is 161.
9. (Optional) Multicast DNS (mDNS) is disabled by default. mDNS is a protocol that resolves host
names in small networks that do not have a DNS server. To enable mDNS, click Enable mDNS.
10. (Optional) Select the Authentication type, either MD5 or SHA. The default is MD5.
11. (Optional) Type the Privacy passphrase. If not set, the password, entered above, is used.
12. (Optional) Select the Privacy protocol, either DES or AES. The default is DES.
13. (Optional) Click Enable version 2c access to enable read-only access to SNMP version 2c.
14. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
6. Set the password for the user that will be used to connect to the SNMP agent:
7. (Optional) Set the port number for the SNMP agent. The default is 161.
9. (Optional) Set the authentication type. Allowed values are MD5 or SHA. The default is MD5.
10. (Optional) Set the privacy passphrase. If not set, the password, entered above, is used.
11. (Optional) Set the privacy protocol, either DES or AES. The default is DES.
(config)> save
Configuration saved.
>
Download MIBs
This procedure is available from the WebUI only.
n Enable SNMP.
To download a .zip archive of the SNMP MIBs supported by this device:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. Enable SNMP.
See Configure Simple Network Management Protocol (SNMP) for information about enabling
and configuring SNMP support on the EX50 device.
3. On the main menu, click Status. Under Services, click SNMP.
Note If you have recently enabled SNMP and the SNMP option is not visible, refresh your
browser.
4. Click Download.
Location information
Your EX50 device can be configured to use the following location sources:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
4. The location service is enabled by default. To disable, or to enable if it has been disabled, click
Enable.
5. For Location update interval, type the amount of time to wait between polling location
sources for new location data. The default is ten seconds.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Location update interval to ten minutes, enter 10m or 600s.
6. For information about configuring Location sources, see the following:
a. To set a static location for the device, see Configure the device to use a user-defined static
location.
b. To accept location information from an external location-enabled server, see Configure the
device to accept location messages from external sources.
If multiple location sources are enabled at the same time, the device's location will be
determined based on the order that the location sources are listed here.
7. For information about configuring Destination servers, see Forward location information to a
remote host.
8. For information about configuring Geofence, see Configure geofencing.
9. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the amount of time that the EX50 device will wait before polling location sources for
updated location data:
where value is any number of hours, minutes, or seconds, and takes the format number
{h|m|s}.
For example, to set interval to ten minutes, enter either 10m or 600s:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
10. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
where int is any integer between -90 and 90, with up to six decimal places.
7. Set the longitude of the device:
where int is any integer between -180 and 180, with up to six decimal places.
8. Set the altitude of the device:
(config)> save
Configuration saved.
>
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
6. Set the UDP port that will receive incoming location messages.
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
__|%s|__|%v|__
14. Type a four-digit alphanumeric Vehicle ID that will be included with to location messages. If
no vehicle ID is configured, this setting defaults to 0000.
15. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the hostname or IP address of the remote host to which location messages will be sent:
6. Set the TCP or UDP port on the remote host to which location messages will be sent:
7. Set the number of Location update intervals to wait before forwarding location data to this
server. See Configure the location service for more information about setting the Location
update interval.
8. Set the protocol type for the messages. Allowed values are taip or nmea; the default is taip:
9. (Optional) Set the text to prepend to the forwarded message. Two variables can be included in
the prepended text:
n %s: Includes the EX50 device's serial number in the prepended text.
n %v: Includes the vehicle ID in the prepended text.
(config service location forward 0)> prepend __|%s|__|%v|__
(config service location forward 0)>
12. (Optional) Specify types of messages that will be forwarded. Allowed values vary depending on
the message protocol type. By default, all message types are forwarded.
b. Use the index number to delete the message type. For example, to delete the gsa
(index number 2) message type:
b. Use the add command to add the message type. For example, to add the gsa
message type:
b. Use the index number to delete the message type. For example, to delete the id
(index number 2) message type:
b. Use the add command to add the message type. For example, to add the id
message type:
(config)> save
Configuration saved.
>
Configure geofencing
Geofencing is a mechanism to create a virtual perimeter that allows you configure your EX50 device to
perform actions when entering or exiting the perimeter. For example, you can configure a device to
factory default if its location service indicates that it has been moved outside of the geofence.
Multiple geofences can be defined for one device, allowing for a complex configuration in which
different actions are taken depending on the physical location of the device.
n Update interval, which determines the amount of time that the geofence should wait between
polling for updated location data.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
The geofence is enabled by default. Click Enable to disable, or to enable if it has been
disabled.
5. For Update interval, type the amount of time that the geofence should wait between polling
for updated location data. The default is one minute.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Update interval to ten minutes, enter 10m or 600s.
6. For Boundary type, select the type of boundary that the geofence will have.
n If Circular is selected:
a. Click to expand Center.
b. Type the Latitude and Longitude of the center point of the circle. Allowed values
are:
l For Latitude, any integer between -90 and 90, with up to six decimal places.
l For Longitude, any integer between -180 and 180, with up to six decimal
places.
c. For Radius, type the radius of the circle. Allowed values are an integer followed by
m or km, for example, 100m or 1km.
n If Polygonal is selected:
a. Click to expand Coordinates.
b. Click to add a point that represents a vertex of the polygon. A vertex is the point
at which two sides of a polygon meet.
c. Type the Latitude and Longitude of one of the vertices of the polygon. Allowed
values are:
l For Latitude, any integer between -90 and 90, with up to six decimal places.
l For Longitude, any integer between -180 and 180, with up to six decimal
places.
d. Click again to add an additional point, and continue adding points to create the
desired polygon.
For example, to configure a square polygon around the Digi headquarters, configure a
polygon with four points:
7. Define actions to be taken when the device's location triggers a geofence event:
n To define actions that will be taken when the device enters the geofence, or is inside
the geofence when it boots:
a. Click to expand On entry.
b. (Optional) Enable Bootup action to configure the device to perform the On entry
actions if the device is inside the geofence when it boots.
c. For Number of intervals, type or select the number of Update Intervals that must
take place prior to performing the On entry actions.
For example, if the Update interval is 1m (one minute) and the Number of
intervals is 3, the On entry actions will not be performed until the device has been
inside the geofence for three minutes.
d. Click to expand Actions.
e. Click to create a new action.
n To define actions that will be taken when the device exits the geofence, or is outside the
geofence when it boots:
a. Click to expand On exit.
b. (Optional) Enable Bootup action to configure the device to perform the On exit
actions if the device is inside the geofence when it boots.
c. For Number of intervals, type or select the number of Update Intervals that must
take place prior to performing the On exit actions.
For example, if the Update interval is 1m (one minute) and the Number of
intervals is 3, the On entry actions will not be performed until the device has been
inside the geofence for three minutes.
d. Click to expand Actions.
e. Click to create a new action.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a geofence:
4. Set the amount of time that the geofence should wait between polling for updated location
data:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set update_interval to ten minutes, enter either 10m or 600s:
6. Define actions to be taken when the device's location triggers a geofence event:
n To define actions that will be taken when the device enters the geofence, or is inside
the geofence when it boots:
a. (Optional) Configure the device to preform the actions if the device is inside the
geofence when it boots:
b. Set the number of update_intervals that must take place prior to performing the
actions:
For example, if the update interval is 1m (one minute) and the num_intervals is set
to 3, the actions will not be performed until the device has been inside the
geofence for three minutes.
c. Add an action:
i. Type ... to return to the root of the configuration:
If the script begins with #!, then the proceeding file path will be used to invoke
the script interpreter. If not, then the default shell will be used.
ii. To log the output of the script to the system log:
iii. To log the errors from the script to the system log:
iv. (Optional) Set the maximum amount of system memory that will be available
for the script and it spawned processes:
If you disable the sandbox, the script may render the system unusable.
vi. Repeat for any additional actions.
n To define actions that will be taken when the device exits the geofence, or is outside the
geofence when it boots:
a. (Optional) Configure the device to preform the actions if the device is outside the
geofence when it boots:
b. Set the number of update_intervals that must take place prior to performing the
actions:
For example, if the update interval is 1m (one minute) and the num_intervals is set
to 3, the actions will not be performed until the device has been outside the
geofence for three minutes.
c. Add an action:
i. Type ... to return to the root of the configuration:
If the script begins with #!, then the proceeding file path will be used to invoke
the script interpreter. If not, then the default shell will be used.
ii. To log the output of the script to the system log:
iii. To log the errors from the script to the system log:
iv. (Optional) Set the maximum amount of system memory that will be available
for the script and it spawned processes:
If you disable the sandbox, the script may render the system unusable.
vi. Repeat for any additional actions.
7. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click Status.
3. Under Services, click Location.
The device's current location is displayed, along with the status of any configured geofences.
Command line
Location Status
---------------
State : enabled
Source : 192.168.2.3
Latitude : 44* 55' 14.809" N (44.92078)
Longitude : 93* 24' 47.262" w (-93.413128)
Altitude : 279 meters
Velocity : 0 meters per second
Direction : None
Quality : Standard GNSS (2D/3D)
UTC Date and Time : Mon, 13 September 2021 8:04:23 03
No. of Satellites : 7
>
>
Modbus gateway
The EX50 supports the ability to function as a Modbus gateway, to provide serial-to-Ethernet
connectivity to Programmable Logic Controllers (PLCs), Remote Terminal Units (RTUs), and other
industrial devices. MODBUS provides client/server communication between devices connected on
different types of buses and networks, and the EX50 gateway allows for communication between
buses and and networks that use the Modbus protocol.
This section contains the following topics:
n Server configuration:
l Enable the server.
l Connection type, either socket or serial.
o If the connection type is socket, the IP protocol to be used.
o If the connection type is serial, the serial port to be used.
n Client configuration:
l Enable the client.
l Connection type, either socket or serial.
o If the connection type is socket:
o The IP protocol to be used.
o The hostname or IPv4 address of the remote host on which the Modbus server is
running.
o If the connection type is serial:
o The serial port to be used.
l Modbus address or addresses to determine if messages should be forwarded to a
destination device.
n Server configuration:
l The packet mode.
l The maximum time between bytes in a packet.
l If the connection type is set to socket:
o The port to use.
o The inactivity timeout.
o Access control list.
l If the connection type is set to serial:
o Whether to use half duplex (two wire) mode.
n Client configuration:
l The packet mode.
l The maximum time between bytes in a packets.
l Whether to send broadcast messages.
l Response timeout
l If connection type is set to socket:
o The port to use.
o The inactivity timeout.
l If connection type is set to serial:
o Whether to use half duplex (two wire) mode.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
3. The new Modbus gateway server is enabled by default. Toggle off Enable the server to
disable.
4. For Connection type, select Socket or Serial. Available options in the gateway server
configuration vary depending on this setting.
n If Socket is selected for Connection type:
a. For IP Protocol, select TCP or UDP. The default is TCP.
b. For Port, enter or select an appropriate port. The default is port 502.
n If Serial is selected for Connection type:
a. For Serial port, select the appropriate serial port on the EX50 device.
5. For Packet mode, select RTU or RAW (if Connection type is set to Socket) or ASCII (if
Connection typeis set to Serial) for the type of packet that will be used by this connection.
The default is RTU.
6. For Packet idle gap, type the maximum allowable time between bytes in a packet.
Allowed values are between 10 milliseconds and one second, and take the format number
{ms|s}.
For example, to set Packet idle gap to 20 milliseconds, enter 20ms.
7. If Connection type is set to Socket, for Inactivity timeout, type the amount of time to wait
before disconnecting the socket when it has become inactive.
Allowed values are any number of minutes or seconds up to a maximum of 15 minutes, and
take the format number{m|s}.
For example, to set Inactivity timeout to ten minutes, enter 10m or 600s.
8. (Optional) If Connection type is set to Serial, click Half duplex to enable half duplex (two
wire) mode.
9. (Optional) If Connection type is set to Socket, click to expand Access control list:
n To limit access to specified IPv4 addresses and networks:
a. Click IPv4 Addresses.
b. For Add Address, click .
c. For Address, enter the IPv4 address or network that can access the device's web
administration service. Allowed values are:
l A single IP address or host name.
l A network designation in CIDR notation, for example, 192.168.1.0/24.
l any: No limit to IPv4 addresses that can access the web administration service.
d. Click again to list additional IP addresses or networks.
Configure clients
1. Click to expand Clients.
2. For Add Modbus client, type a name for the client and click .
3. The new Modbus gateway client is enabled by default. Toggle off Enable the client to disable.
4. For Connection type, select Socket or Serial. Available options in the gateway server
configuration vary depending on this setting.
n If Socket is selected for Connection type:
a. For IP Protocol, select TCP or UDP. The default is TCP.
b. For Port, enter or select an appropriate port. The default is port 502.
c. For Remote host, type the hostname or IP address of the remote host on which the
Modbus server is running.
n If Serial is selected for Connection type:
a. For Serial port, select the appropriate serial port on the EX50 device.
5. For Packet mode, select RTU or RAW (if Connection type is set to Socket) or ASCII (if
Connection typeis set to Serial) for the type of packet that will be used by this connection.
The default is RTU.
6. For Packet idle gap, type the maximum allowable time between bytes in a packet.
Allowed values are between 10 milliseconds and one second, and take the format number
{ms|s}.
For example, to set Packet idle gap to 20 milliseconds, enter 20ms.
7. If Connection type is set to Socket, for Inactivity timeout, type the amount of time to wait
before disconnecting the socket when it has become inactive.
Allowed values are any number of minutes or seconds up to a maximum of 15 minutes, and
take the format number{m|s}.
For example, to set Inactivity timeout to ten minutes, enter 10m or 600s.
8. (Optional) If Connection type is set to Serial, click Half duplex to enable half duplex (two
wire) mode.
9. (Optional) If Connection type is set to Socket, click to expand Access control list:
n To limit access to specified IPv4 addresses and networks:
a. Click IPv4 Addresses.
b. For Add Address, click .
c. For Address, enter the IPv4 address or network that can access the device's web
administration service. Allowed values are:
l A single IP address or host name.
l A network designation in CIDR notation, for example, 192.168.1.0/24.
l any: No limit to IPv4 addresses that can access the web administration service.
d. Click again to list additional IP addresses or networks.
n To limit access to specified IPv6 addresses and networks:
a. Click IPv6 Addresses.
b. For Add Address, click .
c. For Address, enter the IPv6 address or network that can access the device's web
administration service. Allowed values are:
l A single IP address or host name.
l A network designation in CIDR notation, for example, 2001:db8::/48.
l any: No limit to IPv6 addresses that can access the web administration service.
d. Click again to list additional IP addresses or networks.
n To limit access to hosts connected through a specified interface on the EX50 device:
a. Click Interfaces.
b. For Add Interface, click .
c. For Interface, select the appropriate interface from the dropdown.
d. Click again to allow access through additional interfaces.
n To limit access based on firewall zones:
a. Click Zones.
b. For Add Zone, click .
c. For Zone, select the appropriate firewall zone from the dropdown.
See Firewall configuration for information about firewall zones.
d. Click again to allow access through additional firewall zones.
10. (Optional) Enable Send broadcast messages to configure the gateway to send broadcast
messages to this client.
11. For Response timeout, type the maximum time to wait for a response to a message.
Allowed values are between 1 millisecond and 700 milliseconds, and take the format
numberms.
For example, to set Response timeout to 100 milliseconds, enter 100ms. The default is 700ms.
12. Click to expand Modbus address filter.
This filter is used by the gateway to determine if a message should be forwarded to a
destination device. If the Modbus address in the message matches one or more of the filters,
the message is forwarded. If it does not match the filters, the message is not forwarded.
13. For Address or address range, type a Modbus address or range of addresses. Allowed values
are 1 through 255 or a hyphen-separated range.
For example, to have this client filter for incoming messages that contain the Modbus address
of 10, type 10. To filter for all messages with addresses in the range of 20 to 30, type 20-30.
To add additional address filters for this client, click .
14. For Fixed Modbus server address, if request messages handled by this client should always
be forwarded to a specific device, type the device's Modbus address. Leave at the default
setting of 0 to allow messages that match the Modbus address filter to be forwarded to
devices based on the Modbuss address in the message.
15. For Adjust Modbus server address, type a value to adjust the Modbus server address
downward by the specified value prior to delivering the message. Allowed values are 0 through
255. Leave at the default setting of 0 to not adjust the server address.
If a packet contains a Modbus server address above the amount entered here, the address will
be adjusted downward by this amount before the packet is delivered. This allows you to
configure clients on the gateway that will forward messages to remote devices with the same
Modbus address on different buses. For example, if there are two devices on two different
buses that have the same Modbus address of 10, you can create two clients on the gateway:
n Client one:
l Modbus address filter set to 10.
This will configure the gateway to deliver all messages that have the Modbus server
address of 10 to this device.
n Client two:
l Modbus address filter set to 20.
l Adjust Modbus server address set to 10.
This will configure the gateway to deliver all messages that have the Modbus server
address address of 20 to the device with address 10.
16. Repeat these steps to configure additional clients.
17. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Configure servers:
a. Add a server:
where value is any number between 10 milliseconds and one second, and take
the format number{ms|s}.
For example, to set idle_gap to 20 milliseconds, enter 20ms.
v. Set the amount of time to wait before disconnecting the socket when it has
become inactive:
Serial
Additional Configuration
-------------------------------------------------------
------------------------
port1 Port 1
where value is any number between 10 milliseconds and one second, and take
the format number{ms|s}.
For example, to set idle_gap to one second, enter 1000ms or 1s.
b. Add a client:
where value is any number between 10 milliseconds and one second, and take
the format number{ms|s}.
For example, to set idle_gap to 20 milliseconds, enter 20ms.
v. Set the amount of time to wait before disconnecting the socket when it has
become inactive:
vi. Set the hostname or IP address of the remote host on which the Modbus server
is running:
Serial
Additional Configuration
-------------------------------------------------------
------------------------
port1 Port 1
where value is any number between 10 milliseconds and one second, and take
the format number{ms|s}.
For example, to set idle_gap to one second, enter 1000ms or 1s.
iv. (Optional) Enable half-duplex (two wire) mode:
Allowed values are between 1 millisecond and 700 milliseconds, and take the format
numberms.
n To filter for all messages with addresses in the range of 20 to 30, set the index 0
entry to 20-30:
To add additional filters, increment the index number. For example, to add an additional
filter for addresses in the range of 50-100:
g. If request messages handled by this client should always be forwarded to a specific device,
, use fixed_server_address to set the device's Modbus address:
Leave at the default setting of 0 to allow messages that match the Modbus address filter to
be forwarded to devices based on the Modbuss address in the message.
h. To adjust the Modbus server address downward by the specified value prior to delivering
the message, use adjust_server_address:
where value is an integer from 0 to 255. Leave at the default setting of 0 to not adjust the
server address.
If a packet contains a Modbus server address above the amount entered here, the address
will be adjusted downward by this amount before the packet is delivered. This allows you
to configure clients on the gateway that will forward messages to remote devices with the
same Modbus address on different buses. For example, if there are two devices on two
different buses that have the same Modbus address of 10, you can create two clients on
the gateway:
n Client one:
l filter set to 10.
This will configure the gateway to deliver all messages that have the Modbus server
address of 10 to this device.
n Client two:
l filter set to 20.
l adjust_server_address set to 10.
This will configure the gateway to deliver all messages that have the Modbus server
address address of 20 to the device with address 10.
i. Repeat the above instructions for additional clients.
6. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, select Status > Modbus Gateway.
The Modbus Gateway page appears.
Statistics related to the Modbus gateway server are displayed. If the message Server
connections not available is displayed, this indicates that there are no connected clients.
n To view information about Modbus gateway clients, click Clients.
n To view statistics that are common to both the clients and server, click Common
Statistics.
n To view configuration details about the gateway, click the (configuration) icon in the
upper right of the gateway's status pane.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the show modbus-gateway command at the system prompt:
Client Uptime
-------------------- ------
modbus_socket_41 0
modbus_socket_21 0
modbus_serial_client 428
>
If the message Server connections not available is displayed, this indicates that there are no
connected clients.
3. Use the show modbus-gateway verbose command at the system prompt to display more
information:
Client Uptime
-------------------- ------
modbus_socket_41 0
modbus_socket_21 0
modbus_serial_client 506
Common Statistics
-----------------
Configuration Updates : 1
Client Configuration Failure : 0
Server Configuration Failure : 0
Configuration Load Failure : 0
Incoming Connections : 4
Internal Error : 0
Resource Shortages : 0
Servers
-------
modbus_socket
-------------
Clients
-------
modbus_socket_41
----------------
Address Translation Errors : 0
Connection Errors : 0
Packet Errors : 0
RX Responses : 4
RX Timeouts : 0
TX Broadcasts : 0
TX Requests : 4
modbus_socket_21
----------------
Address Translation Errors : 0
Connection Errors : 0
Packet Errors : 0
RX Responses : 4
RX Timeouts : 0
TX Broadcasts : 0
TX Requests : 4
modbus_serial_client
--------------------
Address Translation Errors : 0
Connection Errors : 0
Packet Errors : 0
RX Responses : 4
RX Timeouts : 0
TX Broadcasts : 0
TX Requests : 4
>
System time
By default, the EX50 device synchronizes the system time by periodically connecting to the Digi NTP
server, time.devicecloud.com. In this mode, the device queries the time server based on following
events and schedule:
n At boot time.
n Once a day.
The default configuration has the system time zone set to UTC. No additional configuration is required
for the system time if the default configuration is sufficient. However, you can change the default time
zone and the default NTP server, as well as configuring additional NTP servers. If multiple servers are
configured, a number of time samples are obtained from each of the servers and a subset of the NTP
clock filter and selection algorithms are applied to select the best of these. See Configure the system
time for details about changing the default configuration.
The EX50 device can also be configured to serve as an NTP server, providing NTP services to
downstream devices. See Network Time Protocol for more information about NTP server support.
You can also set the local date and time manually, if there is no access to NTP servers. See Manually
set the system date and time for information
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note This list is synchronized with the list of servers included with NTP server configuration,
and changes made to one will be reflected in the other. See Configure the device as an NTP
server for more information about NTP server configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
3. (Optional) Set the timezone for the location of your EX50 device. The default is UTC.
Where value is the timezone using the format specified with the following command:
Timezone: The timezone for the location of this device. This is used to
adjust the time for log
messages. It also affects actions that occur at a specific time of day.
Format:
Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa
...
(config)>
4. (Optional) Add an upstream NTP server that the device will use to synchronize its time to the
appropriate location in the list of NTP servers. The default setting is time.devicecloud.com.
n To delete the default NTP server, time.devicecloud.com:
n To add the NTP server to the beginning of the list, use the index value of 0 to indicate
that it should be added as the first server:
n To add the NTP server to the end of the list, use the index keyword end:
n To add the NTP server in another location in the list, use an index value to indicate the
appropriate position. For example:
Note This list is synchronized with the list of servers included with NTP server configuration,
and changes made to one will be reflected in the other. See Configure the device as an NTP
server for more information about NTP server configuration.
(config)> save
Configuration saved.
>
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Test the configured NTP servers for connectivity:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Set the device's local date and time:
where value is the The date in year-month-day hour:minute:second format. For example:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note By default, the access control list for the NTP service is empty, which means that all
downstream hosts connected to the EX50 device can use the NTP service.
6. (Optional) Add upstream NTP servers that the device will use to synchronize its time. The
default setting is time.devicecloud.com.
n To change the default value of the NTP server:
a. Click NTP servers.
b. For Server, type a new server name.
n To add an NTP server:
a. Click NTP servers.
b. For Add Server, click .
c. For Server, enter the hostname of the upstream NTP server that the device will use
to synchronize its time.
d. Click to add additional NTP servers. If multiple servers are included, servers are
tried in the order listed until one succeeds.
Note This list is synchronized with the list of servers included with NTP client configuration,
and changes made to one will be reflected in the other. See Configure the system time for
more information about NTP client configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. (Optional) Add an upstream NTP server that the device will use to synchronize its time to the
appropriate location in the list of NTP servers. The default setting is time.devicecloud.com.
n To delete the default NTP server, time.devicecloud.com:
n To add the NTP server to the beginning of the list, use the index value of 0 to indicate
that it should be added as the first server:
n To add the NTP server to the end of the list, use the index keyword end:
n To add the NTP server in another location in the list, use an index value to indicate the
appropriate position. For example:
Note This list is synchronized with the list of servers included with NTP client configuration,
and changes made to one will be reflected in the other. See Configure the system time for
more information about NTP client configuration.
5. (Optional) Configure the access control list to limit downstream access to the EX50 device's
NTP service.
n To limit access to specified IPv4 addresses and networks:
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
Note By default, the access control list for the NTP service is empty, which means that all
downstream hosts connected to the EX50 device can use the NTP service.
6. (Optional) Set the timezone for the location of your EX50 device. The default is UTC.
Where value is the timezone using the format specified with the following command:
Timezone: The timezone for the location of this device. This is used to
adjust the time for log
messages. It also affects actions that occur at a specific time of day.
Format:
Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa
...
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click Status.
3. Under Services, click NTP.
The NTP server status page is displayed.
Command line
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add the multicast route. For example, to add a route named test:
4. The multicast route is enabled by default. If it has been disabled, enable the route:
5. Set the source address for the route. This must be a multicast IP address between 224.0.0.1
and 239.255.255.255.
6. Set the source port for the route. Ensure the port is not used by another protocol.
7. Set the source interface for the route where multicast packets will arrive:
a. Use the ? to determine available interfaces:
8. Set a destination interface that the EX50 device will send mutlicast packets to:
a. Use the ? to determine available interfaces:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
The bond device is enabled by default. To disable, click to toggle off Enable.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Additional Configuration
---------------------------------------------------------------------
-------
loopback
b. Add a device:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
c. For Zone, select the appropriate firewall zone from the dropdown.
See Firewall configuration for information about firewall zones.
d. Click again to allow access through additional firewall zones.
6. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n To limit access to hosts connected through a specified interface on the EX50 device:
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
(config)> save
Configuration saved.
>
Note Using iPerf clients that are at a version earlier than iPerf3 to connect to the EX50 device's iPerf3
server may result in unpredictable results. As a result, Digi recommends using an iPerf client at
version 3 or newer to connect to the EX50 device's iPerf3 server.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. (Optional) Set the port number for the iPerf server listening port. The default is 5201.
5. (Optional) Set the access control list to restrict access to the iPerf server:
n To limit access to specified IPv4 addresses and networks:
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
(config)> save
Configuration saved.
>
$ iperf3 -c device_ip
$ iperf3 -c 192.168.2.1
Connecting to host 192.168.2.1, port 5201
[ 4] local 192.168.3.100 port 54934 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 26.7 MBytes 224 Mbits/sec 8 2.68 MBytes
[ 4] 1.00-2.00 sec 28.4 MBytes 238 Mbits/sec 29 1.39 MBytes
[ 4] 2.00-3.00 sec 29.8 MBytes 250 Mbits/sec 0 1.46 MBytes
[ 4] 3.00-4.00 sec 31.2 MBytes 262 Mbits/sec 0 1.52 MBytes
[ 4] 4.00-5.00 sec 32.1 MBytes 269 Mbits/sec 0 1.56 MBytes
[ 4] 5.00-6.00 sec 32.5 MBytes 273 Mbits/sec 0 1.58 MBytes
[ 4] 6.00-7.00 sec 33.9 MBytes 284 Mbits/sec 0 1.60 MBytes
[ 4] 7.00-8.00 sec 33.7 MBytes 282 Mbits/sec 0 1.60 MBytes
[ 4] 8.00-9.00 sec 33.5 MBytes 281 Mbits/sec 0 1.60 MBytes
[ 4] 9.00-10.00 sec 33.2 MBytes 279 Mbits/sec 0 1.60 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 315 MBytes 264 Mbits/sec 37 sender
[ 4] 0.00-10.00 sec 313 MBytes 262 Mbits/sec receiver
iperf Done.
$
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
l any: No limit to IPv6 addresses that can access the ping responder.
d. Click again to list additional IP addresses or networks.
n To limit access to hosts connected through a specified interface on the EX50 device:
a. Click Interfaces.
b. For Add Interface, click .
c. For Interface, select the appropriate interface from the dropdown.
d. Click again to allow access through additional interfaces.
n To limit access based on firewall zones:
a. Click Zones.
b. For Add Zone, click .
c. For Zone, select the appropriate firewall zone from the dropdown.
See Firewall configuration for information about firewall zones.
d. Click again to allow access through additional firewall zones.
5. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. (Optional) Set the port number for the iPerf server listening port. The default is 5201.
5. (Optional) Set the access control list to restrict access to the iPerf server:
n To limit access to specified IPv4 addresses and networks:
Where value is a firewall zone defined on your device, or the any keyword.
Additional Configuration
--------------------------------------------------------
-----------------------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)>
(config)> save
Configuration saved.
>
$ iperf3 -c device_ip
$ iperf3 -c 192.168.2.1
Connecting to host 192.168.2.1, port 5201
[ 4] local 192.168.3.100 port 54934 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 26.7 MBytes 224 Mbits/sec 8 2.68 MBytes
[ 4] 1.00-2.00 sec 28.4 MBytes 238 Mbits/sec 29 1.39 MBytes
[ 4] 2.00-3.00 sec 29.8 MBytes 250 Mbits/sec 0 1.46 MBytes
[ 4] 3.00-4.00 sec 31.2 MBytes 262 Mbits/sec 0 1.52 MBytes
[ 4] 4.00-5.00 sec 32.1 MBytes 269 Mbits/sec 0 1.56 MBytes
[ 4] 5.00-6.00 sec 32.5 MBytes 273 Mbits/sec 0 1.58 MBytes
[ 4] 6.00-7.00 sec 33.9 MBytes 284 Mbits/sec 0 1.60 MBytes
[ 4] 7.00-8.00 sec 33.7 MBytes 282 Mbits/sec 0 1.60 MBytes
[ 4] 8.00-9.00 sec 33.5 MBytes 281 Mbits/sec 0 1.60 MBytes
[ 4] 9.00-10.00 sec 33.2 MBytes 279 Mbits/sec 0 1.60 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 315 MBytes 264 Mbits/sec 37 sender
[ 4] 0.00-10.00 sec 313 MBytes 262 Mbits/sec receiver
iperf Done.
$
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click System. Under Administration, click File System.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, use the scp command to upload the Python application script to the
EX50 device:
> scp host hostname-or-ip user username remote remote-path local local-
path to local
where:
n hostname-or-ip is the hostname or ip address of the remote host.
n username is the name of the user on the remote host.
n remote-path is the path and filename of the file on the remote host that will be copied
to the EX50 device.
n local-path is the location on the EX50 device where the copied file will be placed.
For example:
To upload a Python application from a remote host with an IP address of 192.168.4.1 to the
/etc/config/scripts directory on the EX50 device, issue the following command:
Note You can also create Python applications by using the vi command when logged in with shell
access.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Custom scripts are enabled by default. To disable, click Enable to toggle off.
5. (Optional) For Label, provide a label for the script.
6. For Run mode, select the mode that will be used to run the script. Available options are:
n On boot: The script will run once each time the device boots.
l If On boot is selected, select the action that will be taken when the script completes
in Exit action. Available options are:
o None: Action taken when the script exits.
o Restart script: Runs the script repeatedly.
o Reboot: The device will reboot when the script completes.
n Interval: The script will start running at the specified interval, within 30 seconds after
the configuration change is saved.
l If Interval is selected, in Interval, type the interval.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and
take the format number{w|d|h|m|s}.
For example, to set Interval to ten minutes, enter 10m or 600s.
l Click to enable Run single to run only a single instance of the script at a time.
If Run single is not enabled, a new instance of the script will be started at every
interval, regardless of whether the script is still running from a previous interval.
n Set time: Runs the script at a specified time of the day.
l If Set Time is selected, specify the time that the script should run in Run time,
using the format HH:MM.
n During system maintenance: The script will run during the system maintenance time
window.
7. For Commands, enter the commands that will execute the script.
If the script begins with #!, then the script will be invoked in the location specified by the path
for the script command. Otherwise, the default shell will be used (equivalent to #!/bin/sh).
8. Script logging options:
a. Click to enable Log script output to log the script's output to the system log.
b. Click to enable Log script errors to log script errors to the system log.
If neither option is selected, only the script's exit code is written to the system log.
9. For Maximum memory, enter the maximum amount of memory available to be used by the
script and its subprocesses, using the format number{b|bytes|KB|k|MB|MB|M|GB|G|TB|T}.
10. Sandbox is enabled by default, which restricts access to the file system and available
commands that can be used by the script. This option protects the script from accidentally
destroying the system it is running on.
11. Click to enable Once to configure the script to run only once at the specified time.
If Once is enabled, rebooting the device will cause the script to not run again. The only way to
re-run the script is to:
n Remove the script from the device and add it again.
n Make a change to the script.
n Uncheck Once.
12. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a script:
where value is any string. if spaces are used, enclose value within double quotes.
5. Set the mode that will be used to run the script:
where value is any number of weeks, days, hours, minutes, or seconds, and takes
the format number{w|d|h|m|s}.
For example, to set on_interval to ten minutes, enter either 10m or 600s:
If once is set to false, a new instance of the script will be started at every interval,
regardless of whether the script is still running from a previous interval.
n set_time: Runs the script at a specified time of the day.
l If set_time is set, set the time that the script should run, using the format HH:MM:
n maintenance_time: The script will run during the system maintenance time window.
6. Set the commands that will execute the script:
where filename is the path and filename of the script, and any related command line
information.
If the script begins with #!, then the script will be invoked in the location specified by the path
for the script command. Otherwise, the default shell will be used (equivalent to #!/bin/sh).
7. Script logging options:
n To log the script's output to the system log:
If syslog_stdout and syslog_stderr are not enabled, only the script's exit code is written to the
system log.
8. Set the maximum amount of memory available to be used by the script and its subprocesses:
If once is enabled, rebooting the device will cause the script to run again. The only way to re-
run the script is to:
n Remove the script from the device and add it again.
n Make a change to the script.
n Disable once.
10. Sandbox is enabled by default. This option protects the script from accidentally destroying the
system it is running on.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click System. Under Administration, click File System.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, use the scp command to upload the Python application script to the
EX50 device:
> scp host hostname-or-ip user username remote remote-path local local-
path to local
where:
n hostname-or-ip is the hostname or ip address of the remote host.
n username is the name of the user on the remote host.
n remote-path is the path and filename of the file on the remote host that will be copied
to the EX50 device.
n local-path is the location on the EX50 device where the copied file will be placed.
For example:
To upload a Python application from a remote host with an IP address of 192.168.4.1 to the
/etc/config/scripts directory on the EX50 device, issue the following command:
Note You can also create Python applications by using the vi command when logged in with shell
access.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Custom scripts are enabled by default. To disable, click Enable to toggle off.
5. (Optional) For Label, provide a label for the script.
6. For Run mode, select Manual.
7. For Commands, enter the commands that will execute the script.
If the script begins with #!, then the script will be invoked in the location specified by the path
for the script command. Otherwise, the default shell will be used (equivalent to #!/bin/sh).
8. Script logging options:
a. Click to enable Log script output to log the script's output to the system log.
b. Click to enable Log script errors to log script errors to the system log.
If neither option is selected, only the script's exit code is written to the system log.
9. For Maximum memory, enter the maximum amount of memory available to be used by the
script and its subprocesses, using the format number{b|bytes|KB|k|MB|MB|M|GB|G|TB|T}.
10. Sandbox is enabled by default, which restricts access to the file system and available
commands that can be used by the script. This option protects the script from accidentally
destroying the system it is running on.
11. Click to enable Once to configure the script to run only once at the specified time.
If Once is enabled, rebooting the device will cause the script to not run again. The only way to
re-run the script is to:
n Remove the script from the device and add it again.
n Make a change to the script.
n Uncheck Once.
12. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a script:
where value is any string. if spaces are used, enclose value within double quotes.
5. Set the run mode to manual:
where filename is the path and filename of the script, and any related command line
information.
If the script begins with #!, then the script will be invoked in the location specified by the path
for the script command. Otherwise, the default shell will be used (equivalent to #!/bin/sh).
7. Script logging options:
n To log the script's output to the system log:
If syslog_stdout and syslog_stderr are not enabled, only the script's exit code is written to the
system log.
8. Set the maximum amount of memory available to be used by the script and its subprocesses:
If once is enabled, rebooting the device will cause the script to run again. The only way to re-
run the script is to:
n Remove the script from the device and add it again.
n Make a change to the script.
n Disable once.
10. Sandbox is enabled by default. This option protects the script from accidentally destroying the
system it is running on.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. At the Status page, click Scripts.
The Scripts page displays:
3. For scripts that are enabled and configured to have a run mode of Manual, click Start Script
to start the script.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Determine the name of scripts that are currently running:
(config)> save
Configuration saved.
>
WebUI
3. For scripts that are currently running, click Stop Script to stop the script.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Determine the name of scripts that are currently running:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. At the Status page, click Scripts.
The Scripts page displays:
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the show scripts command at the system prompt:
Note Python applications cannot be run from the Admin CLI. You must access the device shell in order
to run Python applications from the command line. See Authentication groups for information about
configuring authentication groups that include shell access.
WebUI
Command line
a. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
b. At the command line, use the scp command to upload the Python application script to the
EX50 device:
where:
n hostname-or-ip is the hostname or ip address of the remote host.
n username is the name of the user on the remote host.
n remote-path is the path and filename of the file on the remote host that will be
copied to the EX50 device.
n local-path is the location on the EX50 device where the copied file will be placed.
For example:
To upload a Python application from a remote host with an IP address of 192.168.4.1 to
the /etc/config/scripts directory on the EX50 device, issue the following command:
Note You can also create Python applications by using the vi command when logged in with
shell access.
2. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
3. Use the python command to run the Python application. In the following example, the Python
application, test.py, takes 3 parameters: 120, ports and storage:
Note The Python interactive session is not available from the Admin CLI. You must access the device
shell in order to run Python applications from the command line. See Authentication groups for
information about configuring authentication groups that include shell access.
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
3. Type Python commands at the Python prompt. For example, to view help for the digidevice
module, type:
>>> help("digidevice")
Help on package digidevice:
NAME
digidevice - Digi device python extensions
DESCRIPTION
This module includes various extensions that allow Python
to interact with additional features offered by the device.
...
4. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
Digidevice module
The Python digidevice module provides platform-specific extensions that allow you to interact with
the device’s configuration and interfaces. The following submodules are included with the digidevice
module:
This section contains the following topics:
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
4. Execute a CLI command using the cli.execute(command) function. For example, to print the
system status and statistics to stdout using the show system command:
>>>
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> help(cli.execute)
Help on function execute in module digidevice.cli:
execute(command, timeout=5)
Execute a CLI command with the timeout specified returning the results.
...
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
n Stream ID
n Value
n (Optional) Data type
l integer
l long
l float
l double
l string
l binary
n Units (optional)
n Timestamp (optional)
n Location (optional)
l Tuple of latitude, longitude and altitude
n Description (optional)
n Quality (optional)
l An integer describing the quality of the data point
For example, to use an interactive Python session to upload datapoints related to velocity,
temperature, and the state of the emergency door:
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
You can also upload multiple datapoints:
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
6. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
Once the datapoints have been uploaded to Remote Manager, they can be viewed via Remote
Manager or accessed using Web Services calls. See the Digi Remote Manager Programmers Guide for
more information on web services and datapoints.
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> help(datapoint.upload)
Help on function upload in module digidevice.datapoint:
timestamp:float=None, units:str=None,
geo_location:Tuple[float, float, float]=None, quality:int=None,
data_type:digidevice.datapoint.DataType=None, timeout:float=None)
...
>>> help(datapoint.upload_multiple)
Help on function upload_multiple in module digidevice.datapoint:
upload_multiple(datapoints:List[digidevice.datapoint.DataPoint],
timeout:float=None)
...
6. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
4. Use config.load() and the get() method to return the device's configuration:
a. Return the entire configuration:
>>> from pprint import pprint # use pprint vs. print to make the
output easier to read
>>> cfg = config.load()
>>> pprint(cfg.dump().splitlines())
...
network.interface.lan1.device=/network/bridge/lan1
network.interface.lan1.enable=true
network.interface.lan1.ipv4.address=192.168.2.1/24
network.interface.lan1.ipv4.connection_monitor.attempts=3
...
Which returns:
192.168.2.1/24
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> cfg.commit()
True
>>>
>>> print(cfg.get("system.name"))
New-Name
>>>
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> help(config)
Help on module acl.config in acl:
NAME
acl.config - Python interface to ACL configuration (libconfig).
...
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
Use Remote Manager's SCI interface to create SCI requests that are sent to your EX50 device, and use
the device_request module to send responses to those requests to Remote Manager.
See the Digi Remote Manager Programmers Guide for more information on SCI.
Task one: Use the device_request module on your EX50 device to create a response
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
5. Register a callbackup function that will be called when the device receives a SCI request from
Remote Manager:
Note Leave the interactive Python session active while completing task two, below. Once you have
completed task two, exit the interactive session by using Ctrl-D. You can also exit the session using
exit() or quit().
Task two: Create and send an SCI request from Digi Remote Manager
The second step in using the device_request module is to create an SCI request that Remote Manager
will forward to the device. For example, you can create in SCI request a the Remote Manager API
explorer:
d. Click Add.
e. Click OK.
3. Click Examples > SCI > Data Service > Send Request.
Code similar to the following will be displayed in the HTTP message body text box:
<sci_request version="1.0">
<data_service>
<targets>
<device id="00000000-00000000-0000FFFF-A83CF6A3"/>
</targets>
<requests>
<device_request target_name="myTarget">
my payload string
</device_request>
</requests>
</data_service>
</sci_request>
Note The value of the target_name parameter in the device_request element must
correspond to the target parameter of the device_request.register function in the Python
script. In this example, the two are the same.
4. Click Send.
Once that the request has been sent to the device, the handler on the device is executed.
n On the device, you will receive the following output:
<sci_reply version="1.0">
<data_service>
<device id="00000000-00000000-0000FFFF-A83CF6A3"/>
<requests>
<device_request target_name="myTarget"
status="0">OK</device_request>
</requests>
</device>
</data_service>
</sci_request>
1. Create a Python application, called showsystem.py, that uses the digidevice.cli module to
create a response containing information about device and the device_request module to
respond with this information to a request from Remote Manager:
2. Upload the showsystem.py application to the /etc/config/scripts directory on two or more Digi
devices. In this example, we will upload it to two devices, and use the same request in Remote
Manager to query both devices.
See Configure scripts to run automatically for information about uploading Python
applications to your device. You can also create the script on the device by using the vi
command when logged in with shell access.
3. For both devices:
a. Configure the device to automatically run the showsystem.py application on reboot, and
to restart the application if it crashes. This can be done from either the WebUI or the
command line:
WebUI
i. Log into the EX50 WebUI as a user with full Admin access rights.
ii. On the menu, click System. Under Configuration, click Device Configuration.
ix. Click Apply to save the configuration and apply the change.
Command line
i. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access
selection menu. Type admin to access the Admin CLI.
ii. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
b. Run the showsystem.py application. You can run the application by either rebooting the
device, or by running it from the shell prompt.
n To reboot the device:
i. From the WebUI:
i. From the main menu, click System.
ii. Click Reboot.
i. From the command line, at the Admin CLI prompt, type:
> reboot
# exit
<sci_request version="1.0">
<data_service>
<targets>
<device id="00000000-00000000-0000FFFF-A83CF6A3"/>
<device id="00000000-00000000-0000FFFF-485740BC"/>
</targets>
<requests>
<device_request target_name="myTarget">
my payload string
</device_request>
</requests>
</data_service>
</sci_request>
7. For the device_request element, replace the value of target_name with showSystem. This
matches the target parameter of the device_request.register function in the showsystem.py
application.
<device_request target_name="showSystem">
8. Click Send.
You should receive a response similar to the following:
<sci_reply version="1.0">
<data_service>
<device id="00000000-00000000-0000FFFF-A83CF6A3"/>
<requests>
<device_request target_name="showSystem" status="0">Model
: Digi EX50
Serial Number : EX50-000068
Hostname : EX50
MAC : 00:40:D0:13:35:36
Timezone : UTC
Current Time : Mon, 13 September 2021 8:04:23
CPU : 1.1
Uptime : 1 day, 21 hours, 49 minutes, 47
seconds (164987s)
Temperature : 39C
Disk
----
Load Average : 0.10, 0.05, 0.00
RAM Usage : 85.176MB/250.484MB(34%)
Disk /etc/config Usage : 0.068MB/13.416MB(1%)
Disk /opt Usage : 47.724MB/5309.752MB(1%)
Disk /overlay Usage : MB/MB(%)
Disk /tmp Usage : 0.004MB/40.96MB(0%)
Disk /var Usage : 0.820MB/32.768MB(3%)</device_
request>
</requests>
</device>
<device id="00000000-00000000-0000FFFF-485740BC"/>
<requests>
<device_request target_name="showSystem" status="0">Model
: Digi EX50
Serial Number : EX50-000023
Hostname : EX50
MAC : 00:40:D0:26:79:1C
Timezone : UTC
Current Time : Mon, 13 September 2021 8:04:23
CPU : 1.1
Uptime : 4 day, 13 hours, 43 minutes, 22
seconds (395002s)
Temperature : 37C
</device>
</data_service>
</sci_request>
Help for using Python to respond to Digi Remote Manager SCI requests
Get help for respond to Digi Remote Manager Server Command Interface (SCI) requests by accessing
help for digidevice.device_request:
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> help(device_request)
Help on module digidevice.device_request in digidevice:
NAME
digidevice.device_request - APIs for registering device request handlers
...
You can also use the help command with available device_request functions:
n Use the help command with device_request.register:
>>> help(device_request.register)
Help on function register in module digidevice.device_request:
>>> help(device_request.unregister)
Help on function unregister in module digidevice.device_request:
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> runt.start()
>>>
5. Use the keys() method to display available keys in the runtime database, and use the get()
method to print information from the runtime database:
a. Print available keys:
>>> print(runt.keys(""))
>>> print(runt.keys("system"))
>>> print(runt.get("system.mac"))
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> runt.start()
>>>
>>> print(runt.get("my-variable"))
my-variable
>>>
>>> runt.stop()
>>>
8. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> help(runt)
NAME
acl.runt - Python interface to ACL runtime database (runtd).
...
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
n If the name is being used by to another device in your Remote Manager account, the name will
be removed from the previous device and added to the new device.
n If Remote Manager is configured to apply a profile to a device based on the device name,
changing the name of the device may cause Remote Manager to automatically push a profile
onto the device.
Together, these two features allow you to swap one device for another by using the name submodule
to change the device name, while guaranteeing that the new device will have the same configuration
as the previous one.
Note Because causing a profile to be automatically pushed from Remote Manager may change the
behavior of the device, including overwriting existing usernames and passwords, the name
submodule should be used with caution. As a result, support for this functionality is disabled by
default on Remote Manager.
Enable support on Digi Remote Manager for uploading custom device names
1. In Remote Manager, click API Explorer.
2. For the HTTP method, select PUT.
3. For Enter and API or select an example, type
/ws/v1/settings/inventory/AllowDeviceToSetOwnNameEnabled.
4. In the HTTP message body text box, type the following:
{
"name" : "AllowDeviceToSetOwnNameEnabled",
"value" : "true"
}
5. Click Send.
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> name.upload("my_name")
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> help(name)
NAME
digidevice.name - API for uploading name from the device
...
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
4. Use the valid_fix object to determine if the device has a valid fix:
>>> loc.position
(44.926195299999998, -93.397084499999999, 292.39999399999999)
>>>
>>> loc.latitude
44.926195299999998
>>>
>>> loc.longitude
-93.397084499999999
>>>
>>> loc.altitude
292.39999399999999
>>>
7. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
44.926195299999998,
-93.397084499999999,
273.20001200000002
]
},
"properties": {
"direction": "None",
"horizontal_velocity": "0.0",
"latitude.deg_min_sec": "44* 54' 45.586\" N",
"longitude.deg_min_sec": "93* 33' 52.334\" W",
"num_satellites": "12",
"quality": "Standard GNSS (2D/3D)",
"selected_source_idx": "0",
"source": "USB (/dev/ttyACM0)",
"source_idx.0.altitude": "273.200012",
"source_idx.0.direction": "None",
"source_idx.0.horizontal_velocity": "0.195489",
"source_idx.0.label": "usb",
"source_idx.0.latitude": "44.902662",
"source_idx.0.latitude.deg_min_sec": "44* 55' 45.065\" N",
"source_idx.0.longitude": "-93.560648",
"source_idx.0.longitude.deg_min_sec": "93* 16' 52.966\" W",
"source_idx.0.num_satellites": "12",
"source_idx.0.quality": "Standard GNSS (2D/3D)",
"source_idx.0.utc_date_time": "Sep-13-2021 8:04:23",
"source_idx.0.vertical_velocity": "0.0",
"source_idx.1.label": "gnss",
"source_idx.1.quality": "No Fix / Invalid",
"state": "Enabled, signal",
"utc_date_time": "Sep-13-2021 8:04:23",
"vertical_velocity": "0.0"
}
}
>>>
6. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
>>> help(location)
Help on module digidevice.location in digidevice:
NAME
digidevice.location - digidevice.location - API for accessing location
data
...
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> maintenance.state()
'IN_SERVICE'
>>>
>>> maintenance.out_of_service()
>>> maintenance.state()
'OUT_OF_SERVICE'
>>>
>>> maintenance.in_service()
>>> maintenance.state()
'IN_SERVICE'
>>>
Note Leave the interactive Python session active while completing task two, below. Once you have
completed task two, exit the interactive session by using Ctrl-D. You can also exit the session using
exit() or quit().
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> help(maintenance )
Help on module digidevice.maintenance in digidevice:
NAME
digidevice.maintenance
DESCRIPTION
API for setting the device's service state. The service state is
stored
in runt.
...
5. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
#!/usr/bin/python
"""
import os
import threading
import sys
from digidevice.sms import Callback, send
COND = threading.Condition()
if __name__ == '__main__':
if len(sys.argv) > 1:
dest = sys.argv[1]
else:
dest = '+15005550006'
# NOTE: The number must include either the + prefix or leading zeros
(e.g, either +15005550006 or 0015005550006).
my_callback = Callback(sms_test_callback, COND)
send_sms("+" + dest, 'Hello World!')
print("Please send an SMS message now.")
print("Execution halted until a message is received or 60 seconds have
passed.")
# acquire the semaphore and wait until a callback occurs
COND.acquire()
try:
COND.wait(60.0)
except Exception as err:
print("exception occured while waiting")
print(err)
COND.release()
my_callback.unregister_callback()
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
# ls /dev/serial/
by-id by-path by-usb port1
#
3. At the shell prompt, use the python command with no parameters to enter an interactive
Python session:
# python
Python 3.6.13 (default, May 9 2021, 22:49:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
5. You can now perform operations on the serial port. For example, to write a message to the
serial port:
6. Use Ctrl-D to exit the Python session. You can also exit the session using exit() or quit().
"""
MQTT client example:
- Reporting some device metrics from runt
- Reporting DHCP clients
- Firmware update feature (simple implementation, read TODO in cmd_fwupdate)
"""
import sys
import time
import paho.mqtt.client as mqtt
import json
from acl import runt, config
from http import HTTPStatus
import urllib.request
import tempfile
import os
from digidevice import cli
POLL_TIME = 60
def cmd_reboot(params):
print("Rebooting unit...")
try:
cli.execute("reboot", 10)
except:
print("Failed to run 'reboot' command")
return HTTPStatus.INTERNAL_SERVER_ERROR
return HTTPStatus.OK
def cmd_fwupdate(params):
try:
fw_uri = params["uri"]
except:
print("Firmware file URI not passed")
return HTTPStatus.BAD_REQUEST
try:
fd, fname = tempfile.mkstemp()
os.close(fd)
try:
urllib.request.urlretrieve(fw_uri, fname)
except:
print("Failed to download FW file from URI {}".format(fw_uri))
return HTTPStatus.NOT_FOUND
try:
ret = cli.execute("system firmware update file " + fname, 60)
except:
print("Failed to run firmware update command")
return HTTPStatus.INTERNAL_SERVER_ERROR
return HTTPStatus.OK
CMD_HANDLERS = {
"reboot": cmd_reboot,
"fw-update": cmd_fwupdate
}
if cmd_path.startswith(PREFIX_CMD):
path = cmd_path[len(PREFIX_CMD):]
else:
reply = {
"cmd": cmd,
"status": status
}
Supported commands:
- "fw-update"
params:
- "uri": "<firmware_file_URL>"
- "reboot"
params:
"""
try:
m = json.loads(msg.payload)
cid = m["cid"]
cmd = m["cmd"]
try:
payload = m["params"]
except:
payload = None
except:
print("Invalid command format: {}".format(msg.payload))
if not cid:
# Return if client-ID not passed
return None
send_cmd_reply(client, msg.topic, cid, cmd, HTTPStatus.BAD_REQUEST)
try:
status = CMD_HANDLERS[cmd](payload)
except:
print("Invalid command: {}".format(cmd))
status = HTTPStatus.NOT_IMPLEMENTED
def publish_dhcp_leases():
leases = []
try:
with open('/etc/config/dhcp.leases', 'r') as f:
for line in f:
elems = line.split()
if len(elems) != 5:
continue
leases.append({"mac": elems[1], "ip": elems[2], "host": elems
[3]})
if leases:
client.publish(PREFIX_EVENT + "/leases", json.dumps(leases,
separators=(',',':')))
except:
print("Failed to open DHCP leases file")
def publish_system():
avg1, avg5, avg15 = runt.get("system.load_avg").split(', ')
ram_used = runt.get("system.ram.per")
disk_opt = runt.get("system.disk./opt.per")
disk_config = runt.get("system.disk./etc/config.per")
msg = json.dumps({
"load_avg": {
"1min": avg1,
"5min": avg5,
"15min": avg15
},
"disk_usage": {
"/opt": disk_opt,
"/etc/config:": disk_config,
"ram": ram_used
}
})
runt.start()
serial = runt.get("system.serial")
client = mqtt.Client()
client.on_connect = on_connect
client.on_message = on_message
try:
client.connect("192.168.1.100", 1883, 60)
client.loop_start()
except:
print("Failed to connect to MQTT server")
sys.exit(1)
while True:
publish_dhcp_leases()
publish_system()
time.sleep(POLL_TIME)
where:
> config
(config)>
(config)> ?
auth Authentication
cloud Central management
firewall Firewall
monitoring Monitoring
network Network
serial Serial
service Services
system System
vpn VPN
(config)>
The allowed values for path are listed in the first (left) column.
4. To determine further allowed path location values by using the ? (question mark) with
the path name:
(config> service ?
Services
Additional Configuration
-------------------------------------------------------------------
------------
dns DNS
iperf IPerf
location Location
mdns Service Discovery (mDNS)
modbus_gateway Modbus Gateway
multicast Multicast
ntp NTP
ping Ping responder
snmp SNMP
ssh SSH
telnet Telnet
web_admin Web administration
(config)> service
You can also use the GET method to return the configuration parameters associated with an item:
where:
n path is the path to the configuration parameter, in dot notation (for example,
ssh.service.enable).
n new_value is the new value for the parameter.
For example, to disable the ssh service using curl:
where path is the path to the list item, including the list number, in dot notation (for example,
service.ssh.acl.zone.4).
For example, to remove the external firewall zone to the ssh service:
1. Use the GET method to determine the SSH service's list number for the external zone:
2. Use the DELETE method to remove the external zone (list item 4).
Default
Feature Description configuration
Idle timeout Determines how long a user session can be idle before the n 10 minutes.
system automatically disconnects.
Allow shell If disabled, prevents all authentication prohibits access to n Enabled.
the shell prompt for all authentication groups. This does not
prevent access to the Admin CLI.
Methods Determines how users are authenticated for access: local n local users.
users, TACACS+, or RADIUS.
Groups Associates access permissions for a group. . You can modify n admin: Provides
the released groups and create additional groups as needed the logged-in
for your site. A user can be assigned to more than one group. user with
administrative
and shell
access.
n serial: Provides
the logged-in
user with access
to serial ports.
Users Defines local users for the EX50. n admin: Belongs
to both the
admin and
serial groups.
TACACS+ Configures support for TACACS+ (Terminal Access Controller n Not configured.
Access-Control System Plus) servers and users.
RADIUS Configures support for RADIUS (Remote Authentication Dial- n Not configured.
In User Service) servers and users.
LDAP Configures support for LDAP (Lightweight Directory Access n Not configured.
Protocol) servers and users.
Serial Configures authentication for serial TCP and autoconnect n Not
services. configured.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
5. Select the appropriate authentication type for the new method from the Method drop-down.
Note Authentication methods are attempted in the order they are listed until the first
successful authentication result is returned. See Rearrange the position of authentication
methods for information about how to reorder the authentication methods.
Command line
Authentication methods are attempted in the order they are listed until the first successful
authentication result is returned. This procedure describes how to add methods to various places in
the list.
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add the new authentication method to the appropriate location in the list:
n To determine the current list of authentication methods:
a. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access
selection menu. Type admin to access the Admin CLI.
b. At the command line, type config to enter configuration mode:
> config
(config)>
c. Use the show auth method command to display the current authentication
methods configuration:
n To add the new authentication method to the beginning of the list, use the index value
of 0 to indicate that it should be added as the first method:
n To add the new authentication method to the end of the list, use the index keyword
end:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Use the show auth method command to determine the index number of the authentication
method to be deleted:
Where n is index number of the authentication method to be deleted. For example, to delete
the TACACS+ authentication method as displayed by the example show command, above:
(config)> save
Configuration saved.
>
WebUI
Authentication methods are reordered by changing the method type in the Method drop-down for
each authentication method to match the appropriate order.
For example, the following configuration has Local users as the first method, and RADIUS as the
second.
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
Authentication groups
Authentication groups are used to assign access rights to EX50 users. Three types of access rights can
be assigned:
n Admin access: Users with Admin access can be configured to have either:
l The ability to manage the EX50 device by using the WebUI or the Admin CLI.
l Read-only access to the WebUI and Admin CLI.
n Shell access: Users with Shell access have the ability to access the shell when logging into the
EX50 via ssh, telnet, or the serial console.
Shell access is not available if the Allow shell parameter has been disabled. See Disable shell
access for more information about the Allow shell parameter.
n Serial access: Users with Serial access have the ability to log into the EX50 device by using the
serial console.
n The admin group is configured by default to have full Admin access and Shell access.
Shell access is not available if the Allow shell parameter has been disabled. See Disable shell
access for more information about the Allow shell parameter.
n The serial group is configured by default to have Serial access.
The preconfigured authentication groups cannot be deleted, but the access rights defined for the
group are configurable.
This section contains the following topics:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n Shell access:
l To enable Shell access for the serial group:
Shell access is not available if the Allow shell parameter has been disabled. See
Disable shell access for more information about the Allow shell parameter.
n Serial access:
l To enable Serial access for the admin group:
(config)> save
Configuration saved.
>
n The access rights to be assigned to users that are assigned to this group.
n Access rights to OpenVPN tunnels, and the tunnels to which they have access.
n Access rights to captive portals, and the portals to which they have access.
n Access rights to query the device for Nagios monitoring.
To add an authentication group:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
5. Click the following options, as appropriate, to enable or disable access rights for each:
n Admin access
For groups assigned Admin access, you can also determine whether the Access level
should be Full access or Read-only access.
where value is either:
l Full access full: provides users of this group with the ability to manage the EX50
device by using the WebUI or the Admin CLI.
l Read-only access read-only: provides users of this group with read-only access to
the WebUI and Admin CLI.
The default is Full access full.
n Shell access
Shell access is not available if the Allow shell parameter has been disabled. See Disable
shell access for more information about the Allow shell parameter.
n Serial access
6. (Optional) Configure OpenVPN access. See for further information.
7. (Optional) Configure captive portal access:
a. Enable captive portal access rights for users of this group by checking the box next to
Captive portal access.
b. Click Captive portals to expand the Captive portal node.
c. For Add Captive portal, click .
d. In the Captive portal dropdown, select a captive portal to which users of this group will
have access.
e. Click again to add additional captive portals.
8. (Optional) Enable users that belong to this group to query the device for Nagios monitoring by
checking the box next to Nagios access.
9. (Optional) Enable users that belong to this group to access the Bluetooth scanning service by
checking the box next to Bluetooth scanner access.
10. (Optional) Enable users that belong to this group to access the Wi-Fi scanning service by
checking the box next to Wi-Fi scanner access.
11. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Use the add auth group command to add a new authentication. For example, to add a group
named test:
Shell access is not available if the Allow shell parameter has been disabled. See Disable
shell access for more information about the Allow shell parameter.
n Serial access:
c. Add a captive portal to which users of this group will have access:
i. Determine available portals:
http redirect
no interface
no message
no redirect_url
no terms
timeout 24h
no title
(config)>
(config)> add auth group test acl portal portals end portal1
(config)>
7. (Optional) Enable users that belong to this group to access the Bluetooth scanning service:
8. (Optional) Enable users that belong to this group to access the Wi-Fi scanning service:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
Local users
Local users are authenticated on the device without using an external authentication mechanism such
as TACACS+ or RADIUS. Local user authentication is enabled by default, with one preconfiged default
user.
Default user
At manufacturing time, each EX50 device comes with a default user configured as follows:
n Username: admin.
n Password: The default password is displayed on the label on the bottom of the device.
Note The default password is a unique password for the device, and is the most critical
security feature for the device. If you reset the device to factory defaults, you must log in using
the default user and password, and you should immediately change the password to a custom
password. Before deploying or mounting the EX50 device, record the default password, so you
have the information available when you need it even if you cannot physically access the label
on the bottom of the device.
The default admin user is preconfigured with both Admin and Serial access. You can configure the
admin user account to fit with the needs of your environment.
This section contains the following topics:
You can also change the password for the active user by clicking the user name in the menu
bar:
The active user must have full Admin access rights to be able to change the password.
6. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Where:
n username is the name of the user.
n pwd is the new password for the user. The password must be at least eight characters
long and must contain at least one uppercase letter, one lowercase letter, one number,
and one special character.
4. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
n A username.
n A password. The password must be at least eight characters long and must contain at least
one uppercase letter, one lowercase letter, one number, and one special character. For
security reasons, passwords are stored in hash form. There is no way to get or display
passwords in clear-text form, although prior to saving the configuration, the password can be
shown by clicking Reveal.
n The authentication group or groups from which the user will inherit access rights. See
Authentication groups for information about configuring groups.
n The number of unsuccessful login attempts before the user is locked out of the system.
n The amount of time that the user is locked out of the system after the specified number of
unsuccessful login attempts.
n An optional public ssh key, to authenticate the user when using passwordless SSH login.
n Two-factor authentication information for user login over SSH, telnet, and the serial console:
l The verification type for two-factor authentication: Either time-based or counter-based.
l The security key.
l Whether to allow passcode reuse (time based verification only).
l The passcode refresh interval (time based verification only).
l The valid code window size.
l The login limit.
l The login limit period.
l One-time use eight-digit emergency scratch codes.
To configure a local user:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Note Every user must be configured with at least one group. You can add multiple groups to a
user by clicking Add again and selecting the next group.
8. (Optional) Add SSH keys for the user to use passwordless SSH login:
a. Click SSH keys.
b. In Add SSH key, paste or type a public encryption key that this user can use for
passwordless SSH login and click .
9. (Optional) Configure two-factor authentication for SSH, telnet, and serial console login:
a. Click Two-factor authentication.
b. Check Enable to enable two-factor authentication for this user.
c. Select the Verification type:
n Time-based (TOTP): Time-based One-Time Password (TOTP) authentication uses
the current time to generate a one-time password.
n Counter-based (HOTP): HMAC-based One-Time Password (HOTP) uses a counter to
validate a one-time password.
d. Generate a Secret key:
i. Click ... next to the field label and select Generate secret key.
ii. Copy the secret key for use with an application or mobile device to generate
passcodes.
e. For time-based verification only, select Disallow code reuse to prevent a code from being
used more than once during the time that it is valid.
f. For time-based verification only, in Code refresh interval, type the amount of time that a
code will remain valid.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}. For example, to set Code refresh interval to ten minutes,
enter 10m or 600s.
g. In Valid code window size, type the allowed number of concurrently valid codes. In cases
where TOTP is being used, increasing the Valid code window size may be necessary when
the clocks used by the server and client are not synchronized.
h. For Login limit, type the number of times that the user is allowed to attempt to log in
during the Login limit period. Set Login limit to 0 to allow an unlimited number of login
attempts during the Login limit period.
i. For Login limit period, type the amount of time that the user is allowed to attempt to log
in.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}. For example, to set Login limit period to ten minutes, enter
10m or 600s.
j. Scratch codes are emergency codes that may be used once, at any time. To add a scratch
code:
i. Click Scratch codes.
ii. For Add Code, click .
iii. For Code, enter the scratch code. The code must be eight digits, with a minimum of
10000000.
iv. Click again to add additional scratch codes.
10. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the user's password. The password must be at least eight characters long and must
contain at least one uppercase letter, one lowercase letter, one number, and one special
character.
a. Set the number of unsuccessful login attempts before the user is locked out of the device.
where value is any integer. The minimum value is 1, and the default value is 5.
b. Set the amount of time that the user is locked out after the number of unsuccessful login
attempts defined in lockout tries:
where value is any number of minutes, or seconds, and takes the format number{m|s}.
For example, to set duration to ten minutes, enter either 10m or 600s:
The minimum value is 1 second, and the maximum is 15 minutes. The default is 15
minutes.
6. Add groups for the user.
Groups define user access rights. See Authentication groups for information about configuring
groups.
a. Add a group to the user. For example, to add the admin group to the user:
7. (Optional) Add SSH keys for the user to use passwordless SSH login:
a. Change to the user's ssh_key node:
b. Add the key by using the ssh_key command and pasting or typing a public encryption key
that this user can use for passwordless SSH login:
8. (Optional) Configure two-factor authentication for SSH, telnet, and serial console login:
a. Change to the user's two-factor authentication node:
f. For time-based verification only, configure the code refresh interval. This is the amount of
time that a code will remain valid.
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set refresh_interval to ten minutes, enter either 10m or 600s:
h. Configure the login limit. This represents the number of times that the user is allowed to
attempt to log in during the Login limit period. Set to 0 to allow an unlimited number of
login attempts during the Login limit period
i. Configure the login limit period. This is the amount of time that the user is allowed to
attempt to log in.
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set login_limit_period to ten minutes, enter either 10m or 600s:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
Note TACACS+ configuration, including filenames and locations, may vary depending on your
platform and installation. This example assumes a Ubuntu installation.
To define users:
1. Open the TACACS+ server configuration file in a text editor. For example:
2. Add users to the file using the following format. This example will create two users, one with
admin and serial access, and one with only serial access.
user = user1 {
name ="User1 for EX50"
pap = cleartext password1
service = system {
groupname = admin,serial
}
}
user = user2 {
name ="User2 for EX50"
pap = cleartext password2
service = system {
groupname = serial
}
}
The groupname attribute is optional. If used, the value must correspond to authentication
groups configured on your EX50. Alternatively, if the user is also configured as a local user on
the EX50 device and the LDAP server authenticates the user but does not return any groups,
the local configuration determines the list of groups. See Authentication groups for more
information about authentication groups. The groupname attribute can contain one group or
multiple groups in a comma-separated list.
3. Save and close the file.
4. Verify that your changes did not introduce any syntax errors:
If successful, this command will echo the configuration file to standard out. If the command
encounters any syntax errors, a message similar to this will display:
n Whether other user authentication methods should be used in addition to the TACACS+ server,
or if the TACACS+ server should be considered the authoritative login method.
n The TACACS+ server port. It is configured to 49 by default.
n Add additional TACACS+ servers in case the first TACACS+ server is unavailable.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
key = testing123
For example, in TACACS+ user configuration, the group attribute in the sample tac_plus.conf
file is groupname, which is also the default setting in the EX50 configuration.
7. (Optional) For Service, type the value of the service attribute in the the TACACS+ server's
configuration. For example, in TACACS+ user configuration, the value of the service attribute in
the sample tac_plus.conf file is system, which is also the default setting in the EX50
configuration.
8. Add TACACS+ to the authentication methods:
a. Click Authentication > Methods.
b. For Add method, click .
c. Select TACACS+ for the new method from the Method drop-down.
Authentication methods are attempted in the order they are listed until the first successful
authentication result is returned. See Rearrange the position of authentication methods for
information about rearranging the position of the methods in the list.
9. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. (Optional) Prevent other authentication methods from being used if TACACS+ authentication
fails. Other authentication methods will only be used if the TACACS+ server is unavailable.
4. (Optional) Configure the group_attribute. This is the name of the attribute used in the TACACS+
server's configuration to identify the EX50 authentication group or groups that the user is a
member of. For example, in TACACS+ user configuration, the group attribute in the sample
tac_plus.conf file is groupname, which is also the default setting for the group_attribute in the
EX50 configuration.
5. (Optional) Configure the type of service. This is the value of the service attribute in the the
TACACS+ server's configuration. For example, in TACACS+ user configuration, the value of the
service attribute in the sample tac_plus.conf file is system, which is also the default setting in
the EX50 configuration.
(config)> save
Configuration saved.
>
...
Configuration appears to be OK
servers are unavailable. Additionally, users who are configured locally but are not configured on the
RADIUS server are still able to log into the device. Authentication methods are attempted in the order
they are listed until the first successful authentication result is returned; therefore if you want to
ensure that users are authenticated first through the RADIUS server, and only authenticated locally if
the RADIUS server is unavailable or if the user is not defined on the RADIUS server, then you should
list the RADIUS authentication method prior to the Local users authentication method.
See User authentication methods for more information about authentication methods.
If the RADIUS servers are unavailable and the EX50 device falls back to local authentication, only users
defined locally on the device are able to log in. RADIUS users cannot log in until the RADIUS servers
are brought back online.
n Whether other user authentication methods should be used in addition to the RADIUS server,
or if the RADIUS server should be considered the authoritative login method.
n The RADIUS server port. It is configured to 1812 by default.
n Add additional RADIUS servers in case the first RADIUS server is unavailable.
n The server NAS ID. If left blank, the default value is used:
l If you are access the EX50 device by using the WebUI, the default value is for NAS ID is
httpd.
l If you are access the EX50 device by using ssh, the default value is sshd.
n Time in seconds before the request to the server times out. The default is 3 seconds and the
maximum possible value is 60 seconds.
n Enable additional debug messages from the RADIUS client.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
secret=testing123
e. For Timeout, type or select the amount of time in seconds to wait for the RADIUS server to
respond. Allowed value is any integer from 3 to 60. The default value is 3.
f. (Optional) Click again to add additional RADIUS servers.
5. (Optional) Enable Authoritative to prevent other authentication methods from being used if
RADIUS authentication fails. Other authentication methods will only be used if the RADIUS
server is unavailable.
6. (Optional) Click RADIUS debug to enable additional debug messages from the RADIUS client.
7. (Optional) For NAS ID, type the unique identifier for this network access server (NAS). You can
use the fully-qualified domain name of the NAS or any arbitrary string. If not set, the default
value is used:
n If you are accessing the EX50 device by using the WebUI, the default value is for
NAS ID is httpd.
n If you are accessing the EX50 device by using ssh, the default value is sshd.
c. Select RADIUS for the new method from the Method drop-down.
Authentication methods are attempted in the order they are listed until the first successful
authentication result is returned. See Rearrange the position of authentication methods for
information about rearranging the position of the methods in the list.
9. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. (Optional) Prevent other authentication methods from being used if RADIUS authentication
fails. Other authentication methods will only be used if the RADIUS server is unavailable.
5. (Optional) Configure the NAS ID. This is a unique identifier for this network access server (NAS).
You can use the fully-qualified domain name of the NAS or any arbitrary string. If not set, the
default value is used:
n If you are accessing the EX50 device by using the WebUI, the default value is for
NAS ID is httpd.
n If you are accessing the EX50 device by using ssh, the default value is sshd.
d. Configure the amount of time in seconds to wait for the RADIUS server to respond. Allowed
value is any integer from 3 to 60. The default value is 3.
(config)> save
Configuration saved.
>
LDAP
Your EX50 device supports LDAP (Lightweight Directory Access Protocol), a protocol used for directory
information services over an IP network. LDAP can be used with your EX50 device for centralized
authentication and authorization management for users who connect to the device. With LDAP
support, the EX50 device acts as an LDAP client, which sends user credentials and connection
parameters to an LDAP server. The LDAP server then authenticates the LDAP client requests and sends
back a response message to the device.
When you are using LDAP authentication, you can have both local users and LDAP users able to log in
to the device. To use LDAP authentication, you must set up a LDAP server that is accessible by the
EX50 device prior to configuration. The process of setting up a LDAP server varies by the server
environment.
This section contains the following topics:
$ gedit ./add_user.ldif
dn: uid=john,dc=example,dc=com
objectClass: inetOrgPerson
cn: John Smith
sn: Smith
uid: john
userPassword: password
ou: admin serial
n The value of uid and userPassword must correspond to the username and password
used to log into the EX50 device.
n The ou attribute is optional. If used, the value must correspond to authentication
groups configured on your EX50. Alternatively, if the user is also configured as a local
user on the EX50 device and the LDAP server authenticates the user but does not return
any groups, the local configuration determines the list of groups. See Authentication
groups for more information about authentication groups.
Other attributes may be required by the user’s objectClass. Any objectClass may be used as
long it allows the uid, userPassword, and ou attributes.
3. Save and close the file.
4. Add the user to the OpenLDAP server:
5. Verify that the user has been added by performing an LDAP search:
n Whether other user authentication methods should be used in addition to the LDAP server, or if
the LDAP server should be considered the authoritative login method.
n The LDAP server port. It is configured to 389 by default.
n Whether to use Transport Layer Security (TLS) when communicating with the LDAP server.
n The distinguished name (DN) and password used to communicate with the server.
n The distinguished name used to search to user base.
n The group attribute.
n The number of seconds to wait to receive a message from the server.
n Add additional LDAP servers in case the first LDAP server is unavailable.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
6. For TLS connection, select the type of TLS connection used by the server:
n Disable TLS: Uses a non-secure TCP connection on the LDAP standard port, 389.
n Enable TLS: Uses an SSL/TLS encrypted connection on port 636.
n Start TLS: Makes a non-secure TCP connection to the LDAP server on port 389, then
sends a request to upgrade the connection to a secure TLS connection. This is the
preferred method for LDAP.
7. If Enable TLS or Start TLS are selected for TLS connection:
n Leave Verify server certificate at the default setting of enabled to verify the server
certificate with a known Certificate Authority.
n Disable Verify server certificate if the server is using a self-signed certificate.
8. (Optional) For Server login, type a distinguished name (DN) that is used to bind to the LDAP
server and search for users, for example cn=user,dc=example,dc=com. Leave this field blank
if the server allows anonymous connections.
9. (Optional) For Server password, type the password used to log into the LDAP server. Leave
this field blank if the server allows anonymous connections.
10. For User search base, type the distinguished name (DN) on the server to search for users. This
can be the root of the directory tree (for example, dc=example,dc=com) or a sub-tree (for
example. ou=People,dc=example,dc=com).
11. For Login attribute, enter the user attribute containing the login of the authenticated user. For
example, in the LDAP user configuration, the login attribute is uid. If this attribute is not set,
the user will be denied access.
12. (Optional) For Group attribute, type the name of the user attribute that contains the list of
EX50 authentication groups that the authenticated user has access to. See LDAP user
configuration for further information about the group attribute.
13. For Timeout, type or select the amount of time in seconds to wait for the LDAP server to
respond. Allowed value is between 3 and 60 seconds.
14. Add LDAP to the authentication methods:
a. Click Authentication > Methods.
b. For Add method, click .
c. Select LDAP for the new method from the Method drop-down.
Authentication methods are attempted in the order they are listed until the first successful
authentication result is returned. See Rearrange the position of authentication methods for
information about rearranging the position of the methods in the list.
15. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. (Optional) Prevent other authentication methods from being used if LDAP authentication fails.
Other authentication methods will only be used if the LDAP server is unavailable.
For example:
7. Set the password used to log into the LDAP server. Leave this option unset if the server allows
anonymous connections.
8. Set the distinguished name (DN) on the server to search for users. This can be the root of the
directory tree (for example, dc=example,dc=com) or a sub-tree (for example.
ou=People,dc=example,dc=com).
where value is the user attribute containing the login of the authenticated user. For example,
in the LDAP user configuration, the login attribute is uid. . If this attribute is not set, the user
will be denied access.
10. (Optional) Set the name of the user attribute that contains the list of EX50 authentication
groups that the authenticated user has access to. See LDAP user configuration for further
information about the group attribute.
For example:
11. Configure the amount of time in seconds to wait for the LDAP server to respond.
(config)> save
Configuration saved.
>
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
where:
n CA-cert-name is the name of the certificate for the custom certificate authority.
n cert-and-private-key is the certificate and private key for the custom certificate
authority.
Repeat for additional custom certificate authorities.
7. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
Note If shell access is disabled, re-enabling it will erase the device's configuration and perform a
factory reset.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
3. Click Authentication.
4. Click to disable Allow shell.
Note If shell access is disabled, re-enabling it will erase the device's configuration and perform
a factory reset.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
Note If shell access is disabled, re-enabling it will erase the device's configuration and perform
a factory reset.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
3. Click Authentication.
4. For Idle timeout, enter the amount of time that the active session can be idle before the user
is automatically logged out.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Idle timeout to ten minutes, enter 10m or 600s.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set idle_timeout to ten minutes, enter either 10m or 600s:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. Create the user. In this example, the user is being created with the username adminuser:
1. The user is authenticated by the RADIUS server. If the RADIUS server is unavailable,
2. The user is authenticated by the TACACS+ server. If both the RADIUS and TACACS+ servers are
unavailable,
3. The user is authenticated by the EX50 device using local authentication.
This example uses a FreeRadius 3.0 server running on ubuntu, and a TACACS+ server running on
ubuntu. Server configuration may vary depending on the platforms or type of servers used in your
environment.
WebUI
1. Configure a user on the RADIUS server:
a. On the ubuntu machine hosting the FreeRadius server, open the /etc/freeradius/3.0/users
file:
$ sudo gedit /etc/freeradius/3.0/users
In this example:
n The user's username is admin1.
n The user's password is password1.
n The authentication group on the EX50 device, admin, is identified in the Unix-FTP-
Group-Names parameter.
c. Save and close the users file.
2. Configure a user on the TACACS+ server:
a. On the ubuntu machine hosting the TACACS+ server, open the /etc/tacacs+/tac_plus.conf
file:
$ sudo gedit /etc/tacacs+/tac_plus.conf
user = admin1 {
name ="Admin1 for TX64"
pap = cleartext password1
service = system {
groupname = admin
}
}
}
In this example:
n The user's username is admin1.
n The user's password is password1.
n The authentication group on the EX50 device, admin, is identified in the
groupname parameter.
c. Save and close the tac_plus.conf file.
3. Log into the EX50 WebUI as a user with full Admin access rights.
4. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Configure a user on the RADIUS server:
a. On the ubuntu machine hosting the FreeRadius server, open the /etc/freeradius/3.0/users
file:
$ sudo gedit /etc/freeradius/3.0/users
In this example:
n The user's username is admin1.
n The user's password is password1.
n The authentication group on the EX50 device, admin, is identified in the Unix-FTP-
Group-Names parameter.
c. Save and close the users file.
user = admin1 {
name ="Admin1 for TX64"
pap = cleartext password1
service = system {
groupname = admin
}
}
}
In this example:
n The user's username is admin1.
n The user's password is password1.
n The authentication group on the EX50 device, admin, is identified in the
groupname parameter.
c. Save and close the tac_plus.conf file.
3. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
4. At the command line, type config to enter configuration mode:
> config
(config)>
This output indicates that on this example system, only local authentication is configured.
b. Add RADIUS authentication to the beginning of the list:
Firewall configuration
Firewall configuration includes the following configuration options:
n Zones: A zone is a firewall access group to which network interfaces can be added. You then
use zones to configure packet filtering and access control lists for interfaces that are included
in the zone. Preconfigured zones include:
l Any: Matches any network interface, even if they are not assigned to this zone.
l Loopback: Zone for interfaces that are used for communication between processes
running on the device.
l Internal: Used for interfaces connected to trusted networks. By default, the firewall will
allow most access from this zone.
l External: Used for interfaces to connect to untrusted zones, such as the internet. This zone
has Network Address Translation (NAT) enabled by default. By default, the firewall will
block most access from this zone.
l Edge: Used for interfaces connected to trusted networks, where the device is a client on
the edge of the network rather than a router or gateway.
l Setup: Used for interfaces involved in the initial setup of the device. By default, the firewall
will only allow this zone to access administration services.
l IPsec: The default zone for IPsec tunnels.
l Dynamic routes: Used for routes learned using routing services.
n Port forwarding: A list of rules that allow network connections to the EX50 to be forwarded to
other servers by translating the destination address.
n Packet filtering: A list of packet filtering rules that determine whether to accept or reject
network connections that are forwarded through the EX50.
n Custom rules: A script that is run to install advanced firewall rules beyond the
scope/capabilities of the standard device configuration.
n Quality Of Service: Quality of Service (QOS) options for bandwidth allocation and policy-
based traffic shaping and prioritizing.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
5. (Optional) If traffic on this zone will be forwarded from a private network to the internet,
enable Network Address Translation (NAT).
6. Click Apply to save the configuration and apply the change.
See Configure the firewall zone for a network interface for information about how to configure
network interfaces to use a zone.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add the new zone. For example, to add a zone named my_zone:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Use the del command to delete a custom firewall rule. For example:
(config)> save
Configuration saved.
>
n A white list of devices, based on either IP address or firewall zone, that are authorized to
leverage this forwarding rule.
To configure a port forwarding rule:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Port forwarding rules are enabled by default. To disable, click to toggle off Enable.
5. (Optional) Type a Label that will be used to identify the rule.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
Network connections will only be forwarded if their destination address matches the IP
address of this network interface.
5. Set the IP version. Allowed values are ipv4 and ipv6. The default is ipv4.
6. Set the public-facing port number that network connections must use for their traffic to be
forwarded.
Network connections will only be forwarded if they match the selected protocol. Allowed
values are custom, tcp, tcpudp, or upd. The default is tcp.
9. Set the public-facing port number(s) that network connections must use for their traffic to be
forwarded.
where value is the port number, comma-separated list of port numbers, or range of port
numbers on the server to which traffic should be forwarded. For example, to forward traffic to
ports one, three, and five through ten, enter 1, 3, 5-10.
10. (Optional) To create a white list of devices that are authorized to leverage this forwarding rule,
based on either the IP address or firewall zone, change to the acl node:
Additional Configuration
-------------------------------------------------------------------
-----------
any
dynamic_routes
edge
external
hotspot
internal
ipsec
loopback
setup
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Determine the index number of the port forwarding rule you want to delete:
to_address6 10.10.10.10
to_port 10001
1
acl
no address6
no zone
enable false
interface lan
ip_version ipv6
label IPv6 port forwarding rule
port 10002
protocol tcp
to_address6 c097:4533:bd63:bb12:9a6f:5569:4b53:c29a
to_port 10003
(config)>
4. To delete the rule, use the index number with the del command. For example:
(config)> save
Configuration saved.
>
Packet filtering
By default, there are two preconfigured packet filtering rules:
n Allow all outgoing traffic: Monitors traffic going to and from the EX50 device. The predefined
settings are intended to block unauthorized inbound traffic while providing an unrestricted
flow of outgoing data.
n Allow Hotspot to External: Allows traffic that uses the hotspot firewall zone to be forwarded
to interfaces that use the External zone. You should not modify this packet filtering rule.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
n To edit the default packet filtering rule or another existing packet filtering rule, click to
expand the rule.
The packet filtering rule configuration window is displayed.
Packet filters are enabled by default. To disable, click to toggle off Enable.
4. (Optional) Type a Label that will be used to identify the rule.
5. For Action, select one of:
n Accept: Allows matching network connections.
n Reject: Blocks matching network connections, and sends an ICMP error if appropriate.
n Drop: Blocks matching network connections, and does not send a reply.
6. Select the IP version.
7. Select the Protocol.
8. For Source zone, select the firewall zone that will be monitored by this rule for incoming
connections from network interfaces that are a member of this zone.
See Firewall configuration for more information about firewall zones.
9. For Destination zone, select the firewall zone. Packets destined for network interfaces that are
members of this zone will either be accepted, rejected or dropped by this rule.
See Firewall configuration for more information about firewall zones.
10. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
To edit the default packet filtering rule or another existing packet filtering rule:
a. Determine the index number of the appropriate packet filtering rule:
6. Set the destination firewall zone. Packets destined for network interfaces that are members of
this zone will either be accepted, rejected or dropped by this rule.
See Firewall configuration for more information about firewall zones.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. To enable a packet filtering rule, use the index number with the enable true command. For
example:
5. To disable a packet filtering rule, use the index number with the enable false command. For
example:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Determine the index number of the packet filtering rule you want to delete:
4. To delete the rule, use the index number with the del command. For example:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. (Optional) Instruct the device to override all preconfigured firewall behavior and rely solely on
the custom firewall rules:
5. Set the shell command that will execute the custom firewall rules script:
(config)> save
Configuration saved.
>
n Outbound provides an example of matching packets as they are routed from the device onto
the WAN interface.
n Inbound provides an example of matching packets as they are routed from the device onto a
LAN interface.
These example bindings are disabled by default.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
4. Set the interface for the binding. Use the index number of the binding; for example, to set the
interface for the Outbound binding:
a. Use the ? to determine available interfaces:
5. Examine the remaining default settings and modify as appropriate for your network.
6. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
New QoS binding policies are enabled by default. To disable, click Enable.
c. (Optional) Type a Label for the binding policy.
d. For Weight, type a value for the amount of available bandwidth allocated to the policy,
relative to other policies for this binding.
The larger the weight, with respect to the other policy weights, the larger portion of the
maximum bandwidth is available for this policy. For example, if a binding contains three
policies, and each policy contains a weight of 10, each policy will be allocated one third of
the total interface bandwidth.
e. For Latency, type the maximum delay before the transmission of packets. A lower latency
means that the packets will be scheduled more quickly for transmission.
f. Select Default to identify this policy as a fall-back policy. The fall-back policy will be used
for traffic that is not matched by any other policy. If there is no default policy associated
with this binding, packets that do not match any policy rules will be dropped.
g. If Default is disabled, you must configure at least one rule:
i. Click to expand Rule.
ii. For Add Rule, click .
New QoS binding policy rules are enabled by default. To disable, click Enable.
iii. (Optional) Type a Label for the binding policy rule.
iv. For Type Of Service, type the value of the Type of Service (ToS) packet header that
defines packet priority. If unspecified, this field is ignored.
See https://www.tucny.com/Home/dscp-tos for a list of common TOS values.
v. For Protocol, select the IP protocol matching criteria for this rule.
vi. For Source port, type the port, or any, as a source traffic matching criteria.
vii. For Destination port, type the port, or any, as a destination traffic matching criteria.
viii. Click to expand Source address and select the Type:
n Any: Source traffic from any address will be matched.
n Interface: Only traffic from the selected Interface will be matched.
n IPv4 address: Only traffic from the IP address typed in IPv4 address will be
matched. Use the format IPv4_address[/netmask], or use any to match any
IPv4 address.
n IPv6 address: Only traffic from the IP address typed in IPv6 address will be
matched. Use the format IPv6_address[/prefix_length], or use any to match
any IPv6 address.
n MAC address: Only traffic from the MAC address typed in MAC address will be
matched.
ix. Click to expand Destination address and select the Type:
n Any: Traffic destined for anywhere will be matched.
n Interface: Only traffic destined for the selected Interface will be matched.
n IPv4 address: Only traffic destined for the IP address typed in IPv4 address
will be matched. Use the format IPv4_address[/netmask], or use any to match
any IPv4 address.
n IPv6 address: Only traffic destined for the IP address typed in IPv6 address
will be matched. Use the format IPv6_address[/prefix_length], or use any to
match any IPv6 address.
Repeat to add a new rule. Up to 30 rules can be configured.
10. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a binding:
5. Set the interface to queue egress packets on. The binding will only match traffic that is being
sent out on this interface:
a. Use the ? to determine available interfaces:
6. (Optional) Set the maximum egress bandwidth of the interface, in megabits, allocated to this
binding.
where int is an integer between 1 and 1000. Typically, this should be 95% of the available
bandwidth. The default is 95.
7. Create a policy for the binding:
At least one policy is required for each binding. Each policy can contain up to 30 rules.
a. Change to the policy node of the configuration:
b. Add a policy:
d. Set a value for the amount of available bandwidth allocated to the policy, relative to other
policies for this binding.
The larger the weight, with respect to the other policy weights, the larger portion of the
maximum bandwidth is available for this policy. For example, if a binding contains three
policies, and each policy contains a weight of 10, each policy will be allocated one third of
the total interface bandwidth.
where int is any integer between 1 and 65535. The default is 10.
e. Set the maximum delay before the transmission of packets. A lower number means that
the packets will be scheduled more quickly for transmission.
The fall-back policy will be used for traffic that is not matched by any other policy. If there
is no default policy associated with this binding, packets that do not match any policy
rules will be dropped. If the policy is not a fall-back policy, you must configure at least one
rule:
i. Change to the rule node of the configuration:
iii. (Optional) Set a label for the new binding policy rule:
iv. Set the value of the Type of Service (ToS) packet header that defines packet priority. If
unspecified, this field is ignored.
where value is the IP port number, a range of port numbers using the format IP_port-
IP_port, or any.
vii. Set the destination port to define a destination matching criteria:
where value is the IP port number, a range of port numbers using the format IP_port-
IP_port, or any.
viii. Set the source address type:
n address: Only traffic from the IP address typed in IPv4 address will be
matched. Set the address that will be matched:
n address: Only traffic destined for the IP address typed in IPv4 address will be
matched. Set the address that will be matched:
n address6: Only traffic destined for the IP address typed in IPv6 address will be
matched. Set the address that will be matched:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. From the main menu, click Status. Under Services, click Containers.
3. Click Upload New Container.
4. From your local file system, select the container file in *.tgz format.
You can download a simple example container file, test_lxc.tgz, from the Digi website.
5. Create Configuration is selected by default. This will create a configuration on the device for
the container when it is installed. If deselected, you will need to create the configuration
manually.
6. Click Apply.
7. If Create Configuration was selected when the container was created, click to go to the
container configuration.
See Configure a container for further information about configuring the container.
Configure a container
Required configuration items
n The following configuration options are completed automatically if Create Configuration was
selected when the container was created. See Upload a new LXC container for details:
l Name of the container.
l Enable the container.
l Whether or not the container should use the device's system libraries.
n Determine whether or not the device should including virtual networking capabilities.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
New containers are enabled by default. To disable, or to enable a container if it has been
disabled, click Enable.
5. Clone DAL is enabled by default. This allows the container to use the device's system libraries.
6. Enable Virtual Network if the container should have network access:
a. Select a Network Bridge Device that will provide access to the container.
b. (Optional) Enter a static IP Address and netmask for the container. This must be a valid IP
address for the bridge, or, if left blank, a DHCP server can assign the container an IP
address.
c. (Optional) For Gateway, type the IP address of the network gateway.
7. Click to expand Serial ports to sssign serial ports that the container will have access to.
a. For Add Port, click .
b. For Port, select the serial port.
8. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
5. By default, the container will use the device's system libraries. To disable:
b. Set the network bridge device that will be used to provide network access:
i. Use the ? to determine the available bridges:
7. (Optional) Assign serial ports that the container will have access to:
a. Determine available serial ports:
Serial
Additional Configuration
---------------------------------------------------------------------
----------
port1 Port 1
...
n Non-persistent: Changes made to the container file system will be lost when the container is
stopped.
n Persistent: Changes made to the container file system when not be lost when the container is
stopped.
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, type:
# lxc container_name
lxc #
where container_name is the name of the container as configured on the device. For example:
# lxc test_lxc
lxc #
This will start the container by using /bin/sh -l, which runs the shell and loads the shell profile. The
default shell profile includes an lxc # prompt.
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, type:
# lxc test_lxc -p
lxc #
This will start the container by using /bin/sh -l, which runs the shell and loads the shell profile. The
default shell profile includes an lxc # prompt.
This will run the script from /usr/bin inside the container. If you have /usr/bin/my_python_script.py on
your device's native system, it will be ignored.
lxc # exit
#
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. From the main menu, click Status. Under Services, click Containers.
The Containers status page is displayed.
Command line
1. Log into the EX50 command line as a user with shell access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type shell to access the device shell.
2. At the shell prompt, type:
# lxc
NAME STATE AUTOSTART GROUPS IPV4 IPV6
UNPRIVILEGED
test_lxc RUNNING 0 - 192.168.5.2
fd00:2704::64bf:47ff:fe0a:d616 true
#
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
For example:
9. Click to disable Sandbox. Sandbox restrictions are not necessary when a container is used.
10. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Add a script:
For example:
8. Disable the sandbox. Sandbox restrictions are not necessary when a container is used.
(config)> save
Configuration saved.
>
$ cd rootfs/etc
$
print("Hello world.\n")
$ cd ../..
5. Change user and group permissions on all files in the container file structure:
6. Tar and zip the directory structure to create a new container file:
# lxc python_lxc
lxc #
WebUI
To display system information:
Command line
To display system information, use the show system command.
>
Timezone : UTC
Current Time : Mon, 13 September 2021 8:04:23 +0000
CPU : 1.4%
Uptime : 6 days, 6 hours, 21 minutes, 57 seconds
(541317s)
Load Average : 0.01, 0.03, 0.02
RAM Usage : 119.554MB/1878.984MB(6%)
Temperature : 40C
Disk
----
Load Average : 0.09, 0.10, 0.08
RAM Usage : 127.843MB/1880.421MB(6%)
Disk /etc/config Usage : 18.421MB/4546.371MB(0%)
Disk /opt Usage : -4523.-46MB/549.304MB(-822%)
Disk /overlay Usage : MB/MB(%)
Disk /tmp Usage : 0.007MB/256.0MB(0%)
Disk /var Usage : 1.765MB/256.0MB(1%)
>
Configuration items
n A name for the device.
n The name of a contact for the device.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
3. Click System.
4. For Name, type a name for the device. This name will appear in log messages and at the
command prompt.
5. For Contact, type the name of a contact for the device.
6. For Location, type the location of the device.
7. For Banner, type a banner message that will be displayed when users log into terminal
services on the device.
8. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Set a name for the device. This name will appear in log messages and at the command
prompt.
6. Set the banner for the device. This is displayed when users access terminal services on the
device.
192.168.3.1(config)> save
Configuration saved.
192.168.3.1>
all newly installed devices are updated to that same version. For more information, see the Profiles
section of the Digi Remote Manager User Guide.
Downgrading
Downgrading to an earlier release of the firmware may result in the device configuration being erased.
Update firmware over the air (OTA) from the Digi firmware server
WebUI
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. >Use the system firmware ota check command to determine if new modem firmware is
available on the Digi firmware repository.
3. Use the modem firmware ota list command to list available firmware on the Digi firmware
repository.
> reboot
>
n To perform an OTA firmware update by using a specific version from the Digi firmware
repository, use the version parameter to identify the appropriate firmware version as
determined by using system firmware ota list command. For example:
a. Update the firmware:
> reboot
>
Command line
1. Download the EX50 operating system firmware from the Digi Support FTP site to your local
machine.
2. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
3. Load the firmware image onto the device:
> scp host hostname-or-ip user username remote remote-path local local-
path to local
where:
n hostname-or-ip is the hostname or ip address of the remote host.
n username is the name of the user on the remote host.
n remote-path is the path and filename of the file on the remote host that will be copied
4. Verify that the firmware file has been successfully uploaded to the device:
> ls /etc/config/scripts
-rw-r--r-- 1 root root 37511229 May 16 20:10 EX50-
21.8.24.120.bin
-rw-r--r-- 1 root root 2580 May 16 16:44 accns.json
...
>
5. Update the firmware by entering the update firmware command, specifying the firmware file
name:
6. Reboot the device to run the new firmware image using the reboot command.
> reboot
Rebooting system
>
7. Once the device has rebooted, log into the EX50's command line as a user with Admin access
and verify the running firmware version by entering the show system command.
Hostname : EX50
FW Version : 21.8.24.120
MAC : 0040FF800120
Model : Digi EX50
Current Time : Mon, 13 September 2021 8:04:23 +0000
Uptime : 42 seconds (42s)
>
WebUI
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Duplicate the firmware:
WebUI
1. (Optional) Download the appropriate modem firmware from the Digi repository to your local
machine.
2. Log into the EX50 WebUI as a user with Admin access.
3. From the main menu, click Status > Modems.
4. Click the modem firmware version.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the modem firmware ota check command to determine if new modem firmware is
available on the Digi firmware repository.
>
3. Use the modem firmware ota list command to list available firmware on the Digi firmware
repository.
>
>
n To perform an OTA firmware update by using a specific version from the Digi firmware
repository, use the version parameter to identify the appropriate firmware version as
determined by using modem firmware ota list command. For example::
>
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the modem firmware check command to determine if new modem firmware is available
on local device.
3. Use the modem firmware list command to list available firmware on the EX50 device.
>
4. To perform an firmware update by using a local file, use the version parameter to identify the
appropriate firmware version as determined using the modem firmware check or modem
firmware list command. For example::
-----------------------------
Successfully updated firmware
Modem firmware update complete
>
Note You may want to save your configuration settings to a file before rebooting. See Save
configuration to a file.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. From the main menu, click System.
3. Click Reboot.
> reboot
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
4. For Reboot time, enter the time of the day that the device should reboot, using the format
HH:MM. The device will reboot at this time every day.
If Reboot time is set, but the device is unable to synchronize its time with an NTP server, the
device will reboot after it has been up for 24 hours. See System time for information about
configuring NTP servers. If Reboot window is set, the reboot will occur during a random time
within the reboot window.
5. For Reboot window, enter the maximum random delay that will be added to Reboot Time.
Allowed values are any number of hours, minutes, or seconds, and take the format number
{h|m|s}.
For example, to set parameter name to ten minutes, enter 10m or 600s.
The default is 10m, and the maximum allowed time is 24h.
6. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
where time is the time of the day that the device should reboot, using the format HH:MM. For
example, the set the device to reboot at two in the morning every day:
If reboot_time is set, but the device is unable to synchronize its time with an NTP server, the
device will reboot after it has been up for 24 hours. See System time for information about
configuring NTP servers. If reboot_window is set, the reboot will occur during a random time
within the reboot window.
4. Set the maximum random delay that will be added to reboot_time:
where value is any number of hours, minutes, or seconds, and takes the format number
{h|m|s}.
For example, to set reboot_window to ten minutes, enter either 10m or 600s:
(config)> save
Configuration saved.
>
n Clears all configuration settings. When the device restarts, it uses the factory default
configuration.
n Deletes all user files including Python scripts.
n Clears event and system log files.
Additionally, if the ERASE button is used to erase the configuration, pressing the ERASE button a
second time immediately after the device has rebooted:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click System. Under Configuration, click Configuration Maintenance.
4. Click CONFIRM.
5. After resetting the device:
a. Connect to the EX50 by using the serial port or by using an Ethernet cable to connect the
EX50 LAN port to your PC.
b. Log into the EX50:
User name: Use the default user name: admin.
Password: Use the unique password printed on the bottom label of the device (or the
printed label included in the package).
When you first log into the WebUI or the command line, you will be required the change
the SSIDs and pre-shared keys (passwords) for the preconfigured Wi-Fi access points
before you can save any configuration changes. See Reset default SSIDs and pre-shared
keys for the preconfigured Wi-Fi access points for instructions.
c. (Optional) Reset the default password for the admin account. See Change the default
password for the admin user for further information.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Enter the following:
When you first log into the WebUI or the command line, you will be required the change
the SSIDs and pre-shared keys (passwords) for the preconfigured Wi-Fi access points
before you can save any configuration changes. See Reset default SSIDs and pre-shared
keys for the preconfigured Wi-Fi access points for instructions.
c. (Optional) Reset the default password for the admin account. See Change the default
password for the admin user for further information.
2. Press the ERASE button perform a device reset. The ERASE button has the following modes:
n Configuration reset:
l Press and release the ERASE button .
l The device reboots automatically and resets to factory defaults. This does not
remove any automatically generated certificates and keys.
n Full device reset:
l After the device reboots from the first button press, immediately press and
releasethe ERASE button again.
l The device reboots again and resets to factory defaults, as well as also removing
generated certificates and keys.
3. After resetting the device:
a. Connect to the EX50 by using the serial port or by using an Ethernet cable to connect the
EX50 LAN port to your PC.
b. Log into the EX50:
User name: Use the default user name: admin.
Password: Use the unique password printed on the bottom label of the device (or the
printed label included in the package).
When you first log into the WebUI or the command line, you will be required the change
the SSIDs and pre-shared keys (passwords) for the preconfigured Wi-Fi access points
before you can save any configuration changes. See Reset default SSIDs and pre-shared
keys for the preconfigured Wi-Fi access points for instructions.
c. (Optional) Reset the default password for the admin account. See Change the default
password for the admin user for further information.
You can reset the device to the default configuration without removing scripts, keys, and logfiles by
using the revert command:
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> revert
(config)>
4. Set the password for the admin user prior to saving the changes:
(config)> save
Configuration saved.
>
Note To clear the custom default configuration, press the ERASE button, wait for the device to reboot,
then press the ERASE button again.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. Configure your EX50 device to match the desired custom factory default configuration.
For example, you may want to configure the device to use a custom APN or a particular
network configuration, so that when you reset the device to factory defaults, it will
automatically have your required network configuration.
3. On the main menu, click System. Under Configuration, click Configuration Maintenance.
Do not set a Passphrase for the configuration backup. The file will be downloaded using your
browser's standard download process.
5. After the configuration backup file has been downloaded, rename the file to:
custom-default-config.bin
6. Upload the file to the device:
a. From the main menu, select System > Filesystem.
b. Under Default device configuration, click .
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Enter the following:
3. On the menu, click System again. Ablue circle next to Find Me is blinking, indicating that the
Find Me feature is active.
4. To deactivate the Find Me feature, click System and click Find Me again.
A notification message appears, noting that the LED is no longer flashing on the device. Click
the x in the message to close it.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. To activate the Find Me feature, at the prompt, type the following at the command prompt:
3. To deactivate the Find Me feature, type the following at the command prompt:
4. To determine the status of the Find Me feature, type the following at the command prompt:
Configuration files
The EX50 configuration file, /etc/config/accns.json, contains all configuration changes that have been
made to the device. It does not contain the complete device configuration; it only contains changes to
the default configuration. Both the default configuration and the changes contained in the accns.json
file are applied when the device reboots.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> save
Configuration saved.
>
WebUI
This procedure creates a binary archive file containing the device's configuration, certificates and
keys, and other information.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Enter the following:
where
n path is the location on the EX50's filesystem where the configuration backup file should
be saved.
n passphrase (optional) is a passphrase used to encrypt the configuration backup.
n type is the type of backup, either:
l archive: Creates a binary archive file containing the device's configuration,
certificates and keys, and other information.
l cli-config: Creates a text file containing only the configuration changes.
For example:
> system backup /etc/config/scripts/ type archive
3. (Optional) Use scp to copy the file from your device to another host:
> scp host hostname-or-ip user username remote remote-path local local-
path to remote
where:
n hostname-or-ip is the hostname or ip address of the remote host.
n username is the name of the user on the remote host.
n remote-path is the location on the remote host where the file will be copied.
n local-path is the path and filename on the EX50 device.
For example:
WebUI
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. If the configuration backup is on a remote host, use scp to copy the file from the host to your
device:
> scp host hostname-or-ip user username remote remote-path local local-
path to local
where:
n hostname-or-ip is the hostname or ip address of the remote host.
n username is the name of the user on the remote host.
n remote-path is the path and filename of the file on the remote host that will be copied
to the EX50 device.
n local-path is the location on the EX50 device where the copied file will be placed.
For example:
where
n filepath is the the path and filename of the configuration backup file on the EX50's
filesystem (local-path in the previous step).
n passphrase (optional) is the passphrase to restore the configuration backup, if a
passphrase was used when the backup was created.
For example:
> system restore /opt/backup-archive-0040FF800120-21.8.24.120-
19.23.42.bin
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
n If Check if Python Out-of-Service is set, the maintenance window will only start if the
Python Out-of-Service is set. See Use Python to set the maintenance window for further
information.
7. (Optional) Click to enable Modem firmware update to instruct the system to look for any
updated modem firmware during the maintenance window. If updated firmware is found, it
will then be installed. Modem firmware update looks for updated firmware both on the local
device and over the network, using either a WAN or cellular connection.
8. (Optional) Click to enable Configuration check to allow for the configuration to be updated,
including by custom scripts, during the maintenance window.
9. (Optional) Configure automated checking for device firmware updates:
a. Click to expand Firmware update check.
b. Device firmware update check is enabled by default. This enables to automated
checking for device firmware updates.
c. Modem firmware update check is enabled by default. This enables to automated
checking for modem firmware updates.
d. For Frequency, select how often automated checking for device and modem firmware
should take place. Allowed values are Daily, Weekly, and Monthly. The default is Daily.
10. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n out_of_service: The maintenance window will only start if the Python Out-of-
Service is set.
n time: Configure a time period for the maintenance window:
i. Configure the time of day that the maintenance window should start, using the
syntax HH:MM. If the start time is not set, maintenance tasks are not scheduled
and will not be run.
The behavior of the start time varies depending on the setting of the duration
length, which is configured in the next step.
l If the duration length is set to 0, all scheduled tasks will begin at the exact
time specified in the start time.
l If the duration length is set to 24 hours, the start time is effectively
obsolete and the maintenance tasks will be scheduled to run at any time.
Setting the duration length to 24 hours can potentially overstress the
device and should be used with caution.
l If the duration length is set to any value other than to 0 or 24 hours, the
maintenance tasks will run at a random time during the time allotted for
the duration window.
l If the duration length is set to one or more hours, the minutes field in the
start time is ignored and the duration window will begin at the beginning
of the specified hour.
ii. Configure the duration length (the amount of time that the maintenance tasks
will be run). If 0 is used, all scheduled tasks will begin at the start time, defined
in the previous step.
where value is either true or false. yes or no, and 1 or 0 are also allowed.
6. (Optional) Configure automated checking for device firmware updates:
a. Device firmware update check is enabled by default. This enables to automated
checking for device firmware updates. To disable:
b. Set how often automated checking for device firmware should take place:
(config)> save
Configuration saved.
>
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Disable encryption with the following command:
1. Configure your PC network to connect to the 192.168.210 subnet. For example, on a Windows
PC:
a. Select the Properties of the relevant network connection on the Windows PC.
2. Connect the PC's Ethernet port to the WAN Ethernet port on your EX50 device.
3. Open a telnet session and connect to the EX50 device at the IP address of 192.168.210.1.
4. Log into the device:
n Username: admin
n Password: The default unique password for your device is printed on the device label.
5. At the shell prompt, type:
# rm /etc/config/.nocrypt
# flatfsd -i
This will re-enable encryption and leave the device at its factory default setting.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
where:
n eth_port is the name of the Ethernet port (for example, eth1)
n value is one of:
(config)> save
Configuration saved.
>
intelliFlow 737
Configure NetFlow Probe 744
intelliFlow
intelliFlow monitors system information, network data usage, and traffic information, and displays
the information in a series of charts available in the local WebUI. To use intelliFlow, the EX50 must be
powered on and you must have access to the local WebUI. Once you enable intelliFlow, the Status >
intelliFlow option is available in the main menu. By default, intelliFlow is disabled.
intelliFlow provides charts on the following information:
n System utilisation
n Top data usage by host
n Top data usage by server
n Top data usage by service
n Host data usage over time
intelliFlow charts are dymanic; at any point, you can click inside the chart to drill down to view more
granular information, and menu options allow you to change various aspects of the information being
displayed.
Note When intelliFlow is enabled, it adds an estimated 50MB of data usage for the device by reporting
the metrics to Digi Remote Manager.
Enable intelliFlow
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Enable IntelliFlow:
4. Set the firewall zone. Internal clients that are being monitored by IntelliFlow should be present
on the specified zone:
(config)>
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. If you have not already done so, enable intelliFlow. See Enable intelliFlow.
3. From the menu, click Status > intelliFlow.
The System Utilisation chart is displayed:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. If you have not already done so, enable intelliFlow. See Enable intelliFlow.
3. From the menu, click Status > intelliFlow.
n To display the Top Data Usage by Server chart, click Top Data Usage by Server.
n To display the Top Data Usage by Service chart, click Top Data Usage by Service.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. If you have not already done so, enable intelliFlow. See Enable intelliFlow.
3. From the menu, click Status > intelliFlow.
4. Click Host Data Usage Over Time.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
n Random—Randomly selects one out of every n flows, where n is the value of Flow
sampler population.
n Hash—Randomly selects one out of every n flows using the hash of the flow key, where
n is the value of Flow sampler population.
7. For Flow sampler population, if you selected a flow sampler, enter the number of flows for
the sampler. Allowed value is any number between 2 and 16383. The default is 100.
8. For Inactive timeout, type the the number of seconds that a flow can be inactive before sent
to a collector. Allowed value is any number between 1 and 15. The default is 15.
9. For Active timeout, type the number of seconds that a flow can be active before sent to a
collector. Allowed value is any number between 1 and 1800. The default is 1800.
10. For Maximum flows, type the maximum number of flows to probe simultaneously. Allowed
value is any number between 0 and 2000000. The default is 2000000.
11. Add collectors:
a. Click to expand Collectors.
b. For Add Collector, click .
c. (Optional) Type a Label for the collector.
d. For Address, type the IP address of the collector.
e. (Optional) For Port, enter the port number used by the collector. The default is 2055.
Repeat to add additional collectors.
12. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. Enable NetFlow:
where value is any number between 2 and 16383. The default is 100.
6. Set the number of seconds that a flow can be inactive before sent to a collector:
where value is any is any number between 1 and 15. The default is 15.
7. Set the number of seconds that a flow can be active before sent to a collector:
where value is any is any number between 1 and 1800. The default is 1800.
8. Set the maximum number of flows to probe simultaneously:
where value is any is any number between 0 and 2000000. The default is 2000000.
9. Add collectors:
a. Add a collector:
n Disable the Digi Remote Manager connection if it is not required. You can also configure an
alternate cloud-based central management application.
n Change the reconnection timer.
n The non-cellular keepalive timeout.
n The cellular keepalive timeout.
n The keepalive count before the Remote Manager connection is dropped.
n SMS support.
n HTTP proxy server support.
To configure Digi Remote Manager:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Digi Remote Manager support is enabled by default. To disable, click Enable central
management.
4. (Optional) For Service, select either Digi Remote Manager or Digi aView. The default is Digi
Remote Manager.
5. (Optional) For Management server, type the URL for the central management server. The
default is the Digi Remote Manager server, my.devicecloud.com.
6. (Optional) For Management port, type the destination port for the remote cloud services
connection. The default is 3199.
7. (Optional) For Retry interval, type the amount of time that the EX50 device should wait before
reattempting to connect to remote cloud services after being disconnected. The default is 30
seconds.
Allowed values are any number of hours, minutes, or seconds, and take the format number
{h|m|s}.
For example, to set Retry interval to ten minutes, enter 10m or 600s.
8. (Optional) For Keep-alive interval, type the amount of time that the EX50 device should wait
between sending keep-alive messages to remote cloud services when using a non-cellular
interface. The default is 60 seconds.
Allowed values are any number of hours, minutes, or seconds, and take the format number
{h|m|s}.
For example, to set Keep-alive interval to ten minutes, enter 10m or 600s.
9. (Optional) For Cellular keep-alive interval, type the amount of time that the EX50 device
should wait between sending keep-alive messages to remote cloud services when using a
cellular interface. The default is 290 seconds.
Allowed values are any number of hours, minutes, or seconds, and take the format number
{h|m|s}.
For example, to set Cellular keep-alive interval to ten minutes, enter 10m or 600s.
10. (Optional) For Allowed keep-alive misses, type the number of allowed keep-alive misses. The
default is 3.
11. Enable watchdog is used to monitor the connection to remote cloud services. If the
connection is down, you can configure the device to restart the connection, or to reboot. The
watchdog is enabled by default.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> config
(config)>
3. Digi Remote Manager support is enabled by default. To disable Digi Remote Manager support:
6. (Optional) Set the amount of time that the EX50 device should wait before reattempting to
connect to the remote cloud services after being disconnected. The minimum value is ten
seconds. The default is 30 seconds.
where value is any number of hours, minutes, or seconds, and takes the format number
{h|m|s}.
For example, to set the retry interval to ten minutes, enter either 10m or 600s:
7. (Optional) Set the amount of time that the EX50 device should wait between sending keep-
alive messages to the Digi Remote Manager when using a non-cellular interface. Allowed
values are from 30 seconds to two hours. The default is 60 seconds.
where value is any number of hours, minutes, or seconds, and takes the format number
{h|m|s}.
For example, to set the keep-alive interval to ten minutes, enter either 10m or 600s:
8. (Optional) Set the amount of time that the EX50 device should wait between sending keep-
alive messages to the Digi Remote Manager when using a cellular interface. Allowed values are
from 30 seconds to two hours. The default is 290 seconds.
where value is any number of hours, minutes, or seconds, and takes the format number
{h|m|s}.
For example, to set the cellular keep-alive interval to ten minutes, enter either 10m or 600s:
9. Set the number of allowed keep-alive misses. Allowed values are any integer between 2 and
64. The default is 3.
10. The watchdog is used to monitor the connection to remote cloud services. If the connection is
down, you can configure the device to restart the connection, or to reboot. The watchdog is
enabled by default. To disable:
The minimum value is 30 minutes and the maximum is 48 hours. If not set, this option is
disabled. The default is 30 minutes.
b. (Optional) Set the amount of time to wait before rebooting the device, once the
connection to the remote cloud servicesis down. By default, this option is not set, which
means that the option is disabled.
where value is any number of hours, minutes, or seconds, and takes the format number
{h|m|s}.
For example, to set reboot_timeout to ten minutes, enter either 10m or 600s:
The minimum value is 30 minutes and the maximum is 48 hours. If not set, this option is
disabled. The default is disabled.
12. (Optional) Determine whether to require a login and password to authenticate the user from
the remote cloud services CLI:
If set to false, no login prompt will be presented and the user will be logged in as admin. The
default is false.
13. (Optional) Configure the EX50 device to communicate with remote cloud services by using
SMS:
a. Enable SMS messaging:
1. (Optional) Configure the EX50 device to communicate with remote cloud services by using an
HTTP proxy server:
a. Enable the use of an HTTP proxy server:
c. (Optional) Set the port number on the proxy server that the device should connect to. The
default is 2138.
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n To disable:
4. The interval between health sample uploads is set to 60 minutes by default. To change:
where value is one of 1, 5, 15, 30, or 60, and represents the number of minutes between
uploads of health sample data.
5. By default, the device will only report health metrics values to Digi Remote Manager that have
changed health metrics were last uploaded. This is useful to reduce the bandwidth used to
report health metrics. This is useful to reduce the bandwidth used to report health metrics.
Even if enabled, all metrics are uploaded once every hour.
To disable:
When disabled, all metrics are uploaded every Health sample interval.
6. (Optional) Tuning parameters allow to you configure what data are uploaded to the Digi
Remote Manager. By default, all tuning parameters are enabled.
To view a list of all available tuning parameters, use the show command:
To disable a tuning parameter, set its value to false. For example, to turn off all reporting for
the serial port:
(config)> save
Configuration saved.
>
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
n To disable:
4. The interval between event log uploads is set to 60 minutes by default. To change:
where value is one of 1, 5, 15, 30, or 60, and represents the number of minutes between
uploads of health sample data.
5. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
1. If you have not already done so, click here to sign up for a Digi Remote Manager account.
2. Check your email for Digi Remote Manager login instructions.
3. Go to remotemanager.digi.com.
4. Log into your Digi Remote Manager account.
1. If you have not already done so, connect to your Digi Remote Manager account.
2. Click Device Management to display a list of your devices.
3. Click Devices to display a list of your devices.
4. Use the Filter bar to locate the device you want to manage.
5. Use the Search bar to locate the device you want to manage.
6. Select the device and click Properties to view general information for the device.
WebUI
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
(config)> cancel
>
To view the status of your device's connection to Remote Manager, use the show cloud command at
the command line:
Command line
Status : Connected
Server : my.devicecloud.com
Device ID : 00000000-00000000-0040FFFF-FF0F4594
>
The Device ID is the unique identifier for the device, as used by the Remote Manager.
1. Using the EX50 local WebUI, configure one EX50 router to use as the model configuration for all
subsequent EX50s you need to manage.
2. Register the configured EX50 device in your Digi Remote Manager account.
3. In Digi Remote Manager, create a profile based on the configured EX50.
4. Apply the profile to the EX50 devices you need to configure.
Digi Remote Manager provides multiple methods for applying profiles to registered devices. You can
also include site-specific settings with a profile to override settings on a device-by-device basis.
Learn more
n For information on using Digi Remote Manager to configure and manage EX50 routers, see the
Digi Remote Manager User Guide.
n For information on using Digi Remote Manager APIs to develop custom applications, see the
Digi Remote Manager Programmer Guide.
n /tmp
n /opt
n /etc/config
Files stored in the /tmp directory do not persist across reboots. Therefore, /tmp is a good location to
upload temporary files, such as files used for firmware updates. Files stored in /opt and /etc/config do
persist across reboots, but are deleted if a factory reset of the system is performed. See Erase device
configuration and reset to factory defaults for more information.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click System. Under Administration, click File System.
3. Highlight a directory and click to open the directory and view the files in the directory.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type ls /path/dir_name. For example, to display the contents of the
/etc/config directory:
> ls /etc/config
-rw-r--r-- 1 root root 856 Nov 20 20:12 accns.json
drw------- 2 root root 160 Sep 23 04:02 analyzer
drwxr-xr-x 3 root root 224 Sep 23 04:02 cc_acl
-rw-r--r-- 1 root root 47 Sep 23 04:02 dhcp.leases
...
>
Create a directory
Command line
This procedure is not available through the WebUI. To make a new directory, use the mkdir
command, specifying the name of the directory.
For example:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type mkdir /path/dir_name. For example, to create a directory
named temp in /etc/config:
> ls /etc/config
...
-rw-r--r-- 1 root root 1436 Aug 12 21:36 ssl.crt
-rw------- 1 root root 3895 Aug 12 21:36 ssl.pem
-rw-r--r-- 1 root root 10 Aug 5 06:41 start
drwxr-xr-x 2 root root 160 Aug 25 17:49 temp
>
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type more /path/filename. For example, to view the contenct of the
file accns.json in /etc/config:
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type cp /path/filename|dir_name /path[filename]|dir_name. For
example:
Command line
To rename a file named test.py in /etc/config/scripts to final.py:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click System. Under Administration, click File System.
3. Highlight the directory containing the file to be deleted and click to open the directory.
4. Highlight the file to be deleted and click .
5. Click OK to confirm.
Command line
To delete a file named test.py in /etc/config/scripts:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type:
> rm /etc/config/scripts/test.py
rm: remove '/etc/config/scripts/test.py'? yes
>
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
> rm /opt/temp/
rm: descend into directory '/opt/temp'? yes
rm: remove directory '/opt/temp'? yes
>
Upload files
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click System. Under Administration, click File System.
3. Highlight the directory to which the file will be uploaded and click to open the directory.
4. Click (upload).
5. Browse to the location of the file on your local machine. Select the file and click Open to
upload the file.
Download files
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click System. Under Administration, click File System.
3. Highlight the directory to which the file will be uploaded and click to open the directory.
4. Highlight the appropriate file and click (download).
> scp host hostname-or-ip user username remote remote-path local local-path to
local
where:
> scp host hostname-or-ip user username remote remote-path local local-path to
remote
where:
$ sftp [email protected]
Password:
Connected to 192.168.2.1
sftp> put EX50-21.8.24.120
Uploading EX50-21.8.24.120 to EX50-21.8.24.120
EX50-21.8.24.120
100% 24M 830.4KB/s 00:00
sftp> exit
$
$ sftp [email protected]
Password:
Connected to 192.168.2.1
sftp> get test.py
Fetching test.py to test.py
test.py
100% 254 0.3KB/s 00:00
sftp> exit
$
Perform a speedtest
To perform a speedtest:
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the speedtest command to generate the report:
4. To change the size of the speedtest packet, use the size parameter:
5. By default, the speedtest uses nuttcp for the mode. You can change this to iperf with the mode
parameter:
WebUI
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use the system support-report command to generate the report:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click System > Logs.
3. Limit the display in the system log by using the Find search tool.
4. Use filters to configure the types of information displayed in the system logs.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Use show log at the Admin CLI prompt:
Timestamp Message
-------------- ---------------------------------------------------------
----
Nov 26 21:54:34 EX50 netifd: Interface 'interface_wan' is setting up now
Nov 26 21:54:35 EX50 firewalld[621]: reloading status
...
>
3. (Optional) Use the show log number num command to limit the number of lines that are
displayed. For example, to limit the log to the most recent ten lines:
Timestamp Message
-------------- ---------------------------------------------------------
----
Nov 26 21:54:34 EX50 netifd: Interface 'interface_wan' is setting up now
Nov 26 21:54:35 EX50 firewalld[621]: reloading status
...
>
4. (Optional) Use the show log filter value command to limit the number of lines that are
displayed. Allowed values are critical, warning, info, and debug. For example, to limit the
event list to only info messages:
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the main menu, click System > Logs.
3. Click System Logs to collapse the system logs viewer, or scroll down to Events.
4. Click Events to expand the event viewer.
5. Limit the display in the event log by using the Find search tool.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
3. (Optional) Use the show event number num command to limit the number of lines that are
displayed. For example, to limit the event list to the most recent ten lines:
4. (Optional) Use the show event table value command to limit the number of lines that are
displayed. Allowed values are error, info, and status. For example, to limit the event list to
only info messages:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
Log servers are enabled by default. To disable, click to toggle off Enable.
c. Type the host name or IP address of the Server.
d. Select the event categories that will be sent to the server. By default, all event categories
are enabled. You can disable logging for error, informational, and status event categories
by clicking to toggle off the category.
e. For Syslog egress port, type the port number to use for the syslog server. The default is
514.
f. For Protocol, select the IP protocol to use for communication with the syslog server.
Available options are TCP and UPD. The default is UPD.
5. Click Apply to save the configuration and apply the change.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
d. The event categories that will be sent to the server are automatically enabled when the
server is enabled.
n To disable informational event messages:
where value is any integer between 1 and 65535. The default is 514.
5. Set the IP protocol to use for communication with the syslog server:
(config)> save
Configuration saved.
>
n The heartbeat interval, which determines the amount of time to wait before sending a
heartbeat event if no other events have been sent, is set to 30 minutes.
n All event categories are enabled.
To change or disable the heartbeat interval, or to disable event categories, and to perform other log
configuration:
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
4. (Optional) To change the Heartbeat interval from the default of 30 minutes, type a new value.
The heartbeat interval determines the amount of time to wait before sending a heartbeat
event if no other events have been sent.
Allowed values are any number of weeks, days, hours, minutes, or seconds, and take the
format number{w|d|h|m|s}.
For example, to set Heartbeat interval to ten minutes, enter 10m or 600s.
To disable the Heartbeat interval, enter 0s.
5. (Optional) To disable event categories, or to enable them if they have been disabled:
a. Click to expand Event Categories.
b. Click an event category to expand.
c. Depending on the event category, you can enable or disable informational events, status
events, and error events. Some categories also allow you to set the Status interval, which
is the time interval between periodic status events.
6. (Optional) See Configure syslog servers for information about configuring remote syslog
servers to which log messages will be sent.
7. Enable Preserve system logs to save the current session's system log after a reboot.
By default, the EX50 device erases system logs each time the device is powered off or
rebooted.
Note You should only enable Preserve system logs temporarily to debug issues. Once you are
finished debugging, immediately disable Preserve system logs to avoid unnecessary wear to
the flash memory.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. (Optional) To change the heartbeat interval from the default of 30 minutes, set a new value.
The heartbeat interval determines the amount of time to wait before sending a heartbeat
event if no other events have been sent.
where value is any number of weeks, days, hours, minutes, or seconds, and takes the format
number{w|d|h|m|s}.
For example, to set the heartbeat interval to ten minutes, enter either 10m or 600s:
Note You should only enable Preserve system logs temporarily to debug issues. Once you are
finished debugging, immediately disable Preserve system logs to avoid unnecessary wear to
the flash memory.
5. (Optional) To disable event categories, or to enable them if they have been disabled:
a. Use the question mark (?) to determine available event categories:
Additional Configuration
---------------------------------------------------------------------
----------
arping ARP ping
config Configuration
dhcpserver DHCP server
firmware Firmware
location Location
modem Modem
netmon Active recovery
network Network interfaces
openvpn OpenVPN
portal Captive portal
remote Remote control
restart Restart
serial Serial
sms SMS commands
speed Speed
stat Network statistics
user User
wireless WiFi
wol Wake-On-LAN
b. Depending on the event category, you can enable or disable informational events, status
events, and error events. Some categories also allow you to set the status interval, which
is the time interval between periodic status events. For example, to configure DHCP server
logging:
i. Use the question mark (?) to determine what events are available for DHCP server
logging configuration:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set the status interval to ten minutes, enter either 10m or 600s:
6. (Optional) See Configure syslog servers for information about configuring remote syslog
servers to which log messages will be sent.
7. Save the configuration and apply the change:
(config)> save
Configuration saved.
>
Note Data traffic is captured to RAM and the captured data is lost when the device reboots unless you
save the data to a file. See Save captured data traffic to a file.
WebUI
1. Log into the EX50 WebUI as a user with full Admin access rights.
2. On the menu, click System. Under Configuration, click Device Configuration.
4. For Add Capture settings, type a name for the capture filter and click .
You can select from preconfigured filters to determine which types of packets to capture
or ignore, or you can create your own Berkeley packet filter expression.
b. To create a filter that either captures or ignores packets from a particular IP address or
network:
i. Click to expand Filter IP addresses or networks.
ii. Click to add an IP address/network.
iii. For IP address or network, type the IPv4 or IPv6 address (and optional netmask).
iv. For Source or destination IP address, select whether the filter should apply to
packets when the IP address/network is the source, the destination, or both.
v. Click Ignore this IP address or network if the filter should ignore packets from this
IP address/network. By default, is option is disabled, which means that the filter will
capture packets from this IP address/network.
vi. Click to add additional IP address/network filters.
c. To create a filter that either captures or ignores packets that use a particular IP protocol:
i. Click to expand Filter IP protocols.
ii. Click to add an IP protocol.
iii. For IP protocol to capture or ignore, select the protocol. If Other protocol is
selected, type the number of the protocol.
iv. Click Ignore this protocol if the filter should ignore packets that use this protocol. By
default, is option is disabled, which means that the filter will capture packets that use
this protocol.
v. Click to add additional IP protocols filters.
d. To create a filter that either captures or ignores packets from a particular port:
i. Click to expand Filter TCP/UDP port.
ii. Click to add a TCP /UDP port.
iii. For IP TCP/UDP port to capture or ignore, type the number of the port to be
captured or ingored.
iv. For TCP or UDP port, select the type of transport protocol.
v. For Source or destination TCP/UDP port, select whether the filter should apply to
packets when the port is the source, the destination, or both.
vi. Click Ignore this TCP/UDP port if the filter should ignore packets that use this port.
By default, is option is disabled, which means that the filter will capture packets that
use this port.
vii. Click to add additional port filters.
e. To create a filter that either captures or ignores packets from one or more specified MAC
addresses:
i. Click to expand Filter Ethernet MAC addresses.
ii. Click to add a MAC address.
iii. For Ethernet MAC address, type the MAC address to be captured or ingored.
iv. For Source or destination Ethernet MAC address, select whether the filter should
apply to packets when the Ethernet MAC address is the source, the destination, or
both.
v. Click Ignore this MAC address if the filter should ignore packets that use this port. By
default, is option is disabled, which means that the filter will capture packets that use
this port.
vi. Click to add additional MAC address filters.
f. To create a filter that either captures or ignores packets from one or more VLANs:
i. Click to expand Filter VLANs.
ii. Click to add a VLAN.
iii. For The VLAN to capture or ignore, type the number of the VLAN.
iv. Click Ignore this VLAN if the filter should ignore packets that use this port. By default,
is option is disabled, which means that the filter will capture packets that use this
port.
v. Click to add additional VLAN filters.
g. For Berkeley packet filter expression, type a filter using Berkeley Packet Filter (BPF)
syntax. See Example filters for capturing data traffic for examples of filters using BPF
syntax.
6. Add one or more interface to the capture filter:
a. Click to expand Device.
b. Click to add an interface to the capture setting instance.
Command line
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
iii. Set whether the filter should apply to packets when the IP address/network is the
source, the destination, or both:
By default, is option is set to false, which means that the filter will capture packets
from this IP address/network.
v. Repeat these steps to add additional IP address filters.
b. To create a filter that either captures or ignores packets that use a particular IP protocol:
i. Add a new IP protocol filter:
ii. Use the ? to determine available protocols and the appropriate format:
iv. If other is set for the protocol, set the number of the protocol:
where value is an integer between 1 and 255 and represents the the number of the
protocol.
v. (Optional) Set the filter should ignore packets from this protocol:
By default, is option is set to false, which means that the filter will capture packets
from this protocol.
vi. Repeat these steps to add additional protocol filters.
c. To create a filter that either captures or ignores packets from a particular port:
i. Add a new port filter:
ii. Set the transport protocol that should be filtered for the port:
By default, is option is set to false, which means that the filter will capture packets
from this port.
where value is the MAC address to be filtered, using colon-hexadecimal notation with
lower case, for example, 00:aa:11:bb:22:cc.
iii. Set whether the filter should apply to packets when the MAC address is the source,
the destination, or both:
By default, is option is set to false, which means that the filter will capture packets
from this MAC address.
v. Repeat these steps to add additional MAC addresses.
e. To create a filter that either captures or ignores packets from one or more specified VLANs:
i. Add a new VLAN filter:
iii. (Optional) Set the filter should ignore packets from this VLAN:
By default, is option is set to false, which means that the filter will capture packets
from this MAC address.
iv. Repeat these steps to add additional VLANs.
f. To create a filter using Berkeley Packet Filter (BPF) syntax:
where value is a filter using Berkeley Packet Filter (BPF) syntax. Values that contain spaces
must be enclosed in double quotes (").
See Example filters for capturing data traffic for examples of filters using BPF syntax.
6. (Optional) Schedule the analyzer to run, using this capture filter, based on a specified event or
at a particular time:
a. Enable scheduling for this capture filter:
b. Set the mode that will be used to run the capture filter:
where value is any number of weeks, days, hours, minutes, or seconds, and takes
the format number{w|d|h|m|s}.
For example, to set on_interval to ten minutes, enter either 10m or 600s:
n set_time: Runs the script at a specified time of the day. If set_time is set, set the
time that the script should run, using the format HH:MM:
n maintenance_time: The script will run during the system maintenance time
window.
c. Set the amount of time that the scheduled analyzer session will run:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set duration to ten minutes, enter either 10m or 600s:
where value is any number of weeks, days, hours, minutes, or seconds, and takes the
format number{w|d|h|m|s}.
For example, to set save_interval to ten minutes, enter either 10m or 600s:
(config)> save
Configuration saved.
>
ip host 192.168.1.1
ip proto protocol
where protocol is a number in the range of 1 to 255 or one of the following keywords: icmp,
icmp6, igmp, pim, ah, esp, vrrp, udp, or tcp.
n Capture traffic to and from a TCP port 80:
n Capture to and from IP host 10.0.0.1 but filter out ports 22 and 80:
n A configured packet capture. See Configure packet capture for the network analyzer for packet
capture configuration information.
To start packet capture from the command line:
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Type the following at the Admin CLI prompt:
where capture_filter is the name of a packet capture configuration. See Configure packet
capture for the network analyzer for more information.
To determine available packet capture configurations, use the ?:
Note Data traffic is captured to RAM and the captured data is lost when the device reboots unless you
save the data to a file. See Save captured data traffic to a file.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Type the following at the Admin CLI prompt:
where capture_filter is the name of a packet capture configuration. See Configure packet
capture for the network analyzer for more information.
To determine available packet capture configurations, use the ?:
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Type the following at the Admin CLI prompt:
00 40 ff 80 01 20 b4 b6 86 21 b5 73 08 00 45 00 .@... ..
.!.s..E.
00 28 3d 36 40 00 80 06 14 bc 0a 0a 4a 82 0a 0a .(=6@... ....J..
4a 48 cd ae 00 16 a4 4b ff 5f ee 1f d8 23 50 10 JH.....K
._...#P.
08 02 c7 40 00 00 00 00 00 00 00 00 ...@.... ....
Ethernet Header
Destination MAC Addr : 00:40:D0:13:35:36
Source MAC Addr : fb:03:53:05:11:2f
Ethernet Type : IP (0x0800)
IP Header
IP Version : 4
>
where capture_filter is the name of a packet capture configuration. See Configure packet
capture for the network analyzer for more information.
To determine available packet capture configurations, use the ?:
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
where:
n filename is the name of the file that the captured data will be saved to.
Determine filenames already in use:
Use the tab autocomplete feature to determine filenames that are currently in use:
The file is stored in the /etc/config/analyzer directory. To transfer the file to your PC, see Download
captured data to your PC.
WebUI
1. Log into the EX50 WebUI as a user with Admin access.
2. On the menu, click System. Under Administration, click File System.
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Type scp to use the Secure Copy program to copy the file to your PC:
> scp host hostname-or-ip user username remote remote-path local local-
path to remote
where:
n hostname-or-ip is the hostname or ip address of the remote host.
n username is the name of the user on the remote host.
n remote-path is the location on the remote host where the file will be copied.
n local-path is the path and filename on the EX50 device.
For example:
To download the traffic saved in the file /etc/config/analyzer/eth0.pcpng to a PC with the IP
192.168.210.2, for a user named maria, to the /home/maria directory:
[email protected]'s password:
eth0.pcpng 100% 11KB 851.3KB/s
00:00
Command line
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. Type the following at the Admin CLI prompt:
where capture_filter is the name of a packet capture configuration. See Configure packet
capture for the network analyzer for more information.
To determine available packet capture configurations, use the ?:
Note You can remove data traffic saved to a file using the rm command.
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, type the ping command followed by the host name or IP address of
the server to be pinged:
Example
This example shows using traceroute to verify that the EX50 device can route to host 8.8.8.8
(www.google.com) through the default gateway. The command output shows that 15 routing hops
were required to reach the host:
1. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the Admin CLI prompt, use the traceroute command to view IP routing information:
By entering a whois command on a Unix device, the output shows that the route is as follows:
RF exposure statement
In order to comply with RF exposure limits established in the ANSI C95.1 standards, the distance
between the antenna or antennas and the user should not be less than 20 cm.
Maximum transmit
Frequency bands power
13 overlapping channels at 22 MHz or 40 MHz wide spaced at 5 MHz 651.784 mW
Centered at 2.412 MHz to 2.472 MHz
165 overlapping channels at 22 MHz or 40 MHz or 80 MHz wide spaced at 351.295 mW
5 MHz
Centered at 5180 MHz to 5825 MHz
Safety notices
n Read all instructions before installing and powering the router. You should keep these
instructions in a safe place for future reference.
n If the power supply shows signs of damage or malfunction, stop using it immediately, turn off
the power and disconnect the power supply before contacting your supplier for a repair or
replacement.
n Changes or modifications not expressly approved by the party responsible for compliance
could void the user’s authority to operate the equipment. Use only the accessories,
attachments, and power supplies provided by the manufacturer-connecting non-approved
antennas or power supplies may damage the router, cause interference or create an electric
shock hazard, and will void the warranty.
n Do not attempt to repair the product. The router contains no electronic components that can
be serviced or replaced by the user. Any attempt to service or repair the router by the user will
void the product warranty.
n Ports that are capable of connecting to other apparatus are defined as SELV ports. To ensure
conformity with IEC60950 ensure that these ports are only connected to ports of the same type
on other apparatus.
Wireless routers receive and transmit radio frequency energy when power is on.
Interference can occur when using the router close to TV sets, radios,
computers or inadequately shielded equipment. Follow any special regulations
and always power off your router wherever forbidden or when it may cause
interference or danger.
SOS IMPORTANT! Wireless routers operate using radio signals and cellular
networks cannot be guaranteed to connect in all possible conditions. Therefore,
never rely solely upon any wireless device for life critical communications.
This product contains high quality materials and components which can be
recycled. At the end of its life this product MUST NOT be mixed with other
commercial waste for disposal. Check with the terms and conditions of your
supplier for disposal information.
English
Bulgarian--бъ л га рс ки
Croatian--Hrvatski
French--Français
Greek--Ε λλην ικά
Hungarian--Magyar
Italian--Italiano
Latvian--Latvietis
Lithuanian--Lietuvis
Polish--Polskie
Portuguese--Português
Slovak--Slovák
Slovenian--Esloveno
Spanish--Español
Ensure that the power cord is connected to a socket-outlet with earthing connection.
This appliance does not contain any user-serviceable parts. Never open the equipment. For
safety reasons, the equipment should be opened only by qualified personnel.
The unit must be powered off where blasting is in progress, where explosive atmospheres
are present, or near medical or life support equipment. Do not power on the unit in any
aircraft.
For ambient temperatures above 60° C, this equipment must be installed in a Restricted
Access Location only.
У в е ре т е с е , ч е з а х ра нв а щ ия т ка бе л е с в ъ рз а н къ м конт а кт с ъ с
з а з е м ит е л на в ръ з ка .
У ре дъ т т ря бв а да с е из кл юч и т а м , къ де т о с е из в ъ рш в а в з рив я в а не , къ де т о
им а е кс пл оз ив на а т м ос ф е ра ил и в бл из ос т до м е дицинс ко оборудв а не ил и
оборудв а не з а поддъ ржа не на жив от а . Н е в кл юч в а йт е ус т ройс т в от о в
с а м ол е т .
Ovaj uređaj ne sadrži dijelove koje korisnik može servisirati. Nikada ne otvarajte opremu. Iz
sigurnosnih razloga opremu bi trebalo otvarati samo kvalificirano osoblje.
Uređaj se mora isključiti tamo gdje je u tijeku miniranje, gdje su prisutne eksplozivne
atmosfere ili u blizini medicinske opreme ili opreme za održavanje života. Nemojte
uključivati jedinicu ni u jednom zrakoplovu.
Za okolne temperature iznad 60 ° C, ova oprema mora biti instalirana samo na mjestu s
ograničenim pristupom.
Assurez-vous que le cordon d'alimentation est connecté à une prise de courant avec mise à
la terre.
Pour se conformer aux limites d'exposition RF FCC/IC, une distance de séparation d'au
moins 20 cm doit être maintenue entre toute antenne de l'unité et toute partie de
l'utilisateur à tout moment.
Cet appareil ne contient aucune pièce réparable par l'utilisateur. Ne jamais ouvrir
l'équipement. Pour des raisons de sécurité, l'équipement ne doit être ouvert que par du
personnel qualifié.
L'unité doit être éteinte là où le dynamitage est en cours, où des atmosphères explosives
sont présentes, ou à proximité d'équipements médicaux ou de survie. N'allumez pas
l'appareil dans un avion.
Pour des températures ambiantes supérieures à 60 °C, cet équipement doit être installé
uniquement dans un emplacement à accès restreint.
Α υτ ή η σ υσ κευή δεν περ ιέχ ει εξ αρ τ ήματ α που μπορ ούν ν α επισ κευασ τ ούν από
τ ο χ ρ ήσ τ η. Μην αν οίγ ετ ε ποτ έ τ ον εξ οπλισ μό. Γ ια λόγ ους ασ φαλείας , ο
εξ οπλισ μός πρ έπει ν α αν οίγ ει μόν ο από εξ ειδικευμέν ο πρ οσ ωπικό.
Η λειτ ουρ γ ία αυτ ού τ ου εξ οπλισ μού σ ε οικισ τ ικό περ ιβάλλον μπορ εί ν α
πρ οκαλέσ ει παρ εμβολές ρ αδιοφών ου.
Assicurarsi che il cavo di alimentazione sia collegato ad una presa con messa a terra.
Per rispettare i limiti di esposizione RF FCC/IC è necessario mantenere sempre una distanza
di separazione di almeno 20 cm tra qualsiasi antenna dell'unità e qualsiasi parte
dell'utente.
Questo apparecchio non contiene parti riparabili dall'utente. Non aprire mai
l'apparecchiatura. Per motivi di sicurezza, l'apparecchiatura deve essere aperta solo da
personale qualificato.
L'unità deve essere spenta dove sono in corso esplosioni, dove sono presenti atmosfere
esplosive o vicino ad apparecchiature mediche o di supporto vitale. Non accendere l'unità
in nessun aereo.
Per temperature ambiente superiori a 60° C, questa apparecchiatura deve essere installata
solo in un luogo ad accesso limitato.
Šajā ierīcē nav nevienas lietotāja apkalpojamas daļas. Nekad neatveriet aprīkojumu.
Drošības apsvērumu dēļ aprīkojumu drīkst atvērt tikai kvalificēts personāls.
Iekārtai jābūt izslēgtai, ja notiek spridzināšana, sprādzienbīstama vide vai medicīnas vai
dzīvības uzturēšanas aprīkojuma tuvumā. Nevienā lidmašīnā neieslēdziet ierīci.
Kad būtų laikomasi FCC / IC radijo dažnių apšvitos ribų, tarp bet kurios įrenginio antenos ir
bet kurios vartotojo dalies visada turi būti išlaikytas bent 20 cm atstumas.
Šiame prietaise nėra naudotojui prižiūrimų dalių. Niekada neatidarykite įrangos. Saugumo
sumetimais įrangą turėtų atidaryti tik kvalifikuotas personalas.
Įrenginys turi būti išjungtas ten, kur vyksta sprogdinimas, sprogi aplinka arba šalia
medicinos ar gyvybės palaikymo įrangos. Neįjunkite įrenginio jokiuose orlaiviuose.
Esant aukštesnei nei 60 ° C aplinkos temperatūrai, ši įranga turi būti montuojama tik riboto
patekimo vietoje.
Aby zachować zgodność z limitami ekspozycji FCC/IC RF, między anteną urządzenia a
jakąkolwiek częścią użytkownika musi być zachowana odległość co najmniej 20 cm.
To urządzenie nie zawiera żadnych części, które mogą być naprawiane przez użytkownika.
Nigdy nie otwieraj urządzenia. Ze względów bezpieczeństwa urządzenie powinno być
otwierane wyłącznie przez wykwalifikowany personel.
Certifique-se de que o cabo de alimentação esteja conectado a uma tomada com conexão
de aterramento.
Este aparelho não contém peças cuja manutenção possa ser feita pelo usuário. Nunca abra
o equipamento. Por razões de segurança, o equipamento deve ser aberto apenas por
pessoal qualificado.
A unidade deve ser desligada onde houver detonações em andamento, onde houver
presença de atmosferas explosivas ou próximo a equipamentos médicos ou de suporte à
vida. Não ligue a unidade em nenhuma aeronave.
Para temperaturas ambientes acima de 60 ° C, este equipamento deve ser instalado apenas
em locais de acesso restrito.
Aby boli dodržané limity vystavenia vysokofrekvenčným lúčom FCC / IC, musí byť medzi
anténou jednotky a akoukoľvek časťou používateľa neustále udržiavaná vzdialenosť
najmenej 20 cm.
Jednotka musí byť vypnutá tam, kde prebiehajú trhacie práce, kde je prítomné výbušné
prostredie, alebo v blízkosti lekárskych prístrojov alebo zariadení na podporu života.
Jednotku nezapínajte v žiadnom lietadle.
Pri teplotách okolia nad 60 ° C musí byť toto zariadenie inštalované iba na mieste s
obmedzeným prístupom.
Da bi izpolnili omejitve izpostavljenosti FCC / IC RF, mora biti med katero koli anteno enote
in katerim koli delom uporabnika ves čas vzdrževana najmanj 20 cm razdalja.
Enoto je treba izklopiti tam, kjer poteka razstreljevanje, kjer so prisotne eksplozivne
atmosfere ali v bližini medicinske opreme ali opreme za vzdrževanje življenja. Enote ne
vklopite v nobenem letalu.
Pri temperaturah okolice nad 60 ° C mora biti ta oprema nameščena samo na lokaciji z
omejenim dostopom.
Asegúrese de que el cable de alimentación esté conectado a una toma de corriente con
conexión a tierra.
Para cumplir con los límites de exposición a RF de la FCC / IC, se debe mantener una
distancia de separación de al menos 20 cm entre cualquier antena de la unidad y cualquier
parte del usuario en todo momento.
Este aparato no contiene ninguna pieza que pueda reparar el usuario. Nunca abra el
equipo. Por razones de seguridad, el equipo debe ser abierto únicamente por personal
calificado.
La unidad debe estar apagada donde se estén realizando explosiones, cuando haya
atmósferas explosivas o cerca de equipos médicos o de soporte vital. No encienda la
unidad en ningún avión.
Command line
1. Connect to the EX50 device by using a serial connection, SSH or telnet, or the Terminal in the
WebUI or the Console in the Digi Remote Manager. See Access the command line interface for
more information.
n For serial connections, the default configuration is:
l 115200 baud rate
l 8 data bits
l no parity
l 1 stop bit
l no flow control
n For SSH and telnet connections, the default IP address of the device is192.168.210.1 on
the .
2. At the login prompt, enter the username and password of a user with Admin access:
login: admin
Password: **********
The default username is admin. The default unique password for your device is printed on the
device label.
3. Depending on the device configuration, you may be presented with another menu, for
example:
a: Admin CLI
s: Shell
q: Quit
Connecting now...
Press Tab to autocomplete commands
Press '?' for a list of commands and details
Type 'help' for details on navigating the CLI
Type 'exit' to disconnect from the Admin CLI
>
See Command line interface for detailed instructions on using the command line interface.
Command line
1. At the command prompt, type exit.
> exit
2. Depending on the device configuration, you may be presented with another menu, for
example:
a: Admin CLI
s: Shell
q: Quit
EX50 login:
3. Log into the EX50 command line as a user with Admin access.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
The Admin CLI prompt appears.
>
> help
Commands
------------------------------------------------------------------------------
-
? Show commands help
<Tab> Tab completion, displays all valid commands to complete command,
if only one command is possible, it is used
<Space> Like tab except shortest prefix is used if command is valid
<Enter> Enter an input. If quoting then a new line is created instead. If
the input is invalid then characters will be deleted until a
prefix for a valid command is found.
Ctrl + A Move cursor to start of line
Ctrl + E Move cursor to end of line
Ctrl + W Delete word under cursor until start of line or [\',", ,\,/,.]
Ctrl + R If the current input is invalid then characters will be deleted
until a prefix for a valid command is found.
Ctrl + left Jump cursor left until start of line or [\',", ,\,/,.]
Ctrl + right Jump cursor right until start of line or [\',", ,\,/,.]
>
> ?
Commands
------------------------------------------------------------------------------
-
config View and modify the configuration
exit Exit the CLI
analyzer Analyzer commands.
cp Copy a file or directory.
help Show CLI editing and navigation commands.
ls List a directory.
mkdir Create a directory.
modem Modem commands.
more View a file.
mv Move a file or directory.
ping Ping a host.
reboot Reboot the system.
rm Remove a file or directory.
scp Copy a file or directory over SSH.
show Show instance statistics.
system System commands.
>
1. To display further information about the show command, type either show ? or show help:
> show ?
Commands
------------------------------------------------------------------------
--
> show
Use the Tab key or the space bar to display abbreviated help
When executed from the root command prompt, pressing the Tab key or the space bar displays an
abbreviated list of available commands:
Similar behavior is available with any command name:
n Command names. For example, typing net<Tab> auto-completes the command as network.
n Parameter names. For example:
l ping hostname int<Tab> auto-completes the parameter as interface.
l system b<Tab> auto-completes the parameter as backup.
n Parameter values, where the value is one of an enumeration or an on|off type; for example:
auto-completes to
Available commands
The following commands are available from the Admin CLI prompt:
Command Description
config Used to view and modify the configuration.
See Device configuration using the command line interface for more information
about using the config command.
exit Exits the CLI.
cp Copies a file or directory.
help Displays:
n CLI editing and navigation commands, when executed from the root of the
Admin CLI prompt.
n Available commands, syntax diagram, and parameter information, when
executed in conjunction with another command.
See Display help for commands and parameters for information about the help
command.
ls Lists the contents of a directory.
mkdir Creates a directory.
modem Executes modem commands.
more Displays the contents of a file.
mv Moves a file or directory.
ping Pings a remote host using Internet Control Message Protocol (ICMP) Echo Request
messages.
reboot Reboots the EX50 device.
rm Removes a file.
scp Uses the secure copy protocol (SCP) to transfer files between the EX50 device and a
remote host.
See Use the scp command for information about using the scp command.
show Displays information about the device and the device's configuration.
See Display status and statistics using the show command for more information
about the show command.
system Issues commands related to system functionality.
traceroute Sends and tracks route packets to a destination host.
update Updates the device firmware.
Note For commands that operate on the EX50's file system, such as the cp, ls, and mkdir commands,
see File system for information about the file system, including how to copy, move and delete files
and directories.
> scp host hostname-or-ip user username remote remote-path local local-path to
local
where:
> scp host hostname-or-ip user username remote remote-path local local-path to
remote
where:
show config
The show config command displays all the configuration settings for the device that have been
changed from the default settings. This is a particularly useful when troubleshooting the device.
>
show system
The show system command displays system information and statistics for the device, including CPU
usage.
>
show network
The show network command displays status and statistics for network interfaces.
>
n Execute the config command and parameters at the root prompt. See Execute configuration
commands at the root Admin CLI prompt for more information.
n Enter configuration mode by executing the config command without any parameters. See
Configuration mode for more information.
Note When the config command is executed at the root prompt, certain configuration actions that
are available in configuration mode cannot be performed. This includes validating configuration
changes, canceling and reverting configuration changes, and performing actions on elements in lists.
See Configuration mode for information about using configuration mode.
Display help for the config command from the root Admin CLI
prompt
Display additional configuration commands, as well as available parameters and values, by entering
the question mark (?) character after the config command.
1. For example:
> config ?
> config ?
Additional Configuration
-------------------------------------------------------------------------
-
application Custom scripts
auth Authentication
cloud Central management
firewall Firewall
monitoring Monitoring
network Network
serial Serial
service Services
system System
vpn VPN
> config
2. You can then display help for the additional configuration commands. For example, to display
help for the config service command:
Additional Configuration
-------------------------------------------------------------------------
-
dns DNS
mdns Service Discovery (mDNS)
multicast Multicast
ntp NTP
remote_control Remote control
snmp SNMP
ssh SSH
telnet Telnet
web_admin Web administration
Additional Configuration
-------------------------------------------------------------------------
-
acl Access control list
mdns
4. Lastly, display the allowed values and other information for the enable parameter:
Configuration mode
Configuration mode allows you to perform multiple configuration tasks and validate the changes prior
to saving them. You can cancel all changes without saving them at any time. Configuration changes
do not take effect until the configuration is saved.
> config
(config)>
When the command line is in configuration mode, the prompt will change to include (config), to
indicate that you are currently in configuration mode.
(config)> service
(config service)>
See Move within the configuration schema for more information about moving within the
configuration.
(config)> save
Configuration saved.
>
After using save to save changes to the configuration, you will automatically exit configuration mode.
To return to configuration mode, type config again.
(config)> cancel
>
After using cancel to discard unsaved changes to the configuration, you will automatically exit
configuration mode.
Configuration actions
In configuration mode, configuration actions are available to perform tasks related to saving or
canceling the configuration changes, and to manage items and elements in lists. The commands can
be listed by entering a question mark (?) at the config prompt.
The following actions are available:
(config)> ?
(config)> ?
Additional Configuration
------------------------------------------------------------------------
--
application Custom scripts
auth Authentication
cloud Central management
firewall Firewall
monitoring Monitoring
network Network
serial Serial
service Services
system System
vpn VPN
(config)>
2. You can then display help for the additional configuration commands. For example, to display
help for the config service command, use one of the following methods:
n At the config prompt, enter service ?:
(config)> service ?
(config)> service
(config service)>
(config service)> ?
config> service ?
Services
Additional Configuration
------------------------------------------------------------------------
--
dns DNS
mdns Service Discovery (mDNS)
multicast Multicast
ntp NTP
remote_control Remote control
snmp SNMP
ssh SSH
telnet Telnet
web_admin Web administration
(config)> service
3. Next, to display help for the service ssh command, use one of the following methods:
n At the config prompt, enter service ssh ?:
(config)> service
(config service)>
port 22 Port
Additional Configuration
------------------------------------------------------------------------
--
acl Access control list
mdns
4. Lastly, to display allowed values and other information for the enable parameter, use one of
the following methods:
n At the config prompt, enter service ssh enable ?:
(config)> service
(config service)>
n Move forward one node in the configuration by entering the name of an Additional
Configuration option:
(config)> service
(config service)>
You can also enter multiple nodes at once to move multiple steps in the configuration:
n Move backward one node in the configuration by entering two periods (..):
You can also move back multiples nodes in the configuration by typing multiple sets of two
periods:
n Move to the root of the config prompt from anywhere within the configuration by entering
three periods (...):
2. Add an authentication method by using the add index_item command. For example:
n To add the TACACS+ authentication method to the beginning of the list, use the index
number 0:
n To add the TACACS+ authentication method to the end of the list, use the end keyword:
1. Use the show command to verify that the user is not currently a member of any groups:
2. Use the end keyword to add the admin group to the user's configuration:
3. Use the show command again to verify that the admin group has been added to the user's
configuration:
2. Delete one of the authentication methods by using the del index_number command. For
example:
a. To delete the local authentication method, use the index number 0:
b. Use the show command to verify that the local authentication method was removed:
2. To configure the device to use TACACS+ authentication first to authenticate a user, use the
move index_number_1 index_number_2 command:
After executing the revert command, you must save the configuration changes by using the save
command. You can also discard the configuration changes by using the cancel command.
CAUTION! The revert command reverts all changes to the default configuration, not only
unsaved changes.
(config)> revert
(config)>
2. Set the password for the admin user prior to saving the changes:
(config)> save
Configuration saved.
>
n Enter the revert command with the path parameter. For example, to revert all changes to the
authentication methods configuration:
1. Enter the revert command with the path set to auth method:
(config)> save
Configuration saved.
>
n Move to the location in the configuration and enter the revert command without the path
parameter. For example:
1. Change to the auth method node:
(config)> auth
(config auth)>
1. Log into the EX50 command line as a user with full Admin access rights.
Depending on your device configuration, you may be presented with an Access selection
menu. Type admin to access the Admin CLI.
2. At the command line, type config to enter configuration mode:
> config
(config)>
3. At the config prompt, create a new user with the username user1:
n Method one: Create a user at the root of the config prompt:
(config)> auth
(config auth)>
admin
acl
admin
enable true
nagios
enable false
openvpn
enable false
no tunnels
portal
enable false
no portals
serial
enable false
no ports
shell
enable false
serial
acl
admin
enable true
nagios
enable false
openvpn
enable false
no tunnels
portal
enable false
no portals
serial
enable true
ports
0 port1
shell
enable false
(config auth user user1)>
analyzer
Analyzer commands.
Parameters
name
Name of the capture filter to use.
Syntax: STRING
Parameters
filename
The filename to save captured traffic to. The file will be saved to the device's /etc/config/analyzer
directory.
Syntax: STRING
name
Name of the capture filter to use.
Syntax: STRING
Parameters
name
Name of the capture filter to use.
Syntax: STRING
Parameters
name
Name of the capture filter to use.
Syntax: STRING
clear
Commands to clear the device's status or systems.
clear dhcp-lease
Clear one or more DHCP leases.
ip-address ADDRESS
Clear the DHCP lease for an IP address.
Parameters
ADDRESS
An IPv4 or IPv6 address (Required).
Parameters
ADDRESS
12-digit, colon-delimited MAC address [00:11:22:AA:BB:CC] (Required).
Parameters
None
cp
cp commands.
Parameters
source
The source file or directory to copy.
Syntax: STRING
destination
The destination path to copy the source file or directory to.
Syntax: STRING
force
Do not ask to overwrite the destination file if it exists.
Syntax: BOOLEAN
Default: False
Optional: True
help
Show CLI editing and navigation commands.
Parameters
None
ls
Directory listing command.
ls [show-hidden] PATH
List a directory.
Parameters
path
List files and directories under this path.
Syntax: STRING
show-hidden
Show hidden files and directories. Hidden filenames begin with '.'.
Syntax: BOOLEAN
Default: False
Optional: True
mkdir
mkdir PATH
Create a directory. Parent directories are created as needed.
Parameters
path
The directory path to create.
Syntax: STRING
modem
Modem commands.
Parameters
cmd
The AT command string.
Syntax: STRING
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
modem firmware
Commands for interacting with cellular modem firmware. See Update cellular module firmware for
further information about using the modem firmware commands.
Parameters
imei
The IMEI of the modem to execute this CLI command on
Optional: True
Type: string
name
The configured name of the modem to execute this CLI command on
Optional: True
Ref: /network/modem
Type: string
Parameters
imei
The IMEI of the modem to execute this CLI command on
Optional: True
Type: string
name
The configured name of the modem to execute this CLI command on
Optional: True
Ref: /network/modem
Type: string
firmware ota
Commands for performing FOTA (firmware-over-the-air) interactions with cellular modem.
Parameters
imei
The IMEI of the modem to execute this CLI command on
Optional: True
Type: string
name
The configured name of the modem to execute this CLI command on
Optional: True
Ref: /network/modem
Type: string
Parameters
imei
The IMEI of the modem to execute this CLI command on
Optional: True
Type: string
name
The configured name of the modem to execute this CLI command on
Optional: True
Ref: /network/modem
Type: string
Parameters
imei
The IMEI of the modem to execute this CLI command on
Optional: True
Type: string
name
The configured name of the modem to execute this CLI command on
Optional: True
Ref: /network/modem
Type: string
version
Firmware version name
Optional: True
Type: string
Parameters
imei
The IMEI of the modem to execute this CLI command on
Optional: True
Type: string
name
The configured name of the modem to execute this CLI command on
Optional: True
Ref: /network/modem
Type: string
version
Firmware version name
Optional: True
Type: string
modem pin
PIN commands.
Parameters
old-pin
The SIM's PIN code.
Syntax: STRING
new-pin
The PIN code to change to.
Syntax: STRING
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
pin
The SIM's PIN code.
Syntax: STRING
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
pin
The SIM's PIN code.
Syntax: STRING
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
pin
The SIM's PIN code.
Syntax: STRING
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
modem puk
PUK commands.
Parameters
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
puk
The SIM's PUK code.
Syntax: STRING
new-pin
The PIN code to change to.
Syntax: STRING
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
Parameters
slot
The SIM slot to change to.
Syntax: (1|2|show)
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
monitoring
Commands to clear the device's status or systems.
monitoring metrics
Device metrics commands.
uplaod
Immediately upload current device health metrics. Functions as if a scheduled upload was triggered.
Parameters
None
more
path
The file to view.
Syntax: STRING
mv
Move a file or directory.
Parameters
source
The source file or directory to move.
Syntax: STRING
destination
The destination path to move the source file or directory to.
Syntax: STRING
force
Do not ask to overwrite the destination file if it exists.
Syntax: BOOLEAN
Default: False
Optional: True
ping
Ping a host using ICMP echo.
Parameters
host
The name or address of the remote host to send ICMP ping requests to. If broadcast is enabled, can
be the broadcast address.
Syntax: STRING
broadcast
Enable broadcast ping functionality
Syntax: BOOLEAN
Default: False
Optional: True
count
The number of ICMP ping requests to send before terminating.
Syntax: INT
Minimum: 1
Default: 100
interface
The network interface to send ping packets from when the host is reachable over a default route. If
not specified, the system's primary default route will be used.
Syntax: STRING
Optional: True
ipv6
If a hostname is defined as the value of the 'host' parameter, use the hosts IPV6 address.
Syntax: BOOLEAN
Default: False
Optional: True
size
The number of bytes sent in the ICMP ping request.
Syntax: INT
Minimum: 0
Default: 56
source
The ping command will send a packet with the source address set to the IP address of this interface,
rather than the address of the interface the packet is sent from.
Syntax: STRING
Optional: True
reboot
Reboot the system.
Parameters
None
rm
Remove a file or directory.
rm [force] PATH
Parameters
path
The path to remove.
Syntax: STRING
force
Force the file to be removed without asking.
Syntax: BOOLEAN
Default: False
Optional: True
scp
Copy a file or directory over SSH.
scp host STRING local STRING [port INTEGER] remote STRING to STRING user
STRING
Parameters
host
The name or address of the remote host.
Syntax: STRING
local
The file to copy to or from on the local device.
Syntax: STRING
port
The SSH port to use to connect to the remote host.
Syntax: INT
Maximum: 65535
Minimum: 1
Default: 22
remote
The file to copy to or from on the remote host.
Syntax: STRING
to
Copy the file from the local device to the remote host, or from the remote host to the local device.
Syntax: (remote|local)
user
The username to use when connecting to the remote host.
Syntax: STRING
show
Show instance status and statistics.
Parameters
name
Name of the capture filter to use.
Syntax: STRING
Parameters
ipv4
Display IPv4 routes. If no IP version is specififed IPv4 and IPV6 will be displayed
Syntax: BOOLEAN
Default: False
Optional: True
ipv6
Display IPv6 routes. If no IP version is specififed IPv4 and IPV6 will be displayed
Syntax: BOOLEAN
Default: False
Optional: True
verbose
Display more information (less concise, more detail).
Syntax: BOOLEAN
Default: False
Optional: True
show cloud
Show Digi Remote Manager status and statistics.
Parameters
None
show config
Show changes made to default configuration.
Parameters
None
Parameters
all
Show all leases (active and inactive (not in etc/config/dhcp.*lease)).
Syntax: BOOLEAN
Default: False
Optional: True
verbose
Display more information (less concise, more detail).
Syntax: BOOLEAN
Default: False
Optional: True
show dns
Show DNS servers and associated domains.
Parameters
number
Number of lines to retrieve from log.
Syntax: INT
Minimum: 1
Default: 20
table
Type of event log to be displayed (status, error, info).
Syntax: (status|error|info)
Optional: True
Parameters
ip
IP address of a specific client, to limit the status display to only this client.
Syntax: STRING
Optional: True
name
The configured instance name of the hotspot.
Syntax: STRING
Optional: True
Parameters
all
Display all tunnels including disabled tunnels.
Syntax: BOOLEAN
Default: False
Optional: True
tunnel
Display more details and config data for a specific IPsec tunnel.
Syntax: STRING
Optional: True
verbose
Display status of one or all tunnels in plain text.
Syntax: BOOLEAN
Default: False
Optional: True
Parameters
geofence
Shows the status of any configured geofences.
Parameters
filter
Filters for type of log message displayed (critical, warning, info, debug). Note, filters from the number
of messages retrieved not the whole log (this can be very time consuming). If you require more
messages of the filtered type, increase the number of messages retrieved using 'number'.
Syntax: (critical|warning|debug|info)
Optional: True
number
Number of lines to retrieve from log.
Syntax: INT
Minimum: 1
Default: 20
Parameters
verbose
Display more information (less concise, more detail).
Syntax: BOOLEAN
Default: False
Optional: True
verbose
Display more information.
Syntax: BOOLEAN
Default: False
Optional: True
Parameters
imei
The IMEI of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
name
The configured name of the modem to execute this CLI command on.
Syntax: STRING
Optional: True
verbose
Display more information (less concise, more detail).
Syntax: BOOLEAN
Default: False
Optional: True
Parameters
name
The name of a specific NEMO instance.
Parameters
all
Display all interfaces including disabled interfaces.
Syntax: BOOLEAN
Default: False
Optional: True
interface
Display more details and config data for a specific network interface.
Syntax: STRING
Optional: True
verbose
Display more information (less concise, more detail).
Syntax: BOOLEAN
Default: False
Optional: True
show ntp
Show NTP status and statistics.
show openvpn
Show OpenVPN status and statistics.
Parameters
all
Display all clients including disabled clients.
Syntax: BOOLEAN
Default: False
Optional: True
name
Display more details and config data for a specific OpenVPN client.
Syntax: STRING
Optional: True
Parameters
all
Display all servers including disabled servers.
Syntax: BOOLEAN
Default: False
Optional: True
name
Display more details and config data for a specific OpenVPN server.
Syntax: STRING
Optional: True
Parameters
ipv4
Display IPv4 routes.
Syntax: BOOLEAN
Default: False
Optional: True
ipv6
Display IPv6 routes.
Syntax: BOOLEAN
Default: False
Optional: True
verbose
Display more information (less concise, more detail).
Syntax: BOOLEAN
Default: False
Optional: True
show scripts
Show scheduled system scripts
Parameters
None
Parameters
port
Display more details and config data for a specific serial port.
Syntax: STRING
Optional: True
Parameters
verbose
Display more information (disk usage, etc)
Syntax: BOOLEAN
Default: False
Optional: True
show usb
Show USB information.
Parameters
None
Parameters
verbose
Display more information (build date)
Syntax: BOOLEAN
Default: False
Optional: True
Parameters
all
Display all VRRP instances including disabled instances.
Syntax: {True|False}
Type: boolean
name
Display more details and configuration data for a specific VRRP instance.
Optional: True
Type: string
verbose
Display all VRRP status and statistics including disabled instances.
Syntax: {True|False}
Type: boolean
show web-filter
Show web filter status and statistics.
Parameters
None
show wifi
Show Wi-Fi status and statistics.
Parameters
all
Display all Wi-Fi access points including disabled Wi-Fi access points.
Syntax: BOOLEAN
Default: False
Optional: True
name
Display more details for a specific Wi-Fi access point.
Syntax: STRING
Optional: True
Parameters
all
Display all Wi-Fi clients including disabled Wi-Fi client mode connections.
Syntax: BOOLEAN
Default: False
Optional: True
name
Display more details for a specific Wi-Fi client mode connection.
Syntax: STRING
Optional: True
show wifi-scanner
Show Wi-Fi scanner information.
wifi-scanner log
Show output log for the last update interval.
Parameters
None
speedtest
Perform a speed test to a remote host using nuttcp or iPerf. The system's primary default route will be
used. The speed test will take approximately 30 seconds to complete.
Syntax
speedtest HOST mode {iperf|nuttcp} output {json|text} [size INTEGER]
Parameters
HOST: The name or address of the remote host (Required)
mode: Speed test mode (Default: nuttcp)
output: Output format (Default: text)
size : The speed test packet size in kilobytes (Default: 1000)
ssh
Use SSH protocol to log into a remote server.
Parameters
command
The command that will be automatically executed once the SSH session to the remote host is
established.
Optional: True
Type: string
host
The hostname or IP address of the remote host
Syntax: {hostname|IPv4_address|IPv6_address}
Type: string
port
The SSH port to use to connect to the remote host.
Default: 22
Maximum: 65535
Minimum: 1
Syntax: {Integer}
Type: integer
user
The username to use when connecting to the remote host.
Type: string
system
System commands.
system backup
Save the device's configuration to a file. Archives are full backups including generated SSH keys and
dynamic DHCP lease information. Command backups are a list of CLI commands required to build the
device's configuration.
Syntax
Parameters
PATH: The file path to save the backup to. (Default: /var/log/)
passphrase: Encrypt the archive with a passphrase.
remove: Remove a backup file.
type: The type of backup file to create. (Default: archive)
system disable-cryptography
Erase the device's configuration and reboot into a limited mode with no cryptography available. The
device's shell will be accessible over Telnet (port 23) at IP address 192.168.210.1. To return the device
to normal operation, perform the configuration erase procedure with the device's ERASE button twice
consecutively.
Syntax
system disable-cryptography
Parameters
None
system duplicate-firmware
Duplicate the running firmware to the alternate partition so that the device will always boot the same
firmware version.
Syntax
system duplicate-firmware
Parameters
None
system factory-erase
Erase the device to restore to factory defaults. All configuration and automatically generated keys will
be erased.
Syntax
system factory-erase
Parameters
None
system firmware
System firmware commands.
Syntax
Parameters
file: Firmware filename and path. (Required)
Syntax
Parameters
None
Syntax
Parameters
None
Syntax
Parameters
version: Firmware version name
system restore
Restore the device's configuration from a backup archive or CLI commands file.
Syntax
Parameters
PATH: The path to the backup file. (Required)
passphrase: Decrypt the archive with a passphrase.
Syntax
Parameters
SCRIPT: Script to start. (Required)
Syntax
Parameters
SCRIPT: Script to stop (Required).
Syntax
Parameters
PORT: Serial port (Required).
Syntax
Parameters
PORT: Serial port (Required).
FILENAME: The filename to save the serial log. The file will be saved to the device's /etc/config/serial
directory. (Required)
Syntax
Parameters
PORT: Serial port (Required).
Syntax
Parameters
PORT: Serial port (Required).
size: Maximum log size (Default: 65536)
Syntax
Parameters
PORT: Serial port (Required)
system support-report
Save a support report to a file and include with support requests.
Syntax
Parameters
path: The file path to save the support report to. (Default: /var/log/)
Syntax
Parameters
DATETIME: The date in year-month-day hour:minute:second format (e.g "2021-09-26 12:24:48")
(Required)
Syntax
Parameters
None
Syntax
Parameters
None
traceroute
Print the route packets trace to network host.
Parameters
bypass
Bypass the normal routing tables and send directly to a host on an attached network.
Syntax: BOOLEAN
Default: False
Optional: True
debug
Enable socket level debugging.
Syntax: BOOLEAN
Default: False
Optional: True
dontfragment
Do not fragment probe packets.
Syntax: BOOLEAN
Default: False
Optional: True
first_ttl
Specifies with what TTL to start.
Syntax: INT
Minimum: 1
Default: 1
gateway
Tells traceroute to add an IP source routing option to the outgoing packet that tells the network to
route the packet through the specified gateway
Syntax: STRING
Optional: True
icmp
Use ICMP ECHO for probes.
Syntax: BOOLEAN
Default: False
Optional: True
interface
Specifies the interface through which traceroute should send packets. By default, the interface is
selected according to the routing table.
Syntax: STRING
Optional: True
ipv6
If a hostname is defined as the value of the 'host' parameter, use the hosts IPV6 address.
Syntax: BOOLEAN
Default: False
Optional: True
max_ttl
Specifies the maximum number of hops (max time-to-live value) traceroute will probe.
Syntax: INT
Minimum: 1
Default: 30
nomap
Do not try to map IP addresses to host names when displaying them.
Syntax: BOOLEAN
Default: False
Optional: True
nqueries
Sets the number of probe packets per hop. A value of -1 indicated
Syntax: INT
Minimum: 1
Default: 3
packetlen
Total size of the probing packet. Default 60 bytes for IPv4 and 80 for Ipv6. A value of -1 specifies that
the default value will be used.
Syntax: INT
Minimum: -1
Default: -1
pausemsecs
Minimal time interval between probes
Syntax: INT
Minimum: 0
Default: 0
port
Specifies the destination port base traceroute will use (the destination port number will be
incremented by each probe). A value of -1 specifies that no specific port will be used.
Syntax: INT
Minimum: -1
Default: -1
src_addr
Chooses an alternative source address. Note that you must select the address of one of the interfaces.
By default, the address of the outgoing interface is used.
Syntax: STRING
Optional: True
tos
For IPv4, set the Type of Service (ToS) and Precedence value. Useful values are 16 (low delay) and 8
(high throughput). Note that in order to use some TOS precedence values, you have to be super user.
For IPv6, set the Traffic Control value. A value of -1 specifies that no value will be used.
Syntax: INT
Minimum: -1
Default: -1
waittime
Determines how long to wait for a response to a probe.
Syntax: INT
Minimum: 1
Default: 5
host
The host that we wish to trace the route packets for.
Syntax: STRING