- DALnet-src - nomad.dal.net

Help disabling throttling
by Hunter, Brett E CIV COMPACFLT, N63 11 Sep '17

11 Sep '17

Hi, We are running Bahamut 2.0.7 on our network and we have had issues with the throttling. Our servers are very busy and we have lots of users connecting from the same IP due to firewall NAT going on. Right now we have to set the throttle settings for our servers after each restart. We would like to recompile Bahamut and disable throttling. I tried modifying the config.h file to change "#DEFINE THROTTLE_ENABLE" to "#UNDEF THROTTLE_ENABLE" and tried to recompile the software. However, I received errors during compilation such as: ***/src/m_webirc.c: 127: undefined reference to `throttle_check' ** /rc/m_webirc.c: 82 : undefined reference to `throttle_remove' I was wonder what is best way to disable throttling ? Any assistance at all will be appreciated. Brett

2 4

Re: DALnet-src Digest, Vol 57, Issue 1
by Tatag Danang SN 29 Aug '17

29 Aug '17

can you check on https://github.com/epiphani/bahamut/blob/master/doc/reference.conf ? you can find how to disableing throttling there. # m Enable operator hostmasking # C Bypass clone limiting # F Force umode +F to bypass message flood checks # T Disable rapid (re)connection throttling regards On Mon, Aug 28, 2017 at 2:00 AM, <dalnet-src-request(a)lists.dal.net> wrote: > Send DALnet-src mailing list submissions to > dalnet-src(a)lists.dal.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.dal.net/mailman/listinfo/dalnet-src > or, via email, send a message with subject or body 'help' to > dalnet-src-request(a)lists.dal.net > > You can reach the person managing the list at > dalnet-src-owner(a)lists.dal.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of DALnet-src digest..." > > > Today's Topics: > > 1. Help disabling throttling (Hunter, Brett E CIV COMPACFLT, N63) > 2. Re: Help disabling throttling (Jimmy Hess) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 30 Jun 2017 02:28:24 +0000 > From: "Hunter, Brett E CIV COMPACFLT, N63" <brett.hunter(a)navy.mil> > Subject: [DALnet-src] Help disabling throttling > To: "dalnet-src(a)dal.net" <dalnet-src(a)dal.net> > Cc: "bhunter(a)hawaii.rr.com" <bhunter(a)hawaii.rr.com> > Message-ID: > <A4B3EB109C17834F9E3810451F932B302B7BD7E8@NAWEPRLHXM03V. > nadsuswe.nads.navy.mil> > > Content-Type: text/plain; charset="us-ascii" > > Hi, > We are running Bahamut 2.0.7 on our network and we have had issues > with the throttling. Our servers are very busy and we have lots of users > connecting from the same IP due to firewall NAT going on. Right now we have > to set the throttle settings for our servers after each restart. > We would like to recompile Bahamut and disable throttling. I tried > modifying the config.h file to change "#DEFINE THROTTLE_ENABLE" to "#UNDEF > THROTTLE_ENABLE" and tried to recompile the software. However, I received > errors during compilation such as: > > ***/src/m_webirc.c: 127: undefined reference to `throttle_check' > ** /rc/m_webirc.c: 82 : undefined reference to `throttle_remove' > > I was wonder what is best way to disable throttling ? > > Any assistance at all will be appreciated. > > Brett >

2 1

Suggestion!
by fahadmehar＠hushmail.com 12 Jun '16

12 Jun '16

Dear DALnet ! I have suggestion like we before use to add description on our nick whois. /ns set URL "desc here" Now we no longer add desc instead we only allow to add URL... Please give us back old desc settings. Thank you... Regards.

1 0

IRCd /oper auto join issue
by SuperGod 12 Feb '16

12 Feb '16

Hey, I have some technical question. I'm running small IRC server, I have oper there. Could you tell me what is causing that using "/oper nick password" command force me to join to some channel? I can't find anything in a config files. So I thought I'll ask the other admins. :) Any clue? I'll apprecie any help. Regards.

1 0

Re: s_err.c: Standardize 256 (RPL_ADMINME) with RFC 1459
by Juuso Lapinlampi 29 Dec '15

29 Dec '15

