we are using plenty Mikrotik PPPoE Concentrators integrated with DMA’s Radiusmanagers.
Seems since a while, the API Integration between DMA and Mikrotik doesnt work anymore.
DMA Support is saying, the API on Routeroard 6.x version is broken and we should downgrade to 5.x.
We cannot downgrade due to other issues and missing features on 5.x - therefore what is the solution?
Here’s the Quote from DMA Support:
Dear Sir!
The API functionality is broken in MT 6.x. Please load MT 5.x.
More details are available in this thread:
It’s not the API that is broken in v6, it’s Radius Manager’s API functionality. There’s a difference.
In other words, in a bug/“missing feature” in Radius Manager that they need to fix/add, not a bug in MikroTik or your installation.
Or (since they provide you with the source, since it’s a PHP app), you could try to patch the API module to support RouterOS v6 (and ideally, submit it back to them, so that they can integrate it for other’s sake), or find someone else to do it (me? not any time soon, thank you…).
The biggest difference between v5 and v6 is in queues though, and PPP can generate queues dynamically, so I’m kind of surprised there’s a breaking change there too.
EDIT: Actually, looking at the topic they link too, I can see their real problem - they’re relying on modifying dynamic queues… But that was never supposed to be doable. Any circumstances where that was doable were bugs that MikroTik has since fixed. And relying on bugs is generally a bad practice, precisely because it leads to situations like the one you’re finding yourself in right now.
This can be solved by using CoA instead of modifying dynamic queues, but doing THAT would break OLDER versions of RouterOS that don’t support CoA, and picking one or the other is tricky, which is probably why they still haven’t done it.
I have deployed over dozens of DMA deployments at various location, and at few points where API was used to change the queue dynamically stopped working after latest ROS that is 6.3x.x
For those location, i reverted back to 6.29 and the API started to work again. you can try 6.29 to get API functionality back. I tested it.
For proper solution, DMA should come up with proper solution