filter out unrelated multicast traffic from reporting --- update 4.2.2-4
fixed wrongly detected NX domains in adblock reporting
remove existing pcap files when restarting/stopping adblock to prevent problems when changing tcpdump parameters --- update 4.2.2-3
bugfix: users reported unexpected side effects with the newly introduced rpc-sys ubus service, reverted that part
*bugfix: made "tcpdump" optional --- update 4.2.2-2
removal of a superfluous opkg code block (missed in the last commit)
cosmetics --- update 4.2.2-1
get rid of the opkg dependency
fixed remaining hagezi category issues
adblock still depends on 'gawk', but also accepts busybox awk. The readme describes two officially unsupported installation variants. --- update 4.2.1-1
added full 1Hosts feed support (4 categories)
changed the OISD list sources to alternate wildcard domains syntax
used only the adguard source in default config
fixed a needless reload delay plus a few cosmetics --- update 4.2.0-1
new gawk dependency
full hagezi support (all 32 categories)
refine Stevenblack support
refine whitelist handling
fixed tcpdump command line for ports other than 53 --- update 4.1.5-11
removed an accidentally commited flag of the upcoming adblock 5.x, this fixes a startup regression without trigger interface
--- update 4.1.5-10
made the DNS Reporting / tcpdump parsing code more capable
small init fixes
update readme --- update 4.1.5-9
minimal fix with reporting interface 'any' --- update 4.1.5-8
optimized oisd download sources (use wildcard variants which are much smaller)
removed superfluous version information/function
unbound: fix domain search regression
add lightswitch05 source
auto-whitelist ext. dns lookup domain
add public doh server blocklist source
whitespace fixes in adblock.sources --- release 4.1.3
fix a small json syntax issue in adblock.sources
add easylist addon to reg_fr source
add switch 'adb_fetchinsecure' to allow insecure downloads without certificate check (disabled by default)
better explain 'adb_fetchparm' in readme
add a tcpdump option to resolve IPs in adblock reporting, set 'adb_represolve' accordingly (disabled by default). If enabled tcpdump will perform a reverse DNS (PTR) lookup for each IP address
add 'stalkerware' source
fix regex to prepare google safesearch domains --- release 4.1.2
preserve DNS cache after adblock processing (unbound & bind)
fix redirect issue with oisd basic url
cosmetics --- release 4.1.1
support the RPZ trigger 'RPZ-CLIENT-IP' to always allow/block certain clients based on their IP (currently only supported by bind!)
avoid promiscuous mode in tcpdump setup for adblock reporting
speed up dns report preparation
support dns report mailing (/etc/init.d/adblock report mail)
fix bind autodetection
update LuCI-frontend (separate PR)
update readme --- release 4.1.0-3
add a restrictive "jail mode only" variant, just point your jail directory to your primary dns directory
update readme release 4.1.0-2
add adguard_tracking source (list with cname trackers)
optimize/sort output of active sources in status
optimize log output in EMails --- release 4.1.0
major source changes:
split oisd.nl in basic and full variant
add swedish regional list
made archive categories for shallalist and utcapitole selectable via LuCI
made all list variants of energized and stevenblack selectable via LuCI
udhcpc is the DHCP client fetching a WAN address from your ISP for your WAN interface. Nothing to do with adblock (or DNS) by itself.
Does your router get WAN address when adblock is disabled?
But you seem to have a lot of blocklists loaded. You might test first with only a few lists. And you might reboot the router one more time so that there are surely no leftovers in dnsmasq tmp from the previous ablock version.
My router gets a WAN address also when adblock is enabled.
As far as I can see adblock2 is working without a problem. I just don't understand the errormessages in the log.
My router has plenty of ram (512 MB), so I thought is is not a problem to enable almost every list.
OK, please make a "/etc/init.d/dnsmasq restart" for two times. First with enabled block lists and second time without adblock (after /etc/init.d/adblock stop). In both cases please check the log for dnsmasq/dhcpc errors like you've posted above.
So dns hijacking is no longer an option with adblock2?
I haven't mastered wrapping firewall rules in procd instance, but if you'd want to bring back the pixelserv, I found out uhttpd is really easy to include in PROCD instance.
On ipq806x LEDE Reboot CURRENT r2437+12 with uclient-fetch and ustream-mbedtls installed, adblock2 fails with error: fetch utility 'uclient-fetch' or 'wget' not found. Maybe the below will help:
root@EA8500:~# which /usr/bin/wget* root@EA8500:~# which uclient-fetch /bin/uclient-fetch root@EA8500:~# which /bin/wget* /bin/wget root@EA8500:~# ls -la $_ lrwxrwxrwx 1 root root 13 Dec 10 16:24 /bin/wget -> uclient-fetch
Still it's all about dns spoofing/hijacking but we do not longer need all the firewall/pixel server stuff for that. The dns server itself returns a simple 'NXDOMAIN'. This is nothing but Non-eXistent Internet or Intranet domain name, if domain name is unable to resolve using the dns server, a condition called the 'NXDOMAIN' occurred.
By DNS hijacking I meant that if I have a client in the local network with hardcoded DNS (rather than using DNS server offered by DHCP) it will no longer be forced to use my router's dns server, will it now, without firewall rules?
Ah, sorry, missed that, I was hoping adblock2 would auto-discover what I have installed.
adblock supports a wider range of router modes, incl. AP modes. Therefore it makes no sense to set firewall redirects like that. (same applies to adblock 1.x)
a guy who changed the default ssl-backend can add two config options, too.
a positive side effect: you could use other tools like aria2 ...
The initial adblock_1.9.99-pre0-1_all ran perfectly well for me. Now adblock_1.9.99-pre1-1_all is also running well perfectly for the past 12-14 hours or so. No issues to report on my end as far as functionality goes.
I must admit, I do wish that there still remained an option to keep the pixel server running to replace all of the DNS-related errors that come up now with this NXDOMAIN method. But anyway, I trust in your judgement and coding work 100% and I will continue testing all future releases as they are released.
thanks for testing!
Do you have example urls with "broken links" where ads are not delivered by https server? For ad related content from https server you will receive broken links, even with adblock 1.x cause we cannot redirect secured connections.
Just want to say thanks for this! I run your current version published in trunk (1.5.4-1 with the Luci counter part), and it's a great tool. Thanks for continuing to support it!
Tested on my TP-Link Archer C2600 and my travel-router GLi AR150.
Works like a charm! I love it.
Especially the AR150 can handle this version much easier than the previous version.
