What's new

[Release] AB-Solution 3 - The Ad Blocking Solution

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
after the reboot, I suppose it will be back to vortex merlin firmware? By the way, right now I am using a SD card reader with 1GB micro SD, if I want to switch the reader to another one. Do I need to switch off router to do that?
Routers don't have a factory installed image of the firmware stored someplace on it. It restores default settings for the installed firmware.
There's a safely remove disk button for each device plugged in. Use that.
 
Thanks for this really neat ab solution.

I noticed one small issue, I was unable to update my Raspberry Pi after starting to use this. A quick check in the log when updating the Pi showed "archive.raspberrypi.org" to be on the blacklist, (I'm using the standard hosts file), not sure why, but whitelisting it was easy enough and the Pi now updates.

Anyone else with a Pi might want to whitelist that domain.
 
I couldn't ping or get a response from "archive.raspberrypi.org", I looked in the ab log and it resolved to 127.0.0.1, whitelisting it did the trick.

I've just removed it from the whitelist and now it resolves, so I don't know any more what occurred?
 
Im using shooter40sw too ... resolves ok for me
Code:
Jan 28 14:06:18 dnsmasq[1193]: query[A] archive.raspberrypi.org from 192.168.2.60
Jan 28 14:06:18 dnsmasq[1193]: forwarded archive.raspberrypi.org to 10.0.0.1
Jan 28 14:06:19 dnsmasq[1193]: reply archive.raspberrypi.org is <CNAME>
Jan 28 14:06:19 dnsmasq[1193]: reply lb.raspberrypi.org is 93.93.130.104
Jan 28 14:06:19 dnsmasq[1193]: reply lb.raspberrypi.org is 46.235.227.11
Jan 28 14:06:19 dnsmasq[1193]: reply lb.raspberrypi.org is 93.93.128.133
Jan 28 14:06:19 dnsmasq[1193]: reply lb.raspberrypi.org is 93.93.128.230
Jan 28 14:06:19 dnsmasq[1193]: reply lb.raspberrypi.org is 93.93.130.39
Jan 28 14:06:19 dnsmasq[1193]: reply lb.raspberrypi.org is 93.93.130.214
 
I couldn't ping or get a response from "archive.raspberrypi.org", I looked in the ab log and it resolved to 127.0.0.1, whitelisting it did the trick.
are you using dnscrypt? @eighteen had a similar issue and turned out to be a dnscrypt issue (CNAME problem perhaps) He updated and it all came good.
 
With Pixelserv enabled I have one legit http site that is blocked, I added it to the whitelist and it's still blocked. If I turn off Pixelserv it works without a problem. Clearly I'm missing something, what do I need to do to get it to work with Picelserv on?
 
I rechecked what I did.

Reset to the standard host file and ping "archive.raspberrypi.org"

Code:
Ping request could not find host archive.raspberrypi.org. Please check the name and try again.

Output from ab log is

Code:
Jan 28 15:00:41 dnsmasq[23706]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23706]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23706]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23706]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23907]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23908]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23907]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23907]: dnssec-query[DS] org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23908]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23908]: dnssec-query[DS] org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23908]: validation archive.raspberrypi.org is ABANDONED
Jan 28 15:00:41 dnsmasq[23908]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.128.133
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.130.104
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 46.235.227.11
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.130.39
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.128.230
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.130.214
Jan 28 15:00:41 dnsmasq[23907]: validation archive.raspberrypi.org is ABANDONED
Jan 28 15:00:41 dnsmasq[23907]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:8
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:5
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:7
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:5
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:7
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:6
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:6
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:9

I then whitelist "archive.raspberrypi.org" and ping again..

Code:
Pinging lb.raspberrypi.org [2a00:1098:0:82:1000:13:0:7] with 32 bytes of data:
Reply from 2a00:1098:0:82:1000:13:0:7: time=12ms
Reply from 2a00:1098:0:82:1000:13:0:7: time=12ms
Reply from 2a00:1098:0:82:1000:13:0:7: time=11ms
Reply from 2a00:1098:0:82:1000:13:0:7: time=12ms

