10-21-2021 03:59 AM
Hello!
I have some question about session synchronization in HA Clustering (geographic cluster). All firewalls in HA clustering use the first rule for traffic that should not match it, this only happens on geoclustered firewalls. Later, the rules are processed correctly, but the first one is always used, so I see incorrect traffic in the logs.
Example:
Policy "First": From TRUST zone and 192.168.1.1 src.address to UNTRUST zone 8.8.8.8 dst.address application any action DROP.
Log: From GUEST zone and 10.100.100.1 src.address to DMZ zone 1.1.1.1 dst.address action ALLOW used policy "First".
It doesn't make sense, but I did the configuration in the lab and it works the same there, I think it is related to session synchronization and flooding information about these sessions to the neighbors. However, I cannot find an explanation for this behaviour in the documentation. Can anyone explain it?
Regards!
10-23-2021 05:09 AM
The only thing that comes to mind is that perhaps "First" is a negate rule.
So, if traffic is NOT coming from 192.168.1.1. to 8.8.8.8 then allow... policy log would show First.
10-25-2021 03:42 AM
Hello.
Thank you for your answer.
Can you explain it more precisely? Yes, action for "First" rule is drop, rule log only on session end.
I can see this behaviour only in HA clustering members so it can be indication.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
