Autoreply: Re: [cobalt-security] traffic question

[hostmaster@xxxxxxxxxxxxx]

Bonjour,
Je ne serait pas atteignable la journée du lundi 25 février au vendredi 1er mars inclus. Votre message sera traité en début de soirée. Vous trouverez ci-après la liste des contacts directs pour les questions urgentes :
Connections à Internet     : hotline@xxxxxxxxxxxxx
Hébergements/Commercial    : hosting@xxxxxxxxxxxxx
Compteurs/Scripts/Linux    : linux@xxxxxxxxxxxxx
Facturation/Rappels        : lincey@xxxxxxxxxxxxx
Direction                  : borishome@xxxxxxxxxxxxx

Avec mes meilleures salutations,
Infomaniak Network SA
Fabian Lucchi


Your message reads:

Received: from list.cobalt.com (unverified [63.77.128.170]) by aristote2.infomaniak.ch
 (Rockliffe SMTPRA 4.5.6) with ESMTP id <B0011668801@xxxxxxxxxxxxxxxxxxxxxxx> for <hostmaster@xxxxxxxxxxxxx>;
 Tue, 26 Feb 2002 16:21:27 +0100
Received: from list.cobalt.com (localhost [127.0.0.1])
	by list.cobalt.com (8.9.3/8.9.3) with ESMTP id HAA05268;
	Tue, 26 Feb 2002 07:17:16 -0800
Received: from ns2.befriend.com ([207.218.238.21])
	by list.cobalt.com (8.9.3/8.9.3) with ESMTP id HAA04799
	for <cobalt-security@xxxxxxxxxxxxxxx>; Tue, 26 Feb 2002 07:01:15 -0800
Received: from satellite (pool-209-158-202-143.rich.east.verizon.net [209.158.202.143])
	by ns2.befriend.com (8.10.2/8.10.2) with SMTP id g1QExNM26054
	for <cobalt-security@xxxxxxxxxxxxxxx>; Tue, 26 Feb 2002 08:59:23 -0600
Message-ID: <>
From: "Steve Werby" <steve-lists@xxxxxxxxxxxx>
To: <cobalt-security@xxxxxxxxxxxxxxx>
References: <B8A1009C.73E47%ayoung78@xxxxxxxx>
Subject: Re: [cobalt-security] traffic question
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: cobalt-security-admin@xxxxxxxxxxxxxxx
Errors-To: cobalt-security-admin@xxxxxxxxxxxxxxx
X-BeenThere: cobalt-security@xxxxxxxxxxxxxxx
X-Mailman-Version: 2.0.6
Precedence: bulk
Reply-To: cobalt-security@xxxxxxxxxxxxxxx
List-Help: <mailto:cobalt-security-request@xxxxxxxxxxxxxxx?subject=help>
List-Post: <mailto:cobalt-security@xxxxxxxxxxxxxxx>
List-Subscribe: <http://list.cobalt.com/mailman/listinfo/cobalt-security>,
	<mailto:cobalt-security-request@xxxxxxxxxxxxxxx?subject=subscribe>
List-Id: Mailing list for users to address network security on Cobalt products. <cobalt-security.list.cobalt.com>
List-Unsubscribe: <http://list.cobalt.com/mailman/listinfo/cobalt-security>,
	<mailto:cobalt-security-request@xxxxxxxxxxxxxxx?subject=unsubscribe>
List-Archive: <http://list.cobalt.com/pipermail/cobalt-security/>
Date: Tue, 26 Feb 2002 09:59:55 -0500

"AYoung@Home" <ayoung78@xxxxxxxx> wrote:
> If memory servers me right you can set bandwith if that's what you want to
> do per IP via the Cobalt GUI (Raq4i).
>
> Access Server GUI-->Control Panel-->Bandwith (top of page)-->Add, then
> complete.  Of course if you only have 1 IP # then you'll probably not be
> able to restrict.

True, but that just limits the throughput rate.  From what I understand, the
original poster doesn't want to throttle the throughput rate, just limit the
total traffic during a month by turning the site off or pointing it to a
special page when that traffic total is reached.  To answer Peter's
question, I don't think you'll find a solution that stops serving up users'
sites when their traffic hits the quota you've set.  If their month to date
traffic is stored in a text file, db, html source code, etc. it would be
fairly easy for a programmer to write a script which looks up that number
and compares it to the quota and takes action.  Whether that action is
sending an email, tracking their overage so you can bill them, pointing
their site pages to a special page, shutting down their email, etc. or some
combination of those another script will be needed to perform the action.
If you wanted to point to a special page for example, the script would need
to modify the Apache config file and run a command to reload the config
file.  Both will require root privileges and so a script run as root from
cron automatically at whatever frequency makes sense (probably nightly) may
be the way to go.  These are the types of software solutions I build for
clients so if you want to discuss with me off-list feel free to contact me
by email or at the # listed on my site.

--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/


_______________________________________________
cobalt-security mailing list
cobalt-security@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-security