netdev - Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want to know why its set to zero)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <OF5F2AB2D4.EAFD2016-ON88257488.0067DC0C-88257488.0068AE15@us.ibm.com>
Date:	Wed, 16 Jul 2008 12:03:25 -0700
From:	David Stevens <dlstevens@...ibm.com>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	netdev@...r.kernel.org, netdev-owner@...r.kernel.org
Subject: Re: IPV4: Enable IP_ID sequencing for all traffic (inquiring minds want to
 know why its set to zero)

IP_ID is needed for reassembly of fragments, but a fast network can
go through all the ID's available before datagrams you've already sent
have reached their time to live.

That means you can end up with two different datagrams with the same ID
and incorrectly reassemble parts of them together (which you can hope
the checksum will catch and cause a drop).

By not using IDs for non-fragmented datagrams, the time to wrap the ID
space is increased, which reduces the chance of getting into that
situation.

That really is the only protocol use of IP_IDs, so there isn't any point
in consuming them for non-fragment datagrams. It's useful sometimes
when looking at packet traces to correlate pieces on two different
networks, which I'm guessing is why you want it, but I don't think it's
a good idea to do it all the time.

                                                +-DLS

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html