This is incompatible but a little better in code flow. It's still apparent
that the static mode clashes with CARP so maybe we should stop giving CARP
the benefit of the doubt and the the user decide if the setup should be
static or dyamic CARP or no CARP?
Deal with case (2) and (3) in the lightest way possible. This requires
fixes and features for interface-related code, but it's a good field test. ;)
The static mode isn't really a good construct and will be moved to a checkbox
in the next commit.
Pages only call these to get lists but get_interface_ip*() functions want
a specific one. Handroll these cases and simplify the other end.
PR: https://github.com/opnsense/core/pull/5185
Wanted to do this every now and then since people were not
familiar with clog but never got around to do it. Now that
clog is gone it's easier to do so let's write a few lines
and extend as necessary. :)
It looks like `tail -f' doesn't watch the symlink and instead
tails the target file which makes nightly rotation invisible
and the log starts stalling so it means for any readers of
latest.log it shouldn't be a persistent read.
PR: https://github.com/opnsense/core/issues/4993
We shuffle the cron jobs around a bit to let the script start at
minute 1 of every hour which is close enough.
We might consider a soft-update of the link instead of removing
it every hour depending on how tail -f and such work, but for now
use what PHP has to offer.
PR: https://github.com/opnsense/core/issues/4993
authenticate_user() is not being called by anyone else so
move it to xmlrpc.php and extend it to allow for API keys
to work.
Since the authentication in this page is always bound to
local credentials it makes sense to extend the user-based
access with the API key-based access as they don't get in
the way of each other.
PR: https://github.com/travisghansen/hass-opnsense/discussions/6
Most of the system already uses it and users are informed about
it too. Might just be a good time to write a little manual page
for it...
While here some use of daemon -f suggests that configctl -d should
be used more widely than it is now.
To make verbatim script passthrough work we also need to introduce
a scripting option to reach the random sleep option afterwards.
We add a random delay of up to 25 minutes to the cron based operations
in order to give the update servers more room to breathe.
Download only if necessary, but verify and unpack unconditionally.
Add a cron job for nightly poll to be used with upcoming pending
script to "skim" the changelog for potential updates.
o allow repetitive metadata tags to be used, representing them as multiline options. Since \n can't exist in rules it should be rather save to concat repeating entries
o convert multiline items in the UI (rule info) (convert \n --> <br/>)
