Hi,

I have a script installed in my Mikrotik router, but it´s not running in the desired time.

https://snag.gy/a6xq9N.jpg



Can you tell me what´s wrong here ?

Thanks

You didn't specify any script to run "on-event"

Thanks a lot.

My script didn´t run at the specified time, am I forgetting anything ?

In the field "On Event" I put the script name: "Mac-Change"

Are you sure that the script is syntactically correct ? Script with errors could not "run".

The script is working fine, when I run it I get the message in the Log area:

New MAC 602d0cbf1d28

And the router´s MAC addres is changed, but it´s not running in the scheduller.

Need I mark any option in the "Policy" area ?

Are you sure that the script is syntactically correct ? Script with errors could not "run".

It doesn't say much
post the code of your script.

I got the script from this forum:

http://forum.mikrotik.com/viewtopic.php?t=102357

I created a new schedul - Let´s see tomorrow what´s happen...

It doesn't say much
post the code of your script.

Your On Event should read

Your On Event should read

Code: Select all

/system script run Mac-Change

No, it is enough to specify valid script name.

No, it is enough to specify valid script name.

I have had issues with that in the past, so I have always put the whole command in.

Unfortunately my scripts didn´t work. The router´s mac addres wasn´t changed, and I can´t see any data about
Mac changes in the log area:




When I run the script by hand I can see the information in the log area:

Do both the script and the schedule have full permissions?

Can you tell me how enable permissions in the scripts ?

In the "Policy" section. Try marking all of the boxes.
Also, if you post the script, we can test it and see what's going on.

This is the script:

http://forum.mikrotik.com/viewtopic.php?t=102357


I did your recommendation and check all box in the Policy area:



Let´s go to see what´s happen tomorrow...

In the "Policy" section. Try marking all of the boxes.
Also, if you post the script, we can test it and see what's going on.

Screen Shot 2016-04-29 at 7.22.38 AM.png

Screen Shot 2016-04-29 at 7.22.50 AM.png

Problem solved !

Thanks a lot for your answers .

Glad to have helped.