Of course You can do anything with a network of Mikrotik routers if you put a big computer next to them and use PHP/PERL/Delphi/Putty/Whatever to control them using API/Telnet/FTP;
But thats not the power of Mikrotik.
It's the only router that I know of (apart from a LInux box) that can be scripted?
So make scripting useful.
1) Either remove the 1980's 4 kilobyte string limit, so we can handle firewall lists and share between routers etc etc, or,
2) Ability to read/append text files 1 line at a time, so we can parse them,
3) Many commands are missing the file= or as-value= parameters, and can only be used interactively.
Re: Mikrotik Scripting needs to be useful! Requests!
Agree, I wish there was a proper onboard API to control them.
Re: Mikrotik Scripting needs to be useful! Requests!
On one, there are three way of doing this if I remember it well and append lines to a file goes through environment.Of course You can do anything with a network of Mikrotik routers if you put a big computer next to them and use PHP/PERL/Delphi/Putty/Whatever to control them using API/Telnet/FTP;
But thats not the power of Mikrotik.
It's the only router that I know of (apart from a LInux box) that can be scripted?
So make scripting useful.
1) Either remove the 1980's 4 kilobyte string limit, so we can handle firewall lists and share between routers etc etc, or,
2) Ability to read/append text files 1 line at a time, so we can parse them,
3) Many commands are missing the file= or as-value= parameters, and can only be used interactively.
Two, is one of three mentioned above.
Scripting is sometimes troublesome but the tools are there and you can do almost everything with it. It is a long learning process and you have to forum (scripting) from front to back find those gems.
Also use a search engine to find Mikrotik stuff. The forum search engine is rather basic.
Re: Mikrotik Scripting needs to be useful! Requests!
Well, the Ros script engine is still pretty crippled with years of patchwork and workarounds.
My advice is to replace it with python or other similar standard script language. Mikrotik should focus on advanced networking not on a self-developed script language engine. The NIH (Not Invented Here) syndrome is a bad software development philosophy in that regards.
My advice is to replace it with python or other similar standard script language. Mikrotik should focus on advanced networking not on a self-developed script language engine. The NIH (Not Invented Here) syndrome is a bad software development philosophy in that regards.
Re: Mikrotik Scripting needs to be useful! Requests!
In the old days there was LUA. But it has been removed, I think after it caused a security problem (not sure).
Hopefully something like that can return.
Hopefully something like that can return.
Who is online
Users browsing this forum: No registered users and 13 guests