Objectives
The simulator ticks each one as soon as the network meets it.
Network object LAN (192.168.1.0/24), with automatic NAT: method hide. NAT lives on the object here, not in a rule.
Rule INSIDE-OUT: source LAN, destination any, service any, Accept, Track Log.
Publish. show changes is now empty, and PC1 still can’t reach anything: the gateway has no policy from you yet.
Install the policy on GW1. fw stat on GW1 shows policy Standard.
PC1 reaches 198.51.100.1.
Before you start
After your last rule comes an implicit Drop, so anything you don’t allow is dropped. On a real manager, other admins can’t see your session until you publish. show gateways tells you when a gateway’s policy is out of date. The manager’s show lines (show gateways, show rules, show changes …) and the short set simple-gateway … interface … topology line are RouteBuddy’s own: a real manager shows these in SmartConsole or with mgmt_cli show-… commands.
Concept
Change, publish, install
A Check Point-style manager has three steps. A change is private in your session. Publish moves it into the manager’s database. Install Policy verifies it and sends it to a gateway. The gateway runs what was installed, so three places can disagree.
Concept
A rule names objects, and NAT lives on them
Automatic NAT is set on a host or network, not in a rule. The object stands for both its addresses, so a rule names the object and you never write the public address. A rule that hides another fails verification, because nothing could ever reach the lower one.
