You can find its source '''[https://znc.in/releases/znc-{{ZNC-Version}}.tar.gz <span style="color:#7F0000">here</span>]'''!

−

== Download ZNC {{ZNC-Version}} ==

+

Or you can try testing version, using [https://znc.in/nightly/?C=N&O=D nightly tarball] or [[Git]]{{#if:{{ZNC-Version-Alpha}}|, or '''[https://znc.in/releases/znc-{{ZNC-Version-Alpha}}.tar.gz <span style="color:#7F0000">ZNC {{ZNC-Version-Alpha}}</span>]'''|}}.

−

You can find the latest stable release '''[http://znc.in/releases/znc-{{ZNC-Version}}.tar.gz <span style="color:#7F0000">here</span>]'''!

−

Or you can try testing version, using [http://znc.in/nightly nightly tarball] or [[Git]]<!--, or '''[http://znc.in/releases/znc-1.6.0-rc1.tar.gz <span style="color:#7F0000">ZNC 1.6.0-rc1</span>]'''-->!

+

Older versions can be found [https://znc.in/releases/ here].

+

+

Several distros provide ZNC as a package, look at [[Installation]] page for details.

== How does it work? ==

== How does it work? ==

−

* Install ZNC on your server.

+

* [[Installation|Install]] ZNC on your server.

* Generate an initial configuration via <code>znc --makeconf</code>.

* Generate an initial configuration via <code>znc --makeconf</code>.

−

** (0.206 and earlier)

+

** Each ZNC user can connect to several IRC networks, though you'll need to connect your IRC client to ZNC several times (once per network).

−

*** '''For each IRC network, you need to create a ZNC user.'''

−

*** For example, use one user for Freenode, one user for EFnet, one user for Quakenet, etc.

−

** (1.0)

−

*** Each ZNC user can connect to several IRC networks, though you'll need to connect your IRC client to ZNC several times.

** You can later change settings (add more users, tune existing ones, etc.) via the [[webadmin|web interface]] or from [[controlpanel|IRC]].

** You can later change settings (add more users, tune existing ones, etc.) via the [[webadmin|web interface]] or from [[controlpanel|IRC]].

* Configure your IRC client to connect to your ZNC server.

* Configure your IRC client to connect to your ZNC server.

** If your client has separate '''username''' and '''password''' fields, that works fine.

** If your client has separate '''username''' and '''password''' fields, that works fine.

−

*** You can set ''username'' as <code>username/network</code> to connect to a specific network. The network needs to be configured already. Without <code>/network</code> client will be connected to some random network.

+

*** You can set ''username'' as <code>username@clientid/network</code> to connect to a specific network. The network needs to be configured already. Without <code>/network</code> client will be connected to some random network.

−

** If your client is broken and doesn't support specifying username in well... username, you can use <code>username/network:password</code> as the ''password''.

+

** If your client is broken and doesn't support specifying username in well... username, you can use <code>username@clientid/network:password</code> as the ''password''.

+

** The ''@clientid'' is included with ZNC starting from '''1.6.0'''. It's optional and is name that you give to your client to recognize it in <code>/msg *status listclients</code>. It's also used by some modules such as [[chanfilter]].

* Read the [[FAQ]] if you run into any problems. Feel free to ask on IRC if you need more help.

* Read the [[FAQ]] if you run into any problems. Feel free to ask on IRC if you need more help.

* Enjoy! (Profit?)

* Enjoy! (Profit?)

Line 37:

Line 37:

; Multiple Users : You can add additional users under one running process. Useful for public shells that limit background processes.

; Multiple Users : You can add additional users under one running process. Useful for public shells that limit background processes.

; Multiple Networks : Each user can connect to several IRC networks at once, with an optional limit configured by ZNC admin.

; Multiple Networks : Each user can connect to several IRC networks at once, with an optional limit configured by ZNC admin.

−

; Multiple Clients : Connect to the same user/network with as many clients as you want.

+

; [[Multiple clients|Multiple Clients]] : Connect to the same user/network with as many clients as you want.

; Playback Buffers : Stay up-to-date with what happened and when it happened while you were detached, [[timestamps]] are also printed and can be manually configured.

; Playback Buffers : Stay up-to-date with what happened and when it happened while you were detached, [[timestamps]] are also printed and can be manually configured.

; SSL Support : Encryption for both the listen port and connecting to IRC servers. If your system has OpenSSL, ZNC automatically supports SSL connections.

; SSL Support : Encryption for both the listen port and connecting to IRC servers. If your system has OpenSSL, ZNC automatically supports SSL connections.

; IPv6 Support : Both IPv4 and IPv6 address families just work, if your system supports them.

; IPv6 Support : Both IPv4 and IPv6 address families just work, if your system supports them.

−

; Partyline : Using the global [[partyline]] module, you can join channels and query users on the internal ZNC network

; Web Administration : Using the global [[webadmin]] module, admins can add/remove/edit users and global settings and non admins can edit their own user settings.

; Web Administration : Using the global [[webadmin]] module, admins can add/remove/edit users and global settings and non admins can edit their own user settings.

== Getting started ==

== Getting started ==

+

* [[Introduction]]

* [[Installation|Download and Installation]]

* [[Installation|Download and Installation]]

* [[Connecting to ZNC]]

* [[Connecting to ZNC]]

Line 52:

Line 52:

== Further Info ==

== Further Info ==

−

* [[Using ident spoofs|Setting up ident spoofs via oidentd]]

+

* [[Identfile|Setting up ident spoofs via oidentd]]

* [[Chroot]]

* [[Chroot]]

* [[ZNC Backup]]

* [[ZNC Backup]]

Line 59:

Line 59:

* [[History]]

* [[History]]

* [[Configuration|Configuration parameters]]

* [[Configuration|Configuration parameters]]

+

* [[Tor|Using with Tor]]

+

* [[Reverse proxy|Webadmin behind HTTP reverse proxy]]

* [https://github.com/znc/znc/releases.atom Subscribe to new releases]

* [https://github.com/znc/znc/releases.atom Subscribe to new releases]

Welcome to the ZNC wiki where you may find and publish information about ZNC, an advanced IRC bouncer that is left connected so an IRC client can disconnect/reconnect without losing the chat session. Feel free to update pages which you think are improvable and don't hesitate to ask for help.

How does it work?

Each ZNC user can connect to several IRC networks, though you'll need to connect your IRC client to ZNC several times (once per network).

You can later change settings (add more users, tune existing ones, etc.) via the web interface or from IRC.

Configure your IRC client to connect to your ZNC server.

If your client has separate username and password fields, that works fine.

You can set username as username@clientid/network to connect to a specific network. The network needs to be configured already. Without /network client will be connected to some random network.

If your client is broken and doesn't support specifying username in well... username, you can use username@clientid/network:password as the password.

The @clientid is included with ZNC starting from 1.6.0. It's optional and is name that you give to your client to recognize it in /msg *status listclients. It's also used by some modules such as chanfilter.

Read the FAQ if you run into any problems. Feel free to ask on IRC if you need more help.

ZNC will remain connected to IRC even while you are offline. You can then reattach later and catch up with what happened while you were gone, and your nick (and operator status) will have been kept for you.

Multiple Users

You can add additional users under one running process. Useful for public shells that limit background processes.

Multiple Networks

Each user can connect to several IRC networks at once, with an optional limit configured by ZNC admin.