EAP65x | EAP67x Pre-release Firmware Adapted to Omada Controller v6.0 (Closed on 23st Oct, 2025)

EAP65x | EAP67x Pre-release Firmware Adapted to Omada Controller v6.0 (Closed on 23st Oct, 2025)

45 Reply
Re:EAP65x | EAP67x Pre-release Firmware Adapted to Omada Controller v6.0 (Closed on 23st Oct, 2025)
Wednesday

  @Vincent-TP 

 

In order to improve the integrity of information for the user, it would be beneficial for TP-Link to highlight, in Omada products via a pop-up or informational message with warning indicators, features that may impact their availability. This is especially important in cases like this, where the provisioned feature clearly needs to be effective, unless it is a feature that, due to some eventuality in its functionality, could actually cause this, with the user being responsible for and aware of this and the choice they need to make.

This would significantly reduce the number of posts with these questions, unless they are real problems. And this helps to further consolidate the Omada environment, not only for us enthusiasts but for everyone in the ecosystem.

  0  
  0  
#43
Options
Re:EAP65x | EAP67x Pre-release Firmware Adapted to Omada Controller v6.0 (Closed on 23st Oct, 2025)
Yesterday

Hi  @Artur.Aragao 

 

Thanks for your reply.

 

Turning on this function requires additional processing for all traffic, so it will indeed have a slight impact on performance. Please turn off Prohibit Wi-Fi Sharing, pause other traffic of this EAP, and test the speed for some more times. The performance should be fine.

 

Artur.Aragao wrote

  @Vincent-TP

 

Yes, I have the "Prohibit Wi-Fi Sharing" feature enabled. I started using it, but I feel like it's not just this feature that's limiting me.

I already maxed out at 500MB with a 700MB link a while ago. But, if I'm not mistaken, it was with an older firmware.

Regarding the "Prohibit Wi-Fi Sharing" feature, when I disabled it, the download and upload went from 223MB / 232MB to 265MB (at one point it reached 318MB) / 258MB, respectively. Still, for what I've had, it's low.

This feature is great and I can't see why it causes this anomaly.

Anyway, my dear. Thank you very much for your usual kindness.

 

 

  0  
  0  
#44
Options
Re:EAP65x | EAP67x Pre-release Firmware Adapted to Omada Controller v6.0 (Closed on 23st Oct, 2025)
Yesterday

Hi  @Artur.Aragao 

 

Thanks for the feedback. This is a good idea. You may start a new request post to gather more voters. 

Artur.Aragao wrote

  @Vincent-TP 

 

In order to improve the integrity of information for the user, it would be beneficial for TP-Link to highlight, in Omada products via a pop-up or informational message with warning indicators, features that may impact their availability. This is especially important in cases like this, where the provisioned feature clearly needs to be effective, unless it is a feature that, due to some eventuality in its functionality, could actually cause this, with the user being responsible for and aware of this and the choice they need to make.

This would significantly reduce the number of posts with these questions, unless they are real problems. And this helps to further consolidate the Omada environment, not only for us enthusiasts but for everyone in the ecosystem.

 

  0  
  0  
#45
Options
Re:EAP65x | EAP67x Pre-release Firmware Adapted to Omada Controller v6.0 (Closed on 23st Oct, 2025)
Yesterday

Hello, can anyone who is using this beta firmware in standalone mode confirm if it fixes the constant spamming of "omada" DNS queries? Iv seen other threads mentioning the issue, but never really anyone that has fixed it other than "wait for a new firmware release".

  0  
  0  
#46
Options
Re:EAP65x | EAP67x Pre-release Firmware Adapted to Omada Controller v6.0 (Closed on 23st Oct, 2025)
Yesterday

Hi  @angrynerd 

 

This beta firmware has not integrated that feature. It's still under development. Thanks.

angrynerd wrote

Hello, can anyone who is using this beta firmware in standalone mode confirm if it fixes the constant spamming of "omada" DNS queries? Iv seen other threads mentioning the issue, but never really anyone that has fixed it other than "wait for a new firmware release".

 

  1  
  1  
#47
Options