well, you're pinging 100.200.3.1 but the router tries to contact 192.168.3.1
.....

does that give you a hint ???

Kevin Wigle

----- Original Message -----
From: "Sim, CT (Chee Tong)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, 01 February, 2001 22:33
Subject: why can't ping its own interface it is up ????


> Dear all,
>
> I really don't understand, I have the router interface which is up up
> status, but I can't even ping it? What could be the reasons?? is that
> because of access-list?? Pls tell me!!
>
> interface Ethernet0
>  description Interface facing Financial Service Provider
>  ip address 100.200.3.1 255.255.255.0
>  ip access-group 100 in
>  no ip directed-broadcast
>  ip nat outside
>
> RBFW2514#sh int e0
> Ethernet0 is up, line protocol is up
>   Hardware is Lance, address is 0010.7b81.02e6 (bia 0010.7b81.02e6)
>   Description: Interface facing Financial Service Provider
>   Internet address is 100.200.3.1/24
>   MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
>      reliability 255/255, txload 1/255, rxload 1/255
>   Encapsulation ARPA, loopback not set
>   Keepalive set (10 sec)
>   ARP type: ARPA, ARP Timeout 04:00:00
>   Last input 00:00:00, output 00:00:00, output hang never
>   Last clearing of "show interface" counters never
>   Queueing strategy: fifo
>   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
>   5 minute input rate 45000 bits/sec, 21 packets/sec
>   5 minute output rate 8000 bits/sec, 16 packets/sec
>      161686946 packets input, 2454329523 bytes, 0 no buffer
>      Received 1076750 broadcasts, 0 runts, 0 giants, 0 throttles
>      181 input errors, 0 CRC, 0 frame, 0 overrun, 181 ignored
>      0 input packets with dribble condition detected
>      129416824 packets output, 3918760326 bytes, 0 underruns
>      0 output errors, 296169 collisions, 1 interface resets
>      0 babbles, 0 late collision, 478162 deferred
>      0 lost carrier, 0 no carrier
>      0 output buffer failures, 0 output buffers swapped out
> RBFW2514#ping 100.200.3.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> RBFW2514#
>
> ==================================================================
> De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
> is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
> onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
> de afzender direct te informeren door het bericht te retourneren.
> ==================================================================
> The information contained in this message may be confidential
> and is intended to be exclusively for the addressee. Should you
> receive this message unintentionally, please do not use the contents
> herein and notify the sender immediately by return e-mail.
>
>
> ==================================================================
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>

_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to