1 ########################################################################
3 # ___ ___ ____ ____ _ #
4 # |_ _|_ __ ___ _ __|_ _| _ \ / ___|__| | #
5 # | || '_ \/ __| '_ \| || |_) | | / _` | #
6 # | || | | \__ \ |_) | || _ <| |__| (_| | #
7 # |___|_| |_|___/ .__/___|_| \_\\____\__,_| #
10 # / ___|___ _ __ / _(_) __ _ _ _ _ __ __ _| |_(_) ___ _ __ #
11 # | | / _ \| '_ \| |_| |/ _` | | | | '__/ _` | __| |/ _ \| '_ \ #
12 # | |__| (_) | | | | _| | (_| | |_| | | | (_| | |_| | (_) | | | | #
13 # \____\___/|_| |_|_| |_|\__, |\__,_|_| \__,_|\__|_|\___/|_| |_| #
16 ##################################||####################################
18 ##################################||####################################
20 # This is an example of the config file for InspIRCd. #
21 # Change the options to suit your network #
25 # ____ _ _____ _ _ ____ _ _ _ #
26 # | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
27 # | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
28 # | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
29 # |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
31 # Lines prefixed with READ THIS BIT, as shown above, are IMPORTANT #
32 # lines, and you REALLY SHOULD READ THEM. Yes, THIS MEANS YOU. Even #
33 # if you've configured InspIRCd before, these probably indicate #
34 # something new or different to this version and you SHOULD READ IT. #
36 ########################################################################
38 # Unalphabeticalise the modules list at your own risk #
40 ########################################################################
43 #-#-#-#-#-#-#-#-#-#-#-#- SERVER DESCRIPTION -#-#-#-#-#-#-#-#-#-#-#-#-
45 # Here is where you enter the information about your server. #
47 # Syntax is as follows: #
49 # <server name="server.name" #
50 # description="Server Description" #
52 # network="MyNetwork"> #
54 # The server name should be a syntactically valid hostname, with at #
55 # least one '.', and does not need to resolve to an IP address. #
57 # The description is freeform text. Remember you may put quotes in #
58 # this field by escaping it using \". #
60 # The network field indicates the network name given in on connect #
61 # to clients. It is used by many clients such as mIRC to select a #
62 # perform list, so it should be identical on all servers on a net #
63 # and should not contain spaces. #
65 # The server ID is optional, and if omitted automatically calculated #
66 # from the server name and description. This is similar in #
67 # in behaviour to the server id on ircu and charybdis ircds. #
68 # You should only need to set this manually if there is a collision #
69 # between two server ID's on the network. The server ID must be #
70 # three digits or letters long, of which the first digit must always #
71 # be a number, and the other two letters may be any of 0-9 and A-Z. #
72 # For example, 3F9, 03J and 666 are all valid server IDs, and A9D, #
73 # QFX and 5eR are not. Remember, in most cases you will not need to #
74 # even set this value, it is calculated for you from your server #
75 # name and description. Changing these will change your auto- #
79 <server name="penguin.omega.org.za"
80 description="Waddle World"
84 #-#-#-#-#-#-#-#-#-#-#-#- ADMIN INFORMATION -#-#-#-#-#-#-#-#-#-#-#-#
86 # Describes the Server Administrator's real name (optionally), #
87 # nick, and email address. #
89 # Syntax is as follows: #
90 # <admin name="real name" #
92 # email="email@address.com"> #
95 <admin name="Johnny English"
97 email="MI5@the.best.secret.agent">
100 #-#-#-#-#-#-#-#-#-#-#-#- PORT CONFIGURATION -#-#-#-#-#-#-#-#-#-#-#-
102 # Enter the port and address bindings here. #
104 # bind address - Specifies which address ports bind to. Leaving this #
105 # field blank binds the port to all IP's available. #
107 # port - The port number to bind to. You may specify a port #
108 # range here, e.g. "6667-6669,7000,7001". If you do #
109 # this, the server will count each port within your #
110 # range as a separate binding, making the above #
111 # example equivalent to five separate bind tags. #
112 # A failure on one port in the range does not prevent #
113 # the entire range from being bound, just that one #
116 # type - Can be 'clients' or 'servers'. The clients type is #
117 # a standard TCP based socket, the servers type is a #
118 # also a TCP based connection but of a different #
119 # format. SSL support is provided by modules, to #
120 # enable SSL support, please read the module section #
121 # of this configuration file. #
123 # ssl - When using m_ssl_gnutls.so or m_ssl_openssl.so #
124 # modules, you must define this value to use ssl on #
125 # that port. Valid values are 'gnutls' or 'openssl' #
126 # respectively. If the module is not loaded, this #
127 # setting is ignored. #
129 # transport - If you have m_spanningtree.so loaded, along with #
130 # either one of the SSL modules (m_ssl_gnutls or #
131 # m_ssl_openssl) or m_ziplinks.so, then you may make #
132 # use of this value. #
133 # Setting it to 'openssl' or 'gnutls' or 'zip' #
134 # indicates that the port should accept connections #
135 # using the given transport name. Transports are #
136 # layers which sit on top of a socket and change the #
137 # way data is sent and received, e.g. encryption, #
138 # compression, and other such things. Because this #
139 # may not be limited in use to just encryption, #
140 # the 'ssl' value used for client ports does not #
141 # exist for servers, and this value is used instead. #
142 # ____ _ _____ _ _ ____ _ _ _ #
143 # | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
144 # | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
145 # | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
146 # |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
148 # If you want to link servers to InspIRCd you must load the #
149 # m_spanningtree.so module! Please see the modules list below for #
150 # information on how to load this module! If you do not load this #
151 # module, server ports will NOT be bound! #
153 # Leaving address empty binds to all available interfaces #
155 # Syntax is as follows: #
157 # <bind address="ip address" port="port" type="clients"> #
158 # <bind address="ip address" port="port" type="servers"> #
160 # If InspIRCd is built for IPv6, and you wish to accept IPv4 clients, #
161 # then you can specify IPv4 ip addresses here to bind. You may also #
162 # use the 4in6 notation, ::ffff:1.2.3.4, where 1.2.3.4 is the IPv4 #
163 # address to bind the port, but as of InspIRCd 1.1.1, this is not #
166 # ------------------------------------------------------------------- #
168 # PLEASE NOTE: If you have build InspIRCd as an IPv6 server, and you #
169 # specify an empty bind address, the binding will be bound to ALL THE #
170 # IPv6 IP ADDRESSES, and not the IPv4 addresses. If you are using an #
171 # IPv6 enabled InspIRCd and want to bind to multiple IPv4 addresses #
172 # in this way, you must specify them by hand. If you have built the #
173 # server for IPv4 connections only, then specifying an empty bind #
174 # address binds the port to all IPv4 IP addresses, as expected. #
177 <bind address="" port="6000" type="clients">
178 <bind address="" port="6660-6669" type="clients" ssl="gnutls">
180 # When linking servers, the openssl and gnutls transports are largely
181 # link-compatible and can be used alongside each other or either/or
182 # on each end of the link without any significant issues.
184 <bind address="" port="7000,7001" type="servers">
185 <bind address="1.2.3.4" port="7005" type="servers" transport="openssl">
188 #-#-#-#-#-#-#-#-#-#- DIE/RESTART CONFIGURATION -#-#-#-#-#-#-#-#-#-#-
190 # You can configure the passwords here which you wish to use for #
191 # the die and restart commands. Only trusted IRCop's who will #
192 # need this ability should know the die and restart password. #
194 # Syntax is as follows: #
195 # <power diepass="die password" restartpass="restart password" #
196 # pause="secs before dying"> #
199 <power diepass="" restartpass="" pause="2">
202 #-#-#-#-#-#-#-#-#-# INCLUDE CONFIGURATION #-#-#-#-#-#-#-#-#-#-#-#-#-#
204 # This optional tag allows you to include another config file #
205 # allowing you to keep your configuration tidy. The configuration #
206 # file you include will be treated as part of the configuration file #
207 # which includes it, in simple terms the inclusion is transparent. #
209 # All paths to config files are relative to the directory of the main #
210 # config file inspircd.conf, unless the filename starts with a forward#
211 # slash (/) in which case it is treated as an absolute path. #
213 # You may also include an executable file, in which case if you do so #
214 # the output of the executable on the standard output will be added #
215 # to your config at the point of the include tag. #
217 # Syntax is as follows: #
218 #<include file="file.conf"> #
219 #<include executable="/path/to/executable parameters"> #
222 #-#-#-#-#-#-#-#-#-#- CONNECTIONS CONFIGURATION -#-#-#-#-#-#-#-#-#-#-#
224 # This is where you can configure which connections are allowed #
225 # and denied access onto your server. The password is optional. #
226 # You may have as many of these as you require. To allow/deny all #
227 # connections, use a '*' or 0.0.0.0/0. #
229 # Syntax is as follows: #
231 # <connect name="myallow" allow="1.2.3.0/24" limit="5" #
232 # password="blahblah" timeout="10" timeout="blah" #
233 # flood="5" threshold="8" pingfreq="120" sendq="99999" #
234 # revcq="696969" localmax="3" globalmax="3" #
235 # port="6660" maxchans="50" limit="999"> #
237 # <connect name="blocked" deny="127.0.0.1" port="6667"> #
239 # <connect name="something" parent="myallow" pingfreq="60"> #
241 # IP masks may be specified in CIDR format or wildcard format, #
242 # for IPv4 and IPv6. You *cannot* use hostnames in the allow or #
243 # deny field, as the state is applied before the user's DNS has #
246 # You can optionally name your connect allow/deny tags. If you do #
247 # this, you may reference this connect tag as the parent of another #
248 # connect tag with the <connect:parent> option as shown above. If #
249 # you do this, any options not explicitly specified in the tag will #
250 # be copied from the parent. #
252 # If the value maxchans is included, this overrides all other max #
253 # channels related settings, including the separate oper maximum. #
254 # You may set this to any (sane) value you wish and it applies to #
255 # all users within this connect tag. #
257 # You may optionally include timeout="x" on any allow line, which #
258 # specifies the amount of time given before an unknown connection #
259 # is closed if USER/NICK/PASS are not given. This value is in secs. #
261 # You may optionally limit the number of clients that are matched #
262 # by a single <connect> tag by specifying the maximum in the limit #
263 # parameter. If set to 0, there is no limit, which is the default. #
265 # You should also include a flood="x" line which indicates #
266 # the number of lines a user may place into their buffer at once #
267 # before they are disconnected for excess flood. This feature can #
268 # not be disabled, however it can be set to extremely high values, #
269 # rendering it effectively disabled. A recommended value is 10. #
270 # A counter is maintained for each user which is reset every #
271 # 'threshold' seconds and specifying this threshold value with #
272 # threshold="X" indicates how often the counter is reset. For #
273 # example, with flood="5" and threshold="8", the user may not send #
274 # more than 5 lines in 8 secs. #
276 # You may optionally specify the sendq size and ping frequency of #
277 # each connect:allow line using the pingfreq="X" and sendq="X" #
278 # settings as shown in the full example below. #
279 # The ping frequency is specified in seconds, and the sendq size #
280 # in bytes. It is recommended, although not enforced, that you #
281 # should never set your sendq size to less than 8K. Send Queues are #
282 # dynamically allocated and can grow as needed up to the maximum #
285 # The optional recvq value is the maximum size which users in this #
286 # group may grow their receive queue to. This is recommended to be #
287 # kept pretty low compared to the sendq, as users will always #
288 # receive more than they send in normal circumstances. The default #
289 # if not specified is 4096. #
291 # The sendq is the data waiting to be sent TO THE USER. #
292 # The recvq is the data being received FROM THE USER. #
293 # The names sendq and recvq are from the SERVER'S PERSPECTIVE not #
294 # that of the user... Just to clear up any confusion or complaints #
295 # that these are backwards :p #
297 # The localmax and globalmax values can be used to enforce local #
298 # and global session limits on connections. The session limits are #
299 # counted against all users, but applied only to users within the #
300 # class. For example, if you had a class 'A' which has a session #
301 # limit of 3, and a class 'B' which has a session limit of 5, and #
302 # somehow, two users managed to get into class B which also match #
303 # class A, there is only one connection left for this IP now in A, #
304 # but if they can connect again to B, there are three. You get the #
307 # NOTE NOTE NOTE NOTE NOTE NOTE! #
308 # The maximum limits by default apply to individual IP addresses #
309 # This *MAY* be changed by modifying the <cidr> block, in order #
310 # to detect cloning across an ISP. #
312 # The optional port value determines which port the connect tag is #
313 # handling. If left out the connect tag covers all bound ports else #
314 # only incoming connections on the specified port will match. Port #
315 # tags may be used on connect allow and connect deny tags. #
317 # The limit value determines the maximum number of users which may #
318 # be in this class. Combine this with CIDR masks for various ISP #
319 # subnets to limit the number of users which may connect at any one #
320 # time from a certain ISP. Omit this value to not limit the tag. #
323 <connect allow="196.12.*" password="secret" port="6667">
336 <connect deny="69.254.*">
337 <connect deny="3ffe::0/32">
339 #-#-#-#-#-#-#-#-#-#-#-#- CIDR CONFIGURATION -#-#-#-#-#-#-#-#-#-#-#-
341 # CIDR configuration allows detection of clones and applying of #
342 # throttle limits across a CIDR range. (A CIDR range is a group of #
343 # IPs, for example, the CIDR range 192.168.1.0-192.168.1.255 may be #
344 # represented as 192.168.1.0/24). This means that abuse across an ISP #
345 # is detected and curtailed much easier. #
348 # This specifies how many bits of an IP address should be checked #
349 # against cloning in the <connect> tags, for example, if <connect> #
350 # tags specified a limit of 2 (low!), and three users attempted to #
351 # connect in the IP range 192.168.1.0-192.168.1.255, and ipv4clone #
352 # was set to '24', the third connection would be disconnected. #
354 # Valid values are 0-32, but you *don't* want 0. Using values which #
355 # are not multiples of 8 can give confusing behaviour. #
356 # For more info, see: http://www.inspircd.org/wiki/CIDR_Tutorial #
358 # ipv6clone works in the same way, except for ipv6 addresses. Valid #
359 # range is 0-128, but you *don't* want anything too small. #
361 # Setting these to their maximum value (32, 128) will result in #
362 # no actual CIDR checking being done, and clone checking will only be #
363 # done across individual IPs. This is the default behaviour. #
369 #-#-#-#-#-#-#-#-#-#-#-#- CLASS CONFIGURATION -#-#-#-#-#-#-#-#-#-#-#-
371 # Classes are a group of commands which are grouped together and #
372 # given a unique name. They're used to define which commands #
373 # are available to certain types of Operators. #
375 # Syntax is as follows: #
377 # <class name="name" commands="oper commands" #
378 # usermodes="allowed oper only usermodes" #
379 # chanmodes="allowed oper only channelmodes"> #
381 # The name value indicates a name for this class. #
382 # The commands value indicates a list of one or more commands that #
383 # are allowed by this class (see also 'READ THIS BIT' below). #
384 # The usermodes and chanmodes values indicate lists of usermodes and #
385 # channel modes this oper can execute. This only applies to modes #
386 # that are marked oper-only such as usermode +Q and channelmode +O. #
387 # ____ _ _____ _ _ ____ _ _ _ #
388 # | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
389 # | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
390 # | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
391 # |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
393 # You are not forced to give these classes the names given below. #
394 # You can create your own named classes, if you want, in fact that #
395 # is the whole idea of this system! #
397 # Note: It is possible to make a class which covers all available #
398 # commands. To do this, specify commands="*". This is not really #
399 # recommended, as it negates the whole purpose of the class system, #
400 # however it is provided for fast configuration (e.g. in test nets) #
403 <class name="Shutdown" commands="DIE RESTART REHASH LOADMODULE UNLOADMODULE RELOAD" usermodes="*" chanmodes="*">
404 <class name="ServerLink" commands="CONNECT SQUIT RCONNECT MKPASSWD MKSHA256" usermodes="*" chanmodes="*">
405 <class name="BanControl" commands="KILL GLINE KLINE ZLINE QLINE ELINE" usermodes="*" chanmodes="*">
406 <class name="OperChat" commands="WALLOPS GLOBOPS SETIDLE SPYLIST SPYNAMES" usermodes="*" chanmodes="*">
407 <class name="HostCloak" commands="SETHOST SETIDENT SETNAME CHGHOST CHGIDENT" usermodes="*" chanmodes="*">
410 #-#-#-#-#-#-#-#-#-#-#-#- OPERATOR COMPOSITION -#-#-#-#-#-#-#-#-#-#-#
412 # This is where you specify which types of operators you have on #
413 # your server, as well as the commands they are allowed to use. #
414 # This works alongside with the classes specified above. #
416 # type name - A name for the combined class types. #
417 # a type name cannot contain spaces, however if you #
418 # put an _ symbol in the name, it will be translated #
419 # to a space when displayed in a WHOIS. #
421 # classes - Specified above, used for flexibility for the #
422 # server admin to decide on which operators get #
423 # what commands. Class names are case sensitive, #
424 # separate multiple class names with spaces. #
426 # host - Optional hostmask operators will receive on oper-up. #
428 # Syntax is as follows: #
430 # <type name="name" classes="class names" host="oper hostmask"> #
432 # ____ _ _____ _ _ ____ _ _ _ #
433 # | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
434 # | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
435 # | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
436 # |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
438 # You are not forced to give these types the names given below. #
439 # You can create your own named types, if you want, in fact that #
440 # is the whole idea of this system! #
443 <type name="NetAdmin" classes="OperChat BanControl HostCloak Shutdown ServerLink" host="netadmin.omega.org.za">
444 <type name="GlobalOp" classes="OperChat BanControl HostCloak ServerLink" host="ircop.omega.org.za">
445 <type name="Helper" classes="HostCloak" host="helper.omega.org.za">
448 #-#-#-#-#-#-#-#-#-#-#- OPERATOR CONFIGURATION -#-#-#-#-#-#-#-#-#-#-#
450 # Opers are defined here. This is a very important section. #
451 # Remember to only make operators out of trust worthy people. #
453 # name - Oper name, this is case sensitive, so it is best to #
456 # password - Password to oper-up, also case sensitive. #
457 # encryption is supported via modules. You may load #
458 # modules for MD5 or SHA256 encryption, and if you do, #
459 # this value will be a hash value, otherwise put a #
460 # plaintext password in this value. #
462 # host - Hosts of client allowed to oper-up. #
463 # wildcards accepted, separate multiple hosts with a #
464 # space. You may also specify CIDR IP addresses. #
466 # fingerprint - When using the m_ssl_oper_cert.so module, you may #
467 # specify a key fingerprint here. This can be obtained #
468 # using the /fingerprint command whilst the module is #
469 # loaded, or from the notice given to you when you #
470 # connect to the ircd using a client certificate, #
471 # and will lock this oper block to only the user who #
472 # has that specific key/certificate pair. #
473 # this enhances security a great deal, however it #
474 # requires that opers use clients which can send ssl #
475 # client certificates, if this is configured for that #
476 # oper. Note that if the m_ssl_oper.so module is not #
477 # loaded, and/or one of m_ssl_openssl or m_ssl_gnutls #
478 # is not loaded, this configuration option has no #
479 # effect and will be ignored. #
481 # type - Defines the kind of operator. This must match a type #
482 # tag you defined above, and is case sensitive. #
484 # Syntax is as follows: #
485 # <oper name="login" #
487 # host="hostmask@of.oper" #
488 # fingerprint="hexsequence" #
489 # type="oper type"> #
494 host="ident@dialup15.isp.com *@localhost *@server.com *@3ffe::0/16"
498 #-#-#-#-#-#-#-#-#-#-#- SERVER LINK CONFIGURATION -#-#-#-#-#-#-#-#-#-#
500 # Defines which servers can link to this one, and which servers this #
501 # server may create outbound links to. #
503 # name - The name is the canonical name of the server, does #
504 # not have to resolve - but it is expected to be set #
505 # in the remote servers connection info. #
507 # ipaddr - Valid host or IP address for remote server. These #
508 # hosts are resolved on rehash, and cached, if you #
509 # specify a hostname; so if you find that your server #
510 # is still trying to connect to an old IP after you #
511 # have updated your DNS, try rehashing and then #
512 # attempting the connect again. #
514 # port - The TCP port for the remote server. #
516 # sendpass - Password to send to create an outbound connection #
519 # recvpass - Password to receive to accept an inbound connection #
520 # from this server. #
522 # autoconnect - Sets the server to autoconnect. Where x is the num. #
523 # (optional) of seconds between attempts. e.g. 300 = 5 minutes. #
525 # transport - If defined, this is a transport name implemented by #
526 # another module. Transports are layers on top of #
527 # plaintext connections, which alter them in certain #
528 # ways. Currently the three supported transports are #
529 # 'openssl' and 'gnutls' which are types of SSL #
530 # encryption, and 'zip' which is for compression. #
531 # If you define a transport, both ends of the #
532 # connection must use a compatible transport for the #
533 # link to succeed. OpenSSL and GnuTLS are link- #
534 # compatible with each other. #
536 # statshidden - When using m_spanningtree.so for linking. you may #
537 # set this to 'yes', and if you do, the IP address/ #
538 # hostname of this connection will NEVER be shown to #
539 # any opers on the network. In /stats c its address #
540 # will show as *@<hidden>, and during CONNECT and #
541 # inbound connections, it's IP will show as <hidden> #
542 # UNLESS the connection fails (e.g. due to a bad #
543 # password or servername) #
545 # allowmask - When this is defined, it indicates a range of IP #
546 # addresses to allow for this link (You may use CIDR #
547 # or wildcard form for this address). #
548 # e.g. if your server is going to connect to you from #
549 # the range 1.2.3.1 through 1.2.3.255, put 1.2.3.0/24 #
550 # into this value. If it is not defined, then only #
551 # the ipaddr field of the server shall be allowed. #
553 # failover - If you define this option, it must be the name of a #
554 # different link tag in your configuration. This #
555 # option causes the ircd to attempt a connection to #
556 # the failover link in the event that the connection #
557 # to this server fails. For example, you could define #
558 # two hub uplinks to a leaf server, and set an #
559 # american server to autoconnect, with a european #
560 # hub as its failover. In this situation, your ircd #
561 # will only try the link to the european hub if the #
562 # american hub is unreachable. NOTE that for the #
563 # intents and purposes of this option, an unreachable #
564 # server is one which DOES NOT ANSWER THE CONNECTION. #
565 # If the server answers the connection with accept(), #
566 # EVEN IF THE CREDENTIALS ARE INVALID, the failover #
567 # link will not be tried! Failover settings will also #
568 # apply to autoconnected servers as well as manually #
571 # timeout - If this is defined, then outbound connections will #
572 # time out if they are not connected within this many #
573 # seconds. If this is not defined, the default of ten #
576 # bind - If you specify this value, then when creating an #
577 # outbound connection to the given server, the IP you #
578 # place here will be bound to. This is for multi- #
579 # homed servers which may have multiple IP addresses. #
580 # if you do not define this value, the first IP that #
581 # is not empty or localhost from your <bind> tags #
582 # will be bound to. This is usually acceptable, #
583 # however if your server has multiple network cards #
584 # then you may have to manually specify the bind #
585 # value instead of leaving it to automatic binding. #
586 # you can usually tell if you need to set this by #
587 # looking for the error 'Could not assign requested #
588 # address' in your log when connecting to servers. #
590 # hidden - If this is set to true, yes, or 1, then the server #
591 # is completely hidden from non-opers. It does not #
592 # show in /links and it does not show in /map. Also, #
593 # any servers which are child servers of this one #
594 # in the network will *also* be hidden. Use with #
595 # care! You can use this to 'mask off' sections of #
596 # the network so that users only see a small portion #
597 # of a much larger net. It should NOT be relied upon #
598 # as a security tool, unless it is being used for #
599 # example to hide a non-client hub, for which clients #
600 # do not have an IP address or resolvable hostname. #
602 # To u:line a server (give it extra privileges required for running #
603 # services, Q, etc) you must include the <uline server> tag as shown #
604 # in the example below. You can have as many of these as you like. #
606 # WARNING: Unlike other ircds, u:lining a server allows ALL users on #
607 # that server to operoverride modes. This should only be used for #
608 # services and protected oper servers! #
610 # ------------------------------------------------------------------- #
612 # NOTE: If you have built your server as an IPv6 server, then when a #
613 # DNS lookup of a server's host occurs, AAAA records (IPv6) are #
614 # prioritised over A records (IPv4). Therefore, if the server you are #
615 # connecting to has both an IPv6 IP address and an IPv4 IP address in #
616 # its DNS entry, the IPv6 address will *always* be selected. To #
617 # change this behaviour simply specify the IPv4 IP address rather #
618 # than the hostname of the server. #
620 # ------------------------------------------------------------------- #
622 # ____ _ _____ _ _ ____ _ _ _ #
623 # | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
624 # | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
625 # | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
626 # |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
628 # If you want to link servers to InspIRCd you must load the #
629 # m_spanningtree.so module! Please see the modules list below for #
630 # information on how to load this module! If you do not load this #
631 # module, server links will NOT work! #
633 # Also, if you define any transports, you must load the modules for #
634 # these transports BEFORE you load m_spanningtree, e.g. place them #
635 # above it in the configuration file. Currently this means the three #
636 # modules m_ssl_gnutls, m_ziplinks and m_ssl_openssl, depending on #
637 # which you choose to use. #
640 <link name="hub.penguin.org"
641 ipaddr="penguin.box.com"
643 allowmask="69.58.44.0/24"
645 failover="hub.other.net"
651 sendpass="outgoing!password"
652 recvpass="incoming!password">
654 <link name="services.antarctic.com"
657 allowmask="127.0.0.0/8"
659 recvpass="polarbears">
662 #-#-#-#-#-#-#-#-#-#-#-#- ULINES CONFIGURATION #-#-#-#-#-#-#-#-#-#-#-#-#
663 # This tag defines a ulined server. A U-Lined server has special #
664 # permissions, and should be used with caution. Services servers are #
665 # usually u-lined in this manner. #
667 # The 'silent' value, if set to yes, indicates that this server should#
668 # not generate quit and connect notices, which can cut down on noise #
669 # to opers on the network. #
671 <uline server="services.antarctic.com" silent="yes">
674 #-#-#-#-#-#-#-#-#-#- MISCELLANEOUS CONFIGURATION -#-#-#-#-#-#-#-#-#-#
676 # These options let you define the path to your motd and rules #
677 # files. If these are relative paths, they are relative to the #
678 # configuration directory. #
681 <files motd="inspircd.motd.example"
682 rules="inspircd.rules.example">
684 #-#-#-#-#-#-#-#-#-#-#-# MAXIMUM CHANNELS -#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
686 # This optional configuration tag lets you define the maximum number #
687 # of channels that both opers and users may be on at any one time. #
688 # The default is 20 for users and 60 for opers if this tag is not #
689 # defined. Remote users are not restricted in any manner. #
695 #-#-#-#-#-#-#-#-#-#-#-#-#-#-# DNS SERVER -#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
697 # Define your DNS server address here. InspIRCd has its own resolver. #
698 # If you do not define this value, then InspIRCd will attempt to #
699 # determine your DNS server from your operating system. On POSIX #
700 # platforms, InspIRCd will read /etc/resolv.conf, and populate this #
701 # value with the first DNS server address found. On Windows platforms #
702 # InspIRCd will check the registry, and use the DNS server of the #
703 # first active network interface, if one exists. #
704 # If a DNS server cannot be determined from these checks, the default #
705 # value '127.0.0.1' is used instead. The timeout value is in seconds. #
707 # ____ _ _____ _ _ ____ _ _ _ #
708 # | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
709 # | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
710 # | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
711 # |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
713 # When choosing a server, be sure to choose one which will do a #
714 # RECURSIVE LOOKUP. InspIRCd's resolver does not currently do these #
715 # recursive lookups itself, to save time and resources. The DNS #
716 # server recommended by the InspIRCd team is bind, available from the #
717 # ISC website. If your DNS server does not do a recursive lookup, you #
718 # will be able to notice this by the fact that none of your users are #
719 # resolving even though the DNS server appears to be up! Most ISP and #
720 # hosting provider DNS servers support recursive lookups. #
722 # ------------------------------------------------------------------- #
724 # NOTE: If you have built InspIRCd with IPv6 support, then both #
725 # IPv6 and IPv4 addresses are allowed here, and also in the system #
726 # resolv.conf file. Remember that an IPv4 DNS server can still #
727 # resolve IPv6 addresses, and vice versa. #
730 <dns server="127.0.0.1" timeout="5">
732 # An example of using an IPv6 nameserver
733 #<dns server="::1" timeout="5">
735 #-#-#-#-#-#-#-#-#-#-#-#-#-#-# PID FILE -#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
737 # Define the path to the PID file here. The PID file can be used to #
738 # rehash the ircd from the shell or to terminate the ircd from the #
739 # shell using shell scripts, perl scripts, etc... and to monitor the #
740 # ircd's state via cron jobs. If this is a relative path, it will be #
741 # relative to the configuration directory, and if it is not defined, #
742 # the default of 'inspircd.pid' is used. #
745 #<pid file="/path/to/inspircd.pid">
747 #-#-#-#-#-#-#-#-#-#-#-#-#- BANLIST LIMITS #-#-#-#-#-#-#-#-#-#-#-#-#-#-#
749 # Use these tags to customise the ban limits on a per channel basis. #
750 # The tags are read from top to bottom, and any tag found which #
751 # matches the channels name applies the banlimit to that channel. #
752 # It is advisable to put an entry with the channel as '*' at the #
753 # bottom of the list. If none are specified or no maxbans tag is #
754 # matched, the banlist size defaults to 64 entries. #
757 <banlist chan="#morons" limit="128">
758 <banlist chan="*" limit="69">
760 #-#-#-#-#-#-#-#-#-#-#- DISABLED FEATURES -#-#-#-#-#-#-#-#-#-#-#-#-#-#
762 # This tag is optional, and specifies one or more features which are #
763 # not available to non-operators. #
765 # For example you may wish to disable NICK and prevent non-opers from #
766 # changing their nicknames. #
767 # Note that any disabled commands take effect only after the user has #
768 # 'registered' (e.g. after the initial USER/NICK/PASS on connection) #
769 # so for example disabling NICK will not cripple your network. #
771 # `fakenonexistant' will make the ircd pretend that nonexistant #
772 # commands simply don't exist to non-opers ("no such command"). #
774 #<disabled commands="TOPIC MODE" usermodes="" chanmodes="" fakenonexistant="yes">
777 #-#-#-#-#-#-#-#-#-#-#-#-#-#-#- RTFM LINE -#-#-#-#-#-#-#-#-#-#-#-#-#-#
779 # Just remove this... Its here to make you read ALL of the config #
782 <die value="You should probably edit your config *PROPERLY* and try again.">
786 #-#-#-#-#-#-#-#-#-#-#-#-#- SERVER OPTIONS -#-#-#-#-#-#-#-#-#-#-#-#-#
788 # Settings to define which features are usable on your server. #
790 # prefixquit - A prefix to be placed on the start of a client's #
793 # suffixquit - A suffix to be placed on the end of a client's #
796 # fixedquit - A fixed quit message to display for all client #
797 # QUITS. If specified, overrides both prefixquit #
798 # and suffixquit options. #
800 # prefixpart - A prefix to be placed on the start of a client's #
803 # suffixpart - A suffix to be placed on the end of a client's #
806 # fixedpart - A fixed part message to display for all client #
807 # parts. If specified, overrides both prefixpart #
808 # and suffixpart options. #
810 # allowhalfop - Allows the +h channel mode #
812 # noservices - If noservices is true, yes, or 1, then the first #
813 # user into a channel gets founder status. This is #
814 # only useful on networks running the m_chanprotect #
815 # module without services. #
817 # qprefix - qprefix is used by the chanprotect module to give #
818 # a visible prefix to users set +q (founder) in chan #
819 # It should be set to something sensible like ~ or ! #
820 # If not set, no prefix is applied to users with +q #
822 # aprefix - aprefix is the same as qprefix, except it is for #
823 # giving users with mode +a (protected) a prefix #
825 # deprotectself - If this value is set to yes, true, or 1, then any #
826 # user with +q or +a may remove the +q or +a from #
827 # themselves. The default setting is to not enable #
828 # this feature, which stops even the founder taking #
829 # away their founder status without using services. #
831 # deprotectothers-If this value is set to yes, true, or 1, then any #
832 # user with +q or +a may remove the +q or +a from #
833 # other users. The default setting is to not enable #
834 # this feature, so that only +q may remove +a, and #
835 # nothing but services may remove +q. #
837 # cyclehosts - If this is set to true, yes or 1, then when a #
838 # user's hostname changes, they will appear to quit #
839 # and then rejoin with their new host. This prevents #
840 # clients from being confused by host changes, #
841 # especially in the case of bots, and it is #
842 # recommended that this option is enabled. #
844 # moduledir - This optional value indicates a runtime change of #
845 # the location where modules are to be found. This #
846 # does not add a supplementary directory. There can #
847 # only be one module path. #
849 # syntaxhints - If set to yes, true or 1, when a user does not #
850 # give enough parameters for a command, a syntax #
851 # hint will be given (using the RPL_TEXT numeric) #
852 # as well as the standard ERR_NEEDMOREPARAMS. #
854 # announcets - If this value is defined to yes, true, or 1, then #
855 # a channels' timestamp is updated, the users on #
856 # the channel will be informed of the change via #
857 # a server notice to the channel with the old and #
858 # new TS values in the timestamp. If you think this #
859 # is just pointless noise, define the value to 0. #
861 # ircumsgprefix - Use undernet style message prefix for channel #
862 # NOTICE and PRIVMSG adding the prefix to the line #
863 # of text sent out. Eg. NOTICE @#test :@ testing #
864 # vs. the off setting: NOTICE @#test :testing #
866 # hostintopic - If this is set to yes (the default) then the full #
867 # nick!user@host is shown for who set a TOPIC last. #
868 # if set to no, then only the nickname is shown. #
870 # serverpingfreq- This value, when set, allows you to change the #
871 # frequency of server to server PING messages. This #
872 # can help if you are having certain network issues. #
874 # pingwarning - This should be set to a number between 1 and 59 if #
875 # defined, and if it is defined will cause the server#
876 # to send out a warning via snomask +l if a server #
877 # does not answer to PING after this many seconds. #
878 # This can be useful for finding servers which are #
879 # at risk of pinging out due to network issues. #
881 # defaultmodes - The default modes to be given to each channel on #
882 # creation. Defaults to 'nt'. There should be no + #
883 # or - symbols in this sequence, if you add them #
884 # they will be ignored. You may add parameters for #
885 # modes which take them. #
887 # moronbanner - The NOTICE to show to users who are glined, zlined #
888 # klined or qlined when they are disconnected. This #
889 # is totally freeform, you may place any text here #
892 # exemptchanops - This option allows channel operators to be exempted#
893 # from certain channel modes. #
894 # Supported modes are +SfFgNc. Defaults to off. #
896 # invitebypassmodes - This option allows /invite to bypass modes #
901 <options prefixquit="Quit: "
919 moronbanner="You're banned! Email haha@abuse.com with the ERROR line below for help."
921 invitebypassmodes="yes">
924 #-#-#-#-#-#-#-#-#-#-#-# PERFORMANCE CONFIGURATION #-#-#-#-#-#-#-#-#-#-#
926 # maxwho - The maximum number of results returned by a /WHO #
927 # query. This is to prevent /WHO being used as a #
928 # spam vector or means of flooding an ircd. The #
929 # default is 128, it is not recommended to raise it #
930 # above 1024. Values up to 65535 are permitted. If #
931 # this value is omitted, any size WHO is allowed by #
934 # somaxconn - The maximum number of sockets that may be waiting #
935 # in the accept queue. This usually allows the ircd #
936 # to soak up more connections in a shorter space of #
937 # time when increased but please be aware there is a #
938 # system defined maximum value to this, the same way #
939 # there is a system defined maximum number of file #
940 # descriptors. Some systems may only allow this to #
941 # be up to 5 (ugh) while others such as FreeBSD will #
942 # default to a much nicer 128. #
944 # softlimit - This optional feature allows a defined softlimit. #
945 # if defined sets a soft maxconnections value, has #
946 # to be less than the ./configure maxclients #
948 # nouserdns - If set to yes, true or 1, no user DNS lookups #
949 # will be performed for connecting users. This can #
950 # save a lot of resources on very busy IRC servers. #
952 # quietbursts - When synching or splitting from the network, a #
953 # server can generate a lot of connect and quit #
954 # snotices to the +C and +Q snomasks. Setting this #
955 # value to yes squelches those messages, which can #
956 # make them more useful for opers, however it will #
957 # degrade their use by certain third party programs #
958 # such as BOPM which rely on them to scan users when #
959 # a split heals in certain configurations. #
961 # netbuffersize - Size of the buffer used to receive data from #
962 # clients. The ircd may only read() this amount #
963 # of text in one go at any time. (OPTIONAL) #
966 <performance netbuffersize="10240"
973 #-#-#-#-#-#-#-#-#-#-#-# SECURITY CONFIGURATION #-#-#-#-#-#-#-#-#-#-#-#
976 # - If this option is set, then invites are announced #
977 # to the channel when a user invites another user. #
978 # If you consider this to be unnecessary noise, #
979 # set this to 'none'. To announce to all ops, set #
980 # this to 'ops' and to announce to all users set the #
983 # The value 'dynamic' varies between 'ops' and 'all' #
984 # settings depending on if the channel is +i or not. #
985 # When the channel is +i, messages go only to ops, #
986 # and when the channel is not +i, messages go to #
987 # everyone. In short, the messages will go to every #
988 # user who has power of INVITE on the channel. This #
989 # is the recommended setting. #
991 # disablehmac - If you are linking your InspIRCd to older versions #
992 # then you can specify this option and set it to #
993 # yes. 1.1.6 and above support HMAC and challenge- #
994 # response for password authentication. These can #
995 # greatly enhance security of your server to server #
996 # connections when you are not using SSL (as is the #
997 # case with a lot of larger networks). Linking to #
998 # older versions of InspIRCd should not *usually* be #
999 # a problem, but if you have problems with HMAC #
1000 # authentication, this option can be used to turn it #
1003 # hidemodes - If this option is enabled, then the listmodes #
1004 # given (e.g. +eI), will be hidden from users below #
1005 # halfop. This is not recommended to be set on mode #
1006 # +b, as it may break some features in popular #
1007 # clients such as mIRC. #
1009 # hidesplits - When set to 'yes', will hide split server names #
1010 # from non-opers. Non-opers will see '*.net *.split' #
1011 # instead of the server names in the quit message, #
1012 # identical to the way IRCu displays them. #
1014 # hidebans - When set to 'yes', will hide gline, kline, zline #
1015 # and qline quit messages from non-opers. For #
1016 # example, user A who is not an oper will just see #
1017 # (G-Lined) while user B who is an oper will see the #
1018 # text (G-Lined: Reason here) instead. #
1020 # hidewhois - When defined with a non-empty value, the given #
1021 # text will be used in place of the user's server #
1022 # in WHOIS, when a user is WHOISed by a non-oper. #
1023 # For example, most nets will want to set this to #
1024 # something like '*.netname.net' to conceal the #
1025 # actual server the user is on. #
1027 # flatlinks - When you are using m_spanningtree.so, and this #
1028 # value is set to yes, true or 1, /MAP and /LINKS #
1029 # will be flattened when shown to a non-opers. #
1031 # hideulines - When you are using m_spanningtree.so, and this #
1032 # value is set to yes, true or 1, then U-lined #
1033 # servers will be hidden in /LINKS and /MAP for non #
1034 # opers. Please be aware that this will also hide #
1035 # any leaf servers of a U-lined server, e.g. jupes. #
1037 # userstats - The userstats field is optional and specifies #
1038 # which stats characters in /STATS may be requested #
1039 # by non-operators. Stats characters in this field #
1040 # are case sensitive and are allowed to users #
1041 # independent of if they are in a module or the core #
1043 # operspywhois - If this is set then when an IRC operator uses #
1044 # /WHOIS on a user they will see all channels, even #
1045 # ones if channels are secret (+s), private (+p) or #
1046 # if the target user is invisible +i. #
1048 # customversion - If you specify this configuration item, and it is #
1049 # not set to an empty value, then when a user does #
1050 # a /VERSION command on the ircd, this string will #
1051 # be displayed as the second portion of the output, #
1052 # replacing the system 'uname', compile flags and #
1053 # socket engine/dns engine names. You may use this #
1054 # to enhance security, or simply for vanity. #
1056 # maxtargets - The maxtargets field is optional, and if not #
1057 # defined, defaults to 20. It indicates the maximum #
1058 # number of targets which may be given to commands #
1059 # such as PRIVMSG, KICK etc. #
1061 # hidekills - The hidekills value, if set, replaces the source #
1062 # of all oper-generated kills to be the given text #
1063 # to provide anonimity to your opers. #
1066 <security announceinvites="dynamic"
1080 #-#-#-#-#-#-#-#-#-#-#-#-# LIMITS CONFIGURATION #-#-#-#-#-#-#-#-#-#-#-#
1082 # This configuration tag defines the maximum sizes of various types #
1083 # on IRC, such as the maximum length of a channel name, and the #
1084 # maximum length of a channel. Note that with the exception of the #
1085 # identmax value all values given here are the exact values you would #
1086 # expect to see on IRC. This contrasts with the older InspIRCd #
1087 # releases where these values would be one character shorter than #
1088 # defined to account for a null terminator on the end of the text. #
1090 # The identmax value has special meaning, as it may grow one #
1091 # character longer than you specify, to accomodate for a ~ character #
1092 # when m_ident is loaded. #
1094 # These values should match network-wide, otherwise you may end up #
1095 # with desyncs, and confusing your users by being able to use a nick #
1096 # of a certain length on one server but not on another. Servers will #
1097 # link with mismatched values, but this is NOT recommended as a long #
1100 # Values here should be self explanitory: #
1102 # maxnick - The maximum length of a nickname #
1103 # maxchan - The maximum length of a channel name #
1104 # maxmodes - The maximum number of parameterized mode changes #
1106 # maxident - The maximum length of an ident/username value #
1107 # maxquit - The maximum length of a quit message #
1108 # maxtopic - The maximum length of a channel topic #
1109 # maxkick - The maximum length of a kick message #
1110 # maxgecos - The maximum length of a GECOS (real name) #
1111 # maxaway - The maximum length of an away message #
1114 <limits maxnick="31"
1125 #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
1129 # Logging is covered with the <log> tag, which you may use to change
1130 # the behaviour of the logging of the IRCd.
1132 # In InspIRCd as of 1.2, logging is pluggable and very extensible.
1133 # Different files can log the same thing, different 'types' of log can
1134 # go to different places, and modules can even extend the log tag
1135 # to do what they want.
1137 # An example log tag would be:
1138 # <log method="file" type="OPER" level="default" target="opers.log">
1139 # which would log all information on /oper (failed and successful) to
1140 # a file called opers.log.
1142 # There are many different types which may be used, and modules may
1143 # generate their own. A list of useful types:
1144 # - USERS - information relating to user connection and disconnection
1145 # - CHANNELS - information relating to joining and parting of channels.
1146 # XXX someone doc more on this
1148 # You may also log *everything* by using a type of *, and subtract things out
1149 # of that by using -TYPE - for example "* -USERINPUT -USEROUTPUT".
1151 # The following log tag is highly default and uncustomised. It is recommended you
1152 # sort out your own log tags. This is just here so you get some output.
1153 <log method="file" type="* -USERINPUT -USEROUTPUT -m_spanningtree" level="default" target="ircd.log">
1155 #-#-#-#-#-#-#-#-#-#-#-#-#- WHOWAS OPTIONS -#-#-#-#-#-#-#-#-#-#-#-#-#
1157 # This tag lets you define the behaviour of the /whowas command of #
1160 # groupsize - Controls the maximum entries per nick shown when #
1161 # performing a /whowas nick. Setting this to 0 dis- #
1162 # ables whowas completely. #
1164 # maxgroups - The maximum number of nickgroups that can be added #
1165 # to the list. If max is reached, oldest group will #
1166 # be deleted first like a FIFO. A groupsize of 3 and #
1167 # a maxgroups of 5000 will allow for 5000 nicks to #
1168 # be stored with a history of 3, thus giving a total #
1169 # of 3 * 5000 = 15000 entries. A setting of 0 dis- #
1170 # ables whowas completely. #
1172 # maxkeep - The maximum time a nick is kept in the whowas list #
1173 # before being pruned. Time may be specified in #
1174 # seconds, or in the following format: 1y2w3d4h5m6s #
1175 # meaning one year, two weeks, three days, 4 hours, #
1176 # 5 minutes and 6 seconds. All fields in this format #
1177 # are optional. Minimum is 1 hour, if less InspIRCd #
1178 # will default back to 1 hour. #
1180 #<whowas groupsize="10" #
1181 # maxgroups="100000" #
1184 #-#-#-#-#-#-#-#-#-#-#-#-#-#- BAN OPTIONS -#-#-#-#-#-#-#-#-#-#-#-#-#-#
1186 # The ban tags define nick masks, host masks and ip ranges which are #
1187 # banned from your server. All details in these tags are local to #
1191 # badip lines ban an ip range (same as a zline) #
1193 # ipmask - The ip range to ban (wildcards possible) #
1194 # CIDR is supported in the IP mask. #
1195 # reason - Reason to display when disconnected #
1197 # badnick lines ban a nick mask (same as a qline) #
1199 # nick - Nick mask to ban (wildcards possible) #
1200 # reason - Reason to display on /NICK #
1202 # badhost lines ban a user@host mask (same as a kline) #
1204 # host - ident@hostname (wildcards possible) #
1205 # If you specify an IP, CIDR is supported. #
1206 # reason - Reason to display on disconnection #
1208 # exception lines define a hostmask that is excempt from [kzg]lines #
1210 # host - ident@hostname (wildcards possible) #
1211 # If you specify an IP, CIDR is supported. #
1212 # reason - Reason, shown only in /stats e #
1215 <badip ipmask="69.69.69.69" reason="No porn here thanks.">
1217 <badnick nick="ChanServ" reason="Reserved For Services">
1218 <badnick nick="NickServ" reason="Reserved For Services">
1219 <badnick nick="OperServ" reason="Reserved For Services">
1220 <badnick nick="MemoServ" reason="Reserved For Services">
1222 <badhost host="*@hundredz.n.hundredz.o.1337.kiddies.com" reason="Too many 1337 kiddiots">
1223 <badhost host="*@localhost" reason="No irc from localhost!">
1224 <badhost host="*@172.32.0.0/16" reason="This subnet is bad.">
1226 <exception host="*@ircop.host.com" reason="Opers hostname">
1228 #-#-#-#-#-#-#-#-#-#-#- INSANE BAN OPTIONS -#-#-#-#-#-#-#-#-#-#-#-#-#-#
1230 # This optional tag allows you to specify how wide a gline, eline, #
1231 # kline, zline or qline can be before it is forbidden from being #
1232 # set. By setting hostmasks="yes", you can allow all G, K, E lines, #
1233 # no matter how many users the ban would cover. This is not #
1234 # recommended! By setting ipmasks="yes", you can allow all Z lines, #
1235 # no matter how many users these cover too. Needless to say we #
1236 # don't recommend you do this, or, set nickmasks="yes", which will #
1237 # allow any qline. #
1239 # The trigger value indicates how wide any mask will be before it is #
1240 # prevented from being set. The default value is 95.5% if this tag is #
1241 # not defined in your configuration file, meaning that if your #
1242 # network has 1000 users, a gline matching over 955 of them will be #
1243 # prevented from being added. #
1245 # Please note that remote servers (and services) are exempt from #
1246 # these restrictions and expected to enforce their own policies #
1250 <insane hostmasks="no" ipmasks="no" nickmasks="no" trigger="95.5">
1253 #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#- YAWN -#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
1255 # You should already know what to do here :) #
1257 <die value="User error. Insert new user and press any key. (you didn't edit your config properly.)">
1259 #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-# MODULES #-#-#-#-#-#-#-#-#-#-#-#-#-#-#
1260 # ____ _ _____ _ _ ____ _ _ _ #
1261 # | _ \ ___ __ _ __| | |_ _| |__ (_)___ | __ )(_) |_| | #
1262 # | |_) / _ \/ _` |/ _` | | | | '_ \| / __| | _ \| | __| | #
1263 # | _ < __/ (_| | (_| | | | | | | | \__ \ | |_) | | |_|_| #
1264 # |_| \_\___|\__,_|\__,_| |_| |_| |_|_|___/ |____/|_|\__(_) #
1266 # Well done, you've reached the end of this. #
1267 # We now suggest you read and edit modules.conf, as modules are what #
1268 # provide almost all the features of InspIRCd. :) #
1270 # The default does nothing -- we include it for simplicity for you. #
1271 <include file="modules.conf">
1274 #########################################################################
1276 # - InspIRCd Development Team - #
1277 # http://www.inspircd.org #
1279 #########################################################################
projects / user / henk / code / inspircd.git / blob