Category Network Training

Upgrade FortiGate Firewall

Hello every one , in this video I will upgrade fortigate firewall firmware , as you know upgrading firmware is very important because in older versions of forties , it has different security and performance bugs, also to download firmware, you need to have an account of

  1. Preparation:
    • Identify the target firmware version you want to upgrade to. Check Fortinet’s official website for the latest firmware releases and release notes.
  2. Download Firmware:
    • Access the Fortinet Support Portal and download the firmware image file for your FortiGate model and the desired firmware version. Save it to your local machine.
  3. Backup Configuration:
    • Log in to the FortiGate web-based interface (GUI).
    • Navigate to System > Dashboard > Status and click on “Backup” to create a backup of your current configuration. Store this backup in a safe location.
  4. Check Hardware Requirements:
    • Verify that your FortiGate model has the necessary hardware resources to support the new firmware version. Refer to the release notes for hardware requirements.
  5. Upload Firmware:
    • In the FortiGate GUI, go to System > Firmware > Image and click on “Upload Images.”
    • Select the firmware image file you downloaded earlier and upload it to the FortiGate.
  6. Install Firmware:
    • After the firmware image is uploaded, select it and click on “Upgrade.” Follow the on-screen instructions to start the upgrade process. This process may take several minutes, and your FortiGate will automatically reboot when it’s completed.
  7. Verify Upgrade:
    • Once the FortiGate reboots, log back into the GUI and verify that the new firmware version is running. Go to System > Dashboard > Status to check the firmware version.
  8. Test Functionality:
    • Test critical network functions, such as firewall rules, VPN connections, and any other services you rely on, to ensure they are working as expected.
  9. Review Release Notes:
    • Review the release notes for the new firmware version to understand any changes, bug fixes, or new features introduced.
  10. Monitor and Troubleshoot:
    • Keep an eye on your network for any unexpected issues that may have been introduced by the upgrade. Be prepared to troubleshoot and rollback if necessary.
  11. Rollback (if needed):
    • In case the upgrade causes critical issues that cannot be resolved immediately, you may need to roll back to the previous firmware version using the backup you created earlier. This should be done carefully to avoid further disruptions.
  12. Post-Upgrade Tasks:
    • Update documentation and notify relevant team members or stakeholders about the successful upgrade.
    • Consider making any necessary adjustments or optimizations to the firewall settings based on the new firmware’s capabilities.

FortiGate Traffic Shaping Configuration

Traffic shaping is a method of optimizing network traffic by prioritizing different types of traffic according to their importance. FortiGate firewall offers a traffic shaping feature that can be used to prioritize traffic, limit bandwidth usage, and control network congestion. In this blog post, we’ll discuss how to configure traffic shaping on FortiGate firewall.

Fortigate Traffic Shaping

1. Log in to the FortiGate Web Interface:

  • Open a web browser and enter the IP address of your FortiGate firewall.
  • Log in with the appropriate credentials.

2. Define Traffic Shaping Policy:

  • Navigate to the “Policy & Objects” tab.
  • Click on “Traffic Shaper” to access the Traffic Shaping policies.

3. Create a New Traffic Shaping Policy:

  • Click the “+ Create New” button to create a new policy.
  • Give your policy a name and optionally add a comment for reference.

4. Set Traffic Shaping Parameters:

  • In the “Guaranteed Bandwidth” section, specify the minimum guaranteed bandwidth (in Kbps or Mbps) for the traffic you want to shape. This is the minimum speed that will be allocated to the traffic matching this policy.
  • In the “Maximum Bandwidth” section, set the maximum bandwidth (in Kbps or Mbps) that the traffic can use.
  • You can also configure a burst rate and burst time if needed. Burst rate allows traffic to exceed the defined limits for a short period if there’s available bandwidth.

5. Define Traffic Matching Criteria:

  • In the “Matching Criteria” section, specify the criteria for matching traffic to this policy. You can configure this based on source and destination IP addresses, ports, services, etc.
  • Click the “+” icon to add multiple conditions if necessary.

6. Enable the Policy:

  • In the “Actions” section, set the action to “Apply Shaper” to enable traffic shaping for the matched traffic.
  • Click “OK” to save the policy.

