< Sysadmin
Revision as of 21:43, 15 April 2019 by Valoriez (Talk | contribs) (Settings for Konversation: added clarification of BNC/freenode username:password input)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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 ticket; mention your username.

BNC Configurations

You will receive a password from sysadmin. Then you can login into 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 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 as server, fill in 7778 as port.
  • fill in "yourusername:yourpassword" (without quotes) in the password field and check the SSL option (this is the username:password to BNC, not your freenode password)
  • you should not set any channels in konversation, it will join the channels you have setup in the web interface earlier.
  • if you auto-identify to nickserv, add your freenode password in your Konversation identity on Freenode, not in the connection setup

Settings for IRSSI

For the following, let $USERNAME be your username and $PASSWORD your password for Let "BNCfreenode" be the network name as set at (see previous step).

At first, check that your settings at are correct. For this, start irssi and execute the command:

/server -ssl 7778 $USERNAME/BNCfreenode:$PASSWORD

If irssi correctly connects to the BNC server and to all configured channels, we can proceed to configure irssi such that it autoconnects to the BNC server at program start. For this, open the irssi configuration file at "~/.irssi/config" and edit the following sections:


Add the following snippet to the "servers" section:

  address = "";
  chatnet = "KDE";
  port = "7778";
  autoconnect = true;
  use_ssl = "yes";
  password = "$USERNAME/BNCfreenode:$PASSWORD"; 

Add the following snippet to the "chatnets section:

KDE = { type = "IRC"; };

Note that if you set up several networks at, you must create entries for each of the networks in "servers" and "chatnets".

Now, when starting irssi the client should autoconnect to the BNC server and also to all channels that are set up at the BNC 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.

This page was last modified on 15 April 2019, at 21:43. Content is available under Creative Commons License SA 4.0 unless otherwise noted.