The script runs each time the specific page hits by a user so it should login , execute the command and then logout . the only way is a persistent connection with something like CURL or pfsockopen which needs customization of API_PHP_Class .You aren't following that example literally, are you? It does a login, one command, then logs out. You can log in once, do as many commands as you need to do, then disconnect (logout) once when you are finished for the session.
Tried but unfortunately not workedMaybe a "/quit" command sent just before the disconnect might drop the user from the active list.
That must be true, for on an RB411 with connection tracking disabled (no NAT, just bridging and/or simple routing) running 4.5, repeated API connect/command/disconnect sessions do not accumulate, but behave as expected. (Using the Ruby API library, but the library/language doesn't matter.)The /user active list is directly tied to /ip firewall connection table for that service (from what I've found).
http://forum.mikrotik.com/viewtopic.php?f=2&t=41200what problem exactly?anybody tests this problem in 5.0rc11 ?
If you talk about idling connections in active list - it has been fixed in 5.0beta2