IPv6 networks converted to IPv4 /32 host.

Showing results for 
Show  only  | Search instead for 
Did you mean: 

IPv6 networks converted to IPv4 /32 host.

L0 Member



we are trying to migrate configuration from Cisco Firepower using Expedition to Palo Alto. When it comes to address objects, IPv6 networks are not migrated properly. The object name is modified automatically where at the end of the IPv6 address object expedition adds -32 and changes IPv6 address to It is even marked as IPv4 address. This is not happening with IPv6 hosts. Does anyone experience same problem or have some workaround for IPv6 networks? We are using IPv6 frequently and it would require a lot of manual work. If you check the attachment, all referenced objects are IPv6 networks converted to and name has -32 suffix added by the tool.





L4 Transporter

Hello @thovanec 


Can you please reach out to fwmigrate@paloaltonetworks.com with your problem so that we can look into it further?


Thank you!

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!