EAP110 outdoor frequent connection drops / no SSID broadcasted anymore
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.EAP110 outdoor frequent connection drops / no SSID broadcasted anymore
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have 4 EAP110 together with Omada Controller.
A few times a day my smartphone suddenly has either no connection anymore or it connects with a very weak signal to another AP located further away. When opening Wifi result page of my smartphone, I don't see any networks for quite some time. It is definitely not a problem with the smartphone, because also another phone right beside has the same problem.
It seems the EAP hangs for a few seconds and thus leading to no connection at all. Before I had EAP 110 outdoor v1 and EAP115 and both worked flawlessly, without any interventions.
Since EAP 110 outdoor I have massive problems. I've tried a lot, like rebooting, changing beacon interval (which lead to frequent reboots of the EAPs), enabling fast roaming and so on. But nothing helped. Problem still persists and I'm quite desperate now. I was a huge fan of TP Link EAPs due to its price and quality, but something seems to be wrong with EAP 110 outdoor.
In the LAN details I see on all APs Rx Dropped Packets, which is quite confusing, because shortest cable length is 3 Meters and all other network devices have no problem. Also the EAPs are connected to the same LAN cables like the working older EAPs were before. I suppose that when EAP has this glitches, when no SSIDs are broadcasted it also drops Rx packets.
Hope you can help me. I'd really like to have a reliable WiFi again.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Channels are fixed and 2,4 GHz only. EAP 110 outdoor has no 5 GHz support
- Copy Link
- Report Inappropriate Content
When using a Wifi with Fritzbox 7590 it is stable for days without any drop of Wifi connection. Thats the way it should be. Please help me to do this with Eap 110 Outdoor, too.
- Copy Link
- Report Inappropriate Content
I suggest you reset the EAP by pressing the reset hole. After resetting, do not configure anything, even the SSID and password, just connecting to the default unsecured SSID and check if the issue still exists. If no, you can configure those features back one by one and observer the performance step by step, check if it is certain feature result the issue.
Besides, is there any electric appliance in your environment? Most electric appliances work on 2.4G channel. They may affect the performance of the EAP. You can use wifi analysis tool to select a better channel, and narrow the channel width down to 20M to reduce interference.
- Copy Link
- Report Inappropriate Content
I did a soft reset and added one SSID by one except that one with an access control rule, because I didn't see an option for access control rules in standalone mode.
There are no connection drops with this manuall configured AP.
Then I have disabled access control rule on Omada Controller, so SSID is still sent but without access control rule.
The first connection drops already occured again.
The problem also exists when Omada Controller software is stopped.
So it seems there is some kind of problem how Omada Controller configures the EAP110 outdoor. Omada controller version used is v 4.4.4
- Copy Link
- Report Inappropriate Content
It seems the more SSIDs and the more clients are connected to an AP, the more often the connection problems occur.
On the test AP I habe one connection drop within the last 11 hours. On the APs managed by Omada Controller I have 19 connection drops within the last 11 hours on AP1. On AP2 I have even 41 (!) connection drops within the last 11 hours. AP2 has more clients than AP1.
Are there official TP-Link representatives in this forum to help?
- Copy Link
- Report Inappropriate Content
Dear @Connectionloss,
Connectionloss wrote
It seems the more SSIDs and the more clients are connected to an AP, the more often the connection problems occur.
On the test AP I habe one connection drop within the last 11 hours. On the APs managed by Omada Controller I have 19 connection drops within the last 11 hours on AP1. On AP2 I have even 41 (!) connection drops within the last 11 hours. AP2 has more clients than AP1.
For your case, I'd like to escalate to the TP-Link support team who could help you more efficiently.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Once the issue is addressed or resolved, I'd encourage you to share it with the community.
Thank you so much for your cooperation and support!
- Copy Link
- Report Inappropriate Content
So we're still solving the trouble.
With ssh access the problem could be traced down via dmesg.
ACKTIMEOUT call ath_internal_reset begin leads to a connection drop.
Still figuring out if "ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)" also leads to a connection drop.
Just wanted to have this documentated here if other users with EAP 110 v3 outdoor have similiar problems.
Following is the log of about the last 5 days of one of the EAPs. So there are more than 14 connection drops per day.
dmesg | grep -i ath
[ 24.916000] br0: port 3(ath0) entering forwarding state
[ 259.416000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[ 6111.108000] ACKTIMEOUT call ath_internal_reset begin
[ 6111.120000] ACKTIMEOUT call ath_internal_reset end
[23598.624000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[23600.724000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[31306.384000] ACKTIMEOUT call ath_internal_reset begin
[31306.396000] ACKTIMEOUT call ath_internal_reset end
[34306.560000] ACKTIMEOUT call ath_internal_reset begin
[34306.572000] ACKTIMEOUT call ath_internal_reset end
[38447.508000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[42803.016000] ACKTIMEOUT call ath_internal_reset begin
[42803.028000] ACKTIMEOUT call ath_internal_reset end
[64308.104000] ACKTIMEOUT call ath_internal_reset begin
[64308.116000] ACKTIMEOUT call ath_internal_reset end
[95274.484000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[108668.332000] ACKTIMEOUT call ath_internal_reset begin
[108668.344000] ACKTIMEOUT call ath_internal_reset end
[110042.424000] ACKTIMEOUT call ath_internal_reset begin
[110042.436000] ACKTIMEOUT call ath_internal_reset end
[129153.404000] ACKTIMEOUT call ath_internal_reset begin
[129153.416000] ACKTIMEOUT call ath_internal_reset end
[131541.548000] ACKTIMEOUT call ath_internal_reset begin
[131541.560000] ACKTIMEOUT call ath_internal_reset end
[131721.584000] ACKTIMEOUT call ath_internal_reset begin
[131721.596000] ACKTIMEOUT call ath_internal_reset end
[133065.676000] ACKTIMEOUT call ath_internal_reset begin
[133065.688000] ACKTIMEOUT call ath_internal_reset end
[137475.932000] ACKTIMEOUT call ath_internal_reset begin
[137475.944000] ACKTIMEOUT call ath_internal_reset end
[143386.252000] ACKTIMEOUT call ath_internal_reset begin
[143386.264000] ACKTIMEOUT call ath_internal_reset end
[143476.284000] ACKTIMEOUT call ath_internal_reset begin
[143476.296000] ACKTIMEOUT call ath_internal_reset end
[152857.580000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[153706.820000] ACKTIMEOUT call ath_internal_reset begin
[153706.832000] ACKTIMEOUT call ath_internal_reset end
[166517.496000] ACKTIMEOUT call ath_internal_reset begin
[166517.508000] ACKTIMEOUT call ath_internal_reset end
[172673.832000] ACKTIMEOUT call ath_internal_reset begin
[172673.844000] ACKTIMEOUT call ath_internal_reset end
[175914.016000] ACKTIMEOUT call ath_internal_reset begin
[175914.028000] ACKTIMEOUT call ath_internal_reset end
[176088.052000] ACKTIMEOUT call ath_internal_reset begin
[176088.064000] ACKTIMEOUT call ath_internal_reset end
[177114.128000] ACKTIMEOUT call ath_internal_reset begin
[177114.140000] ACKTIMEOUT call ath_internal_reset end
[195709.080000] ACKTIMEOUT call ath_internal_reset begin
[195709.088000] ACKTIMEOUT call ath_internal_reset end
[205482.564000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[210709.860000] ACKTIMEOUT call ath_internal_reset begin
[210709.872000] ACKTIMEOUT call ath_internal_reset end
[213080.004000] ACKTIMEOUT call ath_internal_reset begin
[213080.016000] ACKTIMEOUT call ath_internal_reset end
[219535.760000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[223286.544000] ACKTIMEOUT call ath_internal_reset begin
[223286.556000] ACKTIMEOUT call ath_internal_reset end
[228848.848000] ACKTIMEOUT call ath_internal_reset begin
[228848.860000] ACKTIMEOUT call ath_internal_reset end
[229082.888000] ACKTIMEOUT call ath_internal_reset begin
[229082.900000] ACKTIMEOUT call ath_internal_reset end
[229179.224000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[230108.968000] ACKTIMEOUT call ath_internal_reset begin
[230108.980000] ACKTIMEOUT call ath_internal_reset end
[230435.316000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[231674.288000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[231771.080000] ACKTIMEOUT call ath_internal_reset begin
[231771.092000] ACKTIMEOUT call ath_internal_reset end
[244887.768000] ACKTIMEOUT call ath_internal_reset begin
[244887.784000] ACKTIMEOUT call ath_internal_reset end
[252082.152000] ACKTIMEOUT call ath_internal_reset begin
[252082.164000] ACKTIMEOUT call ath_internal_reset end
[259866.312000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260440.020000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260440.660000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260441.340000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260441.952000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260442.568000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260443.184000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260443.900000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260444.516000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260447.704000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260448.456000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260449.868000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260454.960000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260457.560000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260458.776000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260463.052000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260463.664000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260464.536000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260465.200000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260465.816000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[260466.432000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[265294.820000] ACKTIMEOUT call ath_internal_reset begin
[265294.832000] ACKTIMEOUT call ath_internal_reset end
[265792.872000] ACKTIMEOUT call ath_internal_reset begin
[265792.884000] ACKTIMEOUT call ath_internal_reset end
[270443.128000] ACKTIMEOUT call ath_internal_reset begin
[270443.140000] ACKTIMEOUT call ath_internal_reset end
[283295.788000] ACKTIMEOUT call ath_internal_reset begin
[283295.800000] ACKTIMEOUT call ath_internal_reset end
[296298.460000] ACKTIMEOUT call ath_internal_reset begin
[296298.472000] ACKTIMEOUT call ath_internal_reset end
[296653.108000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[299730.660000] ACKTIMEOUT call ath_internal_reset begin
[299730.672000] ACKTIMEOUT call ath_internal_reset end
[299838.692000] ACKTIMEOUT call ath_internal_reset begin
[299838.704000] ACKTIMEOUT call ath_internal_reset end
[304896.976000] ACKTIMEOUT call ath_internal_reset begin
[304896.988000] ACKTIMEOUT call ath_internal_reset end
[307326.836000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[309049.620000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[310111.324000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[310385.656000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[310641.236000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[313490.172000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[313492.940000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[317701.640000] ACKTIMEOUT call ath_internal_reset begin
[317701.652000] ACKTIMEOUT call ath_internal_reset end
[330710.308000] ACKTIMEOUT call ath_internal_reset begin
[330710.320000] ACKTIMEOUT call ath_internal_reset end
[343760.988000] ACKTIMEOUT call ath_internal_reset begin
[343760.996000] ACKTIMEOUT call ath_internal_reset end
[346128.152000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[347973.216000] ACKTIMEOUT call ath_internal_reset begin
[347973.228000] ACKTIMEOUT call ath_internal_reset end
[351465.412000] ACKTIMEOUT call ath_internal_reset begin
[351465.424000] ACKTIMEOUT call ath_internal_reset end
[354705.600000] ACKTIMEOUT call ath_internal_reset begin
[354705.612000] ACKTIMEOUT call ath_internal_reset end
[359505.868000] ACKTIMEOUT call ath_internal_reset begin
[359505.876000] ACKTIMEOUT call ath_internal_reset end
[364594.132000] ACKTIMEOUT call ath_internal_reset begin
[364594.144000] ACKTIMEOUT call ath_internal_reset end
[386546.440000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[388487.340000] ACKTIMEOUT call ath_internal_reset begin
[388487.352000] ACKTIMEOUT call ath_internal_reset end
[390707.480000] ACKTIMEOUT call ath_internal_reset begin
[390707.492000] ACKTIMEOUT call ath_internal_reset end
[399365.932000] ACKTIMEOUT call ath_internal_reset begin
[399365.944000] ACKTIMEOUT call ath_internal_reset end
[399485.964000] ACKTIMEOUT call ath_internal_reset begin
[399485.976000] ACKTIMEOUT call ath_internal_reset end
[405108.272000] ACKTIMEOUT call ath_internal_reset begin
[405108.284000] ACKTIMEOUT call ath_internal_reset end
[405426.316000] ACKTIMEOUT call ath_internal_reset begin
[405426.328000] ACKTIMEOUT call ath_internal_reset end
[408108.528000] ACKTIMEOUT call ath_internal_reset begin
[408108.540000] ACKTIMEOUT call ath_internal_reset end
[409908.644000] ACKTIMEOUT call ath_internal_reset begin
[409908.656000] ACKTIMEOUT call ath_internal_reset end
[420709.212000] ACKTIMEOUT call ath_internal_reset begin
[420709.224000] ACKTIMEOUT call ath_internal_reset end
[425161.460000] ACKTIMEOUT call ath_internal_reset begin
[425161.472000] ACKTIMEOUT call ath_internal_reset end
[425509.504000] ACKTIMEOUT call ath_internal_reset begin
[425509.516000] ACKTIMEOUT call ath_internal_reset end
[429541.728000] ACKTIMEOUT call ath_internal_reset begin
[429541.740000] ACKTIMEOUT call ath_internal_reset end
[430909.820000] ACKTIMEOUT call ath_internal_reset begin
[430909.832000] ACKTIMEOUT call ath_internal_reset end
[432079.908000] ACKTIMEOUT call ath_internal_reset begin
[432079.920000] ACKTIMEOUT call ath_internal_reset end
[439836.868000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[444110.516000] ACKTIMEOUT call ath_internal_reset begin
[444110.528000] ACKTIMEOUT call ath_internal_reset end
[467505.692000] ACKTIMEOUT call ath_internal_reset begin
[467505.700000] ACKTIMEOUT call ath_internal_reset end
[469864.512000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[485241.576000] ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 45)
[489682.796000] ACKTIMEOUT call ath_internal_reset begin
[489682.808000] ACKTIMEOUT call ath_internal_reset end
[493985.032000] ACKTIMEOUT call ath_internal_reset begin
[493985.044000] ACKTIMEOUT call ath_internal_reset end
[494507.080000] ACKTIMEOUT call ath_internal_reset begin
[494507.092000] ACKTIMEOUT call ath_internal_reset end
[498095.288000] ACKTIMEOUT call ath_internal_reset begin
[498095.300000] ACKTIMEOUT call ath_internal_reset end
[498707.344000] ACKTIMEOUT call ath_internal_reset begin
[498707.356000] ACKTIMEOUT call ath_internal_reset end
[499775.432000] ACKTIMEOUT call ath_internal_reset begin
[499775.444000] ACKTIMEOUT call ath_internal_reset end
[502475.596000] ACKTIMEOUT call ath_internal_reset begin
[502475.608000] ACKTIMEOUT call ath_internal_reset end
[504755.736000] ACKTIMEOUT call ath_internal_reset begin
[504755.748000] ACKTIMEOUT call ath_internal_reset end
[506735.856000] ACKTIMEOUT call ath_internal_reset begin
[506735.868000] ACKTIMEOUT call ath_internal_reset end
[509538.028000] ACKTIMEOUT call ath_internal_reset begin
[509538.040000] ACKTIMEOUT call ath_internal_reset end
- Copy Link
- Report Inappropriate Content
For the readers with same problem: TP-Link provided me with a beta firmware, which is not perfect, but far better than the latest firmware. So hopefully there is soon an official release.
- Copy Link
- Report Inappropriate Content
For the reader: Problem still exists. Until finally solved I recommend not buying EAP-110 outdoor v3. It causes me a lot of trouble and connection issues.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4231
Replies: 15
Voters 0
No one has voted for it yet.