GNS3 – Network Cards Are Missing

KB ID 0000964 

Problem

Like most techies, I am always fiddling with things. One of my mottoes is “If you never break anything, you never learn how to fix things”. So after messing around with the networks in VMware Workstation (What I typically use for connecting GNS3 to either real machines, or the outside world). I lost the network connections in GNS3 and could not get them back. Seems like any new NICs that you add are not listed either.

Solution

Note: It might be worth resetting your VMware Workstation Network settings before continuing. (Edit > Virtual Network Editor > Restore default).

1. To make things simple, I’ve renamed the Network Cards installed by VMware workstation to something a little more descriptive, (if you unsure which is which, just run ‘ipconfig’).

2. Let’s double check, drop to command line and run the following command;

[box]
netsh interface ipv4 show interfaces
[/box]

3. And let’s affirm what GNS3 is telling us by running the following script from the GNS3 directory;

[box]
“C:Program FilesGNS3network-device-list.cmd”[/box]

LEAVE THIS WINDOW OPEN

4. As you can see (above) there is a discrepancy. To get GNS3 to ‘sync’ with windows we need to restart the NetGroup Packet Filter Driver service. Open an elevated command prompt and issue the following commands;

[box]

net stop npf
net start n/f

[/box]

5. Now execute the script again and it should show the correct network adapters.

6. Now from within GNS3 you can add the correct network cards to your ‘Clouds’.

Related Articles, References, Credits, or External Links

NA

Connecting GNS3 to VMware Workstation

KB ID 0000996 

Problem

A while back I got an email “Here is a suggestion for an article. ‘How to link GNS3 with VMware Workstation'”. Sorry it’s taken me so long to get round to it, here you go Daniel Newton.

Solution

Before we start I’m assuming you have installed VMware Workstation, and you’ve installed and configured GNS3.

1. Launch VMware Workstation > Edit > Virtual Network Editor > By default there will be three networks, the one we are concerned with is the ‘NAT‘ one. I change the default IP range, (in the example below to 123.123.123.123 255.255.255.0) > Apply > OK.

2. NAT Settings > Set the default gateway for the network (Tip: Don’t choose .1, I’ve had problems with that in the past) > OK.

3. DHCP Settings > Even if you’re not going to use DHCP, enter a range of IP addresses on your network > OK.

4. Windows Key + R > ncpa.cpl {Enter} > Notice there’s two new network connections, one for the NAT network, and one for the ‘Host only’ network.

5. To avoid confusion, I rename them.

6. So they are easily identifiable, (you will see why later).

7. In GNS3 drag a ‘Cloud’ onto your workspace.

8. Right click > Configure > NIO Ethernet > Select the Network drop-down box > Select your VMware NAT interface.

9. Add > Apply > OK.

10. Note: If you are working with Cisco ASA firewalls, you cannot simply connect it to the cloud, you need to put a hub/switch or router in between them, or you will see this error message;

Dynamips error
Device does not support this type of NIO. Use an ETHSW or
hub to bridge the connection to the NIO instead.

11. With a switch in between you can connect them together.

12. Now if you give the outside of the firewall an IP on the correct network range (you configure in step 1), and set its default route to point to the gateway address, (you configured in step 2). You will have public Internet access, (assuming the host computer has Internet access).

13 Working with routers (and switches) you can connect them directly to the cloud.

14. Again set the interface IP correctly, and the default route, and you will have public Internet access.

 

Related Articles, References, Credits, or External Links

NA