Hi,
I’ve got the following set of rules:
/ip firewall filter
add action=drop chain=forward dst-port=53 layer7-protocol=facebook protocol=udp \
src-address-list=!non_restricted time=8h-11h59m,sun,mon,tue,wed,thu,fri,sat
add action=drop chain=forward dst-port=53 layer7-protocol=facebook protocol=udp \
src-address-list=!non_restricted time=13h-17h,sun,mon,tue,wed,thu,fri,sat
add action=drop chain=forward dst-port=53 layer7-protocol=instagram protocol=\
udp src-address-list=!non_restricted time=8h-11h59m,sun,mon,tue,wed,thu,fri,sat
add action=drop chain=forward dst-port=53 layer7-protocol=instagram protocol=\
udp src-address-list=!non_restricted time=13h-17h,sun,mon,tue,wed,thu,fri,sat
add action=drop chain=forward dst-port=53 layer7-protocol=youtube protocol=udp \
src-address-list=!non_restricted time=8h-11h59m,sun,mon,tue,wed,thu,fri,sat
add action=drop chain=forward dst-port=53 layer7-protocol=youtube protocol=udp \
src-address-list=!non_restricted time=13h-17h,sun,mon,tue,wed,thu,fri,sat
The idea here is to keep these rules inactive from 17:00:00 to 08:00:00 and from 11:59:00 to 13:00:00
The system clock is always up to date, syncronized to at least 2 NTP servers. The problem is that once these rules go inactive they won’t activate again automatically when they’re supposed to (13:00:00 to 17:00:00 and from 08:00:00 to 11:59:00), the only way for them to “work again” is for me to disable a single one of these, once I do this all the rules start working again (as in they get active when they are supposed to) untill a full cycle ends (ie. goes on, then goes off, it keeps off next time doesn’t matter what happens).
has anyone experienced something like this? Routers are on the latest BFO train (6.34.6)