Bounty $200: Monitor bandwidth use on IP adresses. NOW $250
-
any config mean any config at all. setting any parameters in the package configuration. for example if i choose to save output file and to recover data from it after reboot the service is failed to start…
-
any config mean any config at all. setting any parameters in the package configuration. for example if i choose to save output file and to recover data from it after reboot the service is failed to start…
Yes, on the latest version it should be fine. Deinstall and reinstall.
-
also how to take a look at the config file? bandwidth is counted only 2kb of traffic on my opt1 interface.
-
Try enabling promiscuous mode.
Config file is in /usr/local/bandwidthd/etc/bandwidthd.conf
-
ill try. also there is an error on the "status_services.php?mode=startservice&service=bandwidthd" page. it states "bandwidthd has been started." on top, bat as i can see below it isnt started.
update: reinstalled and the problem with cdf option is still remain.
-
ill try. also there is an error on the "status_services.php?mode=startservice&service=bandwidthd" page. it states "bandwidthd has been started." on top, bat as i can see below it isnt started.
Okay, try launching it by hand and see what it says.
-
how to run it by hands? sorry im a windows man :)
-
how to run it by hands? sorry im a windows man :)
/usr/local/bandwidthd/bandwidthd /usr/local/bandwidth/etc/bandwidthd.conf
-
its a progress with me :) syntax error in line 47 it says, and the line 47 was "output_cdf on", changed it to "output_cdf true" and it works now. the service is started with otput option turned on.
-
its a progress with me :) syntax error in line 47 it says, and the line 47 was "output_cdf on", changed it to "output_cdf true" and it works now. the service is started with otput option turned on.
Fixed. Deinstall and reinstall.
-
ok.
but still there is no result on local ip's. it didnt counted any traffic on my local ips 192.168.2.0/0, but succefully counted my wan interface.
-
ok.
but still there is no result on local ip's. it didnt counted any traffic on my local ips 192.168.2.0/0, but succefully counted my wan interface.
Okay. I will look into it. But its now bedtime.
-
good night :)
-
I had problems with the package until I realized that I had opt interfaces that had not been fully defined. As soon as I removed them reporting started.
-
I had problems with the package until I realized that I had opt interfaces that had not been fully defined. As soon as I removed them reporting started.
What do you mean by this? Optional interfaces that exist but not enabled?
-
Hi Scott
Bandwidthd doesn't grap anything on my pfsense box (snapshot-02-02-2007)
Bandwitdthd Service seems to be running with no errors in system log
any ideas?
-
Found our first BandwidthD bug.
http://sourceforge.net/tracker/index.php?func=detail&aid=1652752&group_id=89685&atid=591011
Also, a known bug about listening on multiple interfaces:
http://sourceforge.net/tracker/index.php?func=detail&aid=1636862&group_id=89685&atid=591011
So… The question is, since we can only listen on one currently... Do we want to just monitor LAN?
-
I had problems with the package until I realized that I had opt interfaces that had not been fully defined. As soon as I removed them reporting started.
What do you mean by this? Optional interfaces that exist but not enabled?
Originally added them on first install. But did not enter any ip information at that time and they weren't connected to the network. So because they were defined under interfaces and had no ip info bandwidthd added them to the conf file but the lack of ip data kept if from starting logging until I removed them from the web configurator (would also have worked by manually removing from the conf file).
-
I had problems with the package until I realized that I had opt interfaces that had not been fully defined. As soon as I removed them reporting started.
What do you mean by this? Optional interfaces that exist but not enabled?
Originally added them on first install. But did not enter any ip information at that time and they weren't connected to the network. So because they were defined under interfaces and had no ip info bandwidthd added them to the conf file but the lack of ip data kept if from starting logging until I removed them from the web configurator (would also have worked by manually removing from the conf file).
Thanks for taking the time to note this. I'll get it fixed tomorrow am. Thanks again!
-
….
So... The question is, since we can only listen on one currently... Do we want to just monitor LAN?Mine is generating stats for LAN and WAN. Wasn't that issue when they had 2 but only wanted to listen on 1? They had 1 subnet defined but 2 interfaces listed in the conf file. Wouldn't workaround be to only define the interfaces you want to listen on in the .conf file or provide a selection box to generate the list of interfaces?
The DAILY subnet stats pages are not being generated. The weekly and monthly subnet stats works for both subnets.