Why is it restricted by rOS whether I can edit a dynamic item? I can´t imagine a reason for this. Perhaps it is not best practice to do so. But it did work, so why I am imposed the will of the developers not to do so?
Of course dynamic items are perhaps changing by the system at any time but when I can handle this, why I am not allowed to do so?
But at the moment there is no consistent way to change rate limit for pppoe-users. There would be Radius CoA feature but that is not supported within ROS for PPPoE-Server with Radius. If that would exist I would agree perhaps.
With the removal of this possiblity I would have have to create/remove simple queues manually on each connect/disconnect and the whole rate-limit attribute is no longer usable if change of rate-limit during connection can occur.
Not important for me whether it was a bug or a feature, it worked for months now
Now I cannot upgrade any longer until we reworked the whole system. Very annoying.
Do you know if proper coa support is already in work?
Dynamic items are temporary, they are created and destroyed by system, based on specifications configured in that system, ability to manually change something in them breaks the meaning of dynamic, if you need something changed or different - make static.
It worked years and worked perfectly. There were no problems when changing the dynamic entries. I could change the rate-limit of thousands of users every day without disconnect (increase the speed at night and decrease at the morning) … and now I can not - “failure: cannot change dynamic”.
The API functionality is broken in MT 6.x
so we cant use radius for changing dynamic rules,
what we should do ?
there will be fix ? or we must downgrade mikrotik version ?
