- GNS3 2.2.17
- VMware Workstation for Windows 16.1.0
- Windows 10 x64 Version 20H2 (Build 19042.685)
- Cisco CSR 1000v (csr1000v-universalk9.17.03.02-serial.qcow2)
When I created GNS3 VM, I told it to use NAT network. As shown in the picture below, it got a DHCP IP 192.168.21.128.
In GNS3, create a CSR instance and connect to GNS3-VM cloud, so that the CSR can have Internet access (to download software). If your GNS3-VM has only one NIC, it'd be eth0. My GNS3-VM has two NICs and the eth1 is connected to the NAT network. When connecting CSR's Gi1 to the GNS3-VM eth1, we actually put the CSR Gi1 into the NAT network.
In home lab, you may do it in a different way. You may configure VPG with "ip unnumber Gi1". VGP will use the IP of Gi1. Then configure the Guest Shell interface in the same subnet as Gi1 (but a different IP). The advantage is - one less subnet in the network. No NAT is needed. The disadvantage is - you need to allocate an IP in the same subnet as Gi1. (this shouldn't be a problem in home lab though). This option is illustrated in the diagram below:
Configure Guest Shell parameters. In the example below, 192.168.28.130 is the VPG IP. 192.168.28.127 is an arbitrary (available) IP in the same subnet. 18.104.22.168 is a DNS server.