From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Mon Jun 07 2004 - 19:51:46 GMT-3
Peng,
Because there isn't an ARP entry for 192.168.1.3. Since there
isn't a device on the segment to reply to the 192.168.1.3 ARP request,
the router does not know the destination MAC address for the packet.
This means that the router can not build the packet and in turn
generates an encapsulation failed message.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Peng Zheng
Sent: Monday, June 07, 2004 3:41 PM
To: ccielab@groupstudy.com
Subject: encapsulation failed when ping a nonexist host
R1----R2, connect by ethernet.
ip for R1: 192.168.1.1
ip for R2: 192.168.1.2
From R1, if I ping ip for R2, it is OK. But if I ping
any other nonexist IP(for instance, 192.168.1.3), I
got "encapsulation failed". Does anyone know why this
happen?
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:34 GMT-3