“Hello, when I got the Surf Soho mk3 when it came out I loved it. Now for awhile it has been freezing up multiple times a week. I looked up how to schedule reboots and had it reboot weekly. That didn’t help much. Then I set it to reboot daily. Still coming home to no wifi multiple times a week. After searching this forum I learned how to set up scheduled rebooting but I didn’t find any other remedy. I like all the security features it has and I was gonna wait for another firmware update but I’ve lost my patience. Please help. Thank you!”
I posted this back in January 2019 before i updated to the latest firmware update. The issues seemed to be fixed by the firmware for a few weeks but now i’m experiencing the same problems as before. Just an hour ago my wifi dropped so I unplugged/ replugged power only to have it freeze again just a few minutes ago. Downright infuriating. Please help.
Please identify whether this is related to Wifi interference or device hangs. Please connect your laptop directly to the LAN port of MK3 when the problem occurs. The laptop managed to grab IP and access web admin of MK3?
I had the same issue twice today.
I have a wired modem/hotspot on the ethernet WAN uplink two cellular hotspots connected WiFi-as-WAN, local WiFi distributed by the Peplink with several wireless devices connecting, and a wired device on the LAN side. I also have a wireless device that connects directly to the same wired modem/hotspot, bypassing the Peplink.
Twice I noticed WiFi had dropped out, and I could not connect to the dashboard from either a wireless or the wired device. The wireless device connecting directly to the modem/hotspot still had service in both instances. In the first case, I power-cycled the Peplink and service was restored to the Peplink-connected devices. In the second case, I waited approx. 5 minutes and local WiFi service came back automatically, but the dashboard was reporting no cable connected on the ethernet WAN port. I had to power cycle again to restore WAN service.
Firmware version 8.3.0
logs for the relevant time period:
Jun 06 13:10:54 WAN: Wi-Fi WAN 5 GHz (Priority 2) standby (redacted)
Jun 06 13:10:54 WAN: WAN (Priority 1) connected (redacted)
Jun 06 13:07:27 System: Time synchronization successful (0.pepwave.pool.ntp.org)
Dec 31 18:04:00 WAN: Wi-Fi WAN 5 GHz (Priority 2) connected to redacted (redacted)
Dec 31 18:04:00 WAN: Wi-Fi WAN 2.4 GHz (Priority 3) standby (redacted)
Dec 31 18:03:23 Admin: admin (redacted) login successful
Dec 31 18:02:57 System: Wi-Fi AP Normal Mode
Dec 31 18:01:56 System: Time synchronization fail
Dec 31 18:01:25 System: Started up (8.3.0 build 5122)
Jun 06 12:49:37 WAN: Wi-Fi WAN 2.4 GHz (Priority 3) standby (redacted)
Jun 06 12:47:28 WAN: Wi-Fi WAN 2.4 GHz (Priority 3) disconnected
Jun 06 09:56:53 Admin: admin (redacted) login successful
Jun 06 09:52:50 WAN: Wi-Fi WAN 2.4 GHz (Priority 3) standby (redacted)
Jun 06 09:52:35 WAN: Wi-Fi WAN 5 GHz (Priority 2) standby (redacted)
Jun 06 09:52:28 System: Time synchronization successful (0.pepwave.pool.ntp.org)
Dec 31 18:03:11 WAN: WAN (Priority 1) connected (redacted)
Dec 31 18:03:03 System: Wi-Fi AP Normal Mode
Dec 31 18:02:04 System: Time synchronization fail
Dec 31 18:01:30 System: Started up (8.3.0 build 5122)
Jun 06 09:44:25 WAN: Wi-Fi WAN 2.4 GHz (Priority 3) disconnected
Jun 06 06:54:20 WAN: Wi-Fi WAN 2.4 GHz (Priority 3) standby (redacted)
It appears to me that the Peplink simply crashed. I don’t think I’ve ever seen it happen before.
Let me know if there’s anything else I can do to diagnose.
UPDATE: same thing has happened again a few times in the last few days.
Also, what’s up with the date/time getting reset every time the Mk3 starts up? Is there a replaceable CMOS battery in this unit?