fix: tcpassembly does not use correct timestamps #277
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tcpassembly only read the bytes of the reassembled stream and ignored other reassembly information, like seen timestamp. Therefore When assembling a HEP packet it had to use the current time. Because of parallel handling of packet capture, reassembly, and extraction this timestamp could be totally wrong.
The changed code processes the reassembly information directly and uses the timestamp of the part with the begin of the SIP message.
refs: #223