Is that correct? I thought that a ping to a router's own
interface would be moved across from the output queue to the
input queue on that interface - if the stack is written properly
which many ATM ones aren't. I don't think the packet will appear
out-with the router. Similarly a broadcast has to be sent to the
all-hosts address (ethernet FF:FF:FF:FF:FF:FF) and /also/ copied
across to the input queue. I remember reading this in one of
Douglas Comer's excellent books: I hope I remember correctly.
Anyone care to comment?
Jim
""John Neiberger"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Show ip route connected will show any networks that are
directly connected
> to a local interface. If you can't ping the interface, then
you have a
> problem either locally or on the remote side of the link.
>
> When you ping a local interface, the packet actually traverses
the link,
> then back, then across again, and then back again. It's
crazy, but that's
> the way it works. If you're experiencing any sort of line
issues or if
> things aren't configured correctly, pings to a local interface
may fail.
>
> HTH,
> John
>
> | Hi all
> | We have eigrp network.
> | When I do "sh ip rou co" --- what ip address are those
under "C"? it says
> it
> | is directly connected. Then why couldn't I ping?
> | It is not local router's interface address, or remote
router's serial
> | interface. Then what ip address ?
> | Thanks
> | JP
> |
> |
> |
> |
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
[EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=16503&t=11219
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
