From: Alex Dubov <oakad@yahoo.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: Bad TCP timestamps on non-PC platforms
Date: Thu, 6 Jan 2011 17:55:34 -0800 (PST) [thread overview]
Message-ID: <117536.54377.qm@web37607.mail.mud.yahoo.com> (raw)
In-Reply-To: <1294301356.2723.73.camel@edumazet-laptop>
Sorry for the awful synopsis of my problem. I never cease to amaze myself
at how bad those usually turn up. :-)
What I really meant to write is:
I have a dev board running 2.6.37-rc7. Normal kernel config, nothing fancy.
Remote machines are just usual linux boxes in constant operation (I tried
several of those).
UDP/DHCP works correctly all the time, so ethernet side is probably ok.
When tcp_timestamps are enabled, SYN packets from dev board just get
ignored by the remote side. I see them arrive in wireshark, but nothing
else happens.
When I disable tcp_timestamps on the dev board everything works.
The problem is reproducible every single time.
The only difference is the "Options" block of the SYN packets.
If timestamps are not really to blame, then it probably window scale
parameters. That's what I see on a usual dropped packet:
Options: (20 bytes)
Maximum segment size: 1460 bytes
SACK permitted
Timestamps: TSval 4294893842, TSecr 0
NOP
Window scale: 5 (multiply by 32)
next prev parent reply other threads:[~2011-01-07 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 6:55 Bad TCP timestamps on non-PC platforms Alex Dubov
2011-01-06 8:09 ` Eric Dumazet
2011-01-07 1:55 ` Alex Dubov [this message]
2011-01-07 2:11 ` Eric Dumazet
2011-01-07 6:39 ` Alex Dubov
2011-01-06 16:44 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2011-01-10 3:41 Alex Dubov
2011-01-10 3:57 ` Stephen Hemminger
2011-01-10 6:33 ` Alex Dubov
2011-01-10 7:07 ` Eric Dumazet
2011-01-10 7:19 ` David Miller
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=117536.54377.qm@web37607.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.