eibgrad DD-WRT Guru
Joined: 18 Sep 2010 Posts: 9336
|
Posted: Wed Oct 16, 2024 21:45 Post subject: |
|
I assume you're creating and disabling these restrictions via the GUI. What makes you think/assume you can readily re-enable them via the CLI using a cronjob?
I could understand the question if you told me you were managing the entire process via the CLI, as the following user has done.
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=329739
But even in his case, it's not clear what strategy/process is appropriate to initiate the rules, let alone make changes. But to the extent that can be determined, at least then I could understand your question about how to schedule THAT particular process (whatever it is).
I'm no expert w/ AR, so perhaps I'm missing something. But there just seems to be a disconnect here between working at the GUI level, then assuming there's some command that's going to re-enable your rule(s) via the CLI. If it's possible, it's likely going to be a bit more complex that a simple cronjob.
IOW, you have to define the "process" you're scheduling! AFAIK, it doesn't exist unless YOU make it so (just like the other user).
All things considered, it's probably just easier to ask Alexa or Siri to remind you to re-enable the restriction. _________________ ddwrt-blacklist-domains.sh * ddwrt-dns-monitor.sh * ddwrt-ovpn-client-backup.sh * ddwrt-ovpn-client-killswitch.sh * ddwrt-ovpn-client-watchdog.sh (UPDATED! 10/2/24) * ddwrt-ovpn-remote-access.sh * ddwrt-ovpn-server-watchdog.sh (UPDATED! 10/2/24) * ddwrt-ovpn-split-advanced.sh * ddwrt-ovpn-split-basic.sh * ddwrt-mount-usb-drives.sh * ddwrt-wol-port-forward.sh |
|