Business Community > WiFi > OC300-EAP225, 2 AP-s are disconnect a lot of time...
< WiFi

OC300-EAP225, 2 AP-s are disconnect a lot of time...

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

OC300-EAP225, 2 AP-s are disconnect a lot of time...

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
OC300-EAP225, 2 AP-s are disconnect a lot of time...
OC300-EAP225, 2 AP-s are disconnect a lot of time...
2022-01-31 08:33:10 - last edited 2022-01-31 08:34:51
Model: EAP225  
Hardware Version: V3
Firmware Version: 5.0.7 Build 20211026 Rel. 33125

Hy Everyone!

 

We have an Omada system with 19x EAP225 with OC300. 

About 2 weeks: 2 devices randomly disconnect according to my omada application. One is connected via cable and the other to another EAP225 in a mesh network. I haved tried the 2 EAPs reset-reconfig but the problem isn't solved. 

Mesh AP: 10-27-F5-37-29-A6

Wired AP: 00-31-92-E7-12-BA <- this connected to TL-SG2008P v1.0 1000 Mbit.

I hope I attached the good log, thanks a lot:

 

 

01-30-2022 09:04:08.272 WARN [netty-tcp-server-worker-15-3] [] c.t.s.e.t.n.ChannelLoggingHandler(47): [id: 0x06cc6101, L:/192.168.10.1:29814 - R:/192.168.10.5:35438] EXCEPTION: io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
01-30-2022 09:04:08.274 INFO [manage-work-group-5] [] c.t.s.o.m.d.p.t.c(129): Device 10-27-F5-37-29-A6 OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) changed to status CONNECTED_ERROR, which don't need to handle.
01-30-2022 09:04:09.125 INFO [manage-work-group-0] [] c.t.s.o.m.d.p.t.c(129): Device 00-31-92-E7-12-BA OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) changed to status CONNECTED, which don't need to handle.
01-30-2022 09:04:19.156 INFO [manage-work-group-0] [] c.t.s.o.m.d.d.m.i.a(160): ignore repeat inform, OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) DeviceMac(00-31-92-E7-12-BA) seq:8310
01-30-2022 09:04:29.196 WARN [netty-tcp-server-worker-15-4] [] c.t.s.e.t.n.ChannelLoggingHandler(47): [id: 0xdcd2a6d3, L:/192.168.10.1:29814 - R:/192.168.10.5:50710] EXCEPTION: io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
01-30-2022 09:04:29.198 INFO [manage-work-group-7] [] c.t.s.o.m.d.p.t.c(129): Device 00-31-92-E7-12-BA OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) changed to status CONNECTED_ERROR, which don't need to handle.
01-30-2022 09:04:37.652 INFO [manage-work-group-7] [] c.t.s.o.m.d.p.t.c(129): Device 10-27-F5-37-29-A6 OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) changed to status CONNECTED, which don't need to handle.
01-30-2022 09:04:59.194 ERROR [RxComputationThreadPool-1] [] c.t.s.o.m.d.p.t.e.a(98): send inform reply to omadacId OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) & mac DeviceMac(00-31-92-E7-12-BA) error
java.util.concurrent.TimeoutException: The source did not signal an event for 30000 milliseconds and has been terminated.
    at io.reactivex.internal.operators.single.SingleTimeout$TimeoutMainObserver.run(SingleTimeout.java:123) [rxjava-2.2.18.jar:?]
    at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:38) [rxjava-2.2.18.jar:?]
    at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:26) [rxjava-2.2.18.jar:?]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0-internal]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0-internal]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0-internal]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0-internal]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0-internal]
    at java.lang.Thread.run(Thread.java:745) [?:1.8.0-internal]
