Date: Fri, 19 Jan 1996 12:30:56 -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: <199601191930.MAA15955@rocky.sri.MT.net> In-Reply-To: <9601191924.AA10122@halloran-eldar.lcs.mit.edu> References: <m0tczOi-0000SaC@pelican.com> <199601182009.NAA12968@rocky.sri.MT.net> <9601191811.AA10365@halloran-eldar.lcs.mit.edu> <199601191857.LAA15780@rocky.sri.MT.net> <9601191924.AA10122@halloran-eldar.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.
>
> 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.
This is obviously not the case.
204.182.243.200 is an unused IP address on my network.
gateway:~ # ping 204.182.243.200
PING 204.182.243.200 (204.182.243.200): 56 data bytes
^C
--- 204.182.243.200 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss
gateway:~ # arp -a
? (204.182.243.200) at (incomplete)
gateway:~ # route get 204.182.243.200
route to: 204.182.243.200
destination: 204.182.243.200
interface: ed0
flags: <UP,HOST,DONE,LLINFO>
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire
16384 16384 0 0 0 0 1500 -6
gateway:~ #
gateway:~ # arp -a
? (204.182.243.200) at (incomplete)
gateway:~ #
gateway:~ # route get 204.182.243.200
route to: 204.182.243.200
destination: 204.182.243.200
interface: ed0
flags: <UP,HOST,DONE,LLINFO>
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire
16384 16384 0 0 0 0 1500 -8
gateway:~ #
gateway:~ # arp -a
? (204.182.243.200) at (incomplete)
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601191930.MAA15955>