Any recent updates to cause a /32 mask to get added to set commands for address objects?

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.

Any recent updates to cause a /32 mask to get added to set commands for address objects?

L0 Member

Just noticed after importing a Check Point migration into a Panorama base config and merging the objects that the set commands for address objects all contain a /32 mask in the address field that did not exist in Check Point. The object > address view in the Expedition project all contain a 32 CIDR.

Any recent changes to cause this?

1 accepted solution

Accepted Solutions

L4 Transporter

Hi @KirkHarvey 

 

Thanks for reaching out and apologies for the inconveniences.

Please check the new Expedition version we are going to release in a few days. It will include a fix for your described issue.

 

Best,

 

David

 

 

View solution in original post

1 REPLY 1

L4 Transporter

Hi @KirkHarvey 

 

Thanks for reaching out and apologies for the inconveniences.

Please check the new Expedition version we are going to release in a few days. It will include a fix for your described issue.

 

Best,

 

David

 

 

  • 1 accepted solution
  • 428 Views
  • 1 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!