> Thanks Juuso - beyond the RFC issue, have you run into any cases of > this causing problems with clients? Hi Aaron. Let's assume this is the raw conversation, compliant with RFC 1459: ADMIN :irc.se.partyvan.eu 256 * irc.se.partyvan.eu :Administrative info :irc.se.partyvan.eu 257 * :Stockholm, Sweden :irc.se.partyvan.eu 258 * :Partyvan NOC :irc.se.partyvan.eu 259 * :noc@partyvan.eu I've tested this a little and so far found a minor regression with weechat 1.3: -- | irc.se.partyvan.eu :Administrative info -- | Stockholm, Sweden -- | Partyvan NOC -- | noc(a)partyvan.eu I've heard ZNC also has the same little regression: * irc.se.partyvan.eu :Administrative info * Stockholm, Sweden * Partyvan NOC * noc(a)partyvan.eu irssi 0.8.17 works perfectly fine! 15:03 -!- irc.se.partyvan.eu Administrative info 15:03 -!- Stockholm, Sweden 15:03 -!- Partyvan NOC 15:03 -!- noc(a)partyvan.eu I've not tested with HexChat, XChat or other IRC clients yet, but I'm interested to hear about them too. I intend to send patches to IRC client developers for major IRC clients which do not follow the RFC syntax, but I've not yet had time to do so. Of course, it would be interesting to get every IRC client and server closer to the standards and help with future adaptation for a new, up to date IRC standard (IRCv3? Harmony?). For what it's worth, this is the progress on different IRC server daemons: - Charybdis: Merged (e0160ec5a4cbd855751571824a0dbf93aae29790) - nefarious2: Merged (5dce7c3a7c1e08b4d68de78a764af83d6e217375) - InspIRCd: Intent to merge (after fixing a parameter issue) - UnrealIRCd: wontfix (bug tracker #4519) - Bahamut: You are here Other IRCds I've not yet looked into, but will try to do so tomorrow. DBoyz also did some testing before anything was merged. It seems different IRCds use(d) different non-standard 256 replies: bahamut-2.0.7 <- :arcor.de.eu.dal.net 256 DBoyz :Administrative info about arcor.de.eu.dal.net charybdis-3.5.0-rc1 <- :irc-us3.alphachat.net 256 DBoyz :Administrative info about irc-us3.alphachat.net InspIRCd-2.0 <- :lazer.techtronix.net 256 DBoyz :Administrative info for lazer.techtronix.net u2.10.12.14+Nefarious(2.0.0) <- :Baltimore.MD.US.ExileNET.Org 256 DBoyz :Administrative info about Baltimore.MD.US.ExileNET.Org UnrealIRCd-4.0.0 <- :irc.blockah.com 256 DBoyz :Administrative info about irc.blockah.com I also checked the CVS history of Undernet's ircu. The non-standard "Administrative info about <server>" string has been there since the initial commit in year 1999 - so I found no reason why they would have changed it away from the standard.

1 0

s_err.c: Standardize 256 (RPL_ADMINME) with RFC 1459
by Juuso Lapinlampi 29 Dec '15

29 Dec '15

>From d412ebf6feea74cdd5ff02a7921b1d4807c2c983 Mon Sep 17 00:00:00 2001 From: Juuso Lapinlampi <wub(a)partyvan.eu> Date: Tue, 29 Dec 2015 04:34:38 +0000 Subject: [PATCH 1/1] s_err.c: Standardize 256 (RPL_ADMINME) with RFC 1459 RPL_ADMINME is a response the client receives using the ADMIN command. Bahamut used to implement a non-standard version of this. The RFC 1459 standard [1] says in section "6.2 Command responses.": 256 RPL_ADMINME "<server> :Administrative info" This commit corrects the behavior to follow the standard. [1]: https://tools.ietf.org/html/rfc1459 --- src/s_err.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/s_err.c b/src/s_err.c index 075e172..073a7ba 100644 --- a/src/s_err.c +++ b/src/s_err.c @@ -280,7 +280,7 @@ static char *replies[] = /* 253 RPL_LUSERUNKNOWN */ ":%s 253 %s %d :unknown connection(s)", /* 254 RPL_LUSERCHANNELS */ ":%s 254 %s %d :channels formed", /* 255 RPL_LUSERME */ ":%s 255 %s :I have %d clients and %d servers", - /* 256 RPL_ADMINME */ ":%s 256 %s :Administrative info about %s", + /* 256 RPL_ADMINME */ ":%s 256 %s %s :Administrative info", /* 257 RPL_ADMINLOC1 */ ":%s 257 %s :%s", /* 258 RPL_ADMINLOC2 */ ":%s 258 %s :%s", /* 259 RPL_ADMINEMAIL */ ":%s 259 %s :%s", -- 2.6.4

2 1

Re: DALnet-src Digest, Vol 54, Issue 1
by mirckid . 16 Dec '15

16 Dec '15

