Date: Fri, 19 Jan 1996 11:57:48 -0700 From: Nate Williams <nate@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 Message-ID: <199601191857.LAA15780@rocky.sri.MT.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601191857.LAA15780>