From: Alex Dubov <oakad@yahoo.com>
To: netdev@vger.kernel.org
Subject: Bad TCP timestamps on non-PC platforms
Date: Wed, 5 Jan 2011 22:55:43 -0800 (PST) [thread overview]
Message-ID: <219643.83181.qm@web37604.mail.mud.yahoo.com> (raw)
Greetings.
I'm dealing with 2.6.37-rc7 kernel on MPC8548 platform.
It so appears, that recent kernels have sysctl_tcp_timestamps set to "1"
by default.
On embedded platforms, where real time clock is initialized lately or
absent outright, this causes TSval field of outgoing TCP packets to be
set to some garbage value, in my case in the vicinity of 0xffffffff. As a
result, other Linux machines silently drop such packets, preventing normal
completion of network boot or any other TCP dependent operation.
Therefore, I feel, two changes are necessary (I can send in a patch):
1. Make sysctl_tcp_timestamps value config-time selectable (it must be
disabled by default on machines without RTC).
2. When re-enabling tcp_timestamps through sysctl, reset the timestamp
counter to the current system clock value.
And an optional, tricky one:
3. Postpone TCP timestamp counter initialization until RTC is actually
available (if RTC is connected to i2c bus, TCP is initialized well ahead
of it).
next reply other threads:[~2011-01-06 7:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 6:55 Alex Dubov [this message]
2011-01-06 8:09 ` Bad TCP timestamps on non-PC platforms Eric Dumazet
2011-01-07 1:55 ` Alex Dubov
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=219643.83181.qm@web37604.mail.mud.yahoo.com \
--to=oakad@yahoo.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.