[AdBlock] Which trigger to reload lists?

Hello,
i've just found out that my adblock instance reloads every 30 seconds. I was getting mad to understand why my dns calls failed now and then.. well, that's it.
I configured it, as i assume is commonly done, with a trigger on my wan interface (dhcp6 interface). Well, it seems this interface has an ifupdate event every 5 minutes. So, my question: assuming it's not viable to keep adblock to reload every 5 minutes (killink dnsmasq) what should be the correct way? it seems adblock can't filter the event (for example waiting only for ifup events), so what should i do?
thanks

Provide your adblock config and the output of /etc/init.d/adblock status

it is really something connected to the wan6 interface.
Here is my config, i've now set the trigger interface to the wan_dhcp6_4 interface (that is a virtual interface created by the map package!) since the "real" interface (wan_dhcp6) has this event every 5 minutes

Thu Jun 12 06:25:22 CEST 2025 :: ACTION=ifupdate INTERFACE=wan_dhcp6
Thu Jun 12 06:30:22 CEST 2025 :: ACTION=ifupdate INTERFACE=wan_dhcp6
Thu Jun 12 06:35:23 CEST 2025 :: ACTION=ifupdate INTERFACE=wan_dhcp6
Thu Jun 12 06:40:23 CEST 2025 :: ACTION=ifupdate INTERFACE=wan_dhcp6
root@RUTTO:~# /etc/init.d/adblock status
::: adblock runtime information
  + adblock_status  : enabled
  + adblock_version : 4.4.1-r2
  + blocked_domains : 244 710
  + active_feeds    : adaway, adguard, adguard_tracking, oisd_big, reg_it
  + dns_backend     : dnsmasq (2.90-r4), /tmp/adblock-blocklist, 23.92 MB
  + run_utils       : download: /usr/libexec/wget-ssl, sort: /usr/libexec/sort-coreutils, awk: /usr/bin/gawk
  + run_ifaces      : trigger: wan_dhcp6_4 , report: -
  + run_directories : base: /tmp, dns: /tmp/adblock-blocklist, backup: /mnt/adblock, report: /tmp/adblock-report, jail: /tmp
  + run_flags       : shift: ✘, force: ✔, flush: ✘, tld: ✔, search: ✘, report: ✘, mail: ✘, jail: ✘
  + last_run        : mode: restart, 2025-06-12T06:11:52+02:00, duration: 0m 21s, 322.23 MB available
  + system_info     : QEMU Standard PC (i440FX + PIIX, 1996), x86/64, OpenWrt 24.10.1 r28597-0425664679 
root@RUTTO:~# cat /etc/config/adblock 

config adblock 'global'
        option adb_enabled '1'
        option adb_debug '0'
        option adb_safesearch '0'
        option adb_mail '0'
        option adb_report '0'
        option adb_dns 'dnsmasq'
        list adb_zonelist 'lan'
        option adb_tmpbase '/tmp'
        option adb_backupdir '/mnt/adblock'
        option adb_dnsdir '/tmp/adblock-blocklist'
        option adb_dnstimeout '20'
        list adb_feed 'adaway'
        list adb_feed 'adguard'
        list adb_feed 'adguard_tracking'
        list adb_feed 'oisd_big'
        list adb_feed 'reg_it'
        option adb_dnsforce '1'
        option adb_fetchcmd 'wget'
        list adb_trigger 'wan_dhcp6_4'

Nope, adblock only responds to ifup events, e.g. the relevant excerpt from the init script:

	for iface in ${trigger}; do
		procd_add_interface_trigger "interface.*.up" "${iface}" "${adb_init}" start
	done

Avoid WAN6 interfaces ... IMHO it's an old odhcpd v6 bug.
Use WAN4 or LAN4 instead.

not good to know :frowning:

well that's what i'm trying to do with the MAP interface, but it's virtual, my only wan interface is a dhcpv6 interface..
just wondering: why adblock is connected to interface going up and down? isn't it a matter of updating list? so a cron task shouldn't be better?

Than bin the trigger and add a cron reload, see the online readme.