Addresses "null" instead of "any" in NAT and Security rules?

Per_Westerlund — Thu, 18 Jul 2019 08:32:06 GMT

Expedition 1.1.28

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".

List view

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).

WorksBroken

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.

OK again

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.

/Per

Re: Addresses "null" instead of "any" in NAT and Security rules?

dgildelaig — Wed, 24 Jul 2019 18:51:14 GMT

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?

topic Re: Addresses "null" instead of "any" in NAT and Security rules? in Expedition Discussions

Addresses "null" instead of "any" in NAT and Security rules?

Re: Addresses "null" instead of "any" in NAT and Security rules?