From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: DF, IP ID always 0 and the reassembly protections
Date: Tue, 20 Jun 2006 17:35:50 -0700 [thread overview]
Message-ID: <44989466.5070308@hp.com> (raw)
In-Reply-To: <20060620.171912.70221261.davem@davemloft.net>
David Miller wrote:
> From: Rick Jones <rick.jones2@hp.com>
> Date: Tue, 20 Jun 2006 16:44:55 -0700
>
>
>>Doesn't that mechanism rely on watching the IP ID's between the pair of
>>IPs? For both fragmented and non-fragmented datagrams? If so, does
>>always setting the IP ID to zero when DF is set affect that mechanism?
>
>
> Only the IDs in packets with DF clear matter.
I thought the ID's even in non-fragmented datagrams gave an idea of how
many IP datagrams had been sent along, and so an idea of how "unlikely"
it was that a datagram with holes could be reassembled?
rick jones
next prev parent reply other threads:[~2006-06-21 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 23:44 DF, IP ID always 0 and the reassembly protections Rick Jones
2006-06-21 0:19 ` David Miller
2006-06-21 0:35 ` Rick Jones [this message]
2006-06-21 0:38 ` akepner
2006-06-21 0:43 ` 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=44989466.5070308@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--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).