EVE-NG – Initial Configs

EVE-NG – Initial Configs

EVE is the ultimate emulation environment. It was renamed from the UNetLab (Unified Network Lab) and you have to love it. This platform is just amazing and you can emulate an entire enterprise network from desktop to servers and from L2 switch to firewalls. You name it EVE does it.

First download the OVA file from UnetLab


Open the download ova file in VMWare Palyer.


When it loads, press the play button to power up the Virtual Machine.


Use the root login with the default password eve. After that in the first boot we will be asked to make change the basic configurations of the system, starting with the root password.


Then we will have the opportunity to change the hostname, the domain and the network configuration mode, where we can choose from DHCP or STATIC. Since we will be accessing EVE as a server it is advise to make the network configurations STATIC.


Then add the desired IP configurations. IP Address, Network Mask, Default Gateway,  Primary and Secondary DNS Server, NTP Server and Proxy according to the network were you virtual machine will be running. After this configuration, EVE will reboot and we will get the prompt to login in to CLI.


But before we can continue with the system configuration there is a issue that must be attended. Has you can see the the pic above EVE is complaining that there is no virtualisation capability in your processor. This will be needed for us to run virtual machines inside EVE which is already a VM (nested virtualisation).

To fix this we must go to the folder where the EVE VM disk is located and we need to alter the file VM_NAME.vmx (EVE-ALFA.vmx in my case).

In this file add the following line to the end:

vhv.enable = "TRUE"

Then reboot the VM again and it should be fixed.


At this point the EVE environment is ready for us to access. Just point the browser to the address we previously configured.


The web default user is admin with the password unl.


Before we continue the are some important changes to be done in the file system. There are 2 folder that will grow drastically in terms of space when we start to use EVE.

Those folders are:

  • /opt/unetlab/addons/qemu/ (equipment images folder)
  • /opt/unetlab/tmp/ (lab folder)

Since the disk of the virtual machine only has 20GB of space, we will add two more virtual disk (give it 100GB each) and permanently mount each one of this folders in an individual disk.

So, shutdown the VM and add the disks.


For demonstration the disk we add only have 5GB of space.

Power it back up and create a primary  partition in each one.


Use the command fdisk -l to identify the create disks, then fdisk /dev/sdb and sdc in our case to create the partitions. Use the options n for new partition, p for primary and w to write the changes into the disk. Use the defaults for the rest of the configurations.


Format the partition with the command mkfs -t ext3 /dev/sdb1.


Add the mount command to the fstab file to permanently mount the folders.

Open the file /etc/fstab with a text editor and add the following line to the end of the file

/dev/sdb1    /opt/unetlab/addons/qemu    ext3    defaults    0    0
/dev/sdc1   /opt/unetlab/tmp    ext3     defaults     0     0



Next post we will add some images to EVE so you can start enjoying it.

Until then, stay good


8 thoughts on “EVE-NG – Initial Configs

  1. hi, when a kame the command mkfs -t ext3 /dev/sdb1, say: “/dev/sdb/1 is apparently in nuse by the system; will not mke a filesystem here


  2. TIP:

    For EVE installations in laptop computers, make sure that after you you load the OVA image enter the virtual machine settings and alter the “network adapter”.

    By default it’s in “bridge”, change it to “NAT” so that the virtual machine shares your public IP, meaning that EVE can communicate with the Internet, wherever you are.

    After this configuration is done, you will start the virtual machine and do the initial configuration.

    Do as suggested and configure a static IP address. It can be any IP address you desire, just make sure that the “Default Gateway” and the “Primary DNS” addresses are the second available address in the Network that you entered in the machines address.

    What this means is: If the network you chose was, the IP address for your machine can be something as “”, but you must use the address “” for both the DNS and DG.
    This is because the virtual machine has the address and you computer has the address. This will mean that the machine asks your computer for that information.

    Hope it was useful.

    Good luck.

    Liked by 1 person

Comments are closed.