Traffic graphs - am I reading this wrong in/out values.

[johnpoz]

@mcury thanks - going to call in @stephenw10 maybe we are both just coffee deficient.. Going to take a look see in redmine if anything has been reported like this. I do recall there being some weirdness with the traffic graph and either not showing the IPs at all or something being off..

I do recall there even being a patch put out to correct....

But yeah in no scenario in my current traffic flow where lan device is sending 19Mbps to the internet should the Wan graph show "in" to the wan at that 19Mbps.. No matter if its the source IP my wan.. Or the destination IP that 76.16 address.

[darcey]

This post is deleted!

[johnpoz]

@johnpoz ok here is another look at it.. Same traffic flow, only the bandwidth has changed a bit..

Looking at the graphs and filtering by either local and or remote - so don't have double lines to look at..

Lines I have tagged with A are wrong, while lines tagged with B are correct.

When I show only local IPs.. Which my wan IP would be included in. Or just remote IPs.. Somewhere the in/out seems reversed.

Line A is wrong, While lines marked B are correct.

In all cases the graphs show correct for in and out bandwidth.. Its only the IP table showing wrong.. But only for when you pick local IPs on the lan, and remote IPs on the wan.

[jrey]

This post is deleted!

[dennypage]

@jrey said in Traffic graphs - am I reading this wrong in/out values.:

usr/local/pfSense/include/www/bandwidth_by_ip.inc

Those changes appear to already be in 23.09.1.

[stephenw10]

Yup that patch is in but only affects output when using rate not iftop. I think all the data above is from iftop?

It could be that the in/out headers don't make much sense for iftop. I don't think anything has changed there since 23.09 though.

[jrey]

@dennypage

Indeed

[jrey]

This post is deleted!

[stephenw10]

What are you testing that on? I only see that patch as revertable in 23.09.1.

[jrey]

This post is deleted!

[stephenw10]

Hmm, I can't replicate that. On a 23.09.1 system creating that patch in the system patches package shows only 'Revert' as an available action. Which is what I'd expect.

[jrey]

This post is deleted!

[stephenw10]

So you see the same as me but you think the webgui should just show the patch as invalid rather than revertable?

[jrey]

This post is deleted!

[johnpoz]

@stephenw10 said in Traffic graphs - am I reading this wrong in/out values.:

up that patch is in but only affects output when using rate not iftop

So still seeing if using RATE vs iftop.. Is there some patch that needs to be applied even when on 23.09.1 ?

I would of thought the patch would of been included?

I thought the patch from before was to show the IPs, I don't recall it having anything to do with if the traffic was in or out of an interface.. In the above same thing my 9.10 box is sending like 4Mbps to the internet.. So to the lan interface that top line is correct, but the 2nd line is showing 4Mbps out of the lan..

I send quite of bit of data to the internet most of the time.. My friends and family are almost always watching something off my plex box. Is there a patch I can apply to show the bandwidth in/out correctly?

[stephenw10]

@jrey said in Traffic graphs - am I reading this wrong in/out values.:

This likely need a new thread if we going to continue discussing the patch mechanism rather than the traffic values ;-)

Yes I agree. Open a feature request for it if you want. However that is the expected behaviour it's not a bug.

[stephenw10]

@johnpoz said in Traffic graphs - am I reading this wrong in/out values.:

Is there some patch that needs to be applied even when on 23.09.1 ?

No all the patches are in 23.09.1. Yes, it was to show the expected IPs and didn't change the in/out data.

It could be those column headings are just wrong and exist from some much earlier version. To/From might be better there.

[jrey]

@johnpoz

Apologies for the thread diversion re:patching

I'm curious about the screen captures you are posting.. when I am testing this I see something more like (likely just optics) because your other devices aren't doing enough traffic to show on the auto scale in comparison)

where there is basically traffic on both sides of the base line... and the traffic on LAN and WAN graphs basically matches
top to bottom, bottom to top between the graphs (there is more traffic on the LAN side being displayed because of other traffic between devices that does not go to WAN.

Again your display might just be because your graphs are only showing the peak of the one device and the auto scale is not making the other traffic visible.. Let me set up a large stream test but as near as I can tell the orange on the top (LAN) matches the blue on the bottom (WAN) and the blue on the top (LAN) matches the orange on the bottom (WAN). With the slight differences in the wave forms being attributed to either traffic being local to the LAN staying on the LAN, or WAN traffic coming in an not getting to the LAN (blocked)

[johnpoz]

@jrey your looking at a different graph. I am looking under traffic under status, what you posted just look like the traffic widget..

The graphs are correct - its the IP in/out for specific interfaces under status / traffic that seems to be off.

[jrey]

@johnpoz

no sir, not the widget. I am on exactly the same page as you, with the exact same settings you are showing in your captures. where you have a WAN and a LAN. I'm also using iftop same as you everything same as you are showing. I basically matching your setting on the screens you are showing and looking at the same type of results.
My first image was basically running on two browser and screen is captured side by each, not too far apart (actually one over the other) . so I could visualize the wave forms IPs at the same time. Sorry that made it look like the widget. (it's not)

This is where I am

the IP rates (for a given IP) look the same at any given point in visually looking, even though the list moves often. The only slight differences I'm seeing in those value would likely be just other traffic that is not going between the interfaces.

I'm just setting up my test box so I can do a more controlled and isolated test, that wouldn't be impacted by so much other lan/lan only or wan/block type traffic where a lot of devices are in use. (ie I want to remove all the normal background noise and network overhead and just look at one device.