Bounty $200: Monitor bandwidth use on IP adresses. NOW $250
-
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.
-
Hello I have jsut set this up in a test enviroment with vmware, i notice that the bandwidthd page isnt being fully created
as you can see from the output bellow it ends 3/4 of the way through the last line and the page stops there, thus meaning that none of the graphs are drawn because they apear under that last line.
Is anyone else having this issue ?
Top 20 IPs by Traffic - Daily
Ip and Name Total Total Sent Total Received FTP HTTP P2P TCP UDP ICMP
Total 161.7M 6.5M 155.3M 0 159.2M 2.2K 160.9M 773.2K 55.7K
10.0.0.104 148.8M 3.5M 145.2M 0 147.8M 2.2K 148.7M 56.9K 4.4K
10.0.0.126 11.6M 2.1M 9.6M 0 11.1M 0 11.5M 83.6K 23.5K
10.0.0.50 437.5K 188.6K 248.9K 0 0 0 357.6K 75.0K 4.4K
10.0.0.111 1.9K 1.9K 0 0 0 0 0 1.6K 0
10.0.0.51 1.6K 1.6K 0 0 0 0 0 1.1K 0
10.0.0.151 1.4K 1.4K 0 0 0 -
Seems to be the issue that i have.
In the generated .conf i get
subnet 192.168.0.0/24
dev "rl0" (Lan)
dev "sis0" (wan from isp dhcp)When started it tried to grap from sis0 using 192.168.0.0/24
So i have to stop service and delete the sis0 line in .conf
When service is started again, stats are generated in daily and weekly tapSo a selection box might be the solution for me.
….
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.
-
as i understand it for me - multiple instances of bandwidthd can listen to multiple interfaces. and also, there's would be better to have a selection in GUI of interface to listen to. anybody can explain me how to get the stats for a specific day or period?
-
as i understand it for me - multiple instances of bandwidthd can listen to multiple interfaces. and also, there's would be better to have a selection in GUI of interface to listen to. anybody can explain me how to get the stats for a specific day or period?
I can do this, but its quite ugly. It would be better to wait until the bug is fixed so one binary can monitor everything.
Besides, I still haven't received much more than 125$ for this bounty. At some point it was starting to look like it was going to be 400$.
I will back off and let everyone figure out what they need to do and will also wait for some of the bugs to get fixed in BandwidthD.
-
as i understand it for me - multiple instances of bandwidthd can listen to multiple interfaces. and also, there's would be better to have a selection in GUI of interface to listen to. anybody can explain me how to get the stats for a specific day or period?
I can do this, but its quite ugly. It would be better to wait until the bug is fixed so one binary can monitor everything.
Besides, I still haven't received much more than 125$ for this bounty. At some point it was starting to look like it was going to be 400$.
I will back off and let everyone figure out what they need to do and will also wait for some of the bugs to get fixed in BandwidthD.
I will pay 200$ when I have something working, as I wrote when I started this bounty, I have to get info from every VLAN also.
But I will pay 100$ now if u just get it to work with one interface ( WAN)I don
t get any data when i have 3 VLANs activated.Is should work for me to just the the traffic who is going true WAN.
-
I can do this, but its quite ugly. It would be better to wait until the bug is fixed so one binary can monitor everything.
how long we shall wait for the bandwidthd to update? it isnt changed for two years and i couldnt found enyone on the internet who is interested in continue to develop on this package. but the package itself is great, you know.
-
as i understand it for me - multiple instances of bandwidthd can listen to multiple interfaces. and also, there's would be better to have a selection in GUI of interface to listen to. anybody can explain me how to get the stats for a specific day or period?
I can do this, but its quite ugly. It would be better to wait until the bug is fixed so one binary can monitor everything.
Besides, I still haven't received much more than 125$ for this bounty. At some point it was starting to look like it was going to be 400$.
I will back off and let everyone figure out what they need to do and will also wait for some of the bugs to get fixed in BandwidthD.
I will pay 200$ when I have something working, as I wrote when I started this bounty, I have to get info from every VLAN also.
But I will pay 100$ now if u just get it to work with one interface ( WAN)I don
t get any data when i have 3 VLANs activated.Is should work for me to just the the traffic who is going true WAN.
I will change the code in a moment to only monitor the WAN interface.
-
I can do this, but its quite ugly. It would be better to wait until the bug is fixed so one binary can monitor everything.
how long we shall wait for the bandwidthd to update? it isnt changed for two years and i couldnt found enyone on the internet who is interested in continue to develop on this package. but the package itself is great, you know.
There was very little tickets in the system so either:
A) They write incredible code or
B) It's being actively maintained.I think B is the answer here.