Ping statistics for 2a00:1098:0:82:1000:13:0:7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 12ms, Average = 11ms

And again from ab log

Code:
Jan 28 15:14:50 dnsmasq[25432]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[25432]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[25432]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[25432]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[27119]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[27120]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[27119]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[27119]: validation result is SECURE
Jan 28 15:14:50 dnsmasq[27119]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.128.133
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.130.39
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 46.235.227.11
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.130.214
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.130.104
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.128.230
Jan 28 15:14:50 dnsmasq[27120]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[27120]: validation result is SECURE
Jan 28 15:14:50 dnsmasq[27120]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:5
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:7
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:5
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:9
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:6
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:6
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:8
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:7

I do have dnscrypt, already latest version. I'll reinstall and see what happens then.
 
With Pixelserv enabled I have one legit http site that is blocked, I added it to the whitelist and it's still blocked. If I turn off Pixelserv it works without a problem. Clearly I'm missing something, what do I need to do to get it to work with Picelserv on?
what is the website?.... if it is not in the host list then it should not even be passed to pixelserv
 
I rechecked what I did.

Reset to the standard host file and ping "archive.raspberrypi.org"

Code:
Ping request could not find host archive.raspberrypi.org. Please check the name and try again.

Output from ab log is

Code:
Jan 28 15:00:41 dnsmasq[23706]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23706]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23706]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23706]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23907]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23908]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:00:41 dnsmasq[23907]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23907]: dnssec-query[DS] org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23908]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23908]: dnssec-query[DS] org to 127.0.0.1
Jan 28 15:00:41 dnsmasq[23908]: validation archive.raspberrypi.org is ABANDONED
Jan 28 15:00:41 dnsmasq[23908]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.128.133
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.130.104
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 46.235.227.11
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.130.39
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.128.230
Jan 28 15:00:41 dnsmasq[23908]: reply lb.raspberrypi.org is 93.93.130.214
Jan 28 15:00:41 dnsmasq[23907]: validation archive.raspberrypi.org is ABANDONED
Jan 28 15:00:41 dnsmasq[23907]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:8
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:5
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:7
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:5
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:7
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:6
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:6
Jan 28 15:00:41 dnsmasq[23907]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:9

I then whitelist "archive.raspberrypi.org" and ping again..

Code:
Pinging lb.raspberrypi.org [2a00:1098:0:82:1000:13:0:7] with 32 bytes of data:
Reply from 2a00:1098:0:82:1000:13:0:7: time=12ms
Reply from 2a00:1098:0:82:1000:13:0:7: time=12ms
Reply from 2a00:1098:0:82:1000:13:0:7: time=11ms
Reply from 2a00:1098:0:82:1000:13:0:7: time=12ms

Ping statistics for 2a00:1098:0:82:1000:13:0:7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 12ms, Average = 11ms

And again from ab log

Code:
Jan 28 15:14:50 dnsmasq[25432]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[25432]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[25432]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[25432]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[27119]: query[A] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[27120]: query[AAAA] archive.raspberrypi.org from 192.168.1.8
Jan 28 15:14:50 dnsmasq[27119]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[27119]: validation result is SECURE
Jan 28 15:14:50 dnsmasq[27119]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.128.133
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.130.39
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 46.235.227.11
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.130.214
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.130.104
Jan 28 15:14:50 dnsmasq[27119]: reply lb.raspberrypi.org is 93.93.128.230
Jan 28 15:14:50 dnsmasq[27120]: forwarded archive.raspberrypi.org to 127.0.0.1
Jan 28 15:14:50 dnsmasq[27120]: validation result is SECURE
Jan 28 15:14:50 dnsmasq[27120]: reply archive.raspberrypi.org is <CNAME>
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:5
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:7
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:5
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:9
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:82:1000:13:0:6
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:6
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:8
Jan 28 15:14:50 dnsmasq[27120]: reply lb.raspberrypi.org is 2a00:1098:0:80:1000:13:0:7