7. Apply Traffic Shaping Policy to Firewall Policy:

  • After creating the traffic shaping policy, you need to apply it to a firewall policy.
  • Go to the “Policy & Objects” tab and click on “Firewall Policy.”
  • Edit an existing policy or create a new one, and in the “Traffic Shaping” section, select the traffic shaping policy you created earlier from the dropdown menu.

8. Monitor Traffic Shaping:

  • You can monitor the traffic shaping policies in action by going to the “Monitor” tab and selecting “Traffic Shaping Monitor.” Here, you can see statistics and real-time information on the traffic matching your policies.

9. Test and Fine-Tune:

  • After configuring traffic shaping, it’s essential to monitor network performance and adjust policies as needed to ensure your network operates efficiently and as intended.

10. Save and Apply Changes:

  • Don’t forget to save your changes and apply the configuration for it to take effect.

Remember that traffic shaping should be used judiciously, as improper configuration can negatively impact network performance. It’s essential to understand your network’s traffic patterns and prioritize traffic accordingly to achieve your desired outcomes with traffic shaping on a FortiGate firewall.

Fortigate Captive Portal Configuration

A captive portal is a web page that is presented to users when they attempt to connect to a network. Captive portals are commonly used in public Wi-Fi hotspots, hotels, and other places where the network owner wants to control the access to the network. FortiGate firewall offers a captive portal feature that can be used to authenticate users and control network access. In this blog post, we’ll discuss how to configure captive portal on FortiGate firewall.

Fortigate Captive Portal Configuration

1. Log in to the FortiGate Web Interface:

  • Open a web browser and enter the IP address of your FortiGate device.
  • Log in using your administrative credentials.

2. Configure Network Interfaces:

  • Ensure that you have configured your network interfaces correctly. You should have at least two interfaces: one for the unauthenticated guest network and another for the trusted network.

3. Create a User Group:

  • Before setting up the captive portal, create a user group that will contain the users allowed to access the network through the captive portal.
    • Go to “User & Device” > “User Groups” and click “Create New.”
    • Define the group’s name and add users to it if needed.

4. Create a Security Policy:

  • You need to create a security policy to control traffic between the unauthenticated network and the trusted network.
    • Go to “Policy & Objects” > “IPv4 Policy” and click “Create New.”
    • Configure the source interface, source address (unauthenticated network), destination interface, and destination address (trusted network).
    • Set the “Action” to “Captive Portal.”

5. Configure Captive Portal:

  • Now, you need to set up the captive portal itself.
    • Go to “Security Fabric” > “Captive Portal” and click “Create New.”
    • Enter a name for the captive portal.

6. Configure Authentication Settings:

  • Under the “Authentication” tab:
    • Select the user group you created earlier.
    • Choose the authentication method (usually, you’d use “Local Database” for basic username and password authentication).
    • Set the authentication timeout.
    • Customize the authentication message if desired.

7. Configure Authentication Portal Settings:

  • Under the “Authentication Portal” tab:
    • Define the portal message and login message.
    • Customize the look and feel of the portal page, including logos and background images.

8. Configure Redirect Settings:

  • Under the “Redirect” tab:
    • Specify the redirection type. Typically, you’d use “External Web Page” to direct users to a terms and conditions page or login page hosted externally.

9. Create a Firewall Policy for Redirect:

  • Create a firewall policy to redirect traffic to the captive portal.
    • Go to “Policy & Objects” > “IPv4 Policy” and click “Create New.”
    • Set the source and destination interfaces and addresses.
    • Set the action to “SSL-VPN” and choose the captive portal you created earlier as the SSL-VPN portal.

10. Configure DNS and Web Filtering: – You may want to configure DNS and web filtering policies to control access for authenticated users.

11. Test the Captive Portal: – To test the captive portal, connect a device to the unauthenticated network and attempt to access the internet. You should be redirected to the captive portal login page.

12. Monitor and Troubleshoot: – Continuously monitor the captive portal for user activity and any issues that may arise. Check logs and statistics for troubleshooting.

Remember that this is a high-level overview of the FortiGate captive portal configuration process. Depending on your specific requirements and network setup, there may be additional configuration options and steps needed to meet your needs. Always refer to the FortiGate documentation and consult with Fortinet support if you encounter any difficulties or require advanced features.

FortiGate IPsec VPN Site to Site Configuration

