In this article, we will give you some information about how to do routine operations such as IPv4 address creation, grouping, and policy creation on your Fortigate Firewall devices through CLI console.

First you can access the CLI console via the web interface or SSH with Putty.

I want to give you some brief information about the commands first.

The “Config“ command allows you to move to the configuration section.
The “Edit“ command is used to create or edit as needed.
The “Set” command is used to add and configure, IP, add members, etc.
The “Next“ gives you a chance to make a new operation in the corresponding config directory.
The “End“ command is used to exit config. We can start now.

We will explain how to connect to your OpenVPN server via Ubuntu in two ways. One is via CLI and the other via GUI. We will use PfSense as the VPN server. In addition to using PfSense as an OpenSource firewall, you can use it for many purposes. We will use the VPN server for the process here and get the configuration files from it.

First, we extract the configuration files from the VPN server. **.Ovpn, \ .p12, * .key. In the meantime, the configuration varies on the server-side. So for ios, for android, for windows and are divided into standard packages.

This article is a continuation of the previous article. In the previous article, we discussed “Mapping paths with Route Rules” so in this article we will discuss [Policy Based Route 2] Mapping Paths with Mangle.

Mangle is one of the features found on the firewall menu. Mangle itself has a function to mark a connection or data packet, which passes through the router, into the router, or exits the router.

Mikrotik is a device that is quite flexible and we can set the configuration according to the needs of the existing network. Many kinds of features are added to the system, such as Firewall, Routing, Bandwidth Management, Web-Proxy, Samba Server, L2 Management, Hotspot, RADIUS functions, etc.

In addition, MikroTik products generally have several ethernet ports which by default each run independently, in other words, we can use it for more than one ISP Line by Loadbalance or Failover methods. Or you can also configure it with bridging mode for L2 Management needs.

In Firewall, some rules may need to be implemented for more than one interface. In such cases, instead of creating a separate firewall rule for each interface, Mikrotik offers us the Interface-List architecture as a solution in both the Firewall and similar fields.

So what does this feature give us?

First, each firewall rule plays an important role in the RAM/CPU relationship. On this side, when you need to write the same rule for 5 different interfaces, a job that can be checked 5 times can be written and controlled at once.