friendly-bits

> * If a cron job is called while an invalid config exists, it correctly exists. Should it report_failure so people can receive a message? Checking on this... Will comment...

> * If a cron job is called while an invalid config exists, it correctly exists. Should it report_failure so people can receive a message? So the challenge here is...

While we're at it, maybe now it's a good time to stop using /root and move stuff to where it should normally be? I.e. probably to /etc/adblock-lean/.

> Seems super daring and ambitious to have config elements automatically changed It looks more impressive than it actually is. The logic is very simple. We check for critical issues...

The only shortcoming of this method (which I'm aware of) is that custom comments are not preserved after fixing the config. You essentially get a vanilla config with your existing...

> Just so I understand, valid old entries will be retained, but invalid old entries will be deleted and any needed replacements adds as defaults, right? So a custom config...

^ - parse_config(): set ${luci_conf_needs_fix} - parse_config(): fix a couple typos - parse_config(): remove ${legacy_keys) (unused variable) - parse_config(): catch another previously uncaught case of invalid entries - fix_config(): move...

Is there a realistic use case? @lynxthecat

While dnsmasq does support this, IMO blocking IP addresses is more efficient when done in the firewall (i.e. via nftables set and nftables rules). If there really is a use...

Hi, thank you for letting me know. I will look into both issues. In the meantime, if you would like to use other IP list sources, you can modify the...