John Neiberger wrote:
>
> 'ip mobile arp' is what allows that device to communicate with
> the local
> router interface. Without that command you'll never end up with
> an entry for
> the errant device in the ARP table of the router.
I will if I have a static route pointing to a broadcast interface. Since you
need the static route anyway, I am not quite sure why the 'ip mobile arp'
command is useful (at all, not just in this situation).
In fact I now tried it out and without the static route, the router which
has 'ip mobile arp' configured, still keeps ARPing out on the interface
where the subnet is configured, even though it has an ARP entry for the
misconfigured device pointing to the interface where that device is
configured:
XXX#sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 20.0.0.1 - 000c.8640.1038 ARPA FastEthernet2/0
Internet 30.0.0.2 5 000c.8640.0c38 ARPA FastEthernet2/0
Internet 30.0.0.3 64 000c.8640.081e ARPA Ethernet1/2
Internet 30.0.0.1 - 000c.8640.101e ARPA Ethernet1/2
XXX#ping 30.0.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 30.0.0.2, timeout is 2 seconds:
01:07:56: IP ARP: sent req src 30.0.0.1 000c.8640.101e,
dst 30.0.0.2 0000.0000.0000 Ethernet1/2.
01:07:58: IP ARP: sent req src 30.0.0.1 000c.8640.101e,
dst 30.0.0.2 0000.0000.0000 Ethernet1/2.
01:08:00: IP ARP: sent req src 30.0.0.1 000c.8640.101e,
dst 30.0.0.2 0000.0000.0000 Ethernet1/2.
01:08:02: IP ARP: sent req src 30.0.0.1 000c.8640.101e,
dst 30.0.0.2 0000.0000.0000 Ethernet1/2.
01:08:04: IP ARP: sent req src 30.0.0.1 000c.8640.101e,
dst 30.0.0.2 0000.0000.0000 Ethernet1/2.
Success rate is 0 percent (0/5)
This might be a bug, of course...
Thanks,
Zsombor
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=73404&t=73370
--------------------------------------------------
**Please support GroupStudy by purchasing from the GroupStudy Store:
http://shop.groupstudy.com
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
