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: <20080716.133048.201600858.davem@davemloft.net>
Date:	Wed, 16 Jul 2008 13:30:48 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	cl@...ux-foundation.org
Cc:	dlstevens@...ibm.com, 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)

From: Christoph Lameter <cl@...ux-foundation.org>
Date: Wed, 16 Jul 2008 14:22:19 -0500

> Wasnt there a time when we did IP_ID on every packet? Any changelogs from that time?

The current behavior existed way before GIT and BK so this might be
hard to come by.

A quick check shows that 2.2.x does an unconditional iph->id = ip_id_count++
so you can work forwards from there :-)
--
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