mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
9d489cde20
Now, in addition to setting thresholds for bytes and packet, one can set a threshold for connection duration. Note that the threshold event is only raised once the next packet in the connection is seen. This also fixes a small pre-existing bug, in which a bunch of warnings were raised if someone just used the lower-level functions without going through the higher-level scripting API.
38 lines
1.4 KiB
Text
38 lines
1.4 KiB
Text
# @TEST-EXEC: zeek -r $TRACES/irc-dcc-send.trace %INPUT
|
|
# @TEST-EXEC: btest-diff .stdout
|
|
|
|
event connection_established(c: connection)
|
|
{
|
|
print fmt("Threshold set for %s", cat(c$id));
|
|
ConnThreshold::set_bytes_threshold(c, 1, T);
|
|
ConnThreshold::set_bytes_threshold(c, 2500, T);
|
|
ConnThreshold::set_bytes_threshold(c, 2700, T);
|
|
ConnThreshold::set_bytes_threshold(c, 3000, T);
|
|
ConnThreshold::delete_bytes_threshold(c, 3000, T);
|
|
ConnThreshold::set_bytes_threshold(c, 2000, F);
|
|
ConnThreshold::set_duration_threshold(c, 0.1secs);
|
|
ConnThreshold::set_duration_threshold(c, 0.2secs);
|
|
|
|
ConnThreshold::set_packets_threshold(c, 50, F);
|
|
ConnThreshold::set_packets_threshold(c, 51, F);
|
|
ConnThreshold::set_packets_threshold(c, 52, F);
|
|
ConnThreshold::delete_packets_threshold(c, 51, F);
|
|
ConnThreshold::set_packets_threshold(c, 63, T);
|
|
ConnThreshold::delete_packets_threshold(c, 63, T);
|
|
ConnThreshold::delete_duration_threshold(c, 0.1secs);
|
|
}
|
|
|
|
event ConnThreshold::bytes_threshold_crossed(c: connection, threshold: count, is_orig: bool)
|
|
{
|
|
print "triggered bytes", c$id, threshold, is_orig;
|
|
}
|
|
|
|
event ConnThreshold::packets_threshold_crossed(c: connection, threshold: count, is_orig: bool)
|
|
{
|
|
print "triggered packets", c$id, threshold, is_orig;
|
|
}
|
|
|
|
event ConnThreshold::duration_threshold_crossed(c: connection, threshold: interval, is_orig: bool)
|
|
{
|
|
print "triggered duration", c$id, threshold, is_orig;
|
|
}
|