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 can be used to disable compile-time features at run time, e.g. if ngircd
52 was built to support ident lookups, but you do not want ngircd to perform
53 ident lookups you can disable them here.
54 This section is optional.
56 is the section where server links are configured. And
58 blocks are used to configure pre-defined ("persistent") IRC channels.
60 There can be more than one [Operator], [Server] and [Channel] sections
61 per configuration file, but only one [Global] and one [Features] section.
65 section is used to define the server main configuration, like the server
66 name and the ports on which the server should be listening.
69 Server name in the IRC network. This is an individual name of the IRC
70 server, it is not related to the DNS host name. It must be unique in the
71 IRC network and must contain at least one dot (".") character.
74 Info text of the server. This will be shown by WHOIS and LINKS requests for
78 Global password for all users needed to connect to the server. The default
79 is empty, so no password is required.
82 Password required for using the WEBIRC command used by some Web-to-IRC
83 gateways. If not set or empty, the WEBIRC command can't be used.
86 \fBAdminInfo1\fR, \fBAdminInfo2\fR, \fBAdminEMail\fR
87 Information about the server and the administrator, used by the ADMIN
91 Ports on which the server should listen. There may be more than one port,
92 separated with commas (","). Default: 6667, unless \fBSSL_Ports\fR are also
96 Same as \fBPorts\fR , except that ngIRCd will expect incoming connections
97 to be SSL/TLS encrypted. Common port numbers for SSL-encrypted IRC are 6669
98 and 6697. Default: none.
101 Filename of SSL Server Key to be used for SSL connections. This is required for
104 \fBSSLKeyFilePassword\fR
105 (OpenSSL only:) Password to decrypt private key.
108 Certificate file of the private key.
111 Name of the Diffie-Hellman Parameter file. Can be created with gnutls
112 "certtool \-\-generate-dh-params" or "openssl dhparam".
113 If this file is not present, it will be generated on startup when ngIRCd
114 was compiled with gnutls support (this may take some time). If ngIRCd
115 was compiled with OpenSSL, then (Ephemeral)-Diffie-Hellman Key Exchanges and several
116 Cipher Suites will not be available.
119 A comma separated list of IP address on which the server should listen.
120 If unset, the defaults value is "0.0.0.0" or, if ngIRCd was compiled
121 with IPv6 support, "::,0.0.0.0". So the server listens on all configured
122 IP addresses and interfaces by default.
125 Syslog "facility" to which ngIRCd should send log messages. Possible
126 values are system dependant, but most probably "auth", "daemon", "user"
127 and "local1" through "local7" are possible values; see syslog(3).
128 Default is "local5" for historical reasons, you probably want to
129 change this to "daemon", for example.
132 Text file with the "message of the day" (MOTD). This message will be shown
133 to all users connecting to the server. Changes made to this file
134 take effect when ngircd is instructed to re-read its configuration file.
137 A simple Phrase (<256 chars) if you don't want to use a MOTD file.
140 User ID under which the server should run; you can use the name of the user
146 For this to work the server must have been
147 started with root privileges! In addition, the configuration and MOTD files
148 must be readable by this user, otherwise RESTART and REHASH won't work!
152 Group ID under which the ngIRCd should run; you can use the name of the
153 group or the numerical ID.
158 For this to work the server must have
159 been started with root privileges!
163 A directory to chroot in when everything is initialized. It doesn't need
164 to be populated if ngIRCd is compiled as a static binary. By default ngIRCd
165 won't use the chroot() feature.
170 For this to work the server must have
171 been started with root privileges!
175 This tells ngIRCd to write its current process ID to a file. Note that the
176 pidfile is written AFTER chroot and switching the user ID, i. e. the
177 directory the pidfile resides in must be writeable by the ngIRCd user and
178 exist in the chroot directory (if configured, see above).
182 After <PingTimeout> seconds of inactivity the server will send a PING to
183 the peer to test whether it is alive or not. Default: 120.
186 If a client fails to answer a PING with a PONG within <PongTimeout>
187 seconds, it will be disconnected by the server. Default: 20.
190 The server tries every <ConnectRetry> seconds to establish a link to not yet
191 (or no longer) connected servers. Default: 60.
194 Should IRC Operators be allowed to use the MODE command even if they are
195 not(!) channel-operators? Default: no.
198 If \fBOperCanUseMode\fR is enabled, this may lead the compatibility problems with
199 Servers that run the ircd-irc2 Software. This Option "masks" mode requests
200 by non-chanops as if they were coming from the server. Default: no.
202 \fBAllowRemoteOper\fR
203 Are IRC operators connected to remote servers allowed to control this server,
204 e. g. are they allowed to use administrative commands like CONNECT, DIE,
205 SQUIT, ... that affect this server? Default: no.
207 \fBPredefChannelsOnly\fR
208 If enabled, no new channels can be created. Useful if
209 you do not want to have channels other than those defined in
210 [Channel] sections in the configuration file.
214 Set this to no if you do not want ngIRCd to connect to other IRC servers using
215 IPv4. This allows usage of ngIRCd in IPv6-only setups.
219 Set this to no if you do not want ngIRCd to connect to other irc servers using IPv6.
223 Maximum number of simultaneous in- and outbound connections the server is
224 allowed to accept (0: unlimited). Default: 0.
226 \fBMaxConnectionsIP\fR
227 Maximum number of simultaneous connections from a single IP address that
228 the server will accept (0: unlimited). This configuration options lowers
229 the risk of denial of service attacks (DoS). Default: 5.
232 Maximum number of channels a user can be member of (0: no limit).
236 Maximum length of an user nick name (Default: 9, as in RFC 2812). Please
237 note that all servers in an IRC network MUST use the same maximum nick name
241 sections are used to define IRC Operators. There may be more than one
243 block, one for each local operator.
246 ID of the operator (may be different of the nick name).
249 Password of the IRC operator.
252 Mask that is to be checked before an /OPER for this account is accepted.
253 Example: nick!ident@*.example.com
255 An optional section that can be used to disable features at
256 run-time. A feature is enabled by default if if ngircd was built with
259 If set to false, ngIRCd will not make DNS lookups when clients connect.
260 If you configure the daemon to connect to other servers, ngIRCd may still
261 perform a DNS lookup if required.
265 If ngIRCd is compiled with IDENT support this can be used to disable IDENT
270 If ngIRCd is compiled with PAM support this can be used to disable all calls
271 to the PAM library at runtime; all users connecting without password are
272 allowed to connect, all passwords given will fail.
276 If ngIRCd is compiled to register its services using ZeroConf (e.g. using
277 Howl, Avahi or on Mac OS X) this parameter can be used to disable service
278 registration at runtime.
282 Other servers are configured in
284 sections. If you configure a port for the connection, then this ngIRCd
285 tries to connect to to the other server on the given port (active);
286 if not, it waits for the other server to connect (passive).
288 ngIRCd supports "server groups": You can assign an "ID" to every server
289 with which you want this ngIRCd to link, and the daemon ensures that at
290 any given time only one direct link exists to servers with the same ID.
291 So if a server of a group won't answer, ngIRCd tries to connect to the next
292 server in the given group (="with the same ID"), but never tries to connect
293 to more than one server of this group simultaneously.
295 There may be more than one
300 IRC name of the remote server.
303 Internet host name (or IP address) of the peer.
306 IP address to use as source IP for the outgoing connection. Default is
307 to let the operating system decide.
310 Port of the remote server to which ngIRCd should connect (active).
311 If no port is assigned to a configured server, the daemon only waits for
312 incoming connections (passive, default).
315 Own password for this connection. This password has to be configured as
316 \fBPeerPassword\fR on the other server. Must not have ':' as first character.
319 Foreign password for this connection. This password has to be configured as
320 \fBMyPassword\fR on the other server.
323 Group of this server (optional).
326 Disable automatic connection even if port value is specified. Default: false.
327 You can use the IRC Operator command CONNECT later on to create the link.
330 Connect to the remote server using TLS/SSL. Default: false.
333 Define a (case insensitive) mask matching nick names that should be treated as
334 IRC services when introduced via this remote server. REGULAR SERVERS DON'T NEED
335 this parameter, so leave it empty (which is the default).
338 When you are connecting IRC services which mask as a IRC server and which use
339 "virtual users" to communicate with, for example "NickServ" and "ChanServ",
340 you should set this parameter to something like "*Serv".
342 Pre-defined channels can be configured in
344 sections. Such channels are created by the server when starting up and even
345 persist when there are no more members left.
347 Persistent channels are marked with the mode 'P', which can be set and unset
348 by IRC operators like other modes on the fly.
350 There may be more than one
355 Name of the channel, including channel prefix ("#" or "&").
358 Topic for this channel.
361 Initial channel modes.
364 Sets initial channel key (only relevant if channel mode "k" is set).
367 Path and file name of a "key file" containing individual channel keys for
368 different users. The file consists of plain text lines with the following
369 syntax (without spaces!):
383 can contain the wildcard character "*".
386 is an arbitrary password.
398 The key file is read on each JOIN command when this channel has a key
399 (channel mode +k). Access is granted, if a) the channel key set using the
400 MODE +k command or b) one of the lines in the key file match.
404 The file is not reopened on each access, so you can modify and overwrite it
405 without problems, but moving or deleting the file will have not effect until
406 the daemon re-reads its configuration!
410 Set maximum user limit for this channel (only relevant if channel mode "l"
413 It's wise to use "ngircd \-\-configtest" to validate the configuration file
414 after changing it. See
418 Alexander Barton, <alex@barton.de>
420 Florian Westphal, <fw@strlen.de>
422 Homepage: http://ngircd.barton.de/
projects / ngircd-alex.git / blob