From owner-freebsd-isp Sat Mar 11 1:10:15 2000 Delivered-To: freebsd-isp@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id D242637B858 for ; Sat, 11 Mar 2000 01:10:09 -0800 (PST) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (root@guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id TAA59561; Sat, 11 Mar 2000 19:40:27 +1030 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id TAA01708; Sat, 11 Mar 2000 19:40:01 +1030 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 11 Mar 2000 19:40:01 +1030 (CST) From: "Daniel O'Connor" To: Rowan Crowe Subject: RE: [Oz-ISP] tagging IP packets travelling over internal network Cc: aussie-isp@aussie.net, freebsd-isp@freebsd.org Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 11-Mar-00 Rowan Crowe wrote: > The problem with this is that I have to account at 4 different inbound > points, and something central has to collect this data from the > individual > points and apply them to a single account. > (Accurate) accounting can't be done from a single point because some > traffic will enter and leave via the same router, plus it's difficult to > assume what is national and international based on the source alone. Why don't you place machines at the entry points which log the information you need, and then have a central machine get the data off them and collate it appropriatly.. Gee, it sounds really simple said like that 8-) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message