Importing FortiNet images on EVE-NG

So you're looking to get into the exciting world of network security and you would like to play around on some FortiNet devices in order to learn? Then EVE-NG has you covered! It is very easy to import a FortiNet appliance into EVE-NG and to run these appliances on a virtual topology.

You will be able to work on FortiGates (Firewalls), FortiAnalyzer (FAZ for reporting) or even the FortiManager (Orchestrator for SD-WAN), below is a quick video on how to import FortiNet images, please see video below where I showcase how to import FortiNet appliances and give tips.

Video:

Written Guide:

Please follow this link to the EVE-NG website if you are looking for a written guide on how to import a FortiNet appliance step by step.

https://www.eve-ng.net/index.php/documentation/howtos/howto-add-fortinet-images/

THE BELOW IS COPIED DIRECTLY FROM THE EVE-NG SITE, ALL CREDIT TO THE EVE-NG TEAM FOR MAKING THE WRITTEN GUIDE.

1. Obtain FortiGate KVM image and prepare for EVE
1.1. Using our image table, create correct image folder, this example is for image 1. in the table above. It is Fortinet FGT image. Per our image naming table we have to create image folder starting with fortinet-, lets do it.
mkdir /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/
1.2. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/  folder using for example FileZilla or WinSCP.
1.3. From the EVE cli, go to newly created image folder.
cd /opt/unetlab/addons/qemu/fortinet-FGT-v6-build1010/
1.4. Unzip original filename
unzip FGT_VM64_KVM-v6-build1010-FORTINET.out.kvm.zip 
1.5. Rename original filename to virtioa.qcow2 and remove original zip file
mv fortios.qcow2 virtioa.qcow2

rm FGT_VM64_KVM-v6-build1010-FORTINET.out.kvm.zip  
1.6.  Fix permissions:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
2. Obtain FortiManager KVM image and prepare for EVE.
2.1. Using our image table, create correct image folder, this example is for image 1. in the table above. It is Fortinet Manager(FMG) image. Per our image naming table we have to create image folder starting with fortinet-, lets do it.
mkdir /opt/unetlab/addons/qemu/fortinet-FMG-v6-build1183/
2.2. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/fortinet-FMG-v6-build1183/  folder using for example FileZilla or WinSCP.
2.3. From the EVE cli, go to newly created image folder.
cd /opt/unetlab/addons/qemu/fortinet-FMG-v6-build1183/ 
2.4. Unzip original filename
unzip FMG_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
2.5. Rename original filename to virtioa.qcow2 and remove original zip file
mv fmg.qcow2 virtioa.qcow2
rm FMG_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
2.6. Create second HDD 100Gb drive virtiob.qcow2
/opt/qemu/bin/qemu-img create -f qcow2 virtiob.qcow2 100G
2.7.  Fix permissions:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
3. Obtain FortiAnalyzer KVM image and prepare for EVE.
3.1. Using our image table, create correct image folder, this example is for image 1. in the table above. It is Fortinet Manager(FMG) image. Per our image naming table we have to create image folder starting with fortinet-, lets do it.
mkdir /opt/unetlab/addons/qemu/fortinet-FAZ-v6-build1183/
3.2. Upload the downloaded image to the EVE /opt/unetlab/addons/qemu/fortinet-FAZ-v6-build1183/  folder using for example FileZilla or WinSCP.
3.3. From the EVE cli, go to newly created image folder.
cd /opt/unetlab/addons/qemu/fortinet-FAZ-v6-build1183/ 
3.4. Unzip original filename
unzip FAZ_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
3.5. Rename original filename to virtioa.qcow2 and remove original zip file
mv fmg.qcow2 virtioa.qcow2
rm FAZ_VM64_KVM-v6-build1183-FORTINET.out.kvm.zip
3.6.  Fix permissions:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

Admin bar avatar

The Network Berg

Network solutions specialist with over 12 years of experience in the computer networking landscape. Involved with solution design, project planning and implementations on Enterprise and ISP networks.