I cannot ping any sites when using NAT node to connect GNS3 to the internet. I get a DHCP address in the 192.168.122.x subnet but cannot ping www.google.com or any other. I saw lab where this works so not sure if it my machine/gns3 setup or even service provider. |
Windows 10 Prof x64 also using GNS3 2.0.0b4 Using the NAT interface on the GNS3 VM (eth1) I am able to ping www.google.com. The NAT interface I am using is the default VMWare NAT vmnet8 with IP 192.168.116.0/24 gateway IP 192.168.116.2. The IOUL2 interface has static IP of 192.168.166.200/24. Default route 192.168.116.2 and name server 8.8.8.8. Hope this helps. |
How your GNS3 is installed? You use the GNS3 VM? |
GNS3 v2.0 beta 4 on 64 bit Windows 7 machine. My GNS3 VM is installed onVMWare workstation 12. …On Thu, Mar 2, 2017 at 2:35 AM, Julien Duponchelle ***@***.*** > wrote: How your GNS3 is installed? You use the GNS3 VM? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1896 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ8qzx-r2eKChUcUd3Jhoupd93geRx6Kks5rhnFAgaJpZM4MQZ_k> . |
I am using Windows 7 x64 and also using 2.0 0 b4. I am not able to selectvmnet8 as option. Can you send me screens shots on how u have this setup? …On Wed, Mar 1, 2017 at 10:12 PM, jtorri ***@***.***> wrote: Windows 10 Prof x64 also using GNS3 2.0.0b4 Using the NAT interface on the GNS3 VM (eth1) I am able to ping www.google.com. The NAT interface I am using is the default VMWare NAT vmnet8 with IP 192.168.116.0/24 gateway IP 192.168.116.2. The IOUL2 interface has static IP of 192.168.166.200/24. Default route 192.168.116.2 and name server 8.8.8.8. Hope this helps. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1896 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ8qz_15PCwOLroZ8F0XiYBeYL8oHP9Jks5rhjONgaJpZM4MQZ_k> . |
GNS3 comes with a command file, vmnet-manager.cmd, located in the folder into which GNS3 application was installed, e.g., c:program filesGNS3 2.0.0b4 If you open a DOS prompt as Windows administrator and run vmnet-manager.cmd it will add additional vmnet interfaces to VMware Workstation. One of those will be vmnet8 as NAT. As you know, you can via the VMWare Workstation network editor decide yourself which vmnet interface you wish to be NAT. Also, when you 'create' the GNS3 VM in VMware Workstation you have the opinion, as with any virtual machine, to add/edit or delete virtual NICs. The default for GNS3 VM is eth0 is host only and eth1 is NAT. You can add a third virtual NIC, eth2, as bridged mode if you like. Hope this helps. |
It already has vmnet8 as NAT but in subnet 192.168.193.0. My router is adhcp ip address from the NAT node in subnet 192.168.122.0 and think that iswhy I am having the issue. Also, only one interface can NAT which vmnet8 isNAT. I am knew to this so not sure what to do. …On Thu, Mar 2, 2017 at 9:34 PM, jtorri ***@***.***> wrote: GNS3 comes with a command file, vmnet-manager.cmd, located in the folder into which GNS3 application was installed, e.g., c:program filesGNS3 2.0.0b4 If you open a DOS prompt as Windows administrator and run vmnet-manager.cmd it will add additional vmnet interfaces to VMware Workstation. One of those will be vmnet8 as NAT. As you know, you can via the VMWare Workstation network editor decide yourself which vmnet interface you wish to be NAT. Also, when you 'create' the GNS3 VM in VMware Workstation you have the opinion, as with any virtual machine, to add/edit or delete virtual NICs. The default for GNS3 VM is eth0 is host only and eth1 is NAT. You can add a third virtual NIC, eth2, as bridged mode if you like. Hope this helps. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1896 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ8qz0altiMHfip6546TQRWe3FlIWRFpks5rh3xNgaJpZM4MQZ_k> . |
KeVI121, I am not able to reproduce your problem. I'm using GNS3 v2.0 beta 4 on 64 bit Windows 10, with the GNS3 VM is installed on VMWare workstation 12.5. To create the test I added a NAT node and a VPCS node to my topology. I then logged into the PC and acquired an address via DHCP and was able to ping internet addresses with no problem. As you can see, it was successful. In VMware, I have not changed the default network adapters that are created in the GNS3 VM. I have only added a third network interface, but that has no effect on this test. I suggest that you try the same experiment. If it works, then maybe there is a problem with your IOUL2 configuration. |
KeVI121 Yep it can be confusing. Can you post a screen shot of your topology? The specific IP of the NAT interface is not important. What is important is the gateway IP of the NAT interface and the configuration of the interface on the network object from which you are trying to ping. You can use the VMWare Workstation network editor to determine the gateway IP of your VMWare Workstation's NAT vmnet. Then use that information to configure the interface of your network object's, e.g, router, appropriate default route, Then configure a name-server and, ip domain-lookup, of course. If you are using a virtual machine, e.g., Lubuntu, from which to ping there may be another issue. Hope this helps! |
Joe,thanks for showing me your VM settings. The issue was I only had oneNetwork Adapter. Once i added Network Adapter 2 as NAT interface now i canping google and cisco. I tried with VPCS like you did in your topology buti will also try with router.Once again, thank you much!!KevA …On Fri, Mar 3, 2017 at 12:50 AM, Joe Lazaro ***@***.***> wrote: KeVI121, I am not able to reproduce your problem. I'm using GNS3 v2.0 beta 4 on 64 bit Windows 10, with the GNS3 VM is installed on VMWare workstation 12.5. To create the test I added a NAT node and a VPCS node to my topology. [image: topology] <https://cloud.githubusercontent.com/assets/25847784/23539661/95f69b22-ff91-11e6-8e61-22625705696a.PNG> I then logged into the PC and acquired an address via DHCP and was able to ping internet addresses with no problem. `PC4> ip dhcp DDORA IP 192.168.122.10/24 GW 192.168.122.1 PC4> ping 8.8.8.8 84 bytes from 8.8.8.8 icmp_seq=1 ttl=127 time=16.301 ms 84 bytes from 8.8.8.8 icmp_seq=2 ttl=127 time=17.954 ms 84 bytes from 8.8.8.8 icmp_seq=3 ttl=127 time=18.485 ms 84 bytes from 8.8.8.8 icmp_seq=4 ttl=127 time=15.060 ms 84 bytes from 8.8.8.8 icmp_seq=5 ttl=127 time=14.050 ms PC4> ping www.google.comwww.google.com resolved to 216.58.216.132 84 bytes from 216.58.216.132 icmp_seq=1 ttl=127 time=28.022 ms 84 bytes from 216.58.216.132 icmp_seq=2 ttl=127 time=27.758 ms 84 bytes from 216.58.216.132 icmp_seq=3 ttl=127 time=29.507 ms 84 bytes from 216.58.216.132 icmp_seq=4 ttl=127 time=28.445 ms 84 bytes from 216.58.216.132 icmp_seq=5 ttl=127 time=50.120 ms PC4>` As you can see, it was successful. In VMware, I have not changed the default network adapters that are created in the GNS3 VM. I have only added a third network interface, but that has no effect on this test. [image: image] <https://cloud.githubusercontent.com/assets/25847784/23539727/fdc0cf02-ff91-11e6-8f85-f2ff5fec9a2a.png> I suggest that you try the same experiment. If it works, then maybe there is a problem with your IOUL2 configuration. - Joe — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1896 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ8qzw8HG-GC290G8x748OwlRYWCwyYHks5rh6oygaJpZM4MQZ_k> . |
jtorri,I figured out the issue. My VM settings only had one Network Adapter (HostOnly). I added a 2nd Network adapter as NAT now i can ping. I didn'tchecked the Virtual Network Editor settings and saw there was a NATinterface there so I assumed there would be NAT adapter in the VM settings.My topology was simple really, a VPCS or router connected to the NAT Node.I appreciate the help and feedback though!! Thanks!! …On Fri, Mar 3, 2017 at 8:19 AM, jtorri ***@***.***> wrote: KeVI121 Yep it can be confusing. Can you post a screen shot of your topology? The specific IP of the NAT interface is not important. What is important is the gateway IP of the NAT interface and the configuration of the interface on the network object from which you are trying to ping. You can use the VMWare Workstation network editor to determine the gateway IP of your VMWare Workstation's NAT vmnet. Then use that information to configure the interface of your network object's, e.g, router, appropriate default route, Then configure a name-server and, ip domain-lookup, of course. If you are using a virtual machine, e.g., Lubuntu, from which to ping there may be another issue. Hope this helps! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1896 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQ8qzygMxhC1Li94vUdxfCiaok5NEd3Nks5riBNMgaJpZM4MQZ_k> . |
KeVI121 Clearly I need to ask a few more questions before offering advice! :) I did not even consider you might be using the NAT object or VPCS. Like you, glad it's all solved! |
It seem solve, I close the issue thanks everyone. |