Projects / bandwidthd

bandwidthd

bandwidthd tracks usage of TCP/IP network subnets and builds HTML files with graphs to display network utilization. Charts are built by individual IP to show their utilization over 2, 8, 45, and 400 day periods. It color codes HTTP, HTTPS, TCP,UDP, ICMP, VPN, and P2P traffic. Unlike MRTG, it tracks each individual IP address and subnets, not the status of any particular link. Static mode is fast and easy to set up and has few dependencies. Database mode supports filtering by subnet, multiple sensors, custom reports and intervals, and can process thousands of IPs efficiently. Network utilization can be logged in CDF or a backend database.

Tags
Licenses
Operating Systems
Implementation

Recent releases

  •  12 Jan 2005 03:55

    Release Notes: This release added an optional PostgreSQL database logging mode and a PHP application for dynamically creating graphs from databases. Support for subnet filtering, multiple sensors, drill down, custom intervals, and reports was provided. autoconf was implemented, allowing the program to compile on all major platforms including Windows. Huge performance gains were achieved in the graphing engine due to bugfixes and interval tweaking. The need for Sys V IPC shared memeory was removed and log rotation was implemented for all logs.

    •  13 Apr 2004 23:31

      Release Notes: This release adds a filter option to bandwidthd.conf to specify the libpcap filter, fixes problems with YAxis labeling and scaling on high volume networks, skips starting a new graphing run if the last run is still going to prevent fork bomb style box crashes, exits on a configuration error, prints out line number of errors in bandwidthd.conf, causes graph_cutoff to be scaled with time range to reduce load, includes weekly/monthly/yearly graphs, reduces loading spam, and updates the documentation.

      •  15 Jan 2004 18:56

        Release Notes: CDF documentation in the README has been fixed.

        •  14 Jan 2004 21:43

          Release Notes: Weekly, monthly, and yearly graphs have been added. This release will do a graph run immediately after loading its data. There are new 10 minute (log2.cdf), 1 hour (log3.cdf), and 12 hour (log4.cdf) interval log files. The graphing code now scales better with different custom intervals and periods.

          •  12 Jan 2004 21:51

            Release Notes: DLT_EN10MB is wrapped in an ifdef for platforms that don't supply it. Crashes when brought up on an IP addressless interface have been fixed. A segfault in DropOldData has been fixed. Some errors in the Makefile have been fixed, and bandwidthd.conf is preserved. HTTPS is detected as HTTP. A bug that would cause "killall -HUP bandwidthd" to kill the graphing process has been fixed. Initial support has been added for datalink type 12 DLT_RAW and for datalink type 6 token ring DLT_IEEE802.

            Recent comments

            11 Jan 2005 17:28 drachs

            Re: Listen on multiple interfaces


            > Is it possible to draw graph on more

            > than one interface? I have 3 interfaces,

            > 1 outside and 2 local and I want see

            > graphs on both local interfaces!

            You have to run multiple instances of bandwidthd on most platforms. On some platforms you can listen on the "all" device.

            30 Jul 2004 02:26 PeeCis

            Listen on multiple interfaces
            Is it possible to draw graph on more than one interface? I have 3 interfaces, 1 outside and 2 local and I want see graphs on both local interfaces!

            Screenshot

            Project Spotlight

            OpenStack4j

            A Fluent OpenStack client API for Java.

            Screenshot

            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.