B One, B One Plus & B One 5G Peplink Firmware 8.4.0 June 2024
18 giu 2024 — The BSSID is the MAC address of the wireless access point (WAP). Choose DHCP or Static IP for the Wi-Fi WAN connection method. Configure the DNS servers that ...
Peplink B One Loadbalance VPN Router 2 WAN 1Gbps, WIFI-6
B One, B One Plus & B One 5G
Peplink Firmware 8.4.0 June 2024
Peplink routers provide link aggregation and load balancing across multiple WAN connections, allowing a combination of technologies like 3G HSDPA, EVDO, 4G LTE, WiFi, external WiMAX dongle, and satellite to be utilized to connect to the Internet.
The MAX wireless SD-WAN router series has a wide range of products suitable for many different deployments and markets. Entry level SD-WAN models such as the MAX BR1 are suitable for SMEs or branch offices. High-capacity SD-WAN routers such as the MAX HD2 are suitable for larger organizations and head offices.
This manual covers setting up Peplink routers and provides an introduction to their features and usage.
Want to know more about Peplink routers? Visit our YouTube Channel (https:// www.youtube.com/PeplinkChannel) for a video introduction (https:// www.youtube.com/PeplinkChannel#p/u/1/1ste4dQV-V8)!
The following terms, acronyms, and abbreviations are frequently used in this manual:
3G
4G DHCP DNS EVDO FQDN HSDPA HTTP ICMP IP LAN MAC Address MTU MSS NAT PPPoE QoS
3rd generation standards for wireless communications (e.g., HSDPA) 4th generation standards for wireless communications (e.g., LTE) Dynamic Host Configuration Protocol Domain Name System Evolution-Data Optimized Fully Qualified Domain Name High-Speed Downlink Packet Access Hyper-Text Transfer Protocol Internet Control Message Protocol Internet Protocol Local Area Network Media Access Control Address
Maximum Transmission Unit Maximum Segment Size Network Address Translation Point to Point Protocol over Ethernet Quality of Service
SNMP TCP UDP VPN VRRP WAN WINS WLAN
Simple Network Management Protocol Transmission Control Protocol User Datagram Protocol Virtual Private Network Virtual Router Redundancy Protocol Wide Area Network Windows Internet Name Service Wireless Local Area Network
Peplink routers enable all LAN users to share broadband Internet connections, and they provide advanced features to enhance Internet access. Below is a list of supported features on Peplink routers. Features vary by model. For more information, please see peplink.com/products.
Ethernet WAN connection in full/half duplex Static IP support for PPPoE Built-in cellular modems USB mobile connection(s) Wi-Fi WAN connection Network address translation (NAT)/port address translation (PAT)
Inbound and outbound NAT mapping IPsec NAT-T and PPTP packet passthrough MAC address clone and passthrough Customizable MTU and MSS values WAN connection health check Dynamic DNS (supported service providers: changeip.com, dyndns.org, no-ip.org,
tzo.com and DNS-O-Matic) Ping, DNS lookup, and HTTP-based health check
Wi-Fi AP Ethernet LAN ports DHCP server on LAN Extended DHCP option support Static routing rules VLAN on LAN support
PepVPN with SpeedFusionTM PepVPN performance analyzer X.509 certificate support VPN load balancing and failover among selected WAN connections Bandwidth bonding and failover among selected WAN connections IPsec VPN for network-to-network connections (works with Cisco and Juniper) Ability to route Internet traffic to a remote VPN peer Optional pre-shared key setting SpeedFusionTM throughput, ping, and traceroute tests PPTP server PPTP and IPsec passthrough
Outbound (LAN to WAN) firewall rules Inbound (WAN to LAN) firewall rules per WAN connection Intrusion detection and prevention Specification of NAT mappings Outbound firewall rules can be defined by destination domain name
Splash screen of open networks, login page for secure networks Customizable built-in captive portal Supports linking to outside page for captive portal
Link load distribution per TCP/UDP service Persistent routing for specified source and/or destination IP addresses per TCP/UDP
service Traffic prioritization and DSL optimization Prioritize and route traffic to VPN tunnels with Priority and Enforced algorithms
Configure and manage Pepwave AP devices Review the status of connected APs
Quality of service for different applications and custom protocols User group classification for different service levels Bandwidth usage control and monitoring on group- and user-level
Application prioritization for custom protocols and DSL/cable optimization
User-friendly web-based administration interface HTTP and HTTPS support for web admin interface (default redirection to HTTPS) Configurable web administration port and administrator password Firmware upgrades, configuration backups, ping, and traceroute via web admin
interface Remote web-based configuration (via WAN and LAN interfaces) Time server synchronization SNMP Email notification Read-only user access for web admin Shared IP drop-in mode Authentication and accounting by RADIUS server for web admin Built-in WINS servers* Syslog SIP passthrough PPTP packet passthrough Event log Active sessions Client list WINS client list * UPnP / NAT-PMP Real-time, hourly, daily, and monthly bandwidth usage reports and charts IPv6 support Support USB tethering on Android 2.2+ phones
* Not supported on MAX Surf-On-The-Go, and BR1 variants
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4448) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4486)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4463)
The statuses indicated by the front panel LEDs are as follows:
OFF
Wi-Fi AP or Wi-Fi WAN is disabled.
Wi-Fi AP or Wi-Fi WAN is enabled.
OFF
Power Off
Booting up or busy
Boot up error
Ready
The statuses indicated by the front panel LEDs are as follows:
OFF
Wi-Fi AP or Wi-Fi WAN is disabled.
Wi-Fi AP or Wi-Fi WAN is enabled.
OFF Blinking Slowly
Disabled or no SIM card inserted Connecting to network(s) Connected to network(s)
OFF
Power Off
Booting up or busy
Boot up error
Ready
The statuses indicated by the front panel LEDs are as follows:
OFF
Wi-Fi AP or Wi-Fi WAN is disabled.
Wi-Fi AP or Wi-Fi WAN is enabled.
OFF Blinking Slowly
Disabled or no SIM card inserted Connecting to network(s) Connected to network(s)
OFF
Power Off
Booting up or busy Boot up error Ready
#4375)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
As your organization grows, it may require more bandwidth, but modifying your
network can be tedious. In
(http://www.peplink.com/knowledgebase/
deploying-the-peplink-balance-in-drop-in-mode/), you can conveniently install your
Peplink router without making any changes to your network. For any reason your
Peplink router loses power, the
(http://www.peplink.com/knowledgebase/
what-is-lan-bypass/) will safely and automatically bypass the Peplink router to resume
your original network connection.
Note: Drop-in mode is compatible for All MAX models except MAX BR1 IP67
VoIP and videoconferencing are highly sensitive to latency. With QoS, Peplink routers can detect VoIP traffic and assign it the highest priority, giving you crystal-clear calls.
With per-user bandwidth control, you can define bandwidth control policies for up to 3 groups of users to prevent network congestion. Define groups by IP address and subnet, and set bandwidth limits for every user in the group.
When your organization has a corporate requirement demanding the highest availability with no single point of failure, you can deploy two Peplink routers in
(http://www.peplink.com/knowledgebase/configuring-11-backupby-vrrp/). With High Availability mode, the second device will take over when needed.
Compatible with: MAX 700, MAX HD2 (All variants), HD4 (All Variants)
For increased WAN diversity, plug in a USB LTE modem as a backup. Peplink routers
are compatible with over
(http://www.peplink.com/
technology/4g3g-modem-support/). You can also tether to smartphones running
Android 4.1.X and above.
Compatible with: MAX 700, HD2 (all variants except IP67), HD4 (All variants)
Use OpenVPN or L2TP with IPsec to safely and conveniently connect remote clients to your private network. L2TP with IPsec is supported by most devices, but legacy devices can also connect using PPTP. (https://forum.peplink.com/t/setting-up-l2tp-with-ipsec/8046)
(https://forum.peplink.com/t/ configure-remote-user-access-using-openvpn/19757)
Cellular-enabled routers can now use USSD to check their SIM card's balance, process pre-paid cards, and configure carrier-specific services.
(http://www.peplink.com/
knowledgebase/how-to-use-ussd-codes-on-cellular-enabled-routers/)
The DPI report written in the updated KB article will show further information on InControl2 through breaking down application categories into subcategories.
(https://forum.peplink.com/t/updatedic2-deep-packet-inspection-dpi-reports-and-everything-you-need-to-know-aboutit/29658)
NetFlow protocol is used to track network traffic. Tracking information from NetFlow can be sent to the NetFlow collector, which analyzes data and generates reports for review. Note: To enable this feature, go to https://<Device's IP>/cgi-bin/MANGA/support.cgi
Pepwave routers support Wi-Fi "Air Monitoring Mode" which is used to troubleshoot remotely and proactively monitor Wi-Fi and WAN performance. The report can be viewed under InControl 2 > Reports > AirProbe Reports after enabling Wi-Fi Air Monitoring.
Note: To enable this feature, go to https://<Device's IP>/cgi-bin/MANGA/support.cgi
The SP Default Configuration feature written in the updated KB article allows for the provisioning of custom made settings (a.k.a. InControl2 configuration) via the Ethernet LAN port and is ideal for those wanting to do a bulk deployment of many Peplink devices.
Note: If you would like to use this feature, please contact your purchase point (Eg.VAD).
Cloud Service Providers often restrict access to certain applications. With SFC Relay, you can route traffic before going out to the Internet, allowing access to previously restricted applications experienced with the public SpeedFusion Cloud nodes. Available as an add-on for your home router or as an upgradable license to your Peplink router, SFC Relay is sure to impress you and any peers you give access to.
(https://forum.peplink.com/t/configurespeedfusion-cloud-relay-server-and-client/6215ca9b017e48e0f3ff2479/)
DoH provides the benefits of communicating DNS information over a secure HTTPS connection in an encrypted manner. The protocol offers increased privacy and confidentiality by preventing data interception and man-in-the-middle attacks.
InTouch is Peplink's zero-touch remote network management solution, leveraging InControl 2 and a SpeedFusion Connect (formerly known as SpeedFusion Cloud) data plan. This service extends a network administrator's ability to reach any device UI backed by a Peplink/Pepwave router. To configure InTouch, all you need is a valid InControl 2 subscription, a SpeedFusion Connect data plan, and a Peplink/Pepwave router (which requires the latest 8.2.0 firmware).
To watch a demonstration and read the FAQ, visit (https://www.peplink.com/enterprise-solutions/
intouch/)
Or learn to configure InTouch at zg0iavHGkJw)
(https://youtu.be/
Synergy mode is a cascade multiple devices and combine the number of WANs to a single device virtually. All the WANs on the Synergized Device will appear as native WAN interfaces at the Synergy Controller and it can be managed like the built-in WAN interfaces.
https://forum.peplink.com/t/synergy-mode-
(firmware-8.3.0)/639be7d8af8c71a6f3050323/ (https://forum.peplink.com/t/synergymode-(firmware-8.3.0)/639be7d8af8c71a6f3050323/)
The Virtual WAN Activation License allows you to create 1 x virtual WAN on a particular VLAN, on either WAN or LAN interface. This means that you can create a virtual WAN on VLAN for a WAN port, or a virtual WAN on VLAN for a LAN port. https://forum.peplink.com/t/b20x-virtual-wan-activation-licensefaq/6204bac7d90b9e6355e96e8d/1 (https://forum.peplink.com/t/b20x-virtual-wanactivation-license-faq/6204bac7d90b9e6355e96e8d/1)
The following section details connecting Pepwave routers to your network.
Before installing your Pepwave router, please prepare the following as appropriate for your installation:
At least one Internet/WAN access account and/or Wi-Fi access information
Depending on network connection type(s), one or more of the following:
: A 10/100/1000BaseT UTP cable with RJ45 connector
: A USB modem
: A SIM card for 5G/4G LTE service
: Wi-Fi antennas
card slot
A PC Card/ExpressCard for the corresponding
A computer installed with the TCP/IP network protocol and a supported web browser. Supported browsers include Microsoft Internet Explorer 11 or above, Mozilla Firefox 24 or above, Apple Safari 7 or above, and Google Chrome 18 or above.
At a high level, construct the network according to the following steps:
1. With an Ethernet cable, connect a computer to one of the LAN ports on the Pepwave router. Repeat with different cables for up to 4 computers to be connected.
2. With another Ethernet cable or a USB modem/Wi-Fi antenna/PC Card/Express Card, connect to one of the WAN ports on the Pepwave router. Repeat the same procedure for other WAN ports.
3. Connect the power adapter to the power connector on the rear panel of the Pepwave router, and then plug it into a power outlet.
To ensure that the Pepwave router works properly in the LAN environment and can access the Internet via WAN connections, please refer to the following setup procedures:
LAN configuration
For basic configuration, refer to manual.peplink.com/peplink-b-series-user-manual/#4367).
For advanced configuration, go to manual.peplink.com/peplink-b-series-user-manual/#4357).
(https:// (https://
WAN configuration For basic configuration, refer to
For advanced configuration, go to peplink-b-series-user-manual/#4358).
. (https://manual.peplink.com/
1. Start a web browser on a computer that is connected with the Pepwave router through the LAN.
2. To connect to the router's web admin interface, enter the following LAN IP address in the address field of the web browser: http://192.168.50.1(This is the default LAN IP address for Pepwave routers.)
3. Enter the following to access the web admin interface. : admin
: admin
(This is the default username and password for Pepwave routers).
You must change the default password on the first successful logon.
Password requirements are: A minimum of 10 lower AND upper case characters, including at least 1 number.
When HTTP is selected, the URL will be redirected to HTTPS by default.
After successful login, the
of the web admin interface will be displayed.
The
shows current WAN, LAN, and Wi-Fi AP statuses. Here, you can change
WAN connection priority and switch on/off the Wi-Fi AP. For further information on
setting up these connections, please refer to
(https://docs.google.com/
document/d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/
edit#bookmark=id.kgcv8k)and (https://docs.google.com/document/
d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/edit#bookmark=id.2afmg28)
displays details about the device, including model name,
firmware version, and uptime. For further information, please refer to
(https://
docs.google.com/document/d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/
edit#heading=h.21od6so) (https://docs.google.com/document/
d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/edit#bookmark=id.3mj2wkv)
Configuration changes (e.g. WAN, LAN, admin settings, etc.) will take effect only
after clicking the
button at the bottom of each page. The
button causes the changes to be saved and applied.
With Peplink products, your device is able to connect to SpeedFusion Connect without the use of a second endpoint. This service has wide access to a number of SpeedFusion endpoints hosted from around the world, providing your device with unbreakable connectivity wherever you are.*
*SpeedFusion Connect is supported in firmware version 8.1.0 and above. SpeedFusion Connect is a subscription basis. SpeedFusion Connect license can be purchased at
(https://estore.peplink.com/) .
All Care plans now come with SpeedFusion Connect Protect included. This data allowance will automatically begin and end in accordance with your warranty. No activation is required.
Access the Web Admin of the device you want to create as the Peplink Relay Server,
navigating to the "
" tab.
To setup a Peplink Relay Mode, select "
the
you wish to connect to > Click on the
confirm the change.
" > Choose to
The Relay Sharing Code will be generated, and other peers can use this code to establish a SpeedFusion Connect Protect that will forward the traffics to this device, allowing them to access local networks and the internet via your WAN connection.
To connect to SpeedFusion Connect Protect, you can select a
of
your choice, or simply and
then the device will establish connection to the
neareset SFC Protect server.
Choose
to confirm the change.
Or you may select
and use your
if you have set up a Peplink Relay Client on another device.
to create a profile
Click on
to save the change.
By default, the router will build a SpeedFusion tunnel to the SpeedFusion Cloud.
If you are running a latency sensitive service like video streaming or VOIP, a WAN Smoothing sub-tunnel can be created. Navigate to Navigate to
.
A SpeedFusion Connect Protect Profile configuration window will pop out. Click on the sign to create the WAN Smoothing sub-tunnel.
Click on
and
to save the configuration. Now, the router has 2
Speedfusion tunnels to the SpeedFusion Connect Protect.
Create an outbound policy to steer the internet traffic to go into SFC Protect. Please go
to
, click on
to create a new outbound policy.
Optimize Cloud Application allows you to route Internet traffic through SpeedFusion Connect Protect based on the application. Go to
.
Select a Cloud application to route through SpeedFusion Connect Protect from the
drop down list Click
Save > Apply Changes.
Click the
to remove a selected Cloud application from routing through
SpeedFusion Connect Protect.
SpeedFusion Connect Protect provides a convenient way to route the Wi-Fi client to the
cloud from
.
Create a new SSID for SFC Protect. The new SSID will inherit all settings from one of the
existing SSIDs including the Security Policy. Then click
followed by
.
SFC Protect SSID will be shown on
.
SpeedFusion Connect Protect provides a convenient way to route the LAN client to the
cloud from
.
Choose a client from the drop down list > Click > Save > Apply Changes.
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4360) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4359)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4358)
LAN interface settings are located at to that page will show the following dashboard:
. Navigating
This represents the LAN interfaces that are active on your router (including VLAN). A gray "X" means that the VLAN is used in other settings and cannot be deleted. You can find which settings are using the VLAN by hovering over the gray "X".
Alternatively, a red "X" means that there are no settings using the VLAN. You can delete that VLAN by clicking the red "X"
Clicking on any of the existing LAN interfaces (or creating a new one) will show the following :
The IP address and subnet mask of the Pepwave router on the LAN.
Enter a name for the LAN.
Enter a number for your VLAN. Check this box to enable routing between virtual LANs.
The remote network of the selected SpeedFusion VPN profiles will be bridged with this local LAN, creating a Layer 2 SpeedFusion VPN, they will be connected and operate like a single LAN, and any broadcast or multicast packets will be sent over the VPN. Click the box will enable STP for this layer 2 profile bridge.
Click on the question Mark if you want to enable DHCP Option 82. This allows the device to inject Option 82 with Router Name information before forwarding the DHCP Request packet to a SpeedFusion VPN peer, such that the DHCP Server can identify where the request originates from.
Select "Do not override" if the LAN IP address and local DHCP server should remain unchanged after the Layer 2 SpeedFusion VPN is up. If you choose to override the IP address when the VPN is connected, the device will not act as a router, and most Layer 3 routing functions will cease to work.
When this setting is enabled, the Pepwave router's DHCP server automatically assigns an IP address to each computer that is connected via LAN and configured to obtain an IP address via DHCP. The Pepwave router's DHCP server can prevent IP address collisions on the LAN.
To enable DHCP bridge relay, please click the menu item.
icon on this
Enable logging of DHCP events in the eventlog by selecting the checkbox.
These settings allocate a range of IP addresses that will be assigned to LAN computers by the Pepwave router's DHCP server.
This setting specifies the length of time throughout which an IP address of a DHCP client remains valid. Upon expiration of
, the assigned IP address will no longer be valid and the IP address assignment must be renewed.
This option allows you to input the DNS server addresses to be
offered to DHCP clients. If
is
selected, the Pepwave router's built-in DNS server address (i.e., LAN
IP address) will be offered.
Check this box to enable BOOTP on older networks that still require it.
In addition to standard DHCP options (e.g. DNS server address,
gateway address, subnet mask), you can specify the value of
additional extended DHCP options, as defined in RFC 2132. With
these extended options enabled, you can pass additional
configuration information to LAN hosts. To define an extended
DHCP option, click the
button, choose the option to define,
and then enter its value. For values that are in IP address list
format, you can enter one IP address per line in the provided text
area input control. Each option can be defined once only.
This setting reserves the assignment of fixed IP addresses for a list of computers on the LAN. The computers to be assigned fixed IP addresses on the LAN are identified by their MAC addresses. The fixed IP address assignment is displayed as a cross-reference list between the computers' names, MAC addresses, and fixed IP addresses.
(an optional field) allows you to specify a name to represent
the device. MAC addresses should be in the format of
. Press
to create a new record. Press
to remove a record. Reserved clients information can be
imported from the
, located at
. For
more details, please refer to
(https://docs.google.com/
document/
d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/
edit#heading=h.u8tczi)
To configure DHCP relay, first click the option to display the settings.
button found next to the
Check this box to turn on DHCP relay. Click the DHCP relay.
icon to disable
Enter the IP addresses of one or two DHCP servers in the provided
fields. The DHCP servers entered here will receive relayed DHCP
requests from the LAN. For active-passive DHCP server
configurations, enter active and passive DHCP server relay IP
addresses in
and
DHCP Option 82 includes device information as relay agent for the attached client when forwarding DHCP requests from client to server. This option also embeds the device's MAC address and network name in circuit and remote IDs. Check this box to enable DHCP Option 82.
Enable logging of DHCP Relay events in the eventlog by selecting the checkbox.
Once DHCP is set up, configure
,
as noted above.
, and
This table is for defining static routing rules for the LAN segment. A static route consists of the network address, subnet mask, and gateway address. The address and subnet mask values are in w.x.y.z format.
The local LAN subnet and subnets behind the LAN will be advertised to
the VPN. Remote routes sent over the VPN will also be accepted. Any
VPN member will be able to route to the local subnets. Press
to
create a new route. Press
to remove a route.
A Advanced feature, please click the
button on the top right hand corner of the
Static Route section to activate and configure Virtual Network Mapping to resolve network address conflict with remote peers.
In case of a network address conflict with remote peers (i.e. SpeedFusion VPN / IPsec VPN / IP Forwarding WAN are considered as remote connections), you can define Virtual Network Mapping to resolve it.
.
For further details on virtual network mapping watch this video:
https://youtu.be/C1FMdZCn3Z8 (https://youtu.be/C1FMdZCn3Z8)
Every IP Address in the Local Network has a corresponding unique Virtual IP Address for NAT. Traffic originating from the Local Network to remote connections will be SNAT'ed and behave like coming from the defined Virtual Network. While traffic initiated by remote peers to the Virtual Network will be DNAT'ed accordingly.
The subnet range defined in Local Network will be mapped to a single Virtual IP Address for NAT. Traffic can only be initiated from local to remote, and these traffic will be NAT'ed and behaves like coming from the same Virtual IP Address.
To enable the DNS proxy feature, check this box, and then set up
the feature at
. A DNS proxy
server can be enabled to serve DNS requests originating from
LAN/PPTP/SpeedFusionTM peers. Requests are forwarded to the
defined for each WAN connection.
This field is to enable DNS caching on the built-in DNS proxy
server. When the option is enabled, queried DNS replies will be
cached until the records' TTL has been reached. This feature can
help improve DNS lookup time. However, it cannot return the most
up-to-date result for those frequently updated DNS records. By
default,
is disabled.
When this option is
, the DNS proxy server will also
forward DNS requests to Google's Public DNS Servers (https://
developers.google.com/speed/public-dns/), in addition to the DNS
servers defined in each WAN. This could increase the DNS service's
availability. This setting is disabled by default.
This table is for defining custom local DNS records. A static local
DNS record consists of a host name and IP address. When looking
up the host name from the LAN to LAN IP of the Pepwave router,
the corresponding IP address will be returned. Press
to
create a new record. Press
to remove a record.
DNS Proxy will lookup the domain names defined in this table using the specified connections only.
This field specifies which DNS servers can receive forwarded DNS requests. If no DNS server is selected, then all of them will be selected by default.
If you wish to select a SpeedFusion VPN peer, enter the IP address(es) of the VPN peer's DNS server.
Incoming queries will be forwarded to one of the selected servers. If none of the selected servers can be reached, then the router will forward incoming queries to all servers with healthy WAN connections.
A Advanced feature, please click the activate.
button on the top right hand corner to
Finally, if needed, configure Bonjour forwarding, Apple's zero configuration networking
protocol. Once VLAN configuration is complete, click
to store your changes.
Check this box to turn on Bonjour forwarding.
Choose
and
and then click
Bonjour listing, click
networks from the drop-down menus, to add the networks. To delete an existing
.
Drop-in mode (or transparent bridging mode) eases the installation of the Pepwave MAX on a live network between the firewall and router, such that changes to the settings of existing equipment are not required. The following diagram illustrates drop-in mode setup:
Check the box Enable to enable the Drop-in Mode. After enabling this feature and selecting the WAN for Drop-in mode, various settings including the WAN's connection method and IP address will be automatically updated. When drop-in mode is enabled, the LAN and the WAN for drop-in mode ports will be bridged. Traffic between the LAN hosts and WAN router will be forwarded between the devices. In this case, the hosts on both sides will not notice any IP or MAC address changes. After successfully setting up the Pepwave MAX as part of the network using drop-in mode, it will, depending on model, support one or more WAN connections. Some MAX units also support multiple WAN connections after activating drop-in mode, though a SpeedFusion license may be required to activate more than one WAN port.
Drop-in mode eases the installation of the Pepwave MAX on a live network between the existing firewall and router, such that no configuration changes are required on existing equipment. Check the box to enable the drop-in mode feature.
Select the WAN port to be used for drop-in mode. If
is selected,
the high availability feature will be disabled automatically.
When this option is enabled, the passthrough IP address will be used to connect to WAN hosts (email notification, remote syslog, etc.). The MAX will listen for this IP address when WAN hosts access services provided by the MAX (web admin access from the WAN, DNS server requests, etc.).
To connect to hosts on the LAN (email notification, remote syslog, etc.), the default gateway address will be used. The MAX will listen for this IP address when LAN hosts access services provided by the MAX (web admin access from the WAN, DNS proxy, etc.).
Access to this IP address will be passed through to the LAN port if this device is not serving the service being accessed. The shared IP address will be used in connecting to hosts on the WAN (e.g., email notification, remote syslog, etc.) The device will also listen on the IP address when hosts on the WAN access services served on this device (e.g., web admin accesses from WAN, DNS server, etc.)
Enter the WAN router's IP address in this field. If there are more hosts in addition to the router on the WAN segment, click the button next to "WAN Default Gateway" and check the other
box and enter the IP address of the hosts that need to access LAN devices or be accessed by others.
Enter the selected WAN's corresponding DNS server IP addresses.
A Advanced feature, please click the activate.
button on the top right-hand corner to
To configure port settings, navigate to
On this screen, you can enable specific ports, as well as determine the speed of the LAN ports, whether each port is a trunk or access port, as well as which VLAN each link belongs to, if any.
The captive portal serves as a gateway that clients have to pass if they wish to access the internet using your router. To configure, navigate to
.
Enter the name for the Captive Portal.
Check
and then, optionally, select the LANs/VLANs that
will use the captive portal.
To customize the portal's form submission and redirection
URL, enter a new URL in this field. To reset the URL to factory
settings, click
.
Click
to allow clients to freely access your router.
Click
to force your clients to
authenticate before accessing your router.
Select HotSpot system.
to use the Captive Portal with a
As described in the following knowledgebase article:
https://forum.peplink.com/t/using-hotspotsystem-wi-fi-onpepwave-max-routers/ (https://forum.peplink.com/t/usinghotspotsystem-wi-fi-on-pepwave-max-routers/)
When selecting the "
" in the Access Mode
field, you will see the available option for the Authentication
via drop-down list:
RADIUS Server
LDAP Server
Fill in the necessary information to complete your connection to the server and enable authentication.
When selecting the "
" in the Access Mode field,
you will see the available option for the Service Type via drop-
down list:
CoovaChilli
HotspotSystem
Fill in the necessary information to complete your connection to the server and enable authentication.
Set a time and data cap to each user's Internet usage.
This menu determines how your usage quota resets. Setting it
to
will reset it at a specified time every day. Setting a
number of
establish a timer for
each user that begins after the quota has been reached.
Clients will get disconnected when the inactive the configured time is reached. Default 0: no timeout
Add networks that can bypass the captive Portal in this field.
To whitelist a network, enter the domain name / IP address
here and click
. To delete an existing network from the
list of allowed networks, click the
button next to the
listing.
Add MAC address and /or IP addresses for client devices that are allowed to bypass the Captive Portal. Clients accessing these domains and IP addresses will not be redirected to the splash page.
Here, you can choose between using the Pepwave router's built-in captive portal and redirecting clients to a URL you define.
Configurable options for popup handling: Bypass Popup (Redirection only takes place on normal browser) Automatically show splash page on Safari for Apple (iOS / macOS) devices
A hostname that can be used to logout captive portal when being accessed on browser.
Click on the provided link in the Captive portal profile to customize the splash page.
A new browser tab is opened with a WYSIWYG editor of the splash page o edit the content, click on the corresponding element after switching Edit Mode to ON.
WAN Interface settings are located at
. To reorder WAN priority, drag
on the appropriate WAN by holding the left mouse button, move it to the desired
priority (the first one would be the highest priority, the second one would be lower
priority, and so on), and drop it by releasing the mouse button.
To able a particular WAN connection, drag on the appropriate WAN by holding the left
mouse button, move it the
row, and drop it by releasing the mouse button.
You can also set priorities on the
. Click the
corresponding row to modify the connection setting.
button in the
Connection details will be changed and become effective immediately after clicking
the
button.
You can also enable IPv6 support in this section.
You can enable DoH (DNS over HTTPS) support in this section.
When this option is enabled, the DNS proxy server will use HTTPS connections to forward DNS requests to the DoH resolver; it will not fallback to traditional UDP DNS options.
The options to configure DoH with a predefined server are:
Cloudflare The DNS server IP addresses for 1.1.1.1, which is unfiltered.
will be using
Quad9 The DNS server IP addresses for
will be using 9.9.9.9
and 142.112.112.112, which is malware blocking and DNSSEC.
Google DNS The DNS server IP addresses for using 8.8.8.8 and 8.8.4.4, which is RFC8484 standard.
will be
OpenDNS The DNS server IP addresses for
will be using
208.67.222.222 and 208.67.220.220, which is standard DNS.
Custom URL You may select
and
.
, and enter the
This settings advice how WAN Quality information is being gathered.
By default, WAN Quality will always be observed and gathered automatically. With customized choice of WAN connections, the device will always observe WAN Quality of those selected WAN connections. Other WAN connections may stop observing WAN Quality information if it is not necessary for the underlying features.
You can enable the Synergy Controller in this section.
You may click this disabled.
to enable the Synergy Controller. By default, the setting is
You may select the WAN connection to use as a Synegy Link which will connect to synergized devices.
(https://manual.peplink.com/peplink-b-series-user-manual/#4356)
#4355)
(https://manual.peplink.com/peplink-b-series-user-manual/
(https://manual.peplink.com/peplink-b-series-user-manual/#4354) (https://manual.peplink.com/peplink-b-series-user-manual/#4353) (https://manual.peplink.com/peplink-b-series-user-manual/#4352)
The DHCP connection method is suitable if the ISP provides an IP address automatically using DHCP (e.g., satellite modem, WiMAX modem, cable, Metro Ethernet, etc.).
Enter a name to represent this WAN connection.
This setting enables the WAN connection. If schedules have been defined, you will be able to select a schedule to apply to the connection.
This option allows you to configure the WAN connection whether for normal daily usage or as a backup connection only.
If
is chosen, the WAN connection will be kept on
continuously, regardless of the priority of other WAN
connections.
If
is chosen, the WAN connection will depend on other
WAN connections. It will not be used when one or more higher
priority dependent WAN connections are connected.
If this is checked, the connection will be working independent from other Backup WAN connections. Those in will ignore the status of this WAN connection, and will be used when none of the other higher priority connections are available.
NAT allows substituting the real address in a packet with a
mapped address that is routable on the destination network. By
clicking the help
icon in this field, you can display the
option, if your network requires it.
you click
is available for configuration when e for other DHCP settings.
This option allows you to configure the management IP address for the DHCP WAN connection.
If your service provider's DHCP server requires you to supply a hostname value upon acquiring an IP address, you may enter the value here. If your service provider does not provide you with the value, you can safely bypass this option.
Each ISP may provide a set of DNS servers for DNS lookups. This setting specifies the DNS (Domain Name System) servers to be used when a DNS lookup is routed through this connection.
Selecting
results in
the DNS servers being assigned by the WAN DHCP server to be
used for outbound DNS lookups over the connection. (The DNS
servers are obtained along with the WAN IP address assigned
from the DHCP server.)
When
is selected,
you may enter custom DNS server addresses for this WAN
connection into the
and
fields.
When this
option is active, after the ethernet
WAN connection is up, the router's DHCP server will offer the
connection's IP address to one LAN client. All incoming or
outgoing traffic will be routed without NAT.
Regardless the WAN connection's state, the router always binds to the LAN IP address (Default: 192.168.50.1). So when the ethernet WAN is connected, the LAN client could access the router's web admin by manually configuring its IP address to the same subnet as the router's LAN IP address (e.g. 192.168.50.10).
Note: when this option is firstly enabled, the LAN client may not be able to refresh its IP address to the ethernet WAN IP address in a timely fashion. The LAN client may have to manually renew its IP address from DHCP server. After this option is enabled, the DHCP lease time will be 2 minutes. I.e. the LAN client could refresh its IP address and access the network at most one minute after the ethernet WAN connection goes up.
This option allows you to choose whether to remain connected
when this WAN connection is no longer in the highest priority
and has entered the standby state. When
is
chosen, upon bringing up this WAN connection to active, it will
be immediately available for use.
If this WAN connection is charged by connection time, you may
want to set this option to
so that connection will be
made only when needed.
SpeedFusion VPN may use connected standby WAN for failover if link failure detected on the higher priority WAN, you can set this option to Disconnect to avoid data passing through.
If the checkbox is
, this option is disabled and the
system will not reply to any ICMP ping echo requests to the
WAN IP addresses of this WAN connection.
Default:
(Yes)
This field refers to the maximum upload speed.
This value is referenced when default weight is chosen for outbound traffic and traffic prioritization. A correct value can result in effective traffic prioritization and efficient use of upstream bandwidth.
This field refers to the maximum download speed.
Default weight control for outbound traffic will be adjusted according to this value.
The Static IP connection method is suitable if your ISP provides a static IP address to connect directly.
NAT allows substituting the real address in a packet with a mapped address that is routable on the destination network. By clicking the help icon in this field, you can display the
option, if your network requires it.
These settings allow you to specify the information required in order to communicate on the Internet via a fixed Internet IP address. The information is typically determined by and can be obtained from the ISP.
Each ISP may provide a set of DNS servers for DNS lookups. This setting specifies the DNS (Domain Name System) servers to be used when a DNS lookup is routed through this connection.
Selecting
results in
the DNS servers being assigned by the WAN DHCP server to be
used for outbound DNS lookups over the connection. (The DNS
servers are obtained along with the WAN IP address assigned
from the DHCP server.
When
is selected,
you may enter custom DNS server addresses for this WAN
connection into the
and
fields.
The PPPoE connection method is suitable if your ISP provides a login ID/password to connect via PPPoE.
NAT allows substituting the real address in a packet with a mapped address that is routable on the destination network. By clicking the help icon in this field, you can display the
option, if your network requires it. Enter the required information in these fields in order to connect via PPPoE to the ISP. The parameter values are determined by and can be obtained from the ISP. Verify your password by entering it again in this field. Service name is provided by the ISP.
If your ISP provides a PPPoE IP address, enter it here.
This is the time interval between each Keep-Alive packet.
This is the number of consecutive Keep-Alive check failures before treating PPPoE connection as down.
Each ISP may provide a set of DNS servers for DNS lookups. This setting specifies the DNS (Domain Name System) servers to be used when a DNS lookup is routed through this connection.
Selecting
results in
the DNS servers being assigned by the WAN DHCP server to be
used for outbound DNS lookups over the connection. (The DNS
servers are obtained along with the WAN IP address assigned
from the DHCP server.)
When
is selected, you
may enter custom DNS server addresses for this WAN connection
into the
and
fields.
L2TP has all the compatibility and convenience of PPTP with greater security. Combine this with IPsec for a good balance between ease of use and security.
NAT allows substituting the real address in a packet with a mapped address that is routable on the destination network. By clicking the help icon in this field, you can display the
option, if your network requires it.
Enter the required information in these fields in order to connect via L2TP to your ISP.
The parameter values are determined by and can be obtained from your ISP.
Verify your password by entering it again in this field.
L2TP server address is a parameter which is provided by your ISP.
.
Your ISP will also indicate whether the server IP address is Dynamic or Static. Please click the appropriate value.
Each ISP may provide a set of DNS servers for DNS lookups. This setting specifies the DNS (Domain Name System) servers to be used when a DNS lookup is routed through this connection.
Selecting
results in
the DNS servers assigned by the PPPoE server to be used for
outbound DNS lookups over the WAN connection.
(The DNS servers are obtained along with the WAN IP address assigned from the PPPoE server.)
When
is selected,
you can enter custom DNS server addresses for this WAN
connection into the
and
fields.
This connection method is suitable if your ISP provides a static WAN IP and Tunnel IP via GRE.
NAT allows substituting the real address in a packet with a mapped address that is routable on the destination network. By clicking the help icon in this field, you can display the
option, if your network requires it. These settings allow you to specify the information required in order to communicate on the Internet via a fixed Internet IP address. The information is typically determined by and can be obtained from the ISP. This field allows you to enter the IP address of the remote GRE. This field allows you to enter the IP address of the local tunnel for the GRE tunnel connection. This field allows you to enter the IP address of the remote tunnel for the GRE tunnel connection. This field is to enter the NAT IP address for outgoing via GRE tunnel.
Each ISP may provide a set of DNS servers for DNS lookups. This setting specifies the DNS (Domain Name System) servers to be used when a DNS lookup is routed through this connection.
Selecting
results
in the DNS servers assigned by the PPPoE server to be used
for outbound DNS lookups over the WAN connection.
(The DNS servers are obtained along with the WAN IP address assigned from the PPPoE server.)
When
is
selected, you can enter custom DNS server addresses for this
WAN connection into the
and
fields.
To access/configure the Cellular WAN settings, click
may click the "
" link to view the Cellular WAN details/status.
. You
This is the International Mobile Subscriber Identity which uniquely identifies the SIM card. This is applicable to 3G modems only. This is a unique number assigned to a SIM card (https://techterms.com/ definition/sim_card) used in a cellular device. Thi field is to display the mobile telephone number of the SIM card. Some Pepwave routers support both HSPA and EV-DO. For Sprint or Verizon Wireless EV-DO users, a unique MEID identifier code (in hexadecimal format) is used by the carrier to associate the EV-DO device with the user. This information is presented in hex and decimal format. This is the unique ID for identifying the modem in GSM/HSPA mode.
Indicate a name you wish to give this Cellular WAN connection Click the checkbox to toggle the on and off state of this connection.
This option allows you to configure the WAN connection whether for normal daily usage or as a backup connection only.
If
is chosen, the WAN connection will be kept on
continuously, regardless of the priority of other WAN
connections.
If
is chosen, the WAN connection will depend on other
WAN connections. It will not be used when one or more higher
priority dependent WAN connections are connected.
If this is checked, the connection will be working independent from other Backup WAN connections. Those in Backup Priority will ignore the status of this WAN connection, and will be used when none of the other higher priority connections are available.
This option allows you to select the routing method to be used in routing IP frames via the WAN connection. The mode can be either NAT (Network Address Translation) or IP Forwarding.
In the case if you need to choose IP Forwarding for your
scenario. Click the
button to enable IP Forwarding.
is available for configuration when you click here for other DHCP settings.
This option allows you to configure the management IP address for the DHCP WAN connection.
Each ISP may provide a set of DNS servers for DNS lookups. This setting specifies the DNS (Domain Name System) servers to be used when a DNS lookup is routed through this connection.
Selecting Obtain DNS server address automatically results in the DNS servers assigned by the WAN DHCP server being used for outbound DNS lookups over the connection. (The DNS servers are obtained along with the WAN IP address assigned by the DHCP server.)
When Use the following DNS server address(es) is selected, you may enter custom DNS server addresses for this WAN connection into the DNS server 1 and DNS server 2 fields.
When this IP Passthrough option is active, after the cellular WAN connection is up, the router's DHCP server will offer the connection's IP address to one LAN client. All incoming or outgoing traffic will be routed without NAT.
Regardless the WAN connection's state, the router always binds to the LAN IP address (Default: 192.168.50.1). So when the cellular WAN is connected, the LAN client could access the router's web admin by manually configuring its IP address to the same subnet as the router's LAN IP address (e.g. 192.168.50.10).
Note: when this option is firstly enabled, the LAN client may not be able to refresh its IP address to the cellular WAN IP address in a timely fashion. The LAN client may have to manually renew its IP address from DHCP server. After this option is enabled, the DHCP lease time will be 2 minutes. I.e. the LAN client could refresh its IP address and access the network at most one minute after the cellular WAN connection goes up
This option allows you to choose whether to remain connected or disconnected when this WAN connection is no longer in the highest priority and has entered the standby state. When
is chosen, bringing up this WAN connection to active makes it immediately available for use.
If this is checked, the connection will disconnect when idle after the configured Time value. This option is disabled by default.
If the checkbox is unticked, this option is disabled and the system will not reply to any ICMP ping echo requests to the WAN IP addresses of this WAN connection.
Default:
If "
" is
selected, the SIM card will be switching according to the
schedule time in the SIM Cards Alternate.
If "
" is selected, you can designate the
priority of the SIM cards (SIM A/ SIM B/ Remote SIM/
SpeedFusion Connect) and connect to.
For routers that support the SIM Injector, you may select the "Remote SIM" to provision a SIM from a SIM Injector. Further details on the SIM Injector found is available here: https:// www.peplink.com/products/sim-injector/ (https:// www.peplink.com/products/sim-injector/).
If "
" is selected in the SIM card section,
the
will be shown.
You may need to enable the remote SIM Host settings in the
Remote SIM management, see the
or
for more details on FusionSIM. After that, click on "
" to show the serial number(s) of
the connected SIM Injector(s).
If you want to select a specific SIM, in the Cellular Settings, type " " and then the number of the SIM slot, eg.1111-2222-3333:7.
This option is allowing to switch to another SIM cards when the Cellular WAN reached fallback timeout.
If "
" is
selected in the SIM Card section, the SIM Cards Alternate will
be shown:
You may set the schedule time for for switching between SIM A only and SIM B only.
This drop-down menu allows restricting cellular to particular
band. Click the
button to enable the selection of specific
bands.
Cellular WANs by default will only handover from 3G to LTE network when there is no active data traffic, enable this option will make it run the handover procedures after fallback to 3G for a defined effective period, even this may interrupt the connectivity for a short while.
When set to
, band selection allows for automatically
connecting to available, supported bands (frequencies) .
When set to Manual, you can manually select the bands
(frequencies) the SIM will connect to.
This checkbox enables data roaming on this particular SIM card. When data roaming is enabled this option allows you to select in which countries the SIM has a data connection. The option is configured by using MMC (country) codes.Please check your service provider's data roaming policy before proceeding.
Choose from
or
to use those
authentication methods exclusively. Select
to
automatically choose an authentication method.
This setting allows you to configure the APN settings of your
connection. If
is selected, the mobile operator should be
detected automatically. The connected device will be
configured and connection will be made automatically. If there
is any difficulty in making connection, you may select
to enter your carrier's
,
,
, and
settings manually. The correct values can be
obtained from your carrier. The default and recommended
setting is
.
When
is selected, the information in these fields will be
filled automatically. Select
to customize these
parameters. The parameter values are determined by and can
be obtained from the ISP.
Check the box Enable to enable bandwidth usage monitoring on this WAN connection for each billing cycle. When this option is not enabled, bandwidth usage of each month is still being tracked but no action will be taken.
If email notification is enabled, you will be notified by email when usage hits 75% and 95% of the monthly allowance. If
is checked, this WAN connection will be disconnected automatically when the usage hits the monthly allowance. It will not resume connection unless this option has been turned off or the usage has been reset when a new billing cycle starts.
This option allows you to define which day of the month each billing cycle begins.
This field is for defining the maximum bandwidth usage allowed for the WAN connection each month.
If signal threshold is defined, this connection will be treated as down when a weaker than threshold signal is determined. The following values are used by the threshold scale:
To define the threshold manually using specific signal strength values, please click on the question Mark and the following field will be visible.
To access/configure the Cellular WAN settings, click .
Enter a name to represent this Wi-Fi WAN connection.
Click the checkbox to toggle the on and off state of this connection.
This option allows you to configure the WAN connection whether for normal daily usage or as a backup connection only.
If
is chosen, the WAN connection will be kept on
continuously, regardless of the priority of other WAN
connections.
If
is chosen, the WAN connection will depend on other
WAN connections. It will not be used when one or more higher
priority dependent WAN connections are connected.
If this is checked, the connection will be working independent from other Backup WAN connections. Those in Backup Priority will ignore the status of this WAN connection, and will be used when none of the other higher priority connections are available.
This option allows you to select the routing method to be used in routing IP frames via the WAN connection. The mode can be either NAT (Network Address Translation) or IP Forwarding.
In the case if you need to choose IP Forwarding for your scenario. Click the button to enable IP Forwarding.
This setting specifies the state of the WAN connection while in
standby. The available options are
and
.
If this setting is disabled, the WAN connection will not respond to ICMP ping requests. By default, this setting is enabled.
Select the channel width for this Wi-Fi WAN. 20MHz will have greater support for older devices using 2.4Ghz, while 40MHz is appropriate for networks with newer devices that connect using 5Ghz
Determine whether the channel will be automatically selected. If you select custom, the following table will appear:
If you are setting up a network with many Wi-Fi devices in close proximity, then you can configure the output power here. Click the "boost" button for additional power. However, with that option ticked, output power may exceed local regulatory limits.
Selecting Auto will enable the router to automatically determine the best data rate, while manually selecting a rate will force devices to connect using the fixed rate.
Checking this box will enable Wi-Fi roaming. Click the for additional options.
icon
This option is to specify whether the Wi-Fi WAN will connect to any open mode access points it finds. This sets the threshold for the number of missed beacons. Configure Channel Scan Interval in ms.
You can manually create a profile to connect to a Wi-Fi connection. This is useful for creating a profile for connecting to hidden-SSID access points. Click
to get started.
This will open a window similar to the one shown below
Enter a name to represent this Wi-Fi connection.
This option allows you to select which security policy is used for this wireless network. Available options:
Enter the password for the wireless network. Configure the BSSID. The BSSID is the MAC address of the wireless access point (WAP). Choose DHCP or Static IP for the Wi-Fi WAN connection method. Configure the DNS servers that this WAN connection should use.
The remaining WAN-related settings are common to the WAN connection:
This is the port speed of the WAN connection. It should be set to the same speed as the connected device in case of any port negotiation problems.
When a static speed is set, you may choose whether to advertise its speed to the peer device or not. Advertise Speed is selected by default. You can choose not to advertise the port speed if the port has difficulty in negotiating with the peer device.
Default: Auto
This field is for specifying the Maximum Transmission Unit value of the WAN connection. An excessive MTU value can cause file downloads stall shortly after connected. You may consult your ISP for the connection's MTU value. Default value is 1440.
This field is for specifying the Maximum Segment Size of the WAN connection.
When Auto is selected, MSS will be depended on the MTU value. When Custom is selected, you may enter a value for MSS. This value will be announced to remote TCP servers for maximum data that it can receive during the establishment of TCP connections.
Some Internet servers are unable to listen to MTU setting if ICMP is filtered by firewall between the connections.
Normally, MSS equals to MTU minus 40. You are recommended to reduce the MSS only if changing of the MTU value cannot effectively inform some remote servers to size down data size.
Default: Auto
Some service providers (e.g. cable network) identify the client's MAC address and require client to always use the same MAC address to connect to the network. If it is the case, you may change the WAN interface's MAC address to the client PC's one by entering the PC's MAC address to this field. If you are not sure, click the Default button to restore to the default value.
Check the box to assign a VLAN to the interface.
To ensure traffic is routed to healthy WAN connections only, the Pepwave router can
periodically check the health of each WAN connection. The health check settings for
each WAN connection can be independently configured via
.
This setting specifies the health check method for the WAN
connection. This value can be configured as
,
,
, or
. The default method is
. For mobile
Internet connections, the value of
can be configured as
or
.
When
is chosen in the
considered as up. The connection will
routing errors.
field, the WAN connection will always be be treated as down in the event of IP
ICMP ping packets will be issued to test the connectivity with a configurable target IP address or hostname. A WAN connection is considered as up if ping responses are received from either one or both of the ping hosts.
This setting specifies IP addresses or hostnames with which connectivity is to be tested via ICMP ping. If
is checked, the target ping host will be the first DNS server for the corresponding WAN connection. Reliable ping hosts with a high uptime should be considered. By default, the first two DNS servers of the WAN connection are used as the ping hosts.
DNS lookups will be issued to test connectivity with target DNS servers. The connection will be treated as up if DNS responses are received from one or both of the servers, regardless of whether the result was positive or negative.
This field allows you to specify two DNS hosts' IP addresses with which connectivity is to be tested via DNS lookup.
If
is
checked, the first two DNS servers will be the DNS lookup targets for
checking a connection's health. If the box is not checked,
must
be filled, while a value for
is optional.
If
is selected and no response is
received from all specified DNS servers, DNS lookups will also be
issued to some public DNS servers. A WAN connection will be treated
as down only if there is also no response received from the public
DNS servers.
Connections will be considered as up if DNS responses are received from any one of the health check DNS servers, regardless of a positive or negative result. By default, the first two DNS servers of the WAN connection are used as the health check DNS servers.
HTTP connections will be issued to test connectivity with configurable URLs and strings to match.
The URL will be retrieved when performing an HTTP health check.
When
is left blank, a health check will pass if the
HTTP return code is between 200 and 299 (Note: HTTP redirection
codes 301 or 302 are treated as failures). When
is
filled, a health check will pass if the HTTP return code is between 200
and 299 and if the HTTP response content contains the string.
If
is also provided, a health check will pass if either one of the
tests passed.
This setting specifies the timeout in seconds for ping/DNS lookup
requests. The default timeout is
.
This setting specifies the time interval in seconds between ping or
DNS lookup requests. The default health check interval is
.
This setting specifies the number of consecutive ping/DNS lookup
timeouts after which the Pepwave router will treat the
corresponding WAN connection as down. Default health retries is set
to . Using the default
setting of , the
corresponding WAN connection will be treated as down after three
consecutive timeouts.
This setting specifies the number of consecutive successful ping/
DNS lookup responses that must be received before the Pepwave
router treats a previously down WAN connection as up again. By
default,
is set to . Using the default setting, a WAN
connection that is treated as down will be considered as up again
upon receiving three consecutive successful ping/DNS lookup
responses.
When the health check method is set to
and health checks fail, the
Pepwave router will automatically perform DNS lookups on public DNS servers. If
the tests are successful, the WAN may not be down, but rather the target DNS
server malfunctioned. You will see the following warning message on the main
page:
If
is enabled, you will be notified by email when
usage hits 75% and 95% of the monthly allowance.
If
is
checked, this WAN connection will be disconnected automatically
when the usage hits the monthly allowance. It will not resume
connection unless this option has been turned off or the usage has
been reset when a new billing cycle starts.
This option allows you to define which day of the month each billing cycle begins.
This field is for defining the maximum bandwidth usage allowed for the WAN connection each month.
Due to different network protocol overheads and conversions, the amount of data reported by this Peplink device is not representative of actual billable data usage as metered by your network provider. Peplink disclaims any obligation or responsibility for any events arising from the use of the numbers shown here.
represents the list of fixed Internet IP addresses assigned by the ISP in the event that more than one Internet IP address is assigned to this WAN connection. Enter the fixed Internet IP addresses and the corresponding subnet mask, and then click the
button to populate IP address entries to the .
Pepwave routers are capable of registering the domain name relationships to dynamic DNS service providers. Through registration with dynamic DNS service provider(s), the default public Internet IP address of each WAN connection can be associated with a host name. With dynamic DNS service enabled for a WAN connection, you can connect to your WAN's IP address from the external, even if its IP address is dynamic. You must register for an account from the listed dynamic DNS service providers before enabling this option.
If the WAN connection's IP address is a reserved private IP address (i.e., behind a NAT router), the public IP of each WAN will be automatically reported to the DNS service provider.
Either upon a change in IP addresses or every 23 days without link reconnection, the Pepwave router will connect to the dynamic DNS service provider to perform an IP address update within the provider's records.
The settings for dynamic DNS service provider(s) and the association of hostname(s) are configured via
.
This setting specifies the dynamic DNS service provider to be used for the WAN based on supported dynamic DNS service providers:
Disabled changeip.com dyndns.org no-ip.org DNS-O-Matic Others...
Support custom Dynamic DNS servers by entering its URL. Works with any service compatible with DynDNS API.
Select
to disable this feature.
This setting specifies the registered user name for the dynamic DNS service.
This setting specifies the password for the dynamic DNS service.
This field allows you to specify a list of host names or domains to be associated with the public Internet IP address of the WAN connection. If you need to enter more than one host, use a carriage return to separate them.
In order to use dynamic DNS services, appropriate host name registration(s) and a valid account with a supported dynamic DNS service provider are required. A dynamic DNS update is performed whenever a WAN's IP address changes (e.g., the IP is changed after a DHCP IP refresh, reconnection, etc.). Due to dynamic DNS service providers' policy, a dynamic DNS host will automatically expire if the host record has not been updated for a long time. Therefore the Pepwave router performs an update every 23 days, even if a WAN's IP address has not changed.
Pepwave bandwidth bonding SpeedFusionTM is our patented technology that enables our SD-WAN routers to bond multiple Internet connections to increase site-to-site bandwidth and reliability. SpeedFusion functionality securely connects your Pepwave router to another Pepwave or Peplink device (Peplink Balance 210/310/380/580/710/1350 only). Data, voice, or video communications between these locations are kept confidential across the public Internet.
Bandwidth bonding SpeedFusionTM is specifically designed for multi-WAN environments. In case of failures and network congestion at one or more WANs, other WANs can be used to continue carrying the network traffic.
Different models of our SD-WAN routers have different numbers of site-to-site connections allowed. End-users who need to have more site-to-site connections can purchase a SpeedFusion license to increase the number of site-to-site connections allowed.
Pepwave routers can aggregate all WAN connections' bandwidth for routing SpeedFusionTM traffic. Unless all the WAN connections of one site are down, Pepwave routers can keep the VPN up and running.
VPN bandwidth bonding is supported in Firmware 5.1 or above. All available bandwidth will be utilized to establish the VPN tunnel, and all traffic will be load balanced at packet level across all links. VPN bandwidth bonding is enabled by default.
To configure SpeedFusion VPN, navigate to
.
The local LAN subnet and subnets behind the LAN (defined under
on the
LAN settings page) will be advertised to the VPN. All VPN members (branch offices and
headquarters) will be able to route to local subnets.
Note that all LAN subnets and the subnets behind them must be unique. Otherwise, VPN members will not be able to access each other.
All data can be routed over the VPN using the 256-bit AES encryption standard. To
configure, navigate to
and click the
button
to create a new VPN profile (you may have to first save the displayed default profile in
order to access the
button). Each profile specifies the settings for making
VPN connection with one remote Pepwave or Peplink device. Note that available
settings vary by model.
A list of defined SpeedFusion connection profiles and a
option will be shown. Click the
button to create a new VPN connection
profile for making a VPN connection to a remote Pepwave or Peplink device via the
available WAN connections. Each profile is for making a VPN connection with one
remote Pepwave or Peplink Device.
This field is for specifying a name to represent this profile. The name can be any combination of alphanumeric characters (0-9, A-Z, a-z), underscores (_), dashes (-), and/or non-leading/trailing spaces ( ).
When this box is checked, this VPN connection profile will be enabled. Otherwise, it will be disabled.
By default, VPN traffic is encrypted with
. If is
selected on both sides of a VPN connection, no encryption
will be applied.
Select from
,
, or
to
specify the method the Pepwave MAX will use to authenticate
peers. When selecting
, be sure to enter a
unique peer ID number in the
field.
This optional field becomes available when is selected as the Pepwave router's VPN method, as explained above.
defines the pre-shared key used for this particular VPN connection. The VPN connection's session key will be further protected by the pre-shared key. The connection will be up only if the pre-shared keys on each side match. When the peer is running firmware 5.0+, this setting will be ignored.
Enter Remote IDs either by typing out each Remote ID and
Pre-shared Key, or by pasting a CSV. If you wish to paste a
CSV, click the
icon next to the "Remote ID / Preshared
Key" setting.
These optional fields become available when
is
selected as the Pepwave MAX's VPN authentication method,
as explained above. To authenticate VPN connections using
X.509 certificates, copy and paste certificate details into these
fields. To get more information on a listed X.509 certificate,
click the
link below the field.
When this option is enabled, the router will allow multiple peers to run using the same remote ID.
Check this box to allow the local DHCP server to assign an IP
address to the remote peer. When
is enabled, all
remote traffic over the VPN will be tagged with the assigned
IP address using network address translation.
If
is not enabled, you can enter a remote peer's
WAN IP address or hostname(s) here. If the remote uses
more than one address, enter only one of them here.
Multiple hostnames are allowed and can be separated by a
space character or carriage return. Dynamic-DNS host names
are also accepted.
This field is optional. With this field filled, the Pepwave MAX will initiate connection to each of the remote IP addresses until it succeeds in making a connection. If the field is empty, the Pepwave MAX will wait for connection from the remote peer. Therefore, at least one of the two VPN peers must specify this value. Otherwise, VPN connections cannot be established.
Define path cost for this profile.
OSPF will determine the best route through the network using the assigned cost.
Default: 10
This field is used to specify a UDP port number for
transporting outgoing VPN data. If
is selected, UDP
port 4500 will be used. Port 32015 will be used if the remote
unit uses Firmware prior to version 5.4 or if port 4500 is
unavailable. If
is selected, enter an outgoing port
number from 1 to 65535.
Click the
icon to configure data stream using TCP
protocol [EXPERIMENTAL].In the case TCP protocol is used, the exposed TCP session option can be authorised to work with TCP accelerated WAN link.
Define maximum download and upload speed to each individual peer. This functionality requires the peer to use SpeedFusion VPN version 4.0.0 or above.
While using SpeedFusion VPN, utilize multiple WAN links to reduce the impact of packet loss and get the lowest possible latency at the expense of extra bandwidth consumption. This is suitable for streaming applications where the average bitrate requirement is much lower than the WAN's available bandwidth.
Off Disable WAN Smoothing.
Normal The total bandwidth consumption will be at most 2x of the original data traffic.
Medium The total bandwidth consumption will be at most 3x of the original data traffic.
High The total bandwidth consumption depends on the number of connected active tunnels.
A A
Forward Error Correction (FEC) can help to recover packet loss by using extra bandwidth to send redundant data packets. Higher FEC level will recover packets on a higher loss rate link.
The expected overhead of Low is 13.3% and High is 26.7%.
Require peer using SpeedFusion VPN version 8.0.0 and above.
Receive Buffer can help to reduce out-of-order packets and jitter, but will introduce extra latency to the tunnel. Default is 0 ms, which disables the buffer, and maximum buffer size is 2000 ms.
If the packet size is larger than the tunnel's MTU, it will be fragmented inside the tunnel in order to pass through.
Select Always to fragment any packets that are too large to send, or Use DF Flag to only fragment packets with Don't Fragment bit cleared. This can be useful if your application does Path MTU Discovery, usually sending large packets with DF bit set, if allowing them to go through by fragmentation, the MTU will not be detected correctly.
Checking this button enables the use of IP ToS header field.
Traffic will be stopped for links that exceed the specified millisecond value with respect to the lowest latency link. (e.g. Lowest latency is 100ms, a value of 500ms means links with latency 600ms or more will not be used)
A Advanced feature, please click the activate.
button on the top right-hand corner to
To enable Layer 2 Bridging between SpeedFusion VPN profiles, navigate to and refer to instructions in section
(https://manual.peplink.com/documentation/pepwave-max-user-manual/ch-8configuring-the-lan-interfaces/basic-settings/) 8.1
This option allows you to select the desired out-bound traffic distribution policy:
Bonding Aggregate multiple WAN-to-WAN links into a single higher throughput tunnel.
Dynamic Weighted Bonding Aggregates WAN-to-WAN links with similar latencies.
By default, Bonding is selected as a traffic distribution policy.
For most WANs, especially on cellular networks, the latency will increase when the link becomes more congested.
Setting the as congested more aggressively.
to
will treat the link
Setting it to
will allow the latency to increase more before
treating it as congested.
By default, when there is packet loss, it is considered as a congestion event. If this is not the case, select this option to ignore the packet loss event.
Bufferbloat is a phenomenon on the WAN side when it is congested. The latency can become very high due to buffering on the uplink. By default, the Dynamic Weighted Bonding policy will try its best to mitigate bufferbloat by reducing TCP throughput when the WAN is congested. However, as a side effect, the tunnel might not achieve maximum bandwidth.
Selecting this option will mentioned above.
the bufferbloat handling
By default, TCP ACK will be forwarded to remote peers as fast as possible. This will consume more bandwidth, but may help to improve TCP performance as well.
Selecting this option will mentioned above.
the TCP ACK optimization
The default jitter buffer is 150ms, and can be modified from 0ms to 500ms. The jitter buffer may increase the tunnel latency. If you want to keep the latency as low as possible, you can set it to 0ms to disable the buffer.
: If the Receive Buffer is set, the Packet Jitter Buffer will be automatically disabled.
If your device supports it, you can specify the priority of WAN
connections to be used for making VPN connections. WAN
connections set to
will never be used. Only available WAN
connections with the highest priority will be used.
To enable asymmetric connections, connection mapping to
remote WANs, cut-off latency, and packet loss suspension time,
click the
button.
This feature allows you to redirect all traffic to a specified SpeedFusion VPN
connection. Click the
button to select your connection and the following
menu will appear:
You could also specify a DNS server to resolve incoming DNS requests. Click the
checkbox next to
to designate a backup SpeedFusion profile that will
take over, should the main SpeedFusion VPN connection fail.
Some models allow you to set outbound policy and custom outbound rules from
. See
for more information on outbound
policy settings.
The local ID is a text string to identify this local unit when establishing a VPN connection. When creating a profile on a remote unit, this local ID must be entered
in the remote unit's
field. Click the
icon to edit
.
To designate a custom handshake port (TCP), click the
A
radio button and enter the port number you wish to designate.
The bonded VPN can detect routing failures on the path between two sites over each WAN connection. Failed WAN connections will not be used to route VPN traffic. Health check packets are sent to the remote unit to detect any failure. The more frequently checks are sent, the shorter the detection time, although more bandwidth will be consumed.
When
(default) is selected, a health check packet
is sent every five seconds, and the expected detection time is 15
seconds.
When
is selected, a health check packet is sent every three
seconds, and the expected detection time is six seconds.
When
is selected, a health check packet is sent every
second, and the expected detection time is two seconds.
When
is selected, a health check packet is sent every 0.1
second, and the expected detection time is less than one second.
A Advanced feature, please click the activate.
button on the top right-hand corner to
Peplink proprietary SpeedFusionTM uses TCP port 32015 and UDP port 4500 for establishing VPN connections. If you have a firewall in front of your Pepwave devices, you will need to add firewall rules for these ports and protocols to allow inbound and outbound traffic to pass through the firewall.
Want to know more about VPN sub-second session failover? Visit our YouTube Channel (https://www.youtube.com/PeplinkChannel) for a video tutorial!
http://youtu.be/TLQgdpPSY88 (https://youtu.be/TLQgdpPSY88)
Pepwave routers support establishing SpeedFusionTM over WAN connections which are behind a NAT (network address translation) router. To enable a WAN connection behind a NAT router to accept VPN connections, you can configure the NAT router in front of the WAN connection to inbound port-forward TCP port 32015 to the Pepwave router. If one or more WAN connections on Unit A can accept VPN connections (by means of port forwarding or not), while none of the WAN connections on the peer Unit B can do so, you should enter all of Unit A's public IP addresses or hostnames into Unit B's
field. Leave the field in Unit A blank. With this setting, a SpeedFusionTM connection can be set up and all WAN connections on both sides will be utilized. See the following diagram for an example of this setup in use:
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
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.
SpeedFusion VPN status is shown in the Dashboard. The connection status of each connection profile is shown as below.
After clicking the
button at the top right corner of the SpeedFusionTM table,
you will be forwarded to
, where you can view subnet and
WAN connection information for each VPN peer.
The entire interconnected SpeedFusionTM network is a single non-NAT IP network. Avoid duplicating subnets in your sites to prevent connectivity problems when accessing those subnets.
IPsec VPN functionality securely connects one or more branch offices to your company's main headquarters or to other branches. Data, voice, and video communications between these locations are kept safe and confidential across the public Internet.
IPsec VPN on Pepwave routers is specially designed for multi-WAN environments. For instance, if a user sets up multiple IPsec profiles for a multi-WAN environment and WAN1 is connected and healthy, IPsec traffic will go through this link. However, should unforeseen problems (e.g., unplugged cables or ISP problems) cause WAN1 to go down, our IPsec implementation will make use of WAN2 and WAN3 for failover.
Many Pepwave products can make multiple IPsec VPN connections with Peplink, Pepwave, Cisco, and Juniper routers. Note that all LAN subnets and the subnets behind them must be unique. Otherwise, VPN members will not be able to access each other. All data can be routed over the VPN with a selection of encryption standards, such as 3DES, AES-128, and AES-256. To configure IPsec VPN on Pepwave devices that support it, navigate to
Click the
button to create new IPsec VPN profiles that make VPN
connections to remote Pepwave, Cisco, or Juniper routers via available WAN
connections. To edit any of the profiles, click on its associated connection name in the
leftmost column.
This field is for specifying a local name to represent this connection profile.
When this box is checked, this IPsec VPN connection profile will be enabled. Otherwise, it will be disabled.
Two versions of the IKE standards are available:
IKEv1 IKEv2
Check this box and select a WAN to connect to this VPN automatically when the specified WAN is disconnected.
Enter the remote peer's public IP address. For , this is optional.
Policy-based (default) All the matched traffic as defined in Local Networks and Remote Networks will be routed to this IPsec connection, this cannot be overridden by other routing methods.
Route-based Outbound Policy rule is required to route traffic to this tunnel and comes with more flexibility to control how to route traffic compared to Policy-based. If you want to modify the traffic selector instead of using the default (0.0.0.0/0).
: This option is available for certain following models only:
MAX: BR1 ENT, Transit, 700 HW3 or above, HD2 HW5 or above, HD4
Enter the local LAN subnets here. If you have defined static routes, they will be shown here.
Using NAT, you can map a specific local network / IP address to another, and the packets received by remote gateway will appear to be coming from the mapped network / IP address. This allow you to establish IPsec connection to a remote site that has one or more subnets overlapped with local site.
Two types of NAT policies can be defined:
One-to-One NAT policy: if the defined subnet in Local Network and NAT Network has the same size, for example, policy "192.168.50.0/24 > 172.16.1.0/24" will translate the local IP address 192.168.50.10 to 172.16.1.10 and 192.168.50.20 to 172.16.1.20. This is a bidirectional mapping which means clients in remote site can initiate connection to the local clients using the mapped address too.
Many-to-One NAT policy: if the defined NAT Network on the right hand side is an IP address (or having a network prefix /32), for example, policy "192.168.1.0/24 > 172.168.50.1/32" will translate all clients in 192.168.1.0/24 network to 172.168.50.1. This is a unidirectional mapping which means clients in remote site will not be able to initiate connection to the local clients.
Enter the LAN and subnets that are located at the remote site here.
To access your VPN, clients will need to authenticate by your
choice of methods. Choose between the
and
methods of authentication.
Choose
if both IPsec peers use static IP
addresses. Choose
if one of the IPsec
peers uses dynamic IP addresses.
For forced UDP encapsulation regardless of NAT-traversal, tick this checkbox.
This defines the peer authentication pre-shared key used to authenticate this VPN connection. The connection will be up only if the pre-shared keys on each side match.
Available only when
e is chosen as the
method, this field allows you to paste a valid
X.509 certificate.
In
, this field can be left blank. In
, if
is filled on this end
and the peer end, this field can be left blank. Otherwise, this
field is typically a U-FQDN.
In
, this field can be left blank. In
, if
is filled on this end
and the peer end, this field can be left blank. Otherwise, this
field is typically a U-FQDN.
In
, this allows setting up to six encryption
standards, in descending order of priority, to be used in
initial connection key negotiations. In
,
only one selection is permitted.
This is the Diffie-Hellman group used within IKE. This allows two parties to establish a shared secret over an insecure communications channel. The larger the group number, the higher the security.
:
is the default value.
:
is the alternative option.
This setting specifies the lifetime limit of this Phase 1
Security Association. By default, it is set at
seconds.
In
, this allows setting up to six encryption
standards, in descending order of priority, to be used for the
IP data that is being transferred. In
, only
one selection is permitted.
Perfect forward secrecy (PFS) ensures that if a key was compromised, the attacker will be able to access only the data protected by that key.
Do not request for PFS when initiating connection. However, since there is no valid reason to refuse PFS, the system will allow the connection to use PFS if requested by the remote peer. This is the default value.
: 1024-bit Diffie-Hellman group. The larger the group number, the higher the security.
:
is the third option.
This setting specifies the lifetime limit of this Phase 2
Security Association. By default, it is set at
seconds.
Select the appropriate WAN connection from the dropdown menu.
Generic Routing Encapsulation (GRE) is a tunneling protocol that can encapsulate a wide variety of network layer protocols inside virtual point-to-point links over an Internet Protocol network. A GRE tunnel is similar to IPSec or SpeedFusion VPN.
To configure a GRE Tunnel, navigate to
.
Click the
button to create new GRE tunnel profiles that establish tunnel
connections to remote tunnel endpoints via available WAN connections. To edit the
profiles, click on its associated connection name in the leftmost column.
This field is for specifying a name to represent this GRE Tunnel connection profile. When this box is checked, this GRE Tunnel connection profile will be enabled. Otherwise, it will be disabled. This field is for entering the remote GRE's IP address
This field is for specifying the tunnel source IP address.
This field is for specifying the tunnel destination IP address
This field is to select the subnet mask that is to be used for the GRE tunnel. Select the appropriate WAN connection from the drop-down menu.
Input the LAN and subnets that are located at the remote site here.
OpenVPN is a site to site VPN mode that can encapsulate a wide variety of network layer protocols inside virtual point-to-point links over an Internet Protocol network.
To configure a OpenVPN, navigate to .
and click the
This field is for specifying a name to represent this OpenVPN profile.
When this box is checked, this OpenVPN connection profile will be enabled. Otherwise, it will be disabled.
Upload the OpenVPN configuration (.ovpn) file from your service provider.
This option is an optional for you to enter the username and password to login for the OpenVPN connection if the profile need to login. Select the appropriate WAN connection from the drop-down menu.
Pepwave routers can flexibly manage and load balance outbound traffic among WAN connections. The settings for managing and load balancing outbound traffic are located at
.
The menu underneath enables you to define Outbound policy rules:
The bottom-most rule is
. Edit this rule to change the device's default manner
of controlling outbound traffic for all connections that do not match any of the rules
above it. Under the
heading, click
to change these settings.
To rearrange the priority of outbound rules, drag and drop them into the desired sequence.
By default,
is selected as the
. You can select
to change the
algorithm to be used. Please refer to the upcoming sections for the details on the
available algorithms.
To create a custom rule, click
at the bottom of the table.
This setting specifies the name of the outbound traffic rule.
This setting specifies whether the outbound traffic rule takes
effect. When
is checked, the rule takes effect: traffic is
matched and actions are taken by the Pepwave router based on
the other parameters of the rule. When
is unchecked,
the rule does not take effect: the Pepwave router disregards the
other parameters of the rule.
Click the drop-down menu next to the checkbox to apply a time schedule to this custom rule.
This setting specifies the source IP Address, IP Network, MAC Address or Grouped Network for traffic that matches the rule.
This setting specifies the destination IP address, IP network, Domain name, SpeedFusion Cloud, SpeedFusion VPN Profile or Grouped network for traffic that matches the rule.
If
is chosen and a domain name, such as
foobar.com, is entered, any outgoing accesses to foobar.com and
*.foobar.com will match this criterion. You may enter a wildcard
(.*) at the end of a domain name to match any host with a name
having the domain name in the middle. If you enter foobar.*, for
example, www.foobar.com, www.foobar.co.jp, or foobar.co.uk will
also match. Placing wildcards in any other position is not
supported.
Note: if a server has one Internet IP address and multiple server
names, and if one of the names is defined here, access to any
one of the server names will also match this rule.
This setting specifies the IP protocol and port of traffic that matches this rule. Via a drop-down menu, the following protocols can be specified:
Any TCP UDP IP DSCP
Alternatively, the
drop-down menu can
be used to automatically fill in the protocol and port number of
common Internet services (e.g., HTTP, HTTPS, etc.) After
selecting an item from the
drop-down
menu, the protocol and port number remains manually
modifiable.
This setting specifies the behavior of the Pepwave router for the custom rule.
One of the following values can be selected (Note that some Pepwave routers provide only some of these options):
Weighted Balance Persistence Enforced Priority Overflow Least Used Lowest Latency Fastest Response Time
For a full explanation of each Algorithm, please see the following article:
https://forum.peplink.com/t/exactly-how-do-peplinks-loadbalancing-algorithmns-work/8059 (https://forum.peplink.com/t/ exactly-how-do-peplinks-load-balancing-algorithmns-work/8059)
This is to define the outbound traffic weight ratio for each WAN connection.
This field allows you to configure the default action when all the selected Connections are not available.
Traffic will be discarded.
Traffic will be routed to any available Connection, even it is not selected in the list.
Traffic will continue to match the next Outbound Policy rule just like this rule is inactive.
This setting specifies whether to terminate existing IP sessions
on a less preferred WAN connection in the event that a more
preferred WAN connection is recovered. This setting is applicable
to the
algorithms. By default, this setting is disabled. In
this case, existing IP sessions will not be terminated or affected
when any other WAN connection is recovered. When this setting
is enabled, existing IP sessions may be terminated when
another WAN connection is recovered, such that only the
preferred healthy WAN connection(s) is used at any point in
time.
This setting specifies the ratio of WAN connection usage to be applied on the specified
IP protocol and port. This setting is applicable only when
is set to
.
The amount of matching traffic that is distributed to a WAN connection is proportional to the weight of the WAN connection relative to the total weight. Use the sliders to change each WAN's weight.
For example, with the following weight settings:
Ethernet WAN1: 10 Ethernet WAN2: 10 Wi-Fi WAN: 10 Cellular 1: 10 Cellular 2: 10
USB: 10
Total weight is 60 = (10 +10 + 10 + 10 + 10 + 10). Matching traffic distributed to Ethernet WAN1 is 16.7% = (10 / 60 x 100%. Matching traffic distributed to Ethernet WAN2 is 16.7% = (10 / 60) x 100%. Matching traffic distributed to Wi-Fi WAN is 16.7% = (10 / 60) x 100%. Matching traffic distributed to Cellular 1 is 16.7% = (10 / 60) x 100%. Matching traffic distributed to Cellular 2 is 16.7% = (10 / 60) x 100%. Matching traffic distributed to USB is 16.7% = (10 / 60) x 100%.
The configuration of persistent services is the solution to the few situations where link load distribution for Internet services is undesirable. For example, for security reasons, many e-banking and other secure websites terminate the session when the client computer's Internet IP address changes mid-session. In general, different Internet IP addresses represent different computers. The security concern is that an IP address change during a session may be the result of an unauthorized intrusion attempt. Therefore, to prevent damages from the potential intrusion, the session is terminated upon the detection of an IP address change. Pepwave routers can be configured to distribute data traffic across multiple WAN connections. Also, the Internet IP depends on the WAN connections over which communication actually takes place. As a result, a LAN client computer behind the Pepwave router may communicate using multiple Internet IP addresses. For example, a LAN client computer behind a Pepwave router with three WAN connections may communicate on the Internet using three different IP addresses. With the persistence feature, rules can be configured to enable client computers to persistently utilize the same WAN connections for e-banking and other secure websites. As a result, a client computer will communicate using one IP address, eliminating the issues mentioned above.
There are two persistent modes:
and
.
The same WAN connection will be used for traffic matching the rule and originating from the same machine, regardless of its destination. This option will provide the highest level of application compatibility.
The same WAN connection will be used for traffic matching the rule, originating from the same machine, and going to the same destination. This option can better distribute loads to WAN connections when there are only a few client machines.
The default mode is
. When there are multiple client requests, they can be
distributed (persistently) to WAN connections with a weight. If you choose
in
, the weights will be automatically adjusted according to each WAN's
which is specified in the WAN settings page). If you choose
, you can customize the weight of each WAN manually by using the sliders.
This setting specifies the WAN connection usage to be applied on the specified IP
protocol and port. This setting is applicable only when
is set to
.
Matching traffic will be routed through the specified WAN connection, regardless of the health check status of the WAN connection. Starting from Firmware 5.2, outbound traffic can be enforced to go through a specified SpeedFusionTM connection.
This setting specifies the priority of the WAN connections used to route the specified network service. The highest priority WAN connection available will always be used for routing the specified type of traffic. A lower priority WAN connection will be used only when all higher priority connections have become unavailable.
Starting from Firmware 5.2, outbound traffic can be prioritized to go through SpeedFusionTM connection(s). By default, VPN connections are not included in the priority list.
Configure multiple distribution rules to accommodate different kinds of services.
The traffic matching this rule will be routed through the healthy WAN connection that has the highest priority and is not in full load. When this connection gets saturated, new sessions will be routed to the next healthy WAN connection that is not in full load.
Drag and drop to specify the order of WAN connections to be used for routing traffic. Only the highest priority healthy connection that is not in full load will be used.
The traffic matching this rule will be routed through the healthy WAN connection that
is selected in
and has the most available download bandwidth. The
available download bandwidth of a WAN connection is calculated from the total
download bandwidth specified on the WAN settings page and the current download
usage. The available bandwidth and WAN selection is determined every time an IP
session is made.
The traffic matching this rule will be routed through the healthy WAN connection that
is selected in
and has the lowest latency. Latency checking packets are
issued periodically to a nearby router of each WAN connection to determine its latency
value. The latency of a WAN is the packet round trip time of the WAN connection.
Additional network usage may be incurred as a result.
The roundtrip time of a 6M down/640k uplink can be higher than that of a 2M down/2M up link because the overall round trip time is lengthened by its slower upload bandwidth, despite its higher downlink speed. Therefore, this algorithm is good for two scenarios:
All WAN connections are symmetric; or
A latency sensitive application must be routed through the lowest latency WAN, regardless of the WAN's available bandwidth.
is available on some Pepwave routers for use by advanced users. To
enable the feature, click on the help icon and click
.
In Expert Mode, a new special rule,
, is displayed in the
table. This rule represents all SpeedFusionTM routes learned from
remote VPN peers. By default, this bar is on the top of all custom rules. This position
means that traffic for remote VPN subnets will be routed to the corresponding VPN
peer. You can create custom
or
rules and move them
above the bar to override the SpeedFusionTM routes.
Upon disabling Expert Mode, all rules above the bar will be removed.
Pepwave routers can act as a firewall that blocks, by default, all inbound access from the Internet. By using port forwarding, Internet users can access servers behind the Pepwave router. Inbound port forwarding rules can be defined at
.
To define a new service, click
.
This setting specifies whether the inbound service takes effect.
When
is checked, the inbound service takes effect: traffic is
matched and actions are taken by the Pepwave router based on
the other parameters of the rule. When this setting is disabled, the
inbound service does not take effect: the Pepwave router
disregards the other parameters of the rule.
This setting identifies the service to the system administrator. Valid values for this setting consist of only alphanumeric and underscore "_" characters.
The
setting, along with the
setting, specifies the
protocol of the service as TCP, UDP, ICMP, or IP. Traffic that is
received by the Pepwave router via the specified protocol at the
specified port(s) is forwarded to the LAN hosts specified by the
setting. Please see below for details on the
and
settings. Alternatively, the
drop-
down menu can be used to automatically fill in the protocol and a
single port number of common Internet services (e.g. HTTP, HTTPS,
etc.). After selecting an item from the
drop-down menu, the protocol and port number remain manually
modifiable.
The
setting specifies the port(s) that correspond to the
service, and can be configured to behave in one of the following
manners:
,
,
,
, and
: all traffic that is received by the Pepwave router via the
specified protocol is forwarded to the servers specified by the
setting. For example, with
set to , and
set to
, all TCP traffic is forwarded to the configured
servers.
: traffic that is received by the Pepwave router via the
specified protocol at the specified port is forwarded via the same
port to the servers specified by the
setting. For example,
with
set to , and
set to
and
80, TCP traffic received on port 80 is forwarded to the
configured servers via port 80.
: traffic that is received by the Pepwave router via the
specified protocol at the specified port range is forwarded via the
same respective ports to the LAN hosts specified by the
setting. For example, with
set to , and
set to
and
80-88, TCP traffic received on ports
80 through 88 is forwarded to the configured servers via the
respective ports.
: traffic that is received by Pepwave router via the
specified protocol at the specified port is forwarded via a different
port to the servers specified by the
setting.
For example, with
set to , and
set to
,
80, and
88, TCP traffic on port
80 is forwarded to the configured servers via port 88.
(Please see below for details on the
setting.)
: traffic that is received by the Pepwave router via
the specified protocol at the specified port range is forwarded via a
different port to the servers specified by the
setting.
This setting specifies the WAN connections and Internet IP address(es) from which the service can be accessed.
This setting specifies the LAN IP address of the server that handles the requests for the service.
UPnP and NAT-PMP are network protocols which allow a computer connected to the LAN port to automatically configure the router to allow parties on the WAN port to connect to itself. That way, the process of inbound port forwarding becomes automated.
When a computer creates a rule using these protocols, the specified TCP/UDP port of all WAN connections' default IP address will be forwarded.
Check the corresponding box(es) to enable UPnP and/or NAT-PMP. Enable these features only if you trust the computers connected to the LAN ports.
When the options are enabled, a table listing all the forwarded ports under these two
protocols can be found at
.
NAT mappings allow IP address mapping of all inbound and outbound NAT'd traffic to
and from an internal client IP address. Settings to configure NAT mappings are located
at
.
To add a rule for NAT mappings, click
.
NAT mapping rules can be defined for a single LAN
, an
, or an
.
This refers to the LAN host's private IP address. The system maps
this address to a number of public IP addresses (specified below) in
order to facilitate inbound and outbound traffic. This option is only
available when
is selected.
The IP range is a contiguous group of private IP addresses used by
the LAN host. The system maps these addresses to a number of
public IP addresses (specified below) to facilitate outbound traffic.
This option is only available when
is selected.
The IP network refers to all private IP addresses and ranges
managed by the LAN host. The system maps these addresses to a
number of public IP addresses (specified below) to facilitate
outbound traffic. This option is only available when
is
selected.
This setting specifies the WAN connections and corresponding
WAN-specific Internet IP addresses on which the system should
bind. Any access to the specified WAN connection(s) and IP
address(es) will be forwarded to the LAN host. This option is only
available when
is selected in the
field.
inbound mapping is not needed for WAN connections in drop-in mode or IP forwarding mode. Also note that each WAN IP address can be associated to one NAT mapping only.
This setting specifies the WAN IP addresses that should be used when an IP connection is made from a LAN host to the Internet. Each LAN host in an IP range or IP network will be evenly mapped to one of each selected WAN's IP addresses (for better IP address utilization) in a persistent manner (for better application compatibility).
if you do not want to use a specific WAN for outgoing
accesses, you should still choose default here, then customize the
outbound access rule in the
section. Also note
that WAN connections in drop-in mode or IP forwarding mode are
not shown here.
Click
to save the settings when configuration has been completed.
Inbound firewall rules override the
settings.
#4310) #4304)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4311) (https://manual.peplink.com/peplink-b-one-series-user-manual/ (https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4305)
Other than the three default user groups, you can add more user groups by entering the group name into the column and clicking the ` ` button. The user group limit is up to 10.
This section is to define how much minimum bandwidth will be reserved to each user
group when a WAN connection is
. When this feature is enabled, a slider
with two indicators will be shown. You can move the indicators to adjust each group's
weighting. The lower part of the table shows the corresponding reserved download
and uploads bandwidth value of each connection.
By default, for Guest.
of bandwidth has been reserved for Manager,
for Staff, and
You can define a maximum download speed (over all WAN connections) and upload speed (for each WAN connection) that each individual Staff and Guest member can consume. No limit can be imposed on individual Managers. By default, download and upload bandwidth limits are set to unlimited (set as ).
This section is to define the QoS Application Queue. You can set guaranteed bandwidth for a queue and assign it to applications.
Click the Add button to create the QoS Application Queue.
This setting specifies a name for the QoS Application Queue.
Bandwidth to be reserved (for each WAN connection) for this queue. When WAN is congested, this bandwidth will remain available for applications assigned to this queue.
Enable this option if you want this queue to utilize WAN's unused bandwidth.
manual/#4309)
(https://manual.peplink.com/peplink-b-one-series-user-
series-user-manual/#4308)
(https://manual.peplink.com/peplink-b-one-
manual/#4307)
(https://manual.peplink.com/peplink-b-one-series-user-
series-user-manual/#4306)
(https://manual.peplink.com/peplink-b-one-
On many Pepwave routers, you can choose whether to apply the same prioritization settings to all user groups or customize the settings for each group.
Three application priority levels can be set:
,
, and . Pepwave
routers can detect various application traffic types by inspecting the packet content.
Select an application by choosing a supported application, or by defining a custom
application manually. The priority preference of supported applications is placed at the
top of the table. Custom applications are at the bottom.
Click the
button to define a custom application. Click the button
in the
column to delete the custom application in the corresponding row.
When
is selected, the Pepwave router will inspect network
traffic and prioritize the selected applications. Alternatively, you can select
and define the application by providing the protocol, scope, port number,
and DSCP value.
DSL/cable-based WAN connections have lower upload bandwidth and higher
download bandwidth. When a DSL/cable circuit's uplink is congested,
the download bandwidth will be affected. Users will not be able to download data at
full speed until the uplink becomes less congested.
can
relieve such an issue. When it is enabled, the download speed will become less
affected by the upload traffic. By default, this feature is disabled.
To enable this option to allow SpeedFusion VPN traffic has highest priority when WAN is congested.
A firewall is a mechanism that selectively filters data traffic between the WAN side (the
Internet) and the LAN side of the network. It can protect the local network from potential hacker attacks, access to offensive websites, and/or other inappropriate uses. The firewall functionality of Pepwave routers supports the selective filtering of data traffic in both directions: Outbound (LAN to WAN) Inbound (WAN to LAN) Internal Network (VLAN to VLAN) Local Service
The firewall also supports the following functionality: Intrusion detection and DoS prevention Web blocking
With SpeedFusionTM enabled, the firewall rules also apply to VPN tunneled traffic.
The outbound firewall settings are located at
To enable or disable the Outbound Firewall to manage device local network traffic, click on the help icon and click here, the screen will show below.
To utilize the Outbound Firewall Rule to block the Peplink device from contacting InControl 2. may refer to the link below:
https://forum.peplink.com/t/faq-prevent-device-reachingincontrol-2./63f48fdfd466df34ab475f55/ (https://forum.peplink.com/t/faq-preventdevice-reaching-incontrol-2./63f48fdfd466df34ab475f55/)
Click
to display the following screen:
Inbound firewall settings are located at
Click
to display the following screen:
Internal Network firewall settings are located at
Click
to display the following window:
This setting specifies a name for the firewall rule.
This setting specifies whether the firewall rule should take effect. If the box is checked, the firewall rule takes effect. If the traffic matches the specified protocol/IP/port, actions will be taken by the Pepwave router based on the other parameters of the rule. If the box is not checked, the firewall rule does not take effect. The Pepwave router will disregard the other parameters of the rule.
Click the dropdown menu next to the checkbox to place this firewall rule on a time schedule.
Select the WAN connection that this firewall rule should apply to.
This setting specifies the protocol to be matched. Via a dropdown menu, the following protocols can be specified:
Alternatively, the
drop-down menu can
be used to automatically fill in the protocol and port number of
common Internet services (e.g., HTTP, HTTPS, etc.)
After selecting an item from the
drop-
down menu, the protocol and port number remains manually
modifiable.
This specifies the source IP address(es) and port number(s) to be
matched for the firewall rule. A single address, or a network, can
be specified as the
setting, as indicated by the
following screenshot:
In addition, a single port, or a range of ports, can be specified for
the
settings.
This specifies the destination IP address(es) and port number(s)
to be matched for the firewall rule. A single address, or a
network, can be specified as the
setting, as
indicated by the following screenshot:
In addition, a single port, or a range of ports, can be specified for
the
settings.
This setting specifies the action to be taken by the router upon encountering traffic that matches the both of the following:
Source IP & port Destination IP & port
With the value of
for the
setting, the matching
traffic passes through the router (to be routed to the destination).
If the value of the
setting is set to
, the matching
traffic does not pass through the router (and is discarded).
This setting specifies whether or not to log matched firewall events. The logged messages are shown on the page
. A sample message is as follows:
Aug 13 23:47:44 Denied CONN=Ethernet WAN SRC=20.3.2.1
DST=192.168.1.20 LEN=48 PROTO=TCP SPT=2260 DPT=80
The connection where the log entry refers to
Source IP address
Destination IP address
Packet length
Protocol
Source port
Destination port
Click
to store your changes. To create an additional firewall rule, click
and repeat the above steps.
To change a rule's priority, simply drag and drop the rule:
Hold the left mouse button on the rule. Move it to the desired position. Drop it by releasing the mouse button.
To remove a rule, click the
button.
Rules are matched from top to bottom. If a connection matches any one of the upper
rules, the matching process will stop. If none of the rules match, the
rule will
be applied. By default, the
rule is set as
for Outbound, Inbound and
Internal Network access.
If the default inbound rule is set to
for NAT-enabled WANs, no inbound Allow
firewall rules will be required for inbound port forwarding and inbound NAT
mapping rules. However, if the default inbound rule is set as
, a corresponding
Allow firewall rule will be required.
Pepwave routers can detect and prevent intrusions and denial-of-service (DoS) attacks
from the Internet. To turn on this feature, click
, check the
check box,
and press the
button.
When this feature is enabled, the Pepwave router will detect and prevent the following kinds of intrusions and denial-of-service attacks.
Port scan NMAP FIN/URG/PSH Xmas tree Another Xmas tree Null scan
SYN/RST SYN/FIN SYN flood prevention Ping flood attack prevention
For every WAN inbound traffic to local service, rules will be matched to take the defined action. The Local Service firewall settings are located at
.
Click
to display the following window:
This setting specifies a name for the firewall rule.
This setting specifies whether the firewall rule should take effect.
If the box is checked, the firewall rule takes effect. If the traffic matches the specified protocol/IP/port, actions will be taken by Peplink Balance based on the other parameters of the rule.
If the box is not checked, the firewall rule does not take effect. The Peplink Balance will disregard the other parameters of the rule.
Click the dropdown menu next to the checkbox to place this firewall rule on a time schedule.
This option allows you to define the supported local service to be matched.
If Any is chosen, the firewall rule will match to all supported local services from the list.
Via a drop-down menu, the following services can be specified:
Any SpeedFusion / PepVPN Handshake SpeedFusion / PepVPN Data Port Web Admin Access DNS Server SNMP Server KVM Management Port KVM VNC Port FusionSIM Agent / Remote SIM Proxy
Select the WAN connection that this firewall rule should apply to.
This specifies the source IP address and IP Network to be matched for the firewall rule.
With the value of
for the
setting, the matching traffic
passes through the router (to be routed to the destination). If the
value of the
setting is set to
, the matching traffic
does not pass through the router (and is discarded).
This setting specifies whether or not to log matched firewall events. The logged messages are shown on the page
. A sample message is as follows:
Aug 13 23:47:44 Denied CONN=Ethernet WAN SRC=20.3.2.1
DST=192.168.1.20 LEN=48 PROTO=TCP SPT=2260 DPT=80
The connection where the log entry refers to
Source IP address
Destination IP address
Packet length
Protocol
Source port
Destination port
Choose applications to be blocked from LAN/PPTP/SpeedFusion VPN peer clients' access, except for those on the Exempted User Groups or Exempted Subnets defined below.
Defines website domain names to be blocked from LAN/PPTP/SpeedFusion VPN peer clients' access except for those on the Exempted User Groups or Exempted Subnets defined below.
If "foobar.com" is entered, any web site with a host name ending in foobar.com will be blocked, e.g. www.foobar.com, foobar.com, etc. However, "myfoobar.com" will not be blocked.
You may enter the wild card ".*" at the end of a domain name to block any web site with a host name having the domain name in the middle. If you enter "foobar.*", then "www.foobar.com", "www.foobar.co.jp", or "foobar.co.uk" will be blocked. Placing the wild card in any other position is not supported.
The device will inspect and look for blocked domain names on all HTTP and HTTPS traffic.
Enter an appropriate website address, and the Pepwave MAX will block and disallow LAN/PPTP/SpeedFusionTM peer clients to access these websites. Exceptions can be added using the instructions in Sections 20.1.3.2 and 20.1.3.3.
You may enter the wild card ".*" at the end of a domain name to block any web site with a host name having the domain name in the middle. For example, If you enter "foobar.*," then "www.foobar.com," "www.foobar.co.jp," or "foobar.co.uk" will be blocked. Placing the wild card in any other position is not supported.
The Pepwave MAX will inspect and look for blocked domain names on all HTTP traffic. Secure web (HTTPS) traffic is not supported.
Check and select pre-defined user group(s) who can be exempted from the access
blocking rules. User groups can be defined at
section. Please refer
to
(https://docs.google.com/document/
d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/edit#bookmark=id.16x20ju)
for details.
With the subnet defined in the field, clients on the particular subnet(s) can be exempted from the access blocking rules.
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4299) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4298)
The Pepwave supports OSPF and RIPv2 dynamic routing protocols.
Click the
tab from the top bar, and then click the
item on the sidebar to reach the following menu:
This field determines the ID of the router. By default, this is specified as the WAN IP address. If you want to specify your own ID, enter it into the
field.
This is an overview of the OSPF areas that you have defined. Clicking on
the name under Area allows you to configure the connection. To define
a new area, click . To delete an existing area, click on the
.
Assign a name to be applied to this group. Machines linked to this group will send and receive related OSPF packets, while unlinked machines will ignore them.
Choose the type of network that this area will use.
If an authentication method is used, select one from this drop-
down menu. Available options are
and
. Authentication
key(s) may be input next to the drop-down menu after selecting
an authentication method.
Select the interface(s) that this area will use to listen to and deliver OSPF packets.
To access RIPv2 settings, click on
.
If an authentication method is used, select one from this drop-
down menu. Available options are
and
. Authentication
key(s) may be input next to the drop-down menu after selecting
an authentication method.
Select the interface(s) that this area will use to listen to and deliver RIPv2 packets.
Isolate SpeedFusion VPN peers from each other. Received SpeedFusion VPN routes will not be forwarded to other SpeedFusion VPN peers to reduce bandwidth consumption..
Networks to be advertised over OSPF & RIPv2. If no network is selected, all LAN / VLAN networks will be advertised by default.
Enabling OSPF & RIPv2 Route Advertising allows it to advertise LAN static routes over OSPF & RIPv2. Static routes on the Excluded Networks table will not be advertised.
Click the
tab along the top bar, and then click the
to configure BGP.
item on the sidebar
Click the " " to delete a BGP profile. Click " " to create a new BGP profile.
This field specifies the name that represents this profile. When this box is checked, this BGP profile will be enabled. If it is left unchecked, it will be disabled. The interface in which the BGP neighbor is located. This field specifies the unique IP as the identifier of the local device running BGP. The Autonomous System Number (ASN) assigned to this profile.
BGP Neighbors and their details. The IP address of the Neighbor.
The Neighbor's ASN.
This field determines the Time-to-live (TTL) of BGP packets. Leave this field blank if the BGP neighbor is directly connected, otherwise you must specify a TTL value. This option should be used if the configured Neighbor's IP address does not match the selected Interface's network subnets. The TTL value must be between 2 to 255.
(Optional) Assign a password for MD5 authentication of BGP sessions.
AS path to be prepended to the routes received from this Neighbor. Values must be ASN and separated by commas. For example: inputting "64530,64531" will prepend "64530, 64531" to received routes.
Wait time in seconds for a keepalive message from a Neighbor before considering the BGP connection as stalled.
The value must be either 0 (infinite hold time) or between 3 and 65535 inclusively.
Default: 240
Enable this option to advertise your own source address as the next hop when propagating routes.
This is the metric advertised to iBGP Neighbors to indicate the preference for external routes. The value must be between 0 to 4294967295 inclusively.
Default: 100
Enable this option to add Bidirectional Forwarding Detection for path failure. All directly connected Neighbors that use the same physical interface share the same BFD settings. All mulithop Neighbors share the same multihop BFD settings. You can configure BFD settings in the BGP profile listing page after this option is enabled.
Select the Networks that will be advertised to the BGP Neighbor. Enable this option to advertise static LAN routes. Static routes that match the Excluded Networks table will not be advertised. Additional routes to be advertised to the BGP Neighbor.
When this box is checked, every learnt OSPF route will be advertised. Assign a prefix to a Community. Community: Two numbers in new-format. e.g. 65000:21344 Well-known communities: no-export 65535:65281 no-advertise 65535:65282 no-export-subconfed 65535:65283 no-peer 65535:65284 Route Prefix: Comma separated networks. e.g. 172.168.1.0/24,192.168.1.0/28
This field allows for the selection of the filter mode for route import.
: All BGP routes will be accepted.
: Routes in "Restricted Networks" will be accepted, routes not in the list will be rejected.
: Routes in "Blocked Networks" will be rejected, routes not in the list will be accepted.
This field specifies the network(s) in the "route import" entry.
When this box is checked, only routes with the same Network and Subnet Mask will be filtered. Otherwise, routes within the Networks and Subnets will be filtered.
This field allows for the selection of the filter mode for route export.
: All BGP routes will be accepted. : Routes in "Restricted Networks" will be
accepted, routes not in the list will be rejected. : Routes in "Blocked Networks" will be rejected,
routes not in the list will be accepted.
This field specifies the network(s) in the "route export" entry.
When this box is checked, only routes with the same Network and Subnet Mask will be filtered. Otherwise, routes within the Networks and Subnets will be filtered.
When this box is checked, routes learnt from this BGP profile will be exported to other BGP profiles.
When this box is checked, routes learnt from this BGP profile will be exported to the OSPF routing protocol.
A remote-access VPN connection allows an individual user to connect to a private business network from a remote location using a laptop or desktop computer connected to the Internet. Networks routed by a Pepwave router can be remotely accessed via OpenVPN, L2TP with IPsec or PPTP. To configure this feature, navigate to
and choose the required VPN type.
When this box is checked, this Remote User Access profile will be enabled. If it is left unchecked, it will be disabled.
This field allows you to select the VPN type for the remote user access connection. The available options are:
L2TP with IPsec
If L2TP with IPsec is selected, it may need to enter the preshared key for the remote user access. PPTP
If PPTP selected, there is no additional configuration required. The Point-to-Point Tunneling Protocol (PPTP) is an obsolete method for implementing virtual private networks. PPTP has many well known security issues OpenVPN
If the OpenVPN is selected, the OpenVPN Client profile can
be downloaded from the
page after the
configuration has been saved.
You have a choice between 2 different OpenVPN Client profiles:
Using this profile, VPN clients will send all the traffic through the OpenVPN tunnel
Using this profile, VPN clients will ONLY send those traffic designated to the untagged LAN and VLAN segment through the OpenVPN tunnel.
If
is selected in the VPN Type, enter the pre
shared key in the text field. Please note that remote devices
will need this preshared key to access the Balance.
You may click the
button to show in the Pre-shared key
and enable this option.
When checked, weak ciphers such as 3DES will be disabled.
Please note: Legacy and Android devices may not able to connect.
If
is selected in the VPN Type, this settings is for
specifying the interval for refreshing the connection.
This setting is for specifying the WAN IP addresses that allow remote user access.
If
is selected in the VPN Type, the
setting
specifies the port(s) that correspond to the service.
Determine the method of authenticating remote users:
This setting allows you to define the Remote User Accounts.
Click
to input username and password to create
an account. After adding the user accounts, you can click on
a username to edit the account password.
The username must contain lowercase letters, numerics, underscore(_), dash(-), at sign(@), and period(.) only. The password must be between 8 and 12 characters long
Enter the matching LDAP server details to allow for LDAP server authentication.
Enter the matching Radius server details to allow for Radius server authentication.
Enter the matching Active Directory details to allow for Active Directory server authentication.
The miscellaneous settings include configuration for High Availability, Certificate Manager, service forwarding, service passthrough, GPS forwarding, GPIO, Groupe Networks and SIM Toolkit (depending the feature is supported on the model of Peplink router that is being used).
Many Pepwave routers support high availability (HA) configurations via an open standard virtual router redundancy protocol (VRRP, RFC 3768). In an HA configuration, two Pepwave routers provide redundancy and failover in a master-slave arrangement. In the event that the master unit is down, the slave unit becomes active. High availability will be disabled automatically where there is a drop-in connection configured on a LAN bypass port.
In the diagram, the WAN ports of each Pepwave router connect to the router and to the modem. Both Pepwave routers connect to the same LAN switch via a LAN port.
An elaboration on the technical details of the implementation of the virtual router redundancy protocol (VRRP, RFC 3768) by Pepwave routers follows:
In an HA configuration, the two Pepwave routers communicate with each other using VRRP over the LAN.
The two Pepwave routers broadcast heartbeat signals to the LAN at a frequency of one heartbeat signal per second.
In the event that no heartbeat signal from the master Pepwave router is received in 3 seconds (or longer) since the last heartbeat signal, the slave Pepwave router becomes active.
The slave Pepwave router initiates the WAN connections and binds to a previously configured LAN IP address.
At a subsequent point when the master Pepwave router recovers, it will once again become active.
You can configure high availability at
.
Checking this box specifies that the Pepwave router is part of a high availability configuration.
This number identifies a pair of Pepwave routers operating in
a high availability configuration. The two Pepwave routers in
the pair must have the same
value.
This setting specifies whether the Pepwave router operates in master or slave mode. Click the corresponding radio button to set the role of the unit. One of the units in the pair must be configured as the master, and the other unit must be configured as the slave.
This option is displayed when
mode is selected in
. If this option is enabled, once the device has
recovered from an outage, it will take over and resume its
role from the slave unit.
This option is displayed when
mode is selected in
. If this option is enabled and the
entered matches with the actual master
unit's, the master unit will automatically transfer the
configuration to this unit. Please make sure the
and the
fields are set correctly in
the LAN settings page. You can refer to the
for the
configuration synchronization status.
If
is checked, the serial number of the
master unit is required here for the feature to work properly.
The HA pair must share the same
. The
and the
must be under the same
network.
This setting specifies a LAN IP address to be used for accessing administration functionality. This address should be unique within the LAN.
This setting specifies the subnet mask of the LAN.
For Pepwave routers in NAT mode, the virtual IP (VIP) should be set as the default gateway for all hosts on the LAN segment. For example, a firewall sitting behind the Pepwave router should set its default gateway as the virtual IP instead of the IP of the master router.
In drop-in mode, no other configuration needs to be set.
Please note that the drop-in WAN cannot be configured as a LAN bypass port while it is configured for high availability.
RADIUS Server settings are located at
.
To configure the Authentication Server and Accounting Server, click
to
display the following screen:
This field is for specifying a name to represent this profile. Specifies the IP address or hostname of the RADIUS server host. This setting specifies the UDP destination port for authentication requests. By default, the port number is 1812. This field is for entering the secret key for communicating to the RADIUS server.
This field is for specifying a name to represent this profile. Specifies the IP address or hostname of the RADIUS server host. This setting specifies the UDP destination port for accounting requests. By default, the port number is 1813.
This field is for entering the secret key for communicating to the RADIUS server.
This section allows for certificates to be assigned to the local VPN, Web Admin SSL, Captive Portal SSL, OpenVPN CA, Wi-Fi WAN Client certificate and Wi-Fi WAN CA Certificate. The following knowledge base article describes how to create self-signed certificates and import it to a Peplink Product. https://forum.peplink.com/t/how-to-create-a-self-signed-certificate-and-import-it-to-apeplink-product/ (https://forum.peplink.com/t/how-to-create-a-self-signed-certificateand-import-it-to-a-peplink-product/)
Service forwarding settings are located at .
When this option is enabled, all outgoing SMTP connections
destined for any host at TCP port 25 will be intercepted. These
connections will be redirected to a specified SMTP server and port
number. SMTP server settings for each WAN can be specified after
selecting
.
When this option is enabled, all outgoing connections destined for
the proxy server specified in
will be intercepted. These connections will be redirected to a
specified web proxy server and port number. Web proxy
interception settings and proxy server settings for each WAN can
be specified after selecting
.
When this option is enabled, all outgoing DNS lookups will be intercepted and redirected to the built-in DNS name server. If any LAN device is using the DNS name servers of a WAN connection, you may want to enable this option to enhance the DNS availability without modifying the DNS server setting of the clients. The built-in DNS name server will distribute DNS lookups to corresponding DNS servers of all available WAN connections. In this case, DNS service will not be interrupted, even if any WAN connection is down.
When custom service forwarding is enabled, outgoing traffic with the specified TCP port will be forwarded to a local or remote server by defining its IP address and port number.
Some ISPs require their users to send e-mails via the ISP's SMTP server. All outgoing SMTP connections are blocked except those connecting to the ISP's. Pepwave routers support intercepting and redirecting all outgoing SMTP connections (destined for TCP port 25) via a WAN connection to the WAN's corresponding SMTP server.
To enable the feature, select
under
. Check
for the WAN connection(s) that needs forwarding. Under
,
enter the ISP's e-mail server host name or IP address. Under
, enter the TCP
port number for each WAN.
The Pepwave router will intercept SMTP connections. Choose a WAN port according to the outbound policy, and then forward the connection to the SMTP server if the chosen WAN has enabled forwarding. If the forwarding is disabled for a WAN connection, SMTP connections for the WAN will be simply be forwarded to the connection's original destination.
If you want to route all SMTP connections only to particular WAN connection(s), you
should create a custom rule in outbound policy (see
).
When this feature is enabled, the Pepwave router will intercept all outgoing connections destined for the proxy server specified in
, choose a WAN connection with reference to the outbound policy, and then forward them to the specified web proxy server and port number. Redirected server settings for each WAN can be set here. If forwarding is disabled for a WAN, web proxy connections for the WAN will be simply forwarded to the connection's original destination.
When DNS forwarding is enabled, all clients' outgoing DNS requests will also be intercepted and forwarded to the built-in DNS proxy server.
After clicking the
checkbox, enter your TCP port for traffic heading to the
router, and then specify the IP Address and Port of the server you wish to forward to the service to.
Service passthrough settings can be found at .
Some Internet services need to be specially handled in a multi-WAN environment. Pepwave routers can handle these services such that Internet applications do not notice being behind a multi-WAN router. Settings for service passthrough support are available here.
Session initiation protocol, aka SIP, is a voice-over-IP protocol. The
Pepwave router can act as a SIP application layer gateway (ALG) which
binds connections for the same SIP session to the same WAN connection
and translate IP address in the SIP packets correctly in NAT mode. Such
passthrough support is always enabled, and there are two modes for
selection:
and
. If your SIP server's
signal port number is non-standard, you can check the box
and input the port numbers to the text boxes.
With this option enabled, protocols that provide audio-visual communication sessions will be defined on any packet network and pass through the Pepwave router.
FTP sessions consist of two TCP connections; one for control and one for
data. In a multi-WAN situation, they must be routed to the same WAN
connection. Otherwise, problems will arise in transferring files. By default,
the Pepwave router monitors TCP control connections on port 21 for any
FTP connections and binds TCP connections of the same FTP session to
the same WAN. If you have an FTP server listening on a port number
other than 21, you can check
and enter the
port numbers in the text boxes.
The Pepwave router monitors outgoing TFTP connections and routes any
incoming TFTP data packets back to the client. Select
if you want
to enable TFTP passthrough support.
This field is for enabling the support of IPsec NAT-T passthrough. UDP
ports 500, 4500, and 10000 are monitored by default. You may add more
custom data ports that your IPsec system uses by checking
. If the VPN contains IPsec site-to-site VPN traffic,
check
and choose the WAN connection to
route the traffic to.
Ignition Sensing detects the ignition signal status of a vehicle it is installed in.
This feature allows the cellular router to start up or shut down when the engine of that vehicle is started or turned off. The time delay setting between ignition off and power down of the router is a configurable setting, which allows the router to stay on for a period of time after the engine of a vehicle is turned off.
Digital Input / Digital Output / Analog Input
Digital Input / Ignition Sensing
connected to permanent negative feed (ground)
connected to permanent positive feed (power)
Brown Orange Black Red
Ignition Sensing options can be found in The configurable option for Ignition Input is stays powered on after the ignition is turned off.
the time in seconds that the router
a.) Ignition sensing: 9-30V active high for IGN purpose b.) Input Sensing: I/O input
The O/P (connected to the I/O pin on a 4 pin connector) can be configured as a digital input, a digital output, or an analog input.
Digital Input the connection supports input sensing; it reads the external input and determines if the settings should be `High' (on) or `Low' (off).
Digital Output when there is a healthy WAN connection, the output pin is marked as `High' (on). Otherwise, it will be marked as `Low' (off). a.) Digital output: Open drain for IO output. It is required to add an external pull up resistor of 10K for 3.3-30V pull up voltage. (DO NOT exceed 250mA) 3.3-30V active high, 0.05-0.5V active low(mapping to 3.3-30V pull up voltage) b.) Digital input: I/O input
.
Analog Input to be confirmed. In most cases, it should read the external input and determine the voltage level.
Pepwave routers can now serve as a local NTP server. Upon start up, it is now able to provide connected devices with the accurate time, precise UTC from either an external NTP server or via GPS and ensuring that connected devices always receive the correct time. Compatible with: BR1 ENT, BR1 Pro CAT-20/5G, 700 HW3, HD2/4, Transit
NTP Server setting can be found via:
Time Settings can be found at
format.
allows to configure destination networks in grouped
Select Add group to create a new group with single IPaddresses or subnets from different VLANs.
The created network groups can be used in outbound policies, firewall rules.
The SIM Toolkit, accessible via
, supports two
functionalities, USSD and SMS.
Unstructured Supplementary Service Data (USSD) is a protocol used by mobile phones to communicate with their service provider's computers. One of the most common uses is to query the available balance.
Enter your USSD code under the
text field and click
.
You will receive a confirmation. To check the SMS response, click .
After a few minutes you will receive a response to your USSD code
The SMS option allows you to read SMS (text) messages that have been sent to the SIM in your Pepwave router.
You may define the UDP relay by clicking the
.
You can click
to enable the UDP relay to relay UDP Broadcast or Multicast traffic
for LAN/VLAN/SpeedFusion VPN.
Click "New UDP Relay Rule" to define the relay rule.
This field is for specifying a name to represent this profile.
This feid is to enter the specific port number for the UDP relay
If Multicast is not selected, it will broadcast relay rule. If Multicast is selected, you may need to enter a valid multicast address.
Select the specific connection as a source network to where the device is to relay UDP Broadcast packets.
You may select the specific connection from the drop-down list or may custom combination network as a destination network that receives the UDP packet relays.
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4277) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4276) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4275) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4274)
The AP controller acts as a centralized controller of Pepwave Access Points. With this feature, users can customize and manage up to 1500 Access Points from a single Pepwave router interface. To configure, navigate to the tab. and the following screen appears.
The AP controller for managing Pepwave APs can be enabled by
checking this box. When this option is enabled, the AP controller
will wait for management connections originating from APs over
the LAN on TCP and UDP port 11753. It will also wait for captive
portal connections on TCP port 443. An extended DHCP option,
(field 138), will be added
to the DHCP server. A local DNS record,
, will be
added to the local DNS proxy.
As soon as possible Progressively One at a time
Access points to manage can be specified here. If
is selected,
the AP controller will manage any AP that reports to it. If
is selected, only APs with serial numbers listed in
the provided text box will be managed.
Current SSID information appears in the
section. To edit an existing SSID, click its
name in the list. To add a new SSID, click . Note that the following settings vary by
model.
The below settings ishows a new SSID window with Advanced Settings enabled (these
are available by selecting the question mark in the top right corner).
This setting specifies the SSID of the virtual AP to be scanned by Wi-Fi clients.
Click the drop-down menu to apply a time schedule to this interface
This setting specifies the VLAN ID to be tagged on all outgoing packets generated from this wireless network (i.e., packets that travel from the Wi-Fi segment through the Pepwave AP One unit to the Ethernet segment via the LAN port). The default value of this setting is , which means VLAN tagging is disabled (instead of tagged with zero).
This setting specifies whether or not Wi-Fi clients can scan the
SSID of this wireless network.
is enabled by
default.
Select
to allow the Pepwave router to set the data rate
automatically, or select
and choose a rate from the
displayed drop-down menu.
This setting enables the filtering of multicast network traffic to the wireless SSID.
This setting specifies the transmit rate to be used for sending
multicast network traffic. The selected
and
settings will affect the rate options and values available
here.
To allow the Pepwave router to listen to internet group management protocol (IGMP) network traffic, select this option.
If you use a distributed DHCP server/relay environment, you can enable this option to provide additional information on the manner in which clients are physically connected to the network.
refers to the second layer in the ISO Open System Interconnect model.
When this option is enabled, clients on the same VLAN, SSID, or subnet are isolated to that VLAN, SSID, or subnet, which can enhance security. Traffic is passed to the upper communication layer(s). By default, the setting is disabled.
Indicate the maximum number of clients that should be able to connect to each frequency.
A Advanced feature. Click the
button on the top right-hand corner to activate.
This setting configures the wireless authentication and encryption methods. Available options :
No Encryption)
(OWE)
(AES:CCMP)
(AES:CCMP)
(AES:CCMP)
(TKIP/AES: CCMP)
When
is configured, RADIUS-based 802.1 x
authentication is enabled. Under this configuration, the
option should be disabled. When using this method, select the
appropriate version using the / controls. The security level of this
method is known to be very high.
When
is configured, a shared key is used for
data encryption and authentication. When using this configuration,
the
option should be enabled. Key length must be
between eight and 63 characters (inclusive). The security level of this
method is known to be high.
When
is configured, if a managed AP which is
NOT WPA3 PSK capable, the AP Controller will not push those WPA3
and WPA2/WPA3 SSID to that AP.
The settings allow the administrator to control access using MAC
address filtering. Available options are
,
,
and
Connection coming from the MAC addresses in this list will be either denied or accepted based on the option selected in the previous field.
If more than one MAC address needs to be entered, you can use a carriage return to separate them.
This field is for specifying the IP address of the primary RADIUS server for Authentication and, if applicable, the secondary RADIUS server.
In the field, the UDP authentication port(s) used by your
RADIUS server(s) or click the
is
.
This settings is enter the RADIUS shared secret for the primary server and, if applicable, the secondary RADIUS server.
This field is for specifying the IP address of the primary RADIUS server for Accounting and, if applicable, the secondary RADIUS server.
In the field, enter the UDP accounting port(s) used by your
RADIUS server(s) or click the
is
.
This settings is enter the RADIUS shared secret for the primary server and, if applicable, the secondary RADIUS server.
Choose between
,
,
and
Check this box to deny all connection attempts by private IP addresses. To create a custom subnet for guest access, enter the IP address and choose a subnet mask from the drop-down menu. To block access from a particular subnet, enter the IP address and choose a subnet mask from the drop-down menu.
The settings allow administrators to control access to the SSID based on Firewall Rules. Available options are and
Create Firewall Rules based on or
Wireless Mesh Support is available on devices running 802.11ac (Wi-Fi 5) and above. Along with the AP Controller, mesh network extensions can be established, which can expand network coverage. Note that the Wireless Mesh settings need to match the Mesh ID and Shared Key of the other devices on the same selected frequency band.
To create a new Wireless Mesh profile, go to >
, and click .
Enter a name to represent the Mesh profile.
Select the 2.4GHz or 5GHz frequency to be used.
Enter the shared key in the text field. Please note that it needs to match the shared keys of the other APs in the Wireless Mesh settings.
Click
to toggle visibility.
To configure the AP settings, navigating to
:
These buttons specify which wireless networks will use this AP profile. You can also select the frequencies at which each network will transmit. Please note that the Pepwave MAX does not detect whether the AP is capable of transmitting at both frequencies. Instructions to transmit at unsupported frequencies will be ignored by the AP.
This drop-down menu specifies the national / regional regulations which the AP should follow.
If a North American region is selected, RF channels 1 to 11 will be available and the maximum transmission power will be 26 dBm (400 mW).
If European region is selected, RF channels 1 to 13 will be available. The maximum transmission power will be 20 dBm (100 mW).
Note: Users are required to choose an option suitable to local laws and regulations.
Per FCC regulation, the country selection is not available on all models marketed in the US. All US models are fixed to US channels only.
These buttons determine the frequency at which access points will attempt to broadcast. This feature will only work for APs that can transmit at both 5.4GHz and 5GHz frequencies.
This option allows you to specify whether 802.11b and/or
802.11g client association requests will be accepted. Available
options are
and
. By default,
is
selected.
There are three options: 20 MHz, 20/40 MHz, and 40 MHz. With this feature enabled, the Wi-Fi system can use two channels at once. Using two channels improves the performance of the Wi-Fi connection.
This drop-down menu selects the 802.11 channel to be
utilized. Available options are from 1 to 11 and from 1 to 13
for the North America region and Europe region, respectively.
(Channel 14 is only available when the country is selected as
Japan with protocol 802.11b.) If
is set, the system will
perform channel scanning based on the scheduled time set
and choose the most suitable channel automatically.
Indicate the time of day at which update automatic channel selection.
This drop-down menu determines the power at which the AP
under this profile will broadcast. When fixed settings are
selected, the AP will broadcast at the specified power level,
regardless of context. When
settings are selected,
the AP will adjust its power level based on its surrounding APs
in order to maximize performance.
The
setting will set the AP to do this
automatically. Otherwise, the
setting will
set the AP to dynamically adjust only if instructed to do so. If
you have set
, you can go to
to give your AP further
instructions.
If you click the
checkbox, the AP under this profile will
transmit using additional power. Please note that using this
option with several APs in close proximity will lead to
increased interference.
This field determines that maximum signal strength each individual client will receive. The measurement unit is megawatts.
This field determines the maximum clients that can be connected to APs under this profile.
This field specifies the VLAN ID to tag to management traffic, such as AP to AP controller communication traffic. The value is
by default, meaning that no VLAN tagging will be applied.
Note: change this value with caution as alterations may result in loss of connection to the AP controller.
This option is to turn on and off to scan the nearby the AP.
: Feature will be automatically turned on with Auto Channel / Dynamic Output Power
This drop-down menu provides the option to send beacons in
different transmit bit rates. The bit rates are
,
,
,
, and
.
This drop-down menu provides the option to set the time
between each beacon send. Available options are
,
, and
.
This field provides the option to set the frequency for beacon to include delivery traffic indication message (DTIM). The interval unit is measured in milliseconds.
This field provides the option to set the minimum packet size for the unit to send an RTS using the RTS/CTS handshake. Setting disables this feature.
Determines the maximum size (in bytes) that each packet fragment will be broken down into. Set 0 to disable fragmentation.
Select the distance you want your Wi-Fi to cover in order to adjust the below parameters. Default values are recommended.
This field provides the option to modify the unit wait time before it transmits. The default value is .
This field provides the option to set the wait time to receive
acknowledgement packet before doing retransmission. The
default value is
.
A Advanced feature. Click the
button on the top right-hand corner to activate.
Per FCC regulation, the country selection is not available on all models marketed in the US. All US models are fixed to US channels only.
The device with integrated AP can operate under the Wi-Fi Operating Mode, and the
default setting is
mode:
.
In this mode, all Wi-Fi will operate as Wi-Fi WAN and no integrated Wi-Fi AP will be operated on this device.
If Wi-Fi Operating mode is choosing front panel LED is as follows:
, The status indicated by the
Wi-Fi 1 is Green if Wi-Fi WAN 1 is enabled. Wi-Fi 2 is Green if Wi-Fi WAN 2 is enabled.
In this mode, some Wi-Fi will operate as Wi-Fi WAN. Some other Wi-Fi WANs will be forced offline and their Wi-Fi resources will be reserved for integrated Wi-Fi AP operations.
If Wi-Fi Operating mode is choosing the front panel LED is as follows:
, The status indicated by
Wi-Fi 1 is Green if WI-FI WAN is enabled. Wi-Fi 2 is Green if Wi-Fi AP is ON.
In this mode, all Wi-Fi functions as integrated Wi-Fi AP. All Wi-Fi WANs will be forced to go offline.
If Wi-Fi Operating mode is choosing panel LED is as follows:
, The status indicated by the front
W-Fi 1 is Green, if there is any Wireless SSID is selected 2.4GHz. W-Fi 2 is Green, if there is any Wireless SSID is selected 5GHz.
Check the box to allow the Pepwave router to manage the web admin access information of the AP.
These buttons specify the web access protocol used for
accessing the web admin of the AP. The two available options
are
and
.
This field specifies the management port used for accessing the device.
This option will be available if you have chosen
as the
. With this enabled, any HTTP access to
the web admin will redirect to HTTPS automatically.
This field specifies the administrator username of the web admin. It is set as admin by default.
This field allows you to specify a new administrator password.
You may also click the
button and let the system
generate a random password automatically.
This allows users to configure AP Time Settings (both Timezone and NTP) in AP Controller.
This field is to select the time zone for the AP controller. This field is to select the time server for the AP controller.
This settings is to allow user to manage external AP's controller unreachable action.
When
is checked, there will have 2 options which are
"
" and "
".
This is an option to enable client load balancing for AP Controller. When the option is enabled, it is trying to balance the station count on APs within the same profile.
Some Pepwave models displays a screen similar to the one shown below, navigating to :
This option sets the country whose regulations the Pepwave router follows. Wi-Fi Antenna Choose from the router's internal or optional external antennas, if so equipped.
This option allows you to specify whether 802.11b and/or
802.11g client association requests will be accepted. Available
options are
and
. By default, 802.11ng is
selected.
This option allows you to select which 802.11 RF channel will be
used.
is selected by default.
is simultaneously.
and
z are available. The default setting
, which allows both widths to be used
This option is for specifying the transmission output power for
the Wi-Fi AP. There are 4 relative power levels available
,
, , and . The actual output power will be bound by
the regulatory limits of the selected country.
This option is for setting the transmit bit rate for sending a
beacon. By default,
is selected.
This option is for setting the time interval between each beacon.
By default,
is selected.
This field allows you to set the frequency for the beacon to
include a delivery traffic indication message. The interval is
measured in milliseconds. The default value is set to
.
This field is for specifying the wait time before the Router transmits a packet. By default, this field is set to .
This field is for setting the wait time to receive an
acknowledgement packet before performing a retransmission.
By default, this field is set to
.
This option allows you to enable frame aggregation to increase transmission throughput.
This setting allows choosing a short or long guard period interval for your transmissions.
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4272) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4271) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4270)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4268) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4269)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4267) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4266)
A comprehensive overview of your AP can be accessed by navigating to .
This field displays the maximum number of AP your Balance router can control. You can purchase licenses to increase the number of AP you can manage.
Underneath, there are two check boxes labeled
and
.
Clicking either box will toggle the display of information for that
frequency. By default, the graphs display the number of clients and
data usage for both 2.4GHz and 5 GHz frequencies.
The colored boxes indicate the SSID to display information for. Clicking any colored box will toggle the display of information for that SSID. By default, all the graphs show information for all SSIDs.
This pie chart and table indicates how many APs are online and how many are offline.
This graph displays the number of clients connected to each network at any given time. Mouse over any line on the graph to see how many clients connected to a specific SSID for that point in time.
This graph enables you to see the data usage of any SSID for any given time period. Mouse over any line on the graph to see the data usage by each SSID for that point in time. Use the buttons next to
to select the time scale you wish to view. In addition, you could use the sliders at the bottom to further refine your timescale.
0
This event log displays all activity on your AP network, down to the client level. Click
to see only alerts, and click the
link for additional records.
This allow user to configure AP Time Settings (both Timezone and NTP) in AP Controller.
Ths field is to select the time zone for the AP controller. Ths field is to select the time server for the AP controller.
This settings is to allow user to manage external AP's controller unreachable action.
When
is checked, there will have 2 options which are
"
" and "
".
This is an option to enable client load balancing for AP Controller. When the option is enabled, it is trying to balance the station count on APs within the same profile.
A detailed breakdown of data usage for each AP is available at .
This table shows the detailed information on each AP, including channel, number of clients, upload traffic, and download traffic. Click the blue arrows at the left of the table to expand and collapse information on each device group.
On the right of the table, you will see the following icons:
.
Click the
icon to see a usage table for each client:
Click the
icon to configure each client
For easier network management, you can give each client a name and designate its location. You can also designate which firmware pack (if any) this client will follow, as well as the channels on which the client will broadcast.
Click the
icon to see a graph displaying usage:
Click any point in the graphs to display detailed usage and client
information for that device, using that SSID, at that point in time. On
the
menu, you can display the information by SSID or
by AP send/receive rate.
Click the
tab next to
log for that particular device:
to view a detailed event
In-depth SSID reports are available under
.
Click the blue arrow on any SSID to obtain more detailed usage information on each SSID.
You can search for specific Wi-Fi users by navigating to .
Here, you will be able to see your network's heaviest users as well as search for specific
users. Click the
icon to bookmark specific users, and click the
icon for
additional details about each user:
Mesh / WDS allows you to monitor the status of your wireless distribution system (WDS) or Mesh, and track activity by MAC address by navigating to
. This table shows the detailed information of each AP, including protocol, transmit rate (sent / received), signal strength, and duration.
A listing of near devices can be accessed by navigating to .
Hovering over the device MAC address will result in a popup with information on
how this device was detected. Click the
icons and the device will be moved
to the bottom table of identified devices.
You can access the AP Controller Event log by navigating to .
This event log displays all activity on your AP network, down to the client level. Use
to filter box to search by MAC address, SSID, AP Serial Number, or AP Profile name.
Click
to see only alerts, and click the
link for additional records.
Tools for managing firmware packs can be found at
.
Here, you can manage the firmware of your AP. Clicking on
will result in
information regarding each firmware pack. To receive new firmware packs, you can
click
to download new packs, or you can click
to manually upload a firmware pack. Click
to define which firmware pack is
default.
#4263)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4262)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4261)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4260)
#4259)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4258)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4257)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4256)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4255)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4254)
#4253)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4252)
There are two types of user accounts available for accessing the web admin: admin and user. They represent two user levels: the admin level has full administrative access, while the user level is read-only. The user level can access only the device's status information; users cannot make any changes on the device.
A web login session will be logged out automatically when it has been idle longer than
the
. Before the session expires, you may click the
button in the web admin to exit the session.
signifies an unlimited session time. This setting should be used
only in special situations, as it will lower the system security level if users do not log
out before closing the browser. The
is 4 hours, 0 minutes.
For security reasons, after logging in to the web admin Interface for the first time, it is
recommended to change the administrator password. Configuring the administration
interface to be accessible only from the LAN can further improve system security.
Administrative settings configuration is located at
.
This field allows you to define a name for this Pepwave router.
By default,
is set as
, where XXXX
refers to the last 4 digits of the unit's serial number.
is set as admin by default, but can be changed, if desired.
This field allows you to specify a new administrator password.
This field allows you to verify and confirm the new administrator password.
changed, if desired.
is set as user by default, but can be
This field allows you to specify a new user password. Once the user password is set, the read-only user feature will be enabled.
This field allows you to verify and confirm the new user password.
This field specifies the number of hours and minutes that a web session can remain idle before the Pepwave router terminates its access to the web admin interface. By default, it is set to
.
With this box is checked, the web admin will authenticate using an external RADIUS server. Authenticated users are treated as either "admin" with full read-write permission or "user" with read-only access. Local admin and user accounts will be disabled. When the device is not able to communicate with the external RADIUS server, local accounts will be enabled again for emergency access. Additional authentication options will be available once this box is checked. Available options:
Local Account RADIUS
This specifies the authentication protocol used. Available options are
and . This specifies the IP address or hostname of the RADIUS server host. This setting specifies the UDP destination port for authentication requests. This field is for entering the secret key for accessing the RADIUS server. This specifies the IP address or hostname of the RADIUS server host. This setting specifies the UDP destination port for accounting requests.
TACACS+
This field is for entering the secret key for accessing the accounting server.
This option specifies the time value for authentication timeout
This specifies the access address of the external TACACS+ server.
This field is for entering the secret key for accessing the RADIUS server.
This option specifies the time value for TACACS+ timeout
The CLI (command line interface) can be accessed via SSH. This
field enables CLI support. For additional information regarding
CLI, please refer to
(https://docs.google.com/
document/
d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/
edit#heading=h.393x0lu)
This menu allows you to choose between granting access to LAN and WAN clients, or to LAN clients only.
This field determines the port on which clients can access CLI SSH.
This field is for entering the Public Key for Admin Users and Read-only Users to access CLI SSH.
This option is for specifying the protocol(s) through which the web admin interface can be accessed:
HTTP HTTPS HTTP/HTTPS
HTTP to HTTPS redirection is enabled by default to force HTTPS access to the web admin interface.
This option is for specifying the network interfaces through which the web admin interface can be accessed:
LAN only LAN/WAN
If LAN/WAN is chosen, the form will be displayed.
This field is for specifying the port number on which the web admin interface can be accessed.
This field allows you to restrict web admin access only from defined IP subnets.
Allow web admin accesses to be from anywhere,
without IP address restriction.
Restrict
web admin access only from the defined IP subnets. When
this is chosen, a text input area will be displayed beneath:
The allowed IP subnet addresses should be entered into this text area. Each IP subnet must be in form of w.x.y.z/m, where w.x.y.z is an IP address (e.g., 192.168.0.0), and m is the subnet mask in CIDR format, which is between 0 and 32 inclusively (For example, 192.168.0.0/24).
To define multiple subnets, separate each IP subnet one in a line. For example:
192.168.0.0/24 10.8.0.0/16
This is to choose which WAN IP address(es) the web server should listen on.
Upgrading firmware can be done in one of three ways. Using the router's interface to automatically check for an update, using the router's interface to manually upgrade the firmware, or using InControl2 to push an upgrade to a router.
The automatic upgrade can be done from
>
.
If an update is found the buttons will change to allow you to the firmware.
Click on the
button. A prompt will be displayed advising to
download the Current Active Configuration. Please click on the underlined download
text. After downloading the current config click the button to start the upgrade
process.
The router will download and then apply the firmware. The time that this process takes will depend on your internet connection's speed.
The firmware will now be applied to the router*. The amount of time it takes for the firmware to upgrade will also depend on the router that's being upgraded.
*Upgrading the firmware will cause the router to reboot.
In some cases, a special build may be provided via a ticket or it may be found in the forum. Upgrading to the special build can be done using this method, or using IC2 if you are using that to manage your firmware upgrades. A manual upgrade using the GA firmware posted on the site may also be recommended or required for a couple of reasons. All of the Peplink/Pepwave GA firmware can be found here (https://www.peplink.com/ support/downloads/) Navigate to the relevant product line (ie. Balance, Max, FusionHub, SOHO, etc). Some product lines may have a dropdown that lists all of the products in that product line. Here is a screenshot from the Balance line.
If the device has more than one firmware version the current hardware revision will be required to know what firmware to download. Navigate to System > Firmware and click the Choose File button under the Manual Firmware Upgrade section. Navigate to the location that the firmware was downloaded to select the ".img" file and click the Open button. Click on the Manual Upgrade button to start the upgrade process.
A prompt will be displayed advising to download the Current Active Configuration. Please click on the underlined download text. After downloading the current config click the Ok button to start the upgrade process. The firmware will now be applied to the router*. The amount of time it takes for the firmware to upgrade will depend on the router that's being upgraded.
*Upgrading the firmware will cause the router to reboot.
Described in this knowledgebase article on our forum. (https://forum.peplink.com/t/ upgrading-firmware-the-incontrol2-method/)
enables the system clock of the Pepwave router to be synchronized with
a specified time server. Time settings are located at
.
This specifies the time zone (along with the corresponding Daylight
Savings Time scheme). The
value affects the time stamps in
the Pepwave router's event log and e-mail notifications. Check
to show all time zone options.
This field allows to select your time sync mode, the available options are:
Time Server GPS GPS with Time Server as fallback
This setting specifies the NTP network time server to be utilized by the Pepwave router.
Enable and disable different functions (such as WAN connections, outbound policy, and firewalls at different times, based on a user-scheduled configuration profile. The settings for this are located at
Enable scheduling, and then click on your schedule name or on the button to begin.
Click this checkbox to enable this schedule profile. Note that if this is disabled, then any associated features will also have their scheduling disabled. Enter your desired name for this particular schedule profile.
Click the drop-down menu to choose pre-defined schedules as your starting point. Please note that upon selection, previous changes on the schedule map will be deleted.
Click on the desired times to enable features at that time period. You can hold your mouse for faster entry.
Email notification functionality provides a system administrator with up-to-date
information on network status. The settings for configuring email notifications are
found at
.
This setting specifies whether or not to enable email notification.
If
is checked, the Pepwave router will send email
messages to system administrators when the WAN status
changes or when new firmware is available. If
is not
checked, email notification is disabled and the Pepwave router
will not send email messages.
This setting specifies the SMTP server to be used for sending email. If the server requires authentication, check
.
This setting specifies via a drop-down menu one of the following valid Connection Security:
None STARTTLS SSL/TLS
This field is for specifying the SMTP port number. By default, this
is set to . If Connection Security is selected "
", the
default port number will be set to . If Connection Security is
selected "
", the default port number will be set to .
You may customize the port number by editing this field.
This setting specifies the SMTP username and password while
sending email. These options are shown only if
is checked in the
setting.
This field allows you to verify and confirm the new administrator password.
This setting specifies the email address the Pepwave router will use to send reports.
This setting specifies the email address(es) to which the Pepwave router will send email notifications. For multiple recipients, separate each email addresses using the enter key.
After you have finished setting up email notifications, you can click the
button to test the settings before saving. After
is
clicked, you will see this screen to confirm the settings:
Click detailed test results.
to confirm. In a few seconds, you will see a message with
Event log functionality enables event logging at a specified remote syslog server. The
settings for configuring the remote system log can be found at
.
This setting specifies whether or not to log events at the specified remote syslog server.
This setting specifies the IP address or hostname of the remote syslog server.
The Pepwave router can also send push notifications to mobile devices that have our Mobile Router Utility installed. Check the box to activate this feature.
This setting is to enable event logging at the specified log server.
This setting specifies the IP address or hostname of the URL log server.
This setting is to enable event logging at the specified log server.
This setting specifies the IP address or hostname of the Session log server.
For more information on the Router Utility, go to: www.peplink.com/products/router-utility (http://www.peplink.com/ products/router-utility)
SNMP or simple network management protocol is an open standard that can be used to collect information about the Pepwave router. SNMP configuration is located at
.
This field shows the router name defined at .
This option specifies the port which SNMP will use. The default port is . This option allows you to enable SNMP version 1. This option allows you to enable SNMP version 2. This option allows you to enable SNMP version 3.
This option allows you to enable SNMP Trap. If enabled, the following entry fields will appear.
This setting specifies the SNMP Trap community name.
Enter the IP address of the SNMP Trap server.
This option specifies the port which the SNMP Trap server will use. The default port is .
This option allows you to enable and configure the heartbeat interval for the SNMP Trap server.
To add a community for either SNMPv1 or SNMPv2, click the
button in the
table, upon which the following screen is displayed:
This setting specifies the SNMP community name.
This setting specifies a subnet from which access to the SNMP server is allowed. Enter subnet address here (e.g., 192.168.1.0) and select the appropriate subnet mask.
To define a user name for SNMPv3, click table, upon which the following screen is displayed:
in the
This setting specifies a user name to be used in SNMPv3.
This setting specifies via a drop-down menu one of the following valid authentication protocols:
NONE MD5 SHA
When MD5 or SHA is selected, an entry field will appear for the password.
This setting specifies via a drop-down menu one of the following valid privacy protocols:
NONE DES
When DES is selected, an entry field will appear for the password.
SMS Control allows the user to control the device using SMS even if the modem does
not have a data connection. The settings for configuring the SMS Control can be found
at
.
Supported Models
: *-LTE-E, *-LTEA-W, *-LTEA-P, *-LTE-MX
: *-LW*, *-LP*
When this box is checked, the device will be allowed to take actions according to received commands via SMS.
Make sure your mobile plan supports SMS, and note that some plans may incur additional charges for this.
SMS Control can reboot devices and configure cellular settings over signalling channels, even if the modem does not have a data connection.
For details of supported SMS command sets, please refer to our knowledge base (https://download.peplink.com/resources/sms_control_command_reference.pdf).
Click the checkbox to enable the SMS Control.
This setting sets the password for authentication maximum of 32 characters, which cannot include semicolon (;).
Optionally, you can add phone number(s) to the whitelist. Only matching phone numbers are allowed to issue SMS commands. Phone numbers must be in the E.164 International Phone Numbers format.
InControl is a cloud-based service which allows you to manage all of your Peplink and Pepwave devices with one unified system. With it, you can generate reports, gather statistics, and configure your devices automatically. All of this is now possible with InControl.
When this check box is checked, the device's status information will be sent to the Peplink InControl system. This device's usage data and configuration will be sent to the system if you enable the features in the system.
Alternatively, you can also privately host InControl. Simply check the "Privately Host InControl" box and enter the IP Address of your InControl Host. If you have multiple hosts, you may enter the primary and backup IP addresses for the InControl Host and tick the "Fail over to InControl in the cloud" box. The device will connect to either the primary InControl Host or the secondary/backup ICA/IC2.
You can sign up for an InControl account at https://incontrol2.peplink.com/. You can register your devices under the account, monitor their status, see their usage reports, and receive offline notifications.
Backing up Pepwave router settings immediately after successful completion of initial
setup is strongly recommended. The functionality to download and upload Pepwave
router settings is found at
. Note that available options vary by
model.
The
button is to reset the
configuration to factory default settings. After clicking the
button, you will need to click the
button on
the top right corner to make the settings effective.
Click
to backup the current active settings.
To restore or change settings based on a configuration file,
click
to locate the configuration file on the
local computer, and then click
. The new settings
can then be applied by clicking the
button
on the page header, or you can cancel the procedure by
pressing
on the main page of the web admin
interface.
In a high availability (HA) configuration, a Pepwave router
can quickly load the configuration of its HA counterpart. To
do so, click the
button. After loading the settings,
configure the LAN IP address of the Pepwave router so that
it is different from the HA counterpart.
Some Pepwave routers have features that can be activated upon purchase. Once the
purchase is complete, you will receive an activation key. Enter the key in the
field, click
, and then click
.
This page provides a reboot button for restarting the system. For maximum reliability,
the Pepwave router can equip with two copies of firmware. Each copy can be a
different version. You can select the firmware version you would like to reboot the
device with. The firmware marked with
is the current system boot up
firmware.
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4250)
#4249)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4247)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4248)
series-user-manual/#4246)
(https://manual.peplink.com/peplink-b-one-
The ping test tool sends pings through a specific Ethernet interface or a
SpeedFusionTM VPN connection. You can specify the number of pings in the field
, to a maximum number of 10 times.
can be set to a
maximum of 1472 bytes. The ping utility is located at
illustrated
below:
A system administrator can use the ping utility to manually check the connectivity of a particular LAN/WAN connection.
The traceroute test tool traces the routing path to the destination through a particular
Ethernet interface or a SpeedFusionTM connection. The traceroute test utility is located
at
.
A system administrator can use the traceroute utility to analyze the connection path of a LAN/WAN connection.
Peplink routers can send special "magic packets" to any client specified from the Web UI. To access this feature, navigate to
Select a client from the drop-down list and click
to send a "magic packet"
The WAN Analysis feature allows you to run a WAN to WAN speed test between 2 Peplink devices .
You can set a device up as a
or a
. One device must be set up as a server
to run the speed tests and the server must have a public IP address.
The default port is 6000 and can be changed if required. The IP address of the WAN
interface will be shown in the
section.
The client side has a few more settings that can be changed. Make sure that the
matches what's been entered on the server side. Select the WAN(s) that
will be used for testing and enter the Servers WAN IP address. Once all of the options
have been set, click the
button.
The test output will show the
and the
.
, the
as a graph,
The test can be run again once it's complete by clicking the
click
and change the parameters for the test.
button or you can
The CLI (command line interface) can be accessed via SSH. This field enables CLI support. The below settings specify which TCP port and which interface(s) should accept remote SSH CLI access. The user name and password used for remote SSH CLI access are the same as those used for web admin access.
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4244)
#4242)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4241)
#4240)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4239)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4238)
#4237)
(https://manual.peplink.com/peplink-b-one-series-user-manual/
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4233)
System information is located at
.
This is the name specified in the
located at
.
field
This shows the model name and number of this device.
If your model uses a product code, it will appear here.
This shows the hardware version of this device.
This shows the serial number of this device.
This shows the firmware version this device is currently running.
This shows the current SpeedFusion VPN version.
This shows the modem support version. For a list of
supported modems, click
.
InControl Managed Configurations (firmware, VLAN, Captive Portal, etcetera)
The host name assigned to the Pepwave router appears here.
This shows the length of time since the device has been rebooted.
This shows the current system time.
Link to download OpenVpn Client profile when this is enabled in Remote User Access
The
link is for exporting a diagnostic report
file required for system investigation.
This option is to time duration.
remote assistance with the
The second table shows the MAC address of each LAN/WAN interface connected. To
view your device's End User License Agreement (EULA), click
Legal.
Information on active sessions can be found at
This screen displays the number of sessions initiated by each application. Click on each service listing for additional information. This screen also indicates the number of sessions initiated by each WAN port. In addition, you can see which clients are initiating the most sessions.
You can also perform a filtered search for specific sessions. You can filter by subnet, port, protocol, and interface. To perform a search, navigate to
.
This
section displays the active inbound/outbound sessions of each
WAN connection on the Pepwave router. A filter is available to sort active session
information. Enter a keyword in the field or check one of the WAN connection boxes for
filtering.
The client list table is located at
. It lists DHCP and online client IP
addresses names (retrieved from the DHCP reservation table or defined by users),
current download and upload rate, and MAC address.
Clients can be imported into the DHCP reservation table by clicking the on the right. You can update the record after import by going to
button .
If the PPTP server (see
(https://docs.google.com/document/
d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/
edit#bookmark=id.3nqndbk) SpeedFusionTM (see
(https://
docs.google.com/document/d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/
edit#bookmark=id.2y3w247)), or AP controller (see
(https://
docs.google.com/document/d/1Vp7p6ElA8pgmy5zbnxpQKqcxCyEaT3QWyxMtVTpwUic/
edit#bookmark=id.1maplo9)) is enabled, you may see the corresponding connection
name listed in the
field.
In the client list table, there is a "Ban Client" feature which is used to disconnect the
Wi-Fi and Remote User Access clients by clicking the
button on the right.
There is a blocklist on the same page after you banned the Wi-Fi or Remote User Access clients.
You may also unblock the Wi-Fi or Remote User Access clients when the client devices
need to reconnect the network by clicking the
button on the right.
The table that shows the forwarded ports under UPnP and NAT-PMP protocols is
located at
. This section appears only if you have enabled UPnP
/ NAT-PMP as mentioned in
.
Click
to delete a single UPnP / NAT-PMP record in its corresponding row. To
delete all records, click
on the right-hand side below the table.
UPnP / NAT-PMP records will be deleted immediately after clicking the
or
without the need to click
or
.
button
Shows status of OSPF and RIPv2
Shows status of BGP
Current SpeedFusion VPN status information is located at
.
Details about SpeedFusion VPN connection peers appears as below:
Click on the corresponding peer name to explore the WAN connection(s) status and subnet information of each VPN peer.
Click the
button for a SpeedFusion chart displaying real-time throughput,
latency, and drop-rate information for each WAN connection.
When pressing the
button, the following menu will appear:
The
shows the details of the selected SpeedFusion VPN
profile, consisting of the Profile name,
,
e and
of
the remote router
Advanced features for the SpeedFusion VPN profile will also be shown when the checkbox is selected.
The (when
show information about the local and remote WAN connections ) is selected.
The available details are connection.
and
used for the Speedfusion
.
Connections can be temporarily disabled by sliding the switch button next to a WAN connection to the left. The wan-to-wan connection disabled by the switch is temporary and will be re-enabled after 15 minutes without any action.
This can be used when testing the SpeedFusion VPN's speed between two locations to see if there is interference or network congestion between certain WAN connections.
The SpeedFusion VPN test configuration allows us to configure and perform thorough tests. This is usually done after the initial installation of the routers and in case there are problems with aggregation.
Press the Start button to perform throughput test according to the configured options. If TCP is selected, 4 parallel streams will be generated to get the optimal results by default. This can be customized by selecting a different value of streams. Using more streams will typically get better results if the latency of the tunnel is high.
Peplink also published a whitepaper about Speedfusion which can be downloaded from the following url: http://download.peplink.com/resources/whitepaper-speedfusion-and-bestpractices-2019.pdf (http://download.peplink.com/resources/whitepaper-speedfusionand-best-practices-2019.pdf)
Event log information is located at
.
The log section displays a list of events that has taken place on the Pepwave router.
Click the
to refresh log entries automatically. Click the
button to clear
the log.
This section displays a list of events that have taken place within a firewall. Click the button and the log will be refreshed.
This section displays a list of events that have taken place within a SpeedFusion VPN
connection. Click the
button and the log will be refreshed.
The WAN connection.
allow to show detailed information about each connected
For cellular connections it shows signal strength, quality, throughput and latency for the past hour.
This section shows bandwidth usage statistics and is located at
Bandwidth usage at the LAN while the device is switched off (e.g., LAN bypass) is neither recorded nor shown.
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4230) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4229) (https://manual.peplink.com/peplink-b-one-series-user-manual/#4228)
(https://manual.peplink.com/peplink-b-one-series-user-manual/#4227)
The
table indicates how much network traffic has
been processed by the device since the first bootup. The
table indicates how much network traffic has been processed by the device
since the last bootup.
This page shows the hourly bandwidth usage for all WAN connections, with the option of viewing each individual connection. Select the desired connection to check from the drop-down menu.
This page shows the daily bandwidth usage for all WAN connections, with the option of viewing each individual connection.
Select the connection to check from the drop-down menu. If you have enabled the
feature the
table for that WAN
connection will be displayed.
Click on a date to view the client bandwidth usage of that specific date. This feature is not available if you have selected to view the bandwidth usage of only a particular WAN connection. The scale of the graph can be set to display megabytes ( ) or gigabytes ( ).
All WAN Daily Bandwidth Usage
This page shows the monthly bandwidth usage for each WAN connection. If you have
enabled the
feature, you can check the usage of each
particular connection and view the information by
or by
.
Click the first two rows to view the client bandwidth usage in the last two months. This feature is not available if you have chosen to view the bandwidth of an individual WAN connection. The scale of the graph can be set to display megabytes ( ) or gigabytes ( ).
All WAN Monthly Bandwidth Usage
Ethernet WAN Monthly Bandwidth Usage By default, the scale of data size is in . 1GB equals 1024MB.
To restore the factory default settings on a Pepwave router, follow the steps below: 1. Locate the reset button on the front or back panel of the Pepwave router.
2. With a paperclip, press and keep the reset button pressed. Hold for approximately 10 seconds for factory reset (Note: The LED status light shows in RED, until the status light off and release the button). After the Pepwave router finishes rebooting, the factory default settings will be restored.
All previous configurations and bandwidth usage data will be lost after restoring factory default settings. Regular backup of configuration settings is strongly recommended.
UDP 5246
Data flow
InControl
Outbound
Enabled
TCP 443
HTTPS service
InControl
Outbound
Enabled
TCP 5246
Optional, used when TCP 443 is not responding
InControl
Outbound
Enabled
TCP 5246
Remote Web Admin
InControl Virtual Appliance
Outbound
Enabled
TCP 4500
VPN Data (TCP Mode)
SpeedFusion VPN / SpeedFusion
Inbound / Outbound*
Disabled
TCP 32015
VPN handshake
SpeedFusion VPN / SpeedFusion
Inbound / Outbound*
Disabled
UDP 4500
VPN Data
SpeedFusion VPN / SpeedFusion
Inbound / Outbound*
Disabled
UDP 32015
VPN Data (alternative)
SpeedFusion VPN / SpeedFusion
Inbound / Outbound*
Disabled
TCP/UDP 4500+N-1^
VPN Sub-Tunnels Data
SpeedFusion VPN / SpeedFusion
Inbound / Outbound*
Disabled
UDP 32015+N-1^
VPN Sub-Tunnels Data (alternative)
SpeedFusion VPN / SpeedFusion
Inbound / Outbound*
Disabled
UDP 4500
VPN Data
IPsec
Inbound / Outbound*
Disabled
UDP 500
VPN initiation
IPsec
Inbound / Outbound*
Disabled
UDP 500
L2TP
Remote User Access
Inbound
Disabled
UDP 1701
L2TP
Remote User Access
Inbound
Disabled
UDP 4500
UDP 1194
IP 47
TCP 2222
TCP 80
TCP 443
TCP 8822 UDP 161 UDP 162 TCP, UDP 1812 TCP, UDP 1813 UDP 123
L2TP
Remote User Access
Inbound
OpenVPN
Remote User Access
Inbound
PPTP (GRE)
Remote User Access
Inbound
Remote Assistance Direct connection
Peplink Troubleshooting Assistance
Outbound
HTTP traffic
Web Admin Interface access
Inbound
HTTPS traffic
Web Admin Interface access (secure)
Inbound
SSH
SSH
Inbound
SNMP Get
SNMP monitoring Inbound
SNMP Trap
SNMP monitoring Outbound
Radius Authentication
Radius
Outbound
Radius Accounting
Radius
Outbound
Network Time Protocol
NTP
Inbound Outbound
Disabled Disabled Disabled Enabled
Enabled Enabled
Disabled Disabled Disabled Disabled Disabled Disabled Enabled
TCP 60660
Real-time
GPS
location data in
NMEA format
Outbound
Disabled
By default, only TCP 32015 and UDP 4500 are needed for SpeedFusion VPN / SpeedFusion.
Inbound / Outbound* Inbound = For Server mode; Outbound = For Client mode UDP 32015 If IPsec VPN or L2TP/IPsec RUA is enabled, the UDP 4500 is occupied,
so SpeedFusion VPN / SpeedFusion will automatically switch to UPD 32015 as VPN data port . UDP 32015+N-1^ / TCP/UDP 4500+N-1^ When using Sub-Tunnels, multiple ports are in use (1 for each Sub-Tunnel profile). The default UDP data ports used when using (N number of Sub-Tunnel profiles) are: 4500...4500+N-1, or (when port 4500 is in use by IPsec or L2TP/IPsec) 32015... 32015+N-1.
© 2022 Peplink | Pepwave. All Rights Reserved.
cairo 1.18.0 (https://cairographics.org) Mozilla Firefox 127.0