Resolved! Sudden issues with address objects in policy rules- behaves as if 0.0.0.0/0 is set
Since about 4 days I am experiencing a critical problem in relation to policy rules with address objects and suspect an update to address/region objects has caused this mess as I am experiencing this issue with: - manually added address objects- predefined country regions- dynamic address groups (based on tags- even if the address group is empty...




