Diversion Does the new experimental YouTube feature cause dcd tainted crashes?

skeal

Part of the Furniture
Since learning that pixelserv-tls causes dcd tainted crashes because of the use of a virtual interface, does the new YouTube add blocking feature use a virtual interface like pixelserv-tld does or is thsi another issue? The YouTube add blocker is the only change on the router that Iv'e made besides adding FlexQOS this last week. Anybody have any ideas or see the samething in their logs? Thanks for your help in advance. I searched the topic and couldn't produce any relevant results.
 

SomeWhereOverTheRainBow

Part of the Furniture
Since learning that pixelserv-tls causes dcd tainted crashes because of the use of a virtual interface, does the new YouTube add blocking feature use a virtual interface like pixelserv-tld does or is thsi another issue? The YouTube add blocker is the only change on the router that Iv'e made besides adding FlexQOS this last week. Anybody have any ideas or see the samething in their logs? Thanks for your help in advance. I searched the topic and couldn't produce any relevant results.
No
 

CriticJay

Senior Member
Since learning that pixelserv-tls causes dcd tainted crashes because of the use of a virtual interface, does the new YouTube add blocking feature use a virtual interface like pixelserv-tld does or is thsi another issue? The YouTube add blocker is the only change on the router that Iv'e made besides adding FlexQOS this last week. Anybody have any ideas or see the samething in their logs? Thanks for your help in advance. I searched the topic and couldn't produce any relevant results.

The Youtube ad-blocking feature does not use a virtual interface; rather it has a semi-complicated script which tries to determine all the "youtube ad domains" for your particular IP, and then send all requests to those domains to your designated blackhole IP (which would be either 0.0.0.0 for NON-pixelserv users, and the Pixelserv IP for pixelserv users).
 

skeal

Part of the Furniture
The Youtube ad-blocking feature does not use a virtual interface; rather it has a semi-complicated script which tries to determine all the "youtube ad domains" for your particular IP, and then send all requests to those domains to your designated blackhole IP (which would be either 0.0.0.0 for NON-pixelserv users, and the Pixelserv IP for pixelserv users).
Thanks, great explanation!!
 

heysoundude

Part of the Furniture
The Youtube ad-blocking feature does not use a virtual interface; rather it has a semi-complicated script which tries to determine all the "youtube ad domains" for your particular IP, and then send all requests to those domains to your designated blackhole IP (which would be either 0.0.0.0 for NON-pixelserv users, and the Pixelserv IP for pixelserv users).
now if I could just get diversion to do the same for the Reuters app on my iphone...
 

SomeWhereOverTheRainBow

Part of the Furniture
The Youtube ad-blocking feature does not use a virtual interface; rather it has a semi-complicated script which tries to determine all the "youtube ad domains" for your particular IP, and then send all requests to those domains to your designated blackhole IP (which would be either 0.0.0.0 for NON-pixelserv users, and the Pixelserv IP for pixelserv users).
Correction, it doesn't send them to 0.0.0.0 or the pixelservtls ip. Instead through trickery, it is sent to a previously captured YouTube ad video ip using /etc/host(s) (or a similar host-record method). Unless @thelonelycoder changed the original way the initial script did the trickery.
 

CriticJay

Senior Member
Right, thanks for the correction. The way the author described it (on the pihole forum), by doing what you described it's possible to avoid or reduce the prevalence of ads while watching YouTube.
 

Latest threads

Sign Up For SNBForums Daily Digest

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