Peplink Pepwave MAX HD2 HW6 Router Firmware 8.2.0

New Features:

- [RC 1] [InTouch] New: Web-based InTouch is supported through InControl. You can visit the web admin of client devices behind Peplink/Pepwave routers. Note: web-based InTouch traffic is counted as SpeedFusion Cloud traffic.
Compatible with All Models

- [Beta 1] [SpeedFusion Cloud] New: SpeedFusion Cloud Home
Compatible with All Models (Except FusionHub)

- [Beta 1] [SpeedFusion] New: Advanced settings for Dynamic Weighted Bonding
Compatible with Balance: 210 or above
Compatible with MAX: 700, HD2/4, Transit
Compatible with UBR: UBR LTE
Compatible with MediaFast: All
Compatible with SFE
Compatible with X Series: All (Except 20X)
Compatible with FusionHub Device with PrimeCare license

- [Beta 1] [Route-Based IPsec] New: Route-Based IPsec VPN support
Compatible with Balance: 30 LTE/Pro, One/Two, 210/310 HW4 or above, 305/380 or above
Compatible with MAX: BR1 ENT, Transit, 700 HW3 or above, HD2 HW5 or above, HD4
Compatible with MediaFast: All
Compatible with X Series: All
Compatible with FusionHub

- [Beta 1] [System] New: DNS over HTTPS (DoH)
Compatible with All Models

Improvements:

- [RC 3] [AP Controller] Added: Preferred Frequency is 5GHz by default
- [RC 3] [AP Controller] Added: Security Policy - Enhanced Open (OWE)
Compatible with Balance: All
Compatible with MAX: 700, HD2/4, Transit
Compatible with MediaFast: All
Compatible with X Series: EPX, SDX Pro, SDX, 580X, 380X, PDX, MBX

- [RC 2] [310X] Added: AP Controller Pro
Compatible with X Series: 310X

- [RC 2] [Cellular] Updated: Changed the APN of Singaporecarrier Singtel from "Internet" to "e-ideas"
- [RC 1] [Cellular] Added: Device API /api/cmd.sms.get supported MTN, ICCID and IMSI
Compatible with Balance: 30 LTE/Pro, 310 5G/Fiber 5G
Compatible with MAX: BR1/2, HD2/4, Transit
Compatible with UBR: UBR LTE
Compatible with MediaFast: HD2/HD4
Compatible with X Series: All

- [Beta 1] [5G] Added: Carrier selection
- [Beta 1] [5G] Added: Cellular Band selection
- [Beta 1] [5G] Added: Cellular supports Authentication Protocol PAP and CHAP
Compatible with Balance: 310 5G/Fiber 5G
Compatible with X Series: EPX, MBX, SDX Pro, SDX, 310X

- [Beta 1] [B20X] Added: DPI Reporting on Balance 20X
- [Beta 1] [B20X] Added: IP Passthrough for Balance 20X
Compatible with X Series: 20X

- [Beta 1] [BR1 Pro 5G] Added: AP Controller could manage up to 30x AP One devices
Compatible with MAX: BR1 Pro 5G

- [Beta 1] [Captive Portal] Updated: Captive Portal SSL certificate (captive-portal.peplink.com) had been renewed
- [Beta 1] [SpeedFusion Cloud] Added: Traffic Steering Priority. Select the priority of the "Connect Clients to Cloud", "Link Wi-Fi to Cloud" and "Optimize Cloud Application" traffic steering rules.
Compatible with All Models (Except FusionHub)

- [Beta 1] [DPI] Added: Enhanced BitTorrent detection
- [Beta 1] [InControl] Added: Priority for multiple InControl Hosts
- [Beta 1] [InControl] Added: Priority settings for InControl Hosts
- [Beta 1] [SNMP] Added: Custom Port for SNMP Trap server
- [Beta 1] [SNMP] Added: SNMP Heartbeat Trap
- [Beta 1] [System] Added: "Download package updates" options under support.cgi
- [Beta 1] [System] Added: Client Type in Client List
- [Beta 1] [System] Added: Public-key authentication in making CLI SSH sessions
- 26703 [Beta 1] [System] Added: QoS > "User Groups" and "Group Bandwidth Reservation" are available to all models
- [Beta 1] [System] Added: WAN Priority is included in WAN up/down event logs
Compatible with All Models

