OMADA 5.15 Radius deprecation
OMADA 5.15 Radius deprecation
Hi, I updated my OC200 controller earlier this week and after that, I saw a warning message advising that the inbuilt RADIUS feature will be deprecated/removed completely in 5.15, eg:
Why is Built-in RADIUS being removed, considering it hasn't been in place for very long?
I personally find it useful for RADIUS authentication of certain sensitive clients in a multi VLAN setup without having to add yet another server/service into my network landscape.
Is it too late to stop this from going ahead?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
We have gradually added more features for Omada controllers, the OC200 hardware is limited to maintaining these changes, so the function was removed.
If you still need this feature, you may consider the OC300 or installing the Omada software controller.
- Copy Link
- Report Inappropriate Content
@Vincent-TP is it the same for openapi ? Will openapi stay with oc300 and software controller?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP I see.
Looks like I'm going to have to bite the bullet on an OC300 which is less than ideal but I really don't want to use/maintain yet another server just for RADIUS authentication. 🤦♂️
Is there a documented process for replacing/migrating to a replacement hardware controller within the same site? So go from OC200 to OC300, preferably with minimal impact?
Btw I don't just mean a "use the migration feature", I mean practical advice/considerations such as:
Currently my Omada devices all use a management VLAN so they have fixed addresses within the 192.168.10.xx range. The existing OC200 controller has a local fixed IP address in that range.
Can I spin up and fully comission the OC300 working in the same local network environment (with an IP address in that same range) to facilitate the migration? Are there any issues with having two controllers sitting in the same LAN segment at the same time (since they will both need to be live presumably to perform the migration??)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Well, Amazon offered me a full refund for the OC200 because of this cr*ppy update. I bought it 2022-12...
Always buy expensive stuff on Amazon...their customer service is excellent...
- Copy Link
- Report Inappropriate Content
This is NOT OK - it's really very poor corporate behaviour, and highly damaging to user's trust in your product offering. With OpenAPI you're taking away a feature I use extensively - it was one of the key reasons I bought the OC200 only a few months ago.
TP-LINK has effectively dropped a key product offering without any user consultation, and with zero user compensation.
What's next??? How can we now trust that you won't do the exact same thing to all other key features?
I hope you're going to offer existing users of the OC200 a very heavily discounted OC300 as compensation ??? What's your plan?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Tyrade Yes exactly this. And what's going to be next on the chopping block?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 3429
Replies: 13
Voters 0
No one has voted for it yet.