zeek/testing/btest/core/reassembly.zeek
Jon Siwek 7967a5b0aa General btest cleanup
- Use `-b` most everywhere, it will save time.

- Start some intel tests upon the input file being fully read instead of
  at an arbitrary time.

- Improve termination condition for some sumstats/cluster tests.

- Filter uninteresting output from some supervisor tests.

- Test for `notice_policy.log` is no longer needed.
2020-08-11 11:26:22 -07:00

26 lines
798 B
Text

# @TEST-EXEC: zeek -b -C -r $TRACES/ipv4/fragmented-1.pcap %INPUT >>output
# @TEST-EXEC: zeek -b -C -r $TRACES/ipv4/fragmented-2.pcap %INPUT >>output
# @TEST-EXEC: zeek -b -C -r $TRACES/ipv4/fragmented-3.pcap %INPUT >>output
# @TEST-EXEC: zeek -b -C -r $TRACES/ipv4/fragmented-4.pcap %INPUT >>output
# @TEST-EXEC: zeek -b -C -r $TRACES/tcp/reassembly.pcap %INPUT >>output
# @TEST-EXEC: btest-diff output
event zeek_init()
{
print "----------------------";
}
event flow_weird(name: string, src: addr, dst: addr, addl: string)
{
print "flow weird", name, src, dst;
}
event net_weird(name: string, addl: string)
{
print "net_weird", name;
}
event rexmit_inconsistency(c: connection, t1: string, t2: string, tcp_flags: string)
{
print "rexmit_inconsistency", c$id, t1, t2, tcp_flags;
}