Peplink Balance 380 HW3 Router Firmware 6.2 Download

Posted at December 31, 2024 by PCI-DB Team

Peplink Balance 380 HW3 Router Firmware 6.2 Description

Important Notices:

- SSLv3 POODLE Vulnerability (CVE-2014-3566) Addressed: A vulnerability in the design of SSLv3 has been made public. Firmware 6.2 addresses this vulnerability.
- Layer 2 PepVPN Profiles Need Reconfiguration: Layer 2 PepVPN is now easier to use and more flexible. However, PepVPN profiles created using Firmware 6.1 or below will need to be reconfigured in order to work in Firmware 6.2.
- Adjustment Needed for AP One AC Mini: In order for clients to connect to the AP One AC Mini using 802.11ac, you will need to make a slight adjustment. Please go to the Web UI and navigate to AP > Profiles > *your profile*. There, find the “5Ghz channel bonding” setting and change it to “auto”.
- PepVPN Will Appear Offline on Router Utility Version 1.3: For devices running Firmware 6.2, Router Utility 1.3 will incorrectly show PepVPN connections as offline. This can be addressed by upgrading to Router Utility version 1.4.

New Features:

Multi-Site PepVPN Profile:

- WebUI: With a single click, form PepVPN / SpeedFusion connections with up to thousands of remote sites using the same ID and preshared key. No further configuration necessary.
- Navigation: Network > Interfaces > SpeedFusion

PepVPN Layer 2 Peer Isolation:

- PepVPN: Isolate different clients connected to the same L2 PepVPN broadcast domain. Each device will see only themselves and headquarters.
- Navigation: Network > LAN > (?) Enable VLAN > Click LAN > (?) Enable Layer-2 bridging based PepVPN

Configurable Traffic Direction:

- PepVPN: Assign any link in a PepVPN tunnel to be upload only, download only, or both ways.
- Navigation: Network > SpeedFusion > Click Profile > WAN Connection Priority > (?) Enable Asymmetric Connection

Internal Service Forwarding:

- Routing: Intercept traffic from specified ports and forward it to a local server.
- Navigation: Network > Service Forwarding > Custom Service Forwarding Setup

Feature Improvements:

- CLI: CLI SSH admin access can now also be restricted by source IP address.
- Firewall: Outbound firewall rules can now match by source MAC address.
- PepVPN: PepVPN profiles can now be configured to connect profiles on a first-come, first-served basis when the number of created profiles exceeds the number of peers supported.
- PepVPN: Layer 2 PepVPN is now compatible with VLAN on LAN. Options located under Network > LAN > IP Settings > Help Button.
- PepVPN: PepVPN is now more compatible with small MTU environments
- PepVPN: PepVPN Test is now showing per WAN info for easier performance analysis
- PepVPN: Bandwidth limits on PepVPN peers can now be set for both uplink and downlink.
- QoS: All devices now support bandwidth limits for individual clients.
- Routing: L2TP is now supported as WAN connection method.
- Routing: PepVPN NAT Mode has improved OSPF support. The client side can now accept routes from the server side without advertising its own network(s).
- Routing: OSPF, and all 7 load balancing algorithms are now available across all Balance and MAX models.
- Web UI: For easier access, the PepVPN Test and Analyzer is now located under Status > PepVPN (Status > SpeedFusion for devices supporting SpeedFusion).

Resolved Issues:

- Captive Portal: The Captive Portal is unable to intercept and redirect HTTPS connections to the splash page. 
- Drop-in Mode: When Drop-in mode is enabled, dropin WAN settings cannot be saved.
- Notifications: Email notifications cannot be sent through PepVPN.
- PepVPN: PepVPN Analyzer does not work with WAN Connection Mapping
- Routing: When mixing authentication modes (none, text, MD5) while using RIP, the routing table will refresh continuously.
- Routing: When switching RIP authentication modes using the same password, the routing table can still be learned
- Routing: The active sessions of LAN VLAN hosts will not show up in the "Status"->"Active Session" page.
- Routing: When using RIPv2, a connected router will remain on the list of learned routes even after the peer router has been removed.

  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.

Related Peplink Drivers