|
1
|
|
|
2
|
# pfSense apinger configuration file. Automatically Generated!
|
|
3
|
|
|
4
|
## User and group the pinger should run as
|
|
5
|
user "root"
|
|
6
|
group "wheel"
|
|
7
|
|
|
8
|
## Mailer to use (default: "/usr/lib/sendmail -t")
|
|
9
|
#mailer "/var/qmail/bin/qmail-inject"
|
|
10
|
|
|
11
|
## Location of the pid-file (default: "/var/run/apinger.pid")
|
|
12
|
pid_file "/var/run/apinger.pid"
|
|
13
|
|
|
14
|
## Format of timestamp (%s macro) (default: "%b %d %H:%M:%S")
|
|
15
|
#timestamp_format "%Y%m%d%H%M%S"
|
|
16
|
|
|
17
|
status {
|
|
18
|
## File where the status information whould be written to
|
|
19
|
file "/tmp/apinger.status"
|
|
20
|
## Interval between file updates
|
|
21
|
## when 0 or not set, file is written only when SIGUSR1 is received
|
|
22
|
interval 5s
|
|
23
|
}
|
|
24
|
|
|
25
|
########################################
|
|
26
|
# RRDTool status gathering configuration
|
|
27
|
# Interval between RRD updates
|
|
28
|
rrd interval 60s;
|
|
29
|
|
|
30
|
## These parameters can be overriden in a specific alarm configuration
|
|
31
|
alarm default {
|
|
32
|
command on "/usr/local/sbin/pfSctl -c 'filter reload'"
|
|
33
|
command off "/usr/local/sbin/pfSctl -c 'filter reload'"
|
|
34
|
combine 10s
|
|
35
|
}
|
|
36
|
|
|
37
|
## "Down" alarm definition.
|
|
38
|
## This alarm will be fired when target doesn't respond for 30 seconds.
|
|
39
|
alarm down "down" {
|
|
40
|
time 10s
|
|
41
|
}
|
|
42
|
|
|
43
|
## "Delay" alarm definition.
|
|
44
|
## This alarm will be fired when responses are delayed more than 200ms
|
|
45
|
## it will be canceled, when the delay drops below 100ms
|
|
46
|
alarm delay "delay" {
|
|
47
|
delay_low 200ms
|
|
48
|
delay_high 500ms
|
|
49
|
}
|
|
50
|
|
|
51
|
## "Loss" alarm definition.
|
|
52
|
## This alarm will be fired when packet loss goes over 20%
|
|
53
|
## it will be canceled, when the loss drops below 10%
|
|
54
|
alarm loss "loss" {
|
|
55
|
percent_low 10
|
|
56
|
percent_high 20
|
|
57
|
}
|
|
58
|
|
|
59
|
target default {
|
|
60
|
## How often the probe should be sent
|
|
61
|
interval 1s
|
|
62
|
|
|
63
|
## How many replies should be used to compute average delay
|
|
64
|
## for controlling "delay" alarms
|
|
65
|
avg_delay_samples 10
|
|
66
|
|
|
67
|
## How many probes should be used to compute average loss
|
|
68
|
avg_loss_samples 50
|
|
69
|
|
|
70
|
## The delay (in samples) after which loss is computed
|
|
71
|
## without this delays larger than interval would be treated as loss
|
|
72
|
avg_loss_delay_samples 20
|
|
73
|
|
|
74
|
## Names of the alarms that may be generated for the target
|
|
75
|
alarms "down","delay","loss"
|
|
76
|
|
|
77
|
## Location of the RRD
|
|
78
|
#rrd file "/var/db/rrd/apinger-%t.rrd"
|
|
79
|
}
|
|
80
|
target "83.85.124.1" {
|
|
81
|
description "GW_OPT1"
|
|
82
|
srcip "83.85.124.128"
|
|
83
|
alarms override "loss","delay","down";
|
|
84
|
rrd file "/var/db/rrd/GW_OPT1-quality.rrd"
|
|
85
|
}
|
|
86
|
|
|
87
|
target "192.168.0.1" {
|
|
88
|
description "GW_WAN"
|
|
89
|
srcip "192.168.0.100"
|
|
90
|
alarms override "loss","delay","down";
|
|
91
|
rrd file "/var/db/rrd/GW_WAN-quality.rrd"
|
|
92
|
}
|
|
93
|
|
