EVE-NG (VMware) Connecting to the Internet

KB ID 0001432

Problem

I did an article a while back on doing this with UNL, so I thought I’d revisit it today for EVE-NG. I really like EVE-NG, for proof of concept work, testing, and just learning new products I cant think of any product better.

But what if you want to connect your labs to the outside world? 

Solution

In all honesty a lot of this article you can skip, I’m just showing you what’s going on down at the Linux level (so you can be sure yours will be OK).

I’m assuming you already have EVE-NG installed and some images in it, and know how to create a lab, and that you want to connect that lab to the internet.

Unlike UNL, EVE-NG will deploy with only one vNIC, (below I’m using vSphere 6), so to keep things nice and simple I’m just going to add one more;

VMXNet3 is fine, just make sure it’s connected to the correct port-group.

Note: You can probably skip down to allowing promiscuous mode below. As the good folk at EVE-NG have configured all the hard stuff for you!

SSH into your EVE-NG server > log on as the root user, and make sure it can see BOTH network cards, with the following command;

ifconfig -a | grep ^eth

Above you can see the original eth0, and the one I just added eth1.

You probably already have nano installed, (it’s a text editor). But just in case, run the following command;

apt-get install nano

Use nano to edit/view the network card settings; 

nano /etc/network/interfaces

Scroll down to the settings for eth1 and make sure it is tied to, (bridged to)  pnet1 (as below). Repeat for any additional network cards.

To exit nano Press CTRL+X, (then if you have made any changes save them).

You can also see a summary of bridged interfaces with the following command;

brctl show/box]

Enable Promiscuous Mode

Your Hyper Visor (VMware) needs to be able to see traffic from your EVE-NG devices, coming out though the vNIC we added earlier, that means a lot of MAC addresses are going to be coming from the MAC address of that vNIC. By default VMWare will block that. so we need to enable promiscuous mode on the port-group that we connected to earlier, (mine was called VM Network).

If you are using the older VMware (Fat) client, see the link at the bottom of the page for the older UNL article.

Edit the port group;

On the Security tab > Tick ‘Override’, and set it to ‘Accept’ > OK.

Add Cloud Objects to EVE-NG

Above, (if you remember) the vNIC (eth1) was bridged to pnet1. These used to be labelled pnet1, pnet2, etc. Now they are labelled Cloud1, Cloud2, etc.

In your lab workspace add a ‘Network’ object.

Select Cloud1 (remember this is mapped to pnet1, which is bridged to eth1.). You may want to change the name from Net, to something like ‘Internet’.

Connect a device to it, (I’m using a router, because they are quick and easy to setup).

EVE-NG Router Live Internet connection

My Network has DHCP on it, so my router picked up an IP from my LAN, and once I’d given it a default route, I now have full internet access from the lab.

011 -EVE-NG Router Test Internet connection

Related Articles, References, Credits, or External Links

Unified Networking Lab – Connecting ESX VM to the Internet

Author: PeteLong

Share This Post On

10 Comments

  1. Thank you! This post saved me some time and nerve!

    Post a Reply
  2. HI,
    Thanks a lot for this post, very helpful.

    For your information, I use vlan tagging on my home lab. and I needed also ‘Accept Forged transmits” on top of “Promiscous mode” on my lab to make it work.

    Post a Reply
  3. I am running EVE-NG on Azure (baremetal installation) and this method is not working for me.

    could you please let me know if i need to make any other change?

    Post a Reply
    • Try this.

      root@eve-ng1:/etc/network# vi interfaces
      # This file describes the network interfaces available on your system
      # and how to activate them. For more information, see interfaces(5).

      # The loopback network interface
      auto lo
      iface lo inet loopback

      # The primary network interface
      iface eth0 inet manual
      auto pnet0
      iface pnet0 inet dhcp
      bridge_ports eth0
      bridge_stp off

      # Cloud devices
      iface eth1 inet manual
      auto pnet1
      iface pnet1 inet static
      address 192.168.0.1
      netmask 255.255.255.0
      network 192.168.0.0
      bridge_ports eth1
      bridge_stp off

      iface eth2 inet manual
      auto pnet2
      iface pnet2 inet manual
      bridge_ports eth2
      bridge_stp off

      iface eth3 inet manual
      auto pnet3
      iface pnet3 inet manual
      bridge_ports eth3
      bridge_stp off

      iface eth4 inet manual
      auto pnet4
      iface pnet4 inet manual
      bridge_ports eth4
      bridge_stp off

      iface eth5 inet manual
      auto pnet5
      iface pnet5 inet manual
      bridge_ports eth5
      bridge_stp off

      iface eth6 inet manual
      auto pnet6
      iface pnet6 inet manual
      bridge_ports eth6
      bridge_stp off

      iface eth7 inet manual
      auto pnet7
      iface pnet7 inet manual
      bridge_ports eth7
      bridge_stp off

      iface eth8 inet manual
      auto pnet8
      iface pnet8 inet manual
      bridge_ports eth8
      bridge_stp off

      iface eth9 inet manual
      auto pnet9
      iface pnet9 inet manual
      bridge_ports eth9
      bridge_stp off

      Post a Reply
  4. Thank you for posting this. I’ve been pulling my hair out for hours.

    Post a Reply
  5. Hi, Can you please explain for VMware, I was able to follow steps successfully before “Enable Promiscuous Mode” but, don’t know how to do on VMware® Workstation 12 Pro?
    Screenshots you have added, it is for the vSphere web client.
    I am not sure how to enable promiscuous mode on VMware Workstation.

    Please help!

    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *