Auto Zone Assign for directly connected networks

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Auto Zone Assign for directly connected networks

L3 Networker

Expedition Version: 1.2.3


Today I learned Expedition needs interfaces assigned to routes for auto zone assign to work. This makes sense as the code uses the interface to find the zone for a specific route rather than doing a [virtual] route lookup.


I have however been unable to get the right zone assigned for a directly connected network unless I add an interface route for that network to the VR, and remove it before I migrate.


This is another Check Point R80 migration, I've imported the policy package and manually imported interfaces/zones/routes as CSV as I have not been able to use the output of a "show route all" reliably.


Surely I'm doing it wrong 😕


L6 Presenter

Hi @mb_equate When you import checkpoint config and route file at the same time, expedition should auto calculate the zone based on route file.  The route file needs to show directly connected interfaces like below:


C is directly connected, eth2

  • 1 replies
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!