pfSense

I was not able to reproduce it here. Is it happening all the time on interface HOME? Could you give me more details about your setup?

Yes it happens consistently. The HOME interface is one of two vlans configured on the em1 lan interface. The em1 interface itself is not configured in pfsense, only the two vlans.

-------------              -------------- VLAN_10 To home private network
|               |  EM1_VLAN10  |                |--------
WAN -----|EM0         EM1|--------------| Managed switch |
|   pfSense     |  EM1_VLAN20  |                |-------- To DMZ server
         -------------              -------------- VLAN_20

Sorry, that picture didn't come out so well. Essentially I have a two port pfSense box. One port is LAN and one port is WAN. Since I need to have a safe DMZ on a separate subnet (both IPV4 and IPV4), I don't use the LAN port directly, but instead configure two VLANS on it, one private and one public. The LAN interface is then connected to a managed switch to distribute each VLAN to a separate switch port. One is connected to my DMZ server and is visible on the Internet by public IP and the second is for the internal private home network.

Hope that helps. Only speculating, maybe whatever component you use to extract the traffic level is summing EM1 traffic with EM1_VLAN20 traffic thus counting it twice?

Oops... should have read '(both IPV4 and IPV6)'

amd64 version is affected too
https://redmine.pfsense.org/issues/3264

Well it is not something to be fixed for 2.1.1 since its an OS issue rather than pfSense collection one.

I am currently seeing this issue without VLANs. 2.1.1 64-bit

hi,
I have similar trouble but on almost all interface VLAN and not VLAN in 2.1.1 x64
Information for SNMP are false too.

Note that this only affects the SVG based graphs (on the dashboard or Status -> Traffic Graph), the RRD based ones (Status -> RRD Graph) are fine. Thus I doubt it is a collection issue.

the RRDs are accurate because they pull from pf's counters, not the OS NIC-level counters. This hopefully works in 2.2 as I suspect the OS-level issue is fixed in FreeBSD 10.x, if someone can test and report back that'd be helpful.

Issue persists on 2.2

As a temporary workaround, would it not be possible to detect VLANs and do something like disabling the graph, automatically dividing by 2, or just plastering a warning on the graph that these numbers are not accurate?

Also, what is it actually showing? Is that the actual output of the underling parent interface? If so, that's a number I've often wished pfSense could display, particularly since my parent interfaces are LAGGs and I don't have an easy way to see aggregate bandwidth through the system.

this looks to work fine. Will leave for additional feedback.

If anyone else can help test, please try the latest 2.2.3 snapshot @ snapshots.pfsense.org and report back.