Bug #5737
closed
Traffic Graph Table and Graph Inverted Values
Added by Lawrence Dudley over 9 years ago.
Updated about 9 years ago.
Description
The traffic graph and the table seem to use opposite values for In/Out. Bit odd.
I'm using a tiered outbound gateway, not sure if that has any impact on this.
Files
The In-Out on the graph is with-respect-to the pfSense interface, e.g. on LAN, In is traffic coming into pfSense from LAN devices (i.e. uploading to the internet) and Out is traffic sent out from pfSense to LAN devices (i.e. downloading from the internet).
The In-Out on the table is with-respect-to the particular client device, e.g. for a device on LAN, iN is traffic arriving at that device from pfSense (i.e. downloading from the internet) and Out is traffic sent by that device to pfSense (i.e. uploading to the internet).
Fair enough! I guess that sort of, kind of makes sense :)
I can't seem to close this issue - if you can then feel free to do so!
- Status changed from New to Not a Bug
I was just getting ready to report this as a bug myself.
I guess my question is: how is this not considered a bug?
I get the explanation, but if we're going to display information side-by-side, we really should be using the same methodology on both. If this isn't a bug, where should we lobby to get this changed?
We've come a long way, let's not impede adoption rates for non-techie users who find stuff like this and immediately consider it a bug. Engineers (like myself) understand how great pfsense is and understand the reasoning for why it's currently being displayed this way. but..... put yourself into the shoes of a desktop support guy who's been installing Sonicwall's for the past 3 years and wants to try out pfsense for the first time -- he may see an issue like this as a bug and assume the product is buggy and not give us another chance.
I'm a looong time pfsense user, have no reason to ever use anything else -- just wanted to add my .02
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
