Non-linear timestamps from packet source causes problems

Description

Due to Bro's internal clock being driven forward by packet timestamps, if packets are received chronologically out of order, Bro's output can get confusing due to timers expiring at unexpected times.

If a packet is ever received that has a timestamp before the previous packet, we should at least do a weird. Something like non_chronological_packet_time?

Environment

None

Assignee

Unassigned

Reporter

Seth Hall

Labels

None

External issue ID

None

Components

Affects versions

Priority

Normal
Configure