From owner-freebsd-current  Fri Jan 19 10:56:42 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA04402
          for current-outgoing; Fri, 19 Jan 1996 10:56:42 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA04392
          for <current@FreeBSD.org>; Fri, 19 Jan 1996 10:56:36 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA15780; Fri, 19 Jan 1996 11:57:48 -0700
Date: Fri, 19 Jan 1996 11:57:48 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199601191857.LAA15780@rocky.sri.MT.net>
To: "Garrett A. Wollman" <wollman@lcs.mit.edu>
Cc: Nate Williams <nate@sri.MT.net>, current@FreeBSD.org
Subject: Re: pppd route/proxy problem
In-Reply-To: <9601191811.AA10365@halloran-eldar.lcs.mit.edu>
References: <m0tczOi-0000SaC@pelican.com>
	<199601182009.NAA12968@rocky.sri.MT.net>
	<9601191811.AA10365@halloran-eldar.lcs.mit.edu>
Sender: owner-current@FreeBSD.org
Precedence: bulk

> >> 3.  It would be nice to have a flag (-v?) for arp -a that would
> >> print out *all* the arp info including expire time or lack of it...
> 
> > I'm not sure this information is even gettable in the kernel, and I
> > don't see how it would be that helpful.  If you know when it times out
> > how will that help you?
> 
> In fact, `route get dot.ted.qu.ad' will tell you almost everything
> that the kernel knows.

Cool.  However, it's not obvious to find when ARP request expire?  The
expire numbers start at zero and are getting more and more negative.
Are they waiting for expire + mtu = 0?


Nate