07-20-2015 02:37 PM - edited 03-08-2019 01:02 AM
Hi Everyone,
This is a very easy inquiry, and I'd appreciate your answers. I'm still preparing for ICND1, and I have three routers set up, in Packet Tracer. The setup is in the attached pic.
R2 has a loopback address of 2.2.2.2, and, for the purposes of R3 being able to ping it using R1 as an intermediary, I've added the following, to R3:
R3#show ip route
Gateway of last resort is not set
2.0.0.0/24 is subnetted, 1 subnets
S 2.2.2.0 [1/0] via 10.1.2.1
3.0.0.0/24 is subnetted, 1 subnets
C 3.3.3.0 is directly connected, Loopback0
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.2.0 is directly connected, FastEthernet0/1
Here's what I've added, to R1:
R1#show ip route
Gateway of last resort is 10.1.1.2 to network 0.0.0.0
* 0.0.0.0/32 is subnetted, 1 subnets
S* 0.0.0.0 [1/0] via 10.1.1.2
10.0.0.0/24 is subnetted, 2 subnets
C 10.1.1.0 is directly connected, FastEthernet0/0
C 10.1.2.0 is directly connected, FastEthernet0/1
S* 0.0.0.0/0 [1/0] via 10.1.1.2
As a reference, here's what's on R2:
R2#show ip route
Gateway of last resort is not set
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback0
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.1.0 is directly connected, FastEthernet0/0
My purpose is simply to get R3 to ping/communicate with R2 through R1, using static routes. I get five periods when trying to ping R2, from R3 (not even U's appear). What am I doing wrong, here? Any help is much appreciated.
07-20-2015 11:04 PM
Woodland,
What is the problem, Please clarify ..
07-21-2015 08:10 AM
You're right; I didn't completely clarify my purpose.
I'm wanting R2 and R3 to communicate with each other, using R1 as the forwarding router.
07-23-2015 12:05 AM
Hi
If You do a standard ping from R3 towards R2 ip 2.2.2.2 the router R3 uses ip 10.1.2.2 as a source for the packet.
R3 looks in his routing tabel a see 2.2.2.0 in the routing table and forwards the packket towards R1.
R1 get the packet looks in hos routing table, see 0.0.0.0 and forwards the packet to R2.
R2 gets the packet realize it is for himself, processes the packet, construct a return packet towards R2.
R2 looks in the routing table to look for 10.1.2.2, doesn't have an entry for that detination and therefore drops the packet.
/Mikael
07-23-2015 12:44 AM
Ok, now its clear that you miss configured ( ip default-network ) command. Do it as follows;
R2
ip default-network 10.1.1.0
R3
ip default-network 10.1.2.0
Regards
Please rate if its helpfull
07-20-2015 11:53 PM
Please paste the below output from all the three routers:
sh run | i ip route
sh ip int brief
07-21-2015 08:10 AM
....
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide