Business Community > All Threads > eap225 adopting loop, but working
< All Threads

eap225 adopting loop, but working

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

eap225 adopting loop, but working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
eap225 adopting loop, but working
eap225 adopting loop, but working
2023-07-20 19:52:24 - last edited 2023-08-21 01:22:45
Model: EAP225-Outdoor  
Hardware Version: V3
Firmware Version: 5.1.0 Build 20220926 Rel. 62456

This afternoon my EAP225-outdoor started to repeatedly re-adopt.

The client connection (security camera) is not affected. But every few minutes I see it in "adopting" state, becomes "connected" for a while and then returns to "adopting".

 

Nothing has changed in the network. My other 6 devices are stable. Tried to power cycle the whole network segment, including EAP. Tried to reboot EAP from the controller. Rebooted the controller itself. No improvement.

The EAP replies to ICMP pings without any problems, Ethernet port statistics on the switch shows no anomaly.

 

In the packet dump I have noticed that EAP actively refuses packets from Omada Software Controller, as if it closes UDP port before reception of the response.

 

10.10.0.103 is the EAP, 10.8.0.1 is my software controller. 

 

21:36:15.557258 IP 10.10.0.103.40912 > 10.8.0.1.29810: UDP, length 921
21:36:15.572086 IP 10.8.0.1.29810 > 10.10.0.103.40912: UDP, length 148
21:36:15.572278 IP 10.8.0.1.29810 > 10.10.0.103.40912: UDP, length 148
21:36:15.572406 IP 10.8.0.1.29810 > 10.10.0.103.40912: UDP, length 148
21:36:15.576988 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 40912 unreachable, length 184
21:36:15.578331 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 40912 unreachable, length 184
21:36:15.578420 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 40912 unreachable, length 184

[...]

21:44:06.817929 IP 10.10.0.103.44404 > 10.8.0.1.29810: UDP, length 921
21:44:06.832638 IP 10.8.0.1.29810 > 10.10.0.103.44404: UDP, length 148
21:44:06.832789 IP 10.8.0.1.29810 > 10.10.0.103.44404: UDP, length 148
21:44:06.832903 IP 10.8.0.1.29810 > 10.10.0.103.44404: UDP, length 148
21:44:06.834601 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 44404 unreachable, length 184
21:44:06.835069 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 44404 unreachable, length 184
21:44:06.835135 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 44404 unreachable, length 184

 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:eap225 adopting loop, but working-Solution
2023-08-19 10:55:10 - last edited 2023-08-21 01:22:45
Dear @Hank21, I'm back with updates. It turned out that due to some misterious configuration reset in the IP camera it had reverted to a fixed IP. The same I have later assigned to EAP. So the core reason of the adoption problems was IP address conflict. To make things more obscure, the camera was generally working and I attributed some glitches to low WiFi signal. Thank you for your support - to you Hank and your colleagues from technical support team. They have put me on a right path by suggesting networking issues. And a lesson learned: It'd be great to have duplicate IP warning from router/Omada controller.
Recommended Solution
  0  
  0  
#15
Options
14 Reply
Re:eap225 adopting loop, but working
2023-07-20 20:27:58

@Hank21 Hank, this is a good one.  Would be interesting to see if it can be replicated.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#2
Options
Re:eap225 adopting loop, but working
2023-07-21 07:45:01

Hello @JackShepard，

 

What's the physical connection(current topology) of your all devices? (You can draw a diagram of Network Topology simply if you don't mind.)

Can it fix by rebooting the router? Did it start to happen after you upgrade the firmware of which device?

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#3
Options
Re:eap225 adopting loop, but working
2023-07-21 09:32:43

  @Hank21 

Hello Hank,

 

Re firmware upgrade - I am not aware of any, although I have autoupgrade enabled in Omada Controller. 

 

Re router reboot - will do later today

 

The connection between Omada Software Controller and the EAP is as below

1. Software controller on Linux virtual machine at my cloud with local IP 10.8.0.1

2. On the same machine OpenVPN server managing 10.8.0.x subnet

( The Internet )

3. ER605 v1 fw 1.0.3  router (LAN subnet 10.10.0.x, static route for 10.8.0.x subnet poining to 10.10.0.250)

4. Raspberry PI 10.10.0.250 with OpenVPN client (10.8.0.2) with packet forwarding enabled - that's where I did packet dump

5. EAP225 as a mesh host

( radio link between buildings )

6. EAP225 as a mesh client

7. Mikrotik switch with SFP (other EAPs also connected here but they are OK, Network Video Recorder also plugged here)

( fibre connection to remote part of the property )

8. Mikrotik switch with SFP - it shows no problems with EAP's ethernet interface, no errors, dropped packets, connection losts etc

9. the problematic EAP (10.10.0.103)

10. security cameras - few connected to the same switch as the EAP, one using the EAP for WiFi connection

 

I'd like to emphasize that this setup has been working successfully since April and the transmission from the cameras to NVR was rock solid, also Mesh uplink is stable. So no problems on the physical layer.

That ICMP packet indicating closed port is definetely coming from the EAP.

Even now, in this strange state, it properly forwards DHCP request from wireless client. And then comes back to adoption loop.

 

10:53:42.691595 IP 10.10.0.103.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from [IP Camera WiFi MAC redacted] (oui Unknown), length 300
10:53:46.360135 IP 10.10.0.103.36403 > 255.255.255.255.29810: UDP, length 921
10:53:46.360729 IP 10.10.0.103.36403 > 10.8.0.1.29810: UDP, length 921
10:53:46.375762 IP 10.8.0.1.29810 > 10.10.0.103.36403: UDP, length 148
10:53:46.375898 IP 10.8.0.1.29810 > 10.10.0.103.36403: UDP, length 148
10:53:46.376044 IP 10.8.0.1.29810 > 10.10.0.103.36403: UDP, length 148
10:53:46.378711 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 36403 unreachable, length 184
10:53:46.379652 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 36403 unreachable, length 184
10:53:46.379802 IP 10.10.0.103 > 10.8.0.1: ICMP 10.10.0.103 udp port 36403 unreachable, length 184
  0  
  0  