FortiGate IPsec VPN Site to Site provides a secure and reliable connection between two networks located in different locations. This is a crucial feature for businesses with remote offices and a requirement for remote workers. In this blog post, we’ll discuss how to configure FortiGate IPsec VPN Site to Site and provide training on its usage.


  • Two FortiGate devices (FortiGate A and FortiGate B) with administrative access.
  • A dedicated public IP address for each FortiGate device.
  • Proper network routing configured on both FortiGate devices.

Step 1: Log in to the FortiGate Web Interface

  1. Open a web browser and enter the IP address of FortiGate A in the address bar.
  2. Log in with administrative credentials.

Step 2: Create Phase 1 Configuration on FortiGate A: Phase 1 sets up the initial connection between the two VPN peers.

  1. Go to “VPN” > “IPsec Wizard” on FortiGate A.
  2. Select “Custom” for the VPN Template.
  3. Configure the following Phase 1 settings:
    • Name: Give the VPN connection a name.
    • Remote Gateway: Enter the public IP address of FortiGate B.
    • Authentication Method: Pre-shared Key (PSK).
    • Pre-shared Key: Enter a strong, secret key.
    • Local Interface: Select the local interface connected to the internet.
    • Mode: Main Mode.
    • IKE Version: IKEv2 or IKEv1, depending on your requirements.
    • Phase 1 Proposal: Define encryption and authentication algorithms.
  4. Click “Next” to save the Phase 1 settings.

Step 3: Create Phase 2 Configuration on FortiGate A: Phase 2 defines the parameters for the actual data encryption.

  1. After saving Phase 1 settings, click “Next” to configure Phase 2.
  2. Configure the following Phase 2 settings:
    • Phase 2 Name: Give it a name.
    • Local Subnet: Enter the local network subnet behind FortiGate A.
    • Remote Subnet: Enter the remote network subnet behind FortiGate B.
    • P2 Proposal: Define encryption and authentication algorithms.
  3. Click “Next” to save the Phase 2 settings.

Step 4: Create Phase 1 and Phase 2 Configuration on FortiGate B: Repeat Steps 2 and 3 on FortiGate B with the corresponding settings, but make sure to reverse the “Remote Gateway” and the “Local Subnet” and “Remote Subnet” settings.

Step 5: Establish the Connection:

  1. After configuring both FortiGate devices, return to FortiGate A.
  2. Go to “VPN” > “IPsec Tunnels” and click the “Create New” button.
  3. Select the Phase 1 and Phase 2 configurations you created for FortiGate B.
  4. Click “OK” to create the VPN tunnel.
  5. Repeat the same steps on FortiGate B, using the Phase 1 and Phase 2 configurations for FortiGate A.

Step 6: Monitor and Troubleshoot:

  1. You can monitor the VPN connection status under “VPN” > “Monitor” > “IPsec Monitor.”
  2. If there are any issues, check the logs and firewall policies for any blocking rules.

That’s it! You should now have a functioning FortiGate IPsec VPN site-to-site connection between the two locations. Ensure that your firewall policies allow traffic to flow over the VPN tunnel, and test the connectivity between the remote networks.

FortiGate Remote Access IPSec VPN Configuration

In today’s digital era, remote access is becoming a fundamental requirement for businesses to ensure continuous productivity. But with remote access comes the risk of cyber threats, making VPN security a top priority.

