From owner-freebsd-pf@FreeBSD.ORG  Thu Oct 13 17:50:01 2005
Return-Path: <owner-freebsd-pf@FreeBSD.ORG>
X-Original-To: freebsd-pf@freebsd.org
Delivered-To: freebsd-pf@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 67DFF16A41F
	for <freebsd-pf@freebsd.org>; Thu, 13 Oct 2005 17:50:01 +0000 (GMT)
	(envelope-from KBuff@zetron.com)
Received: from zetxch01.zetron.com (zetmail2.zetron.com [216.202.42.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 10E8043D49
	for <freebsd-pf@freebsd.org>; Thu, 13 Oct 2005 17:50:00 +0000 (GMT)
	(envelope-from KBuff@zetron.com)
Received: by zetxch01.zetron.com with Internet Mail Service (5.5.2657.72)
	id <PHJCCZ3M>; Thu, 13 Oct 2005 10:49:56 -0700
Message-ID: <054222519C2ED411A68E00508B603AC70A3D0A16@zetxch01.zetron.com>
From: Kurt Buff <KBuff@zetron.com>
To: 'Tyler' <tyler@tylercentral.com>, freebsd-pf@freebsd.org
Date: Thu, 13 Oct 2005 10:49:46 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
Cc: 
Subject: RE: Per Protocol Traffic Accounting
X-BeenThere: freebsd-pf@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
	\(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
	<mailto:freebsd-pf-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pf>
List-Post: <mailto:freebsd-pf@freebsd.org>
List-Help: <mailto:freebsd-pf-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
	<mailto:freebsd-pf-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Oct 2005 17:50:01 -0000

Tyler wrote:
> Hi All,
> 
> I'm trying to count both in and out traffic on a per-protocol basis. 
> With the ultimate goal of MRTG'ing and recording the amount of traffic
> in and out of the server for each service.  So far, my Googling, and
> mailing list archive searches have not produced a solution.  

Uh, perhaps ntop, bound to the external NIC?

It's a very nice package, and although it doesn't provide 'accounting' as
such, it's a very nice tool for understanding who is talking to whom, on
what protocol.