- [Beta 1] [Cellular Cat-20] Added: Support Cat-20 Cellular module
Compatible with Device with integrated cellular and product code

- [Beta 1] [Jumbo Frame] Added: Jumbo Frame MTU on Ethernet and SFP WAN Settings
Compatible with Balance: 305, 380 or above
Compatible with MediaFast: 500, 750
Compatible with X Series: EPX, SDX Pro, SDX, 580X, 380X

- [Beta 1] [Route-Based IPsec] Added: Outbound Policy supports Route-Based IPsec VPN
Compatible with Balance: 30 LTE/Pro, One/Two, 210/310 HW4 or above, 305/380 or above
Compatible with MAX: BR1 ENT, Transit, 700 HW3 or above, HD2 HW5 or above, HD4
Compatible with MediaFast: All
Compatible with X Series: All
Compatible with FusionHub

- [Beta 1] [SpeedFusion] Added: Additional parameters for "Dynamic Weighted Bonding", Congestion Latency Level, Ignore Packet Loss Event, Disable Bufferbloat Handling, Disable TCP ACK Optimization
Compatible with Balance: 210 or above
Compatible with MAX: 700, HD2/4, Transit
Compatible with UBR: UBR LTE
Compatible with MediaFast: All
Compatible with SFE
Compatible with X Series: All (Except 20X)
Compatible with FusionHub Device with PrimeCare license

- [Beta 1] [VDSL] Added: VDSL WAN status
Compatible with Balance: 20X
Compatible with X Series: 580X, 380X

- [Beta 1] [Wi-Fi AP] Added: Web Admin will prompt the user to change the Wi-Fi password when the device started with the default configuration
- [Beta 1] [Wi-Fi] Added: Operating country now supports Argentina
Compatible with Balance: 30 Pro, One
Compatible with MAX: All (Exclude: BR1 ENT, HD2 Mini, HD1/2 Dome)
Compatible with MediaFast: HD2/4
Compatible with X Series: PDX, MBX, 20X
Compatible with UBR: UBR LTE
Compatible with Surf SOHO

- [Beta 1] [Wi-Fi WAN & HD2/HD4] Added: Simultaneous dual radio for Wi-Fi WAN
Compatible with MAX: HD2/4
Compatible with MBX: HD2/4

Resolved Issues:

- [RC 2] [DDNS] Fixed: DDNS client might not update IP address
- [RC 2] [DPI] Fixed: Twitter.com in exemption list did not work
- [Beta 2] [PepVPN] Fixed: Outbound Policy rules in Expert Mode might not route traffic to the expected sub-tunnel if remote peer was configured to route to another sub-tunnel
- [Beta 1] [InControl] Fixed: Some Event Logs could not be sent to InControl if Firewall Logging was enabled
- [Beta 1] [InControl] Fixed: Some of the DPI data might not be resent to InControl if the Internet connection was not stable
- [Beta 1] [IPsec] Fixed: After IPsec IKEv2 connection failed over to lower priority WAN, the IPsec status showed disconnected
- [Beta 1] [OpenVPN] Fixed: Used incorrect subnet mask on OpenVPN WAN
- [Beta 1] [PepVPN] Fixed: Layer 2 PepVPN/SpeedFusion profile might keep disconnecting
- [Beta 1] [PepVPN] Fixed: Multicast traffic might not be forwarded in Layer 2 PepVPN/SpeedFusion
- [Beta 1] [PepVPN] Fixed: PepVPN Test in UDP mode might show unexpected packet loss
- [Beta 1] [Remote User Access] Fixed: Logging in Remote User Access with Local User Accounts would fail if the password contained a space
- [Beta 1] [System] Fixed: Bonjour Forwarding did not work on PepVPN/SpeedFusion
- [Beta 1] [System] Fixed: NAT Mapping or Inbound Port Forwarding did not work for the route for the target LAN host was learned from OSPF
- [Beta 1] [System] Fixed: RADIUS Authentication did not work with Cisco ACS
- [Beta 1] [System] Fixed: Service Passthrough had a higher priority than SpeedFusion Cloud rules
- [Beta 1] [System] Fixed: Service Passthrough traffic (SIP, FTP, TFTP) might not be routed in rare situations
- [Beta 1] [System] Fixed: When a WAN was down, existing IP sessions were kept routing to it
- [RC 1] [DPI] Fixed: YouTube blocking did not work
Compatible with All Models

