Ready to go Linux image pack for EVE
You can choose any of Linux image from the pack below and simply upload into EVE.
2. Download your desirable image
3. Using WinSCP or FileZilla SSH (TCP 22) to your EVE and upload downloaded image to the location: /opt/unetlab/addons/qemu/
4. Using Putty or other telnet client, CLI SSH (TCP 22) to your EVE and go to location:
5. Unzip your uploaded image file, make sure you are using right name of uploaded image. Example for ubuntu desktop image below.
tar xzvf linux-ubuntu-desktop-16.04.4.tar.gz
6. Remove raw zipped image file from EVE
rm -f linux-ubuntu-desktop-16.04.4.tar.gz
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
6. Repeat this procedure for each downloaded image, expecting right image name in commands
Credentials and recommended node settings table:
We have used universal credentials in all our Linux images.
for new Kali 2019.3 linux with RDP enabled: root/toor
How to create own custom Linux host for EVE:
For this you will need real Linux installation CD ISO distro.
We are using: ubuntu-16.04.2-desktop-amd64.iso. Be sure that distro name has not spaces in the filename! Any Linux Server installation has same procedure.
Create new image directory:
mkdir /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.02/
- Use WINSCP or FileZilla SFTP or SCP (port 22) to copy distro ISO image into the newly created directory, path: /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.02/
- From cli go to
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.02/
mv ubuntu-16.04.2-desktop-amd64.iso cdrom.iso
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.02/
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 30G
- Create new lab and add newly created linux-ubuntu-desktop-16.04.02 node
- Connect it to your home LAN cloud/internet, this need to get updates from internet
- Start node in lab and do install of your Linux, customize it as you like, as you have connected it to home LAN and internet this install will be like normal Linux installation.
- Remove cdrom.iso from /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.02/
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.02/ rm -f cdrom.iso
IMPORTANT: Commit the installation to set it as the default image for further use in EVE-NG:
11. On the left side-bar within the lab in the EVE Web-UI choose “Lab Details” to get your lab’s UUID details: In this example: UUID: 3491e0a7-25f8-46e1-b697-ccb4fc4088a2
12. Find out the POD ID of your used and the Node ID of your newly installed node.
The POD number is assigned to your username, and can be found in the EVE GUI, Management/User Management. The Admin user uses POD number 0 by default.
The Node ID can be obtained by right clicking the node on the topology. In this Example it is 8
12. From the EVE CLI, locate the installed image and commit your changes to be used as default for further use in EVE-NG:
cd /opt/unetlab/tmp/0/3491e0a7-25f8-46e1-b697-ccb4fc4088a2/8/
/opt/qemu/bin/qemu-img commit virtioa.qcow2
Advanced instructions on how to make your image smaller in size (sparsify&compress).
13. After you have done all the steps above and your default image is created, you can compress its HDD and make it smaller.
IMPORTANT: for compressing an image you must have sufficient free space on your EVE host, the free space must exceed the total space (30GByte in this example) of the HDD you plan to shrink. The space needed can vary but will be the total space of the disk to be shrunk plus the size of the final sparsified and compressed image. To be safe you should have double the size of the HDD you want to shrink as free space on your EVE host. In our example we needed 35Gbyte of free HDD space. Once this process is done, the temporary file(s) will be deleted and free space reclaimed.
14. From the CLI: go to your windows image directory:
cd /opt/unetlab/addons/qemu/linux-ubuntu-desktop-16.04.02/
and perform the sparsify command:
eve-sparsify --compress virtioa.qcow2 compressedvirtioa.qcow2
15. This will take some time and another compressed image will be created in the same image directory (win-7test)
16. Rename the compressed image name to virtioa.qcow2:
mv compressedvirtioa.qcow2 virtioa.qcow2
17. now you can test your new compressed image on a lab, just wipe the node and start it.
- EVE System Requirements
- Installation
- Virtual Machine Install
- Bare Install
- Google Cloud Install
- EVE-PRO/LC
- Configure EVE during first boot
- Backup EVE-NG content
- Re-install and re-host EVE-PRO
- A10 vThunder
- AlienVault Cybersecurity OSSIM
- Android Nodes
- Arista vEOS
- Aruba ClearPass
- Aruba CX Switch
- Aruba Mobility Controller
- CheckPoint
- Cyberoam Firewall
- Cisco ACS
- Cisco ASAv
- Cisco CSRv1000 (SD-WAN)
- Cisco CSRv1000 16.x, 17.x
- Cisco Catalyst 8000v
- Cisco Catalyst 9000v
- Cisco CUCM
- Cisco DCNM
- Cisco ND (Nexus Dashboard)
- Cisco Dynamips images (Cisco IOS)
- Cisco ESA (Email Security Appliance)
- Cisco Firepower 6 images
- Cisco Firepower 7 images
- Cisco IOL (IOS on Linux)
- Cisco ISE
- Cisco ISRv
- Cisco Nexus 9000v switch
- Cisco Prime Infra
- Cisco StealthWatch
- Cisco vIOS from CML
- Cisco SDWAN Viptela images set
- Cisco vWAAS
- Cisco Wireless C9800-CL
- Cisco vWLC (Virtual Wireless LAN Controller)
- Cisco WSA (Web Security Appliance)
- Cisco SMA Zeus
- Cisco XRv
- Cisco XRv 9000
- Citrix Netscaler
- Clavister Netwall cOS
- Cumulus VX
- Dell OS 10 Switch
- Extreme EXOS
- Extreme VOSS
- F5 BIGIP
- Fortinet images
- Forcepoint FW
- Forescout CounterACT FW
- Hewlett Packard VSR1000
- Hillstone Firewall
- Huawei AR1000v
- Huawei USG6000v
- Infoblox DDI
- Juniper Apstra AOS Server
- Juniper vJunos EX Switch
- Juniper vJunos EVO Router
- Juniper J-Space
- Juniper vMX
- Juniper vQFX
- Juniper VRR
- Juniper SDWAN 128T
- Juniper vSRX 3.0 Version 18.X and later
- Kemp Load Master
- Kerio Control FW
- Linux images
- Mikrotik Cloud router
- MS Windows Workstation
- MS Windows Server
- Nokia VSR Single node
- Nokia VSR Multi Line cards
- OPNsense Firewall
- Palo Alto
- Palo Panorama
- pfSense FW 2.4
- pfSense FW 2.5.2
- Plixer Scrutinizer Netflow
- Pulse Secure Connect
- Radware Alteon VA
- Riverbed SteelHead Virtual CX
- Silver Peak
- SonicWALL FW
- Sophos FW
- Stormshield FW UTM
- TrendMicro vTPS FW
- Versa Networks SD-WAN
- Watchguard FireboxV
- VM Ware ESXi
- VM ware NSX
- VM Ware vCenter
- VM Ware Velocloud SD-WAN
- VyOS Vyatta
- Zabbix Monitoring
- ZScaler Virtual Service Edge (vzen)
- CBT Nuggets Knox Videos
- Cisco CML images
- Commit changes on previously created Qemu image
- EVE embedded Dockers Setup and Usage
- Create customized windows image for EVE
- Designing EVE topology adding objects and text
- Designing EVE mapping nodes to custom topology
- Operate with EVE initial configurations
- Create lab and connect nodes in the EVE
- Expand HDD on EVE VM
- Use HTML5 and native console
- EVE WEB UI Interface functions and features
- Install local management Telnet, VNC and Wireshark for windows
- EVE-NG short presentation
- Template, icons and config scripts update from GIT
- EVE-PRO Upgrade from v4.x to v5.x
- EVE Pro v4 content migration to V5 (rsync)
- Upgrade EVE Professional or Learning Centre to the newest version
- Upgrade EVE Community to the newest version
- Enable SSL EVE PRO with Let’s Encrypt
- Enable SSL EVE Community with Let’s Encrypt
- Enable SSL EVE Community with Self-Sign
- Release Notes EVE (PE) Professional
- Release Notes EVE (CE) Community
EVE-NG hosting partners. Rent EVE server online.
Official partnership. Solution tested and approved by EVE-NG Ltd
Образ роутера на Linux для EVE-NG
В предыдущей публикации был установлен образ EVE-NG и настроена базовая конфигурация. Теперь создадим образ Linux-роутера на основе Debian 11 и добавим его в EVE-NG.
Создание виртуальной машины
Скачиваем образ с официального сайта.
Создаем виртуальную машину, для этих целей будет использоваться VMware Workstation. В процессе настройки ВМ на этапе указания объема диска обязательно выбрать Store virtual disk as a single file.
Т.к. необходим наиболее минимальный образ, то объем диска указываем 3-4 Гб, этого достаточно.
Также, для удобства, на заключительном этапе установки делаем настройку сетевой карты мостом, для этого выбираем Customize Hardware…, выбираем Network adapter -> Bridged, как на изображении ниже.После этого запускаем ВМ и устанавливаем операционную систему.
На этапе установки стоит обратить внимание на то, что графическое окружение устанавливать не нужно, поэтому на шаге software selection оставляем отмеченными только пункты SSH server и standart system utilities.После установки ОС добавим возможность подключения по ssh, для удобства конфигурации. Для этого в файле /etc/ssh/ssdh_config в секцию Authentication добавим строку PermitRootLogin yes, перезапустим сервис ssh systemctl restart ssh.
Установка ПО на виртуальную машину
Подключаемся по ssh к ВМ для установки и настройки необходимых сервисов:
systemctl status inetd.service
● inetd.service - Internet superserver Loaded: loaded (/lib/systemd/system/inetd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-09-15 17:11:40 MSK; 1min 4s ago
- Также необходимо включить доступ по консольному интерфейсу (т.к. EVE-NG использует его, при отсутствии VNC):
systemctl start serial-getty@ttyS0.service systemctl enable serial-getty@ttyS0.service
- Установим программы для работы с сетью:
- FRR — набор утилит для работы с протоколами маршрутизации
apt install traceroute tcpdump dnsutils
Добавление образа в EVE-NG 1
Созданный ранее образ загружаем на виртуальную машину с EVE-NG, для этого:
mkdir /opt/unetlab/addons/qemu/linuxrouter-1.0
Необходимо учитывать схему именования qemu устройств, сначала название папки с образом, а через дефис название образа и версия, либо просто версия. Это имя будет использоваться в шаблоне, для создания устройства.
scp linuxrouter.vmdk root@192.168.22.71:/opt/unetlab/addons/qemu/linuxrouter-1.0/
- На сервере с EVE-NG перейдем в директорию, куда копировали образ, переконвертируем его в формат .qcow2, после чего удалим .vmdk файл:
cd /opt/unetlab/addons/qemu/linuxrouter-1.0/ /opt/qemu/bin/qemu-img convert -f vmdk -O qcow2 linuxrouter.vmdk hda.qcow2 rm linuxrouter.vmdk /opt/unetlab/wrappers/unl_wrapper -a fixpermissions
cd /opt/unetlab/html/templates/amd
cp linux.yml linuxrouter.yml
--- type: qemu description: LinuxRouter name: LinuxRouter cpulimit: 1 icon: Router.png cpu: 1 ram: 1024 ethernet: 4 console: telnet shutdown: 1 qemu_arch: x86_64 qemu_nic: virtio-net-pci qemu_options: -machine type=pc,accel=kvm -serial mon:stdio -nographic -boot order=c .
Здесь мы указали: описание, имя, количество CPU и RAM, количество портов, telnet в качестве консоли и в параметрах qemu использование serial интерфейса
Проверка работы образа
Теперь при добавлении новой Node появляется выбор образа
Также видно, что параметры по умолчанию используются те, которые задавали ранее в шаблоне
Соберем простую топологию, с первое устройство будет роутер Cisco, второе — роутер на Linux
Настроим ip-адреса на обоих устройствах и сделаем ping друг до друга
Router>enable Router#conf t Router(config)#hostname CiscoRouter CiscoRouter(config)#int e0/0 CiscoRouter(config-if)#no sh CiscoRouter(config-if)#ip add 1.1.1.1 255.255.255.0
root@linuxrouter:~# vtysh linuxrouter# configure terminal linuxrouter(config)# interface ens3 linuxrouter(config-if)# ip address 1.1.1.2/24
CiscoRouter#ping 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: . Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
linuxrouter# ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=255 time=0.940 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=255 time=0.655 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=255 time=0.954 ms --- 1.1.1.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2004ms rtt min/avg/max/mdev = 0.655/0.849/0.954/0.137 ms
Как видим образ работает. В следующей статье установим ipsec туннель между Cisco и Linux роутером и настроим OSPF.