From owner-freebsd-current Fri Jan 19 15:12:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA23376 for current-outgoing; Fri, 19 Jan 1996 15:12:21 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA23366 for ; Fri, 19 Jan 1996 15:12:17 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53111(6)>; Fri, 19 Jan 1996 15:11:39 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Fri, 19 Jan 1996 15:11:28 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: Nate Williams cc: "Garrett A. Wollman" , current@freebsd.org Subject: Re: pppd route/proxy problem In-reply-to: Your message of "Fri, 19 Jan 1996 11:30:56 PST." <199601191930.MAA15955@rocky.sri.MT.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Jan 1996 15:11:24 PST From: Bill Fenner Message-Id: <96Jan19.151128pst.177478@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org Precedence: bulk In message <199601191930.MAA15955@rocky.sri.MT.net> Nate wrote: >Garrett: >> If they are negative, they should have already expired. The kernel >> actually stores an explicit expiration time, and the `route' and >> `netstat' programs subtract the current time for you. Unresolved arp entries use the expiration time to store the last time that an ARP request was sent. There is a timer that goes off every 5 minutes and removes all unresolved ARP entries (apparently including those that were just created). So, the timer for an unresolved ARP will generally be negative. (It could be a small positive number, which along with the RTF_REJECT flag indicates that the kernel is trying to avoid flooding the net with ARP requests) (e.g. there's no way to know when an unresolved ARP request is going to disappear from the routing table, other than "probably in less than 5 minutes".) Bill