1. Access the FortiGate Web Interface:
Connect to your FortiGate firewall’s web interface using a web browser. Enter the IP address of the FortiGate in the address bar and log in with administrator credentials.
2. Create a VPN User Group:
Navigate to “User & Device” > “User Groups.”
Click on “Create New.”
Name the group (e.g., “VPN_Users”).
Add the remote users who will be connecting to this group.
3. Configure the VPN Tunnel:
Navigate to “VPN” > “IPsec Wizard.”
Select “Custom” and click “Next.”
Enter a name for the VPN tunnel.
Select “Remote Access” as the type of VPN.
Choose “Pre-shared Key” for authentication.
Create a Pre-shared Key (PSK) and make note of it. This will be used by remote clients to authenticate.
Select the appropriate interface for the VPN (usually the WAN interface).
Configure the Local Interface and Local IP Address settings.
Under Authentication/Phase 1, select the appropriate encryption and authentication settings.
Under Authentication/Phase 2, select the appropriate encryption and authentication settings.
Click “Next” and review your settings.
Click “Finish” to create the VPN tunnel.
4. Configure the Firewall Policies:
Navigate to “Policy & Objects” > “IPv4 Policy.”
Create a new policy for traffic from the VPN to the internal network.Set the source interface to the VPN interface.
Set the destination interface to the internal network.
Specify the appropriate source and destination addresses and services.
Allow the traffic.
5. Configure DNS Settings (optional):
If you want remote users to resolve internal hostnames, configure DNS settings for the VPN users. Navigate to “Network” > “DNS.”
Add internal DNS servers to the list and enable DNS settings for the VPN tunnel.
6. Configure NAT (optional):
If your internal network uses NAT, configure NAT settings for the VPN users. Navigate to “Policy & Objects” > “NAT.”
Create a new NAT policy to translate VPN user traffic to the internal network.
7. Configure User Authentication:
Navigate to “System” > “Administrators” and create a user account for remote authentication.
Ensure the user has permissions to connect via VPN.
8. Configure VPN Client:
On the remote client side, configure the VPN client software (e.g., FortiClient) with the FortiGate’s public IP address and the Pre-shared Key you created earlier.
9. Test the Connection:
Connect the remote client to the FortiGate using the configured VPN settings.
Verify that the connection is established successfully.
These are the basic steps for configuring a FortiGate Remote Access IPSec VPN. Depending on your specific network requirements and security policies, you may need to make additional configurations or adjustments. Always refer to the FortiGate documentation for the most up-to-date and specific instructions for your device.

Fortigate Multiple Interface Policy

“Welcome to my channel! In this video, I will describe how to configure firewall policies with multiple source and destination interfaces in FortiGate. We’ll be looking at how to allow traffic between multiple interfaces on your FortiGate firewall, which is particularly useful when you have different subnets that you want to control traffic between or when you have multiple VLANs that need to communicate with each other. By the end of this video, you’ll have a better understanding of how to configure these policies in FortiGate and how they can help secure your network.

  1. Network Interfaces:
    • In a FortiGate device, you typically have multiple network interfaces, each connected to a different network segment or zone. These interfaces can be physical (Ethernet ports) or virtual (VLANs, subinterfaces, loopback interfaces, etc.).
  2. Traffic Flow:
    • Traffic flows between these interfaces as data packets are transmitted through the FortiGate device. Each interface represents a different security zone, and traffic between these zones must be controlled and inspected for security purposes.
  3. Security Policies:
    • FortiGate uses security policies to determine how traffic is treated as it passes between these interfaces. Security policies are rules that define the permitted actions for specific types of traffic. They include criteria like source and destination IP addresses, ports, protocols, and more.
  4. Multiple Interface Policy:
    • The “Multiple Interface Policy” feature in FortiGate allows you to create a single security policy that applies to traffic flowing between multiple interfaces or zones. This is especially useful when you want to define a consistent policy for a specific category of traffic across multiple interfaces.
  5. Use Cases:
    • There are several use cases for Multiple Interface Policies:
      • DMZ Configuration: If you have a DMZ zone with multiple servers that need different levels of access, you can create a single policy to control traffic from different internal zones to the DMZ.
      • Guest Network Isolation: You can use this feature to control traffic from the guest network to multiple internal networks with a single policy.
      • VPN Traffic: When you have multiple VPN tunnels terminating on different interfaces, you can create a policy that applies to traffic from all those tunnels.
  6. Policy Configuration:
    • When configuring a Multiple Interface Policy, you define the policy’s source and destination interfaces (security zones), specify the criteria for matching traffic (source/destination addresses, services, users, etc.), and define the action to take (allow, deny, NAT, etc.).
  7. Policy Order:
    • Policy order is important. FortiGate processes policies from top to bottom, and the first matching policy is applied. So, you should order your Multiple Interface Policies appropriately to ensure that more specific policies are evaluated before broader ones.
  8. Logging and Monitoring:
    • FortiGate provides extensive logging and monitoring capabilities, allowing you to track traffic as it traverses the different interfaces and the policies applied to it.
  9. Traffic Inspection:
    • Depending on your policy settings, FortiGate can perform various security functions like antivirus scanning, intrusion detection and prevention, content filtering, and more on the traffic as it flows between interfaces.

In summary, FortiGate Multiple Interface Policies are a crucial part of network security configuration. They enable you to manage and secure traffic between multiple network interfaces by defining specific security policies that dictate how traffic should be handled. This feature is particularly useful in complex network environments with diverse security requirements.

