From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: Yurij.Plotnikov@oktetlabs.ru, netdev@vger.kernel.org,
Alexandra.Kossovsky@oktetlabs.ru
Subject: Re: TCP socket receives strange packet
Date: Tue, 14 Oct 2014 12:32:59 -0400 (EDT) [thread overview]
Message-ID: <20141014.123259.185699262217339879.davem@davemloft.net> (raw)
In-Reply-To: <1413298852.17109.3.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 14 Oct 2014 08:00:52 -0700
> On Tue, 2014-10-14 at 18:09 +0400, Yurij M. Plotnikov wrote:
>> Connected TCP socket receives packet without timestamps option which
>> exists in SYN, SYNACK and ACK. It is packet 4 in attached tcpdump output.
>>
>> tcpdump output description: The host has address 10.208.10.1 (server)
>> and the peer host has address 10.208.10.2 (client).
>>
>> Establishing connection: Timestamps option exists in SYN, SYNACK and ACK
>> (packets 1, 2 and 3 in attached file), so accepted socket should receive
>> packets only with timestamps option.
>
> Can you point the RFC paragraph stating so ?
There is no requirement that timestamps be present just because they
were successfuly negoatiated during the handshake.
This has been brought up before several times.
prev parent reply other threads:[~2014-10-14 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 14:09 TCP socket receives strange packet Yurij M. Plotnikov
2014-10-14 15:00 ` Eric Dumazet
2014-10-14 15:40 ` John Heffner
2014-10-14 16:41 ` Christoph Paasch
2014-10-14 16:50 ` David Miller
2014-10-14 16:54 ` Christoph Paasch
2014-10-14 16:32 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141014.123259.185699262217339879.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Alexandra.Kossovsky@oktetlabs.ru \
--cc=Yurij.Plotnikov@oktetlabs.ru \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox