Archive for August, 2018

hanbot's ZNC bouncer notes

Friday, August 31st, 2018

My current ISP, cavalcade of dipshits that they are, has taken to peppering my daily routine with disconnects, making an IRC bouncer necessary in the stew of damage control on my stove1.

ZNC's installation and initial configuration processes are painless enough. Make yourself a dir, cd into it, and grab source:


curl -s https://znc.in/releases/znc-1.7.1.tar.gz -o znc-1.7.1.tar.gz

Unpack, cmake, and install:


tar -xzvf znc-1.7.1.tar.gz
cd znc-1.7.1
cmake -DCMAKE_INSTALL_PREFIX="$HOME/where/you/want/it" -DOPENSSL_ROOT_DIR=/usr/bin2
make
make install

Then create a config file by specifying the full path of your installation in the prefix above followed by --makeconf . ZNC's docs suggest znc --makeconf alone will do this; ten wasted minutes of my life suggest otherwise.

You'll have to pick a port for ZNC to listen on among the prompts that follow. Otherwise, default options've proven fine for me. Launch ZNC when prompted at the end of the configuration dialogue.

Now all that's squared away, official docs and search result flotsam step in with the true timewasting bullshit of dropping anything resembling actionable steps, sense, or the English fucking language. All IRC users are also goats of the same age and gender, right? No need to declare antecedents for "the" password, just dandy to specify "server" password in some forms but not others, certainly no problem to be explicit to the degree of telling folks to cd to a fucking directory but neglecting to mention which network components need what information, and where.

So then, first tell ZNC where you want it to connect via the same's webadmin. Point your browser to http://your.server's.ip:portyouspecified/ . Log in, mosey to "Your settings" on the right-hand menu, and add a network with irc.freenode.net, port 6697. Check the SSL box. Put something you like in the "network name" field up top. Hit "save and return" at the very bottom of the page.

Now, tell your IRC client how to connect to ZNC. I used xchat, where this stuff is accessed under xchat/network list. Click "Add", highlight the stupid default server name that pops up, and enter your.ZNC.server's.ip:portyouspecified . Yes, the separator shows in established server details as a forward slash. Yes, the syntax is actually a forward slash. No, entering the same forward slash will not fucking work, it'll overwrite what you entered with the original default bullshit. Give it a colon; it'll convert it into a forward slash on return. This shit's so enraging they ought to market it as a depilation treatment.

Anyway, in the User name field, enter your ZNC admin name, forward slash (no kidding, it works on its own now), network name from the ZNC webadmin network settings (that very same something you like). The server password is the same as your ZNC webadmin password. Feed it your Nickserv password if it makes you happy. Close the dialogue and connect.

***

  1. Shitty mixed metaphors brought to you by hours of enraged wrangling; may this guide spare you similar emissions. []
  2. This is the Pizarro shared box's openssl path at the time of this writing, change as needed. []