Missing network objects in the Object Explorer

[Jure_Simundic]

Hi!

The network objects that were automatically created during the "Get topology" action do not show under the network objects in the Object Explorer. However, I can reference/use them in the firewall rule base.

For example:

"Get Topology" created two new networks: Net_192.168.111.0 and Net_192.168.222.0. Those object can be added to the firewall rule, but if you try to look them up in the Object Explorer they do not show.

Is this perhaps a known bug?

Regards,

Jure

[Uriel_F]

Hi Jure,

The network objects created via 'Get Topology' shouldn't be available be used in the rule base,

Can you please specify how were you able to add them to the rule base?

Thanks,

Uriel Fleishcman

[Jure_Simundic]

Hi Uriel!

I found those networks in the drop down list of the source/destination field of the rule base.

This is something that is working perfectly in the pre-R80 versions so I do not understand why Check Point moved it now.

New networks pulled/created via "Get topology" are very likely to be used afterwards in the rule base.

I can submit few screenshots to backup the story.

Regards,

Jure Simundic

[Uriel_F]

Hi,

Can you please explain in general your usages for this networks?

When performing get topology those networks are all added into one network group usually called <gwName>_<inetrfaceName>, is this group also usable in the rule base?

Thanks,
Uriel Fleischman

[Jure_Simundic]

Yes, it is usable.

For example, we created a new VLAN interface eth2.214 with two networks behind it. The networks are available in the rule base, but they do not show in the object explorer. In the pre-80 versions this has never been a problem.

[Jure_Simundic]

In general, the Object Explorer is not working well in terms of filtering, e.g. you cannot filter according to NAT IP address, sometimes it does not list the object if you try to filter it according to its IP address.

Are we to have that fixed in R80.10?

Regards,

Jure

[Tomer_Sole]

Hi,

Unfortunately I cannot commit on things planned to be released in R80.10 just yet. We are aware of these 2 issues. Were there any other specific issues that you experienced with the Object Explorer?

[Venkat_Raman_G_]

Hi Tomer -

I do have the same problem and i am running R80.    Is there a fix available?   All the auto created objects are not visible in the object explorer.     Let me know.

[Tomer_Sole · Accepted solution]

Venkat Raman G G wrote:

Hi Tomer -

I do have the same problem and i am running R80. Is there a fix available? All the auto created objects are not visible in the object explorer. Let me know.

Let's continue this conversation at the other thread - Get interfaces auto generated networks

[Tomer_Sole]

In general, the Object Explorer is not working well in terms of filtering, e.g. you cannot filter according to NAT IP address, sometimes it does not list the object if you try to filter it according to its IP address.

Are we to have that fixed in R80.10?

Regards,

Jure

tomera5b2e7f3-09aa-32f8-96c2-f0f5bfa2988b wrote:

Hi,

Unfortunately I cannot commit on things planned to be released in R80.10 just yet. We are aware of these 2 issues. Were there any other specific issues that you experienced with the Object Explorer?

Hi Jure,

Since R80.10 is currently available as EA from the Check Point User Center, I can now confirm that filtering network objects in the Object Explorer by the NAT address is supported in R80.10, as well as fixes to the filter by IP Addresses.