A new Check Point gateway: Mgmt port, console and factory logins
Where this module fits. The Gaia module starts with a gateway that is already reachable. On day one nothing is reachable yet: you have a box (or a virtual machine), a console and a Mgmt port. This module covers the first hour: log in, give the Mgmt port an address, secure the admin account and open the Gaia Portal.
Analogy: the staff door and the customer doors
A gateway has traffic interfaces (the customer doors, where networks connect) and a Mgmt interface (the staff door, used by administrators). Most day-one mistakes come from mixing the two up.
Three ways to manage a Gaia system
| Tool | What it is | Used for |
|---|---|---|
| clish | The Gaia command line (default shell) | Interfaces, routes, users, DNS, NTP, web settings |
| Gaia Portal | Web interface of the operating system on https port 443 | The same OS settings as clish, in a browser |
| SmartConsole | Desktop client that talks to the Security Management Server | Objects, policy, NAT, logs (covered in the later modules) |
The Gaia Portal and SmartConsole are different tools. The portal configures the operating system; SmartConsole configures the security policy.
Factory defaults (as modelled in the simulator)
| Item | Value |
|---|---|
| Mgmt interface | eth0 at 192.168.1.1/24 |
| Administrator | admin / admin (a new password is forced before the portal opens) |
| Allowed clients | any host |
Real appliances run a First Time Configuration Wizard, in the portal or on the console, to set the password, the Mgmt address and the role (gateway, management server). The simulator does the same work with clish commands.
Key takeaways: clish, Gaia Portal and SmartConsole are three different tools. Factory: Mgmt 192.168.1.1/24, admin / admin, password change forced. Keep the Mgmt interface separate from traffic interfaces.