Peplink Firmware 8.6.1 Beta 1: What’s New and What’s Fixed

Peplink posted Router Firmware 8.6.1 Beta 1 on September 11, 2026, a little over two months after 8.6.0 reached general availability. It is a point release, not a feature release, and the notes read that way: 17 improvements and 39 resolved issues, with a heavy lean toward cellular fixes, SpeedFusion plumbing, and three security advisories. If you skipped the 8.6.0 beta cycle and are wondering whether this one is worth your time, the short answer is that 8.6.1 is mostly a consolidation build. It rolls up 21 changes that Peplink had already shipped as special builds against 8.6.0 (the “s0xx” numbers in the notes), then adds a batch of new work on top.

Here is what matters, what is already in your hands if you have been running a special build, and what to watch before putting a beta on a router you depend on.

Download and release notes

• Beta firmware downloads: https://www.peplink.com/support/downloads/beta-firmware/
• Official release notes (PDF): https://download.peplink.com/resources/router-firmware-8.6.1b1-release-notes.pdf
• Open Beta Program terms: https://www.peplink.com/support/downloads/open-beta-program/

You have to click through the Open Beta Program terms before the download page loads. Read them. Section 4 of those terms matters more than most people realize, and we cover it in the counterpoint section below.

Supported hardware

8.6.1 Beta 1 supports the same broad range as 8.6.0: Balance 20X through 5000 EC (including the 310 5G, 310 Fiber 5G, and 310X lines), SDX and SDX Pro, the HD1 Dome family, MBX and MBX Mini, the BR1 Mini, BR1 Pro, BR1 Pro 5G, BR2 Pro and BR2 Micro, Transit Pro E and Duo Pro, MAX Orbit 2, 4 and 8, the entire B One family, MediaFast 500 and 750, UBR Plus, EPX, PDX and FusionHub. Hardware revisions matter for several items, so check the notes for your exact HW version before assuming a feature applies to you.

The 17 improvements, sorted by who cares

Cellular IPv6 (ref 36889)

This is the headline. Peplink added IPv6 support on cellular for a specific list of modem product codes: LTEA-US, LTEA-K, LTE-E, LTEA-D, GLTE-G, LTEA-Q, LTEA-E, LTEA-R, LTE-EJ, LTE-MX, LTE-MXS and LTE-US. That covers most Balance cellular models, the BR1 Pro CAT-20 and BR1 Pro 5G, BR2 Pro, Transit Pro E, B One Plus and B One 5G, EPX, PDX, and every SDX, Dome and MBX. Notably absent from the list: the 5GD and 5GK product codes, which means several current 5G modems are not included in this first pass. If your router’s product code does not contain one of the strings above, do not expect IPv6 over cellular yet.

Why it matters: T-Mobile has run IPv6-first on its consumer and business core for years, and Verizon and AT&T both hand out IPv6 to modern devices. Peplink routers that could only speak IPv4 over cellular were relying on carrier translation for anything IPv6-native. This closes a gap that competitors like Cradlepoint closed a long time ago.

Starlink integration (refs 37401, 37184, 37094, 37185)

Four Starlink items in one beta:

• Inhibit RF control. The router can now tell the dish to stop transmitting. This is the “stow the radio” function that maritime and aviation operators need for regulatory compliance in restricted zones.
• GPS status reporting now identifies when a Starlink subscription restricts location data, instead of just showing GPS as unavailable.
• The Care plan requirement for LAN access to the Starlink Dish API is gone. Any user on the LAN can now hit the dish API through the router without a paid plan.
• The dashboard only shows the “Starlink GPS unavailable” message when Starlink GPS is actually enabled and no Starlink WAN is providing a fix.

All four apply across the Balance, EPX, PDX, SDX, Dome, MBX, BR, Transit, B One, MediaFast and UBR lines. FusionHub is excluded, which makes sense since it has no physical WAN.

License and Care plan requirements removed (refs 37239, 37249)

Two changes here that are worth reading twice, because they cost Peplink revenue:

• Synergy Mode no longer requires a Care plan or a license on either the controller or the synergized device. Synergy Mode is Peplink’s feature for stacking a second router as additional WAN capacity on a primary unit. Until now it was gated behind paid plans on both sides.
• PrimeCare Secure DNS is now available on any active Care plan, not just PrimeCare. This was originally shipped as special build 8.6.0s059.

Peplink has been gradually removing paywalls from features that customers expected to be standard. This is the third or fourth round of that in the last year and a half, and it is a welcome trend.

Security hardening (ref 37690)

The notes say Peplink “hardened security measures against potential remote code execution through API requests” on all models. That phrasing is deliberately vague, and it is listed as an improvement rather than a security advisory, which suggests it is a defense-in-depth change rather than a fix for a known exploitable bug. We flag it anyway because RCE via API is the class of vulnerability that gets routers onto CISA’s KEV list.

Everything else

