From owner-freebsd-isp@FreeBSD.ORG Wed Jul 6 11:35:12 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2542116A41C for ; Wed, 6 Jul 2005 11:35:12 +0000 (GMT) (envelope-from lists@visionsix.com) Received: from mordrede.visionsix.net (mordrede.visionsix.net [206.113.65.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7C3643D45 for ; Wed, 6 Jul 2005 11:35:11 +0000 (GMT) (envelope-from lists@visionsix.com) Received: from vsis169 (unverified [206.113.65.14]) by mordrede.visionsix.net (Vircom SMTPRS 4.0.340.0) with SMTP id for ; Wed, 6 Jul 2005 06:35:10 -0500 Message-ID: <001801c5821e$c455e340$de0a0a0a@visionsix.com> From: "Lewis Watson" To: References: <3b88b80a0507051933f4750f3@mail.gmail.com><06ef01c581f6$c54fb3c0$de0a0a0a@visionsix.com> <1120637769.16870.6.camel@tessa.mysmt.net> Date: Wed, 6 Jul 2005 06:35:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: Multiple IP MRTG or Similar X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2005 11:35:12 -0000 > Hi my expirience is that bandwithd does a terrible job, it sets your > interface in promisious mode if I'm not mistaken and keeps it's data = in > ram. use it only for investigation or test environment's not on > production systems (my advice.) >=20 > -Erik. Hi, I would like to share some of our experiences with Bandwidthd. As I = mentioned in my previous email, Netflow and Bandwidthd are certainly two = vastly different applications. However, we have used and tested = Bandwidthd in a variety of small and small-medium size environments. In = the end we found no problem running Bandwidthd and in each case it did = exactly what we needed it to do. We have ran Bandwidthd on a FreeBSD firewall/ bridge with over 2000 = client machines passing traffic through it daily for six months. The = clients all were connected via T1 circuits or better. We experienced no = problems using the conventional logs it generated. We have also had Bandwidthd running for about two years on a much = smaller network. Initially there was an issue on this host with FreeBSD = but an update resolved the bug that was found a few months ago in = regards to the logs not being able to generate the stats after rebooting = the server. There have been other situations where we have used Bandwidthd and the = results were always similar to the above examples. You can disable = promiscuous mode on startup, otherwise I would probably leave it alone = as well. The new version of bandwidthd gives the option to store the = stats in PostgreSQL or in memory via text files. There is not much in = the way of configuration unless you edit the src directly - (we added a = line to include a css file and a few cosmetic changes) I think the = config file is much simpler to use than MRTG, which was another issue = the user had mentioned in the original email. This is just the luck we have had with Bandwidthd... I have no idea if = it has ever worked for anyone else. Take care, Lewis Watson