Using IP wildcard masks in security policy rules

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Using IP wildcard masks in security policy rules

L0 Member

I have been adding IP wildcard objects into security policy rules and they have been working until yesterday when I added some new rules with several wildcard objects.  I have looked on the support site to see if there are any limitations on how many wildcard objects you can use in a rule and/or in a policy and I have not found anything.  I have opened a ticket on the support site, but wondering if anyone else has seen any issues using wildcard masks for objects using v9.1.

 

Thank you

2 REPLIES 2

Community Team Member

Hi @RandyQueen ,

 

Were you able to get an answer ?

Are you seeing some error while configuring the rules or are they just not working as you'd expect ?

Any chance to provide some more details ?

 

Cheers,

-Kiwi.

 
LIVEcommunity team member, CISSP
Cheers,
Kiwi
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

No, I did not get an answer.  I am still waiting on an engineer to connect with me to review what happened as well.

 

We have over 2000 stores and we use the same IP address scheme in each of our stores - the last octet is the same for each device in each store, so we had been using EDLs for the devices and using up a lot of IP addresses.  We have been cloning existing rules and swapping the EDL for a wildcard mask and after confirming it was hitting the new rule, we would remove the EDL in the previously used rule and validate that traffic was not interrupted and hitting the new rule.  It had been working for several weeks, until the last rules that we created.  The traffic did not hit the new rule and for some reason even bypassed the existing rule and traffic was being blocked because it was hitting a rule further down the stack that did not have the same privileges.  The rules created were for one type of device and even traffic for a different device that had been working suddenly was not hitting that rule and getting blocked.

 

I could not find much documentation on the support site other than an explanation of how the wildcard worked and explaining that there could be issues with overlapping based on how much of the binary string was matched.

 

Thank you for asking,

 

Randy

  • 2469 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!