This patch made bro much more stable and it didn't die in 5 days, BUT it
now spews thousand of "1061597578.544274 WeirdActivity ** non_IPv4_packet"
messages, all the time.Any fixes for that?
As usual, when reporting a problem like this it really helps if you can
provide a trace snippet and a policy script invocation that reproduces it.
Otherwise it can be very hard to track down.
Note, I'll be releasing a new version of Bro with some major enhancements
(and a number of bug fixes) in a couple of days.
Vern