Bug #2602
closed
BandwidthD - Reported Traffic / Usage is approximately Double real amount
0%
Description
2.0.1-RELEASE (amd64)
built on Mon Dec 12 18:43:51 EST 2011
FreeBSD 8.1-RELEASE-p6
bandwidthd 2.0.1.3
AMD PhenomIIx4 CPU with 8 Gigabytes Memory and 1 Terabyte SATA2 Hard Drive.
CARP Dual pfSense Router configuration.
4 x 1GB Ethernet Ports.
The reports generated by BandwidthD are inaccurate / incorrect.
The amount of data transferred is reported as Double (2 times) the actual amount transferred.
- Transferred a 169 MegaByte .iso file multiple times.
- Each time, BandwidthD reported a value approximately 2 times that. (350.6 MegaBytes)
- This is repeatable.
- There are several reports of this problem on the forum.pfsense.org and forum.ubnt.com websites.
- There have been NO useful replies to any of the forum posts on this issue.
- Users on the network have done independent tests and have found that the BandwidthD reported amounts
are double the amount that they have measured locally.
- I and others have noticed that double entries for IP addresses are appearing in the .CDF log files.
Each entry usually has a slightly different value. We do not know if this is supposed to happen.I have not located a report on that problem in this bugtracker.
pfSense BandwidthD Settings :
Interface : LAN
Subnet : public ip address subnet on LAN is 64.xxx.xxx.xxx/24
Skip Intervals : <blank>
Graph Cutoff : <blank>
promiscuous : No
output_cdf : Yes
recover_cdf : Yes
filter : <blank>
Draw Graphs : Yes
Meta Refresh : <blank>
--Brock
Updated by Brock Prozeniuk over 12 years ago
Yup. Problem is still there.
Is this the right bug tracker to be addressing issues with the BandwidthD package for pfSense ?
Is there access to the individual or group who prepared the BandwidthD package for pfSense 2.0.1 where I can arrange for some support in solving / addressing this issue ?
thanks
--Brock
Updated by Chris Buechler almost 12 years ago
- Status changed from New to Closed
haven't ever seen this. It's almost certainly a problem within bandwidthd itself under some specific unusual circumstances, which is outside our control.
Updated by Brock Prozeniuk over 11 years ago
This issue should remain closed.
This note is being added so that there is an answer associated with this issue to explain what the cause was. --Brock
The problem is caused because BandwidthD is being told to count the traffic more than once.
On the pfSense BandwidthD screen (pfSense : Services : BandwidthD) there is a field with the label "Subnet"
If the "Interface" field is set to "LAN" and the "Subnet" field is "Blank / empty", the BandwidthD traffic reports are "accurate".
If the "Interface" field is set to "LAN" and the "Subnet" field is set to the local subnet on the LAN (i.e. 192.168.100.0/24), then the BandwidthD traffic reports are up to two times the proper amount.