- [Beta 1] [OpenVPN WAN] Fixed: Remote Port setting of OpenVPN WAN is not shown correctly
- [Beta 1] [OpenVPN WAN] Fixed: Uploading an ovpn file for OpenVPN WAN may result in getting an "Internal Error" message
- [Beta 1] [Outbound Policy] Fixed: Outbound Policy by Domain Name did not work if the domain name contains an uppercase letter
- [Beta 1] [SpeedFusion Cloud] Fixed: SpeedFusion Cloud custom data ports did not take effect
Compatible with All Models (Except FusionHub)

- [RC 1] [BR1 Pro 5G] Fixed: Wi-Fi WAN might not connect to mobile hotspot
Compatible with MAX: BR1 Pro 5G

- [Beta 2] [AP Controller] Fixed: AP Controller would keep pushing configuration to AP devices if the SSID or passphrase had "%" characters
Compatible with Balance: All
Compatible with MAX: 700, HD2/4, Transit
Compatible with MediaFast: All
Compatible with X Series: EPX, SDX Pro, SDX, 580X, 380X, PDX, MBX

- [Beta 2] [PepVPN with selective models] Fixed: Unencrypted PepVPN/SpeedFusion profiles would not be connected if the device uptime had more than 99 days
Compatible with Balance: 20/30
Compatible with MAX: BR1
Compatible with UBR: UBR LTE
Compatible with Surf SOHO

- [Beta 2] [USB Cellular] Fixed: USB Cellular did not work if the SIM card required username and password
Compatible with Balance: All
Compatible with MAX: BR1 ENT, HD2/4
Compatible with MediaFast: All
Compatible with X Series: All
Compatible with Surf SOHO

- [Beta 1] [5G & -5GD] Fixed: An incorrect IP address obtained when connecting to T-Mobile
- [Beta 1] [5G & -5GD] Fixed: RSSI could not be shown when the cellular is connected to 3G
- [Beta 1] [5G & -5GD] Fixed: Unable to connect to EE (UK carrier)
Compatible with Balance: 310 5G/Fiber 5G
Compatible with X Series: EPX, MBX, SDX Pro, SDX, 310X (Device with 5G Cellular and product code contains -5GD)

- [Beta 1] [B210 HW5] Fixed: VLAN on LAN did not work if the device was applied for Additional WAN License
Compatible with Balance: 210 HW5

- [Beta 1] [Cellular & Transit/HD] Fixed: Cellular could not reconnect after the device passed through the dead zone
Compatible with Balance: 30 LTE/Pro
Compatible with MAX: HD2/4, Transit
Compatible with MediaFast: HD2/HD4

- [Beta 1] [Cellular LTEA-W] Fixed: Could not receive SMS
Compatible with Device with integrated cellular and product code contains "LTEA-W"

- [Beta 1] [Cellular] Fixed: Devices with standby cellular WANs might send incorrect disconnect event logs to InControl
- [Beta 1] [Cellular] Fixed: Unable to stop traffic when SIM pool quota exceeded
Compatible with Balance: 30 LTE/Pro, 310 5G/Fiber 5G
Compatible with MAX: BR1/2, HD2/4, Transit
Compatible with UBR: UBR LTE
Compatible with MediaFast: HD2/HD4
Compatible with X Series: All

