Bug #5744: dpinger alert interval stuck at zero - pfSense - pfSense bugtracker

Actions

#1

Updated by Michael Kellogg over 8 years ago

broke with change 1.1-1.2 on 12-29-15

Dec 29 19:33:57 dpinger send_interval 1000ms loss_interval 10000ms time_period 25000ms report_interval 0ms alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 192.168.254.1 identifier "DSL_DHCP "
Dec 29 19:33:57 dpinger send_interval 1000ms loss_interval 10000ms time_period 25000ms report_interval 0ms alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 209.105.187.107 identifier "CABLEMODEM_DHCP "
Dec 29 19:33:47 kernel dpinger: 1.1 -> 1.2 [pfSense]
Dec 29 12:56:26 dpinger DSL_DHCP 8.8.4.4: Clear latency 52033us stddev 70760us loss 0%
Dec 29 12:55:23 dpinger DSL_DHCP 8.8.4.4: Alarm latency 0us stddev 0us loss 100%
Dec 29 12:55:12 dpinger send_interval 1000ms loss_interval 10000ms time_period 25000ms report_interval 1000ms alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 192.168.254.1 identifier "DSL_DHCP "
Dec 29 12:55:12 dpinger send_interval 1000ms loss_interval 10000ms time_period 25000ms report_interval 1000ms alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 209.105.187.107 identifier "CABLEMODEM_DHCP "
Dec 29 12:55:03 dpinger send_interval 1000ms loss_interval 10000ms time_period 25000ms report_interval 1000ms alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.4.4 bind_addr 192.168.254.1 identifier "DSL_DHCP "
Dec 29 12:55:03 dpinger send_interval 1000ms loss_interval 10000ms time_period 25000ms report_interval 1000ms alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 209.105.187.107 identifier "CABLEMODEM_DHCP "

Actions

Copy link

#2

Updated by Phillip Davis over 8 years ago

The alert_interval there is 1000ms
report_interval is 0ms
I just changed Alert Interval to 2000ms on my system and it changed OK

Actions

Copy link

#3

Updated by Chris Buechler over 8 years ago

Category set to Gateway Monitoring

The alert_interval in that example is 1000ms, not 0. It changes fine for me. At the default 1000, it's correctly running with '-A 1000' and shows:

Jan  6 17:27:31 bootstrap-test2 dpinger: send_interval 250ms  loss_interval 1250ms  time_period 30000ms  report_interval 0ms  alert_interval 1000ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 172.27.44.1  bind_addr 172.27.44.110  identifier "WAN_DHCP "

After changing it to 1234, it's correctly running with '-A 1234' and shows:

Jan  7 22:15:59 bootstrap-test2 dpinger: send_interval 250ms  loss_interval 1250ms  time_period 30000ms  report_interval 0ms  alert_interval 1234ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 172.27.44.1  bind_addr 172.27.44.110  identifier "WAN_DHCP "

Not seeing an issue there. What exactly are you changing?

Actions

Copy link

#4