![]() ![]() Connecting GNS3 to the Internet – Scenario 2 That’s all, now scroll down to the last part of configuring NAT and DNS servers. Try pinging a public IP address such as 8.8.8.8, if you ping a domain name such as you’ll receive an “Unrecognized host or address, or protocol not running” error as we have not yet configured DNS. If you assigned the IP address manually a default route has to be added to ensure internet connectivity. If you had choose the DHCP way of assigning IP address you will see the following line *Mar 1 01:24:31.751: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0/0 assigned DHCP address 192.168.1.101, mask 255.255.255.0, hostname R1 R1(config-if)#ip address dhcpĮlse assign the a static IP address R1(config-if)#ip address 192.168.1.3 255.255.255.0īring this interface “up” R1(config-if)#no shutdown Now if the modem/router connected to the physical computer has a built in DHCP server use the following command to configure the router port to recieve IP address via DHCP. Select and add the network interface of the physical computerĬonnect a router to this cloud using an ethernet link, open the console of the router and navigate to the interface which is connected to the cloud node. Place a cloud node in your topology, right-click select configure and from the drop down list under the ethernet tab select “Local Area Connection” on Windows or “eth0” on Linux and click OK. Open GNS3 as an administrator (Windows) by right clicking it and selecting “Run as administrator” or as a root user (Linux) by using the sudo command. ![]() This is the simplest means of connecting GNS3 to the internet. In this scenario your physical machine is connected to a modem/router using a RJ45 cable and the ethernet port of your computer has a private IP address assigned manually or via DHCP. ![]() (Physical interface has a private IP address) Connecting GNS3 to the Internet – Scenario 1 Apart from making configuration changes to your operating system NAT has to be configured on the emulated router that connects to the internet. But if you are using a WiFi connection/Data card/a device that requires you to assign a public IP on the physical interface getting your lab to access the internet requires a few more commands in Linux or a few more clicks in Windows. If you just have an ADSL modem/router connected to the ethernet port of your physical machine having a private IP address it is very simple to get your lab to the internet. There are many ways to do this based on what internet connection you are using. You should reboot your computer, though.Connecting GNS3 to the internet is just another step to bring your emulated network lab closer to real gear. You don’t need to set up an IP address to this adapter or change any other parameters at this time. It is a good idea to rename this adapter in “Network and Sharing Center” from, say, “Local Area Connection 3” to LOOPBACK3, vmnet3 or something that makes more sense to you in the following steps. Go “Next-Next-Finish” and you have a Loopback adapter installed. The “Add Hardware” wizard starts:Īfter clicking “Next”, select “Install the hardware that I manually select from a list (Advanced)”:įrom the “Manufacturer” list chose Microsoft and from “Network Adapter” pick “Microsoft Loopback Adapter”: Go Start and type “hdwwiz” and press enter. The easiest way of beginning the procedure is starting a hardware wizard. I’m sure it will work for other Windows OSs as well, but I did tried on these two. This blog applies to both Windows 7 and Windows Server 2008. Beside, I need a short blog for a change □ Adding a loopback adapter, how complicated that could be? Well, not complicated at all, but it is a necessery step for interconnecting GNS3 labs with VMWare Workstation machines or even a physical world. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |