On 01/12/2012 02:45 PM, Kenneth Gober wrote: > I'd argue that you should drop all the "constituent fragments" as soon > as you receive them. > > Since there's no legitimate reason of overlapping fragments, get rid of > them asap. And if there were more fragments (for the same packet) > coming, they will be dropped as a result of the reassembly timeout. > > They will be dropped if the remaining fragments can't be assembled > into a complete packet. But when overlapping fragments are combined > with the possibility of fragment duplication, I'd argue that you have to > store just enough state to be able to either immediately drop newly > arriving fragments or tag them as "not to be reassembled".
?? If you detect duplicate/overlapping fragments, you drop all the fragments that you have for that packet. If there were more fragment coming, they will be kept in the fragment reassembly queue until a reassembly timeout. Thanks, -- Fernando Gont e-mail: [email protected] || [email protected] PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
