Automatically created networks in Smartconsole

[Maarten_Sjouw]

While working on a new customer setup I ran into something I did see before but did not really look into last time.

When you build a new FW and you have a number of static routes defined on that box, SmartConsole will collect those routes and add those routes as networks in the interface group for Anti-Spoffing, so far so good.

While building the rulebase, the boxes were staged and shipped half way around the world, I ran into the issue that when I tried to create a network that was created automagically, it started nagging it already existed.

Ok, then where is it?

Opening the Object Explorer and searching for the network 10.10.10.0, it shows the group it is in, but it does not show the network object itself, opening that group shows the networks, that are added based on the routes, searching with the notation Net_10.10.10.0 nothing is shown.

Also searching at the righthand side does not show the networks.

[RickLin]

The issue already exist from R80.

I ever create SR at 2016Q3, but TAC told me it is design behavior.

[Maarten_Sjouw]

Hey Tomer, Maybe you should tell marketing about this cool feature? Hidden network objects. 😉

[PhoneBoy]

You can remove these using the CLI/API (at least I did when I ran into it).

[Maarten_Sjouw · Accepted solution]

Thing is I just want to use them but give them a proper name, so I can recognize and reuse them.

Looked at the sk126872 and it says to update a parameter in GuiDBedit so it will be visible, minor detail this way...

[RickLin]

CheckPoint Update SK this week.

Please check sk126872.

[Markus_Marquard]

We have seen similar behavior. When you get the network topology in R80.10 SmartConsole from Gateway, it will add objects for ALL networks it is seeing in the routing table of that Gateway.

To us this happened also for dynamic routes coming by OSPF to the Gateway - a few hundred objects were created this way, without any warning. Luckily you can discard the changes in SmartConsole. But I think this should be made more obvious with a dialog presented in the UI.