From owner-freebsd-net@FreeBSD.ORG Wed Jan 19 01:57:46 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10AD716A4CE for ; Wed, 19 Jan 2005 01:57:46 +0000 (GMT) Received: from out008.verizon.net (out008pub.verizon.net [206.46.170.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 872D843D49 for ; Wed, 19 Jan 2005 01:57:45 +0000 (GMT) (envelope-from jetman@mycbc.com) Received: from EAGLE ([70.18.34.185]) by out008.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050119015744.SDOP17379.out008.verizon.net@EAGLE> for ; Tue, 18 Jan 2005 19:57:44 -0600 Message-ID: <001801c4fdca$37bc1270$7300a8c0@EAGLE> From: "The Jetman" To: "FreeBSD Net" Date: Tue, 18 Jan 2005 20:57:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Authentication-Info: Submitted using SMTP AUTH at out008.verizon.net from [70.18.34.185] at Tue, 18 Jan 2005 19:57:40 -0600 Subject: Re: Network Accounting X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 01:57:46 -0000 I've been following this little thread and was curious about how my own solution compares w/ the others discussed. #### x.y.z.14 ${ipfw} add pipe 7 ip from x.y.z.14 to any ${ipfw} pipe 7 config bw 1024Kbit/s queue 50 ${ipfw} add pipe 8 ip from any to x.y.z.14 ${ipfw} pipe 8 config bw 1024Kbit/s queue 50 #### I setup a series of rules for each of a real IPs, as shown above, to cap bwidth usage and to provide a series of byte counters that could be captured hourly. This box was a bridge box bet the client's internal net and their T1. My CRON job would sit on the working side of a pipe from the 'ipfw -a list' command, then parse each rule for the inbound then outbound byte/packet count. Each inbound and outbount count was then inserted into a SQL UPDATE stmt for each IP. I inquire bet I've seen a nbr of other approaches and was wondering are all of these approaches equally valid, but I'm esp curious if my approach makes sense. TIA. Later....Jet =============== From the desk of Jethro Wright, III ================ + Beer is proof that God loves us and wants us to be happy. - ============================================== Benjamin Franklin ===