Not able to block youtube using pfblockerng with customlist.
-
Hi Team,
I have prepared a custom list with few website which I need to block in our network. I was able to restrict other websites, where as I could not do it with Youtube.com. I could not trace-out the reason for this issue. I am using Easylist, Ads, Malicious and my custom list in DNSBL Feeds.Thanks,
Ram.
-
This :
did it for me.
That is, when I used youtube.com in a browser - I typed the URL, it was leading to the known error page (certs errors etc).
edit : but the question is wrong.
You'll will find out that app's in phones still work.
That's because they don't use the URL youtube.com to access youtube ....
-
@Gertjan try to block these domains:
www.youtube.com
m.youtube.com
youtubei.googleapis.com
youtube.googleapis.com
www.youtube-nocookie.com
-
@viktor_g I was just showing an example.
I guess @rdatla knows by now that "Youtube" use a lot of URLs... and very hard to block.
Most Phone apps even use URL that aren't even known.
-
@viktor_g I noticed I still get the ads when I used the YouTube app on AppleTV so; from your list I assume the m.youtube.com is the one need to add!
-
@NollipfSense said in Not able to block youtube using pfblockerng with customlist.:
from your list I assume the m.youtube.com is the one need to add!
Assuming could be replaced by being sure.
Use Diagnostics > Packet Capture to snif packets coming from your Apple TV that have a port 53 destination.
When the sniffer runs, start the Youtube app.
Stop the sniffer and have a look.
-
@Gertjan said in Not able to block youtube using pfblockerng with customlist.:
@NollipfSense said in Not able to block youtube using pfblockerng with customlist.:
from your list I assume the m.youtube.com is the one need to add!
Assuming could be replaced by being sure.
Use Diagnostics > Packet Capture to snif packets coming from your Apple TV that have a port 53 destination.
When the sniffer runs, start the Youtube app.
Stop the sniffer and have a look.Cool...the problem on my network the clients are natted on pfSense's LAN.
-
@NollipfSense said in Not able to block youtube using pfblockerng with customlist.:
clients are natted on pfSense's LAN
Throw away the firmware in these natting devices and put pfSense in place.
True, natting after pfSense hides a lot of info.
-
@Gertjan said in Not able to block youtube using pfblockerng with customlist.:
@NollipfSense said in Not able to block youtube using pfblockerng with customlist.:
clients are natted on pfSense's LAN
Throw away the firmware in these natting devices and put pfSense in place.
True, natting after pfSense hides a lot of info.
In my case, the natting is before pfSense...(the king of my LAN is the new Mikrotik RB450x4); so, I'll have to monitor IP > Firewall > Connections to see when the AppleTV YouTube app is talking to DNS. Yes, my system is double natted...seems okay with it as pfSense is king of my WAN.
