💾 Archived View for dimension.sh › ~novaburst › 3eh0rp.gmi captured on 2023-01-29 at 15:53:57. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

IRC (Dis)services are insane

Authors: Aoi Koizumi <novaburst@dimension.sh>

Date: 23 Jul, 2022

As kind of one of my last tests on the IRCNow Bootcamp, I've finally

decided to attach an IRC services package to the IRCd I'm running, which

on this case is Bahamut IRCd, instead of ngIRCd, and using Atheme,

instead of Anope. But it doesn't end there...

kyokoIRC -- | kyoko.nsupdate.info: *** Routing -- from

kyoko.nsupdate.info: Connection to kyokoproject.services activated.

kyokoIRC -- | kyoko.nsupdate.info: *** Routing -- from

kyokoproject.services: Error -- Closing Link: 0.0.0.0 (No Connect block)

kyokoIRC -- | kyoko.nsupdate.info: *** Routing -- from

kyoko.nsupdate.info: Connect error to kyokoproject.services (Connection

reset by peer)

Linking issues opened the door to Hell, and it took me an hour or

something to get it right, I hope. These are the things I did, mostly on

the IRCd side:

Listen to port 16667 exclusively for services
Add a Connect block to the configuration file
Add a U-Line block to said file

And when I thought everything was lost, I sort of realized what I did

wrong, there were some missing details on Atheme and the aforementioned

daemon, so I went to do this:

Use port 16667 instead of 6667 because the latter is for regular

clients

Place an Allow block for servers

and that's pretty much what I sort of did.

A while ago, I was getting this on my client:

kyokoIRC -- | kyoko.nsupdate.info: *** Routing -- from

kyoko.nsupdate.info: Connection to kyokoproject.services activated.

kyokoIRC -- | kyoko.nsupdate.info: *** Notice -- Host

akoizumi.host.thunderirc.net unknown

21:22:44 kyokoIRC -- | kyoko.nsupdate.info: *** Routing -- from

kyoko.nsupdate.info: Connection to kyokoproject.services activated.

There was some hope sort of, of course I had to change the hostname on

the field to an IP (0.0.0.0), and now I'm waiting for news.

-- snip --

Anope 2.0.11, build #2, compiled 13:01:41 Jul 23 2022, flags D

Using configuration file conf/services.conf

Attempting to connect to uplink #1 127.0.0.1 (127.0.0.1/16667) with protocol Bahamut 1.8.x

Successfully connected to uplink #1 127.0.0.1:16667

Lost connection from uplink #1 (127.0.0.1:16667)

Check that you are not connecting Anope to an SSL enabled port without configuring SSL in Anope (or vice versa)

This explains itself, not gonna bother debugging this one.

-- snip --

Is this what I get for not going with the majority? If so, damn it, just

fuck off.