Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Closed on 12 Nov)

Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Closed on 12 Nov)

144 Reply
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 16th Sep)
2025-10-12 12:12:45

  @chamadz i have the same problem 

  0  
  0  
#104
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-12 07:04:47

  @ceejaybassist

 

 

Dear all,

 

It's great that you want to solve your problem and even help others.

 

However, I strongly recommend against downloading Omada apps unless they're from official sources.

 

These apps from unofficial sources may have been manipulated to create a backdoor or worse.

 

Stay tuned. Okay?

 

  0  
  0  
#103
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-12 05:09:30

  @ceejaybassist Absolute legend! Thank you, Thank you, Thank you! 

  0  
  0  
#102
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-12 03:51:31 - last edited 2025-10-12 03:51:53

The V5 app for android is now released. Not available yet in Google Playstore, though, at least in my case.

So I updated it through external source such as this: https://omada.en.uptodown.com/android.

 

  1  
  1  
#101
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-12 02:45:41 - last edited 2025-10-12 04:33:48

@Vincent-TP



 

Dear all,

I found something else here that made me validate and share my experience with what's happening.

 

1- I've already mentioned that I have two WANs in load balancing, and only WAN1 is working properly. WAN2 isn't responding;

 

2- I noticed that my internet on WAN1 is fluctuating a lot and isn't providing the nominal bandwidth. The link is 700Mbps, but only 530Mbps is being provided. I contacted the carrier because I noticed this and prioritized the problem there, but when I validated it directly on the carrier's router, the link worked perfectly. We have a problem here, clearly with the ER605 + OC200's operation in load balancing and processing this link. And the third item will clearly demonstrate this;

 

3- While analyzing the link through Speed ​​Test, I noticed something quite peculiar that may explain some of the problems here and even other issues. The IP address is dynamic on the carrier's routers, but I noticed that it remained the same for a long time. When I set my computer to directly access the carrier's router on WAN1, the IP immediately changed. I resumed the original connections, and the IP remained the same. I restarted the ER605 V2, and incredibly, the IP remained the same, when it should have changed. I think this could be a problem and could be affecting the load balancing. Correct me if I'm wrong.

But it's strange that I didn't change the dynamic IP. And actually, neither turning off nor restarting the carrier's router caused the IP to change. It remained the same. Very peculiar.

 

4- Referencing topics 2 and 3, only when I restarted the ER605 router did the bandwidth return to its nominal value. Please confirm this for us, if it's a point of concern. However, the carrier's IP did not change dynamically;

 

5- I'm not pointing this out as a problem, but as a point of concern or explanation from TP-Link. A reboot seemed to take longer than with a previous firmware version.

 

I know there's an ongoing ticket. I'm adding these details because I noticed it, and maybe it can help with the issues you've encountered so far.

 

Update

 

WAN1 and WAN2 returned to normal load balancing after I performed the above-mentioned procedures.

 

To recap, after connecting my PC directly to the router and getting a new dynamic IP address, I restarted the ER605 V2 router, and the nominal bandwidth returned to normal on WAN1. I can't say whether the dynamic IP change caused this, but I had restarted the ER605 before, but it didn't work. I'm firmly convinced that's what happened.

 

Interesting how all this happened, I turned the ISP router off and on again on WAN2. I waited a few minutes, and load balancing returned to normal.

   

 

I'll need to monitor this daily. There's a problem with the ER605 V2 firmware and the Load Balancer.

 

In the previous post, you can see the image that I only validated with this post. I had already performed the procedures I mentioned, and everything had returned to working order.

 

Please confirm this dynamic IP situation, which didn't change. It only occurred when I connected my PC to the carrier's router on WAN1, then reconnected to the ER605. After that, I restarted the Omada router.

 

Now both WANs are reporting their status correctly.

  0  
  0  
#100
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-11 21:33:17 - last edited 2025-10-12 03:36:43

  @denis-odessit

 

Thank you very much.

The feature is a bit hidden.

I looked a lot, as it was previously called Local DNS.

 

Another detail, as a suggestion to TP-Link:
Obviously, it would be helpful if this service were located under Gateway > DNS.

 

 

  0  
  0  
#99
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-11 12:47:37

  @denis-odessit 

Okies guessing we're waiting on the Android update. 

  0  
  0  
#98
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-11 12:42:44

  @Tunnah 

The iOS app already has an update.

 

  0  
  0  
#97
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-11 12:36:37

  @Julian2111 IOS or Android? Not seeing anything here is Australia 

  0  
  0  
#96
Options
Re:Hardware Controller (Built-in Omada SDN Controller V6.0.0) Pre-release (Release on 28th Sep)
2025-10-11 12:27:00 - last edited 2025-10-11 12:36:12

  @Julian2111 Is it now released? I'm not detecting any update on my Google Playstore.

  0  
  0  
#95
Options