update mikrotik + old freeradius = bad

Hi
I recently bought a rb1100ahx2 to replace one of my old pppoe servers. on the old server the MT version was 2.9.51, and i haven’t upgraded it because i feared that exactly this will happen what is happening with the new version.. My pppoe users logout from radius but they stay logged in MT. I don’t know if i made myself clear.
The radius server is working OK i think, because i have 1 more active pppoe server with 2.9.51 and the users are behaving as they should.
Anyway, the radius logs say:

Mon Mar 26 11:36:05 2012 : Info: rlm_wisp (rlm_wisp_checksimul): User xxx' zapped by max ALIVE counter ((Now:1332754565 - Last_ALIVE:1332753615) >= Max_Interval:900) Mon Mar 26 11:36:05 2012 : Error: rlm_wisp (wisp_add_current): Stop packet with zero session length for user xxx’ [10.20.30.1:]
Mon Mar 26 11:36:05 2012 : Info: rlm_wisp (rlm_wisp_accounting): STOP without START for user xxx', so added START Mon Mar 26 11:36:05 2012 : Auth: rlm_wisp (rlm_wisp_accounting): User xxx’ logout [10.20.30.1:]

But the user stay active in MT with a working pppoe connection, and stays logged in until he manualy disconnects. Maybe i havent configured something in the new MT?
Thanks for your help

rlm_wisp_checksimul is trying to disconnect the PPPoE session on your RAS, and has obviously failed to do so, given the nature of your post.

You will have to investigate what rlm_wisp_checksimul is trying to do, and fix what ever is wrong with that piece of custom code (it’s not FreeRadius standard). It’s more than likely commands in the CLI that changed in terms of how to disconnect PPPoE sessions, and you will need to update your scripts accordingly.

Upgrading from 2.9.51 to (presumably) the latest version without testing, is just plain stupid IMHO.