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

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

jloehler — Mon, 18 Nov 2019 10:21:52 GMT

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

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

BatD — Mon, 18 Nov 2019 12:52:35 GMT

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

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

jloehler — Tue, 19 Nov 2019 09:27:14 GMT

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