Ipv6 fragmentation tracking issue

Gentle people,
We discovered a bug in the IPv6 fragmentation tracking code where =
fragments we=E2=80=99re not being hashed to its parent IPv6 flow, =
causing argus to generate =E2=80=9C    f    =E2=80=9C status indications =
on some IPv6 flows (lower case =E2=80=98f=E2=80=99 is a flow record that =
represents fragments that couldn=E2=80=99t be mapped to its original =
flow).  The flow data is correct, in that we=E2=80=99re accounting for =
the fragmented traffic, but we aren=E2=80=99t doing the right thing.

We have a fix, and are testing it now.  If you are monitoring IPv6 and =
see some of these flows, send me a note, and I=E2=80=99ll try to get the =
fix to you, if you would like to test it.
Hope all is most excellent,

Carter=