02-05-2023, 02:20 PM
Well... There doesn't seem to be a fix for this at the moment.
I did find a workaround, which is to create two schedules in the same profile.
Following the example above of covering Wednesday 18:00 EST to 20:00 EST.
This translates to Wednesday 23:00 UTC to Thursday 01:00 UTC, which is a problem for iptables.
The workaround is to create two schedules in the following way:
- Wednesday 18:00 EST to 19:00 EST which translates to Wednesday 23:00 to Thursday 00:00 UTC
- Wednesday 19:00 EST to 20:00 EST which translates to Thursday 00:00 to Thursday 01:00 UTC
This effectively covers the intended schedule of Wednesday 18:00 to 20:00 EST.
I hope this helps anyone out there with the same issue :-)
I did find a workaround, which is to create two schedules in the same profile.
Following the example above of covering Wednesday 18:00 EST to 20:00 EST.
This translates to Wednesday 23:00 UTC to Thursday 01:00 UTC, which is a problem for iptables.
The workaround is to create two schedules in the following way:
- Wednesday 18:00 EST to 19:00 EST which translates to Wednesday 23:00 to Thursday 00:00 UTC
- Wednesday 19:00 EST to 20:00 EST which translates to Thursday 00:00 to Thursday 01:00 UTC
This effectively covers the intended schedule of Wednesday 18:00 to 20:00 EST.
I hope this helps anyone out there with the same issue :-)