01-30-2022 09:05:02.426 INFO [manage-work-group-7] [] c.t.s.o.m.d.p.t.c(129): Device 00-31-92-E7-12-BA OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) changed to status CONNECTED, which don't need to handle.
01-30-2022 09:05:07.840 WARN [netty-tcp-server-worker-15-5] [] c.t.s.e.t.n.ChannelLoggingHandler(47): [id: 0x6c273533, L:/192.168.10.1:29814 - R:/192.168.10.5:42555] EXCEPTION: io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
01-30-2022 09:05:07.842 INFO [manage-work-group-4] [] c.t.s.o.m.d.p.t.c(129): Device 10-27-F5-37-29-A6 OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) changed to status CONNECTED_ERROR, which don't need to handle.
01-30-2022 09:05:09.387 INFO [vpn-certificate-clean-workgroup-0] [] c.t.s.o.m.c.d.m.s.g.a.a(98): VpnCertificateClearTask handling omadacId: OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7)
01-30-2022 09:05:12.457 INFO [manage-work-group-0] [] c.t.s.o.m.d.d.m.i.a(160): ignore repeat inform, OmadacId(15bf28156de9a26e7a4a169ca8f7bbd7) DeviceMac(00-31-92-E7-12-BA) seq:8311
01-30-2022 09:05:26.089 INFO [scheduled-pool-1] [] c.t.s.o.c.d.m.c.g(92): Need override old client history for client 54-A0-50-4C-86-DE with lastSeen 1643533199653
01-30-2022 09:05:26.098 INFO [scheduled-pool-1] [] c.t.s.o.c.d.m.c.g(92): Need override old client history for client E8-65-D4-DC-69-91 with lastSeen 1643533199653
01-30-2022 09:05:26.098 WARN [scheduled-pool-1] [] c.t.s.o.c.d.m.c.g(105): New connection may override the pre pre history
01-30-2022 09:05:26.107 INFO [scheduled-pool-1] [] c.t.s.o.c.d.m.c.g(92): Need override old client history for client D8-B0-53-0B-F8-09 with lastSeen 1643533199653
01-30-2022 09:05:26.107 WARN [scheduled-pool-1] [] c.t.s.o.c.d.m.c.g(105): New connection may override the pre pre history
01-30-2022 09:05:26.116 INFO [scheduled-pool-1] [] c.t.s.o.c.d.m.c.g(92): Need override old client history for client 9C-9C-1F-C1-CF-28 with lastSeen 1643533199653
01-30-2022 09:05:32.778 WARN [netty-tcp-server-worker-15-6] [] c.t.s.e.t.n.ChannelLoggingHandler(47): [id: 0xc8041f51, L:/192.168.10.1:29814 - R:/192.168.10.5:34325] EXCEPTION: io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer

 

 

Kindly regards, Daniel Molnar.

 

  0      
 
  0      
 
#1
Options
6 Reply
Re:OC300-EAP225, 2 AP-s are disconnect a lot of time...
2022-01-31 16:05:38

@Daniel-nio 

 

If there is a firewall between controller and access point you ned to open TCP 29814

 

1-30-2022 09:04:08.272 WARN [netty-tcp-server-worker-15-3] [] c.t.s.e.t.n.ChannelLoggingHandler(47): [id: 0x06cc6101, L:/192.168.10.1:29814 - R:/192.168.10.5:35438] EXCEPTION: io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer

 

this a new port in omada ver. 5.0.30

 

 

 

  0  
  0  
#2
Options
Re:OC300-EAP225, 2 AP-s are disconnect a lot of time...
2022-03-16 09:41:48

  @shberge 

 

Thanks a lot, problem solved.

  0  
  0  
#3
Options
Re:OC300-EAP225, 2 AP-s are disconnect a lot of time...
2022-08-17 00:41:57

  @Daniel-nio 

 

Sir, I also own an oc300 and have the same problem with my access points. However, I am not a programmer, so I would appreciate it if you could teach how to open port tcp 29814 on this unit. The oc300 gets internet from a mikrotik router rb5009 with ip 172.3.3.1 and is connected to 2 access points. Could you please teach me what to put on the omada? is it on the port forwarding screen and what do i put on the fields? Thank you in advance for your help. 

  0  
  0  
#4
Options
Re:OC300-EAP225, 2 AP-s are disconnect a lot of time...
2022-08-17 05:46:44

  @Noling Hi, you need to open the port on your router.

  0  
  0  
#5
Options
Re:OC300-EAP225, 2 AP-s are disconnect a lot of time...
2022-08-17 08:40:23

  @Yannie 

 

Sir, 

 

Thank you for your reply. I think there is a simpler way to open port 29814 on the oc300 thru the controller. on the nat settings, there is a port forward option, I only need to fill up the required data which I'm having a hard time doing since I'm confused with what to put in, hence I'm asking for help.  It's on page 120 of the oc300 manual. Based on the page, I can assume the source and destination port might be 29814, I have no idea what to put on the destination ip. Is it the ip that is assigned on the controller coming from my router? Cause that is all I can think the ip refers to. Any help on this would be highly appreciated.

 

  0  
  0  
#6
Options
Re:OC300-EAP225, 2 AP-s are disconnect a lot of time...
2022-08-22 06:31:56

  @Noling 

 

I atteched an pic, i hope it is help for you:

  0  
  0  
#7
Options

Information

Helpful: 0

Views: 732

Replies: 6

Related Articles
eap 225 outdoor in disconnect status
238 0
Can't ping devices on AP after a period of time
1267 0
EAP225 unable connect, disconnnect after updating OMADA controller OC300 with Latest Firmware 5.3.2
737 0
EAP225 disconnected
288 0
Series connection of 2 CPE220's
332 0
Wow. That's a lot of spam posts
462 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.