Project

General

Profile

Actions

Bug #4081

closed

Apinger reporting incorrect latency

Added by Denny Page almost 7 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Gateway Monitoring
Target version:
Start date:
12/07/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

If a gateway has an explicit monitor address, apinger will stop reporting latency to the monitor address and switch to reporting latency for the gateway address. Very obvious if the gateway address is local (~ 1ms) and the monitor address is across a remote link (~10ms). Once the switch occurs, apinger appears to remain stuck reporting the lower value.

It's notable that (hours) after the event, the pings are going to the correct (monitor) address even though the latency being reported corresponds to the local gateway address.

It's unclear what the trigger for this is. I haven't caught the event live yet. I have a tcpdump running in hopes of catching the event live.


Files

pfsense 4081.jpg (68.6 KB) pfsense 4081.jpg RTT drop Stuart Wyatt, 03/02/2015 03:34 PM
pfsense 4081 fix.jpg (69 KB) pfsense 4081 fix.jpg RTT "fix" with cable modem/nic reset Stuart Wyatt, 03/02/2015 03:34 PM
Actions

Also available in: Atom PDF