• WAN health checks now target Google, Cloudflare and Quad9 public DNS (ref 37381). Previously the defaults leaned on fewer providers.
• DNS-O-Matic has been removed from Dynamic DNS because the service is shutting down (ref 37764). If you use it, migrate before you upgrade.
• Docker memory allocation is now a shared limit across containers instead of per-container (ref 37098, originally 8.6.0s018). This matters for MediaFast and Docker-capable Balance and BR units running multiple containers.
• WINS server support added for a subset of models including Balance 310, 310 5G HW3, 580X HW2, BR1 Pro, BR1 Pro 5G, BR2 Pro, and all Dome, Transit, Orbit and B One (ref 37393).
• GPIO digital output can now be inverted in WAN Status mode (ref 37260, originally 8.6.0s096).
• IPv6 LAN Router Advertisement intervals now follow ISP-provided lifetimes (ref 37760, originally 8.6.0s076).
• Selected Wi-Fi frequency bands can be disabled across all radio functions, not just the AP (ref 35244). Useful for sites that need to keep a router off 6 GHz or 2.4 GHz entirely.
• MSP-suffix devices get customized product names and email footers in notifications (ref 37117).
• InControl can now apply feature activation keys even when the device is set to Restricted to Status Reporting Only (ref 37535).

The 39 resolved issues, grouped

Security advisories (3)

• DHCP client hostname handling vulnerability (ref 37662), all models.
• Web Admin access control vulnerability (ref 36956), all models.
• Multiple vulnerabilities in the management CLI (ref 37657), all models.

Add to that an input validation fix in device configuration handling on the Device API (ref 37611). Peplink does not publish CVE numbers in beta release notes. We will update this post if CVE identifiers are assigned when 8.6.1 goes GA. Our RouterCVE tool tracks these as they are published: https://routercve.com

Cellular (7)

• Slow registration on Vodafone Italy (ref 37264, originally 8.6.0s027).
• 5GD modules failing to switch carrier profiles (ref 37196, originally 8.6.0s049).
• IMS remaining enabled on 5GK modules connected to private networks (ref 37521, originally 8.6.0s046).
• Cellular firmware upgrades failing on LTE-E, LTE-US, LTE-MX and LTE-MXS modules on RAMIPS-based routers running 8.6.0 (ref 37183). This one is new in 8.6.1 and affects the BR1 Mini and similar MIPS-based hardware. If you have been unable to update modem firmware since moving to 8.6.0, this is why.
• LTEA-K modules failing to get an IPv4 address on Optus (ref 37792).
• LTEA-Q modules unable to establish data on KDDI in Japan (ref 37186, originally 8.6.0s061).
• GPS from cellular modules reporting no fix to InControl (ref 37160, originally 8.6.0s019).

SpeedFusion (6)

• SpeedFusion Connect tunnels dropping large packets (ref 37406).
• SpeedFusion Boost dropping traffic to ports 80, 2222, 5000 and 44444, and from clients on the FusionHub LAN (ref 37703).
• IP-fragmented UDP packets dropped on the receiving side (ref 37705).
• Traffic dropped after the sending peer restarted a flow’s packet sequence (ref 37628, originally 8.6.0s080).
• SpeedFusion Score per-WAN tests failing when a standby WAN was in the tunnel (ref 37557).
• FusionHub could not enable FIPS (ref 37586, originally 8.6.0s070), and InControl Remote Web Admin failed on FusionHub with FIPS enabled and Remote Assistance disabled (ref 37674).

LAN and VLAN (5)

• Balance 310 HW5 dropping tagged VLAN multicast with all ports on Trunk Any (ref 37259, originally 8.6.0s033).
• Balance 310 5G HW3 dropping untagged LAN traffic after reboot with VLAN access ports (ref 37299, originally 8.6.0s033).
• Bonjour forwarding advertising client-network services back into the service network (ref 37668, originally 8.6.0s099).
• UDP and Bonjour forwarding failing between VLANs with similar IDs (ref 37746, originally 8.6.0s099).
• DHCP conflict detection recording blank MAC addresses (ref 37439).

Wi-Fi (3)

• Air-monitor settings disappearing on Wi-Fi 6 and Wi-Fi 7 models after upgrading to 8.6.0 (ref 37718). New in 8.6.1.
• Wi-Fi 6 stability when clients roamed between SSIDs on the same radio (ref 37426, originally 8.6.0s034).
• Wi-Fi WAN failing to roam back to a Fast Transition AP after visiting a non-FT AP (ref 37663, originally 8.6.0s079 and s074).

Everything else (15)

• B One and B One Plus crashing after USB reset (ref 35984).
• Docker storage not cleared by factory restore on devices without other MediaFast storage (ref 37728).
• Malformed TAIP LN sentences in GPS forwarding (ref 37436, originally 8.6.0s048).
• Both Balance 1350 EC units becoming HA master after reboot with LACP on SFP (ref 37788).
• InControl 2 showing PoE usage against the wrong port numbers (ref 37263).
• Reboot during QoS initialization (ref 37505, originally 8.6.0s086).
• Excessive memory from repeated GPS SNMP queries (ref 37627, originally 8.6.0s069).
• BR1 Mini unable to form Synergy Mode when the controller kept default admin credentials and LAN IP (ref 37604).
• CLI SSH failing to start after being enabled (ref 37465).
• Heavy client recognition traffic causing repeated InControl disconnects (ref 37214, originally 8.6.0s021).
• Clipped text on the Balance 580X front panel (ref 37514).
• RAMIPS Ethernet ports failing to link at 100 Mbps with Energy Efficient Ethernet enabled (ref 37500).
• MAX Transit Duo Pro showing a WAN port as LAN in Port Settings (ref 37588, originally 8.6.0s058).

