From owner-freebsd-isp  Tue Aug 19 14:29:02 1997
Return-Path: <owner-freebsd-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA06722
          for isp-outgoing; Tue, 19 Aug 1997 14:29:02 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA06714
          for <freebsd-isp@FreeBSD.ORG>; Tue, 19 Aug 1997 14:28:59 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id OAA00769; Tue, 19 Aug 1997 14:28:41 -0700 (PDT)
To: Nicholas Merrill <nick@calyx.net>
cc: freebsd-isp@FreeBSD.ORG
Subject: Re: WinNT to FreeBSD 
In-reply-to: Your message of "Tue, 19 Aug 1997 16:09:29 EDT."
             <3.0.3.32.19970819160929.0375cc84@calyx.net> 
Date: Tue, 19 Aug 1997 14:28:41 -0700
Message-ID: <765.872026121@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Actually I heard it wasn't possible to track any information like that
> with FreeBSD.  That may be the one edge that NT has in this competition. <g>

You heard wrong - it's possible, just not immediately trivial.

1. You could log connection times with ppp's logging facility (depending
   on how you've got dialins configured) or, if you're doing ppp from
   a PM or Ascend box, with radiusd.

2. Bytes downloaded can be handled with ipfw and its packet accounting
   features, among various other methods.

Neither technique requires heaps of UNIX-guruhood but a good, complete
knowledge of FreeBSD is something of a prerequisite to setting either
of these systems.  I'd also argue that anyone trying to run an ISP
with FreeBSD (or NT, for that matter) without such local expertise is
just living on borrowed time anyway.

					Jordan