Models 2A Unusual Ping Results

Lets test connectivity to them loopbacks:

As we are guessing right now.... there is no routing protocol advertising these networks (DONT ASSUME ONE) so no match in the routing table...

lets enable debug ip packet which shows the issue (obviously in a production network, this is a no no, you would have to be more specific with the debug)

no match shown above in the routing table (and no default route neither)

lets add that static route route in then try pinging again....

MMmmm unreachable, yup you guessed it, R1 does not know how to reach the 2.2.2.2 network, lets run debug ip packet to show:

Here you can see R1 is replying back unreachable (where as before we didnt see anything from R1, we just unroutable from the local router - R3)

Those U's are  a downstream router saying "i dont know how to get to this network"

Lets add the route into R1s routing table:

lets try the ping again from R1 and R3

Notice you can now see the Source address of 2.2.2.2 in the debug

tag(s)
ping, traceroute, show controllers, debug ip packet, recommended nist time server