After some testing and debugging, it appears that RouterOS does not send an: Stop Accounting-Request / Acct-Terminate-Cause
to the Radius server after the PPP user has disconnected.
This issue appears in version 6.11, rolling back to 6.10 fixes the issue.
Do you encounter any other issues with 6.11? i have have issues with PPP dying on pppoe or l2tp disconnection. All services/connections that use PPP instantly stop working until I reboot the machine/router. On shutdown, I can see PPP timeout messages on the console. This doesn’t happend on 6.11rc.
I hope that both of you report these bugs to support, and don’t just assume the developers will happen to read your thread on the forum. It would be very nice if 6.11 was released with bug-free and properly working PPP…it’s been a while (6.5) since that has been the case, and DHCP-over-BCP has been broken for all of 6.x. I don’t want to upgrade to 6.11 in order to fix these issues only to have a bunch of new ones… 
– Nathan
Yes, i reported it.
I think all this new CCR optimization stuff comes to fast without enough testing, they introduce way to many new bugs to use them in production
Yes ofcourse we reported it to MikroTik.
@Shiro: So far not real big issues discovered yet, except for the Radius disconnect one.
I cannot reproduce either evharten’s issue or Shiro’s issue on the March 18 build of 6.11, and I checked for both. Note that I only tested x86 and mipsbe platforms.
– Nathan
If you connect, and then disconnect from PPP for instance (L2TP/PPTP) you should have an entry in your database entry at Stop Time, i am not getting that, only with 6.10 i do.
Have not tried the newest build yet tho, i’ve tested the 14th march build, so will test the new one now.
Yep works again in 6.11 of 18th March.
I’ve updated PPPOE nas with version 6.11 and got Accounting-stop bug.
Could anybody tell me if it works in 6.12 version?
what bug?
Chupaka,
our Mikrotik sends accounting interim update with Accounting-stop message, but Radius server not send reply. We found en error in Radius configuration due to overflow in database.
This is crazy coincidence because radius issue and software upgrades for NAS became at the same time. Sorry to Mikrotiks guys!