<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Testing for TCP/IP Timestamps</title>
	<atom:link href="https://www.exploresecurity.com/testing-for-tcp-ip-timestamps/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.exploresecurity.com/testing-for-tcp-ip-timestamps/</link>
	<description>IT security tools, techniques and commentary</description>
	<lastBuildDate>Sun, 07 Sep 2025 03:12:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6.1</generator>
	<item>
		<title>By: Trias</title>
		<link>https://www.exploresecurity.com/testing-for-tcp-ip-timestamps/#comment-14876</link>
		<dc:creator>Trias</dc:creator>
		<pubDate>Thu, 04 May 2017 18:43:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.exploresecurity.com/?p=261#comment-14876</guid>
		<description><![CDATA[Timestamp Echo Reply (TSecr). 32 bits.
This field is only valid if the ACK bit is set in the TCP header. If it is valid, it echos a timestamp value that was sent by the remote TCP in the TSval field of a Timestamps option. When TSecr is not valid, its value must be zero. The TSecr value will generally be from the most recent Timestamp option that was received; however, there are exceptions that are explained below. A TCP may send the Timestamp option in an initial SYN segment (i.e., segment containing a SYN bit and no ACK bit), and may send a TSopt in other segments only if it received a TSopt in the initial SYN segment for the connection.]]></description>
		<content:encoded><![CDATA[<p>Timestamp Echo Reply (TSecr). 32 bits.<br />
This field is only valid if the ACK bit is set in the TCP header. If it is valid, it echos a timestamp value that was sent by the remote TCP in the TSval field of a Timestamps option. When TSecr is not valid, its value must be zero. The TSecr value will generally be from the most recent Timestamp option that was received; however, there are exceptions that are explained below. A TCP may send the Timestamp option in an initial SYN segment (i.e., segment containing a SYN bit and no ACK bit), and may send a TSopt in other segments only if it received a TSopt in the initial SYN segment for the connection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anant Shrivastava</title>
		<link>https://www.exploresecurity.com/testing-for-tcp-ip-timestamps/#comment-2464</link>
		<dc:creator>Anant Shrivastava</dc:creator>
		<pubDate>Tue, 28 Oct 2014 06:48:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.exploresecurity.com/?p=261#comment-2464</guid>
		<description><![CDATA[or we can do 

hping3 -S -c 2   -p  --tcp-timestamp]]></description>
		<content:encoded><![CDATA[<p>or we can do </p>
<p>hping3 -S -c 2   -p  &#8211;tcp-timestamp</p>
]]></content:encoded>
	</item>
</channel>
</rss>
