It is currently Mon Sep 16, 2019 4:40 pm


All times are UTC




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: Can't ping VMNET hosts from not directly connected routers
PostPosted: Wed Feb 03, 2010 7:32 pm 
After figuring out that I need to run everything from the root account, connecting devices together using serial and vmnet interfaces work great. I'm looking forward to leaving packet tracer behind.

I have gns3 .71 rc1 running on ubuntu and I'm very close to getting my vmware workstation vmnet hosts to communicate, but I'm running into a problem. Do you mind taking a moment to help me solve this? I have watched every video I can find and read everything I can lay my hands on. Here is the scenario. I have started with the most basic configuration possible.

[PC1/vmnet1] <-> Cloud1/vmnet1 <-> f0/0 Router1 s0/0 <-> s0/0 Router2 f0/0 <-> [Cloud2/vmnet2] <-> [PC2/vmnet2]

After configuring Cloud1 for linux ethernet nio:vmnet1 and connecting Cloud1 to Router1(f0/0) I can ping from both sides successfully. I then configure Cloud2 for linux ethernet nio:vmnet2 and connect to Router2 via f0/0 I can ping successfully from both sides as well. I then connect Router1(s0/0) with Router2(s0/0) while the power if off. I have tried both RIPv1 and Static route configurations on each router but cannot seem to get vmnet1 to successfully ping vmnet2 when I 'show ip route' I do see the proper networks in each router's routing table. I am even able to ping the f0/0 interfaces from each opposite router.

PROBLEM_1: I can't ping VMNET1 from Router2 and I can't ping VMNET2 from Router1

PROBLEM_2: I can't ping VMNET2 from VMNET1

I have included a topology screenshot from GNS3 and console results from each router.

Image

-=-=-=-=-=-
| Router 1 |
-=-=-=-=-=-


>>The appropriate routes are in the routing table for the VMNET2 network via RIP<<

R1#show ip route

172.16.0.0/24 is subnetted, 1 subnets
C 172.16.1.0 is directly connected, Serial0/0
R 192.168.102.0/24 [120/1] via 172.16.1.2, 00:00:14, Serial0/0
C 192.168.101.0/24 is directly connected, FastEthernet0/0

>>I CAN ping VMNET1 from Router1<<

R1#ping 192.168.101.129

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.101.129, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/16/64 ms

>>I CAN ping f0/0 interface on Router2 which faces VMNET2<<

R1#ping 192.168.102.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.102.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/23/32 ms

>>I CAN'T ping VMNET2<<

R1#ping 192.168.102.130

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.102.130, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)


-=-=-=-=-=-
| Router 2 |
-=-=-=-=-=-


>>The appropriate routes are in the routing table for the VMNET1 network via RIP<<

R2#show ip route

172.16.0.0/24 is subnetted, 1 subnets
C 172.16.1.0 is directly connected, Serial0/0
C 192.168.102.0/24 is directly connected, FastEthernet0/0
R 192.168.101.0/24 [120/1] via 172.16.1.1, 00:00:20, Serial0/0

>>I CAN ping VMNET2<<

R2#ping 192.168.102.130

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.102.130, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/23/36 ms

>>I CAN ping f0/0 on Router1 which faces VMNET1<<

R2#ping 192.168.101.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.101.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/37/48 ms

>>I CAN'T ping VMNET1<<

R2#ping 192.168.101.129

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.101.129, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)




Top
  
 
 Post subject: Re: Can't ping VMNET hosts from not directly connected routers
PostPosted: Thu Feb 04, 2010 5:48 pm 
Offline

Joined: Mon Oct 13, 2008 11:26 am
Posts: 817
Location: Finland
And what are default gateways for those PCs? I seems that default gateways are missing or misconfigured. This is because from PCs you have connectivity only to local subnet (no gateway is needed). Or is it true?

_________________
Br,
Kaage
Image Image


Top
 Profile  
 
 Post subject: Re: Can't ping VMNET hosts from not directly connected routers
PostPosted: Thu Feb 04, 2010 10:03 pm 
Thank you Kaage. You nailed it! I did not have a default gateway set for either VMNET machine. Once I configured the default gateway for the vm's I was able to ping all interfaces and hosts on the topology. Viva GNS!


Top
  
 
 Post subject: Re: Can't ping VMNET hosts from not directly connected routers
PostPosted: Sun Mar 14, 2010 9:43 pm 
how do you assign the default gateway??
what command did you use in the router configuration??
i'm still newbie in using GNS3, so your help would be so helpful...


Top
  
 
 Post subject: Re: Can't ping VMNET hosts from not directly connected routers
PostPosted: Mon Aug 02, 2010 6:26 pm 
I set the default gateway on the nic of the virtual machine. In my case I was using ttylinux distro for the virtual machine which means I edited /etc/sysconfig/network-scripts/ifcfg-eth0 and restarted the nic.




Top
  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group

phpBB SEO