Hii @subbustrato 

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 TKID240458088, 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 @itsmebaby 

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 TKID240458086, 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 @Belje 

Thanks for posting in our business forum.

Belje wrote

  @Clive_A 

We have the same issue, can you give us a update when this is solved?

I am paying attention to this matter. There was no update as I did not get a reply from the test/dev before.

As for now, the dev's looking into this issue. Test team has reproduced this with the backup.

Please wait for future replies and updates. AFAIK, I met something like this before on ER605 which was a rare case because the parameters were somehow changed leading to this uncommon issue. The reason was unknown and we could not locate it back then.

This time, we are still trying to figure out what might be wrong and if it is the same case as we have on the previous case.

Hi @Belje 

Thanks for posting in our business forum.

Belje wrote

  @Clive_A 

We have the same issue, can you give us a update when this is solved?

We have an assumption that this might relate to the problem with a firmware upgrade. Do you have a firmware upgrade recently? Try to downgrade it to the previous version which adapts to V5.8. Make sure your SFP WAN+ is selected as WAN. 

Then, upgrade to the V5.13 one or the latest one. It seems that you have disselected it from the SFP WAN before you upgraded to the V5.13. After that, it will be missing on your V5.13 or later firmware.

Hi @subbustrato 

Thanks for posting in our business forum.

subbustrato wrote

  @Clive_A 

 

below my considerations that I also reported to the support answering to the ticket:

 

 

The short answer is, no, your suggestion does not work for me. Please consider following items:

 

1) My router is running fw 1.x is a  ER8411 V1, why are you suggesting other firmware branches ??

 

2) In ER8411 V1 WAN1 is a "wan only port" cannot be configured to work in LAN mode!!

 

3) I cannot downgrade and upgrade a router in production in this way, as you may have seen in my backup there are a lot of configurations  in my router and I'm not so sure that the configurations I have will be kept after downgrading the firmware. What would be most appreciate is a new firmware that fixes the issue.

 

Please let me know if I'm missing anything.

 

I don't work on weekends so if you reply to that ticket during weekends, please understand I cannot reply to it timely.

If this is in production, I think I cannot give any better solutions now. If this is the case, we may have a remote session with the dev to further debug what might be wrong. But you may get the same suggestions.

1) Understand the firmware of each release is adapting to a different Omada Controller version.

2) It was a bug on the previous firmware which has been projected to be fixed in future firmware releases. So, I am recommending this because the dev has already taken a look at your config.

3) We don't have any firmware addressing this issue yet. I need to check with the team and see if they can work on a beta. But I cannot guarantee you anything at this moment.

Nor the ETA for an official release.