Hi @Hobbs1210 

Thanks for posting in our business forum.

Hobbs1210 wrote

  @Clive_A 

 

Controller is OC200 1.31.3 version 5.14.26.23 .

After factory reset new firmware worked as expected.

 

Please prepare a backup of your site. Not the support backup, I require a regular backup. I will send you an email later. Please reply to the email with the backup attachment. 

Hi @Hobbs1210 

Thank you so much for taking the time to post the issue on TP-Link community!

To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240777868, please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

Many thanks for your great cooperation and patience!

Hi @paulrob 

Thank you so much for taking the time to post the issue on TP-Link community!

To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240777925, please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

Many thanks for your great cooperation and patience!

  @Clive_A 

Hi again. I  think I've resolved the problem now, and I comfirm (with the short testing I've done so far) that FW V1.2.2 (Pre-Release) seems to now be working okay for me, but I have a little more reconfiguring to do since I started again from scratch instead of restoring my previous settings.

The basic problem was a local static IP address conflict in my static address pool (the range 192.168.0.2 to 192.168.0.99 is excluded from the DHCP pool for static IP use). 

The conflict happened between the Wireguard Server settings and my QNAP NAS. I thought that address 192.168.0.3 was free to move my NAS to (a static IP address makes it easier to access the NAS and PCs locally via SMB on my phone). Looking at the Client List and the DHCP Reservation list, it appeared that this IP was free to use. Problem was I'd forgotten the WireGuard Server was also configured to use that IP, but when I allocated it to the NAS the DHCP Reservation page didn't alert me that this IP was already in use by Wireguard. So: lessons learned (red face). Moving the NAS to a higher free IP number resolved the issues.

By way of suggestion for consideration in future firmware, if I may, it would be helpful if the WireGuard server Local Address was indicated in the Cliient List or the DHCP Reservation list in some way so this doesn't catch others out. Thanks so much, and thanks again for all your assistance. It's been very much appreciated.

I think this ticket can now be considered CLOSED. But if there's any followup you'd like information on, please do let me know.

Best regards,

Paul

Clive_A wrote

Hi @Hobbs1210 

Thanks for posting in our business forum.

Hobbs1210 wrote

 This firmware has caused the router to go into a configuration loop.  Had to factory reset the router to get it working again with the controller.

What's the firmware of the controller? The version of the controller.

So, in your case, you reset it and it behaved properly again? Not the loop like the above, Adopting > Configuring > Heartbeat Missed > Adoptin.

 @Hobbs1210 & Clive_A

I've resolved the problem as per my previous post, but FYI: the OC200 V2.0 controller has Firmware Version: 2.14.4 Build 20240304 Rel.54311

See below.

Hi @paulrob 

Thanks for posting in our business forum.

paulrob wrote

Clive_A wrote

Hi @Hobbs1210 

Thanks for posting in our business forum.

Hobbs1210 wrote

 This firmware has caused the router to go into a configuration loop.  Had to factory reset the router to get it working again with the controller.

What's the firmware of the controller? The version of the controller.

So, in your case, you reset it and it behaved properly again? Not the loop like the above, Adopting > Configuring > Heartbeat Missed > Adoptin.

 @Hobbs1210 & Clive_A

I've resolved the problem as per my previous post, but FYI: the OC200 V2.0 controller has Firmware Version: 2.14.4 Build 20240304 Rel.54311

See below.

 

Very glad to know that it is resolved by your efforts. And great to know that you have located the reason why. I am aware of them but we still would like to diagnose your backup. Please see the email I sent to you.

We would like to make sure everything's okay before a public release is on schedule.

Clive_A wrote

Very glad to know that it is resolved by your efforts. And great to know that you have located the reason why. I am aware of them but we still would like to diagnose your backup. Please see the email I sent to you.

 

We would like to make sure everything's okay before a public release is on schedule.

  @Clive_A 

Thanks for your helpful interest. I've sent the Omada .cfg backup file in reply to your email now. This is the settings backup file taken just before the upgrade to V1.2.2 manifested into my difficulties. Hope it helps. And (stating the obvious) please only try it in an isolated test network, don't use it in a production network :)  FWIW, my ISP provides dual-stack IPV4/IPV6 and I had it configured for both (and still do with the newly fixed configuration). My 1Gbps WAN is connected theough the SFP+ WAN1 port via a TP-Link 10Gbps Ethernet adapter. Sometimes I have a failover 4G LTE WAN also attached to the another WAN port, but not at that time.

Cheers,

Paul