Auto Zone Assign - IP range object as source IP

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 - IP range object as source IP

L1 Bithead

Hi All,


I have recently encountered a very strange issue in Expedition project when trying to make auto-zone assign. 


Quick background:
- In expedition project I have a config migrated from checkpoint
- we have around 15 direcly connected interfaces - all with IP somewhere in the range from to, and 1 uplink from another range.
- Virtual router collecting all the interfaces of the firewall has a single default route via this uplink. All other interfaces are added as connected.
- Some of my security rules are having source address field based on the address-group object that matches following 2 address objects:
---- IP range address object ( -
---- Specific IP (host address object) outside of the firewall (to get there we follow a default route via uplink interface)



Now,when I make auto-zone assign to calculate both source/destination zone (no NAT rules, and I am referring to this specific VR from my config), I am expecting to see ALL the zones under the source address, but I only see an uplink one.

When I then modified address-group as follows:

(WAS ALREADY THERE)---- IP range address object ( -
(WAS ALREADY THERE)---- Specific IP (host address object) outside of the firewall (to get there we follow a default route via uplink interface)
(THE NEW ONE I AM ADDING NOW)----- IP range address object ( -


After this, auto-zone assign resolves and puts all the zones from all interfaces as a source zone inside my security policies. Is anyone away on what is the exact code logic when evaluating zone assignements. The new range I have added is clearly within the already existing one, however it was not matched earlier.


Is this some bug or there are some undocumented limitations of the range objects that I am not aware of? Have anyone seen similar behavior?


Thanks a lot for any hints.


L6 Presenter

@markru114 For checkpoint , Zone will be auto calculated based on route file and the connected interface , if you have the subnet - that's specified in the static route , then when you import the checkpoint config and static route file, expedition should auto calculate the zone for you.  Or you could add static route entry after import , and re-do autozone , it should also work.  If you have two route entries, expedition will evaluate both route statement and choose the most restrict one , for example, if you have below two static routes:


Destination Gateway Genmask Flags MSS Window irtt Iface UGH 0 0 0 eth1-04 UGH 0 0 0 eth1-03


Then Expedition will auto assign zone for any source or destination that fall under to eth1-04 


Hi @lychiang , I fully agree with what you are saying, but it my case the problem revolves around CONNECTED INTERFACES. For some strange reason the network object used inside security policy that definitely covers the subnet used on the CONNECTED interface -  it doesn't add the zone of this connected interface. 


Let me know if my original problem description is clear on it, or I should re-word it.

@markru114 Autozone should also consider connected interface, can you please open a TAC case to share the checkpoint config , after case is opened, please write an email to mentioned about your case#. Thank you!

Hi @lychiang ,


I have done it in the last days. Let me know once you find out what is happening there in the background.



  • 4 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!