I love my mikrotik router because I can finally ‘control’ my 3 boys internet access!
Thing is I my scheduler times don’t start at the time I’ve set it? Guess I’m doing something wrong here.
I have SNTP client setup:
/system clock print
time: 08:08:58
date: may/26/2018
time-zone-autodetect: yes
time-zone-name: Europe/Amsterdam
gmt-offset: +02:00
dst-active: yes
Here’s one of my scheduled scripts:
1 ;;; This script enables all PC en PS4 firewall rules.Time 4 bed boys!
Enable Doolies at night may/27/2018 22:00:00 1d ip firewall filter enable [find comment=“PC JOEY”…
The scripts however kick-off at 20:00 instead of 22:00? I can also see that in winbox - scheduler - next run. Could the gmt-offset has something to do with this?
It works but it’s confusing me. I’d rather have my clock and my next run / scheduled times in sync.
What’s your RouterOS version? I did quick test with current 6.42.3, I have gmt-offset +02:00 too, and it looks ok. I entered start-time 14:40 and it started at 14:40.
I found one router with 6.38.5 and it works correctly there too, so I don’t know what can be wrong with yours. I assume the system time is correct, right?
For the lack of better ideas, try to upgrade. You should do it anyway, 6.38.5 has ugly vulnerability in WinBox service (it may not be a big problem if you have it protected with firewall, but it’s better to have up to date system).
I have updated my software to 6.42.3.
time:
time: 06:35:21
date: jun/05/2018
time-zone-autodetect: yes
time-zone-name: Europe/Amsterdam
gmt-offset: +02:00
dst-active: yes
Scheduler shows for one rule:
Start date Jun/06/2018 01:30:00 interval 1d 00:00:00 next run Jun/06/2018 23:30:00
Please report back tomorrow: will the job actually run at 23:30 Amsterdam time? It could well be just a bug at conversion between UTC time (I’m pretty sure ROS kernel runs at UTC time) in the print-out, specifically conversion of the next scheduled run time.