Adblock support thread

Community Builds, Projects & Packages
306

@dibdot As you know, I have used your Adblock package nearly since your inception of it and with great efficiency and very little issues since that time. Cheers to that! :slight_smile:

Anyway, regarding my LEDE KidSafe configuration (https://forum.openwrt.org/t/kidsafe-or-guest-wifi-forced-safesearch-and-adblock/6559):

Adblock has stopped filtering for me specifically on my KidSafe network only. Everything else works fine. This configuration had worked consistently for some time now but seems to have broken on one of your recent updates. I always backup/restore my overall LEDE configuration and everything has worked well with regard to that.

Is there something in one of your recent major upgrades to Adblock that would potentially break this setup? Thank you for your time.

Some basic info (stripped down a bit):

etc/config/network:

config interface 'kidsafe'
	option _orig_ifname 'wlan2'
	option _orig_bridge 'false'
	option proto 'static'
	option ipaddr '192.168.3.1'
	option netmask '255.255.255.0'
	option delegate '0'
	option force_link '0'
	option type 'bridge'

etc/config/firewall:

config zone
	option name 'kidsafe'
	option input 'ACCEPT'
	option forward 'DROP'
	option output 'ACCEPT'
	option network 'kidsafe'

config rule
	option target 'ACCEPT'
	option proto 'tcp udp'
	option dest_port '53'
	option name 'KidSafe DNS'
	option src 'kidsafe'

config rule
	option enabled '1'
	option target 'ACCEPT'
	option proto 'udp'
	option dest_port '67-68'
	option name 'KidSafe DHCP'
	option src 'kidsafe'

config redirect 'adblock_dns_kidsafe'
	option name 'Adblock DNS KidSafe'
	option src 'kidsafe'
	option proto 'tcp udp'
	option src_dport '53'
	option dest_port '53'
	option target 'DNAT'

config forwarding
	option dest 'wan'
	option src 'kidsafe'

The main firewall rule in there which did all of the magic (much the same as your Force DNS rule) in which the Adblock would not work without on the KidSafe network is:

config redirect 'adblock_dns_kidsafe'
	option name 'Adblock DNS KidSafe'
	option src 'kidsafe'
	option proto 'tcp udp'
	option src_dport '53'
	option dest_port '53'
	option target 'DNAT'

Is there any troubleshooting that I can do to figure this out further? Thanks

So what I know so far is that devices on my regular 2.4GHz and 5GHz bands on LAN default LEDE settings essentially, that works well as always. The KidSafe network used to work with Adblock filtering but has since stopped working. If I switch those kids devices over to the regular networks, adblock works again. My setup does consist of two instances of dnsmasq which has worked great. I have not tried anything yet with regard to multiple Adblock instances (which I believe you mentioned in recent post).