All posts by SinaOnline

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.

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.

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.

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 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.

Prerequisites:

• 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.

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.

“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.

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.

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 (https://www.gns3.com/). 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.

1. Hardware Setup:

• Mount the airFiber 60 LR units in a suitable outdoor location, ensuring a clear line of sight between them.
• Connect the units to power using the included PoE (Power over Ethernet) adapters.
• Use shielded Ethernet cables to connect the PoE adapters to the airFiber units and to your network equipment.

2. Initial Configuration:

• Connect a computer to the LAN port of one of the airFiber units using an Ethernet cable.
• Set a static IP address on your computer in the same subnet as the airFiber unit (e.g., 192.168.1.2).
• Open a web browser and enter the default IP address of the airFiber unit (e.g., 192.168.1.20) in the address bar.
• Log in using the default username and password (ubnt/ubnt).

3. Basic Configuration:

• Once logged in, go to the “Network” tab and configure the IP address, subnet mask, and gateway for the airFiber unit.
• Go to the “Wireless” tab and configure the wireless settings, including the SSID and security settings.

4. Alignment and Link Establishment:

• Use the airFiber’s alignment tool (available in the web interface) to align the units for optimal signal strength.
• Monitor the signal strength and quality indicators in the web interface to ensure a stable connection.

5. Advanced Configuration (Optional):

• Explore the advanced settings in the web interface to optimize the performance of your airFiber link, such as channel width, modulation, and encryption settings.
• Configure any additional features you may need, such as VLANs, QoS, or SNMP.

6. Security Configuration:

• Enable security features such as firewall rules, access control, and secure management protocols (e.g., HTTPS) to protect your airFiber units from unauthorized access.

7. Testing and Optimization:

• Conduct speed tests and signal tests to ensure that the airFiber link is performing as expected.
• Adjust settings as necessary to optimize performance and stability.

8. Monitoring and Maintenance:

• Regularly monitor the performance and health of your airFiber link using the web interface.
• Keep the firmware of your airFiber units up to date to ensure compatibility and security.

This is a general guide, and the exact steps may vary depending on your specific deployment scenario and requirements. Refer to the official Ubiquiti airFiber documentation for detailed instructions and troubleshooting tips.

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

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.

Hello everyone. In this video I will show how you can reset your HP storage password. With this method, you can reset any type of HP storage password.

Note: Before proceeding, ensure you have the necessary permissions and authority to reset passwords, as this action can have security implications.

1. Access the Management Interface:
   • Connect a computer to the same network as the HP storage system.
   • Open a web browser and enter the IP address of the storage system. This IP address can usually be found on a label on the front or back of the storage device.
   • Log in to the management interface using the current administrator username and password. If you’ve forgotten the password, proceed with the password reset.
2. Locate the Password Reset Option:
   • Explore the management interface menus and navigation options to find the password reset feature. Common locations include:
     • System Settings: Look for options related to “User Management,” “Security,” or “Authentication.”
     • User Management: Navigate to the user management section where you can edit user profiles.
3. Select User Account:
   • In the user management section, locate your user account or the account for which you want to reset the password.
4. Initiate Password Reset:
   • Click on the user account, and you should see an option to reset the password. This might be labeled as “Change Password,” “Reset Password,” or something similar.
5. Identity Verification:
   • You may be prompted to verify your identity. This can be done by providing information such as your username, email address, or answering security questions.
6. Reset Password:
   • Once your identity is verified, you can reset the password. You’ll typically need to enter a new password and confirm it. Make sure to create a strong and secure password following any password policy requirements.
7. Confirmation:
   • After successfully resetting the password, you should receive a confirmation message. It may include information about the updated password and any changes made to your account.
8. Log In with New Password:
   • Use the newly reset password to log in to the management interface. Ensure that the new credentials work as expected.
9. Update Password Policy (if necessary):
   • It’s advisable to review and update the password policy settings to align them with your organization’s security requirements. This might include setting password expiration periods and complexity requirements.
10. Test Access:
    • Confirm that you can access and manage the HP storage system using the new password.
11. Document the Changes:
    • It’s important to maintain a record of password changes for audit and security purposes. Document the date and reason for the password reset.
12. Securely Store the New Password:
    • Store the new password securely, and ensure that only authorized personnel have access to it.

If you encounter any difficulties during the password reset process or have concerns about security, consider contacting HP support or your IT department for assistance. Always prioritize security when managing passwords for your storage systems.