concept learnt from IE’s Vol5.0 workbook for “IP Routing”
- When routing to a next-hop value the router performs L2 to L3 resolution on the next-hop address. (e.g. ip route 184.108.40.206 255.255.255.255 220.127.116.11). So in the arp table, you’ll see the MAC for ip address: 18.104.22.168.
- When routing to an INTERFACE, the router performs L2 to L3 resolution on the FINAL destination (not on the next hop). (e.g. ip route 22.214.171.124 255.255.255.255 fa0/0 configured on Router1). Let’s assume 126.96.36.199 is a Loopback interface on Router6 and Router 6 is connected to the LAN via Fa0/6. When we configure the ip route mentioned above on R1, on R1’s ARP table, you’ll see the MAC address of Fa0/6 interface for the loopback of R6 (i.e. 188.8.131.52). This is because, PROXY ARP is enabled by default on the routers. If we were to disable proxy arp on Fa0/6, you’d notice that you won’t be able to ping the loopback of R6 anymore, since the router does not know the correct l2 address to use when building the L2 frame. You’ll see “encapsulation failed” message in the debugs:
*Mar 5 02:18:49.733: IP ARP: creating incomplete entry for IP address: 184.108.40.206 interface FastEthernet0/0
*Mar 5 02:18:49.733: IP ARP: sent req src 220.127.116.11 000f.f756.6560,
dst 18.104.22.168 0000.0000.0000 FastEthernet0/0
*Mar 5 02:18:49.733: IP: s=22.214.171.124 (local), d=126.96.36.199 (FastEthernet0/0), len 100, encapsulation failed.
- Resolution: 1) change the ip routing so it uses next hop rather than ARPing on Final destination. 2)statically configure the MAC address to use when sending packet to the loopback of R6 by using: router(config)”arp 188.8.131.52 <mac> arpa command.