Ubiquiti XR5 2.4GHz Mini PCI module User Manual

Ubiquiti Networks, Inc. 2.4GHz Mini PCI module

UserManual.wiki >

Ubiquiti >

XR5 User Manual >

User Manual

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved2Copyright 2010 - 2015 Persistent Systems, LLC. Wave Relay® is a regis-tered trademark of Persistent Systems, LLC. All rights reserved. This User Manual contains information that is the sole property of Persistent Sys-tems, LLC and may not be excerpted, summarized, copied or published without the written permission of Persistent Systems, LLC.This User Manual applies to Wave Relay® Firmware Version 18.4.0+. For information on older ﬁrmware versions, contact Persistent Systems.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 3Copyright 2010 - 2015 Persistent Systems, LLCIssued: April 201503EN009 (English)

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved4

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 5INTRODUCTION Headquartered in New York City since 2007, Persistent Systems LLC is a global communications technology company which develops, manufactures and integrates a patented and secure Mobile Ad Hoc Networking (MANET) system: Wave Relay®. The company’s industry leading R&D team has designed wireless networking protocols to support their cutting edge Wave Relay® system and technology. Wave Relay® is capable of running real-time data, video, voice and other applications under the most difﬁcult and unpredictable conditions. Their suite of products is ﬁeld proven and utilized in Commercial, Military, Government, Industrial, Agriculture, Mining, Oil and Gas, Robotics, and Unmanned System markets. The Wave Relay® System is a peer-to-peer wireless MANET networking solution in which there is no master node. If any device fails, the rest of the devices continue to commu nicate using any remaining connectivity. By eliminating master nodes, gateways, access points, and central coordinators from the design, Wave Relay® delivers high levels of fault tolerance regardless of which nodes might fail. The system is designed to maximize the capacity of the radio frequency (RF) spectrum and to minimize the network overhead. While optimizing efﬁciency, Wave Relay® also implements tech niques that increase multicast reliability. The advanced multicast functionality allows the system to support both multicast voice and video over IP. Wave Relay® is designed to maintain high bandwidth con nectivity among devices that are on the move. The system is scalable, enabling it to incorporate unlimited meshed devices into the wireless network, where the devices themselves form the communication infrastructure. Even in high ly dynamic environments, the system is able to maintain connectivity by rapidly re-routing data. Wave Relay® “self-form” and “self-heal” as nodes move unpredictably throughout the network, and Wave Relay® routing adapts in less than a second to ﬂuctuations in topology and other environmental conditions, continuously maximizing the communication performance. Due to Wave Relay’s® architecture, deploying the system and establishing the network are as easy as plugging in an Ethernet cable. The system operates on the data link layer (OSI Layer 2) rather than the network layer (Layer 3), facilitating plug-and-play operation. Wave Relay® is a seamless wireless networking system offering a dynamic and reliable solution for all mobile networking needs. Wave Relay® offers all of these capabilities in an inte grated and cost-effective package.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved6 TABLE OF CONTENTSIntroduction 5Persistent Systems, LLC 5Device Hardware Introduction 8Man Portable Unit — Gen4 10Man Portable Unit — Gen3 Single 11Quad Radio Router 12Man Portable Unit — Gen3 Dual 14AID 15Device Operation 16Pushbutton/LED Operation 17Conﬁguration 18Web Management Overview 20Web Management Introduction 21Accessing the Web Management Interface 22Conﬁguring Your Computer’s IP Address 23Security Certiﬁcate Warnings 24Initial Node Configuration 26Steps for Conﬁguring the First Node 27Steps for Conﬁguring Remaining Nodes 32Node List 36Network vs. Managed Nodes Deﬁned 36Network Upgrade 37

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 7Web Management Interface Reference 38Node Status 39Node Conﬁguration 48Creating a Master Conﬁguration File 61Quick Setup 63Reset to Factory Conﬁguration 64Tracking Antenna Control 65Push-To-Talk (PTT) 67RS-232 71Date/Time 75Ampliﬁer Conﬁguration 77Network Status 79Network Conﬁguration 87Network Node List 88Network Defaults 89Security 101Wave Relay® API 104Troubleshooting 106Common Problems And Troubleshooting 107Symptom 1: Nodes Are Unale To Communicate 109Symptom 2: Poor/Low Throughput 110Symptom 3: Multicast Trafﬁc Not Forwarding Correctly 110Hardware Details 112Man Portable Unit — Gen4 114Man Portable Unit — Gen3 122Quad Radio Router 130Sector Array Kit 135Tracking Antenna System 137Regulatory Information 142Change History --Supporting Manuals Cloud Relay™ Manual Android™ Manual Rapid Conﬁguration Tool Manual Quality Control Tool Manual All Available Upon RequestTABLE OF CONTENTS

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved8DEVICEHARDWAREINTRODUCTION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 9DEVICE HARDWARE INTRODUCTION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved10MAN PORTABLE UNIT — GEN4 DEVICE HARDWARE INTRODUCTIONGPS3.3V Active Antennaonly (SMA)RADIO 1 ANTENNA(RP-TNC)BATTERY TWIST-LOCK CONNECTIONIncluded: BAT-06Battery Eliminator: CBL-054Compatible With: PRC-148 Battery PRC-152 Battery POWER10-48VDC(48 VDC is PoE)POWER/DEVICE I/O (19-PIN)Ethernet 1: 10.3.1.254 Ethernet 2: 10.3.2.254Serial RS-232PTT AudioPoE: 10-48 VDCPUSHBUTTON/LED ZEROIZE: PRESS 3X IN < 2SECONDS

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 11MAN PORTABLE UNIT — GEN3 SINGLE DEVICE HARDWARE INTRODUCTION RADIO 1 ANTENNA(RP-TNC)AUXILIARY POWER (3-PIN)10-48 VDCGPS3.3V Active Antenna only (SMA)POWER/DEVICE I/O (19-PIN)Ethernet 1: 10.3.1.254 Ethernet 2: 10.3.2.254Serial RS-232PTT AudioPoE: 10 - 48 VDCPUSHBUTTON/LED ZEROIZE: PRESS 3X IN < 2SECONDS

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved12QUAD RADIO ROUTER DEVICE HARDWARE INTRODUCTIONPUSH-TO-TALK (PTT) AU-DIO (NATO 6-PIN CON-NECTOR)ETHERNET 2 SWITCH PORT(RJ45)CANNOT accept PoEEthernet 2 IP: 10.3.2.254RADIO 2ANTENNA(N-type)RADIO 1ANTENNA(N-type)

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 13DEVICE HARDWARE INTRODUCTION ETHERNET 2 SWITCH PORT(RJ45)CANNOT accept PoEEthernet 2 IP: 10.3.2.254RADIO 4ANTENNA(N-type)GPS3.3V Active Antenna only (SMA)RADIO 3ANTENNA(N-type)AUXILIARY POWER/SERIAL (4-PIN)10-48 VDCPOWER/ETHERNET 1(RJ45)Accepts PoE, 10-48 VDCEthernet 1 IP: 10.3.1.254PUSHBUTTON/LED ZEROIZE: PRESS 3X IN < 2SECONDS

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved14MAN PORTABLE UNIT — GEN3 DUAL DEVICE HARDWARE INTRODUCTIONRADIO 2ANTENNA(RP-TNC)RADIO 1ANTENNA(RP-TNC)GPS3.3V Active Antenna only (SMA)AUXILIARY POWER (3-PIN)10-48 VDCPOWER/DEVICE I/O (19-PIN)Ethernet 1: 10.3.1.254 Ethernet 2: 10.3.2.254Serial RS-232PTT AudioPoE: 10 - 48 VDCPUSHBUTTON/LED ZEROIZE: PRESS 3X IN < 2SECONDS

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 15AIDPOWER/ETHERNET 1(RJ45)Accepts PoE, 10-48 VDCFactory Setup IP: 10.3.1.254ETHERNET 2(RJ45)PoE,10-48 VDCFactory Setup IP: 10.3.2.254TO MPU(19-PIN)PUSH-TO-TALK(PTT) AUDIO(NATO 6-PINCONNECTOR)DEVICE HARDWARE INTRODUCTION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved16DEVICE OPERATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 17Low Battery(MPU4 Only)OFF 2 SEC,ON .5 SECONONSLOW BLINKFAST BLINKOFFHOLD(1 second)TAP 3 TIMES(< 2 sec)NOTE:PUSHBUTTON/LED OPERATIONDEVICE OPERATION STATE LED STATUS OPERATION INSTRUCTIONOFF ON/OFF PowerBoot Up (30s - 2 mins)Fully OperationalZeroizeConﬁguration RequiredZeroize

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved18When a node is shipped from the factory, it is in a state that requires conﬁguration. Nodes can be conﬁgured by using the Web Management Interface or through the Management API. Follow the steps under “Initial Node Conﬁguration” to put the nodes into an opera-tional state. The basic steps required to conﬁgure a node to an operational state are:SET ENCRYPTION KEYA key must be set in order for a node to communicate with other nodes in the net-work. In order for two nodes to communicate, they must share a matching encryp-tion key and crytpo mode. SET CHANNELEach radio module on a node should be assigned a center frequency and channel width. In order for two nodes to communicate, each node must have at least one radio that shares the same center frequency and channel width. SET IP ADDRESSDuring node conﬁguration, a node needs to be assigned a unique management IP address. This management IP address is used for monitoring, conﬁguration, and device services (PTT, Google™ Earth, Tracking, RS-232, etc.). In the event that two nodes are unable to communicate after initial conﬁguration, refer to the “Troubleshooting” section starting on page 104.CONFIGURATION DEVICE OPERATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 19

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved20WEBMANAGEMENTOVERVIEW

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 21WEB MANAGEMENT OVERVIEW WEB MANAGEMENT INTRODUCTIONThe Wave Relay® Web Management Interface enables users to conﬁgure and monitor Wave Relay® units through a web browser. A navigation bar organizes the Management Interface. The “Node Status” and “Node Conﬁguration” tabs pertain only to the node to which the management computer is connected (either by Ethernet cable or by wireless), and the “Network Status” and “Network Conﬁguration” tabs pertain to the entire network of nodes.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved22NODE CONNECTIVITY INFORMATIONDefault Management PasswordEthernet 1 Factory Setup IPEthernet 2 Factory Setup IPPassword10.3.1.25410.3.2.254•Factory Setup IP addresses are always accessible when directly connected to the radio. Use Factory IPs any time you do not remember the management IP address of the radio.•To connect to the Factory IP address, the management computer must be on the correct IP subnet and wired to the correct Ethernet port on the node.MANAGEMENT COMPUTER SETTINGSIP Address Subnet MaskDefault Gateway / Router10.3.1.10255.255.255.010.3.1.1•To connect to the node using Ethernet 1, open a web browser and connect to http://10.3.1.254. •Each time you connect a new device, you may need to accept a security certiﬁcate before you can enter the Web Management Interface.•See next page for information on setting up the management computer.ACCESSING THE WEB MANAGEMENT INTERFACE WEB MANAGEMENT OVERVIEW

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 23For your computer to be able to communicate with the Wave Relay®, it must have an IP address that is in the same IP subnet mask as the Wave Relay®’s IP address. A subnet mask of 255.255.255.0 means that the computer can communicate with another device that has an IP address matching the ﬁrst three numbers of its own IP address. No Default Gateway or DNS server conﬁguration is required; however they can be conﬁgured if necessary. Most computers are capable of having more then one IP address conﬁgured on a single Ethernet adapter. It is recommended that you add all three addresses to your wired Ethernet adapter so that you can easily manage your network.CONFIGURING YOUR COMPUTER’S IP ADDRESSWINDOWS:Start > Network (Right Click) > Properties Change Adapter Settings (Windows Vista / 7 only) Local Area Connection (Right Click) > Properties Select Internet Protocol Version 4 (TCP/IPv4) Click Properties Select Use the following IP AddressClick Advanced…Click Add…Enter IP Address and Subnet maskClick Add and repeat for all IP Addresses LINUX:[sudo] ifconﬁg eth0 10.4.1.10/24 [sudo] ip addr add 10.3.1.10/24 dev eth0 [sudo] ip addr add 10.3.2.10/24 dev eth0WEB MANAGEMENT OVERVIEW

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved24Recommended browsers are Firefox 3+, Internet Explorer 7+, and Google™ Chrome. Internet Explorer 6 is not compatible with the most recent Web Management Interface. If you are having difﬁculty connecting to the Web Management Interface, make sure you are using one of the recommended browsers.When connecting to the Web Management Interface, Firefox and Internet Explorer may ask the user to accept a security certiﬁcate. Firefox and IE handle security cer-tiﬁcates in different ways:SECURITY CERTIFICATE WARNINGS WEB MANAGEMENT OVERVIEWFIREFOX DISPLAYS A PAGEClick “I understand the risks” > ”Add Exception” > ”Conﬁrm Security Exception.”IE DISPLAYS A PAGEClick the red X “Continue to this website (not recomended).”

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 25GOOGLE™ CHROME DISPLAYS A PAGE1. Click the “Proceed anyway” button.2. When the Web Management Interface loads, enter the management password and click “Authenticate.” The default management password is “password” which is set from the factory or after the key/conﬁguration is zeroized by push-ing the on/off button 3 time in less than 2 seconds.WEB MANAGEMENT OVERVIEW

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved26INITIAL NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 27STEPS FOR CONFIGURING THE FIRST NODEAll nodes arrive set to factory default conﬁguration. This section details the recommended setup and custom conﬁguration procedure for a set of identical nodes, for example, a set of 50 MPU4s. In general, the procedure is completed as follows:1. Conﬁgure an individual node2. Save the individual node’s conﬁguration settings and key3. Load key and the saved conﬁguration settings into remaining nodes4. Verify communication among the nodesQUICK CONFIGURATIONIf the network administrator provides a node conﬁguration ﬁle, use it to facilitate quick device conﬁguration. Please refer to Section “Quick Setup.” If a node con-ﬁguration ﬁle has been provided, skip to the “Steps for Conﬁguring the Remaining Nodes” section.INITIAL NODE CONFIGURATION STEPS FOR CONFIGURING THE FIRST NODE1. Conﬁgure Network Defaults2. Customize Node Name and IP Address To Be Unique3. Conﬁgure Radio to Use Defaults4. Setup Node List5. Store Conﬁguration File6. Set and Save Security Settings

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved28 INITIAL NODE CONFIGURATIONSTEP 2: CUSTOMIZE NODE NAME AND IP ADDRESS TO BE UNIQUE Each node in the network should be assigned a unique node name and IP address to facilitate management and network operations.1. Click “Node Conﬁguration” > “Node Conﬁguration.”2. Insert the new name and IP Address in the indicated ﬁelds.3. Set the gateway to match the subnet of the node’s IP address.4. Click the “Save & Reconﬁgure Unit” button at the bottom of the page.5. Load the key and saved conﬁguration ﬁle into remaining nodes. Customize the Node Name and IP address for each node, then click the “Save & Reconﬁgure Unit” button at the bottom of the page.6. Ensure that node names and IP addresses of all nodes are unique.STEP 1: CONFIGURE NETWORK DEFAULTSNetwork Defaults are settings that will be used to manage the conﬁguration of the network. Up to 16 different default Channel settings are able to be conﬁgured. 1. Click “Network Conﬁguration” > “Network Defaults.”2. Choose the settings you would like to use for your network for each Channel.3. Click the “Save to Network” button at the bottom of the page.For more information on setting Network Defaults, refer to the section “Network Conﬁguration > Network Defaults.”WARNING!For units branded with an FCC label and FCC ID, only the provided antenna or equivalent type and gain can be used: this device must comply with Part 15 of the FCC rules.FCC branded devices will be limited so users can-not set output power levels outside of those certi-ﬁed under the FCC rules.FCC test results and reports can be provided by Persistent Systems, LLC upon request.For more information, please contact Persistent Sys-tems, LLC Quality/Compliance personnel.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 29STEP 3: CONFIGURE RADIO TO USE DEFAULTS The node must be conﬁgured to use the appropriate Network Defaults in order for the node to be managed by changes to the Network Conﬁguration.1. Click “Node Conﬁguration” > “Node Conﬁguration.”2. Select the appropriate Network Defaults in the drop down menus.3. Click the “Save & Reconﬁgure Unit” button at the bottom of the page.For more information, see section “Conﬁguring Radio to Use Defaults.”INITIAL NODE CONFIGURATION STEP 5: STORE CONFIGURATION FILE Device settings (both Node Conﬁguration and Network Conﬁguration settings) can be saved to a conﬁguration ﬁle. The conﬁguration ﬁle serves as a backup for device settings and provides the ability to easily transfer settings from one node to another.1. Ensure Network Conﬁguration and Node Conﬁguration settings are set as desired.2. Click “Node Conﬁguration” > “Conﬁg Management.”3. Click the “Store” button. A prompt will appear to choose where to save the conﬁguration ﬁle. Note speciﬁcally that this ﬁle contains settings (both Network Conﬁguration and Node Conﬁguration settings) for the current device only. STEP 4: SETUP NODE LISTThe Node List is a list of IP Addresses of nodes managed by the Web Management Interface.1. Click “Network Conﬁguration” > “Network Node List.”2. Enter the IP Address of a node in the “Manually Add IP(s)” ﬁeld and click “Add” to add the node associated with that IP Address to the Node List. Nodes may also be added from the “Other Nodes on Network” window if they are detected by the network. These nodes may be added individually with the “Selected IPs” button or all at once with the “All” button.3. Repeat this process for every node to be managed.4. With all new nodes programmed and on, ensure that all nodes are on the Network Node List.5. Click the “Push Management List to Network” button. This function will copy the node list to each node in the network. Only nodes in the node list will be affected by Network Conﬁguration functions. Pushing the node list to the network allows network-wide settings to be managed from any node in the network.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved30 INITIAL NODE CONFIGURATION231STEP 6: SET AND SAVE SECURITY SETTINGSA node will not function properly unless it has a valid key. If the “Security” tab in the Web Management Interface is blinking red, then a proper key has not been set. All nodes in a network must use the same Crypto Mode AND Key in order to communicate. 1. Select the “Security” tab in the Web Management Interface.2. Select a Crypto Mode to match your network requirements.3. Once the Crypto Mode is set, enter a key value into the ﬁeld and click “Set” or click “Generate” to generate a random key. The new key information is stored to the node or the network based on the setting in the “Update” menu.For more information on Security information and selecting Crypto Mode options, refer to the “Security” section. The key will NOT be stored in the conﬁguration ﬁle. The key must be stored sepa-rately.1. Click the “Display Key” button.2. Select OK on the warning to open the key. Since the key is displayed in plain-text, only open the key in a secure environment.3. Copy the key to a text ﬁle in a secure place on your management computer.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 31INITIAL NODE CONFIGURATION Ensure all nodes are using the sameCrypto ModeEnter your key hereClick here after entering key123

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved32STEPS FOR CONFIGURING THE REMAINING NODES1. Load Conﬁguration File into All Other Nodes2. Load Key into All Other Nodes3. Verify Nodes are Communicating4. Push Node List to Network5. Set Management PasswordSTEPS FOR CONFIGURING THE REMAINING NODES INITIAL NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 33STEP 1: LOAD CONFIGURATION FILE INTO ALL OTHER NODES When setting up a network of new nodes from the factory, use the conﬁguration ﬁle saved in the “Store Conﬁguration File” step to upload the settings from the previously conﬁgured node into the new node. During this process, node speciﬁc settings (including IP Address, Radio Name, and other radio speciﬁc settings) can be conﬁgured separately for each node while preserving all other settings from the conﬁguration ﬁle.1. Click “Node Conﬁguration” > “Conﬁg Management.”2. In the Load Conﬁguration menu, select “network (require all)” or “network (any available)” to upload conﬁguration settings to all nodes in the network. The “network (require all)” setting will require all nodes in the network be available for any changes to be applied. If not all nodes are available, no changes will be applied. The “network (any available)” setting will apply changes to available nodes only.3. Click the “Choose File” button to ﬁnd the the conﬁguration ﬁle saved in the “Store Conﬁguration File” step.4. Click the “Load” button to upload conﬁguration settings to other nodes in the network.STEP 2: LOAD KEY INTO ALL OTHER NODESThe security key is NOT stored in the conﬁguration ﬁle. You must load the key separately. 1. Select the “Security” tab in the Web Management Interface.2. In the “Set Key” box, select “network (require all)” or “network (any available)” to upload the security key to all nodes in the network. The “network (require all)” setting will require all nodes in the network be available for any changes to be applied. If not all nodes are available, no changes will be applied. The “network (any available)” setting will apply changes to available nodes only.3. Select the Crypto Mode chosen in Step 6 of First Node Conﬁguration from the drop-down menu.4. Copy the security key from the text ﬁle saved in Step 6 of First Node Conﬁgura-tion and paste the security into the “Enter key” ﬁeld. All nodes MUST have the same security key to communicate.INITIAL NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved34STEP 3: VERIFY NODES ARE COMMUNICATINGAfter nodes have been conﬁgured, the connectivity of the nodes should be checked.1. Ensure that all nodes are turned on, that at least one radio on each node has an antenna and is set to the same channel as the other nodes, and that each node has the same key. 2. Access one of the nodes and verify connectivity to all the nodes. Click “Node Status” > “Neighbor Status.” The ﬁgure below displays the Node Neighbor Status, which shows which of the node’s radios are communicating with other radios. This ﬁgure shows that Radio 1 is communicating with one other radio in a neighbor node.STEP 4: PUSH NODE LIST TO NETWORK To be able to control conﬁguration settings for the entire network from any node in the network rather than just this node, the user must push the Node List to all other nodes in the network.1. Click “Network Conﬁguration” > “Network Node List” > “Push Management List to Network.” This function will share the Node List conﬁgured on this node with all nodes in the Node List. INITIAL NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 35STEP 5: SET MANAGEMENT PASSWORD After all nodes have been conﬁgured, the management password should be changed.1. Click “Network Conﬁguration” > “Network Password.”2. Enter the old password in the “Old Password” ﬁeld.3. Enter the new password in both “New Password” ﬁelds.4. Click the “Change” button to change the management password. The management password will be changed on all nodes in the node list. The current node list is displayed at the bottom of the page.INITIAL NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved36The Node List contains a list of nodes speciﬁed by IP Address that are controlled by the Web Management Interface. Any function that resides under Network Status or Network Conﬁguration operates on, and only on, the nodes listed in the node list. In the context of Wave Relay®, the network is deﬁned as the set of nodes for which routing is possible. These nodes do not need to be speciﬁed in the Node List. By contrast, the Node List deﬁnes a set of Managed Nodes that are managed by the network operations in the Web Management Interface. That list, however, does not restrict connectivity between nodes speciﬁed in the Node List and nodes not speciﬁed in the Node List. Therefore, the Node List is just a management tool that deﬁnes the list of nodes on which network management functions operate. In general, the Node List should be updated whenever the network changes in order to ensure that every node has complete and current information and is able to be monitored and controlled by the network operations in the Web Management Interface. NODE LISTNETWORK VS MANAGED NODES DEFINED INITIAL NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 37Network Upgrade installs new ﬁrmware versions on large numbers of nodes with one operation. Since network upgrades function on all nodes in the Node List, make sure the Node List is complete and current before performing a Network Upgrade.1. Click “Network Conﬁguration” > “Network Upgrade.”2. Browse and select the appropriate upgrade ﬁle.3. Check or uncheck “Require All.” If checked, the update will be installed if and only if all the nodes in the Node List are accessible. If unchecked, the update will be installed to only those nodes in the Node List that are accessible. Network Upgrades will cause nodes to be reconﬁgured, an operation that causes a period of downtime. Do not perform Network Upgrades during mission critical operations that cannot tolerate such disruptions. Under such situations, perform Network Upgrades only during scheduled maintenance or other appropriate times.4. Click the “Upload” button to upgrade ﬁrmware for all nodes in the Node List.NOTE: When upgrading or downgrading a node’s ﬁrmware, it is normal for the LED to turn off for 30 seconds then turn on.Do not unnecessarily disturb devices during a Network Upgrade. Loss of power during the Network Upgrade can permanently damage a device.To receive the latest ﬁrmware update:1. Connect to: http://www.persistentsystems.com/requestﬁrmwareupdate.php2. Fill out all ﬁelds on the page.3. Ensure the “Receive Firmware” box is checked.4. Click the “Submit Query” button.NETWORK UPGRADEINITIAL NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved38WEBMANAGEMENTINTERFACEREFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 39WEB MANAGEMENT INTERFACE REFERENCE The “Node Status” tab in the Web Management Interface contains node-speciﬁcinformation for the individual node that the user is connected to.NODE STATUS

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved40MENU ITEM MENU ITEM DESCRIPTIONFirmware Version Firmware version on nodeSerial No. Serial number of nodeUptime Operating time since last node power on or rebootTemperature Temperature of nodeInput Power Voltage Voltage supplied to nodeReal Time Clock Battery Voltage of real-time-clock keep-alive battery (on units with RTC)Current System Time Current system time of node (in both UTC and current time zone if not UTC)Management HW MAC AddressMAC Address for Management Hardware of nodeRadio X HW MAC Ad-dressMAC Address and bandwidth for each radio installed in node (X will vary based on number of radios installed)Ethernet X HW MAC AddressMAC Address for each ethernet port in node (X will vary based on number of Ethernet ports in node)UNIT INFOUnit Info displays a list of hardware and software information related to the node. WEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 41WEB MANAGEMENT INTERFACE REFERENCE MENU ITEM MENU ITEM DESCRIPTIONInterface Each interface in use on nodeNeighbor Name, IP address, and interface of each neighbor nodeReceive SNR Signal-to-Noise Ratio at which local node hears remote nodeNEIGHBOR STATUSNeighbor Status page displays a list of neighbor nodes that the current node has an RF connection with.If the neighbor node is in the node list and the “Update Network” operation has been performed, the node’s name, IP address, and radio interface will be displayed. Otherwise, the neighbor node’s MAC address will be displayed.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved42 WEB MANAGEMENT INTERFACE REFERENCEInternal GPS Status:MENU ITEM MENU ITEM DESCRIPTIONFix Type How node is connected (3D, 2D, or none)Latitude Latitude of current nodeLongitude Longitude of current nodeAltitude Altitude above sea level of current nodeSpeed Speed of node (m/s) in the horizontal planeTrack Path of travel with respect to the Earth expressed in degrees - 000 degrees is North (angle increases clockwise through 360 degrees)Climb Speed of node (m/s) in the vertical planeFix Time When node obtained a satellite ﬁxNumber of satellitesNumber of satellites node is connected toID/PRN ID/PRN of each satellite node is connected toSignal Strength of the connection between node and each satelliteNTP Server Status of the NTP server (available or unavailable)GPS STATUSPosition Update Status:MENU ITEM MENU ITEM DESCRIPTIONSource GPS information sourceLatitude Latitude of current nodeLongitude Longitude of current nodeAltitude Altitude above sea level of current nodeSystem Clock Status:When the system clock was set by GPSCurrent system time

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 43TRAFFIC LOADTrafﬁc load monitors and analyzes the traffﬁc load on the wireless and wired networking interfaces on the node.Channel Usage:MENU ITEMMENU ITEM DESCRIPTIONSent Transmission duty cycle of wireless medium usageReceived Receiving transmission duty cycle of wireless medium usageNoise Duty cycle of wireless medium us-age: Occupied by noiseUsed Total duty cycle of wireless medium usageWEB MANAGEMENT INTERFACE REFERENCE Checking Trafﬁc Load:MENU ITEM MENU ITEM DESCRIPTIONMbps Total Total Mbps used on this interfaceMbps Wave Relay®Total Mbps used by Wave Relay®Mbps Wave Relay® Sent Mbps used by Wave Relay® to sendMbps Wave Relay® Received Mbps used by Wave Relay® to receiveMbps Control Total Mbps used for control functionsMbps Control Ack Mbps used to control ACKMbps Control RTS/CTS Mbps used to control RTS/CTSMbps Other Mbps used for other functionsMbps Sent Total Mbps used for all transmissionsMbps Sent Unicast Mbps used for Unicast transmissionsMbps Sent Broadcast/Multicast Mbps used for Broadcast/Multicast transmissionsMbps Received Total Mbps used to receive all transmissionsMbps Received Unicast Mbps used to receive Unicast transmissionsMbps Received Broadcast/Multi-castMbps used to receive Broadcast/Multicast transmis-sions

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved44BANDWIDTH TESTBandwidth Test is a tool for testing the data throughput from the node to another node in the network. It is recommended to perform at least a 5 second throughput test.Wave Relay® nodes run a TCP iPerf server. To perform a TCP throughput test through the iPerf server, use the command “iperf -c X” (X is the IP address of the node) from the command line. WEB MANAGEMENT INTERFACE REFERENCETO PERFORM A THROUGHPUT TEST:1. Select destination node for throughput test from drop-down menu. Desired destination node must be in Node List for it to appear on this menu.2. Check or uncheck “Upload only test.” If this box is checked, throughput test will only test upload to destination node.3. Enter desired throughput test duration (in seconds) into “Test Duration” ﬁeld. Caution: during tests of long duration, data will continue to be sent for the full speciﬁed duration even if a different data ﬂow is started or the web browser is exited.WARNING: Windows has known issues running iPerf and does not give true bandwidth readings. Contact Persistent Systems for more information.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 45TRACKING STATUSTracking Status displays relevant an-tenna tracking status and diagnostic information.MENU ITEM MENU ITEM DESCRIPTIONTracking Antenna Mode Tracking conﬁguration of nodeLocal Coordinates Coordinates of tracking nodeTarget Coordinates Coordinates of tracked nodeTarget Distance Distance of tracked node from tracking nodeTarget SNR Signal-to-Noise ratio between tracking node and tracked nodeTarget Azimuth Azimuth of tracked nodeTarget Elevation Elevation of tracked nodeTarget Antenna Pan Calculated necessary horizontal position of Tracking Antenna in degrees clockwise from NorthTarget Antenna Tilt Calculated necessary vertical position of Tracking Antenna expressed in degreesActual Antenna Pan Current horizontal position of Tracking Antenna in degrees clockwise from North (will only pan when Target changes at least 0.5 degrees from Actual)Actual Antenna Tilt Current vertical position of Tracking Antenna in degrees (will only tilt when Target changes at least 0.5 degrees from Actual)STATION LISTStation List displays the list of 802.11 client stations currently connected to radios with the 802.11 access point feature enabled.MENU ITEMMENU ITEM DESCRIPTIONmacaddr MAC Address of client device connected to access pointrssi Strength of signal to client devicelast_rx Time (in seconds) since a packet was last receivedWEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved46IP FLOW LISTIP Flow List lists IP data ﬂows passing through node sorted by measured throughput.IP MULTICAST STATUSIP Multicast Status displays IGMP Snoop-ing and IP Multicast Pruning status. This feature shows a table with a row for each multicast group, displaying an “F” if that group is forwarded over the MANET, or a “-” if it is not.There are known issues with IGMP in Windows XP. WEB MANAGEMENT INTERFACE REFERENCEMENU ITEM MENU ITEM DESCRIPTIONMbit/s Speed of each IP data ﬂow in MbpsPkt/s Number of packets transferred each second for each IP data ﬂowTotal bytes Number of bytes transferred for each IP data ﬂowDestination IP IP address of destination nodeSource IP IP address of source nodeDirection/Interfaces Direction of and interfaces used by each IP data ﬂow (MANET, Ether-net X, or this node)MENU ITEM MENU ITEM DESCRIPTIONGroup Multicast address of nodes connected to managed nodeRegistered to receive packets for groupInterface used to receive data for each multicast address (Ether-net X or MANET)WRoIP STATUSWRoIP Status displays the Wave Relay® over IP gateway status.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 47SYSTEM LOGThe System Log page displays a history of node management operations. The “Refresh” button reloads the system log to add more recent operations. The “Download” button allows the user to download the log to the computer.DYNAMIC LINK EXCHANGE PROTOCOL (DLEP) STATUSThe DLEP Status page shows if the DLEP services is running, what port, who it’s connected to and the status of it. It also contains the status of the associated neighbors.It is also possible to set the status of DLEP on the Cisco Router side.WEB MANAGEMENT INTERFACE REFERENCE MENU ITEM MENU ITEM DESCRIPTIONGateway Which gateway the node is connected to as well as the priority of that gate-wayElected Whether the gateway is elected or notElection Priority Election priority of the gateway over other gateways/number of other WRoIP gateways on the IP network.WRoIP gateways detectedDisplays names of detected WRoIP gateway nodesWhen connected to a WRoIP-con-ﬁgured node, the Neighbor SNR status page for the node will NOT display other nodes connected over WRoIP. Instead, these nodes will be displayed on the MANET Monitor page with a SNR of “-” since they are not connected via radio.For detailed information, see the Cloud RelayTM Manual

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved48 WEB MANAGEMENT INTERFACE REFERENCEThe “Node Conﬁguration” tab in the Web Management Interface contains conﬁguration options for managing an individual node. Click “Node Conﬁguration” > “Node Conﬁguration” to access basic Node Conﬁguration settings.NODE CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 49WEB MANAGEMENT INTERFACE REFERENCE SHOW/HIDE ADVANCED FIELDSFor convenience, this button allows you to show (or hide) many of the less frequently used node conﬁguration ﬁelds. The default is to hide the advanced ﬁelds (and thus display a briefer page). If you choose to show the advanced ﬁelds, your choice will remain in effect when you revisit the page. Advanced ﬁelds are indicated as such in the descriptions below.MANAGEMENT SETTINGSMENU ITEM MENU ITEM DESCRIPTIONNode Name Nodes can be assigned a unique name which is displayed in all of the management status functions.IP Address A node IP address can be assigned to allow IP connectivity. The IP address is generally used for node management functions. An IP address is not required for actual network operation, only for management and conﬁguration.Netmask This ﬁeld deﬁnes the netmask for the Web Management Interface.Gateway This ﬁeld deﬁnes the default gateway if a default gateway is required. The gateway must be set to an IP address on the same subnet as the IP address for the node.VLAN ID (advanced)This setting conﬁgures this node’s management port VLAN ID. Management features will ONLY be accessible to the speciﬁed VLAN (trafﬁc to/from all other VLANs is blocked/ﬁltered).

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved50 WEB MANAGEMENT INTERFACE REFERENCERADIO CONFIGURATION(BASIC RADIO SETTINGS)MENU ITEM MENU ITEM DESCRIPTIONName Each radio can be assigned a name to be used in status functions.MANET (ADVANCED)MENU ITEM MENU ITEM DESCRIPTIONIP Multicast Rout-ingAUTO: Node will prune multicast packets that are not requested (de-fault, most efﬁcient setting for network).PULL ALL MULTICAST: Node will accept all multicast packets it hears on the network. Note: Windows CE/XP computers do not respond to IGMP Multicast Group Queries sent by Wave Relay nodes. “Pull All Multicast” should be used in networks with Windows CE/XP computers to work around this issue.Root Gateway Priority (advanced)HIGH: Any node in your network directly connected to wired infrastructure should have priority set to “HIGH.”MEDIUM: All other non-mobile routers should be set to “MEDIUM.”LOW: Mobile routers should be set to “LOW.”DHCP Server Filter (advanced)ALLOW: Device will pass DHCP messages FROM a DHCP server which is bridged directly by one of its interfaces. Only the devices which are directly wired to the switch where the DHCP server resides need to be set to “ALLOW.”BLOCK: Device will not bridge any DHCP reply packets that it picks up off of any of its bridged interfaces. By setting all of the nodes in the network (except the nodes physically connected to the real DHCP server) to “BLOCK,” you will ensure that users of your system will always use the correct DHCP server.SNAP OUI (advanced)Controls the Subnetwork Access Protocol Organizationally Unique Identiﬁer - The factory OUI, 0018A6, is registered to Persistent Systems, LLC with the IEEE. SNAP OUI is used to identify Wave Relay® packets. Changing this ﬁeld allows the user to obscure which protocol is being used by the system. All nodes must be set to the same value or they will not communicate.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 51RADIO CONFIGURATION(ADVANCED RADIO SETTINGS)MENU ITEM MENU ITEM DESCRIPTIONMax Transmit Power (advanced)Max Transmit Power will control the radio’s maximum output power. In general, this conﬁguration is only used to reduce the output power of a radio for regulatory compliance reasons. The factory default setting should provide the best communication performance (highest power) in all other situations.MAC Address(advanced)A custom MAC address may be used for this radio. The entered value MUST be different from ALL other radio MAC addresses used in the same network or with the same encryption key. All radios are factory conﬁgured with a globally unique MAC. Since the MAC address is unencrypted, using a custom MAC that is periodically changed can help prevent identiﬁcation and tracking of the same device across multiple uses.WEB MANAGEMENT INTERFACE REFERENCE Frequency Each radio should be a assigned a frequency. Two radios must be set to the same frequency in order to communicate. If the radio is conﬁgured to use a “Network Default” channel, the radio’s channel assignment can be managed globally by clicking “Network Conﬁguration” > “Network Defaults.” Ensure that the frequency is set to match the radio installed in the unit. A warning will be displayed if the frequency setting does not match the radio hardware.Bandwidth Each radio should be assigned a bandwidth. Two radios must be set to the same bandwidth in order to communicate. Bandwidth should be increased for shorter distances and decreased for increased distances.Max Link Dis-tanceThe Max Link Distance should be set to the upper bound of how long any individual link in the network may need to be. All nodes on the net-work MUST be set to the same Max Link Distance.Channel Density The channel density setting controls how aggressively the radios compete for access to the shared medium. A number of nodes will be displayed in parentheses after each menu item. Choose the menu item that corre-sponds to the number of nodes in your network.Radio Preference Radio Preference instructs the routing protocol to prefer links on a radio (consider them lower cost than normal). This can be used to help shift traf-ﬁc towards radios running on certain channels.None: None is the default factory setting. All links are considered equally.Medium: Routing protocol is more likely to use this radio to forward trafﬁc.High: Routing protocol is signiﬁcantly more likely to use this radio to forward trafﬁc.

$© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved52 WEB MANAGEMENT INTERFACE REFERENCEACCESS POINT SETTINGS(ADVANCED)MENU ITEM MENU ITEM DESCRIPTION802.11 Access Point (advanced)2.4GHz and 5.8GHz radios can be conﬁgured to function as an 802.11 access point. Standard clients such as laptops with built in 802.11 cards may access this system. If the AP is disabled, the ESSID and Beacon Interval conﬁguration options have no effect. For maximum performance, always disable the 802.11 AP unless it is required. To use a radio as a 802.11 Access Point, the radio MUST be set to a valid 802.11 frequency and the channel width MUST be set to 20MHz.The following ﬁelds are only visible when the 802.11 Access Point is “Enabled.”Mesh Routing (ad-vanced)The Mesh Routing setting enables per radio selection of which radios participate in the multi-hop mesh routing process. In a multi-radio node where the user may only want the mesh running on the backhaul radios, this setting enables the user to speciﬁcally disable the mesh on the client access radios. Be aware that if a node is only accessible via the mesh and mesh routing is disabled, connection will be lost to that node.ESSID (advanced) Sets the name of the network that the access point advertises to clients.ESSID Visibility(advanced)The ESSID can be conﬁgured to be “Visible” or “Hidden.” Generally, the ESSID is conﬁgured to be “Visible” to make it easy for clients to connect to the access point. For additional security/privacy the ESSID can be conﬁgured as “Hidden.”AP Security (advanced) Enables or disables 802.11 security on the Access Point - Only WPA2-PSK (Wi-Fi Protected Access v2 with pre-shared keys) is supported.WPA2 Passphrase(advanced)Sets a shared passphrase when AP Security is set to WPA2 - The passphrase should be an ASCII string of length 8-63 characters, excluding these characters: ‘,”\&/<>AP Broadcast Rate(advanced)Controls the rate at which broadcasts are transmitted from an 802.11 Access Point - Increasing this rate can signiﬁcantly increase network capacity but will reduce the range of client con-nectivity. If the rate is set too high, client devices will have trouble receiving broadcast packets from the 802.11 access point.$

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 53WEB MANAGEMENT INTERFACE REFERENCE AP Beacon Interval (advanced)The 802.11 access point can send beacons at an interval between twice and ten times per second.VLAN ID (advanced) Each 802.11 AP is a VLAN-aware bridge port. Each port is as-signed a VLAN ID. Untagged frames received by the port are tagged with the speciﬁed VLAN ID. Frames that are sent by the port which have a VLAN tag matching the speciﬁed VLAN ID will have their tags removed (i.e. they are sent by the port untagged).VLAN Priority (ad-vanced)Speciﬁes the 802.11 priority of the VLAN tag added to untagged frames received by this portVLAN Trunking (ad-vanced)Controls the ﬁltering of VLAN tagged frames that do NOT match this port’s VLAN ID - Trunking enabled: ALL non-matching VLAN tagged frames are passed (no ﬁltering). Trunking disabled: all non-matching VLAN tagged frames are blocked (ﬁltered).IP Mcast/Bcast Limit (advanced)Deﬁnes the maximum bandwidth allowed for IP multicast or broadcast network trafﬁc received on the given interface and retransmitted onto the Wave Relay® network - Trafﬁc in excess of this limit will be dropped. Units are megabits/sec (Mbps). To disable the limit, set to zero.ETHERNET CONFIGURATION(ADVANCED)MENU ITEM MENU ITEM DESCRIPTIONName (advanced) A name can be assigned to each Ethernet interface.MANET Access(advanced)Controls whether MANET trafﬁc is available on a wired Ethernet port - This setting is useful in cases where the node is physically situated in an insecure location, and you want to prevent casual passersby from eavesdropping on the MANET by physically plugging into the Ethernet port (in this case, be sure to disable access for all wired Ethernet interfaces on the node). The default setting is “Enabled,” i.e. the MANET trafﬁc is available on the Ethernet port. Note: the permanent factory IP address for the node is still available on the Ethernet port, regardless of this setting. In addition, two Wave Relay® nodes connected via wired Ethernet can still communicate via encrypted link regardless of this setting.VLAN ID(advanced)Each Ethernet interface is a VLAN-aware bridge port. Each port is assigned a VLAN ID. Untagged frames received by the port are tagged with the speciﬁed VLAN ID. Frames that are sent by the port which have a VLAN tag matching the speciﬁed VLAN ID will have their tags removed (i.e. they are sent by the port untagged).

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved54 WEB MANAGEMENT INTERFACE REFERENCEVLAN Priority(advanced)Speciﬁes the 802.11 priority of the VLAN tag added to untagged frames received by this portVLAN Trunking (advanced)Controls the ﬁltering of VLAN tagged frames that do NOT match this port’s VLAN ID - Trunking enabled: ALL non-matching VLAN tagged frames are passed (no ﬁltering). Trunking disabled: all non-matching VLAN tagged frames are blocked (ﬁltered).IP Mcast/Bcast Limit (advanced)Deﬁnes the maximum bandwidth allowed for IP multicast or broadcast network trafﬁc received on the given interface and retransmitted onto the Wave Relay® network - Trafﬁc in excess of this limit will be dropped. Units are megabits/sec (Mbps). To disable the limit, set to zero.Routing Metric (advanced)Deﬁnes link capacity for the routing protocol - A value lower than the 100 Mbps default should be used when nodes are connected via non-switched Ethernet (e.g. a third-party point-to-point wireless link). The metric allows the routing protocol to make an intelligent decision whether it is better to route over this Ethernet port or use a faster alternate route.USB ETHERNET (ADVANCED)MENU ITEM MENU ITEM DESCRIPTIONUSB Ethernet Charging PowerControls how an EUD connected via a USB Ethernet cable receives a charge from the node - Should be set to “Always On” for the Samsung Note/Note II/Note III, Motorola EUDs, and Nexus 7 and “Carrier Sense” for the Samsung Galaxy SII 9100G.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 55WEB MANAGEMENT INTERFACE REFERENCE MENU ITEM MENU ITEM DESCRIPTIONDHCP Server ScopeSelects which DHCP clients the DHCP server serves IP addresses to. “Local Ethernet/AP Only” serves IP addresses to nodes connected via Ethernet or a wireless 802.11 Access Point. “Entire Network” serves IP addresses to all nodes in the network. “Local Ethernet/AP Only” is the recommended setting.Address Range StartStart of range of IP addresses assigned to DHCP clientsAddress Range EndEnd of range of IP addresses assigned to DHCP clientsNetmask Netmask assigned to DHCP clientsDefault Gateway Gateway assigned to DHCP clientsDNS Server 1 Primary DNS server assigned to DHCP clientsDNS Server 2 Secondary DNS server assigned to DHCP clientsWINS Server WINS server assigned to DHCP clientsLease Time DHCP lease time (defaults to 1 hour)Show Leases Displays the MAC and IP address of assigned DHCP leasesDHCP SERVER (ADVANCED)If enabled, the DHCP server will serve IP addresses to devices connected to the node via the wired Ethernet or wireless 802.11 Access Point interfaces.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved56WAVE RELAY® OVER IP (WRoIP) (ADVANCED)WRoIP allows the Wave Relay® network to extend over and seamlessly interact with a large routed IP network. In order to use this capability, one or more Wave Relay® nodes must be setup as WRoIP gateways. A WRoIP gateway must be directly connected to an appropriately conﬁgured IP router.See Cloud RelayTM Manual WEB MANAGEMENT INTERFACE REFERENCEMENU ITEM MENU ITEM DESCRIPTIONWRoIP(advanced)WRoIP gateway nodes must have the WRoIP protocol enabled on the interface directly connected to the IP router. All other nodes should have the WRoIP protocol disabled. When the WRoIP protocol is enabled on an interface, the interface will no longer function as a normal Wave Relay® Ethernet port for connecting Ethernet devices: it will only work for connecting the IP router.Multicast Routing Mode (advanced)Selects pruning options for multicast trafﬁc:IP Router Controlled (default): All multicast packets travel to the cloud networkWave Relay Controlled: Only subscribed multicast feeds are passed to the cloud network to reduce network trafﬁc congestion.IP Address(advanced)Deﬁnes the IP address of the WRoIP gateway in the IP subnet speciﬁc to the directly connected IP router interface - WRoIP protocol packets will be sent over the IP network using this IP address.Netmask(advanced)Deﬁnes the netmask of the IP subnet speciﬁc to the directly connected IP router interfaceGateway(advanced)Deﬁnes the IP address of the IP router in the IP subnet speciﬁc to the directly connected IP router interface - WRoIP protocol packets will be forwarded to this IP address in order to be sent over the IP network.MTU(advanced)Deﬁnes the maximum transmissible unit size for the IP network - WRoIP protocol packets sent over the IP network will be limited to this MTU. All nodes that communicate over the IP network should be set to the same value.Multicast Address(advanced)Deﬁnes the multicast IP address used by the WRoIP protocol - The next higher IP multicast address will also be used by the WRoIP protocol. For example, if 239.255.90.67 is set as the multicast address, both 239.255.90.67 and 239.255.90.68 will be used.UDP Port (advanced)Deﬁnes the UDP port used by WRoIP protocol packets

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 57NODE CONFIGURATION FOR DLEPDynamic Link Exchange Protocol (DLEP) (advanced): DLEP is used to transmit characteristics and metrics of the wireless network to a connected DLEP-capable router such as the Cisco 5915. This feature is available on all Wave Relay® versions. It supports DLEP Draft 00.The Wave Relay® MANET operates at Layer 2 of the OSI mode. The DLEP protocol runs between a router and its attached Wave Relay device, allowing the Wave Relay® to communicate link characteristics as they change, and convergence events (acquisition and loss of potential Layer 3 (L3) routing neighbors). Upon receipt of the signal, the local router may take whatever action it deems appropriate, such as initiating L3 discovery protocols, and/or issuing HELLO messages to converge the network on L3. On a continuing, as-needed basis, the Wave Relay devices utilize DLEP to report any characteristics of the link (bandwidth, latency, etc)to the L3 router that have changed. DLEP is independent of the link type and topology supported by the Wave Relay. •DLEP (advanced): Enable/disable the DLEP subsystem.•Local UDP Port (advanced): UDP port on the Wave Relay to receive DLEP trafﬁc from the router.•Router IP Address (advanced): Network address of the DLEP-capable router.•Router UDP Port (advanced): UDP port on the DLEP-capable router for receiving DLEP packets.WEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved58 WEB MANAGEMENT INTERFACE REFERENCEPOSITIONThe node’s position must be speciﬁed in order to provide data to the visualization, CoT, and tracking features. The position may be speciﬁed via internal or external GPS, manually, or from an external feed.Position Mode:MENU ITEM MENU ITEM DESCRIPTIONDetermines the source of local positioning informationUse Internal GPS Instructs node to receive GPS position information from the optional integrated GPS module - This control should not be enabled on a device that does not have an integrated GPS module or if a suitable GPS antenna with satellite connectivity is not attached.Use External GPSInstructs node to receive GPS position information from an external GPS device connected via the node’s onboard serial port - A standard NMEA data stream is supported with the following RS-232 settings: 4800 baud, 8-N-1, no ﬂow control. Higher baud rates are also autodetected. Note that this option is disabled on Wave Relay® units without serial connectors or units already using the serial port for other features (e.g. antenna tracking).Manual Entry Allows manual entry of latitude, longitude, and altitude.Use External FeedInstructs node to receive positioning information over the network via the external Wave Relay® ‘wr-update-gps’ commandUse ESD Feed Instructs node to receive positioning information over the network via a ESD (Exploitation Support Data) feedUse CoT Feed Instructs node to receive positioning information over the network via a CoT (Cursor on Target) feed. This feature is not available on all ﬁrmware versions.Use CDF Feed Instructs node to receive positioning information over the network via Shadow CDF (Common Data Feed)GPS Status Displays the current status of the GPS (only visible in “Use Internal GPS” mode)

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 59WEB MANAGEMENT INTERFACE REFERENCE Latitude Allows the user to manually deﬁne the node’s latitude in decimal degrees (only visible in “Manual Entry” mode)Longitude Allows the user to manually deﬁne the node’s longitude in decimal de-grees (only visible in “Manual Entry” mode)Altitude Allows the user to manually deﬁne the node’s altitude in feet above GPS ellipsoid - approximately equal to feet above mean sea level (MSL) (only visible in “Manual Entry” mode)External Update UDP PortDeﬁnes the port number to receive position updates via the external Wave Relay® ‘wr-update-gps’ command (only visible in “Use External Feed” mode)ESD UDP Port Deﬁnes the port number to receive position updates via an external ESD feed (only visible in “Use ESD Feed” mode)CoT UDP Port Deﬁnes the port number to receive position updates via external CoT feed (only visible in “Use CoT Feed” mode)CDF UDP Port Deﬁnes the port number to receive position updates via an external CDF feed (only visible in “Use CDF Feed” mode)Update Interval Controls how often nodes report information back to visualiziation server with visualization enabled - Smaller values allow ﬁner mobile node movements in Google™ Earth. Shorter update intervals require more bandwidth.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved60 WEB MANAGEMENT INTERFACE REFERENCEWAVE RELAY® SA (GOOGLE™ EARTH NETWORK VISUALIZATION)MENU ITEMMENU ITEM DESCRIPTIONReport to ServerSending visualization updates can be individually enabled or disabled on each node. Setting “Network Default,” allows visualization to be turned on and off for the entire network at once via the Network Default conﬁguration. Note that the selected server IP address is displayed here but is conﬁgured as part of the Network Default conﬁguration. Visualization is also used by the Tracking Antenna system and should be enabled on nodes that you wish to track.Icon The user may select an icon that will be used to identify the node in Google™ Earth.MENU ITEM MENU ITEM DESCRIPTIONSend Position Enables or disables transmission of CoT packets to serverServer IP Deﬁnes the IP address of the CoT server - This IP address can be a unicast or multicast addressServer Port Deﬁnes the UDP port of the CoT serverUID Deﬁnes the contents of the CoT “uid” attributeType Deﬁnes the contents of the CoT “type” attributeVideo Address Deﬁnes the contents of the CoT “Video Address” attributeCURSOR ON TARGET (COT) SETTINGSThis feature enables transmission of local position-ing information to a CoT server on the network. This feature is not available on all ﬁrmware ver-sions.SIMPLE SA PACKET GENERATOR (SSPG) (ADVANCED)These settings exist for backwards compatability with an outdated protocol. See earlier versions of the manual for more information.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 61WEB MANAGEMENT INTERFACE REFERENCE A Master Conﬁguration File allows the user to associate IP addresses, conﬁguration ﬁles, and names with speciﬁc nodes.See RCT Tool ManulCREATING A MASTER CONFIGURATION FILE1. Create a temporary directory in an easy to ﬁnd location with a recognizable name.2. Connect a node to the computer and set conﬁguration as desired.3. Click “Node Conﬁguration” > “Conﬁg Management.”4. Click the “Store” button. A prompt will appear to choose where to save the conﬁguration ﬁle. Save the conﬁguration ﬁle to the directory created in Step 1.5. Repeat steps 2 - 4 for each conﬁguration ﬁle that will be uploaded to nodes. Ensure all conﬁguration ﬁle names are unique.6. In Microsoft Excel, create a spreadsheet with 4 columns: Serial Number, IP address, Proﬁle, and Name.7. For each node to be managed by the Master Conﬁguration File, enter that node’s Serial Number, IP address, the name of the conﬁguration ﬁle saved in Step 4 to be uploaded to the node, and the name of the node. Ensure all IP addresses and names are unique.8. Click “File” > “Save As” and save the spreadsheet as a CSV (Comma delimited) .csv ﬁle with a recognizable name in the directory created in Step1.9. Create a .zip ﬁle containing the CSV ﬁle created in Step 8 and ALL conﬁguration ﬁles created in Step 4.CONFIGURATION MANAGEMENT

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved62UPLOADING A MASTER CONFIGURATION FILE1. Ensure all nodes in the Master Conﬁguration File are in the node list.2. Click “Node Conﬁguration” > “Conﬁg Management.”3. In the Load Conﬁguration menu, select “network (require all)” or “network (any available)” to upload conﬁguration settings to all nodes in the network. The “network (require all)” setting will require all nodes in the network be available for any changes to be applied. If not all nodes are available, no changes will be applied. The “network (any available)” setting will apply changes to available nodes only.4. Click the “Choose File” button to ﬁnd the the .zip ﬁle created in Step 9 above.5. Click the “Load” button to upload conﬁguration settings to other nodes in the network.STORE CONFIGURATION TO FILEClicking the “Store” button allows the web browser to download the node’s conﬁguration settings as an encrypted ﬁle. Environment variables, node lists, and network defaults are stored. THE CRYPTO KEY IS NOT STORED IN THE CONFIGURATION FILE. WEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 63Select the conﬁgurationﬁle to upload.All settings from the conﬁguration ﬁle are written to the device except Node Identiﬁers, which are speciﬁed here.QUICK SETUPBoth “Load Conﬁguration from File” and “Quick Setup” load conﬁguration settings from a conﬁguration ﬁle. The difference between the functions is that “Quick Setup” loads all the conﬁguration settings from a ﬁle (except Node Identiﬁers), whereas “Load Conﬁguration from File” loads user-selected conﬁguration categories. Quick Setup facilitates the conﬁguration of a large number of nodes when the nodes share identical conﬁguration settings. Note speciﬁcally that the only conﬁguration categories that must be speciﬁed when using Quick Setup are Node Identiﬁers, which include IP Address, Node Name, and SSPG SA ID.1. Click “Node Conﬁguration” > “Conﬁg Management.” Scroll down to the “Quick Setup” menu.2. Click the “Base Conﬁguration File” ﬁeld or the “Browse...” button and select the conﬁguration ﬁle to load to the device. Note that the conﬁguration ﬁle should be from a device with the same ﬁrmware version and hardware setup (e.g. numbers and types of radios) as the device to which it is being uploaded.3. Insert the IP Address, Node Name, SSPG SA ID, and SSPG SA Name to be set to the device.4. Click the “Quick Setup” button. All settings from the conﬁguration ﬁle will be applied to the device except IP Address, Node Name, SSPG SA ID, and SSPG SA Name, which will populate from the values speciﬁed.WEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved64The Web Management Interface contains a “Reset to Factory Conﬁguration” feature to remove all custom conﬁguration and restore the node to its factory settings.1. Click “Node Conﬁguration” > “Conﬁg Management.” Scroll to the bottom of the page. Resetting the node to its factory settings will remove all custom conﬁguration and will reset the IP address to 10.4.1.254.2. To retain the node name and IP address after the reset, ensure that the box labelled “Keep node name and IP address” is checked. The node’s Crypto Key will NOT be zeroized. For instructions on how to zeroize the Crypto Key from the Security Conﬁguration page, refer to the “Security” section.3. When you are ready to remove all custom conﬁguration and restore the node to its factory settings, click the “Reset” button. WEB MANAGEMENT INTERFACE REFERENCERESET TO FACTORY CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 65WEB MANAGEMENT INTERFACE REFERENCE TRACKING ANTENNA CONTROLFor information on setting up the Tracking Antenna Control system hardware, please refer to the Tracking Antenna Manual.TRACKING CONFIGURATIONMENU ITEM MENU ITEM DESCRIPTIONTracking Antenna ModeUse this menu to choose the source of the coordinates to track or to return the Pan/Tilt unit to its home position for storage. Possible tracking sources include another Wave Relay®, a ESD (Exploitation Support Data) feed, a CoT (Cursor on Target) feed, or CDF (Common Data Feed).Home Position Returns the Pan/Tilt unit to its home position for storageTrack Node Instructs the node to track another Wave Relay® node position - This function works by receiving Wave Relay® visualization packets from the chosen node. Be sure that the tracked node is conﬁgured to transmit Google™ Earth Network Visualization packets.Track Node w/ Initial Coordi-natesThis setting is the same as the “Track Node” setting (instructs the node to track another Wave Relay® node position), but also allows manual entry of initial coordinates in cases where no position has yet been received from the tracked Wave Relay® node.Track via ESD FeedPoints the antenna based on coordinate data received via an external ESD feedTrack via CoT FeedPoints the antenna based on coordinate data received via an external CoT feedTrack via CDF FeedPoints the antenna based on coordinate data received via an external CDF feedTrack Node Selects a Wave Relay® node to track from the Node ListESD UDP Port Deﬁnes the port number to receive coordinate updates via an external ESD feedTo enable the tracking antenna control system, go to the “Node Conﬁguration” tab and click on the “Tracking Conﬁguration” button. On the drop down menu, select “Enabled” next to the Tracking Antenna Control option.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved66INITIAL COORDINATE SETTINGSThese ﬁelds allow speciﬁcation of the initial antenna target location in cases where coordinates have not yet been received from the tracked node. WEB MANAGEMENT INTERFACE REFERENCEMENU ITEM MENU ITEM DESCRIPTIONInitial Latitude Sets the tracked node’s initial latitude in decimal degreesInitial Longi-tudeSets the tracked node’s initial longitude in decimal degreesInitial Altitude Sets the tracked node’s initial altitude in feet above GPS ellipsoid, which is approximately equal to feet above mean sea level (MSL)FINE TUNING SETTINGSMENU ITEM MENU ITEM DESCRIPTIONCompass TweakDeﬁnes the heading correction factor for tracking, speciﬁed in decimal degrees - Use a positive number for right/clockwise correction and a negative number for left/counterclockwise correction.Elevation TweakDeﬁnes the elevation correction factor for tracking, speciﬁed in decimal degrees - Use a positive number for upward correction and a negative number for downward correction.CoT UDP Port Deﬁnes the port number to receive coordinate updates via an external CoT feedCDF UDP Port Deﬁnes the port number to receive coordinate updates via an external CDF feedCompass Read-ingSpeciﬁes the heading of the Pan/Tilt unit - The heading is deﬁned as the compass reading taken when standing behind the Pan/Tilt unit while fac-ing the large circular electrical connector. For more information, see the compass reading step of the setup procedure.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 67WEB MANAGEMENT INTERFACE REFERENCE PUSH-TO-TALK (PTT)Push-to-Talk (PTT) voice is supported on all Wave Relay® nodes. By default, Wave Relay® supports single-channel PTT voice on a speciﬁed multicast IP address and port. You can “switch channels” by specifying an alternate IP address or port. Users can talk or listen (but cannot do both simultaneously). Transmissions from an individual user are broadcast to all other users on the network. Only one person can talk at a time. If a user tries to talk when another user is transmitting, a busy tone will be heard.To conﬁgure Push-to-Talk settings, click “Node Conﬁguration” > “PTT Conﬁguration.”

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved68 WEB MANAGEMENT INTERFACE REFERENCEPUSH-TO-TALK CONFIGURATIONMENU ITEM MENU ITEM DESCRIPTIONRun PTT subsys-temEnables or disables push-to-talk voiceVolume Deﬁnes the default earpiece volume for headsets - Valid values are 0 through 125 (Values above 100 are digitally ampliﬁed)Microphone Level Deﬁnes the default microphone level for headsets - Valid values are 0 through 100 or “auto.” The “auto” conﬁguration uses automatic gain control for microphone input and is recommended for most users.Transmit ModeTransmit onkeypressAudio is transmitted only when the PTT button is pressed on the headset.Transmit continu-ouslyAudio is continuously transmitted. Other nodes may monitor the channel only. Selected Channel audio transmissions will interrupt monitored continuously transmitted audio.Tones on Transmit Enables or disables an audible checktone (either Beeps or Verbal) at the beginning of each transmitted messageTones on Receive Enables or disables an audible checktone (either Beeps or Verbal) at the beginning of each received messageAdvanced Fea-turesIf advanced features are able to be conﬁgured, a drop down menu will appear. If advanced features are not able to be conﬁgured, a string will appear displaying the current conﬁguration. Available features vary among Wave Relay® hardware versions.Silynx PTT Head-setEnables the serial port on the node (Silynx PTT Headsets require this setting be enabled)MicrophoneVoltageEnables +5V power supply voltage on the center pin of the 6-pin head-set connector (required for some headsets)

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 69CHANNEL DEFINITIONSThe Wave Relay® Network has 16 channels numbered 0 through 15. Channel 0 is the Flash Override Channel and has priority over channels 1-15. The Flash Override Channel will always be enabled and is capable of both receiving and transmitting audio.Channels 1-15 are normal audio channels. Audio channels 1-15 may be conﬁgured to be either Selected Channels or Monitored Channels. Flash Override Channel audio will interrupt both Selected Channel audio and Monitored Channel audio. Each channel is deﬁned by a Multicast Address and a Multicast Port. To display the Multicast Address and Multicast Port ﬁelds, click the “Show Customization” button. After Channel Deﬁnition settings have been conﬁgured, click the “Set All” button.WEB MANAGEMENT INTERFACE REFERENCE MENU ITEMMENU ITEM DESCRIPTIONChannel Displays the channel number to be conﬁguredSelected A Selected Channel is capable of both receiving and transmitting PTT audio. Selected Channel audio will NOT interrupt Flash Override Channel audio. Selected Channel audio will interrupt Monitor Channel audio. A user MUST choose a Selected Channel from channels 1-15.Monitor A Monitored Channel is only capable of receiving audio transmissions. Both Flash Override Channel audio and Selected Channel audio will interrupt Monitored Channel audio. A user may select none to multiple channels to be Monitored Channels.Name Deﬁnes the text name of the channelMulticast AddressDeﬁnes the Multicast Address for the channel (Valid values are within the range of 224.0.0.0 through 239.255.255.255) - Note that each talk group must have a unique multicast address and port. This ﬁeld is only visible if the “Show Customization” button has been clickedMulticast PortDeﬁnes the Multicast UDP port for audio trafﬁc (Valid values are within the range of 1 through 65534) - Note that each talk group must have a unique multicast address and port. This ﬁeld is only visible if the “Show Customiza-tion” button has been clicked.FLASH OVERRIDEFlash Override is a new feature which allows audio to be sent to all nodes even if those nodes have selected a different audio channel.• A ﬂash override transmission is triggered by a “tap-tap-hold” of the PTT button(button is pressed and released twice quickly in succession immediately preceding the normal hold for the duration of the transmission.)• The user will hear a unique “triple” tone on TX and RX to indicate a ﬂash over-ride.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved70 WEB MANAGEMENT INTERFACE REFERENCEAUDIBLE NOTIFICATIONSMENU ITEM MENU ITEM DESCRIPTIONLow Battery Enables or disables audible notiﬁcation when the battery is depleted to 5% (notiﬁcation will occur every 5 minutes)In-Net/Out-Net Enables or disables an audible notiﬁcation when a chosen node enters or leaves the networkNode to Monitor Selects a node to monitor for In-Net/Out-Net audible notiﬁcations from the node list (only visible when In-Net/Out-Net Audible Notiﬁcations are enabled)

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 71RS-232WEB MANAGEMENT INTERFACE REFERENCE The RS-232 serial-over-Ethernet feature can be used for remote control of a distant serial device via the Wave Relay® network. A typical application is for a local PC to control a distant pan/tilt camera via a serial link. If the PC and camera cannot be colocated, then two Wave Relay® devices can be used to connect them (similar to an old-fashioned modem-to-modem link). Thus, the serial port on the local PC can be hardwired to a local Wave Relay® device and the serial port on the distant camera can be hardwired to a distant Wave Relay® device. Communication between the two devices is then relayed via the Wave Relay® network. This is called “serial-to-serial mode.”Alternatively, the PC can run emulation software that allows it to create a local virtual COM port that is conﬁgured to communicate directly with a distant network-enabled serial port (e.g. as described in RFC 2217). Thus, the distant camera is hardwired to a distant Wave Relay® device and the local PC can then connect directly to the distant device via Ethernet. This is called “virtual-to-serial mode.”To access RS-232 conﬁguration settings, click “Node Conﬁguration” > “RS-232 Conﬁguration.”

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved72CONFIGURING SERIAL-TO-SERIAL MODE1. Connect the serial device to be controlled (e.g. pan/tilt unit) to the serial port on the distant Wave Relay® device. Conﬁgure the RS-232 Conﬁguration Mode on the distant Wave Relay device to “Server” and set the Serial-over-Ethernet Port as desired. Set the Serial-over-Ethernet Protocol to “Raw.” Set the serial port parameters (Baud, Data Bits, Parity, Stop Bits, Flow Control) to match those of the connected serial device (factory defaults for the Wave Relay® device are 57600 baud, 8 data bits, no parity, 1 stop bit, no ﬂow control). Click “Save” to store the settings.2. Connect the local serial device (e.g. PC) to the serial port on the local Wave Relay® device. Set the RS-232 Conﬁguration Mode on the local Wave Relay® device to “Client,” and set the Server IP Address and Serial-over-Ethernet Port to be those of the distant Wave Relay® device as conﬁgured in Step 1 above. Also set the serial parameters (Baud, Data Bits, Parity, Stop Bits, Flow Control) to match those of your local serial device. Click “Save” to store the settings. CONFIGURING VIRTUAL-TO-SERIAL MODE1. Connect and conﬁgure the serial device to be controlled (e.g. pan/tilt unit) as per Step 1 above for Conﬁguring Serial-to-Serial mode. Set the Serial-over-Ethernet Protocol to whichever protocol is supported by your virtual client (“Raw” or “Telnet RFC 2217”).2. Install Virtual COM port software on the local PC (Eltima Serial to Ethernet Connector v5.0 for Windows has been tested and is known to work). Conﬁgure the virtual COM port in your software to connect to the distant serial port via the address/port as conﬁgured in Step 1. WEB MANAGEMENT INTERFACE REFERENCESERIAL-TO-SERIAL MODE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 73WEB MANAGEMENT INTERFACE REFERENCE VIRTUAL-TO-SERIAL MODECONFIRMING SERIAL CONNECTIVITYOnce you have conﬁgured the server and client as described above, the network connection status is displayed on the “Current Status” line. Statistics are displayed for transmitted and received bytes to/from the attached serial device, which can be used to debug the connection to your serial hardware. For example, if the “tx” byte count increases but the “rx” byte count remains zero, bytes are being sent out on the Wave Relay® serial port but no reply is being received (possibly due to reversed transmit and receive wires in your cable). To update the status and statistics, click the “Refresh” button.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved74 WEB MANAGEMENT INTERFACE REFERENCEMENU ITEM MENU ITEM DESCRIPTIONModeDisabled The serial-over-Ethernet feature is turned off.Server Use this mode when the device to be controlled (e.g. pan/tilt unit) is connected to a Wave Relay® device serial port.Client Use this mode when a controller (e.g. PC) is connected to a Wave Relay® device serial port.Echo Mode Instructs the serial port to retransmit any received serial data out on its transmit pin (useful for debugging serial connections in cases where Rx/Tx pins might be accidentally reversed in the cable)Serial Port Selects the primary or secondary RS-232 port on the Wave Relay®.Serial-over-Ethernet TCP PortDeﬁnes the TCP port for serial-over-Ethernet trafﬁcServer IP Address Dﬁnes the default IP address of the serial-over-Ethernet serverSerial-over-Ethernet ProtocolRaw Serial messages are encapsulated into packets and are transmitted unaltered over the network. This setting requires that the RS-232 parameters (baud, parity, etc.) be set correctly at both ends. This setting is typically used in serial-to-serial mode, e.g. when a hardware serial controller is used to control a remote serial device.Telnet - RFC2217 Serial messages are encapsulated into packets as per RFC2217, and baud settings are automatically controlled by the protocol. This setting is typically used in serial-to-virtual mode, e.g. when a PC with virtual COM ports is used to control a remote serial device.Baud Valid settings are 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, or 115200.Data Bits Valid settings are 7 or 8 bits.Parity Valid settings are None, Even, or Odd.Stop Bits Valid settings are 1 or 2 bits.Flow Control Valid choices are XON/XOFF (a.k.a. software ﬂow control) or None. Note that RTS/CTS (a.k.a. hardware ﬂow control) is not supported.RS-232 CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 75WEB MANAGEMENT INTERFACE REFERENCE DATE/TIMEWhen possible, Wave Relay® will obtain the current date and time from its internal GPS hardware. However, in cases where the GPS is unlocked (or absent), you may alternatively specify an NTP server or manually set the current date and time. You may also set the local time zone. The default time zone is UTC (a.k.a. GMT or Zulu time). Note that some Wave Relay® device models do not contain a clock, and thus these settings may be unavailable.Wave Relay® also supports a sleep feature that allows scheduling remote unit power down and power up in order to conserve battery life and/or maintain radio silence. Sleep can be performed as a one-time power cycle or can be scheduled for repetitive daily or hourly operation. The sleep feature is not available on all Wave Relay® device models.To access Date/Time Conﬁguration, click “Node Conﬁguration” > “Date/Time.”

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved76 WEB MANAGEMENT INTERFACE REFERENCEMENU ITEM MENU ITEM DESCRIPTIONCurrent System Time Displays the current system time (in both UTC and current time zone if not UTC)Set local timezone Sets the local time zone as ±12 hours from UTC (settings also include select US and other global time zones)Manually set time Manually sets the current local timeNTP Server Address Deﬁnes the address, if available, of the NTP (Network Time Proto-col) server for automatic clock synchronizationScheduled powerdown/powerupOne time only Instructs nodes to perform a one-time power down and power up at speciﬁed times as set in the Set powerdown time and Set powerup time ﬁeldsDaily Instructs nodes to perform a daily powerdown and powerup as speciﬁed in the Set powerdown time and Set powerup time ﬁeldsTwice daily Instructs nodes to perform a twice-daily powerdown and powerup as speciﬁed in the Set powerdown time, Set powerup time, Set 2nd powerdown time, and Set 2nd powerup time ﬁeldsHourly Instructs nodes to perform hourly powerdowns and powerups as speciﬁed in the Set powerdown time and Set powerup time ﬁelds - powerdown and powerup times are speciﬁed as minutes past the hour (00 through 59)Set powerdown time Selects the hour and minute (in local time zone) for unit power-down - If the powerdown/power up frequency is set to “Hourly,” then you may only set minutes past the hour.Set powerup time Selects the hour and minute (in local time zone) for unit powerup - If the powerdown/powerup frequency is set to “Hourly,” then you may only set minutes past the hour. If the powerup time is before the powerdown time, then the powerup happens the next day (or hour).Set 2nd powerdown timeSelects the hour and minute (in local time zone) for second daily power-down - This setting is valid only when power down/power up frequency is set to “Twice Daily.”Set 2nd powerup time Selects the hour and minute (in local time zone) for second daily powerup - If the powerup time is before the powerdown time, then the powerup happens the next day (or hour). This setting is valid only when powerdown/powerup frequency is set to “Twice Daily.”DATE/TIME SETTINGS

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 77WEB MANAGEMENT INTERFACE REFERENCE Any Wave Relay® device (MPU4, MPU3 Single, MPU3 Dual, and Quad Radio Router)may be conﬁgured for use with an ampliﬁer. To access Ampliﬁer Conﬁguration settings, select the “Node Conﬁguration” tab, then click the “Ampliﬁer Conﬁguration” button. The page will display separate sections for each radio so that the ampliﬁer settings for each radio may be conﬁgured separately.Depending on the radios installed in the node, several different options will appear. If the radio installed in the node does not support the use of an ampliﬁer, the section on the page corresponding to that radio will display the message “Ampliﬁer not supported on this Radio.”If the radio installed in the node does support the use of an ampliﬁer, a drop-down menu titled “Ampliﬁer Setting” will appear. On the drop-down menu, select the ampliﬁer setting that matches the ampliﬁer being used with the radio.AMPLIFIER CONFIGURATION

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved78VALID AMPLIFIER SETTINGS ARE:• WR-AMP-0900 900 MHz Ampliﬁer• WR-AMP-1370 1.3 GHz Ampliﬁer• WR-AMP-2400 2.3 - 2.5 GHz AmpliﬁerWhen the Ampliﬁer Conﬁguration page for a QAMP device is accessed from the Web Management Interface, the sections for some radios may display the message “Ampliﬁer Speciﬁed by Pelican Case.” The ampliﬁer settings for these radios have already been conﬁgured.WARNING: WAVE RELAY® AMPLIFIERS REQUIRE REGULATED 28V DC POWER SUPPLY (DEVIATIONS WILL CAUSE DEGRADATION IN PERFORMANCE). WEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 79WEB MANAGEMENT INTERFACE REFERENCE NETWORK STATUSThe “Network Status” tab in the Web Management Interface displays information about every node in the node list. Each time a network status feature is used, all nodes in the node list will attempt to be contacted and the combined results will be displayed on one page. This feature is useful for managing a network without having to individually connect to each node. Refer to the “Node Status” section for more detailed information about a speciﬁc feature.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved80 WEB MANAGEMENT INTERFACE REFERENCEMENU ITEM MENU ITEM DESCRIPTIONNode Node name and IP address of each node in the networkUptime Operating time since last node power on or rebootFirmware Ver-sionFirmware version on nodeTemperature Temperature (in celsius) of nodeSupply Voltage Voltage supplied to nodeRCT Battery VoltageVoltage of real-time-clock keep-alive battery. 3 year shelf life when not poweredSystem Clock Current system time of nodeUNIT INFONEIGHBOR STATUSThe Neighbor Status page displays a list of all neighboring nodes in the network.MENU ITEM MENU ITEM DESCRIPTIONNode Name and IP address of nodeResult • Interface on managed node used• Name of each neighbor node• Interface on the neighbor node used• Receive Signal to Noise Ratio of each connection to each Interface on each neighbor node

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 81WEB MANAGEMENT INTERFACE REFERENCE MENU ITEM MENU ITEM DESCRIPTIONSerial Serial number of all nodes active on MANET networkNode Node name and IP address of each neighbor nodeVector Distance and direction from local node to remote node (Only valid if both nodes have a GPS ﬁx or location)Altitude Altitude (above sea level) of each node in MANET networkNeighbors Number of neighbor nodes (includes neighbors transmitting over the air and via Ethernet)Battery Battery percentage remaining (Only valid when using a MPU4 with compatible smart battery)Receive SNR Signal-to-Noise Ratio at which local node hears remote nodeReverse SNR Signal-to-Noise Ratio at which the local node is heard by the remote nodeMANET MONITORMANET Monitor displays informa-tion about active nodes heard on the MANET.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved82GPS STATUSMENU ITEM MENU ITEM DESCRIPTIONNode Name and IP address of each nodeResultFix Type How node is connected (3D, 2D, or none)Latitude Latitude of current nodeLongitude Longitude of current nodeAltitude Altitude above sea level of current nodeSpeed Speed of node (m/s) in the horizontal planeTrack Path of travel with respect to the Earth expressed in degrees - 000 degrees is North (angle increases clockwise through 360 degrees)Climb Speed of node (m/s) in the vertical planeFix Time When node obtained a satellite ﬁxNumber of satellitesNumber of satellites node is connected toID/PRN ID/PRN of each satellite node is connected toSignal Strength of the connection between node and each satelliteNTP Server Status of the NTP server (available or unavailable) WEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 83WEB MANAGEMENT INTERFACE REFERENCE MENU ITEM MENU ITEM DESCRIP-TIONNode Name and IP address of each nodeResultMbps Total Total Mbps used on this interfaceMbps Wave Relay®Total Mbps used by Wave Relay®Mbps Wave Re-lay® SentMbps used by Wave Relay® to sendMbps Wave Relay® ReceivedMbps used by Wave Relay® to receiveMbps Control Total Mbps used for control functionsMbps Control Ack Mbps used to control ACKMbps Control RTS/CTSMbps used to control RTS/CTSMbps Other Mbps used for other functionsMbps Sent Total Mbps used for all transmissionsMbps Sent Unicast Mbps used for Unicast transmissionsMbps Sent Broad-cast/MulticastMbps used for Broadcast/Multicast transmissionsMbps Received Total Mbps used to receive all transmissionsMbps Received UnicastMbps used to receive Unicast transmissionsMbps Received Broadcast/MulticastMbps used to receive Broadcast/Multicast transmissionsNETWORK TRAFFIC LOADNETWORK VISUALIZATIONThis feature displays situational awareness GPS mapping for all network nodes in Google™ Earth. The drop down menu selects how often Google™ Earth will refresh its data from the visualization server. To access Network Visualization:1. Click the “Network Visualization” button. The browser will attempt to open a ﬁle called “node-monitor.kml.” This ﬁle contains geographic data to be displayed in Google™ Earth. 2. Either open the ﬁle directly from the pop-up dialogue box or save the ﬁle to the computer and open it separately.The management computer must have Google™ Earth installed for this feature to work.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved84 WEB MANAGEMENT INTERFACE REFERENCENETWORK DEFAULT CHECKThe Network Default Check page checks and displays which settings on each node are NOT set to the Network Default values. If a setting shows up in this list, it means that that particular setting on that node is NOT managed by Network Defaults and will NOT be changed if the Network Default is changed.NETWORK CHANNEL PLANThe Channel Plan page displays the channel center frequency and channel width for every radio of every node in the node list. Additionally, if “Network Default” is displayed before the chan-nel information, it means that that set-ting is managed by Network Defaults.MENU ITEMMENU ITEM DESCRIPTIONNode Name and IP address of each nodeResultRadio X Radio(s) in use on each nodeChannel Y/ZChannel center frequency/channel width for each radio

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 85WEB MANAGEMENT INTERFACE REFERENCE STATION LISTThe Station List page displays the list of 802.11 client stations connected to radios with 802.11 access point enabled for each node.IP FLOW LISTThe IP Flow List page displays the list of IP data ﬂows passing through node sorted by measured throughput.MENU ITEM MENU ITEM DESCRIPTIONNode Name and IP address of each nodeResultMbit/s Speed of each IP data ﬂow in MbpsPkt/s Number of packets transferred each second for each IP data ﬂowTotal bytes Number of bytes transferred for each IP data ﬂowDestination IP IP address of destination nodeSource IP IP address of source nodeDirection/InterfacesDirection of and interfaces used by each IP data ﬂow (MANET, Ethernet X, or this node)MENU ITEM MENU ITEM DESCRIPTIONNode Name and IP address of each nodeResultRadio X Radio on the nodemacaddr MAC address of each client device connected to the access pointrssi Signal strength to client devicelast_rx Time (in seconds) since a packet was last received

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved86 WEB MANAGEMENT INTERFACE REFERENCEIP MULTICAST STATUSIP Multicast Status displays IGMP Snooping and IP Multicast Pruning status. This feature shows a table with a row for each multicast group, displaying an “F” if that group is forwarded over the MANET, or a “-” if it is not.There are known issues with IGMP in Windows X P.ATTENTION: PRIOR TO FW VERSION 18.4.0, NETWORK WILL NOT FUNCTION PROPERLY IF PRUNING STATUS IS NOT CONSISTENT THROUGHOUT THE NETWORK.MENU ITEM MENU ITEM DESCRIPTIONNode Name and IP address of each nodeResultGroup Multicast address of nodes con-nected to managed nodeRegistered to receive packets for groupInterface used to receive data for each multicast address (Ethernet X or MANET)WRoIP STATUSWRoIP Status displays the Wave Relay® over IP gateway status for each node.MENU ITEM MENU ITEM DESCRIPTIONNode Name and IP address of each nodeResultGateway Which gateway the node is connected to as well as the priority of that gate-wayElected Whether the gateway is elected or notElection Priority Election priority of the gateway over other gateways/number of other WRoIP gateways on the IP network.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 87The “Network Conﬁguration” tab contains options to manage the network node list, conﬁgure the network defaults, upgrade and reboot the network, and change the network password.NETWORK CONFIGURATIONWEB MANAGEMENT INTERFACE REFERENCE

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved88 WEB MANAGEMENT INTERFACE REFERENCENETWORK NODE LIST WEB MANAGEMENT INTERFACE REFERENCEThe Node List is a list of IP Addresses of nodes managed by the Web Management Interface.1. To manage the Node List, click “Network Conﬁguration” > “Network Node List.”2. Enter the IP Address of a node in the “Manually Add IP(s)” ﬁeld and click the “Add” button to add the node associated with that IP Address to the Node List. Alternatively, nodes may be added from the “Other Nodes on Network” window if they are detected by the network. These nodes may be added individually with the “Selected IPs” button or all at once with the “All” button. The “Clear Nodes” button will clear the “Other Nodes on Network” window.3. Repeat this process for every node to be managed. The IP Addresses will appear in the “Management Node List” window on the left side of the screen (see screenshot). The Node List may be rearranged and edited from the “Management Node List” window.4. When the list is populated with all IP Addresses/Nodes, click the “Push Management List to Network” button to send the Managed IP List to all nodes in the network. Node names auto populate across the network.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 89WEB MANAGEMENT INTERFACE REFERENCE WEB MANAGEMENT INTERFACE REFERENCE NETWORK DEFAULTSNetwork Defaults facilitate the management of a large number of nodes. Network Defaults enable administrators to manage settings on all network nodes speciﬁed in the Node List rather than to manage individual settings on single nodes. Any changes to Network Defaults will affect only nodes that are in the Node List. To ensure proper Network Default conﬁguration, conﬁrm that the Node List is current and conﬁgured properly before making changes to Network Defaults. Note that individual nodes will adopt Network Default settings only if those individual nodes are conﬁgured to use Network Defaults.SHOW/HIDE ADVANCED FIELDSFor convenience, this button allows you to show (or hide) many of the less frequently used node conﬁguration ﬁelds. The default is to hide the advanced ﬁelds (and thus display a briefer page). If you choose to show the advanced ﬁelds, your choice will remain in effect when you revisit the page. Advanced ﬁelds are indicated as such in the descriptions below.MANAGEMENT SETTINGSMENU ITEM MENU ITEM DESCRIPTIONNetmask Deﬁnes default netmask for the Web Management InterfaceGateway Deﬁnes default gateway for the Web Management Interface

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved90 WEB MANAGEMENT INTERFACE REFERENCERADIO CHANNEL SETTINGSMENU ITEM MENU ITEM DESCRIPTIONChannel Name Each channel can be assigned a name which to be used in status func-tions.Frequency Each radio should be a assigned a frequency. Two radios must be set to the same frequency in order to communicate. A warning will be displayed if the frequency setting does not match the radio hardware. A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change center frequency and bandwidth if the settings for “Network Default X” are changed in Network Default conﬁguration.Bandwidth Each radio should be assigned a bandwidth. Two radios must be set to the same bandwidth in order to communicate. Bandwidth should be increased for shorter distances and decreased for increased distances.Max Link Dis-tanceMax Link Distance should be set to the upper bound of how long any individual link in the network may need to be. All nodes on the network MUST be set to the same Max Link Distance. A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change Max Link Distance if the settings for “Network Default X” are changed in Network Default conﬁguration.Channel Density The channel density setting controls how aggressively the radios compete for access to the shared medium. A number of nodes will be displayed in parentheses after each menu item. Choose the menu item that corresponds to the number of nodes in your network. A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change Channel Density if the settings for “Network Default X” are changed in Network Default conﬁguration.Radio Preference Radio Preference instructs the routing protocol to prefer links on a radio (consider them lower cost than normal). This can be used to help shift trafﬁc towards radios running on certain channels.None: None is the default factory setting. All links are considered equally.Medium: Routing protocol is more likely to use this radio to forward trafﬁc.High: Routing protocol is signiﬁcantly more likely to use this radio to forward trafﬁc.A node with a radio channel set to “Network Default X” in node conﬁguration will automatically change Radio Preference if the settings for “Network Default X” are changed in Network Default conﬁguration.Each radio must be a assigned a center frequency and bandwidth. These settings determine the “channel” on which the node operates. Up to 16 Network Default channel settings may be conﬁgured to facilitate management of groups of radios of different nodes.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 91WEB MANAGEMENT INTERFACE REFERENCE DHCP SERVER (ADVANCED)If enabled, the DHCP server will serve IP addresses to devices connected to the node via the wired Ethernet or wireless 802.11 Access Point interfaces.MENU ITEM MENU ITEM DESCRIPTIONDHCP Server ScopeSelects which DHCP clients the DHCP server serves IP addresses to. “Local Ethernet/AP Only” serves IP addresses to nodes connected via Ethernet or a wireless 802.11 Access Point. “Entire Network” serves IP addresses to all nodes in the network. “Local Ethernet/AP Only” is the recommended setting.MANETMENU ITEM MENU ITEM DESCRIPTIONIP Multicast Routing AUTO: Node will prune multicast packets that are not requested (default, most efﬁcient setting for network).PULL ALL MULTICAST: Node will accept all multicast packets it hears on the network. Note: Windows CE/XP computers do not respond to IGMP Multicast Group Queries sent by Wave Relay nodes. “Pull All Multicast” should be used in networks with Windows CE/XP computers to work around this issue.Root Gateway Priority (advanced)HIGH: Any node in your network directly connected to wired infrastructure should have priority set to “HIGH.”MEDIUM: All other non-mobile routers should be set to “MEDIUM.”LOW: Mobile routers should be set to “LOW.”DHCP Server Filter (advanced)ALLOW: Device will pass DHCP messages FROM a DHCP server which is bridged directly by one of its interfaces. Only the devices which are directly wired to the switch where the DHCP server resides need to be set to “ALLOW.”BLOCK: Device will not bridge any DHCP reply packets that it picks up off of any of its bridged interfaces. By setting all of the nodes in the network (except the nodes physically connected to the real DHCP server) to “BLOCK,” you will ensure that users of your system will always use the correct DHCP server.SNAP OUI(advanced)Controls the Subnetwork Access Protocol Organizationally Unique Identiﬁer - The factory OUI, 0018A6, is registered to Persistent Systems, LLC with the IEEE. SNAP OUI is used to identify Wave Relay® packets. Changing this ﬁeld allows the user to obscure which protocol is being used by the system. All nodes must be set to the same value or they will not communicate.

© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved92 WEB MANAGEMENT INTERFACE REFERENCEACCESS POINT (AP) SETTINGS(ADVANCED)MENU ITEM MENU ITEM DESCRIPTION802.11 Access Point (advanced)Each radio can be conﬁgured to function as an 802.11 access point. Standard clients such as laptops with built in 802.11 cards may access this system. If the AP is disabled, the ESSID and Beacon Interval conﬁguration options have no effect. For maximum performance, always disable the 802.11 AP unless it is required. To use a radio as a 802.11 Access Point, the radio MUST be set to a valid 802.11 frequency (Numbered channels in the frequency selection menu i.e. “2412 / 5-20 MHz - Channel 1”) and the channel width MUST be set to 20 MHz.The following ﬁelds are only visible when the 802.11 Access Point is “Enabled.”ESSID (advanced) Sets the name of the network that the access point advertises to clients.ESSID Visibility (advanced) The ESSID can be conﬁgured to be “Visible” or “Hidden.” Generally, the ESSID is conﬁgured to be “Visible” to make it easy for clients to connect to the access point. For additional security/privacy the ESSID can be conﬁgured as “Hidden.”AP Security (advanced) Enables or disables 802.11 security on the Access Point - Only WPA2-PSK (Wi-Fi Protected Access v2 with pre-shared keys) is supported.Address Range StartStart of range of IP addresses assigned to DHCP clientsAddress Range EndEnd of range of IP addresses assigned to DHCP clientsNetmask Netmask assigned to DHCP clientsDefault Gateway Gateway assigned to DHCP clientsDNS Server 1 Primary DNS server assigned to DHCP clientsDNS Server 2 Secondary DNS server assigned to DHCP clientsWINS Server WINS server assigned to DHCP clientsLease Time DHCP lease time (defaults to 1 hour)

$© 2010 - 2015 Persistent Systems, LLC – All Rights Reserved 93WEB MANAGEMENT INTERFACE REFERENCE WPA2 Passphrase (advanced)Sets a shared passphrase when AP Security is set to WPA2 - The passphrase should be an ASCII string of length 8-63 characters, excluding these characters: ‘,”\&/<>AP Broadcast Rate (advanced)Controls the rate at which broadcasts are transmitted from an 802.11 Access Point - Increasing this rate can signiﬁcantly increase network capacity but will reduce the range of client connectivity. If the rate is set too high, client devices will have trouble receiving broadcast packets from the 802.11 access point.AP Beacon Interval (advanced)The 802.11 access point can send beacons at an interval between twice and ten times per second.ETHERNET SETTINGS (ADVANCED)MENU ITEM MENU ITEM DESCRIPTIONRouting Metric (advanced) Deﬁnes link capacity for the routing protocol - A value lower than the 100 Mbps default should be used when nodes are connected via non-switched Ethernet (e.g. a third-party point-to-point wireless link). The metric allows the routing protocol to make an intelligent decision on if it is better to route over this Ethernet port or use an alternate route which is faster.VLAN SETTINGS (ADVANCED)MENU ITEM MENU ITEM DESCRIPTIONVLAN ID (advanced) Each VLAN-aware bridge port is assigned a VLAN ID. Un-tagged frames received by the port are tagged with the speci-ﬁed VLAN ID. Frames that are sent by the port which have a VLAN tag matching the speciﬁed VLAN ID will have their tags removed (i.e. they are sent by the port untagged).VLAN Priority (advanced) Speciﬁes the 802.11 priority of the VLAN tag added to untagged frames received by this portVLAN Trunking (advanced) Controls the ﬁltering of VLAN tagged frames that do NOT match this port’s VLAN ID. When trunking is enabled (trunk port), ALL non-matching VLAN tagged frames are passed (no ﬁltering). When trunking is disabled (access port), all non-matching VLAN tagged frames are blocked (ﬁltered)$

Ubiquiti XR5 2.4GHz Mini PCI module User Manual

Ubiquiti Networks, Inc. 2.4GHz Mini PCI module

Contents

User Manual

Navigation menu

Namespaces

Views

Navigation