Diversion Diversion - the Router Ad-Blocker

[joe68000]

Add it to the wildcard-blacklist, if it's not in your hosts file already.

Diversion ---> el , 3, 1

Thank you! Diversion is fantastic @thelonelycoder!

 

[SomeWhereOverTheRainBow]

just wondering: why komputerswiat.pl is on the list?

It is just pre-compiled from several sources that are known not to break anything, I white list as needed. This has a mixture of places that has ads,malware, and trackers. I will update once a week.

 

[Asad Ali]

What is the best way to completely sinkhole a domain when using Diversion and Skynet? I want graph.instagram.com to go completely away! lol

I won't recommend blocking this URL with Diversion if you're also using Pixelserv-tls because this URL is known for bombarding Pixelserv-tls with retry attempts and it'll not only mess up with your "slu" but it'll also impact with Pixelserv-tls performance. It's best to use dnsmasq.conf.add file to directly route this URL to a null IP (0.0.0.0)

Here you'll find a handy way to how you can do it if you're not familiar with this concept:

https://github.com/RMerl/asuswrt-merlin/wiki/Custom-domains-with-dnsmasq#edit-dnsmasq-config-options

 

[joe68000]

I won't recommend blocking this URL with Diversion if you're also using Pixelserv-tls because this URL is known for bombarding Pixelserv-tls with retry attempts and it'll not only mess up with your "slu" but it'll also impact with Pixelserv-tls performance. It's best to use dnsmasq.conf.add file to directly route this URL to a null IP (0.0.0.0)

Here you'll find a handy way to how you can do it if you're not familiar with this concept:

https://github.com/RMerl/asuswrt-merlin/wiki/Custom-domains-with-dnsmasq#edit-dnsmasq-config-options

Thanks! I added this:

address=/graph.instagram.com/0.0.0.0
address=/app-analytics.snapchat.com/0.0.0.0

and restarted dnsmasq. but when I check it, this is what I see...

admin@host:/tmp/home/root# nslookup graph.instagram.com 192.168.2.1
Server:    192.168.2.1
Address 1: 192.168.2.1 host.

Name:      graph.instagram.com
Address 1: 192.168.2.3 192.168.2.3

I expected to see 0.0.0.0 as the address returned. What did I do wrong?

 

[Asad Ali]

Thanks! I added this:

address=/graph.instagram.com/127.0.0.1
address=/app-analytics.snapchat.com/127.0.0.1

and restarted dnsmasq. but when I check it, this is what I see...

admin@host:/tmp/home/root# nslookup graph.instagram.com 192.168.2.1
Server:    192.168.2.1
Address 1: 192.168.2.1 host.

Name:      graph.instagram.com
Address 1: 192.168.2.3 192.168.2.3

I expected to see 127.0.0.1 as the address returned. What did I do wrong?

Yep because you've used the loopback IP (127.0.0.1) use the null IP (0.0.0.0)

 

[dave14305]

Thanks! I added this:

address=/graph.instagram.com/127.0.0.1
address=/app-analytics.snapchat.com/127.0.0.1

and restarted dnsmasq. but when I check it, this is what I see...

admin@host:/tmp/home/root# nslookup graph.instagram.com 192.168.2.1
Server:    192.168.2.1
Address 1: 192.168.2.1 host.

Name:      graph.instagram.com
Address 1: 192.168.2.3 192.168.2.3

I expected to see 127.0.0.1 as the address returned. What did I do wrong?

You also have to whitelist them in Diversion.

 

[Asad Ali]

You also have to whitelist them in Diversion.

+1
I forget to add that part in my original post.

 

[joe68000]

You also have to whitelist them in Diversion.

Ah, ok. I am using 0.0.0.0 now and have them whitelisted!

Perfect, thanks!

 

[thelonelycoder]

The Entware maintainers have released updated packages. This now brings the official release of pixelserv-tls 2.3.1 to those that were patiently waiting for it.
Use ep in amtm or Diversion to update Entware packages.
Note that for those that updated pixelserv-tls manually or through Diversion to v2.3.1 need to restart pixelserv-tls after the update, in ep, 4.
Since both amtm and Diversion see no version change when it was previously updated to v2.3.1, this step is necessary.

 

[Skeptical.me]

The Entware maintainers have released updated packages. This now brings the official release of pixelserv-tls 2.3.1 to those that were patiently waiting for it.
Use ep in amtm or Diversion to update Entware packages.
Note that for those that updated pixelserv-tls manually or through Diversion to v2.3.1 need to restart pixelserv-tls after the update, in ep, 4.
Since both amtm and Diversion see no version change when it was previously updated to v2.3.1, this step is necessary.

Well, that was good timing. I was going to update manually today to 2.3.1.

Done. Cheers.

 

[L&LD]

Along with the pixelserv-tls 2.31 update, Unbound was also updated from 1.93 to 1.96.

I ran unbound and used 'i' to reconfigure it and it picked up the latest version.

Still no luck with the logging in Scribe though (locks up the GUI in System Log).

 

[Butterfly Bones]

Along with the pixelserv-tls 2.31 update, Unbound was also updated from 1.93 to 1.96.

I ran unbound and used 'i' to reconfigure it and it picked up the latest version.

Still no luck with the logging in Scribe though (locks up the GUI in System Log).

Likely this:

ep manage   Entware packages    -> upd avail
- syslog-ng              3.23.1-1  -> 3.25.1-1

I think it was the last update of syslog-ng from 3.20 to 3.23 that tripped us up a few weeks back.
Thankfully elorimer and cmkelley got a workaround quickly until that time was available to update Scribe and get it right.

Did you do the ep updates then get the errors?

I'll post and alert on this in the scribe thread. In the meantime, I'm going to wait until cmkelley responds there.

 

[L&LD]

@Butterfly Bones, thanks. I had the errors after updating to 384.15 Beta 1, but before doing the ep updates.

 

[XIII]

I rebooted my router yesterday and forgot Diversion (and Entware) get uninstalled.

So I reinstalled today and indeed immediately got the new pixelserv-tls v2.3.1 from Entware.

 

[thelonelycoder]

I rebooted my router yesterday and forgot Diversion (and Entware) get uninstalled.

Entware and Diversion don't get uninstalled when rebooting.

 

[XIII]

Entware and Diversion don't get uninstalled when rebooting.

On my router they do... (at least 4 times so far)

Might be caused by having NextDNS installed, as some other user here suggested?

 

[Skeptical.me]

for those wanting to try a generated list of domains try it out.
https://raw.githubusercontent.com/jumpsmm7/MyGeneratedDomainsList/master/My-GeneratedHosts.txt

With a Hosts list for Diversion don't you need to use this format?

https://raw.githubusercontent.com/mrtargaryen/hostsfile/master/facebook_blacklist

 

[Asad Ali]

With a Hosts list for Diversion don't you need to use this format?

Not anymore. Domains only hosts lists are now supported in Diversion.

 

[thelonelycoder]

Not anymore. Domains only hosts lists are now supported in Diversion.

Grudgingly, market pressure can be a convincing mind changer. Just as a hammer is

 

[Skeptical.me]

Not anymore. Domains only hosts lists are now supported in Diversion.

Oh, okay. How about that then. This is great.