VMware emulates PCs. GNS3 emulates routers. For example Cisco Call Manger uses PC to act as the Telephone System Manager so you could use VMware to run the software. GNS3 can connect to equipment in the real world so you might have GNS3 emulating a network and a soft phone running on your PC or even a real telephone. Look for VMware ESXi on the dowmload tab.
try youtube.com and theblindhog.net
free vmware are vmware player and vmware server (was in past, not ESXi, search for server in the name).
you can create a file to be used in vmware player, then use vmware player to open it and create virtual machine.
vmware player cannot create new virtual machines from scratch.
but if you need just a PC to ping or traceroute with GNS3, you can get by with VPCS (small program that runns 8 PCs, virtual ones)
get it here http://www.freecode.com.cn/doku.php?id=wiki:vpcs
Unfortunately, I have been unable to get VMWare to work with GNS3. I'm trying to do a simple lab with a syslog server running in VMWare and can't get any interface to access the VMWare system except the one on the same subnet (192.168.3.1). That inferface on R3 can ping the VMNet8 network adapter in C3 but no other interface can. Also, from the VMWare system, I can ping 192.168.3.1 but no other interfaces.
The network is operating properly and every interface on every router can ping the others. Also, I have the default gateway on the VMNet8 apapter set to 192.168.3.1 on R3.
The same problems exist for the VMNet1 network adapter. I have no idea how to fix it. I've looked at it for hours.
I also don't understand why there are two VMNet adapters shown in my host when the guest has only one adapter installed. That network adapter is installed in NAT mode in VMWare.
If anyone has any advice, I'd appreciate it.
VMWareIssue.jpg 249.7 K
I shall cut the long story short. Give the following a try.. let me know if it works and we can discuss later.
Let VMware do some of the IP default gateway work, so,
- Set on your REAL OS the, VMware Network Adapter VMnet8 to obtain an IP address automatically (192.168.3.1 will be assigned)
- Manually set within the virtual OS installed on VMware, an IP address of 192.168.3.3/24, GW 192.168.3.2
- Assign 192.168.3.2 to R3's f0/0 interface
- Ping 10.2.2.1 from 192.168.3.3 should be successful
Forgot mention, Under "edit virtual machine settings" for VMnet8 , select Network Adapter and set the Network connection to "custom:specific virtual network".
Select, VMnet8 (Host-only) option.
see attached image.
Message was edited by: Ahmed A
Message was edited by: Ahmed A
Re - vmware issue.JPG 744.8 K
In addition to the configs as posted,
If the VMware Network Adapter on your REAL system is set to pick an IP address automatically (which 192.168.3.1 is given)
and you were to set R3's F0/0 IP to 192.168.3.1/24, as well as set the virtual OS's ip address and default gateway manually set to 192.168.3.3/24 and GW 192.168.3.1
A "Windows - System Error There is an IP address conflict with another system on the network" may be generated.
Hence the choice of 192.168.3.2 as the default gateway for the VMware Virtual OS, as well as R3 F0/0 interface.
Without doing any research into the ins/outs of the VMware Network Adpater installed on you real OS, and despite the "windows system error" a ping from the virtual OS to 10.2.2.1 is still successful.
Any thoughts to this would be appreciated.
Thank you for your response. Unfortunately, when I switch the VMNet8 on the host to get the ip address automatically, it gets 192.168.184.1. I do not have DHCP configured on R3 so I'm not sure where it is getting this address. My real network has DHCP configured but it only uses 192.168.0.0.
I am unable to ping anything now from VMWare guest. I can't even ping R3. Is it possible VMWare player (free version) doesn't work fully? I can't seem to get it to do the things you are doing with VMWare workstation.
I finally got it working! The issue was not with VMWare or GNS3. The issue was with XP routing. I have all this running on an XP system. It did not have the correct routes to send any traffic from VMWare to anything beyond R3. To make a long story short, I used wireshark to observe the problem. I then googled XP routing to learn about it and get the commands needed. I ending up doing the following.
For some reason, XP was adding a default route with a metric of 1 to the next
hop of the Microsoft Loopback adapter. This was causing all the traffic for
anything beyond R3 to be sent to the loopback adapter and not the VMNet adapter.
This solution will allow me to use either VMNet1, VMNet8, or the Loopback adapter.
The networks used in GNS3 will have to be one of the networks listed below or
a subnet of that one.
I want the default route to have a next hop to my real router on my real network.
The networks that each of the adpaters in my system use are the following. The second
address is the default gateway. The 0x? number is from "route print" and used with
networking commands for XP.
Marvell Yukon 192.168.0.6 255.255.255.0 192.168.0.1 0x5
Microsoft Loopback 172.16.0.2 255.255.255.0 172.16.0.1 0x4
VMNet1 172.16.1.2 255.255.255.0 172.16.1.1 0x3
VMNet8 172.16.8.2 255.255.255.0 172.16.8.1 0x2
I picked the following networks to be used with GNS3 when using the associated adapter.
10.0.0.0 255.255.255.0 to be used with Microsoft Loopback
10.1.0.0 255.255.255.0 to be used with VMnet1
10.8.0.0 255.255.255.0 to be used with VMNet8
From the cmd prompt, I did the following.
First see existing routes and adapter numbers.
Next clear routes.
Now add needed routes. (arguments used: destination, mask, next hop, metric, interface)
route -p add 0.0.0.0 mask 0.0.0.0 192.168.0.1 METRIC 1 IF 0x5 (this is my real network)
route -p add 10.0.0.0 mask 255.255.0.0 172.16.0.1 if 0x4 (this is for Microsoft loopback)
route -p add 10.1.0.0 mask 255.255.0.0 172.16.1.1 if 0x3 (this is for VMnet1)
route -p add 10.8.0.0 mask 255.255.0.0 172.16.8.1 if 0x2 (this is for VMNet8)
Thanks for helping me work through this! Now i can do all the CCNA Security labs with GNS3 and VMWare Player.