- [Beta 1] [Docker] Fixed: High memory usage of Docker container(s) might cause system instability
Compatible with MediaFast: 500, 750

- [Beta 1] [MBX] Fixed: One of devices' Wi-Fi interfaces did not work after booting up
Compatible with X Series: MBX

- [Beta 1] [SOHO MK3] Fixed: LAN packet might be broadcasted to all LAN Ports
Compatible with Surf SOHO: SOHO MK3

- [Beta 1] [SpeedFusion] Fixed: FEC might not recover packets in rare situations
- [Beta 1] [SpeedFusion] Fixed: Updating Layer 2 SpeedFusion / PepVPN Whitelist might disconnect the tunnel
Compatible with Balance: 210 or above
Compatible with MAX: 700, HD2/4, Transit
Compatible with UBR: UBR LTE
Compatible with MediaFast: All
Compatible with SFE
Compatible with X Series: All (Except 20X)
Compatible with FusionHub Device with PrimeCare license

- [Beta 1] [Wi-Fi AP] Fixed: AP > Event Log showed incorrect Channel Switch information when Wi-Fi WAN was connected
- [Beta 1] [Wi-Fi AP] Fixed: SSIDs were not broadcasted on channel 165 if 5 GHz Wi-Fi Mesh was enabled
- [Beta 1] [Wi-Fi AP] Fixed: Wi-Fi clients could not associate to 2.4 GHz Wi-Fi AP
Compatible with Balance: 30 Pro, One
Compatible with MAX: All (Exclude: BR1 ENT, HD2 Mini, HD1/2 Dome)
Compatible with MediaFast: HD2/4
Compatible with X Series: PDX, MBX, 20X
Compatible with UBR: UBR LTE
Compatible with Surf SOHO

- [Beta 1] [Wi-Fi WAN & 11n] Fixed: Wi-Fi WAN might not reconnect to a Wi-Fi network
Compatible with MAX: BR1/2 (Indoor), 700 HW1-2, HD2 HW1-4
Compatible with UBR: UBR LTE
Compatible with Surf SOHO

Important Notices:

- InControl must be enabled on PrimeCare devices to update software features such as SpeedFusion (Bonding, WAN Smoothing, Hot Failover).
- Balance 20 Hardware Revision 1-6 will NOT be supported by further major firmware updates. They will receive Firmware 8.1.x maintenance releases as needed.
- PepVPN backward compatibility option is no longer available. By deprecating the old firmware versions, we now have a more secure handshake channel as the default setting, only TLS 1.2 will be accepted, no more TLS 1.0 and 1.1 for the old devices. Thus, if you are using devices running Firmware 6.1 or older, you will no longer be able to form PepVPN tunnels with those devices unless the firmware is updated.

About Router Firmware:

Before you consider downloading this firmware, go to the system information page of the router and make sure that the currently installed version isn't either newer or matching this release.

Due to the large variety of router models and different methods for upgrading the device, it is highly recommended that you read and, above all, understand the installation steps before you apply the new firmware, even if you are a power user.

In theory, these steps shouldn't be much of a hassle for anyone, because manufacturers try to make them as easy as possible, even if they don't always succeed. Basically, you must upload the new firmware to the router through its administration page and allow it to upgrade.

If you install a new version, you can expect increased security levels, different vulnerability issues to be resolved, improved overall performance and transfer speeds, enhanced compatibility with other devices, added support for newly developed technologies, as well as several other changes.

If you're looking for certain safety measures, remember that it would be best if you perform the upload using an Ethernet cable rather than a wireless connection, which can be interrupted easily. Also, make sure you don't power off the router or use its buttons during the installation, if you wish avoid any malfunctions.

If this firmware meets your current needs, get the desired version and apply it to your router unit; if not, check with our website as often as possible so that you don't miss the update that will improve your device.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.