Chrome Bypasses YouTube Application Blocking

Product Discussion
,
1

I am aware of known issue 29679, “YouTube blocking may not work if YouTube traffic is using QUIC,” but I doubt that’s the full story.

I install a policy for Chrome to disable both DNS over HTTP and QUIC. For good measure, I also block outbound UDP and a variety of other things in the B One. (Its DNS proxy is enabled.) I clear all site data out of the browser. I flush the macOS DNS cache with dscacheutil -flushcache. Then, I restart the browser, type “youtube.com”, the page loads, and I can watch videos. Wireshark tells me it is using TLS 1.3.

Is anyone else seeing similar issues? This feature is not serving me and I’m not sure what to do next – set up a separate HTTP proxy, try to find a working set of filters, and then require everyone on the network to use it if they want to do any browsing? Not having to administer something like that was my main reason for buying a B One.

  • Chrome 127.0.6533.100
  • macOS 14.6.1
  • B One, Firmware 8.5.0 build 5627 (RC 2)
2

I’m happy to report that it looks like this was the result of a typo in a firewall rule that crept in while manually copying the configuration of the olde Surf SOHO into the new B One.