[95831] in RedHat Linux List
Re: Tools for ISP's...
daemon@ATHENA.MIT.EDU (Nikki Cook)
Wed Oct 21 16:42:17 1998
Date: Wed, 21 Oct 1998 16:41:37 -0400
To: redhat-list@redhat.com
From: Nikki Cook <sunny@mail.suntrix.com>
In-Reply-To: <362E31F4.AAC618AF@eburg.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Hi Gordon,
We run a small ISP here in Daytona. We have had quite a number of ISP's in
our area go under because of bad accounting procedures. Not us, of course,
I'm a killer on due dates.
To specifically answer your question, sounds like a killer project that
would have lots of interest. I hasten to add, accounting online time is
still not being metered here in Florida, afaik. However expire dates,
account types, space used and additional services are important to be
tracked and billed. From your description below, looks like you have a
handle on needs.
Best wishes on the project.
Nikki
At 03:11 PM 10/21/98 , you wrote:
>A while back, someone expressed interest in a set of tools for ISPs.=20
>Something that anyone could use to maintain users of the system, in a
>GUI.
>
>At the time, my ISP was just beginning to undertake just such a
>project. However, as busy as we are, it hasn't gotten far. Last
>week, I was assigned to undertake the project, and see it completed.=20
>I convinced my management that an open project would move faster and
>be more complete, so I'm checking for interest here.
>
>Goals of the project:
>The software must be first, secure. It must provide for the
>maintainance of all aspects of a user's accounts, as well as billing
>and RADIUS authentication (probably).
>
>Design:
>At the heart of the project is an administration daemon, which keeps
>it's data in an SQL database. The first clients will be web based, to
>eliminate the current text-based menus.
>Command line utilities will follow immediately, since there will be
>the neccessity of cron jobs and the like.
>
>At any given interval the daemon must print bills for the users. I'm
>thinking of using Tex here, any ideas for more efficient systems?
>
>The daemon will probably also be the interface for RADIUS
>authentication. It'll have to provide this as some kind of module, I
>suppose, since not all of our equipment uses the same RADIUS
>interface. (we currently run RADIUS on multiple machines...)
>
>I figure that I'll need at least three tables:
>Customer Info:
>Customer # for POS, Last name , First name, Street Ad., City, St, ZIP,
>Phone
>
>User:
>CUSTOMER#, username, status(active, locked), type(employee, free, off
>hours, monthly, quarterly...), expiration date, web space in MB,
>personal webpage indexed (y,n), business webpage indexed(y,n), domain
>names hosted
>
>Billing:
>Service, cost, and billing frequency for each service.
>
>So...Is anyone interested? Any suggestions or requests? Anyone want
>to help?
>
>TIA for any replys
>MSG
>
>
>--=20
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-list-request@redhat.com with=20
> "unsubscribe" as the Subject.
>=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SunTrix Com Internet Services
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Daytona Beach,=
Florida
=A0=A0=A0=A0 PPP and Shell Accounts (904) 258-5434
=A0=A0=A0 WEB Design webdesign@mail.suntrix.com
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 http://www.suntrix.com
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 WEBBnet IRC Network
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 irc.webbnet.org | irc.us.webbnet.org
=A0=A0=A0=A0=A0=A0=A0ftp://ftp.suntrix.com | mail.suntrix.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
