I have a Balance One with an AP One Enterprise running two Wifi networks. This is a new setup that has been running more or less smoothly for a couple of weeks. The Balance One is running a PepVPN link to a Surf SOHO at another site. Twice in the past three days, the Wifi has locked up to where devices lose their connection to the network and while the Wifi still appears to be out there, if you try to reconnect, the AP reports that the password is incorrect. In both cases, the only solution was to reboot the AP One and then everything is instantly back to normal and all devices reconnect automatically. I am not positive that every single device is kicked off the network, but it is certainly true for most. Tonight, I came home to find all of the IOT devices in distress (having been in that condition for six hours). I could not get to them to reconnect, but my phone which came in the door with me was perfectly happy. Again, the reboot solved the problem. I welcome any suggestions! Thanks.
What firmware are you running on the AP? There were numerous firmware updates, many of which were not successful (I’m being polite). The current firmware is good. I’m running 3.6.0 Package ID 1158 which I believe is the most recent.
I’m running 3.6.0 as well. I upgraded shortly after the install. Thanks!
Another thing that might shed some light on this problem is that the AP seems to continually disconnect and reconnect devices. I see nothing in the event log to explain what happens when it locks up, but the log is full of lines like this:
|Oct 03 11:18:50||2935-75E8-7F74: Client C4:9D:ED:19:78:5E disassociated from Emerald|
|Oct 03 09:40:20||2935-75E8-7F74: Client A4:F1:E8:AE:93:86 associated with Emerald|
|Oct 03 09:38:50||2935-75E8-7F74: Client A4:F1:E8:AE:93:86 disassociated from Emerald|
|Oct 03 09:38:21||2935-75E8-7F74: Client 34:12:98:58:74:18 associated with Emerald|
|Oct 03 09:38:20||2935-75E8-7F74: Client 34:12:98:58:74:18 disassociated from Emerald|
|Oct 03 09:28:19||2935-75E8-7F74: Client A4:F1:E8:AE:93:86 associated with Emerald|
|Oct 03 09:27:09||2935-75E8-7F74: Client 34:12:98:58:74:18 associated with Emerald|
|Oct 03 09:27:09||2935-75E8-7F74: Client 34:12:98:58:74:18 disassociated from Emerald|
|Oct 03 09:26:50||2935-75E8-7F74: Client A4:F1:E8:AE:93:86 disassociated from Emerald|
|Oct 03 08:58:20||2935-75E8-7F74: Client E0:33:8E:27:F6:29 disassociated from Emerald|
|Oct 03 08:50:50||2935-75E8-7F74: Client E0:33:8E:27:F6:29 associated with Emerald|
|Oct 03 08:50:50||2935-75E8-7F74: Client E0:33:8E:27:F6:29 disassociated from Emerald|
This clip is just showing one of the SSIDs, but both appear in the log. More often than not, the device is disassociated and then immediately re-associated. There are hundreds of entries per day.
@chklee, the log shows that the clients disassociated themselves from the AP, not AP disassociate the clients. This is different from the issue reported in your first post since the clients able to reassociate back to the AP.
For the reported issue 1 (client disconnected to AP but failed to reconnect. Reboot AP solved the issue), I need your favor below
- Please check how many APs with the same SSID can be scanned by the clients in the affected environment. I just want to ensure AP One Enterprise the only AP for the client to connect to.
- Provide the date and time when the problem occurs.
- Provide the MAC address of the affected clients.
- Download Diagnostic Report from the AP One Enterprise.
For the reported issue 2 (Clients associate/disassociate from AP One Enterprise), it could be caused by poor Wifi signal strength received by clients, clients roam between AP due to 2 or more APs with strong signal strength in the environment, power saving mode from the client’s wifi adapter and etc. On-site Wifi survey is the best approach to rule out the reported issue. You may need to get help from the local Peplink partner.
I can understand that the clients disassociating themselves may not be the same problem, but it is unique to the AP One and is happening with immense frequency. It did not happen when I had the SURF Soho at this location and it does not happen at the other site where I have the same client devices. Importantly, every type of device on the network is reflected in the log. I see IOT devices like NEST thermostats and WEMO devices. I also see windows and Mac devices as well as IOS devices. It happens on both the base network (Emerald) and the guest/IOT network (Blue). I tried to upload the diagnostic report, but this forum does not appear to allow that file type, so I just added a TXT to the end of itAP_Log.txt (129.6 KB)
20181004_aponeenterprise_293575E87F74_diag.report.txt (177.2 KB)
. I am also attaching a text version of the AP Event log.
In terms of WIFI strength, I don’t follow how that would be a problem causing the AP to lock up. I am in a suburban area with a handful of weak detected SSIDs none of which conflict with this one. My SSIDs Emerald is served only through this AP One. The whole idea behind the AP One was to focus on one, professional grade access point to control my network. I have no other access points working here, so my Wifi environment is clean. Over the years I have had many Wifi configurations at this site and have never seen clients dropping connections and I have never had a router or access point that needed to be rebooted. So with all of that being said, I remain convinced the problem here is with the AP One (or the Balance). Those are the only new variables in my system. Either I have configured one of these improperly, or the device is defective. Sadly, I am leaning increasingly toward the latter because no one seems to be coming to the table with alternative suggestions. I can’t see spending more money (and my time) bringing someone in to survey my site when I know that all I have to do is reinstall my Asus router and discard the AP One. I will lose the seamless VLAN control and $250, but that may be the price I have to pay to move on.
So, I came home to find that once again the AP has locked up. This time it is exclusively the Guest network. The base network is still working fine. The event log clearly shows all devices being shed at one time:
|Oct 04 14:26:50||Client 18:B4:30:05:95:C2 disassociated from Blue|
|Oct 04 14:26:50||Client 18:B4:30:01:54:32 disassociated from Blue|
|Oct 04 14:26:50||Client 44:65:0D:B4:78:A8 disassociated from Blue|
|Oct 04 14:26:50||Client 18:B4:30:12:D7:92 disassociated from Blue|
|Oct 04 14:26:50||Client 18:B4:30:12:FB:7E disassociated from Blue|
|Oct 04 14:26:50||Client 58:EF:68:DA:F9:B5 disassociated from Blue|
|Oct 04 14:26:50||Client 94:10:3E:B5:E1:11 disassociated from Blue|
|Oct 04 14:26:50||Client 58:EF:68:DB:08:19 disassociated from Blue|
|Oct 04 14:26:50||Client 14:91:82:D8:C3:7F disassociated from Blue|
|Oct 04 14:26:50||Client 60:38:E0:49:E6:35 disassociated from Blue|
|Oct 04 14:26:50||Client 58:EF:68:F6:03:B9 disassociated from Blue|
|Oct 04 14:26:50||Client 18:B4:30:08:62:E5 disassociated from Blue|
|Oct 04 14:26:50||Client 58:EF:68:BB:56:19 disassociated from Blue|
|Oct 04 14:26:50||Client 58:EF:68:F8:D3:3D disassociated from Blue|
|Oct 04 13:47:04||Client 60:38:E0:49:E6:35 associated with Blue|
I believe this confirms that it is the AP that is “disassociating” the devices rather than the other way around. Does anyone understand a formal process for getting tech support from Peplink? When I sent an inquiry to the 3G Store where I bought this equipment, it fell on deaf ears. Thanks in advance.
Normally, you should contact your purchase point for help as they are the local representative for us. Seem you can’t get anything from them, please open a support ticket here for support team to check.
Thank you. That is super helpful!
Please include the forum link into the support ticket so that support team aware on the request.
I have the same problem. My devices lose their connection and when i try to connect again, i see the password error some times or some times not, but I cant connect to wifi , while I entered the correct password. I have a BP One Core and 3 AP One Enterprise and the firmware is up to date.