Subject: Re: kernel ip_randomid() and libc randomid(3) still "broken"
To: David Laight <david@l8s.co.uk>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
List: tech-net
Date: 11/17/2003 15:01:57
>Then include the port number in the hash function.


No. We can't do that, it violates RFC-791 (and thus  RFC-1122,
per the  references to RFC-791 on fragmentation and reassembly).

If you meant "IP protocol" rather than port, that doesnt help my
scenario one iota: assume all traffic is UDP as the worst-case.


If you meant "port": "Port" is a transport-level notion. Transport
protocol headers only appear in the first fragment of a fragmented
datagram.  A moment's thought would show that if a receiver sees a
fragment other than the first, it has no idea which "port" to
associate that ip_id with, and so no way to pick the correect fragment
chain.