2 .\" ngircd.conf(5) manual page template
4 .TH ngircd.conf 5 "Dec 2010" 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 Most variables can be modified while the ngIRCd daemon is already running:
17 It will reload its configuration when a HUP signal is received.
19 The file consists of sections and parameters. A section begins with the name
20 of the section in square brackets and continues until the next section
23 Sections contain parameters of the form
31 Empty lines and any line beginning with a semicolon (';') or a hash ('#')
32 character are treated as a comment and will be ignored. Leading and trailing
33 whitespaces are trimmed before any processing takes place.
35 The file format is line-based - that means, each non-empty newline-terminated
36 line represents either a comment, a section name, or a parameter.
38 Section and parameter names are not case sensitive.
39 .SH "SECTION OVERVIEW"
40 The file can contain blocks of four types: [Global], [Operator], [Server],
43 The main configuration of the server is stored in the
45 section, like the server name, administrative information and the
46 ports on which the server should be listening. IRC operators of this
51 is the section where server links are configured. And
53 blocks are used to configure pre-defined ("persistent") IRC channels.
55 There can be more than one [Operator], [Server] and [Channel] sections
56 per configuration file, but only one [Global] section.
60 section is used to define the server main configuration, like the server
61 name and the ports on which the server should be listening.
64 Server name in the IRC network. This is an individual name of the IRC
65 server, it is not related to the DNS host name. It must be unique in the
66 IRC network and must contain at least one dot (".") character.
69 Info text of the server. This will be shown by WHOIS and LINKS requests for
73 Global password for all users needed to connect to the server. The default
74 is empty, so no password is required.
77 Password required for using the WEBIRC command used by some Web-to-IRC
78 gateways. If not set or empty, the WEBIRC command can't be used.
81 \fBAdminInfo1\fR, \fBAdminInfo2\fR, \fBAdminEMail\fR
82 Information about the server and the administrator, used by the ADMIN
86 Ports on which the server should listen. There may be more than one port,
87 separated with commas (","). Default: 6667, unless \fBSSL_Ports\fR are also
91 Same as \fBPorts\fR , except that ngIRCd will expect incoming connections
92 to be SSL/TLS encrypted. Common port numbers for SSL-encrypted IRC are 6669
93 and 6697. Default: none.
96 Filename of SSL Server Key to be used for SSL connections. This is required for
99 \fBSSLKeyFilePassword\fR
100 (OpenSSL only:) Password to decrypt private key.
103 Certificate file of the private key.
106 Name of the Diffie-Hellman Parameter file. Can be created with gnutls
107 "certtool \-\-generate-dh-params" or "openssl dhparam".
108 If this file is not present, it will be generated on startup when ngIRCd
109 was compiled with gnutls support (this may take some time). If ngIRCd
110 was compiled with OpenSSL, then (Ephemeral)-Diffie-Hellman Key Exchanges and several
111 Cipher Suites will not be available.
114 A comma separated list of IP address on which the server should listen.
115 If unset, the defaults value is "0.0.0.0" or, if ngIRCd was compiled
116 with IPv6 support, "::,0.0.0.0". So the server listens on all configured
117 IP addresses and interfaces by default.
120 Syslog "facility" to which ngIRCd should send log messages. Possible
121 values are system dependant, but most probably "auth", "daemon", "user"
122 and "local1" through "local7" are possible values; see syslog(3).
123 Default is "local5" for historical reasons, you probably want to
124 change this to "daemon", for example.
127 Text file with the "message of the day" (MOTD). This message will be shown
128 to all users connecting to the server. Changes made to this file
129 take effect when ngircd is instructed to re-read its configuration file.
132 A simple Phrase (<256 chars) if you don't want to use a MOTD file.
135 User ID under which the server should run; you can use the name of the user
141 For this to work the server must have been
142 started with root privileges! In addition, the configuration and MOTD files
143 must be readable by this user, otherwise RESTART and REHASH won't work!
147 Group ID under which the ngIRCd should run; you can use the name of the
148 group or the numerical ID.
153 For this to work the server must have
154 been started with root privileges!
158 A directory to chroot in when everything is initialized. It doesn't need
159 to be populated if ngIRCd is compiled as a static binary. By default ngIRCd
160 won't use the chroot() feature.
165 For this to work the server must have
166 been started with root privileges!
170 This tells ngIRCd to write its current process ID to a file. Note that the
171 pidfile is written AFTER chroot and switching the user ID, i. e. the
172 directory the pidfile resides in must be writeable by the ngIRCd user and
173 exist in the chroot directory (if configured, see above).
177 After <PingTimeout> seconds of inactivity the server will send a PING to
178 the peer to test whether it is alive or not. Default: 120.
181 If a client fails to answer a PING with a PONG within <PongTimeout>
182 seconds, it will be disconnected by the server. Default: 20.
185 The server tries every <ConnectRetry> seconds to establish a link to not yet
186 (or no longer) connected servers. Default: 60.
189 Should IRC Operators be allowed to use the MODE command even if they are
190 not(!) channel-operators? Default: no.
193 If \fBOperCanUseMode\fR is enabled, this may lead the compatibility problems with
194 Servers that run the ircd-irc2 Software. This Option "masks" mode requests
195 by non-chanops as if they were coming from the server. Default: no.
197 \fBAllowRemoteOper\fR
198 Are IRC operators connected to remote servers allowed to control this server,
199 e. g. are they allowed to use administrative commands like CONNECT, DIE,
200 SQUIT, ... that affect this server? Default: no.
202 \fBPredefChannelsOnly\fR
203 If enabled, no new channels can be created. Useful if
204 you do not want to have channels other than those defined in
205 [Channel] sections in the configuration file.
209 If set to true, ngIRCd will not make DNS lookups when clients connect.
210 If you configure the daemon to connect to other servers, ngIRCd may still
211 perform a DNS lookup if required.
215 If ngIRCd is compiled with IDENT support this can be used to disable IDENT
220 If ngIRCd is compiled with PAM support this can be used to disable all calls
221 to the PAM library at runtime; all users connecting without password are
222 allowed to connect, all passwords given will fail.
226 If ngIRCd is compiled to register its services using ZeroConf (e.g. using
227 Howl, Avahi or on Mac OS X) this parameter can be used to disable service
228 registration at runtime.
232 Set this to no if you do not want ngIRCd to connect to other IRC servers using
233 IPv4. This allows usage of ngIRCd in IPv6-only setups.
237 Set this to no if you do not want ngIRCd to connect to other irc servers using IPv6.
241 Maximum number of simultaneous in- and outbound connections the server is
242 allowed to accept (0: unlimited). Default: 0.
244 \fBMaxConnectionsIP\fR
245 Maximum number of simultaneous connections from a single IP address that
246 the server will accept (0: unlimited). This configuration options lowers
247 the risk of denial of service attacks (DoS). Default: 5.
250 Maximum number of channels a user can be member of (0: no limit).
254 Maximum length of an user nick name (Default: 9, as in RFC 2812). Please
255 note that all servers in an IRC network MUST use the same maximum nick name
259 sections are used to define IRC Operators. There may be more than one
261 block, one for each local operator.
264 ID of the operator (may be different of the nick name).
267 Password of the IRC operator.
270 Mask that is to be checked before an /OPER for this account is accepted.
271 Example: nick!ident@*.example.com
273 Other servers are configured in
275 sections. If you configure a port for the connection, then this ngIRCd
276 tries to connect to to the other server on the given port (active);
277 if not, it waits for the other server to connect (passive).
279 ngIRCd supports "server groups": You can assign an "ID" to every server
280 with which you want this ngIRCd to link, and the daemon ensures that at
281 any given time only one direct link exists to servers with the same ID.
282 So if a server of a group won't answer, ngIRCd tries to connect to the next
283 server in the given group (="with the same ID"), but never tries to connect
284 to more than one server of this group simultaneously.
286 There may be more than one
291 IRC name of the remote server.
294 Internet host name (or IP address) of the peer.
297 IP address to use as source IP for the outgoing connection. Default is
298 to let the operating system decide.
301 Port of the remote server to which ngIRCd should connect (active).
302 If no port is assigned to a configured server, the daemon only waits for
303 incoming connections (passive, default).
306 Own password for this connection. This password has to be configured as
307 \fBPeerPassword\fR on the other server. Must not have ':' as first character.
310 Foreign password for this connection. This password has to be configured as
311 \fBMyPassword\fR on the other server.
314 Group of this server (optional).
317 Disable automatic connection even if port value is specified. Default: false.
318 You can use the IRC Operator command CONNECT later on to create the link.
321 Connect to the remote server using TLS/SSL. Default: false.
324 Define a (case insensitive) mask matching nick names that should be treated as
325 IRC services when introduced via this remote server. REGULAR SERVERS DON'T NEED
326 this parameter, so leave it empty (which is the default).
329 When you are connecting IRC services which mask as a IRC server and which use
330 "virtual users" to communicate with, for example "NickServ" and "ChanServ",
331 you should set this parameter to something like "*Serv".
333 Pre-defined channels can be configured in
335 sections. Such channels are created by the server when starting up and even
336 persist when there are no more members left.
338 Persistent channels are marked with the mode 'P', which can be set and unset
339 by IRC operators like other modes on the fly.
341 There may be more than one
346 Name of the channel, including channel prefix ("#" or "&").
349 Topic for this channel.
352 Initial channel modes.
355 Sets initial channel key (only relevant if channel mode "k" is set).
358 Path and file name of a "key file" containing individual channel keys for
359 different users. The file consists of plain text lines with the following
360 syntax (without spaces!):
374 can contain the wildcard character "*".
377 is an arbitrary password.
389 The key file is read on each JOIN command when this channel has a key
390 (channel mode +k). Access is granted, if a) the channel key set using the
391 MODE +k command or b) one of the lines in the key file match.
395 The file is not reopened on each access, so you can modify and overwrite it
396 without problems, but moving or deleting the file will have not effect until
397 the daemon re-reads its configuration!
401 Set maximum user limit for this channel (only relevant if channel mode "l"
404 It's wise to use "ngircd \-\-configtest" to validate the configuration file
405 after changing it. See
409 Alexander Barton, <alex@barton.de>
411 Florian Westphal, <fw@strlen.de>
413 Homepage: http://ngircd.barton.de/
projects / ngircd-alex.git / blob