pfSense

Are you on 64 bit or 32 bit? What dpinger parameters are you using?

2.3-BETA (i386)
built on Fri Feb 26 13:07:04 CST 2016
FreeBSD 10.3-BETA2

dpinger parameters:
Weight: 1
Data Payload: 0 (default)
Latency thresholds: 200 500 (defaults)
Packet loss thresholds: 10 20 (defaults)
Probe Interval: 15000
Loss Interval: 1250 (default)
Time Period: 60000
Alert interval: 15000

Added some echos to the rrdupdate shell script to capture values it's getting from dpinger.
Here's a sample including the problem.

Column 1 = Interface

Column 2: delay (dpinger raw) (microseconds)
Column 3: stddev (dpinger raw) (microseconds)
Column 4: loss

Column 5: delay (converted to seconds) (n/1000^2)
Column 6: stddev (converted to seconds) (n/1000^2)
Column 7: loss

WAN_DHCP 2427 780 0 0.002427 0.00078 0
WAN_DHCP 2207 437 0 0.002207 0.000437 0
WAN_DHCP 2738 571 0 0.002738 0.000571 0
WAN_DHCP 9847 13836 0 0.009847 0.013836 0
WAN_DHCP 2262 788 0 0.002262 0.000788 0
WAN_DHCP 2756 577 0 0.002756 0.000577 0
WAN_DHCP 2230 586 0 0.00223 0.000586 0
WAN_DHCP 2025 220 0 0.002025 0.00022 0
WAN_DHCP 17919 3981923697 0 0.017919 3981.923697 0
WAN_DHCP 2369 490 0 0.002369 0.00049 0
WAN_DHCP 2836 234 0 0.002836 0.000234 0
WAN_DHCP 2406 665 0 0.002406 0.000665 0
WAN_DHCP 1987 270 0 0.001987 0.00027 0
WAN_DHCP 2180 728 0 0.00218 0.000728 0
WAN_DHCP 2657 392 0 0.002657 0.000392 0
WAN_DHCP 1667 165 0 0.001667 0.000165 0
WAN_DHCP 2504 689 0 0.002504 0.000689 0

It's an integer overflow on 32 bit. I'll have a fix up shortly.

The dpinger fix is pushed. It probably won't be in pfSense snapshots until Monday.

Please note that the fix will not change the data already recorded in your rrd file. If you want to edit the existing data, it will require a dump and restore of the rrd file. If you decide you want to do this, PM me and I will do my best to help. Sorry about the problem, and thanks for pointing it out.

Thanks for the quick turnaround. Don't care about the existing data. It's strictly a dev system. Maybe others do. I'll just reset RRD once the updated dpinger is installed.
Again, Thanks.

I've not been on the same network and gateway that this was originally seen on and won't be again till later in the week. So I can say 100% but it does appear to be fixed.
Thanks.