> > sorry if i lost part of the discussion, but why dont you
> > just associate a quota with a rule and specify one of the
> > two possible results when exceeding quota:
> >
> >ipfw match-upto 20MB
> >ipfw deny-above 20MB
...
> Well, it may or may not be able to cover a situation I'
On Thu 2000-06-08 (11:43), Luigi Rizzo wrote:
> sorry if i lost part of the discussion, but why dont you
> just associate a quota with a rule and specify one of the
> two possible results when exceeding quota:
>
>ipfw match-upto 20MB
>ipfw deny-above 20MB
>
> where the first syntax
On Thu, 8 Jun 2000, Luigi Rizzo wrote:
> sorry if i lost part of the discussion, but why dont you
> just associate a quota with a rule and specify one of the
> two possible results when exceeding quota:
>ipfw match-upto 20MB
>ipfw deny-above 20MB
> where the first syntax does not
sorry if i lost part of the discussion, but why dont you
just associate a quota with a rule and specify one of the
two possible results when exceeding quota:
ipfw match-upto 20MB
ipfw deny-above 20MB
where the first syntax does not match when the rule's counters
are above the quota,
On Wed 2000-06-07 (19:18), Poul-Henning Kamp wrote:
> It should be possible to say say
>
>ipfw deny all ip from any to any exquota any
>
> as well as:
>
>ipfw deny all ip from any to any exquota guest
How about:
ipfw quota 1 config quota 10MB (and similar conversions
On Wed, 7 Jun 2000, Poul-Henning Kamp wrote:
> >I'll disallow the name "any" for quota names. This is not exactly pretty, but
>
> Make it so that if no name is specified all apply ?
I'll code the "any" into ipfw.c. The kernel code only verifies the quota name
if the string is not empty.
-Han
In message <[EMAIL PROTECTED]>, Hans Huebner
writes:
>On Wed, 7 Jun 2000, Poul-Henning Kamp wrote:
>
>> It should be possible to say say
>>
>>ipfw deny all ip from any to any exquota any
>>
>> as well as:
>>
>>ipfw deny all ip from any to any exquota guest
>
>Do you say
On Wed, 7 Jun 2000, Poul-Henning Kamp wrote:
> It should be possible to say say
>
>ipfw deny all ip from any to any exquota any
>
> as well as:
>
>ipfw deny all ip from any to any exquota guest
Do you say that in principle you agree with the "quota action, but you want
In message <[EMAIL PROTECTED]>, Hans Huebner
writes:
>Hi there,
>
>I've made a first shot at the prepaid system I described yesterday. Citing
>the ipfw manpage:
>
> The usage of IP quotas is illustrated by the following example:
>
> First, a quota entry is set up:
>
> ifpw quot
Hi there,
I've made a first shot at the prepaid system I described yesterday. Citing
the ipfw manpage:
The usage of IP quotas is illustrated by the following example:
First, a quota entry is set up:
ifpw quota set guest quota 10 warn 9
The above rule creates
You should make the exceeding of a quota a ipfw criteria rather
than an ipfw action, that way people can deny, drop, forward or DUMMYNET
packets exceeeding the quota.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member
Hi there,
I am in need of a prepaid IP accounting scheme for FreeBSD. What I want to be
able to do is: I want to allocate a certain byte quota to an IP adress (or a
subnetwork) and have the kernel automatically block the adress as soon as the
quota has been used up, optionally generating a kern
12 matches
Mail list logo
