Objects named "Any" for services and addresses in NAT Rules after CP migration

Reply
Highlighted
L0 Member

Objects named "Any" for services and addresses in NAT Rules after CP migration

Hi, after migrating a CP R76.50 policy with Expedition 1.11.10 I  see some weird "Any" objects in the NAT policy. Expedition created an address object named "Any" with an IP address  1.1.1.1 instead of any address. Same with services where it  created a service named "Any" without a port. Has anyone run into the same issue?

 

Thanks,

Joerg


Accepted Solutions
Highlighted
L4 Transporter

Re: Objects named "Any" for services and addresses in NAT Rules after CP migration

@jloehler Address objects "1.1.1.1" or service objects "6500" are invalid objects, which the tool could not migrate. You need to investigate and manually update if you see any. 

This could be caused by different reasons and hard to say without looking at the firewa. But as an example, destination nat rule need to alwasy match on IP or range of IPs. If the original firewall has "any" in the destination and it is then converted by the tool to destination NAT rule, then the tool will migrate it as the invalid object above. 

View solution in original post


All Replies
Highlighted
L4 Transporter

Re: Objects named "Any" for services and addresses in NAT Rules after CP migration

@jloehler Address objects "1.1.1.1" or service objects "6500" are invalid objects, which the tool could not migrate. You need to investigate and manually update if you see any. 

This could be caused by different reasons and hard to say without looking at the firewa. But as an example, destination nat rule need to alwasy match on IP or range of IPs. If the original firewall has "any" in the destination and it is then converted by the tool to destination NAT rule, then the tool will migrate it as the invalid object above. 

View solution in original post

L0 Member

Re: Objects named "Any" for services and addresses in NAT Rules after CP migration

@BatD Thanks a lot! Destination NAT with äny" as the target address on the CP side was exactly the root cause here.

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 Live Community as a whole!

The Live Community thanks you for your participation!