@Michael234, yes the special firmware is needed when you have a problem upgrading
the MK3 to 8.1.0.
Thank you.
I have two Surf SOHO Mk3 which are in InControl and repeatedly fail the update from 8.0 to 8.1 . When I got a third Surf SOHO Mk3, I did not put it in InControl and it updated to 8.1.0 on the first try.
Since the first two units are still failing the update, should I use the special firmware mentioned above, or is there a newer one?
Thanks.
Great. Thanks! I’m not sure if I can do this today, but I’ll let you know how it goes when I get there.
Cheers.
I downloaded the file from the link above, and tried to do the upgrade via InControl2 → Settings → Remote Web Admin → System → Firmware.
I selected the file and clicked Manual Upgrade.
The progress bar went across and I got a box with:
JavaScript from “2937-e4bd-990c-ic.rwa10.peplink.com”
Error 504 : error
What should I do next?
OK. I submitted a ticket. Thank you for that link!
How I got firmware 8.1.0 working on my Surf Soho MK IIi :
First I logged directly into the router (I.e. not using InControl to eliminate a variable / layer of complexity) and rolled the firmware back to 8.0.2.
Contacted 5gstore, who filed a ticket on my behalf ( #57445206 ) in hopes of being able to fix my situation without having to factory reset and spend an entire day reconfiguring all of my settings, firewall rules, etc (really wish you could do those via ssh or imported csv file but I understand it’s way way more router capabilities for $200 spent 3 years ago than anything else out there, that’s for sure)
Did a number of combinations of manually uploaded FW upgrades & testing as they suggested using both factory defaults and my previous config file.
In the end the most time consuming solution has been reliable, and I’ve been running FW 8.1.0 for the last couple of months w/o any problems, thankfully:
(All of these steps were taken while being directly logged into the router and not using InControl…I used InControl to upgrade to FW 8 the first time so I wanted to avoid using it for firmware upgrades this time)…
- print to PDFs every single router settings page
- manually upload and reinstall 7.x.x firmware
- power cycle
- factory reset & keep factory default config settings
- power cycle
- manually upload and reinstall 8.1.0 firmware
- power cycle
- go through the long process of manually rebuilding my config using the PDFs I saved, but this time, because I already had the max number of VLANS in use (16), 4 WiFi SSID’s, a trunk port connected to a managed switch, intrusion detection enabled, InControl enabled and doing whatever it does in the background to make it work with the platform, and a LOT of firewall rules (outgoing & internal) on top of all that:
I realized that while it’s really great that you’ve added so many more options over the years to use instead of making them exclusively available on more expensive models, I imagine as a company this is a double-edged sword by making so many options available to the SoHo because while customers would like to be able to use as many of the features that you offer all at once, the router’s particular processor and memory naturally must be proportional to the low cost of the unit.
So therefore I can reasonably expect to be able to use only so many features at once.
Consequently this time I did NOT try to also use the content blocking, content prioritization, some of the newer firewall features found under the AP section, using an external logging server, and I also largely reduced the firewall logging overall (that last one was a little harder to give up, personally) - back up config and power cycle
Everything has been just as stable as it was under FW 7.x.x, I’m happy to say.
No hard feelings, of course.
No company has a 100% perfect development & deployment history, and the last 3 years of service I’ve gotten from Peplink at an incredibly low cost has been highly reliable otherwise.
This was your biggest firmware development effort and deployment since everything around the world went crazy with COVID.
And I know as much as anyone that how much of an exhausting disruptor it has been to suddenly move to doing highly coordinated software development, testing, and deployment, + infrastructure dev work, etc from home, and that greatly increased the degree of complexity logistically, which inevitably raised the probability of errors in a major release like firmware 8 is.
I’m impressed you’ve been able to get squeeze as much additional functionality into the SoHo as you have and continue to do.
Keep up the good work!
1 Like
Yay! I got a reply to my ticket within a few hours. The reply had a link to the very same file that had failed and thrown the nondescript Error 504 : error . But I figured I would download it and try it. And I used the Remote Web Admin in InControl to do a Manual Upgrade - just like I had done before. But this time it worked. Weird. But the double weird thing was that my laptop went weird, the networking stack went goofy and other things quit working. Fortunately, a reboot and then a shutdown and reboot solved the weirdness on my laptop, and the Surf SOHO is still working too.
Cheers!