FortiGate Two Factor Authentication with Email

Hello everyone, in this video, I will introduce how you can set up 2-step verification for SSL VPN users by sending a token through email. By default, there is no way to enable this option via the graphical user interface. We must enable this feature from the CLI.

1. User Login Request:

  • When a user attempts to log in to a FortiGate-protected resource, such as a VPN, web portal, or firewall management interface, they provide their username and password as the first authentication factor.

2. Verification of Username and Password:

  • FortiGate first verifies the provided username and password against its user database or an external authentication source, such as LDAP, RADIUS, or Active Directory. If the credentials are valid, the user passes the first authentication factor.

3. Request for Second Authentication Factor:

  • Once the user successfully completes the first factor (username and password), FortiGate prompts the user for the second authentication factor. In this case, it’s an email-based authentication.

4. Email-Based Authentication:

  • FortiGate sends an email containing a one-time passcode (OTP) or a link to the user’s registered email address. This email typically includes instructions on what the user should do next.

5. Retrieving and Entering the OTP:

  • The user checks their email and retrieves the OTP or clicks on the provided link. The OTP is typically time-limited and can only be used once for security purposes.

6. Entering the OTP or Confirming Access:

  • The user enters the OTP from the email into the FortiGate login prompt or clicks on the link, which confirms their identity as the second authentication factor.

7. Verification of Second Factor:

  • FortiGate verifies the entered OTP or link against its records to ensure it matches the one it sent to the user’s email. If the OTP or link is valid and within the time window, the user passes the second authentication factor.

8. Access Granted:

  • Once both factors are successfully authenticated (username/password and email-based OTP/link), FortiGate grants the user access to the requested resource or system.

9. Continuous Monitoring:

  • FortiGate may also implement continuous monitoring and session management to ensure that user sessions remain secure throughout their usage.

It’s worth noting that while email-based 2FA is a common method, FortiGate also supports various other second-factor authentication methods, including SMS-based codes, hardware tokens, software tokens, and push notifications through mobile apps. The choice of the second-factor method can depend on the organization’s security policies and user preferences.

Implementing 2FA with email in FortiGate enhances security by adding an extra layer of authentication, making it more challenging for unauthorized users to gain access to critical resources and helping protect against unauthorized access and data breaches.

Install and Config Cisco ASA on GNS3

Hello, today we will install GNS3 with you and then we will install CISCO ASA on it. I will also explain how we can connect to Cisco ASA with ASDM.

Let’s start.

Step 1: Obtain Cisco ASA Image

You’ll need a Cisco ASA image file to run it in GNS3. You can acquire this image from legal and legitimate sources, such as Cisco’s official website, or if you have a Cisco ASA device, you may be able to extract it. Make sure you have the proper licensing to use the image.

Step 2: Install GNS3

