We are pleased to announce that Firmware 8.5.4 is now generally available for production environments.
You can download the firmware from the Firmware Download Page or upgrade directly via InControl Firmware Management.
Hello @Lai,
We are unable to find the difference between Firmware 8.5.4 RC1 and the release of Firmware 8.5.4 GA.
Three days does not give the Peplink Community sufficient time to adequately support Peplink in field testing, which contrasts with previous discussions and trends with the Peplink community & Partners.
In a Peplink Partner Community Discussion, this was covered, and Peplink expressed that they would be more vigilant in the release cycle and communications (URL for Peplink Partners
https://forum.peplink.com/t/switch-firmware-2-0-3-ga-announcement-for-partner/57889/6?u=mldowling ).
Please consider withdrawing the GA until fair time is given for the Peplink Community (& your Peplink Partners) to test and address issues found, noting that some have already been reported in the community discussions with 8.5.4 RC1.
Have a good day,
Marcus 
4 Likes
it was a super quick roll-out, i wonder if it was because of the vulnerability? in many cases rc ends up same as ga.
2 Likes
I agree 100%, in particular what about the issue reported against RC1 in ticket#26010096 by @ckirch . It seems unlikely that this would have been addressed since RC1 became GA as is apparently. So why push out to GA a build that has known bugs and has had too short of an RC cycle to fully validate?
2 Likes
This was Waaaaayyy too quick of a firmware release.
Was there like one beta?
3 Likes
I see it similar like @mldowling !
I suggest adding a vulnerability fix to 8.5.3s101 firmware, which is the last working firmware for us.
However as we use the peplink incontrol server we stay with that version as it is hardened against the vulnerability instead of upgrading to the 8.5.4 GA disabling our inter VLAN communication and Bonjour transfers partially.
1 Like
@mldowling @mystery @peparn @ckirch
Firmware version 8.5.4 is primarily released for bug fixes. Unlike other firmware releases that include major feature enhancements and additions, this version focuses on consolidating the major bugs identified and deemed necessary by our valued partners and customers. It serves as a stability improvement update based on firmware version 8.5.3, with an emphasis on resolving key issues.
While it may not include all fixes, it addresses the major bugs related to commonly used features. Many of our valued partners and customers have provided feedback requesting a consolidated release that incorporates the important fixes from version 8.5.3.
For any bug fixes not included in this release, please continue to engage with Peplink Support via support tickets. Our support team will work closely with you to ensure the appropriate firmware is provided for your devices.
3 Likes
Just updated from 8.5.3 to 8.5.4 on two of my balance 380s and now my site-to-site speedfusion vpns won’t establish connections, stuck on ‘starting’ – reverted back to 8.5.3 and it started working again. Seems 8.5.4 needs more bake time…
shaun
1 Like
Hi @sitloongs,
Trusting my years of experience in software development, I can say that no matter how small or large the changes are, a new software release always requires a cool down time to shake out any unintended bugs/consequences to the recently made changes. Software is often more than the sum of its parts when it comes to bugs, and so even if you have just rolled up a number of independently tested bug fixes, putting all the fixes together in a new build will likely have unexpected consequences as shown by the early reports from @ckirch and @Shaun_Coleman (and probably more already). Future will tell, but it would have probably been wise to give that RC1 a few more iterations over at least a week or two to nail it perfectly.
I am in no way criticizing the awesome work that the Peplink team is doing with its products, just sharing bits of hard acquired wisdom, hoping it might help inspire the process for future iterations, and ultimately yield more robust releases that require less special build work to fix issues after the facts 
Cheers!
3 Likes
Indeed – 30yr+ product manager here, (ex RSA, VMware, Citrix, as well as managing a few IPSec and SSL VPNs releases over the years) and I was pretty surprised a core feature such as Speedfusion appears to not have been fully smoke tested before a GA. It is a little concerning… I’ve had good luck with pretty much all z releases of Peplink for more than 10 years until this one. Disappointing…
1 Like
@Shaun_Coleman please submit a ticket as our testlab just has confirmed with B380 running 8.5.4 to be working fine with SpeedFusion. We would need to look deeper on this.
1 Like
Hi Andy,
I have tested 8.5.4 build 6264 version using MAX-BR2-PRO-5GK-T-PRM + SIM Injector Mini on the LAN.
Check if RemoteSIM Proxy is enabled on BR2 Pro under support.cgi menu:
If yes, please open a ticket for support team to investigate.
1 Like
Hello Peplink Team (@Lai, @sitloongs, @Saulius_Saltmeris & @Eddy_Yeung),
We have seen Firmware 8.5.4 break the ability to use InTouch for entire sites using the MAX Transit, Hardware Revision #2.
Rolling back to 8.5.3 GA has restored all InTouch functionality at these sites.
Please see Peplink Ticket #26020300 for supportive diagnostic files while on 8.5.4 before rolling back.
Have a Good Lunar New Year,
Marcus
@mldowling , I just saw your update in the ticket. I will check on it and provide update.
1 Like
The InTouch issue has been identified. It is related to how IC2 handles devices running firmware version 8.5.4.
The IC2 team is working on a fix, and I will provide an update once the issue has been resolved on the IC2 cloud side .
This issue is not related to the firmware 8.5.4 itself.
1 Like
Update :
The IC2 Cloud Engineering team has just confirmed that the InTouch access issue for devices running firmware version 8.5.4 has been resolved.
2 Likes
Hello @sitloongs,
I can confirm the InControl2 fix to work with InTouch for Firmware 8.5.4 is now working with the Peplink MAX Transit series. Thanks for the rapid response.
The fix for InControl2 regarding 8.5.4 supports our case as to why the firmware should have been left as a “Release Candidate” for more than 3 Days to allow for proper Peplink Community field testing ( our previous comment in this thread ).
Have a good Lunar New Year,
Marcus
4 Likes