Major Problems with PEPLINK 580

We are having MAJOR problems with the PEPLINKS 580’s at the corporate office. And since peplink is forcing communication through the purchase vendor and are not helping directly… And since the Vendor can not resolve the issue in a timely manor.

I am hoping this will inspire peplink to contact me directly to resolve the issue, as if this is not resolved I will be looking for another router vendor. When I call for support I expect support to resolution not to be handed off to the purchase vendor.

Primary Issue:

  1. Peplink is rebooting several times a day
  2. at least a few times a week the web interface stalls
  3. Voip failures build up until 1 and or 2 occurs.

We have Roughly 24 peplinks in my network and the 580 at the corporate hq is the only one that keeps crashing.
I have 2 580’s at HQ and get the same result on both PEPLINKS.

Peplink Reolutions Required in future updates:

  1. Complete configuration available from telnet as backup and diagnostics as alternative interface for web interface failures.

This will also resolve the issue of configuring firewalls and network scripting.
2) The configuration file needs to be text readable when downloaded for configuration specs.

@Michael_George, if your certified reseller was unable to resolve your issue they should have opened a support ticket with us as an escalation. Can you let me know what your ticket number is?

If you are unsure or don’t have one yet please do open a support case with us here and we will help get to the bottom of it:


1 Like

Ticket: 771021

The unit crashed its interface and VPN routing. Had to do a hard reboot again. I really need this to stop and have an explanation why this is happening. Please.

The Balance 580 was up for 15 hours now after you upgraded the provided firmware. We will keep monitor on this unit. Thanks for your patience.

1 Like

yes, so far the balance is holding for almost 6 days.

after 6 days I usually find an error requiring the peplink to be rebooted to fix.
I need more visibility in the routing tables and tracking incoming packets.
It appears the peplink is still erroring, also we can not get the radius authentication to work.
It is imperative that we get the radius authentication to work asap.
I require direct support on this issue asap. Today as an example the router broke the external exchange and skype for business for mobile apps due to invalid nat routing.
The peplink was configured correctly, however, the NAT routing pointed to the wrong server until the device was rebooted.