#4
Options
Re:eap225 adopting loop, but working
2023-07-21 10:12:43
ps. router's reboot does not help for a moment EAP stays connected, then drops and re-adopts 12:10:09.152354 IP 10.10.0.103.52261 > 10.8.0.1.29814: Flags [R], seq 1961395829, win 0, length 0 12:10:13.149047 IP 10.10.0.103.52261 > 10.8.0.1.29814: Flags [S], seq 1961395828, win 14600, options [mss 1460,sackOK,TS val 5263051 ecr 0,nop,wscale 4], length 0 12:10:13.161922 IP 10.8.0.1.29814 > 10.10.0.103.52261: Flags [S.], seq 1724049237, ack 1961395829, win 65160, options [mss 1460,sackOK,TS val 3704148710 ecr 5263051,nop,wscale 7], length 0 12:10:13.184375 IP 10.10.0.103.52261 > 10.8.0.1.29814: Flags [R], seq 1961395829, win 0, length 0 12:10:16.164009 IP 10.10.0.103.53596 > 10.8.0.1.29814: Flags [S], seq 2061228063, win 14600, options [mss 1460,sackOK,TS val 5263352 ecr 0,nop,wscale 4], length 0 12:10:16.176369 IP 10.8.0.1.29814 > 10.10.0.103.53596: Flags [S.], seq 840431642, ack 2061228064, win 65160, options [mss 1460,sackOK,TS val 3704151725 ecr 5263352,nop,wscale 7], length 0 12:10:16.178644 IP 10.10.0.103.53596 > 10.8.0.1.29814: Flags [R], seq 2061228064, win 0, length 0 12:10:17.158691 IP 10.10.0.103.53596 > 10.8.0.1.29814: Flags [S], seq 2061228063, win 14600, options [mss 1460,sackOK,TS val 5263452 ecr 0,nop,wscale 4], length 0 12:10:17.171836 IP 10.8.0.1.29814 > 10.10.0.103.53596: Flags [S.], seq 855971371, ack 2061228064, win 65160, options [mss 1460,sackOK,TS val 3704152720 ecr 5263452,nop,wscale 7], length 0 12:10:17.173865 IP 10.10.0.103.53596 > 10.8.0.1.29814: Flags [R], seq 2061228064, win 0, length 0 12:10:19.158483 IP 10.10.0.103.53596 > 10.8.0.1.29814: Flags [S], seq 2061228063, win 14600, options [mss 1460,sackOK,TS val 5263652 ecr 0,nop,wscale 4], length 0 12:10:19.171542 IP 10.8.0.1.29814 > 10.10.0.103.53596: Flags [S.], seq 887217820, ack 2061228064, win 65160, options [mss 1460,sackOK,TS val 3704154720 ecr 5263652,nop,wscale 7], length 0 12:10:19.174418 IP 10.10.0.103.53596 > 10.8.0.1.29814: Flags [R], seq 2061228064, win 0, length 0
  0  
  0  
#5
Options
Re:eap225 adopting loop, but working
2023-07-21 10:20:40 - last edited 2023-07-21 10:26:18

  @JackShepard 

 

Upgrade your router to 1.3.0.

 

1.0.3 is problably full of bugs

 

what version is your controller?

 

  0  
  0  
#6
Options
Re:eap225 adopting loop, but working
2023-07-21 12:42:06

  @MR.S 

Hi,

I already have 1.3.0, sorry for typo

Controller Linux 5.9.31

 

I can give your engineers a remote access, there nothing secret in this network :)

 

  0  
  0  
#7
Options
Re:eap225 adopting loop, but working
2023-07-21 13:00:51

  @JackShepard 

 

OK then you have all the latest versions, seems like this is a tp-link support issue, I can't quite see what your problem is then, have you tried deleting the device and re-adopting?

 

  0  
  0  
#8
Options
Re:eap225 adopting loop, but working
2023-07-21 14:04:24
sure, after forgot/adopt cycle remained connected for an hour or so and the problem is back again Will replace the device during weekend and see if it works at home.
  0  
  0  
#9
Options
Re:eap225 adopting loop, but working
2023-07-21 14:21:30

  @JackShepard 

 

sounds like a plan :-) one of my kids has two of these with 5.1.0 firmware and omada controller 5.9 on linux and ER605v1 whit 1.3.0, never had a problem. but if you test it at home do you want to see if the same thing happens, if the same happen there is probably something wrong with the access point

  0  
  0  
#10
Options
Re:eap225 adopting loop, but working
2023-07-21 16:11:31 - last edited 2023-07-21 16:11:44

Thanks  @MR.S !

 

That's my suspicion. But it'd be a pity to see an outdoor EAP dying so young ;-)

Will come back soon.

Fortunatelly I have a spare 110-Outdoor somewhere. As you see from my screenshot other EAP225s have even 59 days uptime.

No problems till yesterday. (apart from this strange beaviour of heavily loaded EAP110 I described few months ago).

  0  
  0  
#11
Options
12

Information

Helpful: 0

Views: 1937

Replies: 14

Related Articles
Adopt loop with EAP225-Outdoor
458 0
eap225 not adopting
1244 0
TP-Link EAP225-Outdoor not adopting
1290 0
EAP225 not adopting
1227 0
ER605 - Adopting loop
100 0
EAP570 and EAP225 outdoor mesh network not working
1230 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.