I do have dnscrypt, already latest version. I'll reinstall and see what happens then.
looks like a dnscrypt issue to me (dnsmasq is forwarding the query)..... is the dnscrypt server you are using enabled for dnssec?
 
  • Like
Reactions: bmb
looks like a dnscrypt issue to me (dnsmasq is forwarding the query)..... is the dnscrypt server you are using enabled for dnssec?

Thank you, I'll look into it when time permits, good to know where the issue lies.
 
With Pixelserv enabled I have one legit http site that is blocked, I added it to the whitelist and it's still blocked. If I turn off Pixelserv it works without a problem. Clearly I'm missing something, what do I need to do to get it to work with Picelserv on?
Did you process the whitelist after editing in (el)?
You have to do that.
 
Thank you, I'll look into it when time permits, good to know where the issue lies.
This clearly is not an AB issue, whatever script you run beside AB-Solution is blocking archive.raspberrypi.org as evidenced by the log file entries:
Jan 28 15:14:50 dnsmasq[25432]: forwarded archive.raspberrypi.org to 127.0.0.1

AB-Solution uses either 0.0.0.0 or your pixelserv-tls IP to block hosts, never 127.0.0.1
 
I did process the white list after I added bangordailynews.com, still doesn't work..
That host is not blocked.. so no point in whitelisting it
Code:
Jan 28 23:02:45 dnsmasq[2863]: query[A] bangordailynews.com from 192.168.2.60
Jan 28 23:02:45 dnsmasq[2863]: forwarded bangordailynews.com to 10.0.0.1
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.128
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.241
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.92
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.134
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.186
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.101
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.34
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.121

However its a nasty little site that spawns a load of other lookups, some of which are blocked. The site may partially not load because of that.
 
That host is not blocked.. so no point in whitelisting it
Code:
Jan 28 23:02:45 dnsmasq[2863]: query[A] bangordailynews.com from 192.168.2.60
Jan 28 23:02:45 dnsmasq[2863]: forwarded bangordailynews.com to 10.0.0.1
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.128
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.241
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.92
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.134
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.186
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.101
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.34
Jan 28 23:02:45 dnsmasq[2863]: reply bangordailynews.com is 54.192.139.121

However its a nasty little site that spawns a load of other lookups, some of which are blocked. The site may partially not load because of that.

Thanks for the info, so is there no way around it?
 
Thanks for the info, so is there no way around it?
Well as you have discovered, you can turn pixelserv off to kill the responses to the https lookups. Or you can follow the log file and gradually whitelist some of the blocked hosts until you can recover the functionality you are happy with. By the way, with this kind of site, on the first visit pixelserv will take some time to generate a load of certificates on the fly... this may appear to make the site inaccessible, but on subsequent visits the site will load.
 
I found a problem with AB-solution, I noticed that youtube history is not updated/recorded/counted when Ab-blocker is on, don't know why or how, and I don't know if that is something you can fix, but its not a big deal to me.
 
Last edited:
I found a problem with AB-solution, I noticed that youtube history is not updated/recorded/counted when Ab-blocker is on, don't know why or how, and I don't know if that is something you can fix, but its not a big deal to me.
Some of the google hosts are blocked, which one is a matter of finding out through looking at the (f) option and select 2. Then browse and make a good guess which of the blocked hosts may be the culprit.
 
I found a problem with AB-solution, I noticed that youtube history is not updated/recorded/counted when Ab-blocker is on, don't know why or how, and I don't know if that is something you can fix, but its not a big deal to me.

I just whitelist youtube.com and history is back.
 
Status
Not open for further replies.

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top