ZNC 1.8.0 is already at /usr/local/bin/znc on KIRE. --makeconf is valid. SSH in. It daemonizes. Screen/tmux are for irssi/weechat.
AUP: max 2 IRC connections per shell to a given network. ZNC's connection to the net counts.
makeconf
/usr/local/bin/znc --makeconf
Answer the prompts:
- Listen port — 1025–65535, not 6667. Remember it. Clients connect here (often via
bnc.kire.net). - SSL — yes if you want TLS to the bouncer. Let it write a pem if asked.
- Listen host / bind — your vhost/IP, not a random laptop. Blank = all addresses on the account (usually worse).
- Global modules — load webadmin. Load playback if you want proper buffer replay (clients that speak the playback module).
- Create an admin user, nick, altnick, ident (
identshould be your shell username unless you were told otherwise). - IRC server the bouncer should stay on. That uplink is one of your two allowed connections to that net.
ZNC writes ~/.znc/configs/znc.conf and starts.
Webadmin, playback, vhost
- Webadmin:
https://bnc.kire.net:YOURPORT/(or the host you bound) when SSL is on. Same user/pass. - Playback:
/msg *status loadmod playbackif you skipped it in makeconf. Client must support it; otherwise you just get the regular buffer. - Bind vhost: set BindHost in webadmin (user or network) to the vhost you were assigned. Allowed BindHost list is global — add the vhost there first if the user cannot select it.
Client
See Connecting your IRC client to ZNC. Host bnc.kire.net is fine (A 70.39.109.170).
Password reset: this. Restart: this. Hand-edit conf: znc.conf.