FortinetFortiManagerPNETLabEVE-NG2026-04

#5 - Initial Setup of FortiManager in EVE-NG / PNETLab (Management Interface + Internet Access)

•3 min read
#5 - Initial Setup of FortiManager in EVE-NG / PNETLab (Management Interface + Internet Access)

Table of Contents

In this guide, we will walk through the initial configuration of a FortiManager appliance running in a lab environment using EVE-NG or PNETLab. The goal is to establish management access, enable internet connectivity, and prepare the device for FortiGuard services and general lab use.

Lab Environment

  • Platform: EVE-NG / PNETLab
  • Image: FortiManager v7.0.3 (build 0254)
  • CPU: 4 vCPU
  • RAM: 8192 MB

Step 1 - First CLI Access

Access the FortiManager via the console using:

Username: admin
Password: (leave blank)

On the first login, you will be prompted to set a new password. This step is mandatory before proceeding.

Step 2 - Configure the Management Interface

To simplify access to the device, connect one interface, in this example port4, to a Cloud (bridge) network in EVE-NG or PNETLab. This allows direct access from your local machine without requiring an additional VM.

Configuration

Access the device CLI and run:

config system interface
    edit port4
        set ip 192.168.0.X/24
        set allowaccess http https ssh ping
        set alias "GERENCIA"
    next
end

Replace 192.168.0.X with an available IP address in your local network.

  • The allowaccess parameter enables management protocols.
  • The alias parameter is optional, but it helps identify the interface.

Connectivity Test

execute ping 192.168.0.1

If configured correctly, the device should be able to reach your local gateway.

Step 3 - Configure the Default Gateway

To allow external connectivity, configure a default route:

config system route
    edit 1
        set gateway 192.168.0.1
        set dst 0.0.0.0/0
        set device "port4"
    next
end

Test External Connectivity

execute ping 8.8.8.8

A successful response confirms basic internet connectivity.

Step 4 - Configure DNS

DNS configuration is required for name resolution and proper communication with FortiGuard services.

config system dns
    set primary 1.1.1.1
    set secondary 1.0.0.1
end

Test Name Resolution

execute ping google.com

If this works, DNS is correctly configured.

Step 5 – Access via Web Interface and Licensing

Now you can access the FortiManager GUI from your browser:

https://192.168.0.X

Log in using your FortiCloud account credentials:

👉 https://www.forticloud.com

Once authenticated, your lab device will automatically receive a trial license, allowing you to explore features for learning and testing purposes.

Step 6 - Adjust SSL Security Settings for Lab Use

In some EVE-NG or PNETLab environments, especially when using a trial license, the default SSL security settings may prevent proper communication during the initial lab setup. To improve compatibility in this scenario, you can temporarily reduce the SSL security requirements.

Important: This configuration is recommended only for lab and testing environments. It should never be used in production, since it enables weaker cryptographic settings.

Configuration

Access the FortiManager CLI and run:

config system global
    set ssl-low-encryption enable
    set fgfm-ssl-protocol sslv3
end

Security Notice

This configuration enables legacy SSL behavior and weaker encryption support. Use it only when strictly necessary for lab purposes.

Final Notes

  • Ensure your EVE-NG or PNETLab cloud interface is properly bridged to your host network.
  • Avoid IP conflicts with other devices on your LAN.
  • If ping tests fail, verify your bridge configuration, interface settings, and gateway.
  • This setup provides a simple and efficient way to manage your FortiManager directly from your local machine.

GERENCIA = Management