unable to ping directly connected interface ( Mind Bender)

Sep 18, 2007 2 Replies

I'm setting up a home lab



and I've configured my Frame relay switch



and 2 routers so far



I'm able to ping across the cloud but not to the directly connected interface



ie



R1 192.168.2.1 R2 192.168.2.2



from R1 I can ping 192.168.2.2 but from R1 I can't ping 192.168.2.1



If I set up a frame-relay map I can ping the serial interface on R1 from R1



but it sends the traffic out to the switch then back



what would cause this?


Ben



R2 router config

interface Serial0/1 ip address 192.168.2.2 255.255.255.0 encapsulation frame-relay frame-relay map ip 192.168.2.1 201 broadcast no frame-relay inverse-arp

When you ping a Cisco router's own point-to-point interface, it sends the packet out the interface, with the expectation that the device at the other end will forward it back. The idea, I believe, is that this can be used to test that the interface is really connected.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required