Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: concurrency (Nick Edwards)
2. Re: concurrency (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Sat, 13 Sep 2014 10:20:41 +1000
From: Nick Edwards <[email protected]>
To: Julien ?LIE <[email protected]>
Cc: [email protected]
Subject: Re: concurrency
Message-ID:
<CAMD-=vkcjzo1pe67ee-wqjs4r6b568q6a6gk1+ad3o3pmte...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 9/12/14, Julien ?LIE <[email protected]> wrote:
> Hi Nick,
>
>> So far, inn working well, but I need to do two things, firstly, limit
>> max user concurrency (8) at any given time, the closest I can find is
>> running innd with -H -X which does not sound appropriate,
>
> I believe you should do that with a Perl or Python auth hook. This
> feature has not been implemented in INN yet:
> https://inn.eyrie.org/trac/ticket/9
>
Oh, really? wow, hard to imagine inn's been around for so long without
basic features, we use IP access for our /15 , /16, and 2x /19's, we
do not use user/pass authing, we are trying to make this changeover as
transparent as we can with end users doing nothing.
Hrm, perhaps inn is not for us and we are best staying with dnews
then, my manager has already questioned why it has taken so long, he's
very relaxed with time management, else I would have been ordered to
dump inn 5 days ago, but even his patience is running dry, all these
hassles when with dnews its simple as adding into access.conf
x.x.0.0/15:read,post:::*:con=8,mb=1000,max_out=50000 _or_
*.ourdomain:read,post:::*:con=8,mb=1000,max_out=50000 _or_
* :read,post:$lookup :$lookup :*:con=8,mb=1000,max_out=50000 for
radius or pop3
inn is so so so much more complex and although free, not really a
point now since half newsmasters I talk to in past 5 years have gotten
free keys for dnews since its officially unsupported, I'm amazed since
inn has been around for about as long, it still has a very very long
way to go to being newbie-friendly.
perhaps one of reasons why usenet is dying off, admins give up, a few
I've talked to give up on inn after one or two days, but I dont like
to let things beat me LOL so I perservered
Thank you everyone for your help, I certainly learned a lot in this
past week, even if it turns out to be of no immediate use to us here,
it might be if I ever change jobs in an IPv6 only world.
Best Regards
Nik
------------------------------
Message: 2
Date: Sat, 13 Sep 2014 08:44:58 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: concurrency
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Nick,
>>> So far, inn working well, but I need to do two things, firstly, limit
>>> max user concurrency (8) at any given time, the closest I can find is
>>> running innd with -H -X which does not sound appropriate,
>>
>> I believe you should do that with a Perl or Python auth hook.
>
> Oh, really? wow, hard to imagine inn's been around for so long without
> basic features
I bet the reason is that it is very easy to do what you want to achieve
with the very efficient Perl hooks facilities INN provides.
After a few searches on Google, I found out a bit of code written by
Fr?d?ric Senault:
http://news.lacave.net/inn/auth_rate.pl
For your needs, this code should be run at access time (instead of auth
time).
He basically checks user concurrency this way:
my $oc = 0;
open(P, '/bin/ps -ax |') && do {
while(<P>) {
if(/nnrpd: (\S*)/) {
if($1 eq $attributes{hostname}) {
$oc++;
}
}
}
close(P);
};
if($oc > $MAX) {
sleep(2);
return ( '502', 'Too many connections from your host' );
}
> my manager has already questioned why it has taken so long, he's
> very relaxed with time management, else I would have been ordered to
> dump inn 5 days ago, but even his patience is running dry, all these
> hassles when with dnews its simple as adding into access.conf
[...]
> inn is so so so much more complex and although free
I confess INN is not "newbie-friendly" as you also say but on the other
hand, you can customize it and achieve pretty interesting and powerful
things with its hooks facilities (in Perl or Python).
Well, of course it implies that you know such languages, though they are
not in fact complex (see the previous Perl code).
Regarding the other dnews extensions you mention (quota, input/output
bandwidth speed...), and even the one discussed here, I see in our
inn-workers archives that we talked about them:
https://lists.isc.org/pipermail/inn-workers/2003-September/012063.html
https://lists.isc.org/pipermail/inn-workers/2000-July/003386.html
It appears that the best way to do that is the use of xinetd (or a
similar utility). You then get a few handy features for controlling
access at the TCP level and also get the advantage of any further
improvements in those programs.
"No need to reinvent the wheel." :)
> Thank you everyone for your help, I certainly learned a lot in this
> past week, even if it turns out to be of no immediate use to us here,
> it might be if I ever change jobs in an IPv6 only world.
Good luck with your projects! I am a bit sorry that INN did not fit
your needs. If only you had used the straight-forward adequate program
(like xinetd) to fulfil your expectations on user tracking and limiting,
you would have had a more pleasant experience!
--
Julien ?LIE
? Quousque tandem ? ? (Cic?ron)
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 64, Issue 9
******************************************
