Project

General

Profile

Actions

Bug #12295

closed

Gateway RTT of gateways added through packages (OpenVPN and Wireguard) seem off

Added by Faan DG almost 4 years ago. Updated almost 4 years ago.

Status:
Not a Bug
Priority:
Low
Assignee:
-
Category:
Gateways
Target version:
-
Start date:
08/21/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:

Description

Hi,

When looking at RTT in widgets or when extracting information via dpinger it looks as if the latency is very low.
Just wanted to verify with you if this is intended behavior?

https://www.reddit.com/r/PFSENSE/comments/p86j73/inconsistent_rtt_data_in_widgets_monitoring_and/
(contains images)

If intended, can you clarify if this means 'added' RTT or should be displayed as nanoseconds or something else?

Actions #1

Updated by Kris Phillips almost 4 years ago

If your gateway has very low latency, either due to a double NAT or because your static IP block is a routed subnet assigned to your ISP equipment, this is normal. It's likely the upstream gateway is the ISP equipment which is why the latency is so low.

RTT - Round Trip Time for a packet in milliseconds
RTTsd - The standard deviation of RTT from an average

This is not a bug as the gateway monitoring is working fine for me, unless more information can be provided.

Actions #2

Updated by Jim Pingle almost 4 years ago

  • Status changed from New to Not a Bug

There is no difference in monitoring for gateways based on their source like that. It's almost certainly due to differences in what you're actually monitoring in both cases. It may unintentionally be monitoring itself, or something local to you, and not actually hitting a remote system.

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information.

Actions

Also available in: Atom PDF