Debugger is missing! But perfect feature! Thank you!
@zactodd3144
3 ай бұрын
Have been scripting for years and finally have some of my questions answered, plus some I didn't know I had. Keep up the great work
@Gooloso98
3 ай бұрын
Ty 🙏 for adding newer methods to fetch. Now I can use cloudflare's API
@dhiaahmed5420
3 ай бұрын
very informative tutorial, I wish you could do more videos about scripting 😊
@Fu86
3 ай бұрын
Nice easter egg in the endcard :)
@olpchk1115
Ай бұрын
Need more diagnostics and more available events for handling
@JB-df3ek
2 ай бұрын
What is replacement for RB911-5HacD?
@mikrotik
2 ай бұрын
L11UG-5HaxD
@XxSpYxX
3 ай бұрын
I wish scripting and scripts got into the UI
@user-zt1fd9ld7d
3 ай бұрын
Perfect explaining!
@RenzoRosales-sn4vb
3 ай бұрын
Nice haircut! Great video
@FinlayDaG33k
3 ай бұрын
TIL: There is a built-in script editor.
@zenmaster24
2 ай бұрын
can scripts be triggered on events? eg a port gets unplugged/plugged in
@mikrotik
2 ай бұрын
Most likely you can use Netwatch as a trigger, but if you want a realtime layer2 trigger, you could create a script that runs a 'while true' loop and parse the interface data on each step.
@olpchk1115
Ай бұрын
@@mikrotik what a waste!
@alexhawes-hm3xt
2 ай бұрын
instead of showing an example script of multiplying numbers can you show a real world script of internet failover between 2 connections that do not have static addresses please, this is a huge omission from ROS7, i've tried several scripts posted on the internet but nothing works consistently
@stevebot
2 ай бұрын
There are too many different failure and failover scenarios for there to be a single solution. At the most basic in your case, you let your WAN interfaces get their IP information and set their default routes, then you make a routing rule to push traffic out the interface you want to be primary and use gateway checking to let the router determine if they are viable and deactivate them as necessary. Good luck, failover is not an easy nut to crack and different failure modes with different carriers behave differently.
@alexhawes-hm3xt
2 ай бұрын
@@stevebot Thanks, looks like I have some reading to do. I do love a good technical challenge but MT would be complete if this was a built-in feature.
@achillecisco
3 ай бұрын
Nice !!!
@Accountnummer
3 ай бұрын
So, is there also a script to make that when there is one wan-port failing, and a second WAN is ging to work as a failover, to delete all the running connections?
@raminrajabioskouei781
3 ай бұрын
yep
@Accountnummer
3 ай бұрын
Thanks guys. But, the issue i got is that when the internet fails over to the 2nd WAN, the connections are not failing over with port 5060 (SIP). I'm looking for a solution for that, and thought this could be an oppurtunity.
@jferdom
3 ай бұрын
@@Accountnummer Of course you can do that.. the command to kill the connections would be like this: /ip firewall connection remove [ find where dst-address~"^123.123.123.123:" || dst-address~"^231.231.231.231:" ] All of this supposing your PBX´s addresses are 123.123.123.123 and 231.231.231.231. Now you need to do some checks (with ping, for example) to only execute that at the right time. Wrap it all in a script, schedule it, and enjoy! You can search by dst-port instead of dst-address if you wish... Controlling RouterOS via CLI/Scripts is awesome. P.S. Mikrotik, please... Implement a DEBUGGER. PLEASE!!
Пікірлер: 26