I have the following PBR rules for specific sites to bypass our content filter https filtering. The google filter is not working properly. I see counts go up when attempting to access drive.google.com (for my google rule), but traffic still ends up running through my catch all policy (verizon443) and hits the filter (user gets back untrusted connection warning)
1 ;;; Facebook Vbypass
chain=prerouting action=mark-routing new-routing-mark=VBypass
passthrough=yes src-address=10.99.0.0/16 content=facebook log=no
log-prefix=“”
2 ;;; Gmail VBypass
chain=prerouting action=mark-routing new-routing-mark=VBypass
passthrough=yes src-address=10.99.0.0/16 content=gmail log=no
log-prefix=“”
3 ;;; Google VBypass
chain=prerouting action=mark-routing new-routing-mark=VBypass
passthrough=yes protocol=tcp src-address=10.99.0.0/16 dst-port=443
content=google log=no log-prefix=“”
4 ;;; Wells VBypass
chain=prerouting action=mark-routing new-routing-mark=VBypass
passthrough=yes src-address=10.99.0.0/16 content=wellsfargo log=no
log-prefix=“”
5 chain=prerouting action=mark-routing new-routing-mark=VBypass
passthrough=yes src-address=10.99.0.0/16 content=mail.google.com log=no
log-prefix=“”
6 chain=prerouting action=mark-routing new-routing-mark=verizon443
passthrough=no protocol=tcp src-address=10.99.0.0/16 dst-port=443
log=no log-prefix=“”
7 chain=prerouting action=mark-routing new-routing-mark=verizon80
passthrough=no protocol=tcp src-address=10.99.0.0/16 dst-port=80 log=no
log-prefix=“”
CCR1036-12G-4S 6.24 ROS