User's Manual

ManualsBrandsPEPWAVE ManualsElectronicsPEPWAVE / peplink Wireless Product

Table Of Contents

1 Introduction and Scope
Glossary
2 Product Features
- 2.1 Supported Network Features
- 2.2 Other Supported Features
3 Pepwave MAX Mobile Router Overview
- 3.1 MAX BR1 Mini Core
4 Advanced Feature Summary
- 4.1 Drop-in Mode and LAN Bypass: Transparent Deployment
- 4.2 QoS: Clearer VoIP
- 4.3 Per-User Bandwidth Control
- 4.4 High Availability via VRRP
- 4.5 USB Modem and Android Tethering
- 4.6 Built-In Remote User VPN Support
- 4.7 SIM-card USSD support
5 Installation
- 5.1 Preparation
- 5.2 Constructing the Network
- 5.3 Configuring the Network Environment
6 Mounting the Unit
- 6.1 Wall Mount
7 Connecting to the Web Admin Interface
8 Configuring the LAN Interface(s)
- 8.1 Basic Settings
- 8.2 Port Settings
- 8.3 Captive Portal
9 Configuring the WAN Interface(s)
- 9.1 Ethernet WAN
- 9.2 Cellular WAN
- 9.3 Wi-Fi WAN
  - 9.3.1 Creating Wi-Fi Connection Profiles
- 9.4 WAN Health Check
- 9.5 Dynamic DNS Settings
10 Advanced Wi-Fi Settings
11 ContentHub Configuration
- 11.1 ContentHub
- 11.2 Configuring the ContentHub
- 11.3 Configure a website to be published from the ContentHub
- 11.4 Configure an application to be published from the ContentHub
12 MediaFast Configuration
- 12.1 Setting Up MediaFast Content Caching
- 12.2 Scheduling Content Prefetching
- 12.3 Viewing MediaFast Statistics
13 Bandwidth Bonding SpeedFusionTM / PepVPN
- 13.1 PepVPN
- 13.2 The Pepwave Router Behind a NAT Router
- 13.3 SpeedFusionTM Status
14 IPsec VPN
- 14.1 IPsec VPN Settings
15 Outbound Policy Management
- 15.1 Outbound Policy
- 15.2 Custom Rules for Outbound Policy
16 Inbound Access
- 16.1 Port Forwarding Service
  - 16.1.1 UPnP / NAT-PMP Settings
17 NAT Mappings
18 QoS
- 18.1 User Groups
- 18.2 Bandwidth Control
- 18.3 Application
19 Firewall
- 19.1 Outbound and Inbound Firewall Rules
- 19.2 Content Blocking
- 20 OSPF & RIPv2
- 21 BGP
22 Remote User Access
- 22.1 L2TP with IPsec
- 22.2 OpenVPN
- 22.3 PPTP
- 22.4 Authentication Methods
23 Miscellaneous Settings
- 23.1 High Availability
- 23.2 Certificate Manager
- 23.3 Service Forwarding
- 23.4 Service Passthrough
- 23.5 UART
- 23.6 GPS Forwarding
- 23.7 Ignition Sensing
  - Ignition Sensing installation
  - GPIO Menu
- 23.8 Grouped Networks
- 23.9 SIM Toolkit
24 AP - access point
- 25 AP Controller
- 25.1 Wireless SSID
- 25.2 Settings
26 AP Controller Status
- 26.1 Info
- 26.2 Access Point (Usage)
- 26.3 Wireless SSID
- 26.4 Wireless Client
- 26.5 Nearby Device
- 26.6 Event Log
27 Toolbox
28 System Settings
- 28.1 Admin Security
- 28.2 Firmware
- 28.3 Time
- 28.4 Schedule
- 28.5 Email Notification
- 28.6 Event Log
- 28.7 SNMP
- 28.8 InControl
- 28.9 Configuration
- 28.10 Feature Add-ons
- 28.11 Reboot
29 Tools
- 29.1 Ping
- 29.2 Traceroute Test
- 29.3 PepVPN Test
- 29.4 Wake-on-LAN
- 29.5 CLI (Command Line Interface Support)
30 Status
- 30.1 Device
  - 30.2 GPS Data
- 30.3 Active Sessions
- 30.4 Client List
- 30.5 WINS Client
- 30.6 UPnP / NAT-PMP
- 30.7 OSPF & RIPv2
- 30.8 BGP
- 30.9 SpeedFusion Status
- 30.10 Event Log
- 31 WAN Quality
- 32 Usage Reports
- 32.1 Real-Time
- 32.2 Hourly
- 32.3 Daily
- 32.4 Monthly
Appendix A: Restoration of Factory Defaults
Appendix B: Declaration

https://www.peplink.com

One of the WANs connected to Router A is non-NAT’d (212.1.1.1). The rest of the WANs

connected to Router A and all WANs connected to Router B are NAT’d. In this case, the Peer

IP Addresses / Host Names field for Router B should be filled with all of Router A’s hostnames

or public IP addresses (i.e., 212.1.1.1, 212.2.2.2, and 212.3.3.3), and the field in Router A can

be left blank. The two NAT routers on WAN1 and WAN3 connected to Router A should inbound

port-forward TCP port 32015 to Router A so that all WANs will be utilized in establishing the

VPN.

13.3

SpeedFusion

Status

SpeedFusion

status is shown in the Dashboard. The connection status of each connection

profile is shown as below.

After clicking the Status button at the top right corner of the SpeedFusion

table, you will be

forwarded to Status>SpeedFusion

, where you can view subnet and WAN connection

information for each VPN peer. Please refer to Section 22.6 for details.

IP Subnets Must Be Unique Among VPN Peers

The entire interconnected SpeedFusion

network is a single non-NAT IP network. Avoid duplicating

subnets in your sites to prevent connectivity problems when accessing those subnets.

14 IPsec VPN

IPsec VPN functionality securely connects one or more branch offices to your company's main