Project

General

Profile

Actions

Bug #14818

open

StatusTraffic Graph In/Out traffic misplaced in Graph but correct in text table

Added by Ivaylo Velikov 7 months ago. Updated 6 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Traffic Graphs
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
23.05.1
Affected Architecture:

Description

StatusTraffic Graph In/Out traffic misplaced in Graph but correct in text table
See attached picture


Files

Capture.PNG (29.2 KB) Capture.PNG Ivaylo Velikov, 09/29/2023 12:14 PM
bandwidth out.png (58.1 KB) bandwidth out.png bandwidth out Chris W, 10/21/2023 10:05 PM
bandwidth in.png (70.8 KB) bandwidth in.png bandwidth in Chris W, 10/21/2023 10:05 PM
Actions #1

Updated by Jim Pingle 7 months ago

Can you show more of the screenshot there to see all of your current settings when that behavior is observed?

Also is that interface a regular interface, or special in some way (VLAN, PPP, VPN, etc)?

Actions #2

Updated by Ivaylo Velikov 7 months ago

It is a super simple configuration.
One public WAN, one local LAN, only one local client IP

Just look on the picture. Graph that is IN should be OUT and OUT should be IN
Only for graph
Table is correct

Actions #3

Updated by Jim Pingle 7 months ago

Yes but the settings on that traffic graph page can be configured in numerous different ways and how you have that page set can affect the output you observe. We need to know exactly what values are in the "Graph Settings" above the graph and table when you see that output.

Actions #4

Updated by Chris W 6 months ago

It looks like this happens when the Sort By dropdown is set to Bandwidth Out. Using pfSense as an iperf server and a Manjaro client behind it, the Bandwidth In column is roughly correct by default and corresponds with the blue shade for In. But when Bandwidth Out is set, the graph is fine, but the table is what's swapped. Bandwidth Out column now shows the high value which doesn't make sense since the client is still sending traffic in to the interface, and it's a one way iperf stream.

Not sure if that's the setting OP changed but it looks like everything else works as expected. This is on 23.05.1.

Actions

Also available in: Atom PDF