I've updated the script to make it work with the current version of the API and stored it in a public Github repository. Please feel free to create a PR to keep it updated in the future. https://github.com/smangels/mikrotik-sc ... record.rsc
As a software developer I would rather prefer continuous delivery of new features. Let Mikrotik focus on rock-solid basic feature sets and enabling step by step more sophisticated features.
Don't use username and password. Make use of a SSH key instead. The public key of your generated key pair should be imported into the Mikrotik router. Ensure that you're using the right version of such a key pair. I suppose that Mikrotik just supports RSA keys. But that might be an misunderstanding....
Hi, A more elegant solution would be using PPPOE profiles. Such a profile can later be assigned to each and every individual (PPPoE secret) and ensures that the clients will end up in their own IP subnets each with their own firewall rules. I hope that this will clarify my proposed solution. /ppp pr...
You could create a scheduled task using SSH and generate the due date based on the local clock. Furthermore you have to create another scheduled task the removes the first one let's say 1min after the first one has been executed. Should be fairly straightforward
Put all three clients into their own subnet or use the option to put them into their own addresslist. Once this is done filtering a port range will be very simple.
I just gave a presentation on SIP ALG at the Mikrotik MUM in Denver Colorado 2017 explaining everything about SIP ALG in RouterOS
watch here: https://youtu.be/tM7wyKdnIKA
Do you see a need for improving the related article in wiki@Mikrotik?
Hi folks, what I usually do is creating the backup configuration files, downloading them to my local machine. Once this is done I'll strip the very first line containing the time stamp (this makes the files ready for the diff process in GIT, otherwise they will always change). Then I rename them so ...