VERSION.
0.12.1

DESCRIPTION.
pmacct is a small set of passive network monitoring tools to
measure, account, classify, aggregate and export IPv4 and IPv6
traffic; a pluggable and flexible architecture allows to store
collected network data into memory tables or SQL (MySQL, SQLite,
PostgreSQL) databases and export them through NetFlow or sFlow
protocols to remote collectors. pmacct supports fully customizable
historical data breakdown, sampling, filtering and tagging and
triggers. Libpcap, Netlink/ULOG, sFlow v2/v4/v5 and NetFlow v1/
v5/v7/v8/v9 are supported, both unicast and multicast. Also, a
client program makes it easy to export data to tools like RRDtool,
GNUPlot, Net-SNMP, MRTG, and Cacti.


HOMEPAGE.
http://www.pmacct.net/


DOWNLOAD.
http://www.pmacct.net/pmacct-0.12.1.tar.gz


CHANGELOG.
+ Input/output interfaces (SNMP indexes) have now been implemented
  natively; it's therefore not required anymore to pass through the
  (Pre-)tag infrastructure. As a result two aggregation primitives
  are being introduced: 'in_iface' and 'out_iface'.
+ Support for source/destination IP prefix masks is introduced via
  two new aggregation primitives: src_mask and dst_mask. These are
  populated as defined by the [nf|sf|pm|u]acctd_net directive:
  NetFlow/sFlow protocols, BGP, Network files (networks_file) or
  static (networks_mask) being valid data sources.
+ A generic tunnel inspection infrastructure has been developed to
  benefit both pmacctd and uacctd daemons. Handlers are defined via
  configuration file. Once enabled daemons will account basing upon
  tunnelled headers rather than the envelope. Currently the only
  supported tunnel protocol is GTP, the GPRS tunnelling protocol
  (which can be configured as: "tunnel_0: gtp, <UDP port>"). Up to
  8 different tunnel stacks and up to 4 tunnel layers per stack are
  supported. First matching stack, first matching layer wins.
+ uacctd: support for the MAC layer has been added for the Netlink/
  ULOG Linux packet capturing framework.
+ 'nfprobe_source_ip' feature introduced: it allows to select the
  IPv4/IPv6 address to be used to export NetFlow datagrams to the
  collector.
+ nfprobe, sfprobe: network masks are now exported via NetFlow and
  sFlow. 'pmacctd_net' and its equivalent directives define how to
  populate src_mask and dst_mask values.
! cleanup, nfprobe/sfprobe: data source for 'src_as' and 'dst_as'
  primitives is now expected to be always explicitely defined (in
  line with how 'src_net' and 'dst_net' primitives work). See the
  UPGRADE doc for the (limited) backward compatibility impact.
! Updated SQL documentation: sql/README.iface guides on 'in_iface'
  and 'out_iface' primitives; sql/README.mask guides on 'src_mask'
  and 'dst_mask' primitives; sql/README.is_symmetric guides on
  'is_symmetric' primitive.
! fix, nfacctd.h: source and destination network masks were twisted
  in the NetFlow v5 export structure definition. Affected releases
  are: 0.12.0rc4 and 0.12.0.
! fix, nfprobe_plugin.c: l2_to_flowrec() was missing some variable
  declaration when the package was configured for compilation with
  --disable-l2. Thanks to Brent Van Dussen for reporting the issue.
! fix, bgp.c: bgp_attr_munge_as4path() return code was not defined
  for some cases. This was causing some BGP messages to be marked
  as malformed.
! fix, sfprobe: a dummy MAC layer was created whenever this was not
  included as part of the captured packet. This behaviour has been
  changed and header protocol is now set to 11 (IPv4) or 12 (IPv6)
  accordingly. Thanks to Neil McKee for pointing the issue.
! workaround, building sub-system: PF_RING enabled libpcap was not
  recognized due to missing of pcap_dispatch(). This is now fixed.


NOTES.
* data source for 'src_as' and 'dst_as' primitives for nfprobe and
  sfprobe plugins is now expected to be explicitely defined via the
  [ pmacctd_as | uacctd_as ] directive. All other plugins were already
  working like that. In terms of backward compatibility the only case
  affected is getting ASN values out of a Networks File: up to 0.12.0,
  it was sufficient to define a networks_file to implicitely use it.


Cheers,
Paolo

_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Reply via email to