IRC Bouncer
Configuration
The IRC bouncer, since September 2026, has moved from ZNC to soju, meaning there is no longer any web configuration. Configuration can instead be done inside of IRC itself by connecting to the bouncer and then issuing commands to BouncerServ (which can be messaged with /msg BouncerServ [MESSAGE]). See documentation of the commands on the soju manpage here.
Logging In
The bouncer runs on shell.lug.mtu.edu:6697, which is the default port for IRC over TLS. We do not support plaintext IRC, you need to use TLS.
Bouncer logins are done through PAM, so your shell account credentials should work for authentication. As for how you log in, that's specific to your client. Check your client's documentation for how to do SASL authentication.
IRC Information
Nickname is the username that will be on IRC. This is not what you log in to, but this is what others will see.
The other IRC information is not really useful. Just choose an alternative nickname in case someone is trying to impersonate you: register your account to prevent this.
Networks
You can add networks with /msg BouncerServ network create -addr [address] -name [network name]. Note that there are more options than this that can be see with /msg BouncerServ help network create. This will be important if, for example, you needed to log in to an external network with a password (Libera Chat does this!).
The traditional way to determine your network through the bouncer is to log in with your name as [name]/[network]. This is not necessary with soju! If your client supports the bouncer-networks IRCv3 extension, you can just log in normally and your client will detect the networks that soju is watching automatically.
Channels
Channels should be added automatically upon joining them through the bouncer. They can also be added manually through /msg BouncerServ channel create [channel]/[network]. These are the channels that the bouncer will actively watch and log messages from.