[Solved] Custom CRON job gets deleted on every reboot

[QuisaZaderak]

In addition to my DLS and slow LTE line, I have also been using a Starlink connection for a few weeks. With IPv4, this works as desired.

IPv6 also works with the DSL provider and the LTE provider (unfortunately, you only get a 64 prefix with the DSL provider and no prefix at all with LTE, so not reasonably usable with multiple network segments).

Starlink IPv6 has a 56 prefix. However, the IPv6 connection always drops after a few minutes, so a regular call to /sbin/rtsol is necessary. Unfortunately, this can't seem to be set via System -> Cron in the GUI. Also I did not find a configuration option at the interface directly to accomplish this. So a custom CRON job entry via shell is necessary.

Therefore I log in directly to the OPNSense shell and edit the CRON jobs with CRONTAB -e. For this I add like the other existing lines the new line "*/2 * * * (/sbin/rtsol igb7) > /dev/null" and save with :wq. After that everything works as desired.  Until the next reboot of OPNSense. This entry is deleted every time, no matter if it is in the middle or as the last line. I must edit it every time after reboot again with CRONTAB -e.

Since Maltrail currently has the memory bug and the regular restart of the Maltrail sensor alone does not always help, it is currently more frequent reboots, which is then of course even more annoying.

How can I make this custom cron job permanent so that it survives a reboot (and maybe even shows up in the GUI under CRON)?

[Greelan]

Here’s a guide to adding a custom cron job that will stick and will be accessible to configure in the GUI: http://kb.unixservertech.com/other/networking/opnsense/cron-jobs

The description field in the action conf will show up in the GUI (the message field shows in the log)

[chemlud]

...or here

https://forum.opnsense.org/index.php?topic=10740.msg49334#msg49334

;-)

[Greelan]

You could also investigate using monit for this. It could monitor whether IPv6 is up and reload as needed

[Greelan]

Here’s a specific cron job example for checking a WAN connection: https://forum.opnsense.org/index.php?topic=18865.msg86224#msg86224

Shouldn’t be hard to adapt for IPv6

[QuisaZaderak]

I created a custom configd action like recommended. And it works. Thank you for your fast replies.

https://docs.opnsense.org/development/backend/configd.html