Gateway second site disconnected after firmware upgrade ER605 (from 2.3.0 to 2.3.1)

Gateway second site disconnected after firmware upgrade ER605 (from 2.3.0 to 2.3.1)

Gateway second site disconnected after firmware upgrade ER605 (from 2.3.0 to 2.3.1)
Gateway second site disconnected after firmware upgrade ER605 (from 2.3.0 to 2.3.1)
Thursday - last edited 8 hours ago
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.3.1 Build 20251015 Rel.78291

I manage two sites with my OC200 v1.0 controller. The gateway of the secondary site reports over internet into the controller which is located in my primary site.

 

Setup of primary site:

1 x OC200 v1.0 controller (firmware 1.36.7 Build 20250707 Rel.72474)

1 x ER605 v2.0 gateway (firmware 2.3.0 Build 20250428 Rel.18967)

2 x SG2210P v5.20 switch (firmware 5.20.14 Build 20250928 Rel.82909)

1 x ES205G v1.0 switch (firmware 1.0.4 Build 20250609 Rel.74647)

5 x EAP615-Wall(EU) v1.0 access points (firmware 1.5.4 Build 20250515 Rel. 67108)

2 x EAP225-Outdoor(EU) v1.0 access points (firmware 5.2.3 Build 20250709 Rel. 67584)

2 x EAP230-Wall(EU) v1.0 access points (firmware 3.2.5 Build 20250904 Rel. 65179)

 

Setup of secondary site:

1 x ER706W v1.0 wi-fi gateway (firmware 1.2.2 Build 20250821 Rel.60581(4555))

1 x EAP225-Outdoor(EU) v1.0 access point (firmware 5.2.3 Build 20250709 Rel. 67584)

 

Yesterday evening I upgraded my ER605 v2.0 gateway of my main site to firmware 2.3.1 Build 20251015 Rel.78291 to fix the command injection and root access vulnerabilities on Omada gateways. After the upgrade the ER706W v1.0 wi-fi gateway of my secondary site is not reporting into my OC200 v1.0 over internet anymore. It shows as 'DISCONNECTED'. Since I don't have physical access to my secondairy site, I cannot reboot the gateway.

 

Edit: Someone who has physical access to my secondairy site rebooted the gateway, but this did not resolve the issue.

 

Does someone recognize this behavior and knows how to resolve this?

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Gateway second site disconnected after firmware upgrade ER605 (from 2.3.0 to 2.3.1)-Solution
8 hours ago - last edited 8 hours ago

Hi  @WM1 

 

Thanks for posting here.

 

This update only resolves several security vulnerabilities and should not have much impact on remote management.

Have you checked if the port settings are still normal? Did this update change the router's WAN IP? If everything is normal, but the ER706W is offline in the controller and we cannot remotely modify it, the fastest fix might be to reset the ER706W locally and attempt to re-manage it.

 

Reminder: This process will interrupt the network, so it's recommended to perform it when the network is not in use.

Recommended Solution
  0  
  0  
#3
Options
2 Reply
Re:Gateway second site disconnected after firmware upgrade ER605 (from 2.3.0 to 2.3.1)
Friday

Hi @Ethan-TP, making you aware of this issue.

 

Unfortunately, I haven't been able to resolve it yet. The secondary site is fully functional, but it no longer reports to the controller, meaning I can no longer manage it remotely.

 

Interestingly, a few months ago I updated the ER605 v2.0 gateway to firmware 2.3.0 Build 20250428 Rel.18967, which didn't cause any problems after the update and restarting the gateway. This suggests that the issue is caused by changes in the new firmware. Can you please have this checked? Thanks in advance.

  0  
  0  
#2
Options
Re:Gateway second site disconnected after firmware upgrade ER605 (from 2.3.0 to 2.3.1)-Solution
8 hours ago - last edited 8 hours ago

Hi  @WM1 

 

Thanks for posting here.

 

This update only resolves several security vulnerabilities and should not have much impact on remote management.

Have you checked if the port settings are still normal? Did this update change the router's WAN IP? If everything is normal, but the ER706W is offline in the controller and we cannot remotely modify it, the fastest fix might be to reset the ER706W locally and attempt to re-manage it.

 

Reminder: This process will interrupt the network, so it's recommended to perform it when the network is not in use.

Recommended Solution
  0  
  0  
#3
Options