<[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > These *suckers* donn't do any harmless to the system or up/download ;o) > The total load of the newssever is only 4 % for the server and takes less > than 10% of my broadband. > The problem are my feeders......they donn't like to feed servers with > privategroups hwo only can read if you have a account to this newsserver. > > I will use the server as a compromise for the bad newsserver of my ISP. > Every connection will awnser a 502.....3 connections / user. > And I think only 100 (?) userconnections at the same time. > > > servers. I suck all my personal news from free servers and my ISP, > wouldn't > > want them trying to stop me =) > > news.individual.net, free, only registration. > news.kabel-inter.net, free, only for you, 50.000 groups ;o)
I only see half a dozen groups :) > > > If I set in access.conf > > > ## BEGIN MANUAL PART2 - Anything here will be preserved > > > 0.0.0.0/16:logoff::!* > > > Then I refush access to the server for all IP's, but allso to the IP's / > > > people I trust ##protected groups and ##domains ? > > > > You would want to use 82.161.57.87/16 to block access to this IP range. > > Access rules are applied in order, later rules replace earlier rules. > > Uhhh.....## Begin manual part1 is a differend part with his own rules or > take the rules in this part also effect on part2 ? The rules should be thought of as being applied in order from top to bottom, irrespective of which section they are in. The rules at the top can change the behaviour of later rules, depending on how the rules are written, and which IP/user/groups they apply to. Provided you don't edit the files within software, you can place the rules anywhere that is sensible. Generally you set default rules at the top (such as logoff), and user-specific access rules at the bottom. - Roydon L.
