2 # This is a sample configuration file for the ngIRCd IRC daemon, which must
3 # be customized to the local preferences and needs.
5 # Comments are started with "#" or ";".
7 # A lot of configuration options in this file start with a ";". You have
8 # to remove the ";" in front of each variable to actually set a value!
9 # The disabled variables are shown with example values for completeness only
10 # and the daemon is using compiled-in default settings.
12 # Use "ngircd --configtest" (see manual page ngircd(8)) to validate that the
13 # server interprets the configuration file as expected!
15 # Please see ngircd.conf(5) for a complete list of configuration options.
19 # The [Global] section of this file is used to define the main
20 # configuration of the server, like the server name and the ports
21 # on which the server should be listening.
23 # Server name in the IRC network, must contain at least one dot
24 # (".") and be unique in the IRC network. Required!
27 # Info text of the server. This will be shown by WHOIS and
28 # LINKS requests for example.
29 Info = Server Info Text
31 # Global password for all users needed to connect to the server
34 # Information about the server and the administrator, used by the
35 # ADMIN command. Not required by server but by RFC!
36 ;AdminInfo1 = Description
37 ;AdminInfo2 = Location
38 ;AdminEMail = admin@irc.server
40 # Ports on which the server should listen. There may be more than
41 # one port, separated with ",". (Default: 6667)
42 ;Ports = 6667, 6668, 6669
44 # Additional Listen Ports that expect SSL/TLS encrypted connections
48 ;SSLKeyFile = /usr/local/etc/ngircd/ssl/server-key.pem
50 # password to decrypt SSLKeyFile (OpenSSL only)
51 ;SSLKeyFilePassword = secret
53 # SSL Server Key Certificate
54 ;SSLCertFile = /usr/local/etc/ngircd/ssl/server-cert.pem
56 # Diffie-Hellman parameters
57 ;SSLDHFile = /usr/local/etc/ngircd/ssl/dhparams.pem
59 # comma separated list of IP addresses on which the server should
60 # listen. Default values are:
61 # "0.0.0.0" or (if compiled with IPv6 support) "::,0.0.0.0"
62 # so the server listens on all IP addresses of the system by default.
63 ;Listen = 127.0.0.1,192.168.0.1
65 # Text file with the "message of the day" (MOTD). This message will
66 # be shown to all users connecting to the server:
67 ;MotdFile = /usr/local/etc/ngircd.motd
69 # A simple Phrase (<256 chars) if you don't want to use a motd file.
70 # If it is set no MotdFile will be read at all.
71 ;MotdPhrase = "Hello world!"
73 # User ID under which the server should run; you can use the name
74 # of the user or the numerical ID. ATTENTION: For this to work the
75 # server must have been started with root privileges! In addition,
76 # the configuration and MOTD files must be readable by this user,
77 # otherwise RESTART and REHASH won't work!
80 # Group ID under which the ngircd should run; you can use the name
81 # of the group or the numerical ID. ATTENTION: For this to work the
82 # server must have been started with root privileges!
85 # A directory to chroot in when everything is initialized. It
86 # doesn't need to be populated if ngIRCd is compiled as a static
87 # binary. By default ngIRCd won't use the chroot() feature.
88 # ATTENTION: For this to work the server must have been started
89 # with root privileges!
90 ;ChrootDir = /var/empty
92 # This tells ngircd to write its current process id to a file.
93 # Note that the pidfile is written AFTER chroot and switching uid,
94 # i. e. the Directory the pidfile resides in must be writeable by
95 # the ngircd user and exist in the chroot directory.
96 ;PidFile = /var/run/ngircd/ngircd.pid
98 # After <PingTimeout> seconds of inactivity the server will send a
99 # PING to the peer to test whether it is alive or not.
102 # If a client fails to answer a PING with a PONG within <PongTimeout>
103 # seconds, it will be disconnected by the server.
106 # The server tries every <ConnectRetry> seconds to establish a link
107 # to not yet (or no longer) connected servers.
110 # Should IRC Operators be allowed to use the MODE command even if
111 # they are not(!) channel-operators?
114 # Mask IRC Operator mode requests as if they were coming from the
115 # server? (This is a compatibility hack for ircd-irc2 servers)
118 # Are remote IRC operators allowed to control this server, e. g.
119 # use commands like CONNECT, SQUIT, DIE, ...?
120 ;AllowRemoteOper = no
122 # Allow Pre-Defined Channels only (see Section [Channels])
123 ;PredefChannelsOnly = no
125 # Don't do any DNS lookups when a client connects to the server.
128 # Don't do any IDENT lookups, even if ngIRCd has been compiled
129 # with support for it.
132 # try to connect to other irc servers using ipv4 and ipv6, if possible
136 # Maximum number of simultaneous in- and outbound connections the
137 # server is allowed to accept (0: unlimited):
140 # Maximum number of simultaneous connections from a single IP address
141 # the server will accept (0: unlimited):
142 ;MaxConnectionsIP = 5
144 # Maximum number of channels a user can be member of (0: no limit):
147 # Maximum length of an user nick name (Default: 9, as in RFC 2812).
148 # Please note that all servers in an IRC network MUST use the same
149 # maximum nick name length!
153 # [Operator] sections are used to define IRC Operators. There may be
154 # more than one [Operator] block, one for each local operator.
156 # ID of the operator (may be different of the nick name)
159 # Password of the IRC operator
162 # Optional Mask from which /OPER will be accepted
163 ;Mask = *!ident@somewhere.example.com
166 # More [Operator] sections, if you like ...
169 # Other servers are configured in [Server] sections. If you
170 # configure a port for the connection, then this ngircd tries to
171 # connect to to the other server on the given port; if not it waits
172 # for the other server to connect.
173 # There may be more than one server block, one for each server.
176 # The ngIRCd allows "server groups": You can assign an "ID" to every
177 # server with which you want this ngIRCd to link. If a server of a
178 # group won't answer, the ngIRCd tries to connect to the next server
179 # in the given group. But the ngircd never tries to connect to two
180 # servers with the same group ID.
182 # IRC name of the remote server, must match the "Name" variable in
183 # the [Global] section of the other server (when using ngIRCd).
186 # Internet host name or IP address of the peer (only required when
187 # this server should establish the connection).
188 ;Host = connect-to-host.the.net
190 # IP address to use as _source_ address for the connection. if
191 # unspecified, ngircd will let the operating system pick an address.
194 # Port of the server to which the ngIRCd should connect. If you
195 # assign no port the ngIRCd waits for incoming connections.
198 # Own password for the connection. This password has to be configured
199 # as "PeerPassword" on the other server.
200 ;MyPassword = MySecret
202 # Foreign password for this connection. This password has to be
203 # configured as "MyPassword" on the other server.
204 ;PeerPassword = PeerSecret
206 # Group of this server (optional)
209 # Set the "Passive" option to "yes" if you don't want this ngIRCd to
210 # connect to the configured peer (same as leaving the "Port" variable
211 # empty). The advantage of this option is that you can actually
212 # configure a port an use the IRC command CONNECT more easily to
213 # manually connect this specific server later.
216 # Connect to the remote server using TLS/SSL (Default: false)
219 # Define a (case insensitive) mask matching nick names that should be
220 # treated as IRC services when introduced via this remote server.
221 # REGULAR SERVERS DON'T NEED this parameter, so leave it empty
222 # (which is the default).
223 # When you are connecting IRC services which mask as a IRC server
224 # and which use "virtual users" to communicate with, for example
225 # "NickServ" and "ChanServ", you should set this parameter to
226 # something like "*Serv".
230 # More [Server] sections, if you like ...
233 # Pre-defined channels can be configured in [Channel] sections.
234 # Such channels are created by the server when starting up and even
235 # persist when there are no more members left.
236 # Persistent channels are marked with the mode 'P', which can be set
237 # and unset by IRC operators like other modes on the fly.
238 # There may be more than one [Channel] block, one for each channel.
240 # Name of the channel
243 # Topic for this channel
244 ;Topic = a great topic
246 # Initial channel modes
249 # initial channel password (mode k)
252 # Key file, syntax for each line: "<user>:<nick>:<key>".
254 ;KeyFile = /etc/ngircd/#chan.key
256 # maximum users per channel (mode l)
260 # More [Channel] sections, if you like ...