thanks for contact DALnet-src, for frozen nick please use DALnet contact form at https://users.dal.net/karnaf/new.php or email the services abuse at sabuse(a)dal.net best regards On Wed, Dec 2, 2015 at 3:00 AM, <dalnet-src-request(a)lists.dal.net> wrote: > Send DALnet-src mailing list submissions to > dalnet-src(a)lists.dal.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.dal.net/mailman/listinfo/dalnet-src > or, via email, send a message with subject or body 'help' to > dalnet-src-request(a)lists.dal.net > > You can reach the person managing the list at > dalnet-src-owner(a)lists.dal.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of DALnet-src digest..." > > > Today's Topics: > > 1. [SPAM] My Nick is Frozen (Syed Adnan Shah) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 29 Nov 2015 18:59:21 +0000 (UTC) > From: Syed Adnan Shah <shahsyedadnan(a)yahoo.com> > Subject: [DALnet-src] [SPAM] My Nick is Frozen > To: "dalnet(a)dal.net" <dalnet(a)dal.net>, "dalnet-services(a)dal.net" > <dalnet-services(a)dal.net>, "dalnet-src(a)dal.net" < > dalnet-src(a)dal.net> > Message-ID: > <2104143256.11264427.1448823561788.JavaMail.yahoo(a)mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Skipped content of type multipart/alternative-------------- next part > -------------- > Spam detection software, running on the system "momomail.dal.net", has > identified this incoming email as possible spam. The original message > has been attached to this so you can view it (if it isn't spam) or label > similar future email. If you have any questions, see > the administrator of that system for details. > > Content preview: Dear Sir/Ma'am!with due respect it is submitted that I m > regular > , permanent registered user of prestigious network i.e. DAL.NET with > nick > "Moody__Chatter" but from some days i am not signing in /login and > message > is received Â that your nick is frozen , abuse. Respected Senior, kindly > inform me what is the problem and what is the fault on my part i shall > improve > my deficiencies. ThanksÂ [...] > > Content analysis details: (5.6 points, 5.0 required) > > pts rule name description > ---- ---------------------- > -------------------------------------------------- > 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail > provider > (jbarik113[at]gmail.com) > (deception767[at]att.net) > (pintrill[at]gmail.com) > (shahsyedadnan[at]yahoo.com) > (shahsyedadnan[at]yahoo.com) > (shahsyedadnan[at]yahoo.com) > 0.8 SPF_NEUTRAL SPF: sender does not match SPF record (neutral) > 1.6 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' > headers > 2.0 DEAR_SOMETHING BODY: Contains 'Dear (something)' > -0.5 CUSTOM_IRC_DOWNSCORE BODY: dal.net IRC custom word whitelist > 0.0 HTML_MESSAGE BODY: HTML included in message > 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% > [score: 0.5000] > -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from > author's > domain > 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not > necessarily valid > -0.1 DKIM_VALID Message has at least one valid DKIM or DK > signature > 1.0 RDNS_DYNAMIC Delivered to internal network by host with > dynamic-looking rDNS > > > > ------------------------------ > > _______________________________________________ > DALnet-src mailing list > DALnet-src(a)lists.dal.net > https://lists.dal.net/mailman/listinfo/dalnet-src > > > End of DALnet-src Digest, Vol 54, Issue 1 > ***************************************** > -- ervan @ DALnet

1 0

[SPAM] My Nick is Frozen
by Syed Adnan Shah 29 Nov '15

29 Nov '15

Dear Sir/Ma'am!with due respect it is submitted that I m regular , permanent registered user of prestigious network i.e. DAL.NET with nick "Moody__Chatter" but from some days i am not signing in /login and message is received that your nick is frozen , abuse. Respected Senior, kindly inform me what is the problem and what is the fault on my part i shall improve my deficiencies. Thanks Spam detection software, running on the system "momomail.dal.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Dear Sir/Ma'am!with due respect it is submitted that I m regular , permanent registered user of prestigious network i.e. DAL.NET with nick "Moody__Chatter" but from some days i am not signing in /login and message is received Â that your nick is frozen , abuse. Respected Senior, kindly inform me what is the problem and what is the fault on my part i shall improve my deficiencies. ThanksÂ [...] Content analysis details: (5.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jbarik113[at]gmail.com) (deception767[at]att.net) (pintrill[at]gmail.com) (shahsyedadnan[at]yahoo.com) (shahsyedadnan[at]yahoo.com) (shahsyedadnan[at]yahoo.com) 0.8 SPF_NEUTRAL SPF: sender does not match SPF record (neutral) 1.6 FORGED_YAHOO_RCVD 'From' yahoo.com does not match 'Received' headers 2.0 DEAR_SOMETHING BODY: Contains 'Dear (something)' -0.5 CUSTOM_IRC_DOWNSCORE BODY: dal.net IRC custom word whitelist 0.0 HTML_MESSAGE BODY: HTML included in message 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 1.0 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS

1 0

Hi. I've created a pull request on Epiphani's github for bahamut.
by Janice Johnson 21 Aug '15

21 Aug '15

This pull request is meant to add SSL server-to-server link encryption to Bahamut. I just thought it would be useful.

1 0

Pull Request: Channel Mode +T
by Daniel Tan 06 Jun '15

06 Jun '15

Hi all, Upon enduring endless occasions of NOTICE floods in channels, I hereby propose a new channel mode +T as a more effective mitigation tool for channel ops compared to traditional methods (i.e. channel mode +m or +M). Channel mode +T would block non voice or non ops from sending NOTICEs to the channel thus eliminating the necessity to enable the moderation mode. The codes to introduce this new channel mode +T is now available for viewing at Bahamut's Repository at PR #15. I highly appreciate you to review and please feel free to place comments on the PR itself. Thank you. Regards, DBoyz/Daniel

5 5