I was a bit surprised by the rule matching logic in R80(.20).
I have a parent rule for Internal to DMZ traffic:
![](/legacyfs/online/checkpoint/73453_2018-11-01 14_35_51-SmartConsole (fwmgmt.networkschool.org).png)
And a parent rule for Internal to Internal traffic:
![](/legacyfs/online/checkpoint/73454_2018-11-01 14_37_14-SmartConsole (fwmgmt.networkschool.org).png)
In the Internal to Internal policy I have a rule for my Active Directory traffic:
![](/legacyfs/online/checkpoint/73457_2018-11-08 13_34_15-SmartConsole (fwmgmt.networkschool.org).png)
But as I missed a protocol in this bunch the traffic was dropped. But not on the rule I expected it to be dropped on:
![](/legacyfs/online/checkpoint/73455_2018-11-01 14_36_46-Log Details.png)
So why would it drop on the wrong rule here?
There seems to be an inconsistence in the logging as it goes from Internal to Internal on the left hand but on the right hand it declares it from Internal to DMZ.
![](/legacyfs/online/checkpoint/73458_2018-11-08 13_40_00-Interface_ eth0.101.png)
![](/legacyfs/online/checkpoint/73459_2018-11-08 13_40_45-Interface_ eth0.105.png)
Can anyone explain why this inconsistence behaviour occurs?
<< We make miracles happen while you wait. The impossible jobs take just a wee bit longer. >>