2 .\" $Id: ngircd.conf.5.tmpl,v 1.7 2007/11/23 16:26:03 fw Exp $
4 .TH ngircd.conf 5 "May 2008" ngircd "ngIRCd Manual"
6 ngircd.conf \- configuration file of ngIRCd
8 .B :ETCDIR:/ngircd.conf
11 is the configuration file of the
13 Internet Relay Chat (IRC) daemon which you should adept to your local
14 preferences and needs.
16 The file consists of sections and parameters. A section begins with the name
17 of the section in square brackets and continues until the next section
20 Sections contain parameters of the form
28 Empty lines and any line beginning with a semicolon (';') or a hash ('#')
29 character are treated as a comment and will be ignored. Leading and trailing
30 whitespaces are trimmed before any processing takes place.
32 The file format is line-based - that means, each non-empty newline-terminated
33 line represents either a comment, a section name, or a parameter.
35 Section and parameter names are not case sensitive.
36 .SH "SECTION OVERVIEW"
37 The file can contain blocks of four types: [Global], [Operator], [Server],
40 The main configuration of the server is stored in the
42 section, like the server name, administrative information and the
43 ports on which the server should be listening. IRC operators of this
48 is the section where server links are configured. And
50 blocks are used to configure pre-defined ("persistent") IRC channels.
52 There can be more than one [Operator], [Server] and [Channel] sections
53 per configuration file, but only one [Global] section.
57 section is used to define the server main configuration, like the server
58 name and the ports on which the server should be listening.
61 Server name in the IRC network, must contain at least one dot (".").
64 Info text of the server. This will be shown by WHOIS and LINKS requests for
67 \fBAdminInfo1\fR, \fBAdminInfo2\fR, \fBAdminEMail\fR
68 Information about the server and the administrator, used by the ADMIN
72 Ports on which the server should listen. There may be more than one port,
73 separated with ','. Default: 6667.
76 Same as \fBPorts\fR , except that ngircd will expect incoming connections
77 to be SSL/TLS encrypted. Default: None
80 Filename of SSL Server Key to be used for SSL connections. This is required for
83 \fBSSLKeyFilePassword\fR
84 (OpenSSL only:) Password to decrypt private key.
87 Certificate of the private key
90 Name of the Diffie-Hellman Parameter file. Can be created with gnutls "certtool --generate-dh-params" or "openssl dhparam".
91 If this file is not present, it will be generated on startup when ngircd
92 was compiled with gnutls support (this may take some time). If ngircd
93 was compiled with OpenSSL, then (Ephemeral)-Diffie-Hellman Key Exchanges and several
94 Cipher Suites will not be available.
97 A comma seperated list of IP address on which the server should listen.
98 If unset, the defaults value is "0.0.0.0", or, if ngircd was compiled
99 with IPv6 support, "::,0.0.0.0", so the server listens on all configured
100 IP addresses and interfaces by default.
103 Text file with the "message of the day" (MOTD). This message will be shown
104 to all users connecting to the server.
107 A simple Phrase (<256 chars) if you don't want to use a MOTD file.
108 If it is set no MotdFile will be read at all which can be handy if the
109 daemon should run inside a chroot directory.
112 User ID under which the server should run; you can use the name of the user
118 For this to work the server must have been
119 started with root privileges! In addition, the configuration and MOTD files
120 must be readable by this user, otherwise RESTART and REHASH won't work!
124 Group ID under which the ngIRCd should run; you can use the name of the
125 group or the numerical ID.
130 For this to work the server must have
131 been started with root privileges!
135 A directory to chroot in when everything is initialized. It doesn't need
136 to be populated if ngIRCd is compiled as a static binary. By default ngIRCd
137 won't use the chroot() feature.
142 For this to work the server must have
143 been started with root privileges!
147 This tells ngIRCd to write its current process ID to a file. Note that the
148 pidfile is written AFTER chroot and switching the user ID, i. e. the
149 directory the pidfile resides in must be writeable by the ngIRCd user and
150 exist in the chroot directory (if configured, see above).
154 After <PingTimeout> seconds of inactivity the server will send a PING to
155 the peer to test whether it is alive or not. Default: 120.
158 If a client fails to answer a PING with a PONG within <PongTimeout>
159 seconds, it will be disconnected by the server. Default: 20.
162 The server tries every <ConnectRetry> seconds to establish a link to not yet
163 (or no longer) connected servers. Default: 60.
166 Should IRC Operators be allowed to use the MODE command even if they are
167 not(!) channel-operators? Default: no.
170 If OperCanUseMode is enabled, this may lead the compatibility problems with
171 Servers that run the ircd-irc2 Software. This Option "masks" mode requests
172 by non-chanops as if they were coming from the server. Default: no.
174 \fBPredefChannelsOnly\fR
175 If enabled, no new channels can be created. Useful if
176 you do not want to have channels other than those defined in
181 If enabled, ngircd will not make DNS lookups when clients connect.
182 If you configure ngircd to connect to other servers, ngircd may still
183 perform a DNS lookup if required.
187 Set this to no if you do not want ngircd to connect to other irc servers using ipv4.
188 This allows use of ngircd in ipv6-only setups.
192 Set this to no if you do not want ngircd to connect to other irc servers using ipv6.
196 Maximum number of simultaneous in- and outbound connections the server is
197 allowed to accept (0: unlimited). Default: 0.
199 \fBMaxConnectionsIP\fR
200 Maximum number of simultaneous connections from a single IP address that
201 the server will accept (0: unlimited). This configuration options lowers
202 the risk of denial of service attacks (DoS). Default: 5.
205 Maximum number of channels a user can be member of (0: no limit).
209 Maximum length of an user nick name (Default: 9, as in RFC 2812). Please
210 note that all servers in an IRC network MUST use the same maximum nick name
213 Connect to the remote server using TLS/SSL (Default: false)
216 sections are used to define IRC Operators. There may be more than one
218 block, one for each local operator.
221 ID of the operator (may be different of the nick name).
224 Password of the IRC operator.
227 Mask that is to be checked before an /OPER for this account is accepted.
228 Example: nick!ident@*.example.com
230 Other servers are configured in
232 sections. If you configure a port for the connection, then this ngIRCd
233 tries to connect to to the other server on the given port (active);
234 if not, it waits for the other server to connect (passive).
236 ngIRCd supports "server groups": You can assign an "ID" to every server
237 with which you want this ngIRCd to link, and the daemon ensures that at
238 any given time only one direct link exists to servers with the same ID.
239 So if a server of a group won't answer, ngIRCd tries to connect to the next
240 server in the given group (="with the same ID"), but never tries to connect
241 to more than one server of this group simultaneously.
243 There may be more than one
248 IRC name of the remote server.
251 Internet host name (or IP address) of the peer.
254 IP address to use as source IP for the outgoing connection. Default ist
255 to let the operating system decide.
258 Port of the remote server to which ngIRCd should connect (active).
259 If no port is assigned to a configured server, the daemon only waits for
260 incoming connections (passive).
263 Own password for this connection. This password has to be configured as
264 "PeerPassword" on the other server. Must not have ':' as first character.
267 Foreign password for this connection. This password has to be configured as
268 "MyPassword" on the other server.
271 Group of this server (optional).
274 Disable automatic connection even if port value is specified. Default: false.
275 You can use the IRC Operator command CONNECT later on to create the link.
278 Define a (case insensitive) mask matching nick names that sould be treated as
279 IRC services when introduced via this remote server. REGULAR SERVERS DON'T NEED
280 this parameter, so leave it empty (which is the default).
283 When you are connecting IRC services which mask as a IRC server and which use
284 "virtual users" to communicate with, for example "NickServ" amd "ChanServ",
285 you should set this parameter to something like "*Serv".
287 Pre-defined channels can be configured in
289 sections. Such channels are created by the server when starting up and even
290 persist when there are no more members left.
292 Persistent channels are marked with the mode 'P', which can be set and unset
293 by IRC operators like other modes on the fly.
295 There may be more than one
300 Name of the channel, including channel prefix ("#").
303 Topic for this channel.
306 Initial channel modes.
309 Sets initial channel key (only relevant if mode k is set).
312 Set maximum user limit for this channel (only relevant if mode l is set).
314 It's wise to use "ngircd --configtest" to validate the configuration file
315 after changing it. See
320 .UR mailto:alex@barton.de
325 .UR http://ngircd.barton.de/
326 http://ngircd.barton.de/
projects / ngircd-alex.git / blob