A while back (I cannot recall exactly when) the issue of always setting
the IP datagram ID to zero when the DF bit was set was brought-up. I
suggested it might not be a good idea because there are admittedly
broken devices out there that "helpfully" and silently clear DF and the
start to fragment. The counter point was that coding around such broken
hardware was silly.
I was just writing a missive to one of my co-workers on IP
fragmentation. It got me to thinking about the stuff (I think it
went-in?) to try to protect against "Frankengrams" during IP fragment
reassembly.
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?
rick jones
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
