pmacct is a set of passive network monitoring tools to measure, account,
classify, aggregate and export IPv4 and IPv6 traffic, suitable to ISP, IXP,
CDN, IP carrier, data-centre and hot-spot enviroments.
Being able to collect flow data through libpcap, NetFlow and sFlow and
optionally augment this by configuring peering with the included BGP
daemon, granularity is fine enough for essential network management
tasks such as billing, graphing network resource usage, analysing live
or historical traffic trends, steering BGP peerings, real-time alerting,
and certain SLA monitoring.
Aggregation, flexible filtering, sampling and renormalization capabilities
are provided to help cope with the large amounts of data produced by high-
speed networks. Using either memory or database tables (MySQL, PostgreSQL,
SQLite) as backend storage, pmacct can easily feed data into external
tools, including RRDtool, GNUPlot, Net-SNMP, MRTG and Cacti.
The default package provides SQLite support, available flavors are:
threads compile with threads, required for BGP integration
or running packet classification in parallel
mysql compile with support for MySQL
postgresql compile with support for PostgreSQL
A widget to display large sets of data as dots (or lines). Different
data sets will have different colors, you may change colors and style of
the data The widget gives the possibility to zoom into and out of the
data and to scroll around. It also offers a grid like on an
oscilloscope.
With tweaks from landry@
ok landry@
* Shared objects
* Virtual backups
* Duplicate Job Control
* TLS Authentication
* Exclude Dir Containing = <filename-string>
* Plugins including Exchange 2003/2007 Plugin
* libdbi backend abstraction
* Bat enhancements
Upgrading from 2.4.4 to 3.0.2 requires updating the database using
/usr/local/libexec/bacula/update_bacula_database. Database upgrades
from older databases can be done with other scripts in
/usr/local/libexec/bacula/updatedb. You can determine your database
version in mysql and postgresql with 'select * from version'.
As sthen@ reminded me and the documentation points out, when upgrading
between major versions (2.x.x -> 3.x.x), you should upgrade all of your
components at the same time due to protocol changes.
a *lot* of help from and ok sthen@
help from me. The IPv6 features provided by scapy6 are integrated (still
some problems with them, but working well enough) so pkgpath/conflict
markers are set to replace an existing scapy6 installation.
ok wcmaier@ "if it works go for it" claudio@
