NET MODULE NB1601 Router User Manual

NB1601 Router

NetModule Router NB1601
User Manual for Software Version 4.4
Manual Version 1.13
NetModule AG, Switzerland May 20, 2021

NB1601 User Manual for NRSW version 4.4

NetModule Router NB1601
This manual covers all variants of the NB1601 product type.
The specifications and information regarding the products in this manual are subject to change without notice. We would like to point out that NetModule makes no representation or warranties with respect to the contents herein and shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this information This document may contain information about third party products or processes. Such third party information is generally out of influence of NetModule and therefore NetModule shall not be responsible for the correctness or legitimacy of this information. Users must take full responsibility for their application of any products.

Copyright ©2021 NetModule AG, Switzerland All rights reserved

This document contains proprietary information of NetModule. No parts of the work described herein may be reproduced. Reverse engineering of the hardware or software is prohibited and protected by patent law. This material or any portion of it may not be copied in any form or by any means, stored in a retrieval system, adopted or transmitted in any form or by any means (electronic, mechanical, photographic, graphic, optic or otherwise), or translated in any language or computer language without the prior written permission of NetModule.
A large amount of the source code to this product is available under licenses which are both free and open source. Most of it is covered by the GNU General Public License which can be obtained from www.gnu.org. The remainder of the open source software which is not under the GPL, is usually available under one of a variety of more permissive licenses. A detailed license information for a particular software package can be provided on request.
All other products or company names mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective owners. The following description of software, hardware or process of NetModule or other third party provider may be included with your product and will be subject to the software, hardware or other license agreements.

Contact
www.netmodule.com/support

NetModule AG Maulbeerstrasse 10 CH-3011 Bern Switzerland

Tel +41 31 985 25 10 Fax +41 31 985 25 11 info@netmodule.com http://www.netmodule.com

2

