From: Andi Kleen <andi@firstfloor.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want to know why its set to zero)
Date: Thu, 17 Jul 2008 18:12:53 +0200 [thread overview]
Message-ID: <87r69ssd4q.fsf@basil.nowhere.org> (raw)
In-Reply-To: <487E0C15.1070001@linux-foundation.org> (Christoph Lameter's message of "Wed, 16 Jul 2008 09:56:21 -0500")
Christoph Lameter <cl@linux-foundation.org> writes:
> There is some security reason why we set IP_ID == 0 right? Could someone point me at the discussions that lead to having IP_ID be zero? Have not been involved in network that much so forgive my ignorance.... and I can only find some hints about why this was done here and there using google.
AFAIK it was just for efficiency. The way Linux generates ipids
currently is somewhat expensive, because it aims to generate a per ip
ipid counter, so it was turned off when not needed. I used to patch
that out because it always seemed like overkill to me.
-Andi
prev parent reply other threads:[~2008-07-17 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 14:56 IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want to know why its set to zero) Christoph Lameter
2008-07-16 19:03 ` David Stevens
2008-07-16 19:06 ` David Stevens
2008-07-16 19:22 ` Christoph Lameter
2008-07-16 20:30 ` David Miller
2008-07-16 20:39 ` Rick Jones
2008-07-16 21:01 ` David Miller
2008-07-16 21:16 ` IPV4: Enable IP_ID sequencing for all traffic (inquiring mindswant " Templin, Fred L
2008-07-16 22:37 ` Christoph Lameter
2008-07-16 20:27 ` IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want " David Miller
2008-07-17 16:12 ` Andi Kleen [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=87r69ssd4q.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).