Support and News Forum

Hi,

I'm currently having an issue and I've trying to resolve it for several hours now so I'm hoping that someone might be able to help out.

My setup:
----------

VM Workstations PC:
---------------------------
Windows 8, 32 gig ram, 1 nic
VMWorkstation 12 pro (new install)
Host PC run VM has an IP of 192.168.1.100/24 - gw is 192.168.1.1
All firewalls are off on PC



VM of Eve-NG - install
--------------------
eve-ng 2.0.3-59 (I know the main page says 2.0.3-69 but I have reinstalled and update at least 5 times trying to solve this)
eve-ng IP (static) is 192.168.1.75/24 - gw is 192.168.1.1 - dns is 8.8.8.8
eve-ng is setup in bridge mode with only network adapter in VMware
eve-ng can ping the node 192.168.1.54
eve-ng can update without issues

Node or Router running inside Eve-ng
-----------------------------------------------------
Node inside eve-ng has DHCP setup - pulling IP of 192.168.1.54/24 -gateway of 192.168.1.1
Node cannot ping 192.168.1.1
Node cannot ping systems outside of VM
Node can ping 192.168.1.75
Node is connected to Cloud0 via gig0/0
Node does not have an arp entry from 192.168.1.1

Gateway - cannot ping the node 192.168.1.54
Gateway - can ping the host 192.168.1.100
Gateway - can ping Eve-ng 192.168.1.75


My problem is that Node cannot communicate to the default gateway or other devices on the 192.168.1.0/24 network. I know this should be a pretty basic configuration and I have tried to keep it as simple as possible. I've reinstall VMworkstation, reinstalled Eve-ng, tried bridge mode, cloud0, and cloud1.

Now I had a similar problem like this once before on an ESXi setup and that turned out to be setting the nic to promiscuous mode. I'm pretty sure I cannot do that in VM Workstation - looked for a while.

This is what I am able to prove:

-eve-ng and update without any issues
-eve-ng can ping the default gateway without issue
-eve-ng can ping the node without any issue
-eve-ng can ping 192.168.1.5 - another real PC
-node can ping eve-ng without any issuee
-node cannot ping 192.168.1.1
-node cannot ping 192.168.1.5
-wireshark on the PC show packets leaving from the node going out the gateway and then replies coming back - but the node never sees them

Also if someone could confirm what the following setting should be that would be great?

vmware
----------
VMnet0 - currently set to bridged
VMnet1 - currently set to NAT - connect to host virtual adapter to this network
VMnet8 - host-only

vm
-----
network adapter - bridged

What can be stopping the packet from getting back to the node if the PC is seeing the reply in wireshark? This is kinda driving me a bit crazy. I also find it strange that the node can pull an IP from the gateway but is not able to ping it but then again it does not have an arp entry for the gateway. The gateway does have an arp entry from the node.

Andy.

p.s. thanks for any help in advance.

network 192.168.1.0/24 is your home LAN???
Means bridged to with Home LAN?

What is subnet for NAT adapter?

silly mistake I guess, lost logic..

UD

..

Maybe it would be better if I explained what I'm trying to do and see if it's possible.

I trying to run VM Workstation 12 (192.168.1.100/24) with Eve-ng (VM) (192.168.1.75/24) so that the nodes (192.168.1.X/24) inside are on the same subnet , is this possible?

Andy

mate you didnt answer what VMnet interface is used for 192.168.100.0/24 and which interface VMnet is 192.168.75.0/24 ??

Like my VM ware is:
bridged interface responding to 172.25.1.0/24 subnet
NAT interface responding 192.168.10.0/24
vmnet1 responding 192.168.20.0/24

I need to know this... !!!
'VM ware is very flexible, and even I dont know understand your connections, I will answer yes it is possible

UD

I really am thankful for your help and working with me through this. I have a feeling that what I'm trying my not be possible because I"m using vmware workstation and not esxi.

Let me try to explain what I would like to accomplish:

I would like run evn-ng on vmware workstation 12, run a small lab inside of it and then be able to ssh to the lab from another PC on the local lan.

Let me give a small example. Inside of Eve have one cisco router running and it is connected to a cloud (0 or 1) inside the lab. I would like the router to pull an IP from a real ASA (192.168.1.1) and to have other devices on 192.168.1.0/24 be able to connect to the virtual router inside of Eve-ng.

support information:
home lan is 192.168.1.0/24
pc running vmware workstation is 192.168.1.100
eve-ng is running on 192.168.1.75 inside of pc above
default gateway for pc and vm is 192.168.1.1 (real cisco asa, also the dhcp server for 192.168.1.0/24)

I"m able to get the router to pull a dchp address from 192.168.1.1 but unable to ping it. This similar setup worked on my ESXi system but I'm unable to get the same function on my vm workstation. Now on ESXi I had to put the network ports in promiscuous mode to get that to work but I find no similar setting in vmware workstation.

Also, sorry if I'm not explaining this the best, I trying.

Andy

Your scenario must work 100%.

Asuume that EVE router E0/0 IP 192.168.1.11/24, def route GW .1 connected to cloud0.
Cloud0 is management interface and reside in same subnet 192.168.1.0.
Be sure your first nic on EVE VM is bridged, vmnet0 usually. This means your real PC NIc card is bridged with vnet0 and cloud0.
All sit in 192.168.1.0.
ASA as I understand is your GW 192.168.1.1/24.

Questions does your PC can ping GW .1?
Does EVE VM from cli can ping .1?
Does EVE router connected to cloud can ping your PC .100, and GW .1??

You have to check your PC FW settings specially icmp, is there allowed pings for any IP ???
in win8 and win10 it is closed by default.
carefully inspect your win FW advanced settings regarding inbound/outbound echo requests.
Must permit any IP.
You can find me in skype: uldisd.poisonfish
there is some simple silly miestake only:)