NB1601 User Manual for NRSW version 4.4
Contents
1. Welcome to NetModule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1. Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.2. Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.3. Waste Disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.4. National Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.5. Open Source Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3. Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1. Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.2. Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.3. Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.4. Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.4.2. Default LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.4.3. Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.4.4. Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.4.5. Bluetooth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.4.6. WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.4.7. GNSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.4.8. USB 2.0 Host Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.4.9. RJ45 Ethernet Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.4.10.Power Supply (PWR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.4.11.Serial RS-232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.4.12.Digital Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.4.13.Digital Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.4.14.10 Pin Terminal Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.4.15.Extension Port 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.4.16.Extension Port 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 4. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.1. Installation of the Micro-SIM Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.2. Installation of the GSM/UMTS/LTE Antenna . . . . . . . . . . . . . . . . . . . . . . . . 28 4.3. Installation of the WLAN Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.4. Installation of the Bluetooth Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.5. Installation of the GNSS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.6. Installation of the Local Area Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.7. Installation of the Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.1. First Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.1.1. Initial Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.1.2. Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.2. HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 5.3. INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.3.1. WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.3.2. Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 5.3.3. Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.3.4. WLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 5.3.5. Software Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3

NB1601 User Manual for NRSW version 4.4
5.3.6. USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 5.3.7. Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 5.3.8. Digital I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.3.9. Bluetooth Low Energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.3.10.GNSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.4. ROUTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 5.4.1. Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 5.4.2. Extended Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 5.4.3. Multipath Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 5.4.4. Mobile IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 5.4.5. Quality Of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 5.4.6. Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 5.4.7. OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 5.4.8. BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 5.5. FIREWALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.5.1. Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.5.2. Adress/Port Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.5.3. Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 5.5.4. NAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 5.6. VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 5.6.1. OpenVPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 5.6.2. IPsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 5.6.3. PPTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 5.6.4. GRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.6.5. L2TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 5.6.6. Dial-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 5.7. SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.7.1. SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.7.2. DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 5.7.3. DNS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 5.7.4. NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 5.7.5. Dynamic DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 5.7.6. E-Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 5.7.7. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 5.7.8. SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 5.7.9. SSH/Telnet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 5.7.10.SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 5.7.11.Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 5.7.12.MQTT Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 5.7.13.Softflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 5.7.14.Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 5.7.15.Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 5.7.16.ITxPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 5.7.17.Voice Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 5.8. SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 5.8.1. System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 5.8.2. Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 5.8.3. Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 5.8.4. Module Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
4

NB1601 User Manual for NRSW version 4.4
5.8.5. Software Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 5.8.6. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 5.8.7. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 5.8.8. Keys and Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 5.8.9. Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 5.8.10.Legal Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 5.9. LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 6. Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 6.1. General Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 6.2. Print Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 6.3. Getting Config Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 6.4. Setting Config Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 6.5. Checking Config Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 6.6. Getting Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 6.7. Scanning Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 6.8. Sending E-Mail or SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 6.9. Updating System Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 6.10. Manage keys and certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 6.11. Restarting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 6.12. Debug System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 6.13. Resetting System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 6.14. Rebooting System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 6.15. Running Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 6.16. Working with History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 6.17. CLI-PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 A. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 A.1. Abbrevations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 A.2. System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 A.3. Factory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 A.4. SNMP VENDOR MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 A.5. SDK Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
5

NB1601 User Manual for NRSW version 4.4
List of Figures
5.1. Initial Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.2. Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 5.3. WAN Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.4. WAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 5.5. Link Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 5.6. Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 5.7. Ethernet Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 5.8. VLAN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 5.9. LAN IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 5.10. SIMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.11. WWAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.12. WLAN Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 5.13. WLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.14. WLAN IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.15. USB Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 5.16. USB Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 5.17. Serial Port Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 5.18. Serial Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.19. Digital I/O Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.20. Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 5.21. Extended Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 5.22. Multipath Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 5.23. Mobile IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 5.24. Firewall Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5.25. Firewall Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 5.26. Masquerading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 5.27. Inbound NAPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 5.28. OpenVPN Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 5.29. OpenVPN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 5.30. OpenVPN Client Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 5.31. IPsec Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 5.32. IPsec Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.33. PPTP Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 5.34. PPTP Tunnel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 5.35. PPTP Client Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 5.36. Dial-in Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 5.37. SDK Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 5.38. SDK Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5.39. DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 5.40. DNS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 5.41. NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 5.42. Dynamic DNS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 5.43. E-Mail Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 5.44. SMS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 5.45. SSH and Telnet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 5.46. SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
6

NB1601 User Manual for NRSW version 4.4
5.47. Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 5.48. VRRP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 5.49. ITxPT configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 5.50. ITxPT FMStoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 5.51. ITxPT GNSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 5.52. ITxPT Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 5.53. ITxPT VEHICLEtoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 5.54. Voice Gateway Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 5.55. System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 5.56. Regional settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 5.57. User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 5.58. Remote Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 5.59. Manual File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 5.60. Automatic File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 5.61. Factory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 5.62. Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 5.63. Tech Support File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 5.64. Keys and certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 5.65. Certificate Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 5.66. Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
7

NB1601 User Manual for NRSW version 4.4
List of Tables
3.1. Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2. NB1601 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 3.3. NB1601 Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.4. Ethernet Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.5. Mobile Interface EMEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.6. Mobile Interface North America . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.7. Mobile Interface APAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.8. Mobile Antenna Port Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.9. IEEE 802.11 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.10. WLAN Antenna Port Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.11. GNSS Specifications option G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.12. GNSS / GPS Antenna Port Specification . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.13. USB 2.0 Host Port Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.14. Ethernet Port Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.15. Pin Assignments of RJ45 Ethernet Connector . . . . . . . . . . . . . . . . . . . . . . . 21 3.16. Power Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.17. RS-232 Port Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.18. Isolated Digital Outputs Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.19. Isolated Digital Inputs Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.20. Terminal block connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.21. Pin Assignments of Terminal Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.22. Extension Port 1 connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.23. Specification of COMIO Shield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.24. Pin Assignments of COMIO Shield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.25. Specification of 2xCAN Shield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.26. Pin Assignments of 2xCAN Shield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.27. FXS Port Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.28. Pin Assignment of RJ-11 FXS Connector . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1. LTE/UMTS antenna port types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.2. WLAN antenna port types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.20. IEEE 802.11 Network Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 5.48. Static Route Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 5.95. SMS Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 5.105. SMS Number Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 5.157. Certificate Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 5.158. Certificate Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
A.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 A.2. System Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 A.3. SDK Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
8

NB1601 User Manual for NRSW version 4.4
1. Welcome to NetModule
Thank you for purchasing a NetModule Router. This document should give you an introduction to the router and its features. The following chapters describe any aspects of commissioning the device, installation procedure and provide helpful information towards configuration and maintenance. Please find further imformation such as sample SDK script or configuration samples in our wiki on http://wiki.netmodule.com.
9

NB1601 User Manual for NRSW version 4.4
2. Conformity
This chapter provides general information for putting the router into operation.
2.1. Safety Instructions
Please carefully observe all safety instructions in the manual that are marked with the symbol . Compliance information: The NetModule routers must be used in compliance with any and all applicable national and international laws and with any special restrictions regulating the utilization of the communication module in prescribed applications and environments. Information about the accessories / changes to the device: ­ Please only use original accessories to prevent injuries and health risks. ­ Changes made to the device or the use of non-authorized accessories will render the warranty null and void and potentially invalidate the operating license. ­ NetModule routers must not be opened (SIM cards may be used according to the instructions).
10

NB1601 User Manual for NRSW version 4.4
Information about the device interfaces: ­ All systems that are connected to the NetModule router interfaces must meet the
requirements for SELV (Safety Extra Low Voltage) systems. ­ Interconnections must not leave the building nor penetrate the body shell of a vehicle. ­ Connections for antennas may only exit the building or the vehicle hull if transient
overvoltages (according to IEC 62368-1) are limited by external protection circuits down to 1 500 Vpeak. All other connections must remain within the building or the vehicle hull. ­ Always keep a distance of more than 40 cm from the antenna in order to reduce exposure to electromagnetic fields below the legal limits. ­ Devices with a WLAN interface may be operated only with applicable Regulatory Domain configured. Special attention must be paid to country, number of antennas and the antenna gain (see also chapter 5.3.4). The maximum allowed gain is 3dBi in the relevant frequency range. WLAN antennas with a higher amplification may be used with the NetModule router “Enhanced- RF-Configuration” software license and the antenna gain and cable attenuation that have been correctly configured by certified specialized personnel. A misconfiguration will lead to loss of the approval. ­ Cellular antennas attached to the router must have an antenna gain of equal or less than 2.5 dBi. The user is responsible for the compliance with the legal regulations. ­ Only CE-compliant power supplies with a current-limited SELV output voltage range may be used with the NetModule routers.
General safety instructions: ­ Observe the usage limitations of radio units at filling stations, in chemical plants, in
systems with explosives or potentially explosive locations. ­ The devices may not be used in airplanes. ­ Exercise particular caution near personal medical aids, such as pacemakers and hear-
ing aids. ­ The NetModule routers may also cause interference in the nearer distance of TV sets,
radio receivers and personal computers. ­ Never perform work on the antenna system during a thunderstorm. ­ The devices are generally designed for normal indoor use. Do not expose the devices
to extraordinary environmental conditions worse than IP40. ­ Protect them against aggressive chemical atmospheres and humidity or temperatures
outside specifications. ­ We highly recommended creating a copy of a working system configuration. It can be
easily applied to a newer software release afterwards.
11

NB1601 User Manual for NRSW version 4.4
2.2. Declaration of Conformity
NetModule hereby declares that under our own responsibility that the routers comply with the relevant standards following the provisions of the RED Directive 2014/53/EU. The signed version of the Declaration of Conformity can be obtained from http://www.netmodule.com/downloads
2.3. Waste Disposal
In accordance with the requirements of the Council Directive 2012/19/EU regarding Waste Electrical and Electronic Equipment (WEEE), you are urged to ensure that this product will be segregated from other waste at end-of-life and delivered to the WEEE collection system in your country for proper recycling.
2.4. National Restrictions
This product may be generally used in all EU countries (and other countries following the RED Directive 2014/53/EU) without any limitation. Please refer to our WLAN Regulatory Database for getting further national radio interface regulations and requirements for a particular country.
12

NB1601 User Manual for NRSW version 4.4
2.5. Open Source Software
We inform you that NetModule products may contain in part open-source software. We are distributing such open-source software to you under the terms of GNU General Public License (GPL)1, GNU Lesser General Public License (LGPL)2 or other open-source licenses3. These licenses allow you to run, copy, distribute, study, change and improve any software covered by GPL, Lesser GPL, or other open-source licenses without any restrictions from us or our end user license agreement on what you may do with that software. Unless required by applicable law or agreed to in writing, software distributed under open-source licenses is distributed on an “AS IS” basis, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. To obtain the corresponding open source codes covered by these licenses, please contact our technical support at router@support.netmodule.com.
Acknowledgements This product includes:
­ PHP, freely available from http://www.php.net ­ Software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org) ­ Cryptographic software written by Eric Young (eay@cryptsoft.com) ­ Software written by Tim Hudson (tjh@cryptsoft.com) ­ Software written Jean-loup Gailly and Mark Adler ­ MD5 Message-Digest Algorithm by RSA Data Security, Inc. ­ An implementation of the AES encryption algorithm based on code released by Dr Brian Glad-
man ­ Multiple-precision arithmetic code originally written by David Ireland ­ Software from The FreeBSD Project (http://www.freebsd.org)
1Please find the GPL text under http://www.gnu.org/licenses/gpl-2.0.txt 2Please find the LGPL text under http://www.gnu.org/licenses/lgpl.txt 3Please find the license texts of OSI licenses (ISC License, MIT License, PHP License v3.0, zlib License) under
http://opensource.org/licenses
13

NB1601 User Manual for NRSW version 4.4
3. Specifications
3.1. Appearance
Note: Outline with A1-A5 antennas (2x LTE, 2x WLAN/BT, 1x GNSS). Order Number e.g. NB1601LWWtSc-G (with COM/IO shield EXT 1, without extension EXT 2)
14

NB1601 User Manual for NRSW version 4.4
3.2. Features
All models of NB1601 have following standard functionalities: ­ 4x switched FastEthernet (10/100 Mbit/s) ports ­ 2x Micro SIM (3FF) card slots ­ 1x USB 2.0 ­ 1x RS-232 serial interface (3-wire) ­ 1x Digital Input, 1x Digital Output ­ 4 GB internal storage ­ Full featured router software
The NB1601 can be equipped with the following options: ­ 1x LTE,UMTS,GSM ­ 1x WLAN IEEE 802.11 with Bluetooth and Bluetooth Low Energy ­ 1x GNSS ­ 1 Digital Input, 1 Digital Output, RS232 (3-wire) or RS485 (2-wire) SW-configurable (COM/IO shield, Extension 1) ­ 2x CAN (CAN shield, Extension 1) ­ 1x FXS (Extension EXT 2) ­ Software Keys
Due to its modular approach, the NB1601router and its hardware components can be arbitrarily assembled according to its indented usage or application. Please contact us in case of special project requirements.
15

NB1601 User Manual for NRSW version 4.4

3.3. Environmental Conditions

Parameter Input Voltage Operating Temperature Range Storage Temperature Range Humidity Altitude Over-Voltage Category Pollution Degree Ingress Protection Rating

Rating 12 VDC to 24 VDC (-20% / +20%) -40 C to +70 C -40 C to +85 C 0 to 95% (non-condensing) up to 4000m I 2 IP40

Table 3.1.: Environmental Conditions

16

NB1601 User Manual for NRSW version 4.4
3.4. Interfaces
3.4.1. Overview
17

NB1601 User Manual for NRSW version 4.4

Nr. Label 1 EXT 2 2 LED Indicators 3 USB 4 Reset 5 ETH 1- 4 6 MOB 2/ WLAN 2
7 MOB 1
8 BT 9 WLAN 1
10 GNSS 11 EXT 1 12 DO1 13 DI1 14 RS-232 15 PWR 16 SIM

Function Extension interface EXT 2 LED Indicators for the different interfaces USB 2.0 host port, can be used for software/configuration updates. Reboot and factory reset button FastEthernet switch ports, can be used as LAN or WAN interface. SMA female connectors for MIMO LTE 2 antenna or MIMO WLAN 2 antenna. A6 is the main port, A7 is the auxiliary port. SMA female connectors for LTE/UMTS antennas. A1 is the main, A2 the auxiliary port SMA female connector (A3) for Bluetooth. SMA female connectors MIMO WLAN 1 antenna. A3 is the main port, A4 is the auxiliary port. SMA female connector for GNSS antenna Extension interface EXT 1 Digital Output Digital Input RS-232 port Power supply 12-24 VDC. Slots for 2 Micro SIMs (3FF)

Table 3.2.: NB1601 Interfaces

3.4.2. Default LED Indicators The following table describes the default NB1601 status indicators.

Label STAT
WAN
LAN

Color g
g g g g

State Blinking
On On Blinking Off On
Off

Function Device busy; device is in startup, software- or configuration update. The device is ready.
The hotlink connection is up. The hotlink connection is establishing or changing the interface. The hotlink is disabled.
A WLAN access-point or ETH LAN-connection is up. ETH: enabled as LAN and link status is up WLAN: WLAN enabled and configured as access-point. No WLAN or ETH LAN-connection is up.

18

NB1601 User Manual for NRSW version 4.4

Label VPN EXT
SYS

Color g g
gyr

State On
Blinking Off Off
On/ Blinking

Function
VPN connection is up.
VPN is up and waiting for a connection.
VPN connection down.
Extension is disabled.
The EXT LED indicates the state of the extension interfaces: GNSS (default), DIO, CAN, Serial, BLE, âA e or user specific (control via SDK or container) The configuration is done in the UI LED settings. Optional: the signal strength of wireless interfaces could be indicated (LTE, WiFi, BLE, ..).
Shows the overall system state. This could be derived from health indicators such as:
­ all services up and running ­ overall throughput is normal ­ CPU load is normal ­ the supervisor ­ … ­ User application (state set by user in SDK or container)

g

On System operation state: normal

g

Blinking System operation state: during startup

r

On System operation state: emergency, watchdog, failure

Table 3.3.: NB1601 Status Indicators

Ethernet LEDs The following table describes the Ethernet status indicators.

Label S (Speed)
L/A (Link/Activity)

Color y
g
g

State On

Function Link (10 Mbit/s or100 Mbit/s

Off No Link On Link

Blinking Activity Off No Link

Table 3.4.: Ethernet Status Indicators

19

NB1601 User Manual for NRSW version 4.4 3.4.3. Reset The reset button has two functions:
1. Reboot the system: Press at least 3 seconds to release a system reboot. The reboot is indicated with the red blinking STAT LED.
2. Factory reset: Press at least 10 seconds to release a factory reset. The start of the factory reset is confirmed by all LEDs lighting up for a second.
20

NB1601 User Manual for NRSW version 4.4

3.4.4. Mobile The various variants of the NB1601 support multiple multimode modules for mobile communication. EMEA

Standard 4G (LTE) 3G (DC-HSPA+/UMTS) 2G (EDGE/GPRS/GSM)

Bands B1, B3, B5, B7, B8, B20 B1, B2, B5, B8 B5, B8, B3, B2

Table 3.5.: Mobile Interface EMEA

North America
Standard 4G (LTE) 3G (DC-HSPA+/UMTS)

Bands B2, B4, B5, B13, B17 B1, B5
Table 3.6.: Mobile Interface North America

APAC
Standard 4G (LTE) 3G (DC-HSPA+/UMTS) 2G (EDGE/GPRS/GSM)

Bands B1, B3, B5, B7, B8, B28 B1, B2, B5, B8 B5, B8, B3, B2

Table 3.7.: Mobile Interface APAC

The mobile antenna ports have the following specification:

Feature

Specification

Max. allowed cable length

30 m

Max. allowed antenna gain including cable attenuation

2.5 dBi

Min. distance between collocated ra- 20 cm dio transmitter antennas (Example: MOB1 to MOB2)

Min. distance between people and an- 40 cm tenna

Connector type

SMA

Table 3.8.: Mobile Antenna Port Specification

21

NB1601 User Manual for NRSW version 4.4

3.4.5. Bluetooth The NB1601supports Bluetooth 4.2 including Bluetooth Low Energy.

3.4.6. WLAN The variants of the NB1601support a IEEE 802.11a/b/g/n WLAN module.

Standard 802.11a 802.11b 802.11g 802.11n 802.11n

Frequencies 5 GHz 2.4 GHz 2.4 GHz 2.4 GHz 5 GHz

Bandwidth 20 MHz 20 MHz 20 MHz 20 MHz 40 MHz

Max. Data Rate 54 Mbit/s 11 Mbit/s 54 Mbit/s 144 Mbit/s 150 Mbit/s

Table 3.9.: IEEE 802.11 Standards

Note: 802.11n supports 2×2 MIMO in 2.4 GHz and 1×1 in 5 GHz.

The WLAN antenna ports have the following specification:

Feature

Specification

Max. allowed cable length

30 m

Max. allowed antenna gain including cable attenuation

3.0 dBi1

Min. distance between collocated ra- 20 cm dio transmitter antennas (Example: WLAN1 to MOB1)

Min. distance between people and an- 40 cm tenna

Connector type

SMA

Table 3.10.: WLAN Antenna Port Specification

1Note: WLAN antennas with a higher amplification may be used with the NetModule router “Enhanced-RF-Configuration” software license and the antenna gain and cable attenuation that have been correctly configured by certified specialized personnel.
22

NB1601 User Manual for NRSW version 4.4

3.4.7. GNSS

Feature Systems Data stream Tracking sensitivity Supported antennas

Specification GPS/GLONASS/GALILEO/BEIDOU JSON or NMEA up to -162 dBm Active and passive

Table 3.11.: GNSS Specifications option G

The GNSS antenna port have the following specification:

Feature

Specification

Max. allowed cable length

30 m

Max. allowed antenna gain

3.0 dBi

Min. distance between collocated ra- 20 cm dio transmitter antennas (Example: GNSS to MOB1)

Connector type

SMA

Table 3.12.: GNSS / GPS Antenna Port Specification

3.4.8. USB 2.0 Host Port The USB 2.0 host port has the following specification:

Feature Speed Current Max. cable length Cable shield Connector type

Specification Low, Full & Hi-Speed max. 500 mA 3m mandatory Type A

Table 3.13.: USB 2.0 Host Port Specification

23

NB1601 User Manual for NRSW version 4.4

3.4.9. RJ45 Ethernet Connectors

Specification The Ethernet port is specified as follows:

Feature Isolation Speed Mode Crossover Max. cable length Cable type Cable shield Connector type

Specification 1500 VDC 10/100 Mbit/s Half- & Full-Duplex Automatic MDI/MDI-X 100 m CAT5e or better mandatory RJ45

Table 3.14.: Ethernet Port Specification

Pin Assignment

Pin Signal 1 TX+ 2 TX- 3 RX+ 456 RX- 78-
Table 3.15.: Pin Assignments of RJ45 Ethernet Connector
Note: Pairs 4-5 and 7-8 have an internal 75 termination.

24

NB1601 User Manual for NRSW version 4.4

3.4.10. Power Supply (PWR) NB1601 routers have a non-isolated power supply input. It has the following specifications:

Feature Power supply nominal voltages Voltage range Avg. power consumption Max. power consumption Max. cable length Cable shield

Specification 12 VDC and 24 VDC 12 VDC to 24 VDC (-20% / +20%) 7W 10 W 30 m not required

Table 3.16.: Power Specifications

For connector type and pin assignment check chapter 3.4.14.

3.4.11. Serial RS-232 The RS-232 port has the following specification (bold characters show the default configuration):

Feature Protocol Baud rate
Data bits Parity Stop bits Software flow control Hardware flow control Galvanic isolation to enclosure Max. cable length Cable shield

Specification 3-wire RS-232: GND, TXD, RXD 300, 1 200, 2 400, 4 800, 9 600, 19 200, 38 400, 57 600, 115 200, 230 400, 460 800 7 bit, 8 bit none, odd, even 1, 2 none, XON/XOFF none none 10 m not required

Table 3.17.: RS-232 Port Specification

For connector type and pin assignment check chapter 3.4.14.

25

NB1601 User Manual for NRSW version 4.4

3.4.12. Digital Output The isolated digital output ports have the following specification:

Feature Number of outputs
Limiting continuous current Maximum switching voltage Maximum switching capacity Isolation

Specification 1 on-board 1 optional with COM/IO shield (EXT 1) 1A 32 VDC 32 W 1500 Vp (transients)

Table 3.18.: Isolated Digital Outputs Specification

For connector type and pin assignment check chapter 3.4.14.

3.4.13. Digital Input The isolated digital input ports have the following specification:

Feature Number of inputs
Maximum input voltage Minimum voltage for level 1 (set) Maximum voltage for level 0 (not set) Isolation

Specification 1 on-board 1 optional with COM/IO shield (EXT 1) 32 VDC
9 VDC
3 VDC 1500 Vp (transients)

Table 3.19.: Isolated Digital Inputs Specification Note: A negative input voltage is not recognized.

For connector type and pin assignment check chapter 3.4.14.

26

NB1601 User Manual for NRSW version 4.4

3.4.14. 10 Pin Terminal Block

Feature Connector type

Specification 10 pin terminal block header 3.5 mm (screw locking)
Table 3.20.: Terminal block connector

Pin Assignment

DOUT DIn RS-232 PWR

Pin Name Description

1

V+ Power Input

2

VGND Power Ground

3 GND RS-232 GND (non-isolated)

4

RxD RS-232 RxD (non-isolated)

5

TxD RS-232 TxD (non-isolated)

6

DI- Negative signal input (isolated to GND)

7

DI+ Positive signal input (isolated to GND)

8

NO Digital Output isolated, Relay contact normally open

9 COM Digital Output isolated, Relay common

10 NC Digital Output isolated, Relay contact normally closed

Table 3.21.: Pin Assignments of Terminal Block

3.4.15. Extension Port 1

Available Options The NB1601 has an extension connector, following interfaces may be present:

­ Non-isolated RS-232 or RS-485 + 1x digital input and 1x digital output (Option Sc, COM/IO Shield)
­ Dual CAN (Option 2C, Dual CAN Shield)

Extension Port 1 connector

Feature Connector type

Specification
8 pin terminal block header 3.5mm (screw locking)

Table 3.22.: Extension Port 1 connector

27

NB1601 User Manual for NRSW version 4.4

COM/IO Shield (Option Sc) The COM/IO Shield has the following specification:

Feature Feature
RS-232 Signals RS-232 Signal Level RS-232 Bitrate RS-485 Signals RS-485 Signal Level RS-485 Bitrate RS-485 Termination DI Signals DI Level DO Signals DO Level DIO Isolation

Specification 1xRS-232/485 1xdigital input 1xdigital output TX, RX High > 5 VDC, low < -5 VDC Up to 1 Mbit/s A,B Differential output, 1.5 VDC- 3.5 VDC Up to 1 Mbit/s 120 configurable by SW +, Low: 0 VDC- 3 VDC, high: 0 VDC- 32 VDC NO, NC, COM 0-32 VDC/1A 1500 VDC

Table 3.23.: Specification of COMIO Shield

Pin Assignment

Pin Signal 1 RS232 GND 2 RS232 RX (router input); RS485 A (Half-Duplex) 3 RS232 TX (router output); RS485 B (Half-Duplex) 4 In- (Digital Input isolated) 5 In+ (Digital Input isolated) 6 Out NO (Digital Output isolated, Relay contact normally open) 7 Out COM (Digital Output isolated, Relay common) 8 Out NC (Digital Output isolated, Relay contact normally closed)
Table 3.24.: Pin Assignments of COMIO Shield

28

NB1601 User Manual for NRSW version 4.4

2xCAN Shield (Option 2C) The 2xCAN Shield has the following specification:

Feature Features Signals Signal Level Bitrate Termination2
Bus access

Specification 2x CAN V2.0B CANH, CANL High > 2.75 VDC, low < 2.0 VDC Up to 1 Mbit/s No internal bus termination On request: 120 configurable by software Passive (read access only On request: write access

Table 3.25.: Specification of 2xCAN Shield

Pin Assignment

Pin Signal 1- 2 CAN1_H 3 CAN1_L 4 GND 5 CAN2_H 6 CAN2_L 7 GND 8-
Table 3.26.: Pin Assignments of 2xCAN Shield

2Note: On each end of the CAN bus is a 120 termination mandatory
29

NB1601 User Manual for NRSW version 4.4

3.4.16. Extension Port 2

Available Options The NB1601 has one optional extension slot for low end application. One of the following extension modules can be inserted in the EXT2 slot:
­ FXS (Option Fx)
FXS Port Specification (Option Fx)

Feature Ringer Equivalence number Loop current limit TIP-RING voltage Galvanic isolation to enclosure Max. cable length Cable shield Connector type

Specification up to 0.7 REN 23 mA 42 VDC non-isolated 30m not required RJ-11

Table 3.27.: FXS Port Specification

Pin Signal 123 RING 4 TIP 56-
Table 3.28.: Pin Assignment of RJ-11 FXS Connector

30

NB1601 User Manual for NRSW version 4.4

4. Installation
The NB1601is designed for mounting on a DIN rail. Additional mounting holes allow the user to change DIN rail adaptor orientation 90° rotated vs. default position. Please consider the safety instructions in chapter 2 and the environmental conditions in chapter 3.3.
The following precautions must be taken before installing a NB1601 router: ­ Avoid direct solar radiation ­ Protect the device from humidity, steam and aggressive fluids ­ Guarantee sufficient circulation of air around the device ­ The device is for indoor use only
Attention: NetModule routers are not intended for the end consumer market. The device must be installed and commissioned by a certified expert.

4.1. Installation of the Micro-SIM Card
Two Micro-SIM cards can be inserted in a NB1601 router. To install the SIM cards, you will have to remove the SIM cover first. The SIM card connectors have a push to insert, push to eject mechanism. So just push the SIM cards into the connector until it’s fix. The cover should be closed again afterwards.
Warning Please power off the router before inserting the SIM card.

4.2. Installation of the GSM/UMTS/LTE Antenna
NetModule routers will only operate efficiently in the cellular network if there is a good signal. A stub antenna will be suitable for most applications. However, in some circumstances it might be necessary to use remote antennas together with an extended cable (max. 3 meters) to reach a better location offering an adequate signal. In doubt, please contact us and we would be pleased to assist you in figuring out the best matching antenna setup for your application. Keep in mind that effects caused by Faraday cages such as large metal surfaces (elevators, machine housings, etc.), close meshed iron constructions and others may reduce signal reception significantly. The mounted antennas or antenna cables should be fixed with a wrench. The following table shows how to connect the LTE/UMTS antennas. Generally, LTE antennas use both, main and auxiliary ports, but UMTS requires only main ports.

Antenna Port MOB 1 A1 MOB 1 A2 MOB 2 A6

Type Main Auxiliary Main

31

NB1601 User Manual for NRSW version 4.4

Antenna Port MOB 2 A7

Type Auxiliary

Table 4.1.: LTE/UMTS antenna port types

Attention: Following points must be observed when installing the antennas: ­ A minimum clearance of at least 40 cm between people and the antennas must always
be ensured.
­ If one mobile inerface transmit simultaneously with other collocated radio transmitters the separation distance of 20 cm between the antennas must be maintained at all times.
­ Antennas which are installed outside a building or the vehicle hull must limit transient overvoltages (according to IEC 62368-1) to below a peak of 1500 V through external protection circuits.
­ Mobile communications antennas may have an amplification of maximum 2.5dBi, including the cable attenuation, in the relevant frequency range.

4.3. Installation of the WLAN Antennas
The following table shows how to connect the WLAN antennas. The number of attached antennas can be configured in the software. If only one antenna is used, it must be attached to the main port. However, for better diversity and thus better throughput and coverage, we highly recommend using two antennas.

Antenna Port WLAN 1 A3 WLAN 1 A4 WLAN 2 A6 WLAN 2 A7

Type Main Auxiliary Main Auxiliary

Table 4.2.: WLAN antenna port types

32

NB1601 User Manual for NRSW version 4.4
Attention: Following points must be observed when installing the antennas: ­ A minimum clearance of at least 40 cm between people and the antennas must always
be ensured. ­ If one WLAN inerface transmit simultaneously with other collocated radio transmitters
the separation distance of 20 cm between the antennas must be maintained at all times. ­ WLAN antennas must only be installed in buildings or within vehicle hulls. ­ WLAN antennas may have an amplification of maximum 3dBi in the relevant frequency range. WLAN antennas with a higher amplification may be used with the NetModule router “Enhanced-RF-Configuration” software license and the antenna gain and cable attenuation that have been correctly configured by certified specialized personnel.
4.4. Installation of the Bluetooth Antenna
The Bluetooth antenna must be mounted to the connector BT, A3. Only use antennas with cables shorter than 3 meters.
4.5. Installation of the GNSS Antenna
The GNSS antenna must be mounted to the connector GNSS. Whether the antenna is an active or passive GNSS antenna has to be configured in the software. We recommend active GNSS antennas for highly accurate GNSS tracking.
Attention: Following points must be observed when installing the antenna: ­ A minimum clearance of at least 40 cm between people and the antenna must always
be ensured. ­ Antennas which are installed outside a building or the vehicle hull must limit transient
overvoltages (according to IEC 62368-1) to below a peak of 1500 V through external protection circuits.
4.6. Installation of the Local Area Network
Four 10/100 Mbps Ethernet devices can be directly connected to the router, further devices can be attached via an addtional Ethernet switch. Please ensure that the connector has been plugged in properly and remains in a fixed state, you might otherwise experience sporadical link loss during operation. The L/A (Link/Activity) LED will lit up as soon as the device has synced. If not, it might be necessary to configure a different link setting as described in chapter 5.3.2 The S (Speed) LED is on when the link speed is 100 Mbit/s. It’s off when the link speed is at 10 Mbit/s.
33

NB1601 User Manual for NRSW version 4.4
Attention: Only a shielded Ethernet cable may be used.
4.7. Installation of the Power Supply
The router can be powered with an external source supplying between 12 VDC and 24 VDC. It is to be used with a certified (CE or equivalent) power supply, which must have a limited and SELV circuit output.Furthermore, power supply wires attached to V+ and V- inputs of the router must be able to withstand up to 5A current without heating up significantly or damaging its isolation.
Attention: Only CE-compliant power supplies with a current-limited SELV output voltage range may be used with the NetModule routers.
34

NB1601 User Manual for NRSW version 4.4
5. Configuration
The following chapters give information about setting up the router and configuring its features as provided with system software 4.4.
NetModule provides regularly updated router software with new functions, bug fixes and closed vulnerabilities. Please keep your router software up to date. ftp://share.netmodule.com/router/public/system-software/
5.1. First Steps
NetModule routers can be easily set up by using the HTTP-based configuration interface, called the Web Manager. It is supported by the latest web browsers (e.g. Microsoft Internet Explorer 11, Mozilla Firefox 28.0, Safari 7 and many others). Please ensure to have JavaScript turned on. Any submitted configuration via the Web Manager will be applied immediately to the system when pressing the Apply button. When configuring subsystems which require multiple steps (for instance WLAN) you can use the Continue button to store any settings temporarily and apply them at a later time. Please note, that those settings will be neglected at logout unless applied. You may also upload configuration files via SNMP, SSH, HTTP or USB in case you intend to deploy a larger numbers of routers. Advanced users may also use the Command Line Interface (CLI) and set configuration parameters directly. The IP address of Ethernet1 is 192.168.1.1 and the Dynamic Host Configuration Protocol (DHCP) is activated on the interface by default. The following steps need to be taken to establish your first Web Manager session:
1. Connect the Ethernet port of your computer to the Ethernet 1 (FastEthernet) port of the router using a shielded CAT5 cable with RJ45 (or M12) connector.
2. If not yet activated, enable DHCP on your computer’s Ethernet interface so that an IP address can be obtained automatically from the router. This usually takes a short amount of time until your PC has received the corresponding parameters (IP address, subnet mask, default gateway, name server). You may track the progress by having a look to your network control panel and check whether your PC has correctly retrieved an IP address of the range 192.168.1.100 to 192.168.1.199.
3. Launch your favorite web browser and point it to the IP address of the router (the URL is http://192.168.1.1).
4. Please follow the instructions of the Web Manager for configuring the router. Most of the menus are self-explanatory, further details are given in the following chapters.
5.1.1. Initial Access
In factory state you will be prompted for a new administrator password. Please choose a password which is both, easy to remember but also robust against dictionary attacks (such as one that contains numbers, letters and punctuation characters). The password shall have a minimum length of 6 characters. It shall contain a minimum of 2 numbers and 2 letters.
35

NB1601 User Manual for NRSW version 4.4

Admin Password Setup
Please set a password for the admin account. It shall have a minimum length of 6 characters and contain at least 2 numbers and 2 letters.

Username: Enter new password: Confirm new password:
I agree to the terms and conditions

admin

Configure automatic mobile data connection

Apply

NetModule Router Simulator Hostname netbox Software Version 4.4.0.103 © 2004-2020, NetModule AG

NetModule Insights
Subscribe to our mailing and get the latest news about software releases and much more

Figure 5.1.: Initial Login
Please note that the admin password will be also applied for the root user which can be used to access the device via the serial console, telnet, SSH or to enter the bootloader. You may also configure additional users which will only be granted to access the summary page or retrieve status information but not to set any configuration parameters. A set of services (USB Autorun, CLI- PHP) are by default activated in factory state and will be disabled as soon as the admin password has been set. They can be enabled again afterwards in the relevant sections. Other services (SSH, Telnet, Console) can be accessed in factory state by providing an empty or no password.
5.1.2. Recovery
Following actions might be taken in case the router has been misconfigured and cannot be reached anymore:
1. Factory Reset: You can initiate a reset back to factory settings via the Web Manager, by running the command factory-reset or by pressing the reset button. The latter would require a slim

36

NB1601 User Manual for NRSW version 4.4

needle or paper clip which must be inserted into the hole pressed for up to 5 seconds until all LEDs flash up.

. The button must be hold

2. Serial Console Login: It is also possible to log into the system via the serial port. This would require a terminal emulator (such as PuTTY or HyperTerminal) and an RS232 connection (115200 8N1) attached to the serial port of your local computer. You will also see the kernel messages at bootup there.

3. Recovery Image: In severe cases we can provide a recovery image on demand which can be loaded into RAM via TFTP and executed. It offers a minimal system image for running a software update or doing other modifications. You will be provided with two files, recovery-image and recovery-dtb, which must be placed in the root directory of a TFTP server (connected via LAN1 and address 192.168.1.254). The recovery image can be launched from the boot-loader using a

serial connection. You will have to stop the boot process by pressing s and enter the bootloader. You can then issue run recovery to load the image and start the system which can be accessed via HTTP/SSH/Telnet and its IP address 192.168.1.1 afterwards. This procedure can be also initiated by holding the factory reset button longer than 15 seconds.

37

NB1601 User Manual for NRSW version 4.4

5.2. HOME
This page provides a status overview of enabled features and connections.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

Status Summary WAN WWAN WLAN GNSS Ethernet LAN Bridges DHCP OpenVPN IPsec PPTP MobileIP Firewall System

Summary Description LAN2 WWAN1 WLAN1 IPsec1 PPTP1 MobileIP

Administrative Status enabled enabled enabled, access-point enabled enabled, server enabled

Operational Status dialing down up down up down

LOGOUT

NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG
Figure 5.2.: Home
Summary This page offers a short summary about the administrative and operational status of the router’s interfaces. WAN This page offers details about any enabled Wide Area Network (WAN) links (such as the IP addresses, network information, signal strength, etc.) The information about the amount of downloaded/uploaded data is stored in non-volatile memory, thus survive a reboot of the system. The counters can be reset by pressing the Reset button. WWAN This page shows information about modems and their network status. WLAN The WLAN page offers details about the enabled WLAN interfaces when operating in access-point mode. This includes the SSID, IP and MAC address and the currently used frequency and transmit
38

NB1601 User Manual for NRSW version 4.4
power of the interface as well as the list of associated stations. GNSS This page displays the position status values, such as latitude/longitude, the satellites in view and more details about the used satellites. Ethernet This page shows information about the Ethernet interfaces and packet statistics information. LAN This page shows information about the LAN interfaces plus the neighborhood information. Bridges This page shows information about configured virtual bridge devices. Bluetooth This page shows information about Bluetooth interfaces. DHCP This page offers details about any activated DHCP service, including a list of issued DHCP leases. OpenVPN This page provides information about the OpenVPN tunnel status. IPSec This page provides information about the IPsec tunnel status. PPTP This page provides information about the PPTP tunnel status. GRE This page provides information about the GRE tunnel status. L2TP This page provides information about the L2TP tunnel status. MobileIP This page provides information about Mobile IP connections. Firewall This page offers information about any firewall rules and their matching statistics. It can be used to debug the firewall. QoS This page provides information about the used QoS queues. BGP This page provides information about the Border Gateway Protocol.
39

NB1601 User Manual for NRSW version 4.4 OSPF This page provides information about the Open Shortest Path First routing protocol. DynDNS This page provides information about Dynamic DNS. System Status The system status page displays various details of your NB1601 router, including system details, information about mounted modules and software release information. SDK This section will list all webpages generated by SDK scripts.
40

NB1601 User Manual for NRSW version 4.4

5.3. INTERFACES
5.3.1. WAN
Link Management Depending on your hardware model, WAN links can be made up of either Wireless Wide Area Network (WWAN), Wireless LAN (WLAN), Ethernet or PPP over Ethernet (PPPoE) connections. Please note that each WAN link has to be configured and enabled in order to appear on this page.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

WAN Link Management
In case a WAN link goes down, the system will automatically switch over to the next link in order of priority. A link can be either established when the switch occurs or permanently to minimize link downtime. Outgoing traffic can also be distributed over multiple links on a per IP session basis.

Priority Interface 1st LAN2 2nd WWAN1

Operation Mode permanent permanent

Apply

Figure 5.3.: WAN Links

41

NB1601 User Manual for NRSW version 4.4

In general, a link will be only dialed or declared as up if the following prerequisites are met:

Condition Modem is registered Registered with valid service type Valid SIM state Sufficient signal strength Client is associated Client is authenticated Valid DHCP address retrieved Link is up and holds address Ping check succeeded

WWAN X X X X
X X X

WLAN
X X X X X X

ETH
X X X

PPPoE
X X X

The menu can be used further to prioritize your WAN links. The highest priority link which has been established successfully will become the so- called hotlink which holds the default route for outgoing packets.
In case a link goes down, the system will automatically switch over to the next link in the priority list. You can configure each link to be either established when the switch occurs or permanently in order to minimize link downtime.

Parameter 1st priority 2nd priority
3rd priority
4th priority

WAN Link Priorities
The primary link which will be used whenever possible.
The first fallback link, it can be enabled permanently or being dialed as soon as Link 1 goes down.
The second fallback link, it can be enabled permanently or being dialed as soon as Link 2 goes down.
The third fallback link, it can be enabled permanently or being dialed as soon as Link 3 goes down.

Links are being triggered periodically and put to sleep in case it was not possible to establish them within a certain amount of time. Hence it might happen that permanent links will be dialed in background and replace links with lower priority again as soon as they got established. In case of interfering links sharing the same resources (for instance in dual-SIM operation) you may define a switch-back interval after which an active hotlink is forced to go down in order to let the higher-prio link getting dialed again.
We recommend to use the permanent operation mode for WAN links in general. However, in case of time-limited mobile tariffs for instance, the switchover mode might be applicable. By using the distributed mode, it is possible to distribute outgoing traffic over multiple WAN links based on their weight ratio.

42

NB1601 User Manual for NRSW version 4.4

Attention: You can have concurrent WWAN links which share a common recource like one WWAN module using SIM cards of different providers. In that case it would not be possible to find out if the link with the higher priority is available without putting down the low priority link. Therefor such a link will behave like a switchover even if configured as permanent.

For mobile links, it is further possible to pass through the WAN address towards a local host (also called Drop-In or IP Pass-through). In particular, the first DHCP client will receive the public IP address. More or less, the system acts like a modem in such case which can be helpful in case of firewall issues. Once established, the Web Manager can be reached over port 8080 using the WAN address but still over the LAN1 interface using port 80.

Parameter disabled permanent on switchover
distributed

WAN Link Operation Modes Link is disabled Link is being established permanently Link is being established on switchover, it will be dialled if previous links failed Link is member of a load distribution group

Parameter Operation mode Weight Switch-back
Bridging interface1

WAN Link Settings The operation mode of the link
The weight ratio of a distributed link
Specifies the switch-back condition of a switchover link and the time after an active hotlink will be teared down
If WLAN client, the LAN interface to which the WAN link should be bridged.

NetModule routers provide a feature called IP pass-through (aka Drop-In mode). If enabled, the WAN address will be be passed-through to the first DHCP client of the specified LAN interface. As Ethernetbased communication requires additional addresses, we pick an appropriate subnet to talk to the LAN host. In case this overlaps with other addresses of your WAN network, you may optionally specify the network given by your provider to avoid any address conflicts.

Parameter IP Pass-through Interface WAN network WAN netmask

IP Pass-Through Settings Enables or disables IP pass-through Specifies the interface on which the address shall be passed-through Specifies the WAN network Specifies the WAN netmask

1This options requires an Access Point with four address frame format support.

43

NB1601 User Manual for NRSW version 4.4

WAN Settings
This page can be used to configure WAN specific settings like the Maximum Segment Size (MSS). The MSS corresponds to the largest amount of data (in bytes) that the router can handle in a single, unfragmented TCP segment. In order to avoid any negative side effects the number of bytes in the data segment and the headers must not add up to more than the number of bytes in the Maximum Transmission Unit (MTU). The MTU can be configured per each interface and corresponds to the largest packet size that can be transmitted.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

TCP Maximum Segment Size

The maximum segment size defines the largest amount of data of TCP packets (usually MTU minus 40). You may decrease the value in case of fragmentation issues or link-based limits.

MSS adjustment: Maximum segment size:

enabled disabled
1380

Apply

Figure 5.4.: WAN Settings

Parameter MSS adjustment Maximum segment size

TCP MSS Settings Enable or disable MSS adjustment on WAN interfaces. Maximum number of bytes in a TCP data segment.

44

NB1601 User Manual for NRSW version 4.4

Supervision
Network outage detection on a per-link basis can be performed by sending pings on each link to some authoritative hosts. A link will be declared as down in case all trials have failed and only as up if at least one host can be reached.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Link Supervision

Network outage detection can be performed by sending pings on each WAN link to authoritative hosts. The link will be declared as down in case all trials failed. You may further specify an emergency action if a certain downtime is reached.

Link

Hosts

Emergency Action

ANY

8.8.8.8, 8.8.4.4

none

Parameter Link Mode
Primary host Secondary host Ping timeout

Figure 5.5.: Link Supervision
Supervision Settings The WAN link to be monitored (can be ANY) Specifies whether the link shall only be monitored if being up (e.g. for using a VPN tunnel) or if connectivity shall be also validated at connection establishment (default) The primary host to be monitored The secondary host to be monitored (optional) The amount of time in milliseconds a response for a single ping can take, consider to increase this value in case of slow and tardy links (such as 2G connections)

45

NB1601 User Manual for NRSW version 4.4

Parameter Ping interval Retry interval Max. number of failed trials Emergency action

Supervision Settings
The interval in seconds at which pings are transmitted on each interface
The interval in seconds at which pings are re-transmitted in case a first ping failed
The maximum number of failed ping trials until the link will be declared as down
The emergency action which should be taken after a maximum downtime has been reached. Using reboot would perform a reboot of the system, restart link services will restart all link-related applications including a reset of the modem.

46

NB1601 User Manual for NRSW version 4.4

5.3.2. Ethernet
ETH1 usually forms the LAN1 interface which should be used for LAN purposes. Other interfaces can be used to connect other LAN segments or for configuring a WAN link. The LAN10 interface will be available as soon as a pre-configured USB Ethernet device has been plugged in.
Ethernet Port Assignment

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Port Assignment

Link Settings

Ethernet 1 Administrative status: Network interface:
Ethernet 2 Administrative status: Network interface:

enabled disabled LAN1
enabled disabled LAN2

Apply

LOGOUT

Figure 5.6.: Ethernet Ports
This menu can be used to individually assign each Ethernet port to a LAN interface, just in case you want to have different subnets per port or use one port as WAN interface. You may assign multiple ports to the same interface.

47

NB1601 User Manual for NRSW version 4.4

Ethernet Link Settings

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Port Assignment

Link Settings

Link speed for Ethernet 1: Link speed for Ethernet 2:
Apply

auto-negotiated auto-negotiated

LOGOUT

Figure 5.7.: Ethernet Link Settings
Link negotiation can be set for each Ethernet port individually. Most devices support auto-negotiation which will configure the link speed automatically to comply with other devices in the network. In case of negotiation problems, you may assign the modes manually but it has to be ensured that all devices in the network utilize the same settings then.
VLAN Management NetModule routers support Virtual LAN according to IEEE 802.1Q which can be used to create virtual interfaces on top of an Ethernet interface. The VLAN protocol inserts an additional header to Ethernet frames carrying a VLAN Identifier (VLAN ID) which is used for distributing the packets to the associated virtual interface. Any untagged packets, as well as packets with an unassigned ID, will be distributed to the native interface.

48

NB1601 User Manual for NRSW version 4.4

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

VLAN Management

VLAN ID
Interface

LAN1-1

1

Network Interface Priority

LAN1

default

LAN1-2

5

LAN1

background

Mode routed routed

LOGOUT

Figure 5.8.: VLAN Management

In order to form a distinctive subnet, the network interface of a remote LAN host must be configured with the same VLAN ID as defined on the router. Further, 802.1P introduces a priority field which influences packet scheduling in the TCP/IP stack.
The following priority levels (from lowest to highest) exist:

Parameter 0 1 2 3 4 5 6 7

VLAN Priority Levels Background Best Effort Excellent Effort Critical Applications Video (< 100 ms latency and jitter) Voice (< 10 ms latency and jitter) Internetwork Control Network Control

49

NB1601 User Manual for NRSW version 4.4

IP Settings
This page can be used to configure IP addressing for your LAN/WAN Ethernet interfaces. In addition to the primary IP address/subnet mask you may define an additional IP address alias on the interface.
Please keep in mind that the DNS servers can be set globally in the DNS server configuration menu. But as soon as a link comes up it will use the interface- specific name-servers (e.g. the ones being retrieved over DHCP) and update the resolver configuration accordingly.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

IP Address Management

Network Interface

Mode IP Address Mode

LAN1

LAN Static IP

IP Address Netmask 192.168.1.1 24

LAN1-1

LAN Static IP

192.168.101.1 24

LAN1-2

LAN Static IP

192.168.102.1 24

LAN2

WAN DHCP mode

n/a

-1

LOGOUT

Figure 5.9.: LAN IP Configuration

Parameter Mode

LAN IP Settings Defines whether this interface is being used as LAN or WAN interface

When running in LAN mode, the interface may be configured with the following settings:

Parameter IP address Subnet mask Alias IP address

LAN IP Settings The IP interface address The subnet mask for this interface The alias IP interface address

50

NB1601 User Manual for NRSW version 4.4

Parameter Alias subnet mask

LAN IP Settings The alias subnet mask for this interface

When running in WAN mode, the interface may be configured with the following settings:

Parameter WAN mode
MTU

WAN IP Settings
The WAN operation mode, defines whether the interface should run as DHCP client, statically configured or over PPPoE.
The Maximum Transmission Unit for the interface, if provided it will specify the largest size of a packet transmitted on the interface.

When running as DHCP client, no further configuration is required because all IP-related settings (address, subnet, gateway, DNS server) will be retrieved from a DHCP server in the network. You may also define static values but caution has to be taken to assign an unique IP address as it would otherwise raise IP conflicts in the network.

PPPoE is commonly used when communicating with another WAN access device (like a DSL modem). The following settings can be applied:

Parameter User name Password Service name
Access concentrator name

PPPoE Configuration
PPPoE user name for authenticating at the access device
PPPoE password for authenticating at the access device
Specifies the service name set of the access concentrator and can be left blank unless you have multiple services on the same physical network and need to specify the one you want to connect to.
The name of the concentrator (the PPPoE client will connect to any access concentrator if left blank)

51

NB1601 User Manual for NRSW version 4.4

5.3.3. Mobile
Modems Configuration This page lists all available WWAN modems. They can be disabled on demand.
Query This page allows you to send Hayes AT commands to the modem. Besides the 3GPP-conforming AT command-set further modem-specific commands can be applicable which we can provide on demand. Some modems also support running Unstructured Supplementary Service Data (USSD) requests, e.g. for querying the available balance of a prepaid account. SIMs

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Mobile SIMs
This menu can be used to assign a default modem to each SIM which will also be used by SMS and GSM voice services. A SIM card can get switched in case of multiple WWAN interfaces sharing the same modem.

SIM Default SIM1 Mobile1

Current Mobile1

SIM State missing

SIM Lock unknown

Registered no

Update

Figure 5.10.: SIMs
The SIM page gives an overview about the available SIM cards, their assigned modems and the current state. Once a SIM card has been inserted, assigned to a modem and successfully unlocked, the card should remain in state ready and the network registration status should have turned to registered. If

52

NB1601 User Manual for NRSW version 4.4 not, please double-check your PIN. Please keep in mind that registering to a network usually takes some time and depends on signal strength and possible radio interferences. You may hit the Update button at any time in order to restart PIN unlocking and trigger another network registration attempt. Under some circumstances (e.g. in case the modem flaps between base stations) it might be necessary to set a specific service type or assign a fixed operator. The list of operators around can be obtained by initiating a network scan (may take up to 60 seconds). Further details can be retrieved by querying the modem directly, a set of suitable commands can be provided on request.
53

NB1601 User Manual for NRSW version 4.4

Configuration
A SIM card is generally assigned to a default modem but might be switched, for instance if you set up two WWAN interfaces with one modem but different SIM cards. Close attention has to be paid when other services (such as SMS or Voice) are operating on that modem, as a SIM switch will naturally affect their operation. The following settings can be applied:

Parameter PIN code PUK code Default modem Preferred service
Registration mode Network selection

WWAN SIM Configuration
The PIN code for unlocking the SIM card
The PUK code for unlocking the SIM card (optional)
The default modem assigned to this SIM card
The preferred service to be used with this SIM card. Remember that the link manager might change this in case of different settings. The default is to use automatic, in areas with interfering base stations you can force a specific type (e.g. 3G-only) in order to prevent any flapping between the stations around.
The desired registration mode
Defines which network shall be selected. This can be bound to a specific LAI which can be retrieved by running a network scan.

54

NB1601 User Manual for NRSW version 4.4

WWAN Interfaces
This page can be used to manage your WWAN interfaces. The resulting link will pop up automatically as WAN link once an interface has been added. Please refer to chapter 5.3.1 for how to manage them.
The Mobile LED will be blinking during the connection establishment process and goes on as soon as the connection is up. Refer to section 5.8.7 or consult the system log files for troubleshooting the problem in case the connection did not come up.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Mobile Interfaces Interface Modem SIM PDP WWAN1 Mobile1 SIM1 PDP1

Number Service APN / User *99***1# automatic internet.telekom / tm

LOGOUT

Figure 5.11.: WWAN Interfaces

The following mobile settings are required:

Parameter Modem SIM Service type

WWAN Mobile Parameters The modem to be used for this WWAN interface The SIM card to be used for this WWAN interface The required service type

Please note that these settings supersede the general SIM based settings as soon as the link is being dialed.

55

NB1601 User Manual for NRSW version 4.4

Generally, the connection settings are derived automatically as soon as the modem has registered and the network provider has been found in our database. Otherwise, it will be required to configure the following settings manually:

Parameter Phone number
Access point name Authentication Username Password

WWAN Connection Parameters
The phone number to be dialed, for 3G+ connections this commonly refers to be *99***1#. For circuit-switched 2G connections you can enter the fixed phone number to be dialed in international format (e.g. +41xx).
The access point name (APN) being used
The authentication scheme being used, if required this can be PAP or/and CHAP
The user-name used for authentication
The password used for authentication

Furtheron, you may configure the following advanced settings:

Parameter Required signal strength Home network only Negotiate DNS Call to ISDN Header compression
Data compression Client address MTU

WAN Advanced Parameters
Sets a minimum required signal strength before the connection is dialed
Determines whether the connection should only be dialed when registered to a home network
Specifies whether the DNS negotiation should be performed and the retrieved name-servers should be applied to the system
Has to be enabled in case of 2G connections talking to an ISDN modem
Enables or disables 3GPP header compression which may improve TCP/IP performance over slow serial links. Has to be supported by your provider.
Enables or disables 3GPP data compression which shrinks the size of packets to improve throughput. Has to be supported by your provider.
Specifies a fixed client IP address if assigned by the provider
The Maximum Transmission Unit for this interface

56

NB1601 User Manual for NRSW version 4.4

5.3.4. WLAN
WLAN Management In case your router is shipping with a WLAN (or Wi-Fi) module you can operate it either as client, access point, mesh point or certain dual modes. As a client it can create an additional WAN link which for instance can be used as backup link. As access point, it can form another LAN interface which can be either bridged to an Ethernet-based LAN interface or create a self-contained IP interface which can be used for routing and to provide services (such as DHCP/DNS/NTP) in the same way like an Ethernet LAN interface does. As mesh point, it can create a wireless mesh network to provide a backhaul connectivity with dynamic path selection. As dual mode, it is possible to run access point and client or mesh point and access point functionality on the same radio module.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

WLAN Management Administrative status:

Operational mode:

Regulatory domain: Operation type: Radio band: Bandwidth: Channel: Number of antennas: Antenna gain:

Apply

Continue

enabled disabled client access point mesh point dual modes European Union 802.11b 2.4 GHz 20 MHz
Auto
2 0 dB

Channel utilisation

LOGOUT

Figure 5.12.: WLAN Management
If the administrative status is set to disabled, the module will be powered off in order to reduce the overall power consumption. Regarding antennas, we generally recommend using two antennas for better coverage and throughput. A second antenna is definitely mandatory if you want to achieve higher throughput rates as in 802.11n. A WLAN client and a mesh point will automatically became a WAN link and can be managed as described in chapter 5.3.1.

57

NB1601 User Manual for NRSW version 4.4

Configurable parameters for access-point, client mode, mesh point and any dual mode:

Parameter Regulatory Domain Number of antennas Antenna gain
Disable low data rates

WLAN Management Select the country the Router operates in Set the number of connected antennas Specify the antenna gain for the connected antennas. Please refer to the antennas datasheet for the correct gain value. Avoid sticky clients by disabling low data rates.

Warning Please be aware that any inappropriate parameters can lead to an infringement of conformity regulations.

Running as access point or dual mode, you can further configure the following settings:

Parameter Operation type Radio band
Bandwidth Channel Short Guard Interval

WLAN Management Specifies the desired IEEE 802.11 operation mode Selects the radio band to be used for connections, depending on your module it could be 2.4 or 5 GHz Specify the channel bandwidth operation mode Specifies the channel to be used Enables the Short Guard Interval (SGI)

Running as client, you can further configure the following settings:

Parameter Scan channels
2.4 GHz 5 GHz

WLAN Management Select if all supported channels should be scanned or just user defined channels Set the channels which should be scanned in 2.4 GHz Set the channels which should be scanned in 5 GHz

Available operation modes are:

Standard 802.11a 802.11b

Frequencies 5 GHz 2.4 GHz

Bandwidth 20 MHz 20 MHz

Data Rate 54 Mbit/s 11 Mbit/s

58

NB1601 User Manual for NRSW version 4.4

Standard 802.11g 802.11n 802.11n

Frequencies 2.4 GHz 2.4 GHz 5 GHz

Bandwidth 20 MHz 20 MHz 40 MHz

Table 5.20.: IEEE 802.11 Network Standards

Data Rate 54 Mbit/s 144 Mbit/s 150 Mbit/s

59

NB1601 User Manual for NRSW version 4.4

Running as mesh point, you can further configure the following settings:

Parameter Operation type Radio band
Channel

WLAN Mesh-Point Management Specifies the desired IEEE 802.11 operation mode Selects the radio band to be used for connections, depending on your module it could be 2.4 or 5 GHz Specifies the channel to be used

Note: 802.11n with 2×2 MIMO in 2.4 GHz and 1×1 in 5 GHz.

60

NB1601 User Manual for NRSW version 4.4

Prior to setting up an access point, it is always a good idea to run a network scan for getting a list of neighboring WLAN networks and then choose the less interfering channel. Please note that two adequate channels are required for getting good throughputs with 802.11n and a bandwidth of 40 MHz.
WLAN Configuration Running in client mode, it is possible to connect to one ore more remote access-points. The system will switch to the next network in the list in case one goes down and return to the highest-prioritized network as soon as it comes back. You can perform a WLAN network scan and pick the settings from the discovered information directly. The authentication credentials have to be obtained by the operator of the remote access point.

Parameter SSID Security mode WPA/WPA2 mixed mode
WPA cipher
Identity Passphrase
Required signal strength

WLAN Client Configuration The network name (called SSID)
The desired security mode
WPA2 should be preferred over WPA1, running WPA/WPA2 mixedmode offers both.
The WPA cipher to be used, the default is to run both (TKIP and CCMP)
The identity used for WPA-RADIUS and WPA-EAP-TLS
The passphrase used for authentication with WPA-PSK, otherwise the key passphrase for WPA-EAP-TLS
Required signal strength to esablish the connection

The client is performing background scans for the purpose of roaming within an ESS. The background scans are based on the current signal strenght.

Parameter Threshold
Long interval
Short interval

WLAN Client Background Scan Parameters
The signal strength threshold in dBm when the long or short time interval should occur
The time in seconds when a background scan should be performed if the threshold is above the given threshold value
The time in seconds when a background scan should be performed if the threshold is below the given threshold value

61

NB1601 User Manual for NRSW version 4.4

Running in access-point mode you can create up to 4 SSIDs with each running their own network configuration. The networks can be individually bridged to a LAN interface or operate as dedicated interface in routing-mode.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

WLAN Access-Point Configuration

Interface

SSID

WLAN1

NB1600-Private

Security Mode WPA / Cipher

WPA-PSK

WPA + WPA2 / TKIP + CCMP

Figure 5.13.: WLAN Configuration

62

NB1601 User Manual for NRSW version 4.4

This section can be used to configure security-related settings.

Parameter SSID Security mode WPA/WPA2 mixed mode
WPA cipher
Identity Passphrase
Force PMF Hide SSID Isolate clients Band steering master Accounting

WLAN Access-Point Configuration The network name (called SSID) The desired security mode WPA2 should be preferred over WPA1, running WPA/WPA2 mixedmode offers both. The WPA cipher to be used, the default is to run both (TKIP and CCMP) The identity used for WPA-RADIUS and WPA-EAP-TLS The passphrase used for authentication with WPA-PSK, otherwise the key passphrase for WPA-EAP-TLS Enables Protected Management Frames Hides the SSID Disables client-to-client communication The WLAN interface which the client should be steered to Sets accounting profile

The following security modes can be configured:

Parameter Off None WEP WPA-PSK
WPA-RADIUS
WPA-TLS

WLAN Security Modes SSID is disabled
No authentication, provides an open network
WEP (is nowadays discouraged)
WPA-PSK (TKIP, CCMP) aka WPA-Personal/Enterprise, provides password-based authentication
EAP-PEAP/MSCHAPv2, can be used to authenticate against a remote RADIUS server which can be configured in chapter 5.8.2
EAP-TLS, performs authentication using certificates which can be configured in chapter 5.8.8

63

NB1601 User Manual for NRSW version 4.4

Running in mesh point mode, it is possible to connect to one or more mesh points within the mesh network at the same time. The system will automatically join the wireless network, connect to the other mesh partners with the same ID and sercurtiy credentials. The authentication credentials have to be obtained by the operator of the mesh network.

Parameter

WLAN Mesh-Point Configuration

MESHID

The network name (called MESHID)

Security mode

The desired security mode

enable gate announcements To enable gate announcments for the mesh network

64

NB1601 User Manual for NRSW version 4.4

The following security modes can be configured:

Parameter Off None SAE

WLAN Mesh-Point Security Modes MESHID is disabled No authentication, provides an open network SAE (Simultaneous Authentication of Equals) is a secure passwordbased authentication and key establishment protocol

65

NB1601 User Manual for NRSW version 4.4

WLAN IP Settings
This section lets you configure the TCP/IP settings of your WLAN network. A client interface can be run over DHCP or with a statically configured address and default gateway.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

WLAN1 IP Settings Network mode: IP address: Netmask:

Apply

Continue

bridged routed 192.168.200.1 255.255.255.0

LOGOUT

Figure 5.14.: WLAN IP Configuration

The access point networks can be bridged to any LAN interface for letting WLAN clients and Ethernet hosts operate in the same subnet. However, for multiple SSIDs we strongly recommend to set up separated interfaces in routing-mode in order to avoid unwanted access and traffic between the interfaces. The corresponding DHCP server for each network can be configured in afterwards as described in chapter 5.7.2.

Parameter Network mode
Bridge interface
IP address / netmask

WLAN IP Settings
Choose whether the interface shall be operated bridged or in routingmode
If bridged, the LAN interface to which the WLAN network should be bridged
In routing-mode, the IP address and netmask for this WLAN network

66

NB1601 User Manual for NRSW version 4.4

The following feature can be configured if the WLAN interface is bridged

Parameter IAPP Pre-auth

WLAN Bridging features Enables the Inter-Access Point Protocol feature
Enables the pre-authentication mechanism for roaming clients (if supported by the client)

67

NB1601 User Manual for NRSW version 4.4

5.3.5. Software Bridges
Software bridges can be used to bridge layer-2 devices like OpenVPN TAP, GRE or WLAN interfaces without the need for a physical LAN interface.
Bridge Settings This page can be used to enable/disable software bridges. It can be configured as follows:

Parameter Administrative status IP Address Netmask MTU

Bridge Settings
Enables or disables the bridge interface. If you need an interface to the local system you need to define an IP address for the local device.
IP address of the local interface (available only if “Enabled with local interface” was selected
Netmask of the local interface (available only if “Enabled with local interface” was selected
Optional MTU size for the local interface (available only if “Enabled with local interface” was selected

68

NB1601 User Manual for NRSW version 4.4

5.3.6. USB
NetModule routers ship with a standard USB host port which can be used to connect a storage, network or serial USB device. Please contact our support in order to get a list of supported devices.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Administration USB Administration

Devices

Autorun

This menu can be used to activate USB-based serial and network devices.

Administrative status:

enabled disabled

Enable hotplug:

Apply

LOGOUT

USB Administration
Parameter Administrative status Enable hotplug

Figure 5.15.: USB Administration
USB Administration Specifies whether devices shall be recognized Specifies whether device shall be recognized if plugged in during runtime or only at bootup

69

NB1601 User Manual for NRSW version 4.4

USB Devices
This page show the currently connected devices and it can be used to enable a specific device based on its Vendor and Product ID. Only enabled devices will be recognized by the system and raise additional ports and interfaces.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Administration

Devices

Autorun

Connected USB Devices Vendor ID Product ID Bus ID Manufacturer

Device

Enabled USB Devices Vendor ID Product ID Bus ID Module

Type

Refresh

LOGOUT
Type Attached

Figure 5.16.: USB Device Management

Parameter Vendor ID Product ID Module

USB Devices The USB Vendor ID of the device The USB Product ID of the device The USB module and type of driver to be applied for this device

Any ID must be specified in hexadecimal notation, wildcards are supported (e.g. AB[0-1][2-3] or AB*) A USB network device will be referenced as LAN10.

70

NB1601 User Manual for NRSW version 4.4
USB Autorun This feature can be used to automatically launch a shell script or perform a software/config update as soon as an USB storage stick has been plugged in. For authentication, a file called autorun.key must exist in the root directory of a FAT16/32 formatted stick. It can be downloaded from that page and holds the SHA256 hash key of the admin password. The file can hold multiple hashes which will be processed line-by-line during authentication which can be used for setting up more systems with different admin passwords. For new devices with an empty password the hash key e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 can be used. The hash keys can be generated by running the command echo -n “<admin- password>” | sha256sum on a Linux system or an Internet hash key generator (search for “sha-256 hash calculator”). Once authentication has succeeded, the system scans for other files in the root directory which can perform the following actions:
1. For running a script: autorun.sh 2. For a configuration update: cfg-.zip (e.g. cfg-00112B000815.zip), or if not avail-
able cfg.zip 3. For a software update: sw-update.img
71

NB1601 User Manual for NRSW version 4.4

5.3.7. Serial Port This page can be used to manage your serial ports. A serial port can be used by:

Parameter none login console
device server modem bridge modem emulator
SDK

Serial Port Usage
The serial port is not used
The serial port is used to open a console which can be accessed with a serial terminal client from the other side. It will provide helpful bootup and kernel messages and spawns a login shell, so that users can login to the system. If more than one serial inrterface is available, one serial interface can be configured as ‘login console’ at a time.
The serial port will be exposed over a TCP/IP port and can be used to implement a Serial/IP gateway.
Bridges the Serial Interface to the Modem TTY of an intergrated WWAN Modem.
Emulates a classical AT command driven modem on the serial interface. See http://wiki.netmodule.com/app-notes/hayes-modemat-simulator for detailed information.
The serial port will be reserved for SDK scripts.

72

NB1601 User Manual for NRSW version 4.4

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Administration

Port Settings

SERIAL1 is used by:

Apply

Back

none login console device server modem emulator SDK

Figure 5.17.: Serial Port Administration

LOGOUT

73

NB1601 User Manual for NRSW version 4.4

Running a device server, the following settings can be applied:

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges USB Serial Digital I/O GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Administration

Port Settings

SERIAL1 Port Settings

Physical protocol: Baud rate: Data bits: Parity: Stop bits: Software flow control: Hardware flow control: Server Configuration Protocol on IP port: Port:
Timeout: Allow remote control (RFC 2217): Show banner:
Allow clients from:

Apply

RS232 115200 8 data bits None 1 stop bit None None

Telnet

2000

endless

numbered

600

everywhere specify

Figure 5.18.: Serial Port Settings

LOGOUT

Parameter Physical protocol Baud rate Data bits Parity
Stop bits

Serial Settings Selects the desired physical protocol on the serial port Specifies the baud rate run on the serial port Specifies the number of data bits contained in each frame Specifies the parity used for every frame that is transmitted or received Specifies the number of stop bits used to indicate the end of a frame
74

NB1601 User Manual for NRSW version 4.4

Parameter Software flow control
Hardware flow control Protocol on TCP/IP Port Timeout

Serial Settings
Defines the software flow control for the serial port, XOFF will send a stop, XON a start character to the other end to control the rate of any incoming data
You may enable RTS/CTS hardware flow control, so that the RTS and CTS lines are used to control the flow of data
You may choose the IP protocols Telnet or TCP raw for the device server
The TCP port for the device server
The timeout until a client is declared as disconnected

Parameter Protocol on IP port Port Timeout
Allow remote control Show banner Stop bits Allow clients from

Server Settings Selects the desired IP protocol (TCP or Telnet) Specifies the TCP port on which the server will be available The time in seconds before the port will be disconnected if there is no activity on it. A zero value disables this function. Allow remote control (ala RFC 2217) of the serial port Show a banner when clients connect Specifies the number of stop bits used to indicate the end of a frame Specifies which clients are allowed to connect to the server

Please note that the device server does not provide authentication or encryption and clients will be able connect from everywhere. Please consider to restrict access to a limited network/host or block packets by using the firewall.

75

NB1601 User Manual for NRSW version 4.4

When running the serial port as AT modem emulator the following settings can be applied:

Parameter Physical protocol Baud rate Hardware flow control

Serial Port Settings Selects the desired physical protocol on the serial port Specifies the baud rate run on the serial port You may enable RTS/CTS hardware flow control, so that the RTS and CTS lines are used to control the flow of data

Parameter Port

Incoming connections via Telnet The TCP port for the device server

Parameter Number IP address Port

Phonebook Entries Phone number that will get an alias IP address the number will become Port value for the IP address

76

NB1601 User Manual for NRSW version 4.4

5.3.8. Digital I/O
The Digital I/O page displays the current status of the I/O ports and can be used to turn output ports on or off.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

WAN Link Management Supervision Settings
Ethernet Port Setup VLAN Management IP Settings
Mobile Modems SIMs Interfaces
WLAN Administration Configuration IP Settings
Bridges
USB
Serial
Digital I/O
GNSS
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Digital I/O Status DI1: DI2: DO1: DO2:
Digital I/O Configuration
DO1 after reboot: DO2 after reboot:
Apply

off on

off

turn on

on

turn off

default default

LOGOUT

Figure 5.19.: Digital I/O Ports

You can apply the following settings:

Parameter DO1 after reboot DO2 after reboot

Digital I/O Settings Initial status of DO1 after system has booted Initial status of DO2 after system has booted

Besides on and off you may keep the default status as the hardware has initialized it after power-up. The digital inputs and outputs can also be monitored and controlled by SDK scripts.

77

NB1601 User Manual for NRSW version 4.4

5.3.9. Bluetooth Low Energy
If a Bluetooth interface is available it can be used either with the SDK scripting engine or forwarded to the Virtualization.
Bluetooth Settings This page can be used to assign the Bluetooth module either to SDK or Virtualization or to turn Bluetooth functionality off. It can be configured as follows:

Parameter Administrative status

Bluetooth Settings Enables the module for SDK or Virtualization

If you enable the module for SDK usage you need a SDK script that handles the hardware interface. You can start advertising or scanning mode and setup parameters via SDK. Please have a look at the SDK API for detailed description.
If you enable the module for Virtualization there will be no interaction to the module from the host system. It is in your responsibility to use it correctly. Please refer to our examples and documentation in the public Wiki.

78

NB1601 User Manual for NRSW version 4.4

5.3.10. GNSS

Administration
The GNSS page lets you enable or disable the GNSS modules present in the system and can be used to configure the daemon that can be used to share access to receivers without contention or loss of data and to respond to queries with a format that is substantially easier to parse than the NMEA 0183 emitted directly by the GNSS device.
We are currently running the Berlios GPS daemon (version 3.15), supporting the new JSON format. Please navigate to http://www.catb.org/gpsd/ for getting more information about how to connect any clients to the daemon remotely. The position values can also be queried by the CLI and used in SDK scripts.

Parameter Administrative status Operation mode Antenna type Accuracy
Fix frame interval

GNSS Module Configuration
Enable or disable the GNSS module
The mode of operation, either standalone or assisted (for A-GPS)
The type of the connected GPS antenna, either passive or actively 3 volt powered
The GNSS receiver compares the calculated position accuracy based on the satellite information and compares it with this accuracy threshold in meters. If the calculated position accuracy is better than the accuracy threshold, the position is reported. Adjust this parameter to a higher threshold in case the GNSS receiver does not report a position fix, or when it takes a long time to calculate a fix. This could be caused when there is no clear sky view of the GNSS antenna which is the case in tunnels, beside tall buildings, trees, and so on.
The amount of time to wait between fix attempts

If the GNSS module does support AssistNow and the operation mode is assisted the following configuration can be done:

Parameter Primary URL Secondary URL

GNSS Assisted GPS Configuration The primary AssistNow URL The secondary AssistNow URL

Information about AssistNow: If you have a lot of devices in the field that use the AssistNow service, please consider creating your own AssistNow token at http://www. u-blox.com. If there are too many requests per time, the service may not work as expected. If you have further questions, please contact our support.

Parameter Server port

GNSS Server Configuration
The TCP port on which the daemon is listening for incoming connections

79

NB1601 User Manual for NRSW version 4.4

Parameter Allow clients from
Clients start mode

GNSS Server Configuration
Specifies where clients can connect from, can be either everywhere or from a specific network
Specifies how data transferal is accomplished when a client connects. You can specify on request which typically requires an R to be sent. Data will be sent instantly in case of raw mode which will provide NMEA frames or super-raw which includes the original data of the GPS receiver. If the client supports the JSON format (i.e. newer libgps is used) the json mode can be specified.

Please consider to restrict access to the server port, either by a specifying a dedicated client network or by using a firewall rule.

80

NB1601 User Manual for NRSW version 4.4

Position This pages provides further information about the satellites in view and values derived from them:

Parameter Latitude Longitude Altitude Satellites in view Speed
Satellites used
Dilution of precision

GNSS Information The geographic coordinate specifying the north-south position The geographic coordinate specifying the east-west position The height above sea level of the current location The number of satellites in view as stated in GPGSV frames The horizontal and vertical speed in meter per second as stated in GPRMC frames The number of satellites used for calculating the position as stated in GPGGA frames The dilution of precision as stated in GPGSA frames

Furtheron, each satellite also comes with the following details:

Parameter PRN Elevation Azimuth SNR

GNSS Satellite Information
The PRN code of the satelitte (also referred as satellite ID) as stated in GPGSA frames
The elevation (up-down angle between the dish pointing direction) in degrees as stated in GPGSV frames
The azimuth (rotation around the vertical axis) in degrees as stated in GPGSV frames
The SNR (Signal to Noise Ratio), often referred as signal strength

Please note that the values are shown as calculated by the daemon, their accuracy might be suggestive.
Supervision

Parameter Administrative status Mode Max. downtime
Emergency action

GNSS Supervision
Enable or disable GNSS supervision
Specifies whether to monitor the NMEA stream or GPS fixes
The period of time without valid NMEA stream or GPS fix after which an emergency action shall be taken
The corresponding emergency action. You can either let just restart the server, which will also re-initialize the GPS function on the module, or reset the module in severe cases. Please note that this may have effects on any running WWAN/SMS services.

81

NB1601 User Manual for NRSW version 4.4

5.4. ROUTING
5.4.1. Static Routes
This menu shows all routing entries of the system. They are typically formed by an address/netmask couple (represented in IPv4 dotted decimal notation) which specify the destination of a packet. The packets can be directed to either a gateway or an interface or both. If interface is set to ANY, the system will choose the route interface automatically, depending on the best matching network configured for an interface.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

Static Routes Extended Routes Multipath Routes Multicast
IGMP Proxy Static Routes BGP OSPF Mobile IP Administration QoS Administration Classification

Static Routes

This menu shows all routing entries of the system, they can consist of active and configured ones. The flags are as follows: (A)ctive, (P)ersistent, (H)ost Route, (N)etwork Route, (D)efault Route (Netmasks can be specified in CIDR notation)

Destination Netmask

Gateway

Interface Metric Flags

192.168.1.0 255.255.255.0 0.0.0.0

LAN1 0 AN

192.168.101.0 255.255.255.0 0.0.0.0

LAN1-1 0 AN

192.168.102.0 255.255.255.0 0.0.0.0

LAN1-2 0 AN

192.168.200.0 255.255.255.0 0.0.0.0

WLAN1 0 AN

Route lookup

NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG
Figure 5.20.: Static Routing
In general, host routes precede network routes and network routes precede default routes. Additionally, a metric can be used to determine the priority of a route, a packet will go in the direction with the lowest metric in case a destination matches multiple routes. Netmasks can be specified in CIDR notation (i.e. /24 expands to 255.255.255.0).

82

NB1601 User Manual for NRSW version 4.4

Parameter Destination Netmask
Gateway Interface Metric Flags

Static Route Configuration
The destination address of a packet
The subnet mask which forms, in combination with the destination, the network to be addressed. A single host can be specified by a netmask of 255.255.255.255, a default route corresponds to 0.0.0.0.
The next hop which operates as gateway for this network (can be omitted on peer-to-peer links)
The network interface on which a packet will be transmitted in order to reach the gateway or network behind it
The routing metric of the interface (default 0), higher metrics have the effect of making a route less favorable
(A)ctive, (P)ersistent, (H)ost Route, (N)etwork Route, (D)efault Route

The flags obtain the following meanings:

Flag

Description

A

The route is considered active, it might be inactive if the interface for this route is not yet

up.

P

The route is persistent, which means it is a configured route, otherwise it corresponds to

an interface route.

H

The route is a host route, typically the netmask is set to 255.255.255.255.

N

The route is a network route, consisting of an address and netmask which forms the

subnet to be addressed.

D

The route is a default route, address and netmask are set to 0.0.0.0, thus matching any

packet.

Table 5.48.: Static Route Flags

83

NB1601 User Manual for NRSW version 4.4

5.4.2. Extended Routing Extended routes can be used to perform policy-based routing, they generally precede static routes.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

Static Routes Extended Routes
Multipath Routes Multicast
IGMP Proxy Static Routes BGP OSPF Mobile IP Administration QoS Administration Classification

Extended Routes

Extended routes can be used to perform policy-based routing. In general, they precede any other static routes.

Interface Source

Destination

TOS Route to

ANY

4.4.4.4/32

8.8.8.8/32

any WWAN1

NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Figure 5.21.: Extended Routing

In contrast to statis routes, extended routes can be made up, not only of a destination address/netmask, but also a source address/netmask, incoming interface and the type of service (TOS) of packets.

Parameter Source address Source netmask Destination address Destination netmask Incoming interface Type of service Route to
discard if down

Extended Route Configuration The source address of a packet The source address of a packet The destination address of a packet The destination address of a packet The interface on which the packet enters the system The TOS value within the header of the packet Specifies the target interface or gateway to where the packet should get routed to Discard packets if the specified interface is down

84

NB1601 User Manual for NRSW version 4.4

5.4.3. Multipath Routes
Multipath routes will perform weighted IP-session distribution for particular subnets across multiple interfaces.

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

Static Routes Extended Routes Multipath Routes Multicast
IGMP Proxy Static Routes BGP OSPF Mobile IP Administration QoS Administration Classification

Multipath Routes Multipath routes will perform weighted IP-session distribution for particular subnets across multiple interfaces.

Destination 8.8.4.4/32

Distribution
WWAN1 (50%) LAN2 (50%)

NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Figure 5.22.: Multipath Routes

At least two interfaces have to be defined to establish multipath routing. Additional interfaces can be added by pressing the plus sign.

Parameter Target network/netmask Interface Weight NextHop

Add Multipath Routes Defines the target network for which multipath routing shall be applied Selects the interface for one path Weight of the interface in relation to the others Overrides the default gateway of this interface

85

NB1601 User Manual for NRSW version 4.4

5.4.4. Mobile IP
Mobile IP (MIP) can be used to enable seamless switching between different kinds of WAN links (e.g. WWAN/WLAN). The mobile node hereby remains reachable via the same IP address (home address) at any time, independently of the WAN link being used. Effectively, any WAN link switch causes very small outages during switchover while keeping all IP connections alive.

Moreover, NetModule routers also support NAT-Traversal for mobile nodes running behind a firewall (performing NAT), which makes mobile nodes even there accessible from a central office via their home address, and thus, bypassing any complicated VPN setups.

The home agent accomplishes this by establishing a tunnel (similar to a VPN tunnel) between itself and the mobile node. WAN link switching works by telling the home agent that the WAN IP address (called the care-of address in MIP terms) of the mobile node has changed. The home agent will then encapsulate packets destined to a mobile node’s home address into a tunnel packet containing the current care-of address of the mobile node as its destination address.

To prevent problems with firewalls and private IP addressing, the MIP implementation always employs reverse tunneling, which means that all traffic sent by a mobile node is relayed via the tunnel to the home agent instead of directly being conveyed to the final destination. This fact also empowers MIP to be used as a lightweight VPN replacement (without payload secrecy).

The MIP implementation supports RFCs 3344, 5177, 3024 and 3519. For applications requiring vast numbers of mobile nodes, interoperability with the Cisco 2900 Series home agent implementation has been verified. However, since NetModule routers implement a mobile node as well as a home agent, a MIP network with up to 10 mobile nodes can be implemented without requiring expensive third party routers.

If MIP is run as a mobile node, the following settings can be configured:

Parameter

Mobile IP Configuration

Primary home agent ad- The address of the primary home agent dress

Secondary home agent ad- The address of the secondary home agent. The mobile node will try to

dress

register with this home agent, if the primary home agent is not reach-

able.

Home address

The permanent home address of the mobile node which can be used to reach the mobile router at any time

SPI

The Security Parameter Index (SPI) identifying the security context for

the mobile IP tunnel between the mobile node and the home agent.

This is used to distinguish mobile nodes from each other. Therefore

each mobile node needs to be assigned a unique SPI. This is a 32-bit

hexadecimal value.

Authentication type

The used authentication algorithm. This can be prefix-suffix-md5 (default for MIP) or hmac-md5.

86

NB1601 User Manual for NRSW version 4.4

Parameter Shared secret
Life time UDP encapsulation Mobile network address
Mobile network mask

Mobile IP Configuration
The shared secret used for authentication of the mobile node at the home agent. This can be either a 128-bit hexadecimal value or a random length ASCII string.
The lifetime of security associations in seconds
Specifies whether UDP encapsulation shall be used or not. To allow NAT traversal, UDP encapsulation must be enabled.
Optionally specifies a subnet which should be routed to the mobile node. This information is forwarded via Network Mobility (NEMO) extensions to the home agent. The home agent can then automatically add IP routes to the subnet via the mobile node. Note that this feature is not supported by all third party home agent implementations.
The network mask for the optional routed network

87

NB1601 User Manual for NRSW version 4.4

If MIP is run as a home agent, you will have to set up a home address and network mask for the home agent first. Then you will need to add the configuration for all mobile nodes which is made up of the following settings:

HOME INTERFACES ROUTING FIREWALL VPN SERVICES SYSTEM

LOGOUT

Static Routes Extended Routes Multipath Routes Multicast
IGMP Proxy Static Routes BGP OSPF Mobile IP Administration QoS Administration Classification
NetModule Router Simulator Hostname NB1600 Software Version 4.4.0.103 © 2004-2020, NetModule AG

Mobile IP
Mobile IP can be used to move from one network to another while maintaining a permanent IP address and thus avoiding that running IP sessions (including VPN tunnels) must be reconnected.

Administrative status:
Primary home agent address: Secondary home agent address: Home address: SPI: Authentication type: Shared secret: Life time: MTU: UDP encapsulation: Mobile network address: Mobile network mask:

mobile node home agent disabled
194.29.27.205

10.20.0.13 103

(optional)

hmac-md5 ASCII 1800

········

1468 enabled

disabled

(optional)

(optional)

Apply

Figure 5.23.: Mobile IP

Parameter SPI
Authentication type

Mobile IP Node Configuration
The Security Parameter Index (SPI) identifying the security context for the tunnel between the mobile node and the home agent. This is used to distinguish mobile nodes from each other. Therefore each mobile node needs to be assigned a unique SPI. This is a 32-bit hexadecimal value.
The used authentication algorithm. This can be prefix-suffix-md5 (default for mobile IP) or hmac-md5.

88

NB1601 User Manual for NRSW version 4.4

Parameter Shared secret

Mobile IP Node Configuration
The shared secret used for authentication of the mobile node at the home agent. This can be either a 128-bit hexadecimal value or a random length ASCII string.

89

NB1601 User Manual for NRSW version 4.4

5.4.5. Quality Of Service
NetModule routers are able to prioritize and shape certain kinds of IP traffic. This is currently limited on egress, which means that only outgoing traffic can be stipulated. The current QoS solution is using Stochastic Fairness Queueing (SFQ) classes in combination with Hierarchy Token Bucket (HTB) qdiscs. Its principle of operation can be summarized as ceiling the max. throughput per link and shaping traffic by reflecting the specified queue priorities. In general, the lowest priority number of a queue gets most out of the available bandwidth. In case of demands for other class or qdisc algorithms please contact our support team in order to evaluate the best approach for your application.
QoS Administration The administration page can be used to enable and disable QoS.
QoS Classification The classification section can be used to define the WAN interfaces on which QoS should be active.

Parameter Interface Bandwidth congestion
Downstream bandwidth Upstream bandwidth IP to ping (primary)
IP to ping (secondary)

QoS Interface Parameters
The WAN interface on which QoS should be active
The bandwidth congestion method. In case of auto the system will try to apply limits in a best-effort way. However, it is suggested to set fixed bandwidth limits as they also offer a way of tuning the QoS behaviour.
The available bandwidth for incoming traffic
The available bandwidth for outgoing traffic
An IP, which answers ICMP echo requests to determine the bandwidth of the link
An IP, which answers ICMP echo requests to determine the bandwidth of the link

When defining limits, you should consider bandwidth limits which are at least possible as most shaping and queues algorithms will not work correctly if the specified limits cannot be achieved. In particular, any WWAN interfaces operating in a mobile environment are suffering variable bandwidths, thus rather lower values should be used.

90

NB1601 User Manual for NRSW version 4.4

In case an interface has been activated, the system will automatically create the following queues:

Parameter high
default low

QoS Default Queues
A high priority queue which may hold any latency-critical services (such as VoIP)
A default queue which will handle all other services
A low priority queue which may hold less-critical services for which shaping is intended

Each queue can be configured as follows:

Parameter Name Priority Bandwidth
Set TOS

QoS Queue Parameters
The name of the QoS queue
A numerical priority for the queue, lower values indicate higher priorities
The maximum possible bandwidth for this queue in case the total bandwidth of all queues exceeds the set upstream bandwidth of “QoS Interface Parameters”
The TOS/DiffServ value to set on matching packets

You can now configure and assign any services to each queue. The following parameters apply:

Parameter Interface Queue Source
Destination
Protocol Source Port Destination Port Type of Service

QoS Service Parameters The QoS interface of the queue The QoS queue to which this service shall be assigned Specifies a network address and netmask used to match the source address of packets Specifies a network address and netmask used to match the destination (target) address of packets Specifies the protocol for packets to be matched Specifies the source port for packets to be matched Specifies the destination port for packets to be matched Specifies the TOS/DiffServ for packets to be matched

91

NB1601 User Manual for NRSW version 4.4

5.4.6. Multicast

Multicast routing (MCR) can be configured and managed by a daemon. Only one MCR daemon can be used at a time.
NetModule routers ship with two different MCR daemons to select from depending on your dependencies:

Parameter IGMP proxy
static routes
disabled

Administrative Status
Forwarding of multicast messages that are dynamically detected on a given interface to another interface
List of MCR rules to forward messages of dedicated source and group from a given interface to another
Disable routing of multicast messages

IGMP proxy IGMP proxy which is able to maintain multicast groups on a particular interface and distribute incoming multicast packets towards the downstream interfaces on which hosts have joined the groups.

Parameter Administrative status Incoming interface
Distribute to

Multicast Routing Settings
Specifies whether multicast routing is active
The upstream interface on which multicast groups are joined and on which multicast packets come in
Specifies the downstream interfaces to which multicast packets will be forwarded

Static Routes Routes multicast messages in different directions depending on their origin and group based on a given set of MCR rules:

Parameter Group Source Incoming interface Outgoing interface

Static Multicast Route IP address of MCR group Source-IP of the packets Interface to listen on for messages of given group and source Interface to forward the messages to

92

NB1601 User Manual for NRSW version 4.4

5.4.7. OSPF

The OSPF tab allows the NetModule router to be added to a network of OSPF routers.

Parameter

OSPF General Settings

OSPF status

Specifies whether the OSPF routing protocol is active

Redistribute routes

connected Redistribute routes to networks which are directly connected to the NetModule router

Redistribute local routes

Redistribute routes from the NetModule router’s own routing table

Redistribute BGP routes

Redistribute routes learned via the BGP routing protocol

Redistribute default route Redistribute the routers default route

Disable BGP when VRRP Disables the OSPF protocol when the router is set to slave mode by

slave

the VRRP redundancy protocol

The interfaces tab is used to define OSPF specific settings for the IP interfaces of the router. If no settings are defined for a specific interface, default settings will be used.

Parameter Interface Authentication
Key Key ID Cost
Passive

OSPF Interfaces The name of the interface for which settings shall be defined The authentication protocol to be used on the interface to authenticate OSPF packets The key to be used for authentication The ID of the key to be used for authentication (1-255) The cost for sending packets via this interface. If not specified or set to 0 OSPF defaults are used. Do not send out OSPF packets on this interface

The networks tab defines the IP networks to be handled in OSPF as well as to which routing area they belong.

Parameter Prefix Prefix length Area

OSPF Networks Prefix of the network Length of the prefix Routing area to which this interface belongs (0-65535, 0 means backbone)

93

NB1601 User Manual for NRSW version 4.4

5.4.8. BGP

The BGP tab allows to set up peerings of the NetModule router with other Border Gateway Protocol enabled routers.

Parameter

BGP General Settings

BGP status

Specifies whether the BGP routing protocol is active

AS number

The number of the autonomous system to which the NetModule router belongs (1-4294967295)

Redistribute routes

connected Redistribute routes to networks which are directly connected to the NetModule router

Redistribute local routes

Redistribute routes from the NetModule router’s own routing table

Redistribute OSPF routes Redistribute routes learned via the OSPF routing protocol

Disable BGP when VRRP Disables the BGP protocol when the router is set to slave mode by

slave

the VRRP redundancy protocol

The neighbors tab is used to configure all the BGP routers to peer with.

Parameter IP address As number Password
Multihop

BGP Neighbors IP address of the peer router
Autonomous system number of the peer router (1-4294967295)
Password for authentication with the peer router. If left blank authentication is disabled.
Allow multiple hops between this router and the peer router instead of requiring the peer to be directly connected.

The Networks tab allows to add IP network prefixes that shall be distributed via BGP in addition to the networks that are redistributed from other sources as defined on the general tab.

Parameter Prefix Prefix len

References

• autorun.sh
• My Dyn Account
• NetModule | Robust Communication
• Support | NetModule
• Licenses – Open Source Initiative
• Home | u-blox
• start [NetModule Router Wiki]
• app-notes:hayes-modem [NetModule Router Wiki]
• app-notes:hayes-modem-at-simulator [NetModule Router Wiki]
• GPSD redirection page
• The FreeBSD Project
• The GNU Operating System and the Free Software Movement
• GNU General Public License v2.0 - GNU Project - Free Software Foundation
• gnu.org/licenses/gpl-2.0.txt
• gnu.org/licenses/lgpl.txt
• netfilter/iptables project homepage - The netfilter.org project
• NetModule | Robust Communication
• Downloads | Router Software | NetModule
• /index.html
• /index.html
• Business VPN For Secure Networking | OpenVPN
• PHP: Hypertext Preprocessor
• Home | u-blox
• Wireshark · Go Deep
• Login required - ITxPT Wiki

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>