11-15-2023 04:25 PM
Hello,
I have bypassed the sqlnet inspection, in packet-tracer phase 3, it shows that it is bypassed:
Phase: 3
Type: CONN-SETTINGS
Subtype:
Result: ALLOW
Elapsed time: 3794 ns
Config:
class-map oracle-tcp-bypass
match access-list oracle-tcp-bypass
policy-map global_policy
class oracle-tcp-bypass
set connection advanced-options tcp-state-bypass
service-policy global_policy global
however, in phase 6, it says the packet is inspected:
Phase: 6
Type: INSPECT
Subtype: inspect-sqlnet
Result: ALLOW
Elapsed time: 14826 ns
Config:
class-map SQLNET-INSPECTION
match access-list SQLNET-INSPECTION
policy-map global_policy
class SQLNET-INSPECTION
inspect sqlnet
service-policy global_policy global
My question is, is the packet really being bypassed or inspected for sqlnet?
Cheers,
-Rouzbeh
Additional Information:
11-15-2023 04:32 PM
I dont think so
Check this link for bypass inspect
11-16-2023 07:27 AM
The packet won't be inspected. Packet-tracer is unwise sometimes. But why do you need tcp-state-bypass if you already have class-map defined for sqlnet where you can disable and enable inspection selectively? Deny in the corresponding ACL would mean "don't inspect" and permit would mean "inspect".
11-16-2023 08:54 AM
thank you!
11-19-2023 12:43 PM
Show service policy
This command can give you short view about if packet drop in policy or not.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide