Hi there people,
i really didn't want to make a thread but i have searched google and read through several pages of documentation.
Still can't find a solution to what i want to do.
Basically i have a bot on my server that likes to SPEW lots of information (which is fine it's what i want)
but the server doesn't like it.
for example:
*** Flood -- TOOLMAN![email protected] (9120) exceeds 8000 recvQ
then it connects straight after and carrys on, but just annoys me that it leaves for a couple of seconds.
-Thanks everyone!
How to make a client exempt from flood control?
Re: How to make a client exempt from flood control?
Click the configuration link in my signature and read about class blocks and allow blocks.
Configuration - https://www.unrealircd.org/docs/Configuration
FAQ - https://www.unrealircd.org/docs/FAQ
FAQ - https://www.unrealircd.org/docs/FAQ
Re: How to make a client exempt from flood control?
thank you for reply,
i have already read this, but i may understand it wrong.
as it states 8000 is the highest, so i don't see how i can exempt a person, doesn't seem to be a option for this.
i have already read this, but i may understand it wrong.
as it states 8000 is the highest, so i don't see how i can exempt a person, doesn't seem to be a option for this.
-
- Head of Support
- Posts: 2085
- Joined: Tue Jun 15, 2004 8:50 pm
- Location: Chino Hills, CA, US
- Contact:
Re: How to make a client exempt from flood control?
The documentation says the default is 8000, you can make the value as high as you want.
The way you exempt 1 person is you make an allow block AFTER your normal allow block to put them into a different class. In the different class is where you may specify the higher recvq limit.
Your allow/class blocks should be in this order in the conf:
The way you exempt 1 person is you make an allow block AFTER your normal allow block to put them into a different class. In the different class is where you may specify the higher recvq limit.
Your allow/class blocks should be in this order in the conf:
- allow block for *@* (everyone)
- allow block for the client you wish to exempt - note to specify BOTH IP and host for your bot!
- class block for normal people
- class block for your bot
Re: How to make a client exempt from flood control?
ok thanks for the help..
i have setup the following, but it seems when people are now connecting. they are all connecting as bots. for example;
*** Notice -- Client connecting on port 7000: mrman ([email protected]) [bots] [secure AES256-SHA]
shouldn't the [bots] bit be client?
i have setup the following, but it seems when people are now connecting. they are all connecting as bots. for example;
*** Notice -- Client connecting on port 7000: mrman ([email protected]) [bots] [secure AES256-SHA]
shouldn't the [bots] bit be client?
Code: Select all
class clients
{
pingfreq 90;
maxclients 500;
sendq 100000;
recvq 8000;
};
class bots
{
pingfreq 60;
maxclients 20;
sendq 100000;
recvq 32000;
};
Code: Select all
allow {
ip *@*;
hostname *@*;
class clients;
maxperip 5;
password "RANDOMTXT" { md5; };
};
allow {
ip *@222.22.222.222;
hostname *@*;
class bots;
maxperip 5;
};
Re: How to make a client exempt from flood control?
No.tetrix wrote:shouldn't the [bots] bit be client?
Firstly:
So to solve this see:unreal32docs.html#allowblock wrote:The access control works like this: ip matches OR host matches, so "hostname *@*"; and "ip *@1.2.3.4" will mean it will always match.
Secondly the allow block you have that uses the clients class will ONLY put clients in the clients class IF they supply the correct password at connect.unreal32docs.html#allowblock wrote:Additionally, if you want to setup a block that only matches based on IP, then set the hostname to something invalid, such as "hostname NOBODY;", this will allow the block to only match based on IP.
Your IP:
Your Country:
Your Country:
Re: How to make a client exempt from flood control?
ok ive now enetered a HOST as well as the IP. surely this would mean it will only allow that one bot to connect through that allow line.
*fingures crossed seems to be working.
*fingures crossed seems to be working.