|
Bugtraq
mailing list archives
Re: TCP Timestamping and Remotely gathering uptime information
From: bert hubert <ahu () DS9A NL>
Date: Mon, 19 Mar 2001 19:48:23 +0100
On Sat, Mar 17, 2001 at 12:31:22AM +0000, Stephen White wrote:
On Wed, Mar, 2001, Bret wrote:
either by creating a new 'timestamp clock' for
each TCP session (that uses timestamps)
You can't do this .. it breaks the use of such timestamps for things
like TCP Sequence number wrap-around protection on fast networks
(gigabit).
Yes you can. PAWS is not needed to differentiate *different* sessions,
unless you also cycle through all your local ports in a few seconds. Which
is exceedingly unlikely.
Regards,
bert hubert
--
http://www.PowerDNS.com Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
By Date
By Thread
Current thread:
- Re: TCP Timestamping and Remotely gathering uptime information, (continued)
Re: TCP Timestamping and Remotely gathering uptime information Chris Tobkin (Mar 19)
Re: TCP Timestamping and Remotely gathering uptime information Ted U (Mar 19)
Re: TCP Timestamping and Remotely gathering uptime information Matt Lewis (Mar 19)
|