Disable anti-flooding in inspIRCd
How do I go about disabling anti-flooding in inspIRCd? It is only an annoyance on a private chat.
No anti-flooding modules are enabled and all flooding-limits have been set to maximum - yet it still blocks posting for example an ascii image.
Any pointers in the right direction?
irc ircd
asked May 23 '15 at 20:07
cxoucxou
137110
add a comment |
How do I go about disabling anti-flooding in inspIRCd? It is only an annoyance on a private chat.
No anti-flooding modules are enabled and all flooding-limits have been set to maximum - yet it still blocks posting for example an ascii image.
Any pointers in the right direction?
irc ircd
asked May 23 '15 at 20:07
cxoucxou
137110
add a comment |
How do I go about disabling anti-flooding in inspIRCd? It is only an annoyance on a private chat.
No anti-flooding modules are enabled and all flooding-limits have been set to maximum - yet it still blocks posting for example an ascii image.
Any pointers in the right direction?
irc ircd
asked May 23 '15 at 20:07
cxoucxou
137110
How do I go about disabling anti-flooding in inspIRCd? It is only an annoyance on a private chat.
No anti-flooding modules are enabled and all flooding-limits have been set to maximum - yet it still blocks posting for example an ascii image.
Any pointers in the right direction?
irc ircd
irc ircd
asked May 23 '15 at 20:07
cxoucxou
137110
asked May 23 '15 at 20:07
cxoucxou
137110
asked May 23 '15 at 20:07
cxoucxou
137110
asked May 23 '15 at 20:07
cxoucxou
137110
asked May 23 '15 at 20:07
cxoucxou
137110
137110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The short answer: you can't.
However:
You should also include a flood="x" line which indicates the number of
lines a user may place into their buffer at once before they are
disconnected for excess flood. This feature can not be disabled,
however it can be set to extremely high values, rendering it
effectively disabled. A recommended value is 10. A counter is
maintained for each user which is reset every 'threshold' seconds and
specifying this threshold value with threshold="X" indicates how often
the counter is reset. For example, with flood="5" and threshold="8",
the user may not send more than 5 lines in 8 secs.
(Source: https://brainbox.cc/stash/projects/INSP/repos/inspircd/browse/docs/inspircd.conf.example?at=a3491c9be4bf2c9899bde9c85da9e7d2c4fd694e)
This paragraph refers to the "connect" tag in /etc/inspircd/inspircd.conf which might look like this:
<connect allow="*" timeout="60"
flood="999999" threshold="1"
pingfreq="120"
sendq="262144" recvq="8192"
localmax="3" globalmax="3">
Unfortunately, I have not yet tried this out myself. Apparently, InspIRCd has every conceivable feature except good documentation, and having a "flood" Attribute in a "connect" tags made me assume that it refers to Connection flooding, not message flooding. So after three days of searching, I just built rate limiting into my bot.
answered 7 hours ago
KlawsKlaws
1011
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f205268%2fdisable-anti-flooding-in-inspircd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The short answer: you can't.
However:
You should also include a flood="x" line which indicates the number of
lines a user may place into their buffer at once before they are
disconnected for excess flood. This feature can not be disabled,
however it can be set to extremely high values, rendering it
effectively disabled. A recommended value is 10. A counter is
maintained for each user which is reset every 'threshold' seconds and
specifying this threshold value with threshold="X" indicates how often
the counter is reset. For example, with flood="5" and threshold="8",
the user may not send more than 5 lines in 8 secs.
(Source: https://brainbox.cc/stash/projects/INSP/repos/inspircd/browse/docs/inspircd.conf.example?at=a3491c9be4bf2c9899bde9c85da9e7d2c4fd694e)
This paragraph refers to the "connect" tag in /etc/inspircd/inspircd.conf which might look like this:
<connect allow="*" timeout="60"
flood="999999" threshold="1"
pingfreq="120"
sendq="262144" recvq="8192"
localmax="3" globalmax="3">
Unfortunately, I have not yet tried this out myself. Apparently, InspIRCd has every conceivable feature except good documentation, and having a "flood" Attribute in a "connect" tags made me assume that it refers to Connection flooding, not message flooding. So after three days of searching, I just built rate limiting into my bot.
answered 7 hours ago
KlawsKlaws
1011
add a comment |
The short answer: you can't.
However:
You should also include a flood="x" line which indicates the number of
lines a user may place into their buffer at once before they are
disconnected for excess flood. This feature can not be disabled,
however it can be set to extremely high values, rendering it
effectively disabled. A recommended value is 10. A counter is
maintained for each user which is reset every 'threshold' seconds and
specifying this threshold value with threshold="X" indicates how often
the counter is reset. For example, with flood="5" and threshold="8",
the user may not send more than 5 lines in 8 secs.
(Source: https://brainbox.cc/stash/projects/INSP/repos/inspircd/browse/docs/inspircd.conf.example?at=a3491c9be4bf2c9899bde9c85da9e7d2c4fd694e)
This paragraph refers to the "connect" tag in /etc/inspircd/inspircd.conf which might look like this:
<connect allow="*" timeout="60"
flood="999999" threshold="1"
pingfreq="120"
sendq="262144" recvq="8192"
localmax="3" globalmax="3">
Unfortunately, I have not yet tried this out myself. Apparently, InspIRCd has every conceivable feature except good documentation, and having a "flood" Attribute in a "connect" tags made me assume that it refers to Connection flooding, not message flooding. So after three days of searching, I just built rate limiting into my bot.
answered 7 hours ago
KlawsKlaws
1011
add a comment |
The short answer: you can't.
However:
You should also include a flood="x" line which indicates the number of
lines a user may place into their buffer at once before they are
disconnected for excess flood. This feature can not be disabled,
however it can be set to extremely high values, rendering it
effectively disabled. A recommended value is 10. A counter is
maintained for each user which is reset every 'threshold' seconds and
specifying this threshold value with threshold="X" indicates how often
the counter is reset. For example, with flood="5" and threshold="8",
the user may not send more than 5 lines in 8 secs.
(Source: https://brainbox.cc/stash/projects/INSP/repos/inspircd/browse/docs/inspircd.conf.example?at=a3491c9be4bf2c9899bde9c85da9e7d2c4fd694e)
This paragraph refers to the "connect" tag in /etc/inspircd/inspircd.conf which might look like this:
<connect allow="*" timeout="60"
flood="999999" threshold="1"
pingfreq="120"
sendq="262144" recvq="8192"
localmax="3" globalmax="3">
Unfortunately, I have not yet tried this out myself. Apparently, InspIRCd has every conceivable feature except good documentation, and having a "flood" Attribute in a "connect" tags made me assume that it refers to Connection flooding, not message flooding. So after three days of searching, I just built rate limiting into my bot.
answered 7 hours ago
KlawsKlaws
1011
The short answer: you can't.
However:
You should also include a flood="x" line which indicates the number of
lines a user may place into their buffer at once before they are
disconnected for excess flood. This feature can not be disabled,
however it can be set to extremely high values, rendering it
effectively disabled. A recommended value is 10. A counter is
maintained for each user which is reset every 'threshold' seconds and
specifying this threshold value with threshold="X" indicates how often
the counter is reset. For example, with flood="5" and threshold="8",
the user may not send more than 5 lines in 8 secs.
(Source: https://brainbox.cc/stash/projects/INSP/repos/inspircd/browse/docs/inspircd.conf.example?at=a3491c9be4bf2c9899bde9c85da9e7d2c4fd694e)
This paragraph refers to the "connect" tag in /etc/inspircd/inspircd.conf which might look like this:
<connect allow="*" timeout="60"
flood="999999" threshold="1"
pingfreq="120"
sendq="262144" recvq="8192"
localmax="3" globalmax="3">
Unfortunately, I have not yet tried this out myself. Apparently, InspIRCd has every conceivable feature except good documentation, and having a "flood" Attribute in a "connect" tags made me assume that it refers to Connection flooding, not message flooding. So after three days of searching, I just built rate limiting into my bot.
answered 7 hours ago
KlawsKlaws
1011
answered 7 hours ago
KlawsKlaws
1011
answered 7 hours ago
KlawsKlaws
1011
answered 7 hours ago
KlawsKlaws
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f205268%2fdisable-anti-flooding-in-inspircd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
