User's Manual

ManualsBrandsPEPWAVE ManualsElectronicsPEPWAVE / peplink Wireless Product

100

Table Of Contents

Introduction and Scope
Glossary
1 Product Features
- 1.1 Supported Network Features
- 1.2 Other Supported Features
2 Overview
- 2.1 MAXAdapter
- 2.2 Drop-in Mode and LAN Bypass: Transparent Deployment
- 2.3 QoS: Clearer VoIP
- 2.4 Per-User Bandwidth Control
- 2.5 High Availability via VRRP
- 2.6 USB Modem and Android Tethering
- 2.7 Built-In Remote User VPN Support
- 2.8 SIM-card USSD support
- 2.9 DPI Engine
3 Installation
- 3.1 Preparation
- 3.2 Constructing the Network
- 3.3 Configuring the Network Environment
4 Connecting to the Web Admin Interface
5 SpeedFusion Cloud
- 5.1 Activate SpeedFusion Cloud Service
- 5.2 Enable SpeedFusion Cloud
- 5.3 Connect Clients to Cloud
- 5.4 Link Wi-Fi to Cloud
6 Configuring the LAN Interface(s)
- 6.1 Basic Settings
- 6.2 Port Settings
- 6.3 Captive Portal
7 Configuring the WAN Interface(s)
- 7.1 Ethernet WAN
- 7.2 Cellular WAN
- 7.3 Wi-Fi WAN
  - 7.3.1 Creating Wi-Fi Connection Profiles
- 7.4 WAN Health Check
- 7.5 Dynamic DNS Settings
8 Advanced Wi-Fi Settings
9 ContentHub Configuration
- 9.1 ContentHub
- 9.2 Configuring the ContentHub
- 9.3 Configure a website to be published from the ContentHub
- 9.4 Configure an application to be published from the ContentHub
10 MediaFast Configuration
- 10.1 Setting Up MediaFast Content Caching
- 10.2 Scheduling Content Prefetching
- 10.3 Viewing MediaFast Statistics
11 Bandwidth Bonding SpeedFusionTM / PepVPN
- 11.1 PepVPN
- 11.2 The Pepwave Router Behind a NAT Router
12 IPsec VPN
- 12.1 IPsec VPN Settings
13 Outbound Policy Management
- 13.1 Outbound Policy
- 13.2 Custom Rules for Outbound Policy
14 Inbound Access
- 14.1 Port Forwarding Service
  - 14.1.1 UPnP / NAT-PMP Settings
15 NAT Mappings
16
- 16.1 User Groups
- 16.2 Bandwidth Control
- 16.3 Application
17 Firewall
- 17.1 Outbound and Inbound Firewall Rules
- 17.2 Content Blocking
- 18 OSPF & RIPv2
- 19 BGP
20 Remote User Access
- 20.1 L2TP with IPsec
- 20.2 OpenVPN
- 20.3 PPTP
- 20.4 Authentication Methods
21 Miscellaneous Settings
- 21.1 High Availability
- 21.2 Certificate Manager
- 21.3 Service Forwarding
- 21.4 Service Passthrough
- 21.5 UART
- 21.6 GPS Forwarding
- 21.7 Ignition Sensing
  - Ignition Sensing installation
  - GPIO Menu
- 21.8 NTP Server
- 21.9 Grouped Networks
- 21.10 SIM Toolkit
22 AP - access point
- 23 AP Controller
- 23.1 Wireless SSID
- 23.2 Settings
24 AP Controller Status
- 24.1 Info
- 24.2 Access Point (Usage)
- 24.3 Wireless SSID
- 24.4 Wireless Client
- 24.5 Nearby Device

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.

11.3 SpeedFusion

Status

SpeedFusionTM 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.