Lately I have seen some occasions where Source or Destination fields in NAT or Security rules show up as "null" in the main table. Earlier, when I worked on this project, they showed up as "any". In some rules they still show up as "any", not all are showing "null".
If I edit these rulles individually, the difference is that the "broken" ones show as "any" (all lower case), the others show "Any" (initial capital).
I can fix the problem (at least momentarily) by selecting the address "any" and deleting it. Then it suddenly turns into the proper "Any", and now it is OK.
I have a feeling that I fixed this on my rules, but that it reappeared when I returned to the project later, but I cannot definitely prove it (yet).
Anyone else seen this problem?
It is problematic, because I have to fix it by hand (or reimporting form CSV), because I cannot find a way to find and replace these errors using Multi-Edit.
We will take a look at this.
If you can provide more information, it will be helpful to check the case.
I underztand that the issue is that after importing CSV NAT rules, some of the fields are not collected properly.
Is that the origin of the whole process?
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!