<div dir="ltr">From the RFC (<a href="http://www.networksorcery.com/enp/rfc/rfc1323.txt">http://www.networksorcery.com/enp/rfc/rfc1323.txt</a>):<br><pre> TCP Timestamps Option (TSopt):
Kind: 8
Length: 10 bytes
+-------+-------+---------------------+---------------------+
|Kind=8 | 10 | TS Value (TSval) |TS Echo Reply (TSecr)|
+-------+-------+---------------------+---------------------+
1 1 4 4
The Timestamps option carries two four-byte timestamp fields.
The Timestamp Value field (TSval) contains the current value of
the timestamp clock of the TCP sending the option.
The Timestamp Echo Reply field (TSecr) is only valid if the ACK
bit is set in the TCP header; if it is valid, it echos a times-
tamp 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.<br><br></pre><pre>When you enable timestamps they don't match so the packet is discarded, this could be due to the ISP fiddling with the packets on the way.<br></pre><pre>
Regards,<br></pre><pre>Eliyahu - אליהו<br></pre><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/1/24 Shachar Shemesh <span dir="ltr"><<a href="mailto:shachar@shemesh.biz" target="_blank">shachar@shemesh.biz</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="direction:ltr" text="#000000" bgcolor="#FFFFFF"><div><div class="h5">
<div>On 01/24/2013 10:04 AM, shimi wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<br>
<div class="gmail_quote">On Thu, Jan 24, 2013 at 8:54 AM,
Shachar Shemesh <span dir="ltr"><<a href="mailto:shachar@shemesh.biz" target="_blank">shachar@shemesh.biz</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="direction:ltr" text="#000000" bgcolor="#FFFFFF">
<div>Hail the conquering hero!<br>
<br>
Color me dumbfounded. Disabling TCP timestamps actually
allows me to connect to Google. Reenabling them
re-introduces the problem.<br>
<br>
The only question still remaining is "why"? I have up on
the site two captures. One of the working session, and
one of the not working session. To me, this still looks
like a kernel bug.<br>
<br>
Get them:<br>
<a href="http://www.shemesh.biz/connection/working.dump" target="_blank">http://www.shemesh.biz/connection/working.dump</a><br>
<a href="http://www.shemesh.biz/connection/notworking.dump" target="_blank">http://www.shemesh.biz/connection/notworking.dump</a><br>
<br>
Ideas, anyone?<br>
</div>
</div>
</blockquote>
<div><br>
Really have to go now, so I cannot take a look at the
captures, but...<br>
<br>
You started the thread with "This is NOT an ISP problem".
Any chance you're using BezeqInt?<br>
</div>
</div>
</div>
</blockquote></div></div>
Indeed I am. Please stop sounding clairvoyant and start sharing your
experience. If I need to call and yell, I want to be as informed as
I can get.<span class="HOEnZb"><font color="#888888"><br>
<br>
Shachar<br>
<br>
<pre cols="72">--
Shachar Shemesh
</pre>
</font></span></div>
<br>_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
<br></blockquote></div><br></div>