RE: (ASCEND) Arp routing

[Dave Van Allen <dave@fast.net>]

RFC 826 (the ARP RFC) specifically avoided the time-out/cache aging issue.
I don't know where cisco decided that 4 hours was Good Thing.  In fact, in a
modern environment the arp table should be small enough on the local segment
to make aging any value you want outside of the time expected to move a host
or replace a NIC.


Best regards,

David Van Allen - FASTNET(tm) / You Tools Corporation
dave@fast.net (888)321-FAST(3278) http://www.fast.net
FASTNET - Business and Personal Internet Solutions




-----Original Message-----
From: Phillip Vandry [mailto:vandry@Mlink.NET]
Sent: Tuesday, April 07, 1998 5:54 PM
To: gerard@mnet.fr
Cc: ascend-users@bungi.com
Subject: Re: (ASCEND) Arp routing 


> Doest anybody has an idea for either :
>     - clearing arp table in cisco

Default Cisco ARP parameters:

  ARP type: ARPA, ARP Timeout 04:00:00

That's 4 hours!

I recommend not using "Arp" routing except for things (like the pools)
which are always going to stay on one Max or the other.

-Phil
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

• Prev by Date: Re: (ASCEND) V.90 Status?
• Next by Date: RE: (ASCEND) Ascend Pipeline50 and DHCP
• Prev by thread: RE: (ASCEND) Arp routing
• Next by thread: (ASCEND) Hard Timeout settings
• Index(es):
  • Main
  • Thread