Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Replying to my own mail yesterday (again) no-traffic-bug which caused no-graphing-possible (skipping current run) fixed... (My suspicion than something more was broken was probably just because I was in a hurry and didn't notice that I've configured the subnet wrong.) Will submit this to the bandwidthd patch tracker at sourceforge. David: please continue with the review/merge... http://fjortis.info/pub/debian/bandwidthd-1.2.1/upstream/ New debian package 1.2.1b-14 which includes this fix and some other changes suggested by Eduard Bloch. Eduard: could you please test this new version (and investigate why bandwidthd doesn't pick up any packets on your system, possible subnet configuration error). http://fjortis.info/pub/debian/bandwidthd-latest/ Regards, Andreas Henriksson
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Replying to my own mail yesterday (again) no-traffic-bug which caused no-graphing-possible (skipping current run) fixed... (My suspicion than something more was broken was probably just because I was in a hurry and didn't notice that I've configured the subnet wrong.) Will submit this to the bandwidthd patch tracker at sourceforge. David: please continue with the review/merge... http://fjortis.info/pub/debian/bandwidthd-1.2.1/upstream/ New debian package 1.2.1b-14 which includes this fix and some other changes suggested by Eduard Bloch. Eduard: could you please test this new version (and investigate why bandwidthd doesn't pick up any packets on your system, possible subnet configuration error). http://fjortis.info/pub/debian/bandwidthd-latest/ Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Replying to my own mail yesterday David: Please don't merge the patches I've sent you. I've looked into the skipping current run problem this morning. I haven't found the root cause but here are my conclusions so far... Affected: bandwidthd-1.2.1b-13 (debian package) bandwidthd-1.2.1b + all patches sent upstream (http://fjortis.info/pub/debian/bandwidthd-1.2.1/upstream/) bandwidthd-1.2.1b + fork patch sent upstream Not affected: (?) bandwidthd-1.2.1b (plain upstream) Minor bug: CommitData sets MayGraph=FALSE before initiating a graphing run to prevent another graphing run before the first one is finished and then calls WriteOutWebpages. MayGraph=TRUE is set when there is a (grapher) child to reap. WriteOutWebpages doesn't fork a child if there's nothing in DataStore. One solution to this would be to change WriteOutWebpages to return an error code so CommitData can reenable MayGraph if WriteOutWebpages fails to not prevent future graphing runs forever. Alternative solution: Check the datastore before changing MayGraph and calling WriteOutWebpages (this OTOH can't handle fork failures). Problem: The skipping current run problem is there because the minor bug above. The real bug is somewhere else though and I need to find out why the DataStore is empty. I can't see how any of my changes can cause this problem. I will have to look closer on the fork patch and investigate this further If the workarounds mentioned doesn't cure it for you or have anything to add in tracking down the problem please drop me a mail and I'll look at it as soon as I get my next chance to investigate. I'll post a status update later on Thanks to everyone testing the package! Thanks Adeodato for the suggestion on lists @lists.debian.org in muttrc which I've now added. Still I want to urge everyone to please CC me thanks. Regards, Andreas Henriksson
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Replying to my own mail yesterday David: Please don't merge the patches I've sent you. I've looked into the skipping current run problem this morning. I haven't found the root cause but here are my conclusions so far... Affected: bandwidthd-1.2.1b-13 (debian package) bandwidthd-1.2.1b + all patches sent upstream (http://fjortis.info/pub/debian/bandwidthd-1.2.1/upstream/) bandwidthd-1.2.1b + fork patch sent upstream Not affected: (?) bandwidthd-1.2.1b (plain upstream) Minor bug: CommitData sets MayGraph=FALSE before initiating a graphing run to prevent another graphing run before the first one is finished and then calls WriteOutWebpages. MayGraph=TRUE is set when there is a (grapher) child to reap. WriteOutWebpages doesn't fork a child if there's nothing in DataStore. One solution to this would be to change WriteOutWebpages to return an error code so CommitData can reenable MayGraph if WriteOutWebpages fails to not prevent future graphing runs forever. Alternative solution: Check the datastore before changing MayGraph and calling WriteOutWebpages (this OTOH can't handle fork failures). Problem: The skipping current run problem is there because the minor bug above. The real bug is somewhere else though and I need to find out why the DataStore is empty. I can't see how any of my changes can cause this problem. I will have to look closer on the fork patch and investigate this further If the workarounds mentioned doesn't cure it for you or have anything to add in tracking down the problem please drop me a mail and I'll look at it as soon as I get my next chance to investigate. I'll post a status update later on Thanks to everyone testing the package! Thanks Adeodato for the suggestion on lists @lists.debian.org in muttrc which I've now added. Still I want to urge everyone to please CC me thanks. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Hi Eduard! ... and David, which I think might be interested in the bandwidthd skips graphing bug part right below. Eduard, sorry for not spotting your mail sooner... I'm not subscribed to debian-mentors and forgot to mention that I want to be CCed. For anyone interested in reading Eduards initial mail: http://lists.debian.org/debian-mentors/2004/07/msg00136.html The thread started here: http://lists.debian.org/debian-mentors/2004/07/msg00120.html To everyone for the future: Please _always_ CC me when replying to any of my mails or anything that you think I might be interested in Bandwidthd skips graphing bug... I also triggered this when installing bandwidthd on my workstation yesterday (trying out debconf changes which I finally managed to get working). I haven't done an extensive review of the code but from what I've seen it could need some cleanups (more then the few ones I've already done). About Previouse graphing run not complete... Skipping current run.. Bandwidthd forks of children for doing the graphing so that no packets get lost if it takes some time to finish. These children aren't reaped until the next graphing run... If it's time to graph and there aren't any children to reap bandwidthd currently thinks the previous run isn't complete. Atleast on my workstation yesterday there where no graph childs at all... just the main 4 processes I don't know (yet) how this is possible but I will look into in really soon. The only thing I can think of straight up is that the first fork fails (and checking for fork failures isn't done) and there's no children to reap creating the infinite loop which never forks any children. I don't think that fork failure is very likely to happen on my idle workstation every time I tried restarting bandwidthd so as I said, I'll have to look closer at it... Priority: critical Next issue... Bandwidthd outputs stuff to stdout like Packet Encoding: Ethernet. It's on the upstream TODO-list and also one of my highest priorities to change bandwidthd to behave like a daemon should This includes _not_ working out of the current directory as it currently does and using syslog for any messages. Closing stdin/stdout/stderr is required before the package can be moved to the debconf layout I've created. I've send a couple of minor patches to David Hinkle (upstream) which I'd like to see merged before I continue with more work though... (He said he'll do a final review and then merge them but I haven't heard anything and they haven't shown up in the cvs at sourceforge so I'm still waiting..) Priority: high Moving along Few things that come to my mind... - write the required config steps into README.Debian Don't know why I haven't done this yet Will do ASAP. My goal is to (optionally) manage the config file with debconf though, but as this will not happen until I've finished the daemon behave cleanup I'll document the config steps for now. Priority: critical - move TODO paragrah into debian/TODO file (there are extra handling methods for a such file) I've though about it, but my goal was to not have any unfinished buissness. I guess that was really naive of me.. Will do this... Priority: high - do not confuse with megabyte (m, MB, 10^6) and mebibyte (M, MiB, 2^10) I was under the impression that bandwidthd only did bits (not bytes) which simplifies this issue alot. :) The TODO-item in my readme is more about when to use upper- and lower-case. AFAIK this is how it's supposed to be: Mega and above should be uppercase. Kilo and below should be lowercase. Bit should be lowercase (and byte uppercase, but since there's only bits...) Seconds should be lowercase. But who cares Priority: low Guess I need to go shopping for medium priority issues. ;) Just started my vacation like 1 hour ago, so these issues will have to wait a couple of days. I've hopefully made some progress in a week unless someone else cracks all these nuts before I get a chance. I'll post a status report to the list later on Thanks to everyone who've posted comments so far! Regards, Andreas Henriksson
RE: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Hi Eduard! ... and David, which I think might be interested in the bandwidthd skips graphing bug part right below. Eduard, sorry for not spotting your mail sooner... I'm not subscribed to debian-mentors and forgot to mention that I want to be CCed. For anyone interested in reading Eduards initial mail: http://lists.debian.org/debian-mentors/2004/07/msg00136.html The thread started here: http://lists.debian.org/debian-mentors/2004/07/msg00120.html To everyone for the future: Please _always_ CC me when replying to any of my mails or anything that you think I might be interested in Bandwidthd skips graphing bug... I also triggered this when installing bandwidthd on my workstation yesterday (trying out debconf changes which I finally managed to get working). I haven't done an extensive review of the code but from what I've seen it could need some cleanups (more then the few ones I've already done). About Previouse graphing run not complete... Skipping current run.. Bandwidthd forks of children for doing the graphing so that no packets get lost if it takes some time to finish. These children aren't reaped until the next graphing run... If it's time to graph and there aren't any children to reap bandwidthd currently thinks the previous run isn't complete. Atleast on my workstation yesterday there where no graph childs at all... just the main 4 processes I don't know (yet) how this is possible but I will look into in really soon. The only thing I can think of straight up is that the first fork fails (and checking for fork failures isn't done) and there's no children to reap creating the infinite loop which never forks any children. I don't think that fork failure is very likely to happen on my idle workstation every time I tried restarting bandwidthd so as I said, I'll have to look closer at it... Priority: critical Next issue... Bandwidthd outputs stuff to stdout like Packet Encoding: Ethernet. It's on the upstream TODO-list and also one of my highest priorities to change bandwidthd to behave like a daemon should This includes _not_ working out of the current directory as it currently does and using syslog for any messages. Closing stdin/stdout/stderr is required before the package can be moved to the debconf layout I've created. I've send a couple of minor patches to David Hinkle (upstream) which I'd like to see merged before I continue with more work though... (He said he'll do a final review and then merge them but I haven't heard anything and they haven't shown up in the cvs at sourceforge so I'm still waiting..) Priority: high Moving along Few things that come to my mind... - write the required config steps into README.Debian Don't know why I haven't done this yet Will do ASAP. My goal is to (optionally) manage the config file with debconf though, but as this will not happen until I've finished the daemon behave cleanup I'll document the config steps for now. Priority: critical - move TODO paragrah into debian/TODO file (there are extra handling methods for a such file) I've though about it, but my goal was to not have any unfinished buissness. I guess that was really naive of me.. Will do this... Priority: high - do not confuse with megabyte (m, MB, 10^6) and mebibyte (M, MiB, 2^10) I was under the impression that bandwidthd only did bits (not bytes) which simplifies this issue alot. :) The TODO-item in my readme is more about when to use upper- and lower-case. AFAIK this is how it's supposed to be: Mega and above should be uppercase. Kilo and below should be lowercase. Bit should be lowercase (and byte uppercase, but since there's only bits...) Seconds should be lowercase. But who cares Priority: low Guess I need to go shopping for medium priority issues. ;) Just started my vacation like 1 hour ago, so these issues will have to wait a couple of days. I've hopefully made some progress in a week unless someone else cracks all these nuts before I get a chance. I'll post a status report to the list later on Thanks to everyone who've posted comments so far! Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Andreas Henriksson [EMAIL PROTECTED] writes: Hi everybody! I'm looking for a sponsor to my bandwidthd package. BandwidthD tracks traffic on the local network. It uses libpcap to dissect the traffic and libgd to draw graphs (optional). Capable of logging traffic to CDF (optional), recovering from CDF (optional) and putting interface in promisc mode (optional). The daemon is totally stand alone and very easy to configure and use. Only dependancies are libpcap and libgd (any version). Example output available at http://fjortis.info/bandwidthd/. ... Any suggestions, comments, flames welcome! Nice one. I would like to see this included. I also have some feature suggestions (if its not yet possible): 1. logarithmic scale for bandwith and time options 2. draw incoming positive and outgoing negative in the same graph or vice versa 3. stack the different protocols on top of each other 4. draw line or bar graphs 5. smoothing of the graph (e.g. each point is the average bandwith over the last hour while points are 10m apart, i.e. they overlap timewise) 6. draw multiple views of the same data in one graph (e.g. unsmooth as bars, 1h avg. and 1d avg as lines overlayed) MfG Goswin
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Example output available at http://fjortis.info/bandwidthd/. ... Any suggestions, comments, flames welcome! Nice one. I would like to see this included. Ack. I would like to sponsor it but it does not work for me! I see only this messages repeating every minute: Previouse graphing run not complete... Skipping current run Previouse graphing run not complete... Skipping current run and the webpage says bandwidthd is collecting data... and seems not to be updated. Also, on start it spews few messages after the program is forked: Packet Encoding: Ethernet Packet Encoding: Ethernet Packet Encoding: Ethernet Packet Encoding: Ethernet Few things that come to my mind... - write the required config steps into README.Debian - move TODO paragrah into debian/TODO file (there are extra handling methods for a such file) - do not confuse with megabyte (m, MB, 10^6) and mebibyte (M, MiB, 2^10) Regards, Eduard. -- VI ist kein Editor, das ist ein Eingabestrom-Modifikator. -- Michael Kleinhenz
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Hi Goswin! Goswin von Brederlow [EMAIL PROTECTED] skrev den Thu, 08 Jul 2004 15:29:11 +0200: Nice one. I would like to see this included. Me too... ;) I also have some feature suggestions (if its not yet possible): Great! Unfortunately bandwidthd isn't very configurable, which on the other hand is also good because it makes it really easy to use. 1. logarithmic scale for bandwith and time options missing. 2. draw incoming positive and outgoing negative in the same graph or vice versa missing. I really like the idea though... I'll implement this some day. ;) 3. stack the different protocols on top of each other hmm. isn't the current graph stacked? a config option to make all protocols start from the bottom of the graph and an extra color for total might be good. Currently the next protocol adds on top of the previous. Although basing it from the ground up also requires intelligence on which protocol to put in front so they all show up and I guess quite some more code this isn't something I'm prepared to do with the package... on the other hand, nothing is stopping me from having a separate working tree where I do development against upstream. That will probably happen when the package require less time. (I currently have my hands full trying to learn debconf.) 4. draw line or bar graphs missing. Lines (you mean a line for the top right?) could be an easy solution to the which protocol to put in front problem that appears when starting all protocols from the baseline. 5. smoothing of the graph (e.g. each point is the average bandwith over the last hour while points are 10m apart, i.e. they overlap timewise) missing. I kind of like the edgy graphs, but smoothing shouldn't be very hard to implement as an option. 6. draw multiple views of the same data in one graph (e.g. unsmooth as bars, 1h avg. and 1d avg as lines overlayed) missing. If they all get implemented there's no reason why not to make a config option which not only gives you the possibility of choosing one. We can just as well change ip-timeframe-something.png to include GRAPHMETHOD and then just enable/disable each method in the config and adjust the html-output. :) Graphs are drawn quite frequently though and I guess multiplying all the work a couple of times will use up quite some resources. MfG Goswin As you see there's not really much flexibility in bandwidthd today. On the other hand thats probably why so many people like it. Flexible graphs can be created with mrtg/rrd-tool/scripts or whatever combination. The problem with that is just that it usually takes up alot of time and I guess many people like me don't really want to spend alot of time on network graphs. It's only something nice to have if you can get it for free. I'll send your comments to David Hinkle (upstream) and also keep them around for a rainy day to try to implement myself. Hopefully this will give him something to think about so he stops thinking that bandwidthd is for the most part to be stable and complete. ;P Thanks for your comments! Btw. If you are good at debconf and have a minute over to help me find out why the config script isn't getting triggered even though I've tried dh_installdebconf and manually copying the script and templates to tmp/DEBIAN/ please yell! :) -- Regards, Andreas Henriksson
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Andreas Henriksson [EMAIL PROTECTED] wrote: Btw. If you are good at debconf and have a minute over to help me find out why the config script isn't getting triggered even though I've tried dh_installdebconf and manually copying the script and templates to tmp/DEBIAN/ please yell! :) Is it executable (which shouldn't be a problem with dh_installdebconf, I guess)? Is it in the final package? Regards, Frank -- Frank Küster, Biozentrum der Univ. Basel Abt. Biophysikalische Chemie
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Andreas Henriksson [EMAIL PROTECTED] writes: As you see there's not really much flexibility in bandwidthd today. On the other hand thats probably why so many people like it. Flexible graphs can be created with mrtg/rrd-tool/scripts or whatever combination. The problem with that is just that it usually takes up alot of time and I guess many people like me don't really want to spend alot of time on network graphs. It's only something nice to have if you can get it for free. Problem is that neither mrtg nor rrd-tool graphs can do it. For example rrd-tool can do logartihmic scale or drawing outgoing positive and incoming negative. But not both (since log of negative numbers is undefined). And a smoothing function using PREV() causes segfaults. If drawing the graphs takes too much time you might want to only draw them on demand and cache them (even cache them longer than the actual update interval). But that would require some sort or database or a drawing server so you can output them on demand. Haven't looked at the design. I'll send your comments to David Hinkle (upstream) and also keep them around for a rainy day to try to implement myself. Hopefully this will give him something to think about so he stops thinking that bandwidthd is for the most part to be stable and complete. ;P Thanks for your comments! Btw. If you are good at debconf and have a minute over to help me find out why the config script isn't getting triggered even though I've tried dh_installdebconf and manually copying the script and templates to tmp/DEBIAN/ please yell! :) I'm a novice with writing debconf scripts. Only done some cutpaste there myself. MfG Goswin
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Andreas Henriksson [EMAIL PROTECTED] writes: Hi everybody! I'm looking for a sponsor to my bandwidthd package. BandwidthD tracks traffic on the local network. It uses libpcap to dissect the traffic and libgd to draw graphs (optional). Capable of logging traffic to CDF (optional), recovering from CDF (optional) and putting interface in promisc mode (optional). The daemon is totally stand alone and very easy to configure and use. Only dependancies are libpcap and libgd (any version). Example output available at http://fjortis.info/bandwidthd/. ... Any suggestions, comments, flames welcome! Nice one. I would like to see this included. I also have some feature suggestions (if its not yet possible): 1. logarithmic scale for bandwith and time options 2. draw incoming positive and outgoing negative in the same graph or vice versa 3. stack the different protocols on top of each other 4. draw line or bar graphs 5. smoothing of the graph (e.g. each point is the average bandwith over the last hour while points are 10m apart, i.e. they overlap timewise) 6. draw multiple views of the same data in one graph (e.g. unsmooth as bars, 1h avg. and 1d avg as lines overlayed) MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Example output available at http://fjortis.info/bandwidthd/. ... Any suggestions, comments, flames welcome! Nice one. I would like to see this included. Ack. I would like to sponsor it but it does not work for me! I see only this messages repeating every minute: Previouse graphing run not complete... Skipping current run Previouse graphing run not complete... Skipping current run and the webpage says bandwidthd is collecting data... and seems not to be updated. Also, on start it spews few messages after the program is forked: Packet Encoding: Ethernet Packet Encoding: Ethernet Packet Encoding: Ethernet Packet Encoding: Ethernet Few things that come to my mind... - write the required config steps into README.Debian - move TODO paragrah into debian/TODO file (there are extra handling methods for a such file) - do not confuse with megabyte (m, MB, 10^6) and mebibyte (M, MiB, 2^10) Regards, Eduard. -- VI ist kein Editor, das ist ein Eingabestrom-Modifikator. -- Michael Kleinhenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Andreas Henriksson [EMAIL PROTECTED] wrote: Btw. If you are good at debconf and have a minute over to help me find out why the config script isn't getting triggered even though I've tried dh_installdebconf and manually copying the script and templates to tmp/DEBIAN/ please yell! :) Is it executable (which shouldn't be a problem with dh_installdebconf, I guess)? Is it in the final package? Regards, Frank -- Frank Küster, Biozentrum der Univ. Basel Abt. Biophysikalische Chemie
Re: RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Andreas Henriksson [EMAIL PROTECTED] writes: As you see there's not really much flexibility in bandwidthd today. On the other hand thats probably why so many people like it. Flexible graphs can be created with mrtg/rrd-tool/scripts or whatever combination. The problem with that is just that it usually takes up alot of time and I guess many people like me don't really want to spend alot of time on network graphs. It's only something nice to have if you can get it for free. Problem is that neither mrtg nor rrd-tool graphs can do it. For example rrd-tool can do logartihmic scale or drawing outgoing positive and incoming negative. But not both (since log of negative numbers is undefined). And a smoothing function using PREV() causes segfaults. If drawing the graphs takes too much time you might want to only draw them on demand and cache them (even cache them longer than the actual update interval). But that would require some sort or database or a drawing server so you can output them on demand. Haven't looked at the design. I'll send your comments to David Hinkle (upstream) and also keep them around for a rainy day to try to implement myself. Hopefully this will give him something to think about so he stops thinking that bandwidthd is for the most part to be stable and complete. ;P Thanks for your comments! Btw. If you are good at debconf and have a minute over to help me find out why the config script isn't getting triggered even though I've tried dh_installdebconf and manually copying the script and templates to tmp/DEBIAN/ please yell! :) I'm a novice with writing debconf scripts. Only done some cutpaste there myself. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Hi everybody! I'm looking for a sponsor to my bandwidthd package. BandwidthD tracks traffic on the local network. It uses libpcap to dissect the traffic and libgd to draw graphs (optional). Capable of logging traffic to CDF (optional), recovering from CDF (optional) and putting interface in promisc mode (optional). The daemon is totally stand alone and very easy to configure and use. Only dependancies are libpcap and libgd (any version). Example output available at http://fjortis.info/bandwidthd/. Relevant information about upstream: - Name: BandwidthD - Version : 1.2.1b - Upstream Author : David Hinkle [EMAIL PROTECTED] - URL : http://bandwidthd.sourceforge.net/ - License : GPL - Description : tracks network utilization per ip and draws graphs. Relevant information about package: - Name: bandwidthd - Version : 1.2.1b-13 - URL : http://fjortis.info/pub/debian/bandwidthd-latest/ - Packager: Andreas Henriksson [EMAIL PROTECTED] - Lintian clean : Yes. - ITP : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=227768 - Example output : http://fjortis.info/bandwidthd/ Additional information: - Package also available from http://mentors.debian.net/. - RFP filed by upstream author. - Contact with upstream author established. (Changes done in the bandwidthd package are on it's way into the upstream cvs.) - Package compatible with Woody (simply build on woody and install). - Very easy to configure and use. Any suggestions, comments, flames welcome! Regards, Andreas Henriksson signature.asc Description: Digital signature
RFS: bandwidthd - tracks network utilization per ip and draws graphs.
Hi everybody! I'm looking for a sponsor to my bandwidthd package. BandwidthD tracks traffic on the local network. It uses libpcap to dissect the traffic and libgd to draw graphs (optional). Capable of logging traffic to CDF (optional), recovering from CDF (optional) and putting interface in promisc mode (optional). The daemon is totally stand alone and very easy to configure and use. Only dependancies are libpcap and libgd (any version). Example output available at http://fjortis.info/bandwidthd/. Relevant information about upstream: - Name: BandwidthD - Version : 1.2.1b - Upstream Author : David Hinkle [EMAIL PROTECTED] - URL : http://bandwidthd.sourceforge.net/ - License : GPL - Description : tracks network utilization per ip and draws graphs. Relevant information about package: - Name: bandwidthd - Version : 1.2.1b-13 - URL : http://fjortis.info/pub/debian/bandwidthd-latest/ - Packager: Andreas Henriksson [EMAIL PROTECTED] - Lintian clean : Yes. - ITP : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=227768 - Example output : http://fjortis.info/bandwidthd/ Additional information: - Package also available from http://mentors.debian.net/. - RFP filed by upstream author. - Contact with upstream author established. (Changes done in the bandwidthd package are on it's way into the upstream cvs.) - Package compatible with Woody (simply build on woody and install). - Very easy to configure and use. Any suggestions, comments, flames welcome! Regards, Andreas Henriksson signature.asc Description: Digital signature
