Hi Dave,
The rules which you have mentioned needs to be modified a bit.
Instead of "deny" using the "permit" action modifier will apply the normal forwarding logic.
All the below rules must be in same policy file.
Here is a sample.
entry HTTP_PACKETS_TO_10.234.0.0 {
If match all {
Protocol TCP;
destination-port 80;
source-address 10.234.0.0/16;
destination-address 10.234.0.0/16;
} then {
permit;
}
}
# same subnet but matching https traffic
entry HTTPS_PACKETS_TO_10.234.0.0 {
If match all {
Protocol TCP;
destination-port 443;
source-address 10.234.0.0/16;
destination-address 10.234.0.0/16;
} then {
permit;
}
}
entry HTTP_to_other_than_10.234.0.0/16 {
if match all {
protocol TCP ;
destination-port 80 ;
source-address 10.234.0.0/16 ;
}
then {
redirect-name ToBluecoat;
count WebHTTP;
}
}
entry HTTPS_to_other_than_10.234.0.0/16 {
if match all {
protocol TCP ;
destination-port 443 ;
source-address 10.234.0.0/16 ;
}
then {
redirect-name ToBluecoat;
count WebHTTPS;
}
}
Here is an article on how to configure flow redirect.
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-flow-redirect
I hope this is helps!