Support and News Forum

Hello,

I am using EVE on Ubuntu 18 Desktop. I have a router connected to Management Cloud but I cannot ping the vmnet interface (in my case, vmnet8 in NAT mode). From the Eve cli, I can ping the router and can also reach internet, but using the router, can't ping vmnet8 and the internet as well.

vmnet8 IP: 172.16.199.1
Router's interface (connected to Management cloud): 172.16.199.250
Mask: 255.255.255.0

Router (vIOS) is configured with the route: 0.0.0.0 0.0.0.0 via 172.16.199.1

Any suggestions or help is highly appreciated.

BTW, I can successfully ping internet using a Windows host machine.

Thanks,
-Uzair

If you have VM Ware installed on your Ubuntu desktop and EVE VM in is and your mgmt is NAT interface,
GW is .2 not 1 !!!
172.16.199.2, is special NAT IP for vmnet8 and it is GW for all NAT subnet

Uldis

Thanks for your response Uldis.

Even ping to .2 IP fails from the router connected to Management cloud. Can't figure out why....

Thanks,
-Uzair

Thanks, It worked plus setting up the vmnet8 in promiscuous mode.

Uzair

It failed again after working for a little bit.

Router is directly connected to Management Cloud.
vmnet8: 172.16.119.1
mask: 255.255.255.0
NAT IP: 172.16.119.2

Router's interface connected to MCloud: 172.16.119.100
Mask: 255.255.255.0

Host machine: 172.16.119.0/24 dev vmnet8 proto kernel scope link src 172.16.119.1 metric 100

Why can't I ping the router from the host machine? I am preparing for my exam and this thing has caused too much of a problem. Iptables are empty as firewall is disabled on Ubuntu host machine. vmnet8 adapter is set to obtain IP address automatically. Whenever Eve boots, it generates an error message that the ethernet port canot be set in Promiscous mode. I do it manually always using "ifconfig eno1 promisc" command. Any suggestions please?

I tried Ubuntu 18 and after reaching it;s not supported, installed Ubuntu 16 but same problem. What am I missing? Please help.

I configured the network adapter of the EVE VM to bridged mode which now uses the same physical interface's subnet ip, it still doesnt work. My 2 days are not burnt to no avail.

Thanks,
-Uzair