If you haven’t already, download and install GNS3 on your computer from the official website ( Follow the installation instructions for your specific operating system.

Step 3: GNS3 Initial Setup

  1. Launch GNS3 and complete the initial setup wizard. This typically includes configuring preferences like where to store your projects and images.
  2. Make sure you have the GNS3 VM (Virtual Machine) configured and running. You can download the GNS3 VM from the GNS3 website and follow the installation instructions provided there.

Step 4: Add Cisco ASA to GNS3

  1. In GNS3, go to “Edit” > “Preferences.”
  2. In the Preferences window, click on “QEMU VMs” on the left sidebar.
  3. Click the “New” button to add a new virtual machine.
  4. Provide a name for the virtual machine (e.g., “Cisco ASA”).
  5. In the “Type” dropdown menu, select “ASA” for Cisco ASA.
  6. In the “QEMU binary” section, browse and select the QEMU binary executable. This binary should be located in your GNS3 VM.
  7. Set the RAM and CPU settings based on your system resources and requirements.
  8. Click “Next” and follow the on-screen instructions to complete the virtual machine setup.

Step 5: Add ASA Image to GNS3

  1. In GNS3, go to “Edit” > “Preferences” again.
  2. In the Preferences window, click on “QEMU” on the left sidebar.
  3. Click the “QEMU VMs” tab.
  4. Select the “Cisco ASA” virtual machine you created earlier.
  5. In the “QEMU Options” section, click the “Browse” button next to “QEMU image” and select the Cisco ASA image file you obtained.

Step 6: Configure Cisco ASA in GNS3

  1. Drag and drop the Cisco ASA device from the GNS3 device list onto your GNS3 workspace.
  2. Right-click on the ASA device and choose “Start.”
  3. Right-click again and select “Console” to open the console window for the ASA.
  4. Configure the ASA as needed using the command-line interface (CLI). This includes setting up interfaces, IP addresses, access control policies, and any other configurations you require.
  5. Save your configurations to ensure they persist across sessions.

With these steps, you should have a Cisco ASA running in GNS3, ready for configuration and testing in your simulated network environment. Remember to follow proper licensing and usage guidelines when using Cisco ASA images.

How to Configure VXLAN on Fortigate

Hello everyone, in this video I will show how can you extend VLANs over IP. In FortiGate by using vxlan you can do this.

How to Configure VXLAN on Fortigate

1. Access the FortiGate GUI:

  • Open a web browser and enter the IP address of your FortiGate firewall to access the graphical user interface (GUI).
  • Log in with administrator credentials.

2. Create VXLAN Interface:

  • Navigate to Network > Interfaces.
  • Click Create New and select VXLAN.
  • Fill in the following details for the VXLAN interface:
    • Name: A descriptive name for the VXLAN interface (e.g., VXLAN1).
    • Alias: An optional alias for identification purposes.
    • VLAN ID (Optional): If you want to associate the VXLAN interface with a specific VLAN, provide the VLAN ID.
    • VXLAN ID (VNI): Specify a unique VXLAN ID. This is critical, as it is used to identify the VXLAN segment. Ensure that VNIs match across devices in your VXLAN network.
    • VXLAN Port: Specify the UDP port for VXLAN traffic (default is 4789).
  • Click OK to create the VXLAN interface.

3. Configure VXLAN Settings:

  • Under Network > VXLAN, select the VXLAN interface you just created.
  • Configure the following VXLAN settings:
    • Local IP Address: Enter the IP address associated with the FortiGate’s VXLAN interface. This IP should be on the same subnet as the VXLAN endpoints.
    • Multicast Address (Optional): If you intend to use multicast for VXLAN traffic, specify a multicast IP address. Ensure that both ends of the VXLAN have the same multicast settings.
    • Remote IP Address (Peer): Enter the IP address of the remote FortiGate firewall or VXLAN endpoint that you want to connect to.
  • Click OK to save the VXLAN settings.

4. Create VXLAN Overlay Network:

  • Go to Policy & Objects > Objects.
  • Click Create New and select Virtual Network.
  • Fill in the VXLAN overlay network details:
    • Name: A descriptive name for the VXLAN overlay network.
    • Interface: Select the VXLAN interface you created in step 2.
    • VXLAN ID (VNI): Set the same VNI as you did in the VXLAN interface configuration.
  • Click OK to create the VXLAN overlay network object.

5. Create Firewall Policies:

  • Under Policy & Objects > IPv4 Policy, create firewall policies to allow traffic between VXLAN overlay networks or between VXLAN networks and the physical network.
  • In the policy settings:
    • Define the source and destination addresses using the VXLAN overlay network objects you created.
    • Specify the desired action (e.g., allow).
    • Set any required security profiles, such as antivirus or intrusion prevention.
  • Click OK to create the firewall policy.

6. Routing (if needed):

  • If routing between VXLAN overlay networks or between VXLAN and physical networks is necessary, configure routing on the FortiGate firewall.

7. Security Profiles (if needed):

  • Apply security profiles to the firewall policies to enhance security for VXLAN traffic. These profiles can include antivirus scanning, intrusion prevention, and application control.

8. Monitor and Troubleshoot:

  • Use the FortiGate GUI or CLI to monitor the VXLAN interface’s status and traffic.
  • Check logs for any issues or errors related to VXLAN.
  • Verify that routes are correctly configured, especially if you have multiple VXLAN segments.

9. Repeat on Remote FortiGate (if applicable):

  • If you have multiple FortiGate firewalls participating in the VXLAN network, repeat the configuration steps on the remote FortiGate(s), ensuring that VXLAN settings match on both ends.

10. Test and Verify:

  • Test connectivity between devices on the VXLAN overlay networks to ensure that traffic is correctly routed and policies are applied.

Always consult the Fortinet documentation for your specific FortiGate model and firmware version, as there may be slight variations in the user interface and configuration options.