I recently upgraded to Firmware v 8.5.2 Build 5581 (using the Check for New Firmware option within the Web Admin Interface, ie I did NOT do a manual update by downloading the file separately and selecting it in the Web Admin Interface). Since then I have experienced multiple issues:
-
B20X reboots on its own at apparently random intervals anywhere from 17-138 hours after the last startup (without any admin/user intervention). This has happened 4 times in 10 days
-
I use a schedule to turn on/off Wi-Fi AP SSIDs at certain times. While the Device Event Log shows the expected line entries at the correct time of “Schedule: [ScheduleName] turned off [SSIDx]”, the Wi-Fi AP SSIDs were NOT turned off and remained active. There was also a missing line entry “System: Changes applied (schedule)” in the Device Event Log immediately after the expected “Schedule” line entries, which explains why the SSIDs were not turned off. This happened the first time after the firmware upgrade but has not happened again
-
when connecting an ethernet cable to a LAN port to log in to the Web Admin Interface from a computer, the Device Event Log was MISSING the usual line entry “Port: Port (LAN Port) status changed (link up, speed 1 Gbps Full Duplex)” that is always captured. Next, when in the browser connecting to the correct router IP address/port in order to log in to the Web Admin Interface, I received an error page “500 Internal Server Error nginx”. I have never seen that page before when accessing the Web Admin Interface login page and in order to get around it I had to manually unplug the router and power it down and then back up again to be able to log in to the Web Admin Interface successfully (where I confirmed the missing “Port” line entry I referenced at the beginning of this point #3)
-
after this manual reboot (unplugging and powering up again), a client device failed to connect to one of the router’s Wi-Fi AP SSIDs and simply gave an “unknown error” message in the OS and refused to connect. However, on that client device I could connect to another Wi-Fi AP SSID broadcast by the router and once I had done so, I disconnected from that SSID and then was able to connect successfully to the first SSID (which had previously been unable to connect with the “unknown error” message)
I do not use InControl and the router is set to allow Admin Access from local LAN only. It is locked down in line with Michael Horowitz’s Router Security website advice (albeit he gives it for the Surf SOHO).
Post firmware upgrage, the behavior suggests that there are either lots of bugs here or, more ominously, that the router has been hacked (maybe in the the firmware upgrade?). #3 above is especially worrying.
For now, I have rebooted back to the previous v 8.5.1 Build 5531 firmware and am running that on the router, but frankly I have concerns about the integrity of the router given what I have observed.
I am unable to see any signs of compromise by inspecting the Device Event Log. I am unable to view the Diagnostic Report I have downloaded (as other Peplink users have previously posted about).
Have others experienced any similar issues following the v 8.5.2 Build 5581 firmware upgrade? I saw on the Forum that one of the earlier Release Candidate versions of this firmware version had problems with the router rebooting on its own (my #1 above).
Cheers
Charlie