Traffic Graphc statistics are backwards for LAN interface
-
If you really what to twist your brain. Figure this one out.
The graph has a "better" longer-term view of the total data in/out on the pfSense interface. The table of clients takes a shorter-term snapshot on each update. Thus the table is just a "rough idea" of what is going on. For clients that are doing something consistent across time it gives a good snapshot of the activity, for clients that do bursty things then it is hit and miss.
Also, anyone making further comments about In/Out please always say if you are talking about the graph or the table - it is very difficult to sort out who is commenting about what.
-
If you really what to twist your brain. Figure this one out.
The graph has a "better" longer-term view of the total data in/out on the pfSense interface. The table of clients takes a shorter-term snapshot on each update. Thus the table is just a "rough idea" of what is going on. For clients that are doing something consistent across time it gives a good snapshot of the activity, for clients that do bursty things then it is hit and miss.
There was only the one client doing anything of significance; copying a 600 MB video to remote client on a 1.5 mbps DSL connection. All the traffic (for practical purpose of this) was to/from that one client.
If I'm correct about what is causing the discrepancy in the numbers (graph LAN In/Out the same and seemingly Out being wildly incorrect, but client table showing correct In/Out values). Something that CMB mentioned earlier is a clue.
@cmb:
The RRD data comes from pf's counters rather than netstat (where Status>Traffic Graph pulls), . . .
-
@phil-davis said in Traffic Graphc statistics are backwards for LAN interface:
It has always been like that. The graph is with respect to the pfSense interface - so download traffic goes OUT LAN.
The table of clients is with respect to the client - download traffic is IN to the client.
It needs to be this way, because the clients in the table can also be systems out on the public internet (selecting to show "Remote" or "All"). And in that case it looks sensible that the table shows bandwidth out of some public IP and bandwidth in to some LAN client.Just quoting this comment because, despite being a nearly 10 year old thread, this is the comment that made it click in my head. I had no idea why the graphs worked this way until Phil explained it. Thank you!
