Anope + Bahamut

[ghost]

Thank You very much for the Anope IRC services. I just installed the latest release of both Anope and Bahamut IRCD and it pretty much went seamless, without a hitch. After firing it up, I had one little glitch connecting with the client, but it was in the default ircd.conf where the connection listen block had bind lines added to the ports. After removing those, the whole setup purrs like a kitten. Thank You for the work, you put into this!!

[TehPeGaSuS]

Please, be aware that Bahamut was removed from the list of compatible IRCds on the upcoming 2.1 branch, with this commit.

I strongly suggest you to choose another IRCd, such as UnrealIRCd or InspIRCd, if you really want to keep going forward with your project. Those IRCds are much more featureful and have much more protections than Bahamut.

Cheers!

[TehPeGaSuS]

I'm not saying that Bahamut is broken but I'm not saying that it isn't broken.

Also, NickServ, ChanServ are Anope features and not really stuff provided by the IRCd itself.

Regarding the modern features, I'm talking about native DNSBL (DroneBL, etc), flood protections, etc.

IRCds, like UnrealIRCd or InspIRCd, focus on providing more tools and features that can used by admins/users to fight against misbehaving users, such as spammers, etc.

[sadiepowell]

Bahamut support was dropped in 2.1 (2.0 still supports it) because according to the IRCStats data it has almost zero users other than DALnet (who don't use Anope). If you want a similarly basic IRCd then you might wish to try ngircd.

[TehPeGaSuS]

did you do /os login Thunder <password> where password is the one you've specified on the Anope oper block?

Because you're requiring two layers of oper:

1. /oper <nick> <password> (to become IRCd oper)
2. /os login <nick> <password> (to become Anope oper)

If you don't want to have have to /os login, then remove the password on the Anope oper block.

[ghost]

[sadiepowell]

Check your log file and there should be more details as to why it was rejected.

[ghost]

Ya, all we got with log was (non-oper) for a reason, but no big deal. I added my two friends to the oper blocks in ircd conf and everything is running great now. All 3 of us have operserv access, with no issues. Got the server, website and forums up and running now. Thank You for your help. It's a lot easier now, than back when I was doing this stuff with BSD, but I've been a Debian fan for last 10 years, haha
www.chatnet.ca
forums.chatnet.ca
irc.chatnet.ca

[TehPeGaSuS]

But so far, as it turns out, anyone who is not in the ircd conf, can't get access to /operserv even though they are configured for it in the services conf. Even myself, if I don't FIRST /oper into ircd, then I have no access to /operserv commands.

That's exactly what's expected to happen. Anope oper blocks require a registered nickname and also need an IRCd oper block unless you have require_oper = no on their Anope oper block (something I strongly advise against).

[ghost]

Yes, Thank You TehPeGaSuS. That was the overall thing that wasn't clicking with me, previously, but I don't mind the security aspect of it. It's just a matter of "non-lazy" fingers having to enter 3 different passwords. (one for nick, one for oper and one for operserv). Sucks to be them, haha

[TehPeGaSuS]

I mean, you can automate that all in your IRC client if you know how to. You can even use oper auto-login on UnrealIRCd (via certfp, account, etc).

You should definitely visit #unreal-support at irc.unrealircd.org if you need help further configuring or tweaking UnrealIRCd configuration. :D