Figure out how the client connects to the resource that you want to block. Need target FQDNs, IP address(es), and ports. This requires logging your traffic, and knowing whether the client device is subject to Standard Web, Transparent Web, Both, or Neither. By default, Firewall Rules only log blocked traffic, but you can log allowed traffic as well.
In the case of Chrome talking to Google, the traffic is probably running on UDP 443 (QUIC). By default, this will evade your web filter. Add a firewall rule to block UDP 443 so that it is forced to use TCP 443 and Webfilter.
Figure out how the client connects to the resource that you want to block. Need target FQDNs, IP address(es), and ports. This requires logging your traffic, and knowing whether the client device is subject to Standard Web, Transparent Web, Both, or Neither. By default, Firewall Rules only log blocked traffic, but you can log allowed traffic as well.
In the case of Chrome talking to Google, the traffic is probably running on UDP 443 (QUIC). By default, this will evade your web filter. Add a firewall rule to block UDP 443 so that it is forced to use TCP 443 and Webfilter.