Who should install this beta

Install it if:

• You need IPv6 over cellular and your modem product code is on the list above.
• You run Starlink on a vessel or aircraft and need RF inhibit.
• You have been unable to update modem firmware on a BR1 Mini or other RAMIPS router since 8.6.0.
• You are on a Care plan and want Secure DNS, or want to try Synergy Mode without buying licenses.
• You run a lab, a test bench, or a secondary unit and want to help Peplink shake out bugs.

Wait for GA if:

• The router is your only WAN at a production site.
• You use DNS-O-Matic for Dynamic DNS and have not migrated.
• You are on a 5GD or 5GK modem and were hoping for IPv6. It is not in this build.
• You have not read the beta terms.

The counterpoint: what the beta terms actually say

We recommend Peplink hardware to a lot of customers, and we are generally positive on this release. But two things in the Open Beta Program terms deserve a plain reading.

First, there is no formal technical support for beta firmware. Assistance is best-effort from Peplink, other participants or the community forum. If a beta build takes down a site, you are on your own in a way you are not with GA firmware.

Second, section 4 of the terms states that until an official public announcement, beta software, features and specifications are confidential, and participants must refrain from sharing screenshots, performance data or other details with third parties, including on social media or public forums. That clause is broader than most people expect from an “open” beta. It technically covers posting a speed test result on the Peplink forum. We doubt Peplink enforces it that way, and the release notes themselves are publicly hosted, but if your organization has a legal review process for software terms, run it through them before you install.

There is also the question of how much is actually new. By our count, 21 of the 56 line items in these notes were already available as 8.6.0 special builds. If Peplink support has already handed you an s0xx build for a specific problem, 8.6.1 Beta 1 may not contain anything you do not already have.

None of this changes the recommendation. It just means “beta” is doing real work in the name.

5Gstore Take

8.6.1 is a maintenance release with three changes that matter beyond bug fixes: cellular IPv6 for the non-5GD, non-5GK modem lines, Starlink RF inhibit for mobile operators, and the removal of licensing on Synergy Mode. The security items are worth tracking, and we will update this post with CVE numbers if they are published at GA.

If you are trying to figure out whether your specific router and modem combination gets IPv6 in this build, or whether an s0xx special build you already have covers your issue, we can help. Contact us at https://5gstore.com/site/contact_us with your model, hardware revision and product code.

We carry the full Peplink lineup at https://5gstore.com/landing/m/peplink/ and also stock Cradlepoint (https://5gstore.com/landing/m/cradlepoint/), Teltonika (https://5gstore.com/landing/m/teltonika/), Semtech (https://5gstore.com/landing/m/sierra_wireless/), Inseego (https://5gstore.com/landing/m/inseego/), Digi (https://5gstore.com/landing/m/digi/) and Katalyst (https://5gstore.com/landing/m/katalyst/) if Peplink is not the right fit for your deployment.

FAQ

Is Peplink 8.6.1 Beta 1 safe to run in production?
Peplink’s own terms say to refrain from relying on beta firmware in production or mission-critical environments. Run it on a test unit or a secondary router first.

Does 8.6.1 add IPv6 on cellular for all Peplink routers?
No. IPv6 on cellular applies only to modems with product codes LTEA-US, LTEA-K, LTE-E, LTEA-D, GLTE-G, LTEA-Q, LTEA-E, LTEA-R, LTE-EJ, LTE-MX, LTE-MXS and LTE-US. The 5GD and 5GK product codes are not included in this beta.

Where do I download Peplink 8.6.1 Beta 1?
Accept the Open Beta Program terms at https://www.peplink.com/support/downloads/open-beta-program/ and you will be taken to the beta firmware download page.

Do I still need a Care plan for Synergy Mode?
Not in 8.6.1 Beta 1. Both the Care plan and license requirements for Synergy Controllers and synergized devices have been removed.

What security issues does 8.6.1 fix?
Three security advisories: a DHCP client hostname handling vulnerability, a Web Admin access control vulnerability, and vulnerabilities in the management CLI. All apply to all models. Peplink has not published CVE numbers for these at beta stage.

When will 8.6.1 reach general availability?
Peplink does not publish timelines. For reference, 8.6.0 went through two betas and multiple release candidates before GA. Watch the Peplink forum at https://forum.peplink.com for RC announcements.

Can I downgrade from 8.6.1 Beta 1 back to 8.6.0?
Peplink routers keep two firmware partitions, so you can normally boot back to the previous firmware from the System menu. Back up your configuration before upgrading regardless.