Eve ng нет интернета

Restart Networking:

[email protected]:~# systemctl restart networking 

Turn on IPv4 Forwarding:

Edit /etc/sysctl.conf as root and uncomment: # net.ipv4.ip_forward=1 so that it reads: net.ipv4.ip_forward=1 

Force sysctl to read the new values from the file:

sudo -i sysctl -p /etc/sysctl.conf 

Configure iptables to NAT outbound connections:

sudo -i iptables -t nat -A POSTROUTING -s 10.199.199.0/24 -o pnet0 -j MASQUERADE # The source "-s ##.###.###.#/##" needs to match the subnet you configured the "pnet1" interface with from above. 

Make iptables changes persistent:

Save the current iptables rules (including the new rule we just added) and create a new file for our script:

sudo -i [email protected]:~# iptables-save > /etc/iptables.rules [email protected]:~# nano /etc/network/if-pre-up.d/iptables 

Enter this content:

#!/bin/sh iptables-restore < /etc/iptables.rules exit 0 

Save changes then edit/create next “iptables” file:

[email protected]:~# nano /etc/network/if-post-down.d/iptables 

Enter this content:

#!/bin/sh iptables-save -c > /etc/iptables.rules if [ -f /etc/iptables.rules ]; then iptables-restore < /etc/iptables.rules fi exit 0 

Save changes. Make both files executable:

sudo chmod +x /etc/network/if-post-down.d/iptables sudo chmod +x /etc/network/if-pre-up.d/iptables 

Troubleshooting

The Proper Process

I have had great success with this process:

1. Making the above configuration changes to the VM.
2. Adding the Cloud 1 network to your topology.
3. Adding any device images.
4. Connecting their MGMT interfaces to Cloud 1.
5. Power on the device images.
6. Configure their MGMT IP address, subnet mask and Default Gateway.
7. Ping the Default Gateway
8. Ping an external network (8.8.8.8)

Your first test should always verify you can ping your default gateway(pnet1 interface) from your lab images. If you cannot ping your default gateway try these steps:

• Shutdown your lab images conencted to Cloud 1 and restart them. Try to ping the Default GW.
• Delete your Cloud 1 from your topology, save and exit your topology. Launch your topology again and drop in the Cloud 1 network again, reconnect it to the device images mgmt interfaces and start the device images.

Источник

EVE-NG access to the Internet from lab nodes.

EVE-NG community edition doesn’t support NAT Cloud. We need a workaround to Connect nodes inside EVE-NG with the Internet.

1- When you create a node indide EVE-NG, you assign its interfaces private IP addresses.
Any interface of this node to have access to the Internet needs:
– A gateway to access the Internet and
– Its IP to be translated to a public IP because its IP is not real ==> (PAT or Port Forwarding)
The only real IP that we have is the external IP assigned to the VM instance hosting EVE-NG.
2- EVE-NG, during installation, creates 10 bridge interfaces on the host machine:

The role of a bridge interface is to connect a guest (a node inside EVE) interface to the host network interface (eth0).

How to Connect nodes inside EVE-NG with the Internet

Let’s assume you have assigned an IP of 192.168.13.10/24 to the windows server node in our topology so you will need a gateway with an IP in this subnet to access the Internet (let’s say 192.168.13.1):

1- Create a virtual gateway with an IP address from the 192.168.13.0/24 subnet:

ip address add 192.168.13.1/24 dev pnet1

You can configure any pnet interface (leave pnet0 for the Management access only).

To make this configuration persistent to survive between reboots:

vim /etc/network/interfaces

iface eth1 inet manual auto pnet1 iface pnet1 inet static address 192.168.13.1 netmask 255.255.255.0 bridge_ports eth1 bridge_stp off 

2-As the communication between the guest and host interfaces is established on the kernel level, you need to enable IP forwarding in the kernel:

echo 1 > /proc/sys/net/ipv4/ip_forward

To make IP forwarding persistent:

vim /etc/sysctl.conf

and uncomment net.ipv4.ip_forward=1

3- Translate the IP addresses in this subnet to the dynamic interface IP address of the VM instance:

iptables -t nat -A POSTROUTING -o pnet0 -s 192.168.13.0/24 -j MASQUERADE

To save this configuration:

apt-get install iptables-persistent

Follow the wizard, the defaults are what we need. Then:

netfilter-persistent save netfilter-persistent reload

Verification

1- Add Cloud1 network (equivalent to pnet1):

2- Connect it to windows server node:

3- RDP the windows server node and open any web browser and test any web server on the Internet:

It works!
Note:
Cloudx is equivalent to pnetx, i.e., if you have configured pnet2 for another subnet, connect the nodes in this subnet to cloud2 if they need access directly to the Internet.

Источник

Настройка сети Eve-ng

После того как мы в прошлой статье создали виртуальную машину с Eve-ng, настала очередь подготовить сеть. В конце статьи я описывал что нужно запустить пару sh скриптов которые нам создадут виртуальные интерфейсы.

Вырезка из прошлой статьи

Переходим в каталог : cd /opt/ovf и запускаем файл sh ovfstartup.sh , после его настройки запускаем sh ovfconfig.sh. После данной настройки у нас появятся виртуальные сетевые интерфейсы.

Проверяем работу сети

Для проверки мы будем использовать интерфейсс подключение типа Мост и виртуальным стенд компьютером который установлен в комплекте с eve-ng.

Авторизовываемся в веб интерфейсе

Добавляем новый обьект — Add an object

Выбираем тип обьекта — Network

Выбираем наш интерфейс — Management(Cloud0) он и есть интерфейс типа мост. Такой интрефейс будет смотреть в нашу сеть!

После добавления сети на карту , добавим и стендовый компьютер.
Выбираем Add an object — Node

из списка выбираем Virtual PC(VPCS)

После добавления, от облака Net , от его розетки(Синяя на скриншоте) тянем провод до розетки стенда(VPC)

Нажимаем Start и подключаемся к стенду. Если возникают ошибки устанавливаем пак для Windows для подключения https://www.eve-ng.net/index.php/download/#DL-WIN

В консоле вбиваем команду dhcp — для автоматического получения адреса
Либо для статического адреса команда
ip 192.168.88.10/24

Видим что адрес нам выдался , а значит сеть через мост работает корректно.

Последнее проверяем пинги, если идут значит все хорошо.

Источник