Sysadmin/BNC

Sysadmin maintains an IRC Bouncer (BNC) for all registered KDE developers. The software used for this bouncer is ZNC. The advantage of using a bouncer is that you can see what happened on a channel when you are not connected to it.

You can request an account via a sysadmin bugreport; mention your identity.kde.org username.

BNC Configurations

You will receive a password from sysadmin. Then you can login into https://bnc.kde.org:7778/ and configure the bouncer. Most of the settings are straightforward or explained in the user interface. Some nice settings are:

• add the freenode network, and configure the channels that you want to join (use the form irc.freenode.net port #. All freenode servers listen on ports 6665, 6666, 6667, 6697 (SSL only), 7000 (SSL only), 7070 (SSL only), 8000, 8001 and 8002).
• for each channel set the buffercount, this is the amount of lines you would like to see replayed when you connect.

Connect your client to the BNC

It's time to connect to your IRC client to the bouncer.

Settings for Konversation

You would need the following settings in Konversation:

• add a new network, called KDE, connect at the start
• add a new server to the network, use bnc.kde.org as server, fill in 7778 as port.
• fill in "yourusername:yourpassword" (without quotes) in the password field and check the SSL option.
• you should not set any channels in konversation, it will join the channels you have setup in the web interface earlier.

Settings for IRSSI

For the following, let $USERNAME be your bnc.kde.org username and $PASSWORD your password for bnc.kde.org. And we assume that you called the created network "BNCfreenode".

First, let us check that your settings at bnc.kde.org are correct. For this, start irssi and execute the command: /server -ssl bnc.kde.org 7778 $USERNAME/BNCfreenode:$PASSWORD

If this connects correctly to the BNC server and the channels, we can proceed with configuring irssi to autoconnect to the BNC sever. Open the configuration at "~/.irssi/config" and edit the following sections:

Servers

Add the following snippet to the "servers" section:

{
  address = "bnc.kde.org";
  chatnet = "BNCfreenode";
  port = "7778";
  autoconnect = true;
  use_ssl = "yes";
  password = "$USERNAME/BNCfreenode:$PASSWORD"; 
}

Chatnets

Add the following to the "chatnets section:

BNCfreenode = { type = "IRC"; };

Now starting irssi, the client should connect to the BNC server and also all channels that are set up at the web frontend.

Configure Identify

Now you need to configure to identify to the freenode network properly.

• don't use znc's 'nickserv' module. This only identifies after the connection, which means you will join the channels uncloaked first and only later get your cloak. Another reason is that some channels might be shielded based on your cloak, autojoining channels won't work. Better is to use the sasl module. This identifies you directly at the moment of the connection.
• after you are connected issue '/msg *status loadmod sasl'
• after that issue '/msg *sasl set primarynick freenodepassword'. Replace primarynick with the primary nick you once registered at nickserv and replace 'freenodepassword' is the password you set to protect your nick. This is not (and should not) be the same as the username and password you use for the znc web interface.