I have created some scripts, really tiny ones, that are meant to disable certain network interfaces when not in the office.
The scripts themselves are just simple one liners that are working well when started by manually. For some reason the scheduler does not start them reliable.
Please have a look at the screenshot to see the summary of it.
I followed the guidelines and do not see, where I have made a mistake. Permissions should be fine, clock is set, syntax should be okay, manual trigger works. But the scheduler is not reliable.
What is really confusing: OVPN_an is triggered by the scheduler, but OVPN_aus is not. Does anybody see the difference? I feel like blind…
Thanks for the hints.
I experimented with the permissions already, starting from default, going to everything and nothing.
The settings now reflect what makes sense to me and what is working on manual trigger. Following the rule that the scheduler should have the same permissions as the script.
Still OVPN_an is working and OVPN_aus is not. This seems to be not logical at all.
I included the logging thing, even though the scheduler and script reports run times.
This is not bringing security forward.
It makes scripting an adventure with a huge security risk. Ouch! In the end I need to protect my firewall with a firewall…