Did anyone test CoA with PPPoE users ?
No, waiting for the final.
please dont fix the wrong bugs, we need to change dynamic queue values as previous posters. This means only we will stay stuck on V6.31 as its now a feature that was removed
My 2 cents
Sew
Yes - you could change dynamic queues in the past but now it is fixed.
We will not leave something working incorrectly if we know that it is not correct.
We fixed that and implemented CoA so you should use this feature which actually allows to change queues correct way.
Hello
I upgraded to 6.33
but not changing automatically Dynamic Queues
please help me
thank you
CoA implemented in 6.33??
It does not seems to be true…
[root@testhost ~]# echo “User-Name=user,Framed-IP-Address=192.168.0.2,Acct-Session-Id=81c00003,MIKROTIK_XMIT_LIMIT=512000” | radclient -x 192.168.0.9:1700 coa testing123
Sending CoA-Request of id 77 to 192.168.0.9 port 1700
User-Name = “user”
Framed-IP-Address = 192.168.0.2
Acct-Session-Id = “81c00003”
rad_recv: CoA-NAK packet from host 192.168.0.9 port 1700, id=77, length=49
Error-Cause = Unsupported-Extension
NAS-Identifier = “MikroTik 6.x RB”
NAS-IP-Address = 192.168.0.9
Someone reported here that CoA works fine.
This time it is really working:
This is the command:
echo “User-Name=username,Mikrotik-Rate-Limit=‘2M/1M 2512K/2512K 512K/512K 600/600 2’” | radclient -x 172.16.255.1:1700 coa radiussecret
The simple queue is deleted and re-created with the new values 
Help… not only the simple queue is deleted an added again.
But also the pppoe dynamic interface!!!
I can not give any disconnection to the user.
Please Mikrotik this is not acceptable at all! fix it…, please…
Are you sure about this? Did you try latest ROS version?
If this is true, it would be a real issue and you should open a bug report.
Do you try to contact support when it is not working?
In order to use CoA:
- You have to have working Radius + RouterOS solution;
- Enabled incoming messages from Radius on router;
- Enabled CoA on Radius;
- Same ports must be configured on router and Radius.
/radius
add address=x.x.x.x secret=123 service=login timeout=10ms
/radius incoming
set accept=yes port=3799
/ool user-manager router
add shared-secret=123 ip-address=x.x.x.x customer=admin use-coa=yes coa-port=3799
As it has been stated many times in forum - this is users forum. In most cases you will not get in touch with support and even if it is software issue you will still need to send information to support@mikrotik.com
If something is not working and you do not get fix fast through forum then contact with support@mikrotik.com
I downgraded to version 6.29 for test purposes, and now the queue is changing on the fly properly without disconnecting the active users.
(both hotspot and pppoe working ok now)
we must stay on 6.29 
Finally COA attribute really works…!
I tested it on Mikrotik version 6.34
echo “User-Name=test,Mikrotik-Rate-Limit=‘1M/1M 2512K/2512K 512K/512K 600/600 2’” | radclient -x 192.168.50.3:1700 coa radsecret
Sending CoA-Request of id 90 to 192.168.50.3 port 1700
User-Name = “zzztest”
Mikrotik-Rate-Limit = “2M/2M 2512K/2512K 512K/512K 600/600 2”
rad_recv: CoA-ACK packet from host 192.168.50.3 port 1700, id=90, length=37
NAS-Identifier = “ROUTER-EU”
NAS-IP-Address = 192.168.50.3
And this is what happens on NAS:
12:48:38 radius,debug,packet received CoA-Request with id 121 from 192.168.50.20:56242
12:48:38 radius,debug,packet Signature = 0xc37c7bdda3ae3c38e59788b5e02d07a5
12:48:38 radius,debug,packet User-Name = “test”
12:48:38 radius,debug,packet MT-Rate-Limit = “1M/1M 2512K/2512K 512K/512K 600/600 2”
12:48:38 radius,debug received remote request 8 code=CoA-Request from 192.168.50.20:56242
12:48:38 radius,debug sending CoA-ACK to remote request 8
12:48:38 radius,debug,packet sending CoA-ACK with id 121 to 192.168.50.20:56242
12:48:38 radius,debug,packet Signature = 0x956c87a9e70ff1010875de8b9042bdcb
12:48:38 radius,debug,packet NAS-Identifier = “ROUTER-EU”
12:48:38 radius,debug,packet NAS-IP-Address = 192.168.50.3
There is a case in which the pppoe session is restarted: if the MT-Rate-Limit contains errors (for example Max-Limit bigger than Burst-Limit). Otherwise only the simple queue is modified, the pppoe session stays up.
I have this problem too please do something about it . Here is my post http://forum.mikrotik.com/t/radius-manager-cant-change-the-bandwidth-on-fly-after-routeros-v6-31/96445/1
So, I was using 6.30.2 and I had a simple script that would add dynamic address-list entries. I added them dynamic so they wouldn’t persist on reboot.
How can I had non persistent entries now? On Queues, Address-list, etc.?
MT removed the ability to add dynamic address-list entries as of 6.35.4 / 6.36rc28 and nobody has explained why.
I hope more people chime in, so MT will get a better understanding of how many people used this function, that has now been taken away.
i was thinking about making dynamic queues for pppoe clients to static queues with the same parameters by new feature in ppp profile script on log on and log out and don’t touch any thing else .
what i need is to have a script that can create a static queue with the same parameters of dynamic queue for each client on log in and remove dynamic queue and finally remove the static queues on user log out so i will be able to change queue’s parameters like before with out changing any thing elese.
i would be great full if anybody can help me to have the scripts i need .
hi
you can use the following scripts but the problem is that they don’t run always specially when some users try to log on together i have opened a topic about this problem or bug
on up
:local ppp (“<pppoe-$user>”);
:local maxl [/queue simple get $ppp max-limit];
:local burstl [/queue simple get $ppp burst-limit];
:local burstt [/queue simple get $ppp burst-time];
:local burstth [/queue simple get $ppp burst-threshold];
:local prio [/queue simple get $ppp priority];
:local limitat [/queue simple get $ppp limit-at];
:local target [/queue simple get $ppp target];
[/queue simple remove $ppp];
[/queue simple add target=$target max-limit=$maxl burst-limit=$burstl burst-time=$burstt burst-threshold=$burstth priority=$prio limit-at=$limitat name=$ppp];
on down
:local ppp (“<pppoe-$user>”);
[/queue simple remove $ppp];
please reenable this function in every upcoming versions