DareNET Wiki - User contributions [en]

DareNET IRCd Configuration/1.5

2013-06-17T18:00:33Z

Nitemare: /* Connect block */

__NOTOC__
This is a reference guide for ircd-darenet 1.5.x's configuration file.

The configuration format consists of various blocks, each containing name-value pairs, tags or string data. It is designed to be easily readable by both human ircd.

A block consists of a name, an opening '{' brace, statements, a closing '}' brace, and a ';' semicolon. A statement consists of a name possibly followed by an '=' equals sign and a value, ending with a semicolon. All strings must be surrounded by '"' double quotes.

A sample block:

<html><pre>blockname {
name = value;
name = "string";
name = 123;
tag;
};</pre></html>

All elements of the configuration are separated by whitespace, and can be packed on one line, or broken up over several lines. Whitespace is defined as space, tab or carriage return/linefeed. Three forms of comments are allowed:

<pre>/* C style single/multi-line */

// C++ style single-line

# Shell style single-line
</pre>

{{info|text=Blocks are used in the reverse order than how they're listed, when the configuration file is parsed. This means you should start multiple block definitions with the "fall through", and end with the most detailed.}}

== General block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>M:name:vhost:description::numeric</code>
|}

The General block defines information about the server itself. It is required for the server to start.

<html><pre>General {
/* name: the name of our server. */
name = "test.area.zone.darenet.org";

/* description: the description of our server. */
description = "ircd-darenet test server";

/* numeric: the unique server numeric for our server. It must be a
* digit between 0 and 4095, and is not updated on a rehash.
*/
numeric = 999;

/* vhost: the IP to bind to when we connect outward to other servers.
* It must contain either a * or a valid ipv4 address in dotted quad notation.
*/
vhost = "192.169.0.1";

/* ssl_private_key: our ssl private key. */
ssl_private_key = "etc/ircd.key";

/* ssl_pem: file containing our ssl certificate and private key */
ssl_pem = "etc/ircd.pem";

/* dpass: (optional) password for DIE command. */
dpass = "encrypted pass";

/* rpass: (optional) password for RESTART command. */
rpass = "$PLAIN$password";
};
</pre></html>

The server name may only be changed by a server restart. The description can be changed on rehash, but will not propagate to other linked servers.

There must be exactly one General block.

== Admin block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>A:line1:line2:line3</code>
|}

The Admin block defines information that can be retrieved with the <code>/ADMIN</code> command.

<html><pre>Admin {
location = "DareNET - http://www.darenet.org";
location = "Infrastructure Team";
contact = "<infrastructure@darenet.org>";
};
</pre></html>

Not all lines are required. There may only be one Admin block.

== Class block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>Y:class:pingfreq::maxlinks:sendq (clients)</code> <code>Y:class:pingfreq:connectfreq:maxlinks:sendq (servers)</code>
|-
|}

The Class blocks define connection classes. All connections to the server are associated with a "connection class", whether they be incoming or outgoing (initiated by the server), be they clients or servers.

<html><pre>Class {
/* name: a name for the connection class. */
name = "Users";

/* pingfreq: how often to PING idle connections. */
pingfreq = 1 minute 30 seconds;

/* sendq: send buffer limit (i.e., the amount of data allowed in
* a client's queue before they are dropped.
*/
sendq = 100 kilobytes;

/* maxlinks: the maximum number of connections that may use this
* class. May be between 0 and 4,000,000,000.
*/
maxlinks = 100;

/* usermode: an optional list of user modes that should set
* upon the user while connecting.
*/
usermode = "+iw";

/* maxchans: the maximum number of channels that clients may join.
*/
maxchans = 50;
};

Class {
name = "Opers";
pingfreq = 2 minutes;
sendq = 100 kilobytes;
maxlinks = 10;
usermode = "+iw";
whox;
};

Class {
name = "Server";
pingfreq = 3 minutes;

/* connectfreq: this token applies only to servers, and specifies
* the frequency that the server tries to auto connect. Setting this to 0 will cause a
* server to attempt to connect repeatedly, with no delay until the maxlinks condition
* is satisfied (which is not a good thing).
*/
connectfreq = 5 minutes;

/* maxlinks: for server classes, specifies the maximum number of
* servers to autoconnect to. This should be 0 for hubs, and 1 for leafs.
*/
maxlinks = 0;

sendq = 10 megabytes;
};

Class {
name = "Leaf_Server";
pingfreq = 3 minutes;
connectfreq = 5 minutes;
maxlinks = 1;
sendq = 10 megabytes;
};
</pre></html>

For connection classes intended for operator use, you can specify privileges the operator should be granted when the Operator block names the class. The local privilege MUST be defined by either the Class or Operator block. It is highly recommended that most privileges be explicitly specified in the operator's Operator block on DareNET.

A "default" class is created internally. This class is used when no other class is specified, but its settings are not useful for most situations. Custom classes are strongly recommended.

There may be multiple Class blocks; at least one is recommended.

== Client block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>I:ipmask:passwd:hostmask:port:class</code>
|}

The Client blocks define the hosts client connections are allowed from, and places them into classes. While the server will start without a Client block, it will not be usable.

<html><pre>Client {
/* host: resolved user@host mask allowed to connect. This is optional
* if you are using the ip mask to match against. Additionally, if you specify *@loc for
* this field it will match all LOC users.
*/
host = "*@*.wirehub.net";

/* ip: unresolved user@ip mask allowed to connect. */
ip = "*@195.86.128.*";

/* password: (optional) password that is required to use this block.
* This password string is not encrypted.
*/
password = "letMEHin";

/* class: the class the user should be placed in. */
class = "Users";

/* maxlinks: if specified, the server will only accept clients when
* the total number of connections to the network from the same IP number doesn't exceed
* this number.
*/
maxlinks = 6;

/* port: (optional) a port to limit this block to. */
port = 6660;
};
</pre></html>

The server uses a default deny policy for incoming connections. You need to define at least one Client block if you wish to use your server.

The <code>host</code> and <code>ip</code> fields specify which connections the block matches. The server always performs a DNS and ident lookup for connections. If DNS cannot find a hostname, the IP address is used instead. If ident cannot get a valid reply, "unknown" is used during this state. The client's resolved hostname, IP address, ident reply, and username (from the USER line) are used according to the results of the matches described below.

'''Note:''' There is a specify case for UNIX domain sockets and localhost connections. In these cases, the <code>ip / host</code> field is compared with the name of the server, and thus not with any IP number representation. The name of the server is that returned in the numeric 002 reply, example: <code>002 Your host is 2.darenet.org[jolan.ppro]. running version ...</code> In this example, "jolan.ppro" is the name used for matching; therefore, UNIX domain sockets and connections to localhost would match a block containing: <code>host = "*@jolan.ppro";</code>.

The <code>host</code> field attempts to match first against the resolved hostname, if available, and then against the IP address. To include the connection's ident reply in the match, use a mask in the form "ident@host". If a client matches, it appears on IRC using its resolved hostname.

The <code>ip</code> field attempts to match against the IP address only. An ident may be specified to match against, as well.

'''Note:''' If the ident portion is specified in a mask (i.e., "ident@host" instead of "host"), and no ident reply is received from the client, it will appear on IRC with its username prefixed with a '~' tilde. If the matching mask used only the "host" form, the client's username is not prefixed. If a valid ident reply is received, it is always used and not prefixed.

You need only specify a <code>host</code> or <code>ip</code> field, not both. If both are used, <code>host</code> is matched against first.

There may be multiple Client blocks; at least one is recommended.

== Motd block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>T:hostmask|classnumber:path</code>
|}

The Motd blocks allow a different Message of the Day to be shown to connecting clients based on their origin.

<html><pre>Motd {
/* host: a hostmask, class number or class name to match against. */
host = "*.jp";

/* file: the path to the MOTD file to be shown (relative to DPATH). */
file = "jp.motd";
};
</pre></html>

More then one <code>host</code> field may be present in an Motd block.

There may be multiple Motd blocks.

== Connect block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>C:host:cpassword:name:port:class</code> <code>N:host:apassword:name:flags:class</code> <code>H:host::name:maxhops</code> <code>L:host::mask:depth</code>
|}

The Connect blocks define links to other servers.

<html><pre>Connect {
/* name: the name of the server. */
name = "uplink.darenet.org";

/* host: the host or IP to connect to. If a hostname is used it
* must match the reverse dns of the server.
*/
host = "192.168.0.1";

/* password: the password we send and accept. */
password = "somepass";

/* port: the port to connect to this server on. This is also the
* port used when the server attempts to auto-connect (if enabled).
*/
port = 7325;

/* class: the class this server should be placed in. */
class = "Server";

/* maxhops: the max number of hops a hub may introduce. If a hub
* tries to introduce servers farther away than what is specified here, an SQUIT is
* issued. The 'leaf' token is an alias for "maxhops = 0;".
*/
maxhops = 2;

/* hub: (optional) the mask of servers that this server may hub
* for. The tag 'hub' is an alias for 'hub = "*";'.
*/
hub = "*.us.darenet.org";

/* autoconnect: (optional) determines if we should try to
* automatically connect to this server. The default is to autoconnect.
*/
autoconnect = no;
};
</pre></html>

There may be multiple Connect blocks.

== CRule block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>D:servermask::rule</code> <code>d:servermask::rule</code>
|}

The CRule (connection rule) blocks control ircd-darenet's advanced, real-time rule-based routing decision making system.

<html><pre>CRule {
/* server: rules will be applied towards servers matching this mask. */
server = "*.eu.darenet.org";

/* rule: the connection rule. */
rule = "connected(amsterdam.eu.*)";

/* all: (optional) setting this to 'yes' will make the rule always
* apply; otherwise, it only applies to autoconnects.
*/
all = yes;
};
</pre></html>

If more than one server mask is present in a single crule, the rule will apply to all servers.

See doc/readme.crules for more information on the crule system, including examples of allowed rules.

There may be multiple CRule blocks.

== Port Block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>P:hostmask:interface:<[CES][H]>:port</code>
|}

The Port blocks define where the server will accept connections. At least one port block is required to start.

<html><pre>Port {
/* port: the specific port to listen on. */
port = 7325;

/* mask: (optional) the IP address (or a range of IP addresses) that
* the server will allow connections from.
*/
mask = "127.0.*.*";

/* vhost: (optional) set a specific IP/host the port (listed after
* the 'port' token) will listen for.
*/
vhost = "127.0.0.1";

/* server: setting this to yes makes this a server only port. */
server = yes;

/* hidden: (optional) setting this to 'yes' makes the port
* "hidden" from stats replies.
*/
hidden = yes;

/* crypt: (optional) setting this to 'yes' makes the port accept
* SSL connections.
*/
crypt = yes;

/* exempt: (optional) setting this to 'yes' makes the port exempt
* from connection restrictions during a timed /RESTART or /DIE.
*/
exempt = no;
};
</pre></html>

The <code>mask</code> field should only contain IP addresses (CIDR notation is supported) or '*', if used. This does not use DNS in any way, so you cannot use it to allow *.dk or *.uk, for example. Attempting to specify anything other than IP addresses will result in the port allowing connections from anyone (as if you used '*').

If the <code>vhost</code> field (i.e., bind address) is not specified, the server will listen on all available interfaces for that port.

There may be multiple Port blocks.

== Operator block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>O:host:password:name:flags:class</code> <code>o:host:password:name:flags:class</code>
|}

The Operator blocks define server operators. One or more of these blocks is recommended if you intend to maintain your server.

<html><pre>Operator {
/* name: the oper's username. */
name = "johndoe";

/* host: the user@host/IP mask required for this operator. CIDR
* notation is supported. Multiple host="" lines are supported.
*/
host = "god@*";
host = "*@127.0.0.1";

/* password: the password required to oper. By default, the password is
* hashed using the system's native crypt() function. Other password
* mechanisms are available; the umkpasswd utility located in the ircd
* directory can hash passwords using those mechanisms. If you use a
* password format that is not generated by umkpasswd, ircd-darenet will
* not recognize the oper's password.
*/
password = "/home/irc/keys/johndoe.key";

/* flags: misc options for the oper. */
flags = "OAWInFR";

/* snomask: (optional) specific server notice mask on oper up. If this
* is specified, an oper will not be given sno_default.
*/
snomask = "+cegGiKorRs";

/* privileges: (optional) you can specify privileges an oper will be
* explicitly granted (or denied) upon opering. Any privileges defined
* will override any privilege settings that may be present in the class
* block specified above, and the default setting for those privileges.
*/
local = no; routing = yes; routeinfo = yes;
};
</pre></html>

The <code>name</code> and <code>password</code> fields match the parameters of the <code>OPER</code> command. To authenticate as an IRC operator, a client must match one of the <code>host</code> fields, which may be a resolved hostname or IP address.

To use an unencrypted password, prefix the password with '$PLAIN', e.g., "$PLAIN$aPpLe".

If you want to use a more secure password authentication system, generate a 1024bit RSA key, and specify the path to the key as the password (as shown in the example above), and add 'R' to the <code>flags</code> field. This will use the <code>/CHALLENGE</code> system instead of <code>/OPER</code>. See doc/challenge.txt for more details.

A client may also use their SSL client certificate fingerprint to authenticate as an IRC operator. To use this method, specify the client's certificate fingerprint as the password, and add 'S' to the <code>flags</code> field.

Only one password authentication method may be used at a time. That is, you cannot use <code>CHALLENGE</code> and SSL client certificate fingerprint at the same time.

There are currently 9 different oper flags:
* o - Local operator
* O - Global operator
* A - Server administrator
* r - This operator block may be used from remote servers
* W - Allowed to set user mode +W
* I - Allowed to set user mode +I
* n - Allowed to set user mode +n
* F - Allowed to set user mode +F
* S - Use SSL client certificate fingerprint to <code>/OPER</code>
* R - Use <code>/CHALLENGE</code> password authentication system.
* j - Allowed to use juped nicknames.

The <code>class</code> field specifies the connection class the client will be placed in, regardless of their previous connection class. If not specified, the default class is used; see the Class block description for details.

There may be multiple Operator blocks.

== UWorld block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The Uworld block defines "U-lined" servers, which are allowed to do special network things. Used for network services.

<html><pre>UWorld {
/* name: the server name or wildcard mask the "U-line" applies to. */
name = "services.darenet.org";
name = "stats.darenet.org";
};
</pre></html>

UWorld servers are permitted to do things typical network services would want to do, such as apply network bans, manage channel modes, etc; the details are too numerous and complex to provide here.

There may be multiple UWorld blocks; all blocks are combined into one list.

== NickJupe block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The NickJupe blocks disallow certain nicknames from being used.

<html><pre>NickJupe {
"ChanServ" = "Reserved for Services";
"NickS?rv" = "Reserved for Services";
};
</pre></html>

Entries are specified in a key-value format, with the key being the nick to disallow (the '*' and '?' wildcards are supported), and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice).

There may be multiple NickJupe blocks; all blocks are combined into one list.

== Quarantine block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>Q:channel:reason</code>
|}

The Quarantine blocks disallow certain channel names from being used by non-opers.

<html><pre>Quarantine {
"#help" = "For assistance, please join #Support instead.";
};
</pre></html>

Entries are specified in a key-value format, with the key being the channel to disallow, and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice). Note, these are only checked at <code>/JOIN</code>, so if you add a channel and rehash, users will not be kicked if they're already in the channel.

There may be multiple Quarantine blocks; all blocks are combined into one list.

== Ban Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| K:line
|}

Ban {} blocks disallow connections from clients based on specific ident, host and/or gecos masks. They are a flexible general client ban mechanism.

<pre>Ban
{
host = "user@host";
reason = "The reason the user will see";
klineprompt;
name = "mark";
};</pre>

'''Required tokens (at least one of):''' <code>host, realname, username</code>

'''Optional tokens:''' <code>klineprompt, reason, name, file</code>

If <code>klineprompt;</code> is present, users may bypass the ban by using Login-on-Connect (LOC). You can also mark clients by using <code>name = "mark here";</code>

<pre>Ban
{
realname = "realname here";
reason = "The reason the user will see";
};</pre>

It is also possible to ban based on username.

<pre>Ban
{
username = "username here";
reason = "The reason the user will see";
};</pre>

It is also possible to use a file as comment for the ban, using.

<pre>Ban
{
host = "user@host";
file = "path/to/file/with/reason/to/show";
};</pre>

The file can contain for example, a reason, a link to the server rules and a contact address. Also, note the combination of username and host in the host field. IP-based Ban {} blocks apply to all hosts, even if an IP address has a properly resolving host name. CIDR format is the most efficient, and should be used when possible. The server will attempt to convert wildcard IP masks to CIDR form internally.

Additionally, you may specify a hostmask prefixed with $V to indicate a match should be performed against the CTCP version of the user rather han the host/IP.

<pre>Ban
{
version = "string";
reason = "reason here";
};</pre>

There may be multiple Ban {} blocks.

'''Example blocks:'''

<c>Ban
{
host = "*@*.aol.com";
reason = "Due to abuse, AOL users must login with their DareNET account to connect.";
klineprompt;
};</c>

<c>Ban
{
host = "192.168.*";
reason = "Monkeys.";
};</c>

<c>Ban
{
host = "192.168.0.0/16";
reason = "Monkeys.";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

== Except Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| E:line
|}

Except {} blocks can be used to exempt a user from Kill {} blocks, GLINEs, ZLINEs, SHUNs, spam filters, IDENT_CHALLENGE and LIST restrictions.

<pre>Except
{
mask = "<mask>";
flags = "<flags>";
};</pre>

<mask> is an ident@ip/host/cidr mask that is to match the user to be exempted. <flags> is one or more of the following flags to specify what the exempt is to match.

* k - Except affects KLINEs.
* g - Except affects GLINEs.
* i - Except affects ident challenges (see IDENT_CHALLENGE feature).
* n - Except for notilde.
* s - Except affects SHUNs.
* z - Except affects ZLINEs.
* F - Forces umode +F on user to bypass message flood checks.
* I - Exempts user from rapid (re)connection throttling & clone checks.
* L - Except affects LIST restrictions.
* N - Exempts user from "no connections" restrictions, allowing them to connect anyway.
* S - Except affects spam filters.

NOTE: For throttling/clone exemptions (I), only IP addresses are supported, since these checks are performed before any DNS resolutions or identd replies are received.
NOTE: For notilde (n), IP/Host is required.

Example block:

<c>Except
{
mask = "*@*.darenet.org";
flags = "kgzsL";
};</c>

<c>Except
{
mask = "*@127.0.0.1";
flags = "I";
};</c>

== Command Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| B:line
|}

Command {} blocks aim to improve the generic IRC users ability to use network services. Each block sets up a /<service> alias so that users may type that instead of a full /msg command. Some might argue this is a bit more secure as well :)

<pre>Command
{
cmd = "<alias name>";
service = "<target>";
prefix = "<anything to prepend to the message>";
};</pre>

If <code> prefix = "";</code> is given, then ircd-darenet will prefix the specified string to whatever the user inputs before sending it to the service.

Example blocks:

<c>Command
{
cmd = "AUTH";
service = "NickServ@services.darenet.org";
prefix = "AUTH";
};</c>

<c>Command
{
cmd = "NICKSERV";
service = "NickServ@services.darenet.org";
};</c>

== Forward Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| b:line
|}

Forward {} blocks enable the server to forward any messages which are prefixed and specific with a Forward {} block. This allows users to use Services' fantasy commands without a service client being in the channel (provided the channel is registered). This also removes the need for ChanServ to monitor channel traffic (e.g. allowing the use of umode +d).

<pre>Forward
{
"<prefix>" = "<server>";
};</pre>

Example block:

<c>Forward
{
"." = "services.darenet.org";
"?" = "services.darenet.org";
};</c>

== Redirect Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| R:line
|}
When a client connects and his/her host matches a Redirect {} block, then a 010 reply is sent back to the client with the redirection server and port.

Currently only EPIC supports auto redirection when it gets a 010 reply (e.g. it will automatically connect to the server specified in the 010 reply). Other clients will get a message specifying what server and port to connect to. as well as an unauthorized disconnect.

<pre>Redirect
{
mask = "<mask>";
server = "<redirection server>";
port = "<redirection port>";
};</pre>

<c>Redirect
{
mask = "*.aol.com";
server = "irc.aol.com";
port = "6667";
};</c>

== Spoofhost Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| S:line
|}

Spoofhost {} blocks allows clients/opers to spoof their host.

<pre>Spoofhost "<spoof host>"
{
pass = "<password>";
host = "<*.host.cc|a.b.c.*|CIDR>";
username = "<ident>";
};</pre>

* <spoof host> - The spoofed hostname.
* <pass> - A password for this spoof host. Used if SETHOST_USER is set to TRUE.
* <host> - A hostmask to match against users that are to be auto-spoofed. Used if SETHOST_AUTO is set to TRUE. Can be in the form of: host.domain.cc, 127.0.0.1 or 127.0.0.0/24, supports wildcards for non-CIDR.
* <username> - A mask for matching against the user's ident reply.

Example block:

<c>Spoofhost "sline.darenet.org"
{
pass = "anygoodpass";
host = "127.0.0.1";
username = "*";
};</c>

== DNSBL Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| X:line
|}

DNSBL {} blocks allow you to prevent clients connecting who are listed on DNS blacklists. Their connection will be rejected during the connection process along with the name and reason you give for the DNSBL they have been matched on.

<pre>DNSBL
{
server = "<dnsbl.site.org>";
name = "<name>";
flags = "<flags>";
replies = "<replies/mask>";
reply = "<rejection message>";
rank = "<rank>";
};</pre>

Available flags:

* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.
* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.
* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels.
* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.
* m (Mark Hostname) - Mark the hostname of a skipped client

The name option is used for the Mark Hostname flag, and may only contain hostname valid characters only (e.g. NO spaces). With Reply DNSBL's you need to list the replies in a comma separated list. See below for an example. With Bitmask DNSBL's, again, specify the replies you need to match for. The server will sum them up and match them against the DNSBL reply. The rejected user's nick, username, ip, and host can be placed into the rejection message by using these codes:

* %n - Nickname
* %u - Username
* %h - Hostname
* %i - IP Address

The rank number must be unique over all DNSBL {} blocks. The higher the number, the greater precedence it has. The highest ranking DNSBL {} block which is a matched against a user will get its name marked in the hostname.

Notes: MAKE SURE you read the DNSBL website before you go ahead and use it as they may have rules for large sites/servers who use them. If you do not wish to use DNSBL checking then simply do not create any DNSBL {} blocks.

Example blocks:

Reply DNSBL:
<c>DNSBL
{
server = "dnsbl.sorbs.net";
name = "sorbs.net";
flags = "r";
replies = "1,2,3,4";
reply = "%n!%u@%h Found On Sorbs DNSBL http://www.dnsbl.us.sorbs.net/cgi-bin/lookup?IP=%i";
rank = "1";
};</c>

Bitmask DNSBL:
<c>DNSBL
{
server = "dnsbl.dnsbl.net";
name = "dnsbl.net";
flags = "b";
replies = "1,3,5";
reply = "%n!%u@%h Found On DNSBL";
rank = "2";
};</c>

== WebIRC Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| W:line
|}

WebIRC {} blocks allow you display the real hostname of users connecting via CGI:IRC clients and sites such as Mibbit.com. These clients will send a WEBIRC command along with the user's hostname, ip and WebIRC {} block password to the server. The password needs to be encrypted like Operator {} block passwords. When the ircd receives the command, instead of using the hostname of the site the users is connecting from, the hostname sent in WEBIRC will be set. All this is done before the client enters the network completely. Please remember to enclose the description using quotes otherwise things will break.

<pre>WebIRC
{
mask = "<mask>";
pass = "<password>";
flags = "<flags>";
ident = "<ident>";
desc = "<description>";
};</pre>

Available flags:

* m - Marks each client connected via the WebIRC {} block using the provided description.
* s - Sets the ident specified in the ident field for each WEBIRC client.
* u - Uses the ident from USER that the WEBIRC client sends.

Note: Do not use both s and u, only choose one of them.

Example:

<c>WebIRC
{
mask = "*@webchat.darenet.org";
pass = "VRKLKuGKn0jLs";
flags = "ms";
ident = "webirc";
desc = "DareNET WebChat";
};</c>

== SpamFilter Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| -
|}

This is probably the most controversial addition to ircd-darenet 1.3.x; however, sadly, it may become useful.

SpamFiler {} blocks allow you to filter PRIVMSG's, NOTICE's, TOPIC's and AWAY's for spam. The filtering is done using regular expressions, so please be careful.

<pre>SpamFilter {
regex = "<regex>";
rtype = "<watch flags>";
action = "<action flags>";
reason = "<reason>";
channel = "<optional alert channel>";
length = <length in seconds>;
};</pre>

* <regex> - PCRE format regular expression to match against.
* <watch flags> - See below for a list.
* <action flags> - See below for a list.
* <reason> - Used in error messages displayed to the user and/or kills/shuns/glines/zlines.
* <optional alert channel> - Requires the C action flag.
* <length in seconds> - Only applies to glines, zlines and shuns.

Available watch flags:

* n - Notices.
* N - Channel notices.
* p - Privmsgs.
* C - Channel privmsgs.
* q - Quits.
* P - Parts.
* d - DCCs.
* a - Away messages.
* t - Topics.
* u - Connects (nick!user@host:gecos).
* i - Nickname changes.

Available action flags:

* a - Auth. If used, logged in clients will be exempt from the filter.
* C - Channel alert. If used, filter matches will be sent to what is set in the SpamFilter {} block channel setting.
* S - Server (snotice) alert.
* k - Kill anyone who matches the filter.
* g - Gline anyone who matches the filter. The length can be given in seconds.
* z - Zline anyone who matches the filter. The length can be given in seconds. This zlines *@ip, so you do not need the i action flag.
* s - Shun anyone who matches the filter. The length can be given in seconds.
* i - Uses the client's IP vice host in a Gline/Shun.
* b - Block; will prevent the PRIVMSG/NOTICE/TOPIC/AWAY from going through.
* n - Notify; will notify the person matching the filter, stating they've matched a filter, and deny their message.
* m - Mark; will mark the client as being a spam source.
* K - Kick; will kick the user triggering the Spam Filter. The kick reason given will be the reason set in the Spam Filter. This Flag will only work with the N and C watch flags.
* o - Ops/HalfOps; exempts ops and halfops from any checks which have a channel target.
* v - Voice; exempts voiced users from any checks which have a channel target.

Notes:

* Shuns and Glines will be set using *@hostname. If you would them to be set using *@ip use the 'i' action flag.
* If you do not specify a length, then FILTER_DEFAULT_LENGTH will be used.
* The 'b' action flag cannot be used with the 'u' watch flag. You will need to use a kill flag to block them.

== Features Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| SUGGESTED
|-
| Old conf format equivalents:
| F:line
|}

ircd-darenet has a large number of options and features, most of which can be configured using a Features {} block. If linking to DareNET, your Features {} block will be rather bare, since most DareNET-specific settings have been already defined in the source.

<pre>Features
{
"featurename" = "value";
"featurename2" = "value2";
};</pre>

You only need one Features {} block, in which you use "featurename" = "value1";, "featurename2" = "value2";, and so on. Please note all values, whether integers or strings, must be enclosed in double quotes.

See the [[Server_Features|servers features]] page for a list of available features.

Example block:

<c>Features
{
"LOG" = "SYSTEM" "FILE" "ircd.log";
"LOG" = "SYSTEM" "LEVEL" "CRIT";
"HUB" = "FALSE";
};</c>

[[Category:IRCd]]

DareNET IRCd Configuration/1.5

2013-06-17T17:59:09Z

Nitemare: Reverted edits by Nitemare (Talk) to last revision by Admin

__NOTOC__
This is a reference guide for ircd-darenet 1.5.x's configuration file.

The configuration format consists of various blocks, each containing name-value pairs, tags or string data. It is designed to be easily readable by both human ircd.

A block consists of a name, an opening '{' brace, statements, a closing '}' brace, and a ';' semicolon. A statement consists of a name possibly followed by an '=' equals sign and a value, ending with a semicolon. All strings must be surrounded by '"' double quotes.

A sample block:

<html><pre>blockname {
name = value;
name = "string";
name = 123;
tag;
};</pre></html>

All elements of the configuration are separated by whitespace, and can be packed on one line, or broken up over several lines. Whitespace is defined as space, tab or carriage return/linefeed. Three forms of comments are allowed:

<pre>/* C style single/multi-line */

// C++ style single-line

# Shell style single-line
</pre>

{{info|text=Blocks are used in the reverse order than how they're listed, when the configuration file is parsed. This means you should start multiple block definitions with the "fall through", and end with the most detailed.}}

== General block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>M:name:vhost:description::numeric</code>
|}

The General block defines information about the server itself. It is required for the server to start.

<html><pre>General {
/* name: the name of our server. */
name = "test.area.zone.darenet.org";

/* description: the description of our server. */
description = "ircd-darenet test server";

/* numeric: the unique server numeric for our server. It must be a
* digit between 0 and 4095, and is not updated on a rehash.
*/
numeric = 999;

/* vhost: the IP to bind to when we connect outward to other servers.
* It must contain either a * or a valid ipv4 address in dotted quad notation.
*/
vhost = "192.169.0.1";

/* ssl_private_key: our ssl private key. */
ssl_private_key = "etc/ircd.key";

/* ssl_pem: file containing our ssl certificate and private key */
ssl_pem = "etc/ircd.pem";

/* dpass: (optional) password for DIE command. */
dpass = "encrypted pass";

/* rpass: (optional) password for RESTART command. */
rpass = "$PLAIN$password";
};
</pre></html>

The server name may only be changed by a server restart. The description can be changed on rehash, but will not propagate to other linked servers.

There must be exactly one General block.

== Admin block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>A:line1:line2:line3</code>
|}

The Admin block defines information that can be retrieved with the <code>/ADMIN</code> command.

<html><pre>Admin {
location = "DareNET - http://www.darenet.org";
location = "Infrastructure Team";
contact = "<infrastructure@darenet.org>";
};
</pre></html>

Not all lines are required. There may only be one Admin block.

== Class block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>Y:class:pingfreq::maxlinks:sendq (clients)</code> <code>Y:class:pingfreq:connectfreq:maxlinks:sendq (servers)</code>
|-
|}

The Class blocks define connection classes. All connections to the server are associated with a "connection class", whether they be incoming or outgoing (initiated by the server), be they clients or servers.

<html><pre>Class {
/* name: a name for the connection class. */
name = "Users";

/* pingfreq: how often to PING idle connections. */
pingfreq = 1 minute 30 seconds;

/* sendq: send buffer limit (i.e., the amount of data allowed in
* a client's queue before they are dropped.
*/
sendq = 100 kilobytes;

/* maxlinks: the maximum number of connections that may use this
* class. May be between 0 and 4,000,000,000.
*/
maxlinks = 100;

/* usermode: an optional list of user modes that should set
* upon the user while connecting.
*/
usermode = "+iw";

/* maxchans: the maximum number of channels that clients may join.
*/
maxchans = 50;
};

Class {
name = "Opers";
pingfreq = 2 minutes;
sendq = 100 kilobytes;
maxlinks = 10;
usermode = "+iw";
whox;
};

Class {
name = "Server";
pingfreq = 3 minutes;

/* connectfreq: this token applies only to servers, and specifies
* the frequency that the server tries to auto connect. Setting this to 0 will cause a
* server to attempt to connect repeatedly, with no delay until the maxlinks condition
* is satisfied (which is not a good thing).
*/
connectfreq = 5 minutes;

/* maxlinks: for server classes, specifies the maximum number of
* servers to autoconnect to. This should be 0 for hubs, and 1 for leafs.
*/
maxlinks = 0;

sendq = 10 megabytes;
};

Class {
name = "Leaf_Server";
pingfreq = 3 minutes;
connectfreq = 5 minutes;
maxlinks = 1;
sendq = 10 megabytes;
};
</pre></html>

For connection classes intended for operator use, you can specify privileges the operator should be granted when the Operator block names the class. The local privilege MUST be defined by either the Class or Operator block. It is highly recommended that most privileges be explicitly specified in the operator's Operator block on DareNET.

A "default" class is created internally. This class is used when no other class is specified, but its settings are not useful for most situations. Custom classes are strongly recommended.

There may be multiple Class blocks; at least one is recommended.

== Client block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>I:ipmask:passwd:hostmask:port:class</code>
|}

The Client blocks define the hosts client connections are allowed from, and places them into classes. While the server will start without a Client block, it will not be usable.

<html><pre>Client {
/* host: resolved user@host mask allowed to connect. This is optional
* if you are using the ip mask to match against. Additionally, if you specify *@loc for
* this field it will match all LOC users.
*/
host = "*@*.wirehub.net";

/* ip: unresolved user@ip mask allowed to connect. */
ip = "*@195.86.128.*";

/* password: (optional) password that is required to use this block.
* This password string is not encrypted.
*/
password = "letMEHin";

/* class: the class the user should be placed in. */
class = "Users";

/* maxlinks: if specified, the server will only accept clients when
* the total number of connections to the network from the same IP number doesn't exceed
* this number.
*/
maxlinks = 6;

/* port: (optional) a port to limit this block to. */
port = 6660;
};
</pre></html>

The server uses a default deny policy for incoming connections. You need to define at least one Client block if you wish to use your server.

The <code>host</code> and <code>ip</code> fields specify which connections the block matches. The server always performs a DNS and ident lookup for connections. If DNS cannot find a hostname, the IP address is used instead. If ident cannot get a valid reply, "unknown" is used during this state. The client's resolved hostname, IP address, ident reply, and username (from the USER line) are used according to the results of the matches described below.

'''Note:''' There is a specify case for UNIX domain sockets and localhost connections. In these cases, the <code>ip / host</code> field is compared with the name of the server, and thus not with any IP number representation. The name of the server is that returned in the numeric 002 reply, example: <code>002 Your host is 2.darenet.org[jolan.ppro]. running version ...</code> In this example, "jolan.ppro" is the name used for matching; therefore, UNIX domain sockets and connections to localhost would match a block containing: <code>host = "*@jolan.ppro";</code>.

The <code>host</code> field attempts to match first against the resolved hostname, if available, and then against the IP address. To include the connection's ident reply in the match, use a mask in the form "ident@host". If a client matches, it appears on IRC using its resolved hostname.

The <code>ip</code> field attempts to match against the IP address only. An ident may be specified to match against, as well.

'''Note:''' If the ident portion is specified in a mask (i.e., "ident@host" instead of "host"), and no ident reply is received from the client, it will appear on IRC with its username prefixed with a '~' tilde. If the matching mask used only the "host" form, the client's username is not prefixed. If a valid ident reply is received, it is always used and not prefixed.

You need only specify a <code>host</code> or <code>ip</code> field, not both. If both are used, <code>host</code> is matched against first.

There may be multiple Client blocks; at least one is recommended.

== Motd block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>T:hostmask|classnumber:path</code>
|}

The Motd blocks allow a different Message of the Day to be shown to connecting clients based on their origin.

<html><pre>Motd {
/* host: a hostmask, class number or class name to match against. */
host = "*.jp";

/* file: the path to the MOTD file to be shown (relative to DPATH). */
file = "jp.motd";
};
</pre></html>

More then one <code>host</code> field may be present in an Motd block.

There may be multiple Motd blocks.

== Connect block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>C:host:cpassword:name:port:class</code> <code>N:host:apassword:name:flags:class</code> <code>H:host::name:maxhops</code> <code>L:host::mask:depth</code>
|}

The Connect blocks define links to other servers.

<html><pre>Connect {
/* name: the name of the server. */
name = "uplink.darenet.org";

/* host: the host or IP to connect to. If a hostname is used it
* must match the reverse dns of the server.
*/
host = "192.168.0.1";

/* vhost: (optional) the host or IP to bind to for this connection.
* If this is not specified, the default vhost (in general {}) is used.
*/
#vhost = "192.168.0.50";

/* password: the password we send and accept. */
password = "somepass";

/* port: the port to connect to this server on. This is also the
* port used when the server attempts to auto-connect (if enabled).
*/
port = 7325;

/* class: the class this server should be placed in. */
class = "Server";

/* maxhops: the max number of hops a hub may introduce. If a hub
* tries to introduce servers farther away than what is specified here, an SQUIT is
* issued. The 'leaf' token is an alias for "maxhops = 0;".
*/
maxhops = 2;

/* hub: (optional) the mask of servers that this server may hub
* for. The tag 'hub' is an alias for 'hub = "*";'.
*/
hub = "*.us.darenet.org";

/* autoconnect: (optional) determines if we should try to
* automatically connect to this server. The default is to autoconnect.
*/
autoconnect = no;
};
</pre></html>

There may be multiple Connect blocks.

== CRule block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>D:servermask::rule</code> <code>d:servermask::rule</code>
|}

The CRule (connection rule) blocks control ircd-darenet's advanced, real-time rule-based routing decision making system.

<html><pre>CRule {
/* server: rules will be applied towards servers matching this mask. */
server = "*.eu.darenet.org";

/* rule: the connection rule. */
rule = "connected(amsterdam.eu.*)";

/* all: (optional) setting this to 'yes' will make the rule always
* apply; otherwise, it only applies to autoconnects.
*/
all = yes;
};
</pre></html>

If more than one server mask is present in a single crule, the rule will apply to all servers.

See doc/readme.crules for more information on the crule system, including examples of allowed rules.

There may be multiple CRule blocks.

== Port Block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>P:hostmask:interface:<[CES][H]>:port</code>
|}

The Port blocks define where the server will accept connections. At least one port block is required to start.

<html><pre>Port {
/* port: the specific port to listen on. */
port = 7325;

/* mask: (optional) the IP address (or a range of IP addresses) that
* the server will allow connections from.
*/
mask = "127.0.*.*";

/* vhost: (optional) set a specific IP/host the port (listed after
* the 'port' token) will listen for.
*/
vhost = "127.0.0.1";

/* server: setting this to yes makes this a server only port. */
server = yes;

/* hidden: (optional) setting this to 'yes' makes the port
* "hidden" from stats replies.
*/
hidden = yes;

/* crypt: (optional) setting this to 'yes' makes the port accept
* SSL connections.
*/
crypt = yes;

/* exempt: (optional) setting this to 'yes' makes the port exempt
* from connection restrictions during a timed /RESTART or /DIE.
*/
exempt = no;
};
</pre></html>

The <code>mask</code> field should only contain IP addresses (CIDR notation is supported) or '*', if used. This does not use DNS in any way, so you cannot use it to allow *.dk or *.uk, for example. Attempting to specify anything other than IP addresses will result in the port allowing connections from anyone (as if you used '*').

If the <code>vhost</code> field (i.e., bind address) is not specified, the server will listen on all available interfaces for that port.

There may be multiple Port blocks.

== Operator block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>O:host:password:name:flags:class</code> <code>o:host:password:name:flags:class</code>
|}

The Operator blocks define server operators. One or more of these blocks is recommended if you intend to maintain your server.

<html><pre>Operator {
/* name: the oper's username. */
name = "johndoe";

/* host: the user@host/IP mask required for this operator. CIDR
* notation is supported. Multiple host="" lines are supported.
*/
host = "god@*";
host = "*@127.0.0.1";

/* password: the password required to oper. By default, the password is
* hashed using the system's native crypt() function. Other password
* mechanisms are available; the umkpasswd utility located in the ircd
* directory can hash passwords using those mechanisms. If you use a
* password format that is not generated by umkpasswd, ircd-darenet will
* not recognize the oper's password.
*/
password = "/home/irc/keys/johndoe.key";

/* flags: misc options for the oper. */
flags = "OAWInFR";

/* snomask: (optional) specific server notice mask on oper up. If this
* is specified, an oper will not be given sno_default.
*/
snomask = "+cegGiKorRs";

/* privileges: (optional) you can specify privileges an oper will be
* explicitly granted (or denied) upon opering. Any privileges defined
* will override any privilege settings that may be present in the class
* block specified above, and the default setting for those privileges.
*/
local = no; routing = yes; routeinfo = yes;
};
</pre></html>

The <code>name</code> and <code>password</code> fields match the parameters of the <code>OPER</code> command. To authenticate as an IRC operator, a client must match one of the <code>host</code> fields, which may be a resolved hostname or IP address.

To use an unencrypted password, prefix the password with '$PLAIN', e.g., "$PLAIN$aPpLe".

If you want to use a more secure password authentication system, generate a 1024bit RSA key, and specify the path to the key as the password (as shown in the example above), and add 'R' to the <code>flags</code> field. This will use the <code>/CHALLENGE</code> system instead of <code>/OPER</code>. See doc/challenge.txt for more details.

A client may also use their SSL client certificate fingerprint to authenticate as an IRC operator. To use this method, specify the client's certificate fingerprint as the password, and add 'S' to the <code>flags</code> field.

Only one password authentication method may be used at a time. That is, you cannot use <code>CHALLENGE</code> and SSL client certificate fingerprint at the same time.

There are currently 9 different oper flags:
* o - Local operator
* O - Global operator
* A - Server administrator
* r - This operator block may be used from remote servers
* W - Allowed to set user mode +W
* I - Allowed to set user mode +I
* n - Allowed to set user mode +n
* F - Allowed to set user mode +F
* S - Use SSL client certificate fingerprint to <code>/OPER</code>
* R - Use <code>/CHALLENGE</code> password authentication system.
* j - Allowed to use juped nicknames.

The <code>class</code> field specifies the connection class the client will be placed in, regardless of their previous connection class. If not specified, the default class is used; see the Class block description for details.

There may be multiple Operator blocks.

== UWorld block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The Uworld block defines "U-lined" servers, which are allowed to do special network things. Used for network services.

<html><pre>UWorld {
/* name: the server name or wildcard mask the "U-line" applies to. */
name = "services.darenet.org";
name = "stats.darenet.org";
};
</pre></html>

UWorld servers are permitted to do things typical network services would want to do, such as apply network bans, manage channel modes, etc; the details are too numerous and complex to provide here.

There may be multiple UWorld blocks; all blocks are combined into one list.

== NickJupe block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The NickJupe blocks disallow certain nicknames from being used.

<html><pre>NickJupe {
"ChanServ" = "Reserved for Services";
"NickS?rv" = "Reserved for Services";
};
</pre></html>

Entries are specified in a key-value format, with the key being the nick to disallow (the '*' and '?' wildcards are supported), and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice).

There may be multiple NickJupe blocks; all blocks are combined into one list.

== Quarantine block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>Q:channel:reason</code>
|}

The Quarantine blocks disallow certain channel names from being used by non-opers.

<html><pre>Quarantine {
"#help" = "For assistance, please join #Support instead.";
};
</pre></html>

Entries are specified in a key-value format, with the key being the channel to disallow, and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice). Note, these are only checked at <code>/JOIN</code>, so if you add a channel and rehash, users will not be kicked if they're already in the channel.

There may be multiple Quarantine blocks; all blocks are combined into one list.

== Ban Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| K:line
|}

Ban {} blocks disallow connections from clients based on specific ident, host and/or gecos masks. They are a flexible general client ban mechanism.

<pre>Ban
{
host = "user@host";
reason = "The reason the user will see";
klineprompt;
name = "mark";
};</pre>

'''Required tokens (at least one of):''' <code>host, realname, username</code>

'''Optional tokens:''' <code>klineprompt, reason, name, file</code>

If <code>klineprompt;</code> is present, users may bypass the ban by using Login-on-Connect (LOC). You can also mark clients by using <code>name = "mark here";</code>

<pre>Ban
{
realname = "realname here";
reason = "The reason the user will see";
};</pre>

It is also possible to ban based on username.

<pre>Ban
{
username = "username here";
reason = "The reason the user will see";
};</pre>

It is also possible to use a file as comment for the ban, using.

<pre>Ban
{
host = "user@host";
file = "path/to/file/with/reason/to/show";
};</pre>

The file can contain for example, a reason, a link to the server rules and a contact address. Also, note the combination of username and host in the host field. IP-based Ban {} blocks apply to all hosts, even if an IP address has a properly resolving host name. CIDR format is the most efficient, and should be used when possible. The server will attempt to convert wildcard IP masks to CIDR form internally.

Additionally, you may specify a hostmask prefixed with $V to indicate a match should be performed against the CTCP version of the user rather han the host/IP.

<pre>Ban
{
version = "string";
reason = "reason here";
};</pre>

There may be multiple Ban {} blocks.

'''Example blocks:'''

<c>Ban
{
host = "*@*.aol.com";
reason = "Due to abuse, AOL users must login with their DareNET account to connect.";
klineprompt;
};</c>

<c>Ban
{
host = "192.168.*";
reason = "Monkeys.";
};</c>

<c>Ban
{
host = "192.168.0.0/16";
reason = "Monkeys.";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

== Except Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| E:line
|}

Except {} blocks can be used to exempt a user from Kill {} blocks, GLINEs, ZLINEs, SHUNs, spam filters, IDENT_CHALLENGE and LIST restrictions.

<pre>Except
{
mask = "<mask>";
flags = "<flags>";
};</pre>

<mask> is an ident@ip/host/cidr mask that is to match the user to be exempted. <flags> is one or more of the following flags to specify what the exempt is to match.

* k - Except affects KLINEs.
* g - Except affects GLINEs.
* i - Except affects ident challenges (see IDENT_CHALLENGE feature).
* n - Except for notilde.
* s - Except affects SHUNs.
* z - Except affects ZLINEs.
* F - Forces umode +F on user to bypass message flood checks.
* I - Exempts user from rapid (re)connection throttling & clone checks.
* L - Except affects LIST restrictions.
* N - Exempts user from "no connections" restrictions, allowing them to connect anyway.
* S - Except affects spam filters.

NOTE: For throttling/clone exemptions (I), only IP addresses are supported, since these checks are performed before any DNS resolutions or identd replies are received.
NOTE: For notilde (n), IP/Host is required.

Example block:

<c>Except
{
mask = "*@*.darenet.org";
flags = "kgzsL";
};</c>

<c>Except
{
mask = "*@127.0.0.1";
flags = "I";
};</c>

== Command Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| B:line
|}

Command {} blocks aim to improve the generic IRC users ability to use network services. Each block sets up a /<service> alias so that users may type that instead of a full /msg command. Some might argue this is a bit more secure as well :)

<pre>Command
{
cmd = "<alias name>";
service = "<target>";
prefix = "<anything to prepend to the message>";
};</pre>

If <code> prefix = "";</code> is given, then ircd-darenet will prefix the specified string to whatever the user inputs before sending it to the service.

Example blocks:

<c>Command
{
cmd = "AUTH";
service = "NickServ@services.darenet.org";
prefix = "AUTH";
};</c>

<c>Command
{
cmd = "NICKSERV";
service = "NickServ@services.darenet.org";
};</c>

== Forward Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| b:line
|}

Forward {} blocks enable the server to forward any messages which are prefixed and specific with a Forward {} block. This allows users to use Services' fantasy commands without a service client being in the channel (provided the channel is registered). This also removes the need for ChanServ to monitor channel traffic (e.g. allowing the use of umode +d).

<pre>Forward
{
"<prefix>" = "<server>";
};</pre>

Example block:

<c>Forward
{
"." = "services.darenet.org";
"?" = "services.darenet.org";
};</c>

== Redirect Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| R:line
|}
When a client connects and his/her host matches a Redirect {} block, then a 010 reply is sent back to the client with the redirection server and port.

Currently only EPIC supports auto redirection when it gets a 010 reply (e.g. it will automatically connect to the server specified in the 010 reply). Other clients will get a message specifying what server and port to connect to. as well as an unauthorized disconnect.

<pre>Redirect
{
mask = "<mask>";
server = "<redirection server>";
port = "<redirection port>";
};</pre>

<c>Redirect
{
mask = "*.aol.com";
server = "irc.aol.com";
port = "6667";
};</c>

== Spoofhost Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| S:line
|}

Spoofhost {} blocks allows clients/opers to spoof their host.

<pre>Spoofhost "<spoof host>"
{
pass = "<password>";
host = "<*.host.cc|a.b.c.*|CIDR>";
username = "<ident>";
};</pre>

* <spoof host> - The spoofed hostname.
* <pass> - A password for this spoof host. Used if SETHOST_USER is set to TRUE.
* <host> - A hostmask to match against users that are to be auto-spoofed. Used if SETHOST_AUTO is set to TRUE. Can be in the form of: host.domain.cc, 127.0.0.1 or 127.0.0.0/24, supports wildcards for non-CIDR.
* <username> - A mask for matching against the user's ident reply.

Example block:

<c>Spoofhost "sline.darenet.org"
{
pass = "anygoodpass";
host = "127.0.0.1";
username = "*";
};</c>

== DNSBL Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| X:line
|}

DNSBL {} blocks allow you to prevent clients connecting who are listed on DNS blacklists. Their connection will be rejected during the connection process along with the name and reason you give for the DNSBL they have been matched on.

<pre>DNSBL
{
server = "<dnsbl.site.org>";
name = "<name>";
flags = "<flags>";
replies = "<replies/mask>";
reply = "<rejection message>";
rank = "<rank>";
};</pre>

Available flags:

* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.
* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.
* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels.
* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.
* m (Mark Hostname) - Mark the hostname of a skipped client

The name option is used for the Mark Hostname flag, and may only contain hostname valid characters only (e.g. NO spaces). With Reply DNSBL's you need to list the replies in a comma separated list. See below for an example. With Bitmask DNSBL's, again, specify the replies you need to match for. The server will sum them up and match them against the DNSBL reply. The rejected user's nick, username, ip, and host can be placed into the rejection message by using these codes:

* %n - Nickname
* %u - Username
* %h - Hostname
* %i - IP Address

The rank number must be unique over all DNSBL {} blocks. The higher the number, the greater precedence it has. The highest ranking DNSBL {} block which is a matched against a user will get its name marked in the hostname.

Notes: MAKE SURE you read the DNSBL website before you go ahead and use it as they may have rules for large sites/servers who use them. If you do not wish to use DNSBL checking then simply do not create any DNSBL {} blocks.

Example blocks:

Reply DNSBL:
<c>DNSBL
{
server = "dnsbl.sorbs.net";
name = "sorbs.net";
flags = "r";
replies = "1,2,3,4";
reply = "%n!%u@%h Found On Sorbs DNSBL http://www.dnsbl.us.sorbs.net/cgi-bin/lookup?IP=%i";
rank = "1";
};</c>

Bitmask DNSBL:
<c>DNSBL
{
server = "dnsbl.dnsbl.net";
name = "dnsbl.net";
flags = "b";
replies = "1,3,5";
reply = "%n!%u@%h Found On DNSBL";
rank = "2";
};</c>

== WebIRC Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| W:line
|}

WebIRC {} blocks allow you display the real hostname of users connecting via CGI:IRC clients and sites such as Mibbit.com. These clients will send a WEBIRC command along with the user's hostname, ip and WebIRC {} block password to the server. The password needs to be encrypted like Operator {} block passwords. When the ircd receives the command, instead of using the hostname of the site the users is connecting from, the hostname sent in WEBIRC will be set. All this is done before the client enters the network completely. Please remember to enclose the description using quotes otherwise things will break.

<pre>WebIRC
{
mask = "<mask>";
pass = "<password>";
flags = "<flags>";
ident = "<ident>";
desc = "<description>";
};</pre>

Available flags:

* m - Marks each client connected via the WebIRC {} block using the provided description.
* s - Sets the ident specified in the ident field for each WEBIRC client.
* u - Uses the ident from USER that the WEBIRC client sends.

Note: Do not use both s and u, only choose one of them.

Example:

<c>WebIRC
{
mask = "*@webchat.darenet.org";
pass = "VRKLKuGKn0jLs";
flags = "ms";
ident = "webirc";
desc = "DareNET WebChat";
};</c>

== SpamFilter Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| -
|}

This is probably the most controversial addition to ircd-darenet 1.3.x; however, sadly, it may become useful.

SpamFiler {} blocks allow you to filter PRIVMSG's, NOTICE's, TOPIC's and AWAY's for spam. The filtering is done using regular expressions, so please be careful.

<pre>SpamFilter {
regex = "<regex>";
rtype = "<watch flags>";
action = "<action flags>";
reason = "<reason>";
channel = "<optional alert channel>";
length = <length in seconds>;
};</pre>

* <regex> - PCRE format regular expression to match against.
* <watch flags> - See below for a list.
* <action flags> - See below for a list.
* <reason> - Used in error messages displayed to the user and/or kills/shuns/glines/zlines.
* <optional alert channel> - Requires the C action flag.
* <length in seconds> - Only applies to glines, zlines and shuns.

Available watch flags:

* n - Notices.
* N - Channel notices.
* p - Privmsgs.
* C - Channel privmsgs.
* q - Quits.
* P - Parts.
* d - DCCs.
* a - Away messages.
* t - Topics.
* u - Connects (nick!user@host:gecos).
* i - Nickname changes.

Available action flags:

* a - Auth. If used, logged in clients will be exempt from the filter.
* C - Channel alert. If used, filter matches will be sent to what is set in the SpamFilter {} block channel setting.
* S - Server (snotice) alert.
* k - Kill anyone who matches the filter.
* g - Gline anyone who matches the filter. The length can be given in seconds.
* z - Zline anyone who matches the filter. The length can be given in seconds. This zlines *@ip, so you do not need the i action flag.
* s - Shun anyone who matches the filter. The length can be given in seconds.
* i - Uses the client's IP vice host in a Gline/Shun.
* b - Block; will prevent the PRIVMSG/NOTICE/TOPIC/AWAY from going through.
* n - Notify; will notify the person matching the filter, stating they've matched a filter, and deny their message.
* m - Mark; will mark the client as being a spam source.
* K - Kick; will kick the user triggering the Spam Filter. The kick reason given will be the reason set in the Spam Filter. This Flag will only work with the N and C watch flags.
* o - Ops/HalfOps; exempts ops and halfops from any checks which have a channel target.
* v - Voice; exempts voiced users from any checks which have a channel target.

Notes:

* Shuns and Glines will be set using *@hostname. If you would them to be set using *@ip use the 'i' action flag.
* If you do not specify a length, then FILTER_DEFAULT_LENGTH will be used.
* The 'b' action flag cannot be used with the 'u' watch flag. You will need to use a kill flag to block them.

== Features Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| SUGGESTED
|-
| Old conf format equivalents:
| F:line
|}

ircd-darenet has a large number of options and features, most of which can be configured using a Features {} block. If linking to DareNET, your Features {} block will be rather bare, since most DareNET-specific settings have been already defined in the source.

<pre>Features
{
"featurename" = "value";
"featurename2" = "value2";
};</pre>

You only need one Features {} block, in which you use "featurename" = "value1";, "featurename2" = "value2";, and so on. Please note all values, whether integers or strings, must be enclosed in double quotes.

See the [[Server_Features|servers features]] page for a list of available features.

Example block:

<c>Features
{
"LOG" = "SYSTEM" "FILE" "ircd.log";
"LOG" = "SYSTEM" "LEVEL" "CRIT";
"HUB" = "FALSE";
};</c>

[[Category:IRCd]]

DareNET IRCd Configuration/1.5

2013-06-17T17:58:22Z

Nitemare: /* General block */

__NOTOC__
This is a reference guide for ircd-darenet 1.5.x's configuration file.

The configuration format consists of various blocks, each containing name-value pairs, tags or string data. It is designed to be easily readable by both human ircd.

A block consists of a name, an opening '{' brace, statements, a closing '}' brace, and a ';' semicolon. A statement consists of a name possibly followed by an '=' equals sign and a value, ending with a semicolon. All strings must be surrounded by '"' double quotes.

A sample block:

<html><pre>blockname {
name = value;
name = "string";
name = 123;
tag;
};</pre></html>

All elements of the configuration are separated by whitespace, and can be packed on one line, or broken up over several lines. Whitespace is defined as space, tab or carriage return/linefeed. Three forms of comments are allowed:

<pre>/* C style single/multi-line */

// C++ style single-line

# Shell style single-line
</pre>

{{info|text=Blocks are used in the reverse order than how they're listed, when the configuration file is parsed. This means you should start multiple block definitions with the "fall through", and end with the most detailed.}}

== General block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>M:name:vhost:description::numeric</code>
|}

The General block defines information about the server itself. It is required for the server to start.

<html><pre>General {
/* name: the name of our server. */
name = "test.area.zone.darenet.org";

/* description: the description of our server. */
description = "ircd-darenet test server";

/* numeric: the unique server numeric for our server. It must be a
* digit between 0 and 4095, and is not updated on a rehash.
*/
numeric = 999;

/* ssl_private_key: our ssl private key. */
ssl_private_key = "etc/ircd.key";

/* ssl_pem: file containing our ssl certificate and private key */
ssl_pem = "etc/ircd.pem";

/* dpass: (optional) password for DIE command. */
dpass = "encrypted pass";

/* rpass: (optional) password for RESTART command. */
rpass = "$PLAIN$password";
};
</pre></html>

The server name may only be changed by a server restart. The description can be changed on rehash, but will not propagate to other linked servers.

There must be exactly one General block.

== Admin block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>A:line1:line2:line3</code>
|}

The Admin block defines information that can be retrieved with the <code>/ADMIN</code> command.

<html><pre>Admin {
location = "DareNET - http://www.darenet.org";
location = "Infrastructure Team";
contact = "<infrastructure@darenet.org>";
};
</pre></html>

Not all lines are required. There may only be one Admin block.

== Class block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>Y:class:pingfreq::maxlinks:sendq (clients)</code> <code>Y:class:pingfreq:connectfreq:maxlinks:sendq (servers)</code>
|-
|}

The Class blocks define connection classes. All connections to the server are associated with a "connection class", whether they be incoming or outgoing (initiated by the server), be they clients or servers.

<html><pre>Class {
/* name: a name for the connection class. */
name = "Users";

/* pingfreq: how often to PING idle connections. */
pingfreq = 1 minute 30 seconds;

/* sendq: send buffer limit (i.e., the amount of data allowed in
* a client's queue before they are dropped.
*/
sendq = 100 kilobytes;

/* maxlinks: the maximum number of connections that may use this
* class. May be between 0 and 4,000,000,000.
*/
maxlinks = 100;

/* usermode: an optional list of user modes that should set
* upon the user while connecting.
*/
usermode = "+iw";

/* maxchans: the maximum number of channels that clients may join.
*/
maxchans = 50;
};

Class {
name = "Opers";
pingfreq = 2 minutes;
sendq = 100 kilobytes;
maxlinks = 10;
usermode = "+iw";
whox;
};

Class {
name = "Server";
pingfreq = 3 minutes;

/* connectfreq: this token applies only to servers, and specifies
* the frequency that the server tries to auto connect. Setting this to 0 will cause a
* server to attempt to connect repeatedly, with no delay until the maxlinks condition
* is satisfied (which is not a good thing).
*/
connectfreq = 5 minutes;

/* maxlinks: for server classes, specifies the maximum number of
* servers to autoconnect to. This should be 0 for hubs, and 1 for leafs.
*/
maxlinks = 0;

sendq = 10 megabytes;
};

Class {
name = "Leaf_Server";
pingfreq = 3 minutes;
connectfreq = 5 minutes;
maxlinks = 1;
sendq = 10 megabytes;
};
</pre></html>

For connection classes intended for operator use, you can specify privileges the operator should be granted when the Operator block names the class. The local privilege MUST be defined by either the Class or Operator block. It is highly recommended that most privileges be explicitly specified in the operator's Operator block on DareNET.

A "default" class is created internally. This class is used when no other class is specified, but its settings are not useful for most situations. Custom classes are strongly recommended.

There may be multiple Class blocks; at least one is recommended.

== Client block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>I:ipmask:passwd:hostmask:port:class</code>
|}

The Client blocks define the hosts client connections are allowed from, and places them into classes. While the server will start without a Client block, it will not be usable.

<html><pre>Client {
/* host: resolved user@host mask allowed to connect. This is optional
* if you are using the ip mask to match against. Additionally, if you specify *@loc for
* this field it will match all LOC users.
*/
host = "*@*.wirehub.net";

/* ip: unresolved user@ip mask allowed to connect. */
ip = "*@195.86.128.*";

/* password: (optional) password that is required to use this block.
* This password string is not encrypted.
*/
password = "letMEHin";

/* class: the class the user should be placed in. */
class = "Users";

/* maxlinks: if specified, the server will only accept clients when
* the total number of connections to the network from the same IP number doesn't exceed
* this number.
*/
maxlinks = 6;

/* port: (optional) a port to limit this block to. */
port = 6660;
};
</pre></html>

The server uses a default deny policy for incoming connections. You need to define at least one Client block if you wish to use your server.

The <code>host</code> and <code>ip</code> fields specify which connections the block matches. The server always performs a DNS and ident lookup for connections. If DNS cannot find a hostname, the IP address is used instead. If ident cannot get a valid reply, "unknown" is used during this state. The client's resolved hostname, IP address, ident reply, and username (from the USER line) are used according to the results of the matches described below.

'''Note:''' There is a specify case for UNIX domain sockets and localhost connections. In these cases, the <code>ip / host</code> field is compared with the name of the server, and thus not with any IP number representation. The name of the server is that returned in the numeric 002 reply, example: <code>002 Your host is 2.darenet.org[jolan.ppro]. running version ...</code> In this example, "jolan.ppro" is the name used for matching; therefore, UNIX domain sockets and connections to localhost would match a block containing: <code>host = "*@jolan.ppro";</code>.

The <code>host</code> field attempts to match first against the resolved hostname, if available, and then against the IP address. To include the connection's ident reply in the match, use a mask in the form "ident@host". If a client matches, it appears on IRC using its resolved hostname.

The <code>ip</code> field attempts to match against the IP address only. An ident may be specified to match against, as well.

'''Note:''' If the ident portion is specified in a mask (i.e., "ident@host" instead of "host"), and no ident reply is received from the client, it will appear on IRC with its username prefixed with a '~' tilde. If the matching mask used only the "host" form, the client's username is not prefixed. If a valid ident reply is received, it is always used and not prefixed.

You need only specify a <code>host</code> or <code>ip</code> field, not both. If both are used, <code>host</code> is matched against first.

There may be multiple Client blocks; at least one is recommended.

== Motd block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>T:hostmask|classnumber:path</code>
|}

The Motd blocks allow a different Message of the Day to be shown to connecting clients based on their origin.

<html><pre>Motd {
/* host: a hostmask, class number or class name to match against. */
host = "*.jp";

/* file: the path to the MOTD file to be shown (relative to DPATH). */
file = "jp.motd";
};
</pre></html>

More then one <code>host</code> field may be present in an Motd block.

There may be multiple Motd blocks.

== Connect block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>C:host:cpassword:name:port:class</code> <code>N:host:apassword:name:flags:class</code> <code>H:host::name:maxhops</code> <code>L:host::mask:depth</code>
|}

The Connect blocks define links to other servers.

<html><pre>Connect {
/* name: the name of the server. */
name = "uplink.darenet.org";

/* host: the host or IP to connect to. If a hostname is used it
* must match the reverse dns of the server.
*/
host = "192.168.0.1";

/* vhost: (optional) the host or IP to bind to for this connection.
* If this is not specified, the default vhost (in general {}) is used.
*/
#vhost = "192.168.0.50";

/* password: the password we send and accept. */
password = "somepass";

/* port: the port to connect to this server on. This is also the
* port used when the server attempts to auto-connect (if enabled).
*/
port = 7325;

/* class: the class this server should be placed in. */
class = "Server";

/* maxhops: the max number of hops a hub may introduce. If a hub
* tries to introduce servers farther away than what is specified here, an SQUIT is
* issued. The 'leaf' token is an alias for "maxhops = 0;".
*/
maxhops = 2;

/* hub: (optional) the mask of servers that this server may hub
* for. The tag 'hub' is an alias for 'hub = "*";'.
*/
hub = "*.us.darenet.org";

/* autoconnect: (optional) determines if we should try to
* automatically connect to this server. The default is to autoconnect.
*/
autoconnect = no;
};
</pre></html>

There may be multiple Connect blocks.

== CRule block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>D:servermask::rule</code> <code>d:servermask::rule</code>
|}

The CRule (connection rule) blocks control ircd-darenet's advanced, real-time rule-based routing decision making system.

<html><pre>CRule {
/* server: rules will be applied towards servers matching this mask. */
server = "*.eu.darenet.org";

/* rule: the connection rule. */
rule = "connected(amsterdam.eu.*)";

/* all: (optional) setting this to 'yes' will make the rule always
* apply; otherwise, it only applies to autoconnects.
*/
all = yes;
};
</pre></html>

If more than one server mask is present in a single crule, the rule will apply to all servers.

See doc/readme.crules for more information on the crule system, including examples of allowed rules.

There may be multiple CRule blocks.

== Port Block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>P:hostmask:interface:<[CES][H]>:port</code>
|}

The Port blocks define where the server will accept connections. At least one port block is required to start.

<html><pre>Port {
/* port: the specific port to listen on. */
port = 7325;

/* mask: (optional) the IP address (or a range of IP addresses) that
* the server will allow connections from.
*/
mask = "127.0.*.*";

/* vhost: (optional) set a specific IP/host the port (listed after
* the 'port' token) will listen for.
*/
vhost = "127.0.0.1";

/* server: setting this to yes makes this a server only port. */
server = yes;

/* hidden: (optional) setting this to 'yes' makes the port
* "hidden" from stats replies.
*/
hidden = yes;

/* crypt: (optional) setting this to 'yes' makes the port accept
* SSL connections.
*/
crypt = yes;

/* exempt: (optional) setting this to 'yes' makes the port exempt
* from connection restrictions during a timed /RESTART or /DIE.
*/
exempt = no;
};
</pre></html>

The <code>mask</code> field should only contain IP addresses (CIDR notation is supported) or '*', if used. This does not use DNS in any way, so you cannot use it to allow *.dk or *.uk, for example. Attempting to specify anything other than IP addresses will result in the port allowing connections from anyone (as if you used '*').

If the <code>vhost</code> field (i.e., bind address) is not specified, the server will listen on all available interfaces for that port.

There may be multiple Port blocks.

== Operator block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>O:host:password:name:flags:class</code> <code>o:host:password:name:flags:class</code>
|}

The Operator blocks define server operators. One or more of these blocks is recommended if you intend to maintain your server.

<html><pre>Operator {
/* name: the oper's username. */
name = "johndoe";

/* host: the user@host/IP mask required for this operator. CIDR
* notation is supported. Multiple host="" lines are supported.
*/
host = "god@*";
host = "*@127.0.0.1";

/* password: the password required to oper. By default, the password is
* hashed using the system's native crypt() function. Other password
* mechanisms are available; the umkpasswd utility located in the ircd
* directory can hash passwords using those mechanisms. If you use a
* password format that is not generated by umkpasswd, ircd-darenet will
* not recognize the oper's password.
*/
password = "/home/irc/keys/johndoe.key";

/* flags: misc options for the oper. */
flags = "OAWInFR";

/* snomask: (optional) specific server notice mask on oper up. If this
* is specified, an oper will not be given sno_default.
*/
snomask = "+cegGiKorRs";

/* privileges: (optional) you can specify privileges an oper will be
* explicitly granted (or denied) upon opering. Any privileges defined
* will override any privilege settings that may be present in the class
* block specified above, and the default setting for those privileges.
*/
local = no; routing = yes; routeinfo = yes;
};
</pre></html>

The <code>name</code> and <code>password</code> fields match the parameters of the <code>OPER</code> command. To authenticate as an IRC operator, a client must match one of the <code>host</code> fields, which may be a resolved hostname or IP address.

To use an unencrypted password, prefix the password with '$PLAIN', e.g., "$PLAIN$aPpLe".

If you want to use a more secure password authentication system, generate a 1024bit RSA key, and specify the path to the key as the password (as shown in the example above), and add 'R' to the <code>flags</code> field. This will use the <code>/CHALLENGE</code> system instead of <code>/OPER</code>. See doc/challenge.txt for more details.

A client may also use their SSL client certificate fingerprint to authenticate as an IRC operator. To use this method, specify the client's certificate fingerprint as the password, and add 'S' to the <code>flags</code> field.

Only one password authentication method may be used at a time. That is, you cannot use <code>CHALLENGE</code> and SSL client certificate fingerprint at the same time.

There are currently 9 different oper flags:
* o - Local operator
* O - Global operator
* A - Server administrator
* r - This operator block may be used from remote servers
* W - Allowed to set user mode +W
* I - Allowed to set user mode +I
* n - Allowed to set user mode +n
* F - Allowed to set user mode +F
* S - Use SSL client certificate fingerprint to <code>/OPER</code>
* R - Use <code>/CHALLENGE</code> password authentication system.
* j - Allowed to use juped nicknames.

The <code>class</code> field specifies the connection class the client will be placed in, regardless of their previous connection class. If not specified, the default class is used; see the Class block description for details.

There may be multiple Operator blocks.

== UWorld block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The Uworld block defines "U-lined" servers, which are allowed to do special network things. Used for network services.

<html><pre>UWorld {
/* name: the server name or wildcard mask the "U-line" applies to. */
name = "services.darenet.org";
name = "stats.darenet.org";
};
</pre></html>

UWorld servers are permitted to do things typical network services would want to do, such as apply network bans, manage channel modes, etc; the details are too numerous and complex to provide here.

There may be multiple UWorld blocks; all blocks are combined into one list.

== NickJupe block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The NickJupe blocks disallow certain nicknames from being used.

<html><pre>NickJupe {
"ChanServ" = "Reserved for Services";
"NickS?rv" = "Reserved for Services";
};
</pre></html>

Entries are specified in a key-value format, with the key being the nick to disallow (the '*' and '?' wildcards are supported), and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice).

There may be multiple NickJupe blocks; all blocks are combined into one list.

== Quarantine block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>Q:channel:reason</code>
|}

The Quarantine blocks disallow certain channel names from being used by non-opers.

<html><pre>Quarantine {
"#help" = "For assistance, please join #Support instead.";
};
</pre></html>

Entries are specified in a key-value format, with the key being the channel to disallow, and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice). Note, these are only checked at <code>/JOIN</code>, so if you add a channel and rehash, users will not be kicked if they're already in the channel.

There may be multiple Quarantine blocks; all blocks are combined into one list.

== Ban Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| K:line
|}

Ban {} blocks disallow connections from clients based on specific ident, host and/or gecos masks. They are a flexible general client ban mechanism.

<pre>Ban
{
host = "user@host";
reason = "The reason the user will see";
klineprompt;
name = "mark";
};</pre>

'''Required tokens (at least one of):''' <code>host, realname, username</code>

'''Optional tokens:''' <code>klineprompt, reason, name, file</code>

If <code>klineprompt;</code> is present, users may bypass the ban by using Login-on-Connect (LOC). You can also mark clients by using <code>name = "mark here";</code>

<pre>Ban
{
realname = "realname here";
reason = "The reason the user will see";
};</pre>

It is also possible to ban based on username.

<pre>Ban
{
username = "username here";
reason = "The reason the user will see";
};</pre>

It is also possible to use a file as comment for the ban, using.

<pre>Ban
{
host = "user@host";
file = "path/to/file/with/reason/to/show";
};</pre>

The file can contain for example, a reason, a link to the server rules and a contact address. Also, note the combination of username and host in the host field. IP-based Ban {} blocks apply to all hosts, even if an IP address has a properly resolving host name. CIDR format is the most efficient, and should be used when possible. The server will attempt to convert wildcard IP masks to CIDR form internally.

Additionally, you may specify a hostmask prefixed with $V to indicate a match should be performed against the CTCP version of the user rather han the host/IP.

<pre>Ban
{
version = "string";
reason = "reason here";
};</pre>

There may be multiple Ban {} blocks.

'''Example blocks:'''

<c>Ban
{
host = "*@*.aol.com";
reason = "Due to abuse, AOL users must login with their DareNET account to connect.";
klineprompt;
};</c>

<c>Ban
{
host = "192.168.*";
reason = "Monkeys.";
};</c>

<c>Ban
{
host = "192.168.0.0/16";
reason = "Monkeys.";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

== Except Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| E:line
|}

Except {} blocks can be used to exempt a user from Kill {} blocks, GLINEs, ZLINEs, SHUNs, spam filters, IDENT_CHALLENGE and LIST restrictions.

<pre>Except
{
mask = "<mask>";
flags = "<flags>";
};</pre>

<mask> is an ident@ip/host/cidr mask that is to match the user to be exempted. <flags> is one or more of the following flags to specify what the exempt is to match.

* k - Except affects KLINEs.
* g - Except affects GLINEs.
* i - Except affects ident challenges (see IDENT_CHALLENGE feature).
* n - Except for notilde.
* s - Except affects SHUNs.
* z - Except affects ZLINEs.
* F - Forces umode +F on user to bypass message flood checks.
* I - Exempts user from rapid (re)connection throttling & clone checks.
* L - Except affects LIST restrictions.
* N - Exempts user from "no connections" restrictions, allowing them to connect anyway.
* S - Except affects spam filters.

NOTE: For throttling/clone exemptions (I), only IP addresses are supported, since these checks are performed before any DNS resolutions or identd replies are received.
NOTE: For notilde (n), IP/Host is required.

Example block:

<c>Except
{
mask = "*@*.darenet.org";
flags = "kgzsL";
};</c>

<c>Except
{
mask = "*@127.0.0.1";
flags = "I";
};</c>

== Command Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| B:line
|}

Command {} blocks aim to improve the generic IRC users ability to use network services. Each block sets up a /<service> alias so that users may type that instead of a full /msg command. Some might argue this is a bit more secure as well :)

<pre>Command
{
cmd = "<alias name>";
service = "<target>";
prefix = "<anything to prepend to the message>";
};</pre>

If <code> prefix = "";</code> is given, then ircd-darenet will prefix the specified string to whatever the user inputs before sending it to the service.

Example blocks:

<c>Command
{
cmd = "AUTH";
service = "NickServ@services.darenet.org";
prefix = "AUTH";
};</c>

<c>Command
{
cmd = "NICKSERV";
service = "NickServ@services.darenet.org";
};</c>

== Forward Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| b:line
|}

Forward {} blocks enable the server to forward any messages which are prefixed and specific with a Forward {} block. This allows users to use Services' fantasy commands without a service client being in the channel (provided the channel is registered). This also removes the need for ChanServ to monitor channel traffic (e.g. allowing the use of umode +d).

<pre>Forward
{
"<prefix>" = "<server>";
};</pre>

Example block:

<c>Forward
{
"." = "services.darenet.org";
"?" = "services.darenet.org";
};</c>

== Redirect Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| R:line
|}
When a client connects and his/her host matches a Redirect {} block, then a 010 reply is sent back to the client with the redirection server and port.

Currently only EPIC supports auto redirection when it gets a 010 reply (e.g. it will automatically connect to the server specified in the 010 reply). Other clients will get a message specifying what server and port to connect to. as well as an unauthorized disconnect.

<pre>Redirect
{
mask = "<mask>";
server = "<redirection server>";
port = "<redirection port>";
};</pre>

<c>Redirect
{
mask = "*.aol.com";
server = "irc.aol.com";
port = "6667";
};</c>

== Spoofhost Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| S:line
|}

Spoofhost {} blocks allows clients/opers to spoof their host.

<pre>Spoofhost "<spoof host>"
{
pass = "<password>";
host = "<*.host.cc|a.b.c.*|CIDR>";
username = "<ident>";
};</pre>

* <spoof host> - The spoofed hostname.
* <pass> - A password for this spoof host. Used if SETHOST_USER is set to TRUE.
* <host> - A hostmask to match against users that are to be auto-spoofed. Used if SETHOST_AUTO is set to TRUE. Can be in the form of: host.domain.cc, 127.0.0.1 or 127.0.0.0/24, supports wildcards for non-CIDR.
* <username> - A mask for matching against the user's ident reply.

Example block:

<c>Spoofhost "sline.darenet.org"
{
pass = "anygoodpass";
host = "127.0.0.1";
username = "*";
};</c>

== DNSBL Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| X:line
|}

DNSBL {} blocks allow you to prevent clients connecting who are listed on DNS blacklists. Their connection will be rejected during the connection process along with the name and reason you give for the DNSBL they have been matched on.

<pre>DNSBL
{
server = "<dnsbl.site.org>";
name = "<name>";
flags = "<flags>";
replies = "<replies/mask>";
reply = "<rejection message>";
rank = "<rank>";
};</pre>

Available flags:

* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.
* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.
* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels. (Bypass LOC requirements)
* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.
* m (Mark Hostname) - Mark the hostname of a skipped client

The name option is used for the Mark Hostname flag, and may only contain hostname valid characters only (e.g. NO spaces). With Reply DNSBL's you need to list the replies in a comma separated list. See below for an example. With Bitmask DNSBL's, again, specify the replies you need to match for. The server will sum them up and match them against the DNSBL reply. The rejected user's nick, username, ip, and host can be placed into the rejection message by using these codes:

* %n - Nickname
* %u - Username
* %h - Hostname
* %i - IP Address

The rank number must be unique over all DNSBL {} blocks. The higher the number, the greater precedence it has. The highest ranking DNSBL {} block which is a matched against a user will get its name marked in the hostname.

Notes: MAKE SURE you read the DNSBL website before you go ahead and use it as they may have rules for large sites/servers who use them. If you do not wish to use DNSBL checking then simply do not create any DNSBL {} blocks.

Example blocks:

Reply DNSBL:
<c>DNSBL
{
server = "dnsbl.sorbs.net";
name = "sorbs.net";
flags = "r";
replies = "1,2,3,4";
reply = "%n!%u@%h Found On Sorbs DNSBL http://www.dnsbl.us.sorbs.net/cgi-bin/lookup?IP=%i";
rank = "1";
};</c>

Bitmask DNSBL:
<c>DNSBL
{
server = "dnsbl.dnsbl.net";
name = "dnsbl.net";
flags = "b";
replies = "1,3,5";
reply = "%n!%u@%h Found On DNSBL";
rank = "2";
};</c>

== WebIRC Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| W:line
|}

WebIRC {} blocks allow you display the real hostname of users connecting via CGI:IRC clients and sites such as Mibbit.com. These clients will send a WEBIRC command along with the user's hostname, ip and WebIRC {} block password to the server. The password needs to be encrypted like Operator {} block passwords. When the ircd receives the command, instead of using the hostname of the site the users is connecting from, the hostname sent in WEBIRC will be set. All this is done before the client enters the network completely. Please remember to enclose the description using quotes otherwise things will break.

<pre>WebIRC
{
mask = "<mask>";
pass = "<password>";
flags = "<flags>";
ident = "<ident>";
desc = "<description>";
};</pre>

Available flags:

* m - Marks each client connected via the WebIRC {} block using the provided description.
* s - Sets the ident specified in the ident field for each WEBIRC client.
* u - Uses the ident from USER that the WEBIRC client sends.

Note: Do not use both s and u, only choose one of them.

Example:

<c>WebIRC
{
mask = "*@webchat.darenet.org";
pass = "VRKLKuGKn0jLs";
flags = "ms";
ident = "webirc";
desc = "DareNET WebChat";
};</c>

== SpamFilter Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| -
|}

This is probably the most controversial addition to ircd-darenet 1.3.x; however, sadly, it may become useful.

SpamFiler {} blocks allow you to filter PRIVMSG's, NOTICE's, TOPIC's and AWAY's for spam. The filtering is done using regular expressions, so please be careful.

<pre>SpamFilter {
regex = "<regex>";
rtype = "<watch flags>";
action = "<action flags>";
reason = "<reason>";
channel = "<optional alert channel>";
length = <length in seconds>;
};</pre>

* <regex> - PCRE format regular expression to match against.
* <watch flags> - See below for a list.
* <action flags> - See below for a list.
* <reason> - Used in error messages displayed to the user and/or kills/shuns/glines/zlines.
* <optional alert channel> - Requires the C action flag.
* <length in seconds> - Only applies to glines, zlines and shuns.

Available watch flags:

* n - Notices.
* N - Channel notices.
* p - Privmsgs.
* C - Channel privmsgs.
* q - Quits.
* P - Parts.
* d - DCCs.
* a - Away messages.
* t - Topics.
* u - Connects (nick!user@host:gecos).
* i - Nickname changes.

Available action flags:

* a - Auth. If used, logged in clients will be exempt from the filter.
* C - Channel alert. If used, filter matches will be sent to what is set in the SpamFilter {} block channel setting.
* S - Server (snotice) alert.
* k - Kill anyone who matches the filter.
* g - Gline anyone who matches the filter. The length can be given in seconds.
* z - Zline anyone who matches the filter. The length can be given in seconds. This zlines *@ip, so you do not need the i action flag.
* s - Shun anyone who matches the filter. The length can be given in seconds.
* i - Uses the client's IP vice host in a Gline/Shun.
* b - Block; will prevent the PRIVMSG/NOTICE/TOPIC/AWAY from going through.
* n - Notify; will notify the person matching the filter, stating they've matched a filter, and deny their message.
* m - Mark; will mark the client as being a spam source.
* K - Kick; will kick the user triggering the Spam Filter. The kick reason given will be the reason set in the Spam Filter. This Flag will only work with the N and C watch flags.
* o - Ops/HalfOps; exempts ops and halfops from any checks which have a channel target.
* v - Voice; exempts voiced users from any checks which have a channel target.

Notes:

* Shuns and Glines will be set using *@hostname. If you would them to be set using *@ip use the 'i' action flag.
* If you do not specify a length, then FILTER_DEFAULT_LENGTH will be used.
* The 'b' action flag cannot be used with the 'u' watch flag. You will need to use a kill flag to block them.

== Features Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| SUGGESTED
|-
| Old conf format equivalents:
| F:line
|}

ircd-darenet has a large number of options and features, most of which can be configured using a Features {} block. If linking to DareNET, your Features {} block will be rather bare, since most DareNET-specific settings have been already defined in the source.

<pre>Features
{
"featurename" = "value";
"featurename2" = "value2";
};</pre>

You only need one Features {} block, in which you use "featurename" = "value1";, "featurename2" = "value2";, and so on. Please note all values, whether integers or strings, must be enclosed in double quotes.

See the [[Server_Features|servers features]] page for a list of available features.

Example block:

<c>Features
{
"LOG" = "SYSTEM" "FILE" "ircd.log";
"LOG" = "SYSTEM" "LEVEL" "CRIT";
"HUB" = "FALSE";
};</c>

[[Category:IRCd]]

Staff:Reference Guide

2013-06-13T15:39:51Z

Nitemare:

__NOTOC__A quick reference guide.

== Channels ==

{| class="srvcscmd" width="100%" style="font-size: 95%;"
|-
|width="500px" |Max entries C user lists
| 200
|-
| Max entries C lamers lists
| 100
|-
| Max length channel greetings
| 120 characters
|-
| Max length user infoline
| 400 characters
|-
| Time a user must remain outside of channel before showing infoline again
| 30 seconds
|-
| Max number of channels a user may join
| 50
|-
| Max entries channel ban lists
| 100
|-
| Max length of topic and kick messages
| 250 characters
|-
| Max channels a user may register
| Up to 15 channels on a single account
|-
| Minimum access level needed to set C notes
| See <code class="scmd">/msg C HELP NOTE TYPES</code>
|-
| Can non-oper view a channel's ban list from outside channel?
| No
|-
| How to view a channel's creation date?
| Use <code class="scmd">/mode #channelname</code> - may not necessarily match a channel's registration date
|-
| How to remove O from a channel?
| Contact an IRC operator
|-
| When do channels expire?
| Automatically after 30 days of inactivity, if channel is not flagged as ''nodelete''
|}

== Users ==

{| class="srvcscmd" width="100%" style="font-size: 95%;"
|-
|width="500px" |How often can user change their account password?
| Once every 3 days
|-
| What is the hard limit for max logins?
| 4
|-
| When do cookies expire?
| 24 hours, or when used. Whichever comes first.
|-
| Max length for account names
| 15 characters.
|-
| Max length for nicknames
| 30 characters
|-
| Max length for away messages
| 250 characters
|-
| When do accounts expire?
| They don't
|-
| When do nicknames expire?
| Automatically after 30 days of inactivity, if account not flagged as ''vacation/nodelete''
|-
| How often can a user change their title?
| Once every 14 days
|-
| How to check what clients are logged into an account?
| Use N's <code class="scmd">STATUS</code> command
|-
| How to check number of nicknames registered to an account?
| Use N's <code class="scmd">STATUS</code> command
|-
| How to check if a user is eligible to change their title?
| Use N's <code class="scmd">STATUS</code> command
|-
|}

== Miscellaneous ==

{| class="srvcscmd" width="100%" style="font-size: 95%;"
|-
|width="500px" |Max clients allowed from a single IP/Host
| 5, anything over requires a trust
|-
| Duration for G-lines set for exceeding session limit
| 30 minutes
|-
| Duration of gags (services ignore) set for failed auth attempts
| 30 minutes
|-
| Who can see other helpers' stats?
| Support trainers and higher
|-
| What does O's <code class="scmd">BLOCK</code> command do?
| Places a 1 hour G-line on a host matching the user given.
|-
| What is #staff?
| Our official staff channel. All staff are required to idle in this channel.
|-
| How to check the duration of a G-line manually?
| Type <code class="scmd">/gline *@IP</code> Then use <code class="scmd">/OperServ UTIME <long_number_you_get></code> mIRC users could also use: <code class="scmd">//echo $asctime(long_number_you_get)</code>
|-
| Is DareNET's IRCu and Srvx patches/modifications publicly available?
| No
|}

[[Category:Staff Documentation|Reference Guide]]

DareNET IRCd Configuration/1.5

2012-12-06T21:29:27Z

Nitemare: /* DNSBL Block */

__NOTOC__
This is a reference guide for ircd-darenet 1.5.x's configuration file.

The configuration format consists of various blocks, each containing name-value pairs, tags or string data. It is designed to be easily readable by both human ircd.

A block consists of a name, an opening '{' brace, statements, a closing '}' brace, and a ';' semicolon. A statement consists of a name possibly followed by an '=' equals sign and a value, ending with a semicolon. All strings must be surrounded by '"' double quotes.

A sample block:

<html><pre>blockname {
name = value;
name = "string";
name = 123;
tag;
};</pre></html>

All elements of the configuration are separated by whitespace, and can be packed on one line, or broken up over several lines. Whitespace is defined as space, tab or carriage return/linefeed. Three forms of comments are allowed:

<pre>/* C style single/multi-line */

// C++ style single-line

# Shell style single-line
</pre>

{{info|text=Blocks are used in the reverse order than how they're listed, when the configuration file is parsed. This means you should start multiple block definitions with the "fall through", and end with the most detailed.}}

== General block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>M:name:vhost:description::numeric</code>
|}

The General block defines information about the server itself. It is required for the server to start.

<html><pre>General {
/* name: the name of our server. */
name = "test.area.zone.darenet.org";

/* description: the description of our server. */
description = "ircd-darenet test server";

/* numeric: the unique server numeric for our server. It must be a
* digit between 0 and 4095, and is not updated on a rehash.
*/
numeric = 999;

/* vhost: the IP to bind to when we connect outward to other servers.
* It must contain either a * or a valid ipv4 address in dotted quad notation.
*/
vhost = "192.169.0.1";

/* ssl_private_key: our ssl private key. */
ssl_private_key = "etc/ircd.key";

/* ssl_pem: file containing our ssl certificate and private key */
ssl_pem = "etc/ircd.pem";

/* dpass: (optional) password for DIE command. */
dpass = "encrypted pass";

/* rpass: (optional) password for RESTART command. */
rpass = "$PLAIN$password";
};
</pre></html>

The server name may only be changed by a server restart. The description can be changed on rehash, but will not propagate to other linked servers.

There must be exactly one General block.

== Admin block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>A:line1:line2:line3</code>
|}

The Admin block defines information that can be retrieved with the <code>/ADMIN</code> command.

<html><pre>Admin {
location = "DareNET - http://www.darenet.org";
location = "Infrastructure Team";
contact = "<infrastructure@darenet.org>";
};
</pre></html>

Not all lines are required. There may only be one Admin block.

== Class block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>Y:class:pingfreq::maxlinks:sendq (clients)</code> <code>Y:class:pingfreq:connectfreq:maxlinks:sendq (servers)</code>
|-
|}

The Class blocks define connection classes. All connections to the server are associated with a "connection class", whether they be incoming or outgoing (initiated by the server), be they clients or servers.

<html><pre>Class {
/* name: a name for the connection class. */
name = "Users";

/* pingfreq: how often to PING idle connections. */
pingfreq = 1 minute 30 seconds;

/* sendq: send buffer limit (i.e., the amount of data allowed in
* a client's queue before they are dropped.
*/
sendq = 100 kilobytes;

/* maxlinks: the maximum number of connections that may use this
* class. May be between 0 and 4,000,000,000.
*/
maxlinks = 100;

/* usermode: an optional list of user modes that should set
* upon the user while connecting.
*/
usermode = "+iw";

/* maxchans: the maximum number of channels that clients may join.
*/
maxchans = 50;
};

Class {
name = "Opers";
pingfreq = 2 minutes;
sendq = 100 kilobytes;
maxlinks = 10;
usermode = "+iw";
whox;
};

Class {
name = "Server";
pingfreq = 3 minutes;

/* connectfreq: this token applies only to servers, and specifies
* the frequency that the server tries to auto connect. Setting this to 0 will cause a
* server to attempt to connect repeatedly, with no delay until the maxlinks condition
* is satisfied (which is not a good thing).
*/
connectfreq = 5 minutes;

/* maxlinks: for server classes, specifies the maximum number of
* servers to autoconnect to. This should be 0 for hubs, and 1 for leafs.
*/
maxlinks = 0;

sendq = 10 megabytes;
};

Class {
name = "Leaf_Server";
pingfreq = 3 minutes;
connectfreq = 5 minutes;
maxlinks = 1;
sendq = 10 megabytes;
};
</pre></html>

For connection classes intended for operator use, you can specify privileges the operator should be granted when the Operator block names the class. The local privilege MUST be defined by either the Class or Operator block. It is highly recommended that most privileges be explicitly specified in the operator's Operator block on DareNET.

A "default" class is created internally. This class is used when no other class is specified, but its settings are not useful for most situations. Custom classes are strongly recommended.

There may be multiple Class blocks; at least one is recommended.

== Client block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>I:ipmask:passwd:hostmask:port:class</code>
|}

The Client blocks define the hosts client connections are allowed from, and places them into classes. While the server will start without a Client block, it will not be usable.

<html><pre>Client {
/* host: resolved user@host mask allowed to connect. This is optional
* if you are using the ip mask to match against. Additionally, if you specify *@loc for
* this field it will match all LOC users.
*/
host = "*@*.wirehub.net";

/* ip: unresolved user@ip mask allowed to connect. */
ip = "*@195.86.128.*";

/* password: (optional) password that is required to use this block.
* This password string is not encrypted.
*/
password = "letMEHin";

/* class: the class the user should be placed in. */
class = "Users";

/* maxlinks: if specified, the server will only accept clients when
* the total number of connections to the network from the same IP number doesn't exceed
* this number.
*/
maxlinks = 6;

/* port: (optional) a port to limit this block to. */
port = 6660;
};
</pre></html>

The server uses a default deny policy for incoming connections. You need to define at least one Client block if you wish to use your server.

The <code>host</code> and <code>ip</code> fields specify which connections the block matches. The server always performs a DNS and ident lookup for connections. If DNS cannot find a hostname, the IP address is used instead. If ident cannot get a valid reply, "unknown" is used during this state. The client's resolved hostname, IP address, ident reply, and username (from the USER line) are used according to the results of the matches described below.

'''Note:''' There is a specify case for UNIX domain sockets and localhost connections. In these cases, the <code>ip / host</code> field is compared with the name of the server, and thus not with any IP number representation. The name of the server is that returned in the numeric 002 reply, example: <code>002 Your host is 2.darenet.org[jolan.ppro]. running version ...</code> In this example, "jolan.ppro" is the name used for matching; therefore, UNIX domain sockets and connections to localhost would match a block containing: <code>host = "*@jolan.ppro";</code>.

The <code>host</code> field attempts to match first against the resolved hostname, if available, and then against the IP address. To include the connection's ident reply in the match, use a mask in the form "ident@host". If a client matches, it appears on IRC using its resolved hostname.

The <code>ip</code> field attempts to match against the IP address only. An ident may be specified to match against, as well.

'''Note:''' If the ident portion is specified in a mask (i.e., "ident@host" instead of "host"), and no ident reply is received from the client, it will appear on IRC with its username prefixed with a '~' tilde. If the matching mask used only the "host" form, the client's username is not prefixed. If a valid ident reply is received, it is always used and not prefixed.

You need only specify a <code>host</code> or <code>ip</code> field, not both. If both are used, <code>host</code> is matched against first.

There may be multiple Client blocks; at least one is recommended.

== Motd block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>T:hostmask|classnumber:path</code>
|}

The Motd blocks allow a different Message of the Day to be shown to connecting clients based on their origin.

<html><pre>Motd {
/* host: a hostmask, class number or class name to match against. */
host = "*.jp";

/* file: the path to the MOTD file to be shown (relative to DPATH). */
file = "jp.motd";
};
</pre></html>

More then one <code>host</code> field may be present in an Motd block.

There may be multiple Motd blocks.

== Connect block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>C:host:cpassword:name:port:class</code> <code>N:host:apassword:name:flags:class</code> <code>H:host::name:maxhops</code> <code>L:host::mask:depth</code>
|}

The Connect blocks define links to other servers.

<html><pre>Connect {
/* name: the name of the server. */
name = "uplink.darenet.org";

/* host: the host or IP to connect to. If a hostname is used it
* must match the reverse dns of the server.
*/
host = "192.168.0.1";

/* vhost: (optional) the host or IP to bind to for this connection.
* If this is not specified, the default vhost (in general {}) is used.
*/
#vhost = "192.168.0.50";

/* password: the password we send and accept. */
password = "somepass";

/* port: the port to connect to this server on. This is also the
* port used when the server attempts to auto-connect (if enabled).
*/
port = 7325;

/* class: the class this server should be placed in. */
class = "Server";

/* maxhops: the max number of hops a hub may introduce. If a hub
* tries to introduce servers farther away than what is specified here, an SQUIT is
* issued. The 'leaf' token is an alias for "maxhops = 0;".
*/
maxhops = 2;

/* hub: (optional) the mask of servers that this server may hub
* for. The tag 'hub' is an alias for 'hub = "*";'.
*/
hub = "*.us.darenet.org";

/* autoconnect: (optional) determines if we should try to
* automatically connect to this server. The default is to autoconnect.
*/
autoconnect = no;
};
</pre></html>

There may be multiple Connect blocks.

== CRule block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>D:servermask::rule</code> <code>d:servermask::rule</code>
|}

The CRule (connection rule) blocks control ircd-darenet's advanced, real-time rule-based routing decision making system.

<html><pre>CRule {
/* server: rules will be applied towards servers matching this mask. */
server = "*.eu.darenet.org";

/* rule: the connection rule. */
rule = "connected(amsterdam.eu.*)";

/* all: (optional) setting this to 'yes' will make the rule always
* apply; otherwise, it only applies to autoconnects.
*/
all = yes;
};
</pre></html>

If more than one server mask is present in a single crule, the rule will apply to all servers.

See doc/readme.crules for more information on the crule system, including examples of allowed rules.

There may be multiple CRule blocks.

== Port Block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>P:hostmask:interface:<[CES][H]>:port</code>
|}

The Port blocks define where the server will accept connections. At least one port block is required to start.

<html><pre>Port {
/* port: the specific port to listen on. */
port = 7325;

/* mask: (optional) the IP address (or a range of IP addresses) that
* the server will allow connections from.
*/
mask = "127.0.*.*";

/* vhost: (optional) set a specific IP/host the port (listed after
* the 'port' token) will listen for.
*/
vhost = "127.0.0.1";

/* server: setting this to yes makes this a server only port. */
server = yes;

/* hidden: (optional) setting this to 'yes' makes the port
* "hidden" from stats replies.
*/
hidden = yes;

/* crypt: (optional) setting this to 'yes' makes the port accept
* SSL connections.
*/
crypt = yes;

/* exempt: (optional) setting this to 'yes' makes the port exempt
* from connection restrictions during a timed /RESTART or /DIE.
*/
exempt = no;
};
</pre></html>

The <code>mask</code> field should only contain IP addresses (CIDR notation is supported) or '*', if used. This does not use DNS in any way, so you cannot use it to allow *.dk or *.uk, for example. Attempting to specify anything other than IP addresses will result in the port allowing connections from anyone (as if you used '*').

If the <code>vhost</code> field (i.e., bind address) is not specified, the server will listen on all available interfaces for that port.

There may be multiple Port blocks.

== Operator block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>O:host:password:name:flags:class</code> <code>o:host:password:name:flags:class</code>
|}

The Operator blocks define server operators. One or more of these blocks is recommended if you intend to maintain your server.

<html><pre>Operator {
/* name: the oper's username. */
name = "johndoe";

/* host: the user@host/IP mask required for this operator. CIDR
* notation is supported. Multiple host="" lines are supported.
*/
host = "god@*";
host = "*@127.0.0.1";

/* password: the password required to oper. By default, the password is
* hashed using the system's native crypt() function. Other password
* mechanisms are available; the umkpasswd utility located in the ircd
* directory can hash passwords using those mechanisms. If you use a
* password format that is not generated by umkpasswd, ircd-darenet will
* not recognize the oper's password.
*/
password = "/home/irc/keys/johndoe.key";

/* flags: misc options for the oper. */
flags = "OAWInFR";

/* snomask: (optional) specific server notice mask on oper up. If this
* is specified, an oper will not be given sno_default.
*/
snomask = "+cegGiKorRs";

/* privileges: (optional) you can specify privileges an oper will be
* explicitly granted (or denied) upon opering. Any privileges defined
* will override any privilege settings that may be present in the class
* block specified above, and the default setting for those privileges.
*/
local = no; routing = yes; routeinfo = yes;
};
</pre></html>

The <code>name</code> and <code>password</code> fields match the parameters of the <code>OPER</code> command. To authenticate as an IRC operator, a client must match one of the <code>host</code> fields, which may be a resolved hostname or IP address.

To use an unencrypted password, prefix the password with '$PLAIN', e.g., "$PLAIN$aPpLe".

If you want to use a more secure password authentication system, generate a 1024bit RSA key, and specify the path to the key as the password (as shown in the example above), and add 'R' to the <code>flags</code> field. This will use the <code>/CHALLENGE</code> system instead of <code>/OPER</code>. See doc/challenge.txt for more details.

A client may also use their SSL client certificate fingerprint to authenticate as an IRC operator. To use this method, specify the client's certificate fingerprint as the password, and add 'S' to the <code>flags</code> field.

Only one password authentication method may be used at a time. That is, you cannot use <code>CHALLENGE</code> and SSL client certificate fingerprint at the same time.

There are currently 9 different oper flags:
* o - Local operator
* O - Global operator
* A - Server administrator
* r - This operator block may be used from remote servers
* W - Allowed to set user mode +W
* I - Allowed to set user mode +I
* n - Allowed to set user mode +n
* F - Allowed to set user mode +F
* S - Use SSL client certificate fingerprint to <code>/OPER</code>
* R - Use <code>/CHALLENGE</code> password authentication system.
* j - Allowed to use juped nicknames.

The <code>class</code> field specifies the connection class the client will be placed in, regardless of their previous connection class. If not specified, the default class is used; see the Class block description for details.

There may be multiple Operator blocks.

== UWorld block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The Uworld block defines "U-lined" servers, which are allowed to do special network things. Used for network services.

<html><pre>UWorld {
/* name: the server name or wildcard mask the "U-line" applies to. */
name = "services.darenet.org";
name = "stats.darenet.org";
};
</pre></html>

UWorld servers are permitted to do things typical network services would want to do, such as apply network bans, manage channel modes, etc; the details are too numerous and complex to provide here.

There may be multiple UWorld blocks; all blocks are combined into one list.

== NickJupe block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The NickJupe blocks disallow certain nicknames from being used.

<html><pre>NickJupe {
"ChanServ" = "Reserved for Services";
"NickS?rv" = "Reserved for Services";
};
</pre></html>

Entries are specified in a key-value format, with the key being the nick to disallow (the '*' and '?' wildcards are supported), and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice).

There may be multiple NickJupe blocks; all blocks are combined into one list.

== Quarantine block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>Q:channel:reason</code>
|}

The Quarantine blocks disallow certain channel names from being used by non-opers.

<html><pre>Quarantine {
"#help" = "For assistance, please join #Support instead.";
};
</pre></html>

Entries are specified in a key-value format, with the key being the channel to disallow, and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice). Note, these are only checked at <code>/JOIN</code>, so if you add a channel and rehash, users will not be kicked if they're already in the channel.

There may be multiple Quarantine blocks; all blocks are combined into one list.

== Ban Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| K:line
|}

Ban {} blocks disallow connections from clients based on specific ident, host and/or gecos masks. They are a flexible general client ban mechanism.

<pre>Ban
{
host = "user@host";
reason = "The reason the user will see";
klineprompt;
name = "mark";
};</pre>

'''Required tokens (at least one of):''' <code>host, realname, username</code>

'''Optional tokens:''' <code>klineprompt, reason, name, file</code>

If <code>klineprompt;</code> is present, users may bypass the ban by using Login-on-Connect (LOC). You can also mark clients by using <code>name = "mark here";</code>

<pre>Ban
{
realname = "realname here";
reason = "The reason the user will see";
};</pre>

It is also possible to ban based on username.

<pre>Ban
{
username = "username here";
reason = "The reason the user will see";
};</pre>

It is also possible to use a file as comment for the ban, using.

<pre>Ban
{
host = "user@host";
file = "path/to/file/with/reason/to/show";
};</pre>

The file can contain for example, a reason, a link to the server rules and a contact address. Also, note the combination of username and host in the host field. IP-based Ban {} blocks apply to all hosts, even if an IP address has a properly resolving host name. CIDR format is the most efficient, and should be used when possible. The server will attempt to convert wildcard IP masks to CIDR form internally.

Additionally, you may specify a hostmask prefixed with $V to indicate a match should be performed against the CTCP version of the user rather han the host/IP.

<pre>Ban
{
version = "string";
reason = "reason here";
};</pre>

There may be multiple Ban {} blocks.

'''Example blocks:'''

<c>Ban
{
host = "*@*.aol.com";
reason = "Due to abuse, AOL users must login with their DareNET account to connect.";
klineprompt;
};</c>

<c>Ban
{
host = "192.168.*";
reason = "Monkeys.";
};</c>

<c>Ban
{
host = "192.168.0.0/16";
reason = "Monkeys.";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

== Except Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| E:line
|}

Except {} blocks can be used to exempt a user from Kill {} blocks, GLINEs, ZLINEs, SHUNs, spam filters, IDENT_CHALLENGE and LIST restrictions.

<pre>Except
{
mask = "<mask>";
flags = "<flags>";
};</pre>

<mask> is an ident@ip/host/cidr mask that is to match the user to be exempted. <flags> is one or more of the following flags to specify what the exempt is to match.

* k - Except affects KLINEs.
* g - Except affects GLINEs.
* i - Except affects ident challenges (see IDENT_CHALLENGE feature).
* n - Except for notilde.
* s - Except affects SHUNs.
* z - Except affects ZLINEs.
* F - Forces umode +F on user to bypass message flood checks.
* I - Exempts user from rapid (re)connection throttling & clone checks.
* L - Except affects LIST restrictions.
* N - Exempts user from "no connections" restrictions, allowing them to connect anyway.
* S - Except affects spam filters.

NOTE: For throttling/clone exemptions (I), only IP addresses are supported, since these checks are performed before any DNS resolutions or identd replies are received.
NOTE: For notilde (n), IP/Host is required.

Example block:

<c>Except
{
mask = "*@*.darenet.org";
flags = "kgzsL";
};</c>

<c>Except
{
mask = "*@127.0.0.1";
flags = "I";
};</c>

== Command Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| B:line
|}

Command {} blocks aim to improve the generic IRC users ability to use network services. Each block sets up a /<service> alias so that users may type that instead of a full /msg command. Some might argue this is a bit more secure as well :)

<pre>Command
{
cmd = "<alias name>";
service = "<target>";
prefix = "<anything to prepend to the message>";
};</pre>

If <code> prefix = "";</code> is given, then ircd-darenet will prefix the specified string to whatever the user inputs before sending it to the service.

Example blocks:

<c>Command
{
cmd = "AUTH";
service = "NickServ@services.darenet.org";
prefix = "AUTH";
};</c>

<c>Command
{
cmd = "NICKSERV";
service = "NickServ@services.darenet.org";
};</c>

== Forward Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| b:line
|}

Forward {} blocks enable the server to forward any messages which are prefixed and specific with a Forward {} block. This allows users to use Services' fantasy commands without a service client being in the channel (provided the channel is registered). This also removes the need for ChanServ to monitor channel traffic (e.g. allowing the use of umode +d).

<pre>Forward
{
"<prefix>" = "<server>";
};</pre>

Example block:

<c>Forward
{
"." = "services.darenet.org";
"?" = "services.darenet.org";
};</c>

== Redirect Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| R:line
|}
When a client connects and his/her host matches a Redirect {} block, then a 010 reply is sent back to the client with the redirection server and port.

Currently only EPIC supports auto redirection when it gets a 010 reply (e.g. it will automatically connect to the server specified in the 010 reply). Other clients will get a message specifying what server and port to connect to. as well as an unauthorized disconnect.

<pre>Redirect
{
mask = "<mask>";
server = "<redirection server>";
port = "<redirection port>";
};</pre>

<c>Redirect
{
mask = "*.aol.com";
server = "irc.aol.com";
port = "6667";
};</c>

== Spoofhost Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| S:line
|}

Spoofhost {} blocks allows clients/opers to spoof their host.

<pre>Spoofhost "<spoof host>"
{
pass = "<password>";
host = "<*.host.cc|a.b.c.*|CIDR>";
username = "<ident>";
};</pre>

* <spoof host> - The spoofed hostname.
* <pass> - A password for this spoof host. Used if SETHOST_USER is set to TRUE.
* <host> - A hostmask to match against users that are to be auto-spoofed. Used if SETHOST_AUTO is set to TRUE. Can be in the form of: host.domain.cc, 127.0.0.1 or 127.0.0.0/24, supports wildcards for non-CIDR.
* <username> - A mask for matching against the user's ident reply.

Example block:

<c>Spoofhost "sline.darenet.org"
{
pass = "anygoodpass";
host = "127.0.0.1";
username = "*";
};</c>

== DNSBL Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| X:line
|}

DNSBL {} blocks allow you to prevent clients connecting who are listed on DNS blacklists. Their connection will be rejected during the connection process along with the name and reason you give for the DNSBL they have been matched on.

<pre>DNSBL
{
server = "<dnsbl.site.org>";
name = "<name>";
flags = "<flags>";
replies = "<replies/mask>";
reply = "<rejection message>";
rank = "<rank>";
};</pre>

Available flags:

* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.
* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.
* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels. (Bypass LOC requirements)
* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.
* m (Mark Hostname) - Mark the hostname of a skipped client

The name option is used for the Mark Hostname flag, and may only contain hostname valid characters only (e.g. NO spaces). With Reply DNSBL's you need to list the replies in a comma separated list. See below for an example. With Bitmask DNSBL's, again, specify the replies you need to match for. The server will sum them up and match them against the DNSBL reply. The rejected user's nick, username, ip, and host can be placed into the rejection message by using these codes:

* %n - Nickname
* %u - Username
* %h - Hostname
* %i - IP Address

The rank number must be unique over all DNSBL {} blocks. The higher the number, the greater precedence it has. The highest ranking DNSBL {} block which is a matched against a user will get its name marked in the hostname.

Notes: MAKE SURE you read the DNSBL website before you go ahead and use it as they may have rules for large sites/servers who use them. If you do not wish to use DNSBL checking then simply do not create any DNSBL {} blocks.

Example blocks:

Reply DNSBL:
<c>DNSBL
{
server = "dnsbl.sorbs.net";
name = "sorbs.net";
flags = "r";
replies = "1,2,3,4";
reply = "%n!%u@%h Found On Sorbs DNSBL http://www.dnsbl.us.sorbs.net/cgi-bin/lookup?IP=%i";
rank = "1";
};</c>

Bitmask DNSBL:
<c>DNSBL
{
server = "dnsbl.dnsbl.net";
name = "dnsbl.net";
flags = "b";
replies = "1,3,5";
reply = "%n!%u@%h Found On DNSBL";
rank = "2";
};</c>

== WebIRC Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| W:line
|}

WebIRC {} blocks allow you display the real hostname of users connecting via CGI:IRC clients and sites such as Mibbit.com. These clients will send a WEBIRC command along with the user's hostname, ip and WebIRC {} block password to the server. The password needs to be encrypted like Operator {} block passwords. When the ircd receives the command, instead of using the hostname of the site the users is connecting from, the hostname sent in WEBIRC will be set. All this is done before the client enters the network completely. Please remember to enclose the description using quotes otherwise things will break.

<pre>WebIRC
{
mask = "<mask>";
pass = "<password>";
flags = "<flags>";
ident = "<ident>";
desc = "<description>";
};</pre>

Available flags:

* m - Marks each client connected via the WebIRC {} block using the provided description.
* s - Sets the ident specified in the ident field for each WEBIRC client.
* u - Uses the ident from USER that the WEBIRC client sends.

Note: Do not use both s and u, only choose one of them.

Example:

<c>WebIRC
{
mask = "*@webchat.darenet.org";
pass = "VRKLKuGKn0jLs";
flags = "ms";
ident = "webirc";
desc = "DareNET WebChat";
};</c>

== SpamFilter Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| -
|}

This is probably the most controversial addition to ircd-darenet 1.3.x; however, sadly, it may become useful.

SpamFiler {} blocks allow you to filter PRIVMSG's, NOTICE's, TOPIC's and AWAY's for spam. The filtering is done using regular expressions, so please be careful.

<pre>SpamFilter {
regex = "<regex>";
rtype = "<watch flags>";
action = "<action flags>";
reason = "<reason>";
channel = "<optional alert channel>";
length = <length in seconds>;
};</pre>

* <regex> - PCRE format regular expression to match against.
* <watch flags> - See below for a list.
* <action flags> - See below for a list.
* <reason> - Used in error messages displayed to the user and/or kills/shuns/glines/zlines.
* <optional alert channel> - Requires the C action flag.
* <length in seconds> - Only applies to glines, zlines and shuns.

Available watch flags:

* n - Notices.
* N - Channel notices.
* p - Privmsgs.
* C - Channel privmsgs.
* q - Quits.
* P - Parts.
* d - DCCs.
* a - Away messages.
* t - Topics.
* u - Connects (nick!user@host:gecos).
* i - Nickname changes.

Available action flags:

* a - Auth. If used, logged in clients will be exempt from the filter.
* C - Channel alert. If used, filter matches will be sent to what is set in the SpamFilter {} block channel setting.
* S - Server (snotice) alert.
* k - Kill anyone who matches the filter.
* g - Gline anyone who matches the filter. The length can be given in seconds.
* z - Zline anyone who matches the filter. The length can be given in seconds. This zlines *@ip, so you do not need the i action flag.
* s - Shun anyone who matches the filter. The length can be given in seconds.
* i - Uses the client's IP vice host in a Gline/Shun.
* b - Block; will prevent the PRIVMSG/NOTICE/TOPIC/AWAY from going through.
* n - Notify; will notify the person matching the filter, stating they've matched a filter, and deny their message.
* m - Mark; will mark the client as being a spam source.
* K - Kick; will kick the user triggering the Spam Filter. The kick reason given will be the reason set in the Spam Filter. This Flag will only work with the N and C watch flags.
* o - Ops/HalfOps; exempts ops and halfops from any checks which have a channel target.
* v - Voice; exempts voiced users from any checks which have a channel target.

Notes:

* Shuns and Glines will be set using *@hostname. If you would them to be set using *@ip use the 'i' action flag.
* If you do not specify a length, then FILTER_DEFAULT_LENGTH will be used.
* The 'b' action flag cannot be used with the 'u' watch flag. You will need to use a kill flag to block them.

== Features Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| SUGGESTED
|-
| Old conf format equivalents:
| F:line
|}

ircd-darenet has a large number of options and features, most of which can be configured using a Features {} block. If linking to DareNET, your Features {} block will be rather bare, since most DareNET-specific settings have been already defined in the source.

<pre>Features
{
"featurename" = "value";
"featurename2" = "value2";
};</pre>

You only need one Features {} block, in which you use "featurename" = "value1";, "featurename2" = "value2";, and so on. Please note all values, whether integers or strings, must be enclosed in double quotes.

See the [[Server_Features|servers features]] page for a list of available features.

Example block:

<c>Features
{
"LOG" = "SYSTEM" "FILE" "ircd.log";
"LOG" = "SYSTEM" "LEVEL" "CRIT";
"HUB" = "FALSE";
};</c>

[[Category:IRCd]]

DareNET IRCd Configuration/1.5

2012-11-04T01:19:01Z

Nitemare: /* Except Block */

__NOTOC__
This is a reference guide for ircd-darenet 1.5.x's configuration file.

The configuration format consists of various blocks, each containing name-value pairs, tags or string data. It is designed to be easily readable by both human and ircd.

A block consists of a name, an opening '{' brace, statements, a closing '}' brace, and a ';' semicolon. A statement consists of a name possibly followed by an '=' equals sign and a value, ending with a semicolon. All strings must be surrounded by '"' double quotes.

A sample block:

<html><pre>blockname {
name = value;
name = "string";
name = 123;
tag;
};</pre></html>

All elements of the configuration are separated by whitespace, and can be packed on one line, or broken up over several lines. Whitespace is defined as space, tab or carriage return/linefeed. Three forms of comments are allowed:

* C style single/multi-line
* C++ style single-line
* Shell style single-line

'''Important:''' When the configuration file is parsed by the ircd, blocks are used in reverse order than how they are listed. This means you should start multiple block definitions with the "fall through", and end with the most detailed. Keep in mind that Class {} blocks must be specified before anything that uses them. That means they must be defined before Client {}, Connect {} and Operator {} blocks.

Time / duration is written as:
* A number in seconds (e.g., 60)
* A grammatical expression (e.g., 1 hour 30 minutes 10 seconds)
* An arithmetic expression (e.g., 1*60*20)

Valid units of time:
* decade / decades
* year / years
* month / months
* week / weeks
* day / days
* hour / hours
* minute / minutes
* second / seconds

Valid units of size:
* terabyte / terabytes / tbyte
* gigabyte / gigabytes / gbyte
* megabyte / megabytes / mbyte
* kilobyte / kilobytes / kbyte
* byte / bytes

== General block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>M:name:vhost:description::numeric</code>
|}

The General block defines information about the server itself. It is required for the server to start.

<html><pre>General {
/* name: the name of our server. */
name = "test.area.zone.darenet.org";

/* description: the description of our server. */
description = "ircd-darenet test server";

/* numeric: the unique server numeric for our server. It must be a
* digit between 0 and 4095, and is not updated on a rehash.
*/
numeric = 999;

/* vhost: the IP to bind to when we connect outward to other servers.
* It must contain either a * or a valid ipv4 address in dotted quad notation.
*/
vhost = "192.169.0.1";

/* ssl_private_key: our ssl private key. */
ssl_private_key = "etc/ircd.key";

/* ssl_pem: file containing our ssl certificate and private key */
ssl_pem = "etc/ircd.pem";

/* dpass: (optional) password for DIE command. */
dpass = "encrypted pass";

/* rpass: (optional) password for RESTART command. */
rpass = "$PLAIN$password";
};
</pre></html>

The server name may only be changed by a server restart. The description can be changed on rehash, but will not propagate to other linked servers.

There must be exactly one General block.

== Admin block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>A:line1:line2:line3</code>
|}

The Admin block defines information that can be retrieved with the <code>/ADMIN</code> command.

<html><pre>Admin {
location = "DareNET - http://www.darenet.org";
location = "Infrastructure Team";
contact = "<infrastructure@darenet.org>";
};
</pre></html>

Not all lines are required. There may only be one Admin block.

== Class block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>Y:class:pingfreq::maxlinks:sendq (clients)</code> <code>Y:class:pingfreq:connectfreq:maxlinks:sendq (servers)</code>
|-
|}

The Class blocks define connection classes. All connections to the server are associated with a "connection class", whether they be incoming or outgoing (initiated by the server), be they clients or servers.

<html><pre>Class {
/* name: a name for the connection class. */
name = "Users";

/* pingfreq: how often to PING idle connections. */
pingfreq = 1 minute 30 seconds;

/* sendq: send buffer limit (i.e., the amount of data allowed in
* a client's queue before they are dropped.
*/
sendq = 100 kilobytes;

/* maxlinks: the maximum number of connections that may use this
* class. May be between 0 and 4,000,000,000.
*/
maxlinks = 100;

/* usermode: an optional list of user modes that should set
* upon the user while connecting.
*/
usermode = "+iw";

/* maxchans: the maximum number of channels that clients may join.
*/
maxchans = 50;
};

Class {
name = "Opers";
pingfreq = 2 minutes;
sendq = 100 kilobytes;
maxlinks = 10;
usermode = "+iw";
whox;
};

Class {
name = "Server";
pingfreq = 3 minutes;

/* connectfreq: this token applies only to servers, and specifies
* the frequency that the server tries to auto connect. Setting this to 0 will cause a
* server to attempt to connect repeatedly, with no delay until the maxlinks condition
* is satisfied (which is not a good thing).
*/
connectfreq = 5 minutes;

/* maxlinks: for server classes, specifies the maximum number of
* servers to autoconnect to. This should be 0 for hubs, and 1 for leafs.
*/
maxlinks = 0;

sendq = 10 megabytes;
};

Class {
name = "Leaf_Server";
pingfreq = 3 minutes;
connectfreq = 5 minutes;
maxlinks = 1;
sendq = 10 megabytes;
};
</pre></html>

For connection classes intended for operator use, you can specify privileges the operator should be granted when the Operator block names the class. The local privilege MUST be defined by either the Class or Operator block. It is highly recommended that most privileges be explicitly specified in the operator's Operator block on DareNET.

A "default" class is created internally. This class is used when no other class is specified, but its settings are not useful for most situations. Custom classes are strongly recommended.

There may be multiple Class blocks; at least one is recommended.

== Client block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|RECOMMENDED
|-
|Old conf format equivalents:
|<code>I:ipmask:passwd:hostmask:port:class</code>
|}

The Client blocks define the hosts client connections are allowed from, and places them into classes. While the server will start without a Client block, it will not be usable.

<html><pre>Client {
/* host: resolved user@host mask allowed to connect. This is optional
* if you are using the ip mask to match against. Additionally, if you specify *@loc for
* this field it will match all LOC users.
*/
host = "*@*.wirehub.net";

/* ip: unresolved user@ip mask allowed to connect. */
ip = "*@195.86.128.*";

/* password: (optional) password that is required to use this block.
* This password string is not encrypted.
*/
password = "letMEHin";

/* class: the class the user should be placed in. */
class = "Users";

/* maxlinks: if specified, the server will only accept clients when
* the total number of connections to the network from the same IP number doesn't exceed
* this number.
*/
maxlinks = 6;

/* port: (optional) a port to limit this block to. */
port = 6660;
};
</pre></html>

The server uses a default deny policy for incoming connections. You need to define at least one Client block if you wish to use your server.

The <code>host</code> and <code>ip</code> fields specify which connections the block matches. The server always performs a DNS and ident lookup for connections. If DNS cannot find a hostname, the IP address is used instead. If ident cannot get a valid reply, "unknown" is used during this state. The client's resolved hostname, IP address, ident reply, and username (from the USER line) are used according to the results of the matches described below.

'''Note:''' There is a specify case for UNIX domain sockets and localhost connections. In these cases, the <code>ip / host</code> field is compared with the name of the server, and thus not with any IP number representation. The name of the server is that returned in the numeric 002 reply, example: <code>002 Your host is 2.darenet.org[jolan.ppro]. running version ...</code> In this example, "jolan.ppro" is the name used for matching; therefore, UNIX domain sockets and connections to localhost would match a block containing: <code>host = "*@jolan.ppro";</code>.

The <code>host</code> field attempts to match first against the resolved hostname, if available, and then against the IP address. To include the connection's ident reply in the match, use a mask in the form "ident@host". If a client matches, it appears on IRC using its resolved hostname.

The <code>ip</code> field attempts to match against the IP address only. An ident may be specified to match against, as well.

'''Note:''' If the ident portion is specified in a mask (i.e., "ident@host" instead of "host"), and no ident reply is received from the client, it will appear on IRC with its username prefixed with a '~' tilde. If the matching mask used only the "host" form, the client's username is not prefixed. If a valid ident reply is received, it is always used and not prefixed.

You need only specify a <code>host</code> or <code>ip</code> field, not both. If both are used, <code>host</code> is matched against first.

There may be multiple Client blocks; at least one is recommended.

== Motd block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>T:hostmask|classnumber:path</code>
|}

The Motd blocks allow a different Message of the Day to be shown to connecting clients based on their origin.

<html><pre>Motd {
/* host: a hostmask, class number or class name to match against. */
host = "*.jp";

/* file: the path to the MOTD file to be shown (relative to DPATH). */
file = "jp.motd";
};
</pre></html>

More then one <code>host</code> field may be present in an Motd block.

There may be multiple Motd blocks.

== Connect block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>C:host:cpassword:name:port:class</code> <code>N:host:apassword:name:flags:class</code> <code>H:host::name:maxhops</code> <code>L:host::mask:depth</code>
|}

The Connect blocks define links to other servers.

<html><pre>Connect {
/* name: the name of the server. */
name = "uplink.darenet.org";

/* host: the host or IP to connect to. If a hostname is used it
* must match the reverse dns of the server.
*/
host = "192.168.0.1";

/* vhost: (optional) the host or IP to bind to for this connection.
* If this is not specified, the default vhost (in general {}) is used.
*/
#vhost = "192.168.0.50";

/* password: the password we send and accept. */
password = "somepass";

/* port: the port to connect to this server on. This is also the
* port used when the server attempts to auto-connect (if enabled).
*/
port = 7325;

/* class: the class this server should be placed in. */
class = "Server";

/* maxhops: the max number of hops a hub may introduce. If a hub
* tries to introduce servers farther away than what is specified here, an SQUIT is
* issued. The 'leaf' token is an alias for "maxhops = 0;".
*/
maxhops = 2;

/* hub: (optional) the mask of servers that this server may hub
* for. The tag 'hub' is an alias for 'hub = "*";'.
*/
hub = "*.us.darenet.org";

/* autoconnect: (optional) determines if we should try to
* automatically connect to this server. The default is to autoconnect.
*/
autoconnect = no;
};
</pre></html>

There may be multiple Connect blocks.

== CRule block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>D:servermask::rule</code> <code>d:servermask::rule</code>
|}

The CRule (connection rule) blocks control ircd-darenet's advanced, real-time rule-based routing decision making system.

<html><pre>CRule {
/* server: rules will be applied towards servers matching this mask. */
server = "*.eu.darenet.org";

/* rule: the connection rule. */
rule = "connected(amsterdam.eu.*)";

/* all: (optional) setting this to 'yes' will make the rule always
* apply; otherwise, it only applies to autoconnects.
*/
all = yes;
};
</pre></html>

If more than one server mask is present in a single crule, the rule will apply to all servers.

See doc/readme.crules for more information on the crule system, including examples of allowed rules.

There may be multiple CRule blocks.

== Port Block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|REQUIRED
|-
|Old conf format equivalents:
|<code>P:hostmask:interface:<[CES][H]>:port</code>
|}

The Port blocks define where the server will accept connections. At least one port block is required to start.

<html><pre>Port {
/* port: the specific port to listen on. */
port = 7325;

/* mask: (optional) the IP address (or a range of IP addresses) that
* the server will allow connections from.
*/
mask = "127.0.*.*";

/* vhost: (optional) set a specific IP/host the port (listed after
* the 'port' token) will listen for.
*/
vhost = "127.0.0.1";

/* server: setting this to yes makes this a server only port. */
server = yes;

/* hidden: (optional) setting this to 'yes' makes the port
* "hidden" from stats replies.
*/
hidden = yes;

/* crypt: (optional) setting this to 'yes' makes the port accept
* SSL connections.
*/
crypt = yes;

/* exempt: (optional) setting this to 'yes' makes the port exempt
* from connection restrictions during a timed /RESTART or /DIE.
*/
exempt = no;
};
</pre></html>

The <code>mask</code> field should only contain IP addresses (CIDR notation is supported) or '*', if used. This does not use DNS in any way, so you cannot use it to allow *.dk or *.uk, for example. Attempting to specify anything other than IP addresses will result in the port allowing connections from anyone (as if you used '*').

If the <code>vhost</code> field (i.e., bind address) is not specified, the server will listen on all available interfaces for that port.

There may be multiple Port blocks.

== Operator block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|SUGGESTED
|-
|Old conf format equivalents:
|<code>O:host:password:name:flags:class</code> <code>o:host:password:name:flags:class</code>
|}

The Operator blocks define server operators. One or more of these blocks is recommended if you intend to maintain your server.

<html><pre>Operator {
/* name: the oper's username. */
name = "johndoe";

/* host: the user@host/IP mask required for this operator. CIDR
* notation is supported. Multiple host="" lines are supported.
*/
host = "god@*";
host = "*@127.0.0.1";

/* password: the password required to oper. By default, the password is
* hashed using the system's native crypt() function. Other password
* mechanisms are available; the umkpasswd utility located in the ircd
* directory can hash passwords using those mechanisms. If you use a
* password format that is not generated by umkpasswd, ircd-darenet will
* not recognize the oper's password.
*/
password = "/home/irc/keys/johndoe.key";

/* flags: misc options for the oper. */
flags = "OAWInFR";

/* snomask: (optional) specific server notice mask on oper up. If this
* is specified, an oper will not be given sno_default.
*/
snomask = "+cegGiKorRs";

/* privileges: (optional) you can specify privileges an oper will be
* explicitly granted (or denied) upon opering. Any privileges defined
* will override any privilege settings that may be present in the class
* block specified above, and the default setting for those privileges.
*/
local = no; routing = yes; routeinfo = yes;
};
</pre></html>

The <code>name</code> and <code>password</code> fields match the parameters of the <code>OPER</code> command. To authenticate as an IRC operator, a client must match one of the <code>host</code> fields, which may be a resolved hostname or IP address.

To use an unencrypted password, prefix the password with '$PLAIN', e.g., "$PLAIN$aPpLe".

If you want to use a more secure password authentication system, generate a 1024bit RSA key, and specify the path to the key as the password (as shown in the example above), and add 'R' to the <code>flags</code> field. This will use the <code>/CHALLENGE</code> system instead of <code>/OPER</code>. See doc/challenge.txt for more details.

A client may also use their SSL client certificate fingerprint to authenticate as an IRC operator. To use this method, specify the client's certificate fingerprint as the password, and add 'S' to the <code>flags</code> field.

Only one password authentication method may be used at a time. That is, you cannot use <code>CHALLENGE</code> and SSL client certificate fingerprint at the same time.

There are currently 9 different oper flags:
* o - Local operator
* O - Global operator
* A - Server administrator
* r - This operator block may be used from remote servers
* W - Allowed to set user mode +W
* I - Allowed to set user mode +I
* n - Allowed to set user mode +n
* F - Allowed to set user mode +F
* S - Use SSL client certificate fingerprint to <code>/OPER</code>
* R - Use <code>/CHALLENGE</code> password authentication system.
* j - Allowed to use juped nicknames.

The <code>class</code> field specifies the connection class the client will be placed in, regardless of their previous connection class. If not specified, the default class is used; see the Class block description for details.

There may be multiple Operator blocks.

== UWorld block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The Uworld block defines "U-lined" servers, which are allowed to do special network things. Used for network services.

<html><pre>UWorld {
/* name: the server name or wildcard mask the "U-line" applies to. */
name = "services.darenet.org";
name = "stats.darenet.org";
};
</pre></html>

UWorld servers are permitted to do things typical network services would want to do, such as apply network bans, manage channel modes, etc; the details are too numerous and complex to provide here.

There may be multiple UWorld blocks; all blocks are combined into one list.

== NickJupe block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>U:server:jupednicks:*</code>
|}

The NickJupe blocks disallow certain nicknames from being used.

<html><pre>NickJupe {
"ChanServ" = "Reserved for Services";
"NickS?rv" = "Reserved for Services";
};
</pre></html>

Entries are specified in a key-value format, with the key being the nick to disallow (the '*' and '?' wildcards are supported), and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice).

There may be multiple NickJupe blocks; all blocks are combined into one list.

== Quarantine block ==

{| class="simpletable" width="100%"
|width="250px"|Requirement:
|OPTIONAL
|-
|Old conf format equivalents:
|<code>Q:channel:reason</code>
|}

The Quarantine blocks disallow certain channel names from being used by non-opers.

<html><pre>Quarantine {
"#help" = "For assistance, please join #Support instead.";
};
</pre></html>

Entries are specified in a key-value format, with the key being the channel to disallow, and the value being the reason (a single-line reason for the restriction, which is sent to clients along with the rejection notice). Note, these are only checked at <code>/JOIN</code>, so if you add a channel and rehash, users will not be kicked if they're already in the channel.

There may be multiple Quarantine blocks; all blocks are combined into one list.

== Ban Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| K:line
|}

Ban {} blocks disallow connections from clients based on specific ident, host and/or gecos masks. They are a flexible general client ban mechanism.

<pre>Ban
{
host = "user@host";
reason = "The reason the user will see";
klineprompt;
name = "mark";
};</pre>

'''Required tokens (at least one of):''' <code>host, realname, username</code>

'''Optional tokens:''' <code>klineprompt, reason, name, file</code>

If <code>klineprompt;</code> is present, users may bypass the ban by using Login-on-Connect (LOC). You can also mark clients by using <code>name = "mark here";</code>

<pre>Ban
{
realname = "realname here";
reason = "The reason the user will see";
};</pre>

It is also possible to ban based on username.

<pre>Ban
{
username = "username here";
reason = "The reason the user will see";
};</pre>

It is also possible to use a file as comment for the ban, using.

<pre>Ban
{
host = "user@host";
file = "path/to/file/with/reason/to/show";
};</pre>

The file can contain for example, a reason, a link to the server rules and a contact address. Also, note the combination of username and host in the host field. IP-based Ban {} blocks apply to all hosts, even if an IP address has a properly resolving host name. CIDR format is the most efficient, and should be used when possible. The server will attempt to convert wildcard IP masks to CIDR form internally.

Additionally, you may specify a hostmask prefixed with $V to indicate a match should be performed against the CTCP version of the user rather han the host/IP.

<pre>Ban
{
version = "string";
reason = "reason here";
};</pre>

There may be multiple Ban {} blocks.

'''Example blocks:'''

<c>Ban
{
host = "*@*.aol.com";
reason = "Due to abuse, AOL users must login with their DareNET account to connect.";
klineprompt;
};</c>

<c>Ban
{
host = "192.168.*";
reason = "Monkeys.";
};</c>

<c>Ban
{
host = "192.168.0.0/16";
reason = "Monkeys.";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

<c>Ban
{
username = "sub7";
realname = "s*7*";
reason = "You are infected with a Trojan";
};</c>

== Except Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| E:line
|}

Except {} blocks can be used to exempt a user from Kill {} blocks, GLINEs, ZLINEs, SHUNs, spam filters, IDENT_CHALLENGE and LIST restrictions.

<pre>Except
{
mask = "<mask>";
flags = "<flags>";
};</pre>

<mask> is an ident@ip/host/cidr mask that is to match the user to be exempted. <flags> is one or more of the following flags to specify what the exempt is to match.

* k - Except affects KLINEs.
* g - Except affects GLINEs.
* i - Except affects ident challenges (see IDENT_CHALLENGE feature).
* n - Except for notilde.
* s - Except affects SHUNs.
* z - Except affects ZLINEs.
* F - Forces umode +F on user to bypass message flood checks.
* I - Exempts user from rapid (re)connection throttling & clone checks.
* L - Except affects LIST restrictions.
* N - Exempts user from "no connections" restrictions, allowing them to connect anyway.
* S - Except affects spam filters.

NOTE: For throttling/clone exemptions (I), only IP addresses are supported, since these checks are performed before any DNS resolutions or identd replies are received.
NOTE: For notilde (n), IP/Host is required.

Example block:

<c>Except
{
mask = "*@*.darenet.org";
flags = "kgzsL";
};</c>

<c>Except
{
mask = "*@127.0.0.1";
flags = "I";
};</c>

== Command Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| B:line
|}

Command {} blocks aim to improve the generic IRC users ability to use network services. Each block sets up a /<service> alias so that users may type that instead of a full /msg command. Some might argue this is a bit more secure as well :)

<pre>Command
{
cmd = "<alias name>";
service = "<target>";
prefix = "<anything to prepend to the message>";
};</pre>

If <code> prefix = "";</code> is given, then ircd-darenet will prefix the specified string to whatever the user inputs before sending it to the service.

Example blocks:

<c>Command
{
cmd = "AUTH";
service = "NickServ@services.darenet.org";
prefix = "AUTH";
};</c>

<c>Command
{
cmd = "NICKSERV";
service = "NickServ@services.darenet.org";
};</c>

== Forward Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| b:line
|}

Forward {} blocks enable the server to forward any messages which are prefixed and specific with a Forward {} block. This allows users to use Services' fantasy commands without a service client being in the channel (provided the channel is registered). This also removes the need for ChanServ to monitor channel traffic (e.g. allowing the use of umode +d).

<pre>Forward
{
"<prefix>" = "<server>";
};</pre>

Example block:

<c>Forward
{
"." = "services.darenet.org";
"?" = "services.darenet.org";
};</c>

== Redirect Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| R:line
|}
When a client connects and his/her host matches a Redirect {} block, then a 010 reply is sent back to the client with the redirection server and port.

Currently only EPIC supports auto redirection when it gets a 010 reply (e.g. it will automatically connect to the server specified in the 010 reply). Other clients will get a message specifying what server and port to connect to. as well as an unauthorized disconnect.

<pre>Redirect
{
mask = "<mask>";
server = "<redirection server>";
port = "<redirection port>";
};</pre>

<c>Redirect
{
mask = "*.aol.com";
server = "irc.aol.com";
port = "6667";
};</c>

== Spoofhost Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| S:line
|}

Spoofhost {} blocks allows clients/opers to spoof their host.

<pre>Spoofhost "<spoof host>"
{
pass = "<password>";
host = "<*.host.cc|a.b.c.*|CIDR>";
username = "<ident>";
};</pre>

* <spoof host> - The spoofed hostname.
* <pass> - A password for this spoof host. Used if SETHOST_USER is set to TRUE.
* <host> - A hostmask to match against users that are to be auto-spoofed. Used if SETHOST_AUTO is set to TRUE. Can be in the form of: host.domain.cc, 127.0.0.1 or 127.0.0.0/24, supports wildcards for non-CIDR.
* <username> - A mask for matching against the user's ident reply.

Example block:

<c>Spoofhost "sline.darenet.org"
{
pass = "anygoodpass";
host = "127.0.0.1";
username = "*";
};</c>

== DNSBL Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| X:line
|}

DNSBL {} blocks allow you to prevent clients connecting who are listed on DNS blacklists. Their connection will be rejected during the connection process along with the name and reason you give for the DNSBL they have been matched on.

<pre>DNSBL
{
server = "<dnsbl.site.org>";
name = "<name>";
flags = "<flags>";
replies = "<replies/mask>";
reply = "<rejection message>";
rank = "<rank>";
};</pre>

Available flags:

* b (Bitmask DNSBL) - See your DNSBL provider as to whether you should use this or not.
* r (Reply DNSBL) - See your DNSBL provider as to whether you should use this or not.
* a (Allow Connect) - Allow the client to connect anyway. This could used with a DNSBL whitelist. This could also be used to allow users to still connect, but mark their hosts so that channel ops can easily ban them from their channels.
* d (Deny Connect) - If the user is found on this DNSBL, then they can't connect, even if they are allowed on through another DNSBL {} block.
* m (Mark Hostname) - Mark the hostname of a skipped client

The name option is used for the Mark Hostname flag, and may only contain hostname valid characters only (e.g. NO spaces). With Reply DNSBL's you need to list the replies in a comma separated list. See below for an example. With Bitmask DNSBL's, again, specify the replies you need to match for. The server will sum them up and match them against the DNSBL reply. The rejected user's nick, username, ip, and host can be placed into the rejection message by using these codes:

* %n - Nickname
* %u - Username
* %h - Hostname
* %i - IP Address

The rank number must be unique over all DNSBL {} blocks. The higher the number, the greater precedence it has. The highest ranking DNSBL {} block which is a matched against a user will get its name marked in the hostname.

Notes: MAKE SURE you read the DNSBL website before you go ahead and use it as they may have rules for large sites/servers who use them. If you do not wish to use DNSBL checking then simply do not create any DNSBL {} blocks.

Example blocks:

Reply DNSBL:
<c>DNSBL
{
server = "dnsbl.sorbs.net";
name = "sorbs.net";
flags = "r";
replies = "1,2,3,4";
reply = "%n!%u@%h Found On Sorbs DNSBL http://www.dnsbl.us.sorbs.net/cgi-bin/lookup?IP=%i";
rank = "1";
};</c>

Bitmask DNSBL:
<c>DNSBL
{
server = "dnsbl.dnsbl.net";
name = "dnsbl.net";
flags = "b";
replies = "1,3,5";
reply = "%n!%u@%h Found On DNSBL";
rank = "2";
};</c>

== WebIRC Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| W:line
|}

WebIRC {} blocks allow you display the real hostname of users connecting via CGI:IRC clients and sites such as Mibbit.com. These clients will send a WEBIRC command along with the user's hostname, ip and WebIRC {} block password to the server. The password needs to be encrypted like Operator {} block passwords. When the ircd receives the command, instead of using the hostname of the site the users is connecting from, the hostname sent in WEBIRC will be set. All this is done before the client enters the network completely. Please remember to enclose the description using quotes otherwise things will break.

<pre>WebIRC
{
mask = "<mask>";
pass = "<password>";
flags = "<flags>";
ident = "<ident>";
desc = "<description>";
};</pre>

Available flags:

* m - Marks each client connected via the WebIRC {} block using the provided description.
* s - Sets the ident specified in the ident field for each WEBIRC client.
* u - Uses the ident from USER that the WEBIRC client sends.

Note: Do not use both s and u, only choose one of them.

Example:

<c>WebIRC
{
mask = "*@webchat.darenet.org";
pass = "VRKLKuGKn0jLs";
flags = "ms";
ident = "webirc";
desc = "DareNET WebChat";
};</c>

== SpamFilter Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| OPTIONAL
|-
| Old conf format equivalents:
| -
|}

This is probably the most controversial addition to ircd-darenet 1.3.x; however, sadly, it may become useful.

SpamFiler {} blocks allow you to filter PRIVMSG's, NOTICE's, TOPIC's and AWAY's for spam. The filtering is done using regular expressions, so please be careful.

<pre>SpamFilter {
regex = "<regex>";
rtype = "<watch flags>";
action = "<action flags>";
reason = "<reason>";
channel = "<optional alert channel>";
length = <length in seconds>;
};</pre>

* <regex> - PCRE format regular expression to match against.
* <watch flags> - See below for a list.
* <action flags> - See below for a list.
* <reason> - Used in error messages displayed to the user and/or kills/shuns/glines/zlines.
* <optional alert channel> - Requires the C action flag.
* <length in seconds> - Only applies to glines, zlines and shuns.

Available watch flags:

* n - Notices.
* N - Channel notices.
* p - Privmsgs.
* C - Channel privmsgs.
* q - Quits.
* P - Parts.
* d - DCCs.
* a - Away messages.
* t - Topics.
* u - Connects (nick!user@host:gecos).
* i - Nickname changes.

Available action flags:

* a - Auth. If used, logged in clients will be exempt from the filter.
* C - Channel alert. If used, filter matches will be sent to what is set in the SpamFilter {} block channel setting.
* S - Server (snotice) alert.
* k - Kill anyone who matches the filter.
* g - Gline anyone who matches the filter. The length can be given in seconds.
* z - Zline anyone who matches the filter. The length can be given in seconds. This zlines *@ip, so you do not need the i action flag.
* s - Shun anyone who matches the filter. The length can be given in seconds.
* i - Uses the client's IP vice host in a Gline/Shun.
* b - Block; will prevent the PRIVMSG/NOTICE/TOPIC/AWAY from going through.
* n - Notify; will notify the person matching the filter, stating they've matched a filter, and deny their message.
* m - Mark; will mark the client as being a spam source.
* K - Kick; will kick the user triggering the Spam Filter. The kick reason given will be the reason set in the Spam Filter. This Flag will only work with the N and C watch flags.
* o - Ops/HalfOps; exempts ops and halfops from any checks which have a channel target.
* v - Voice; exempts voiced users from any checks which have a channel target.

Notes:

* Shuns and Glines will be set using *@hostname. If you would them to be set using *@ip use the 'i' action flag.
* If you do not specify a length, then FILTER_DEFAULT_LENGTH will be used.
* The 'b' action flag cannot be used with the 'u' watch flag. You will need to use a kill flag to block them.

== Features Block ==

{| class="wikitable" width="40%" style="font-size: 97%; text-align: left;"
| Requirement:
| SUGGESTED
|-
| Old conf format equivalents:
| F:line
|}

ircd-darenet has a large number of options and features, most of which can be configured using a Features {} block. If linking to DareNET, your Features {} block will be rather bare, since most DareNET-specific settings have been already defined in the source.

<pre>Features
{
"featurename" = "value";
"featurename2" = "value2";
};</pre>

You only need one Features {} block, in which you use "featurename" = "value1";, "featurename2" = "value2";, and so on. Please note all values, whether integers or strings, must be enclosed in double quotes.

See the [[Server_Features|servers features]] page for a list of available features.

Example block:

<c>Features
{
"LOG" = "SYSTEM" "FILE" "ircd.log";
"LOG" = "SYSTEM" "LEVEL" "CRIT";
"HUB" = "FALSE";
};</c>

[[Category:IRCd]]

C/access

2012-10-15T03:13:25Z

Nitemare: Reverted edits by Nitemare (Talk) to last revision by Admin

{{Related commands|[[ChanServ/myaccess|MYACCESS]] [[ChanServ/levels|LEVELS]]}}<div class="cmdsyn">ACCESS <#channel> [nickname|*account]</div>

Shows the user's access level in the channel, and their ''infoline'', should they have one set.

The <code>ACCESS</code> command can also be used to determine if a user is network staff.

If no nickname or account is specified, your own information will be shown.

===Examples===
* <code>/msg ChanServ ACCESS #chat Joe</code>
* <code>/msg ChanServ ACCESS #chat</code>

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

C/access

2012-10-15T03:08:21Z

Nitemare:

{{Services|C - Command: ACCESS}}
{{ServicesDesc2 | syntax = /CS ACCESS <#channel> [nickname<nowiki>|</nowiki>*account]
|main = Shows the user's access level in the channel, and their ''infoline'', should they have one set.
 The <code>ACCESS</code> command can also be used to determine if a user is network staff.
 If no nickname or account is specified, your own information will be shown.
|see = [[C/myaccess|MYACCESS]], [[C/levels|LEVELS]]}}
<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

C/mdelmanager

2012-10-15T02:58:23Z

Nitemare:

{{Services|C - Command: MDELMANAGER}}
{{ServicesDesc2 | syntax = /CS MDELMANAGER <#channel> <pattern>
|main = Deletes all accounts with an access level of MANAGER that match the specified pattern from the channel's user list.
 Where <pattern> is a string, that may contain the <code>*</code> and <code>?</code>, to match account names against.
|see = [[C/clist|MLIST]], [[C/deluser|DELUSER]]}}
<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

C

2012-10-15T02:53:38Z

Nitemare: /* User Management Commands */

C is our channel services bot here on DareNET. It provides numerous features that help automate channel management, prevent channel takeovers and generally make life easier for both users and staff. This document describes the different commands and features that C provides.

== Usage ==

You can communicate with C via private message, or through server-side aliases, as shown below:

* <code>/msg C <nowiki><text></nowiki></code>
* <code>/msg C@services.darenet.org <nowiki><text></nowiki></code>
* <code>/ChanServ <nowiki><text></nowiki></code>
* <code>/CS <nowiki><text></nowiki></code>

C also supports "in-channel" (also known as "fantasy") commands, which is discussed below.

For the purpose of this document, we will be using the first two methods listed, as some IRC clients do not readily support server-side aliases without additional setup and/or client commands. However, you can choose to use any of the above methods.

==In-channel Commands==

As previously mentioned, C supports what we call ''in-channel'' commands. You can use the ''in-channel'' method for just about any of the commands C recognizes. All ''in-channel'' commands directed towards C begin with a period. If a command is given in a channel, and the channel parameter is not given, C will use the name of the channel that the command was used in.

''In-channel'' commands may only be used in registered channels; however, C does not have to reside in the channel for them to work.

'''Example:'''

To illustrate what we're talking about, let's say we have a channel named ''#chat'' and we would like to grant the user ''JoeClient'' op status. Using the ''in-channel'' method, we could achieve this by simply typing the following in ''#chat'':

<code>.OP JoeClient</code>

==User Management Commands==
{| class="srvcscmd" width="100%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[C/access|ACCESS]] Check a user's access level in a channel.
| style="width: 310px;"|[[C/clvl|CLVL]] Change a user's access level.
| style="width: 310px;"|[[C/mdelowner|MDELCOOWNER]] Delete multiple Co-owners.
| style="width: 310px;"|[[C/suspend|SUSPEND]] Suspend a user's access.
|-
| [[C/addcoowner|ADDCOOWNER]] Grant user Co-owner access.
| [[C/clist|CLIST]] List all Co-owners.
| [[C/mdelgrunt|MDELGRUNT]] Delete multiple Grunts.
| [[C/trim|TRIM]] Delete users based on last activity
|-
| [[C/addgrunt|ADDGRUNT]] Grant user Grunt access.
| [[C/deleteme|DELETEME]] Delete yourself from a channel's user list.
| [[C/mdelhop|MDELHOP]] Delete multiple HalfOps.
| [[C/unsuspend|UNSUSPEND]] Restore a suspended user's access.
|-
| [[C/addhop|ADDHOP]] Grant user HalfOp access.
| [[C/delban|DELBAN]] Delete entry from bans list.
| [[C/mdelmanager|MDELMANAGER]] Delete multiple Managers.
| [[C/users|USERS]] View channel's user list.
|-
| [[C/addban|ADDBAN]] Add entry to bans list.
| [[C/deluser|DELUSER]] Delete user from channel's user list.
| [[C/mdelop|MDELOP]] Delete multiple Ops.
| [[C/uset|USET]] Set your user options for a channel.
|-
| [[C/addmanager|ADDMANAGER]] Grant user Manager access.
| [[C/glist|GLIST]] List all Grunts.
| [[C/mlist|MLIST]] View Managers list.
| [[C/wipeinfo|WIPEINFO]] Remove a user's info line.
|-
| [[C/addop|ADDOP]] Grant a user Op access in a channel.
| [[C/giveownership|GIVEOWNERSHIP]] Give away ownership of channel.
| [[C/myaccess|MYACCESS]] List channels you have access in.
| [[C/wlist|WLIST]] List all Owners.
|-
| [[C/addtimedban|ADDTIMEDBAN]] Add entry to bans list that expires.
| [[C/hlist|HLIST]] List all HalfOps.
| [[C/olist|OLIST]] List all Ops.
|
|-
| [[C/adduser|ADDUSER]] A more advanced way of granting access to users.
| [[C/bans|BANS]] View channel's bans list.
| [[C/seen|SEEN]] View last time a user was in the channel.
|
|}

==Channel Management Commands==
{| class="srvcscmd" width="100%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[C/ban|BAN]] Set a ban on a user/host.
| style="width: 310px;"|[[C/events|EVENTS]] List recent activity by channel users.
| style="width: 310px;"|[[C/op|OP]] Grant use Op status (+o).
| style="width: 310px;"|[[C/unbanall|UNBANALL]] Clear channel ban list.
|-
| [[C/dehop|DEHOP]] Remove HalfOp status from user(s).
| [[C/hop|HOP]] Grant user HalfOp status (+h).
| [[C/open|OPEN]] Remove modes/bans preventing you from joining channel.
| [[C/unbanme|UNBANME]] Remove bans matching yourself.
|-
| [[C/delnote|DELNOTE]] Delete a channel note.
| [[C/invite|INVITE]] Invite yourself (or others) into the channel.
| [[C/resync|RESYNC]] Synchronize the channel's member list.
| [[C/unregister|UNREGISTER]] Unregister a channel.
|-
| [[C/deop|DEOP]] Remove Op status from user(s).
| [[C/kick|KICK]] Kick user(s) from channel.
| [[C/register|REGISTER]] Registers a channel to your account.
| [[C/up|UP]] Grant yourself (Half)Op status.
|-
| [[C/devoice|DEVOICE]] Remove Voice status from user(s).
| [[C/kickban|KICKBAN]] Kick + Ban user(s) from channel.
| [[C/set|SET]] Change various channel settings.
| [[C/upall|UPALL]] Grant yourself (Half)Op/Voice status in all channels.
|-
| [[C/down|DOWN]] Remove (Half)Op/Voice status from yourself.
| [[C/mode|MODE]] Manipulate channel's mode settings.
| [[C/topic|TOPIC]] Set (or restore) the channel's topic.
| [[C/voice|VOICE]] Grant user voice status (+v)
|-
| [[C/downall|DOWNALL]] Remove (Half)Op/Voice status in all channels.
| [[C/note|NOTE]] Set a channel note.
| [[C/unban|UNBAN]] Remove entries from channel ban list.
|
|-
|}

==Quote Database Management Commands==
{| class="srvcscmd" width="100%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[ChanServ/addquote|ADDQUOTE]] Add a quote.
| style="width: 310px;"|[[ChanServ/delquote|DELQUOTE]] Delete a quote.
| style="width: 310px;"|[[ChanServ/quote|QUOTE]] View a quote, or search quote database.
| style="width: 310px;"|[[ChanServ/qvote|QVOTE]] Rate a quote.
|-
|}

==Informative / Miscellaneous Commands==
{| class="srvcscmd" width="100%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[ChanServ/command|COMMAND]] View some misc. info about a command.
| style="width: 310px;"|[[ChanServ/info|INFO]] View channel's registration record.
| style="width: 310px;"|[[ChanServ/levels|LEVELS]] List numerical equivalents for named access levels.
| style="width: 310px;"|[[ChanServ/staff|STAFF]] List all network staff (opers+helpers) currently online.
|-
| [[ChanServ/helpers|HELPERS]] List support helpers currently online.
| [[ChanServ/ircops|IRCOPS]] List IRC operators currently online.
| [[ChanServ/peek|PEEK]] View information on a channel's modes, topic and member list.
| [[ChanServ/version|VERSION]] View version information about C.
|-
|}

==Toys==
{| class="srvcscmd" width="100%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[ChanServ/8ball|8BALL]] Ask the magic 8ball a question.
| style="width: 310px;"|[[ChanServ/fml|FML]] Get a random quote from [http://www.fmylife.com www.fmylife.com].
| style="width: 310px;"|[[ChanServ/inspire|INSPIRE]] Get a random inspirational quote.
| style="width: 310px;"|[[ChanServ/pastebin|PASTEBIN]] Paste text to [http://pastebin.com pastebin.com].
|-
| style="width: 310px;"|[[ChanServ/calc|CALC]] Calculate a mathematical expression.
| style="width: 310px;"|[[ChanServ/google|GOOGLE]] Search [http://www.google.com Google].
| style="width: 310px;"|[[ChanServ/isgd|ISGD]] Expands or shortens url for [http://is.gd is.gd].
| style="width: 310px;"|[[ChanServ/twitter|TWITTER]] View tweets via IRC.
|-
| style="width: 310px;"|[[ChanServ/dice|DICE]] Roll the dice.
| style="width: 310px;"|[[ChanServ/guess|GUESS]] Guess the number (between 1 and 100).
| style="width: 310px;"|[[ChanServ/isitdown|ISITDOWN]] Check whether a site is reachable (up) or not (down).
| style="width: 310px;"|[[ChanServ/weather|WEATHER]] Get weather conditions for a location.
|-
|}

[[Category:All]] [[Category:IRC Services]]

Services Usage

2012-10-15T02:52:14Z

Nitemare:

{{Expand|text=page}}

* [[N CertFP Auth]]
* [[Topic Masking Guide|Guide to using C's topic masking feature]]

'''Services Bots:'''

* [[C]] Channel management bot
* [[G]] Global services notification bot
* [[H]] Support ticketing bot
* [[N]] Nickname management bot
* [[S]] Statistical bot
* [[V]] Fake host management bot
* [[MemoServ]]
* [[SpamServ]]

Server Features

2012-10-12T14:31:43Z

Nitemare:

{{NeedUpdate}}

This page documents various features supported by ircd-darenet, most of which can be configured at run-time. While we will make every effort to update this page as new versions of ircd-darenet are released, we cannot guarantee it is 100% accurate or complete. Nonetheless, it can still be a useful reference.

==DOMAINNAME==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| ircd.darenet
|}

This option allows the server administrator to specify what should be consider "local." It is used purely for statistical purposes only. When the IRC command <code>/STATS w</code> or <code>/STATS userload</code> is issued, the server will respond with statistics of how many clients have connected to the server in the last minute, hour and day. It lists these statistics for all connections (including servers), all clients (from anywhere) and also for clients whose hostname ends on the domain you specify here.

So, if you would like to know what the client load on your own domain is, you could specify that domain here. If you are unsure what to do, then you don't need to specify this f-line at all. Whatever you do, do not give an empty string. Also, please note that the string you give should NOT start with a '.' or use quotes.

==RELIABLE_CLOCK==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This option should ONLY be specified as "TRUE" when your system clock is stable and accurate at all times (e.g. within a few seconds). If you are running ntpdate on a regular basis, or an equivalent like xntpd, to keep your system clock synchronized over the network, then you _might_ have an accurate clock; however, this not guaranteed. For example, it is known that xntpd gives unreliable results on linux in some cases.

An unreliable clock is worse than a clock that has a constant offset, because the servers attempt to correct for a constant offset, but do not correct jumps of your system clock! In general, you should SHOULD be running ntpd or equivalent AND make sure it works. On DareNET, this should always be "FALSE" unless a member of the Infrastructure Team has told you otherwise.

==BUFFERPOOL==
{| class="wikitable"
| integer
|-
| '''Default:'''
| 27000000
|}

This option specifies the maximum amount of RAM that your server will allocate for buffering sendQs. Small leafs can use a value as little as 1000000, while large HUBs need to specify a value as high as 20000000. If you run out of memory, clients and/or servers are dropped with the error "Buffer allocation error"; then you will need to increase this number (and install more RAM if appropriate).

If you want a more educated guess for this value then realize that any value is good if you _really_ would rather drop servers and clients than allocate more memory; this will be the case when there is the danger you may run out of memory for other allocations. Even if you run the daemon on a dedicated machine, specifying all of the RAM you have is a bad thing, because running out of memory is a lot worse than dropping clients in a controlled way; if possible you should have memory left for all the internal structures (channels, clients, ban lists, receive buffers) at all times.

On average, clients seem to use 150 bytes of sendQ, but at peak moments this can easily increase to 2032 bytes per client (sendQs are allocated in chunks of 2032 bytes). The maximum possible amount that can be allocated for sendQs is the number of connected clients times whatever you specified as the maximum sendQ in your Y: lines in the ircd.conf file. That value will likely be larger then the amount of RAM you have. The educated guess I talked about earlier would be "number of clients" times * 2048 bytes + "size of net.burst" * n, where "n" is 1 for leafs and up to 5 for HUBs. The "size of net.burst" is about 125 bytes per online client (on the whole network). For large HUBs with 4000 clients on a network with 30,000 users, this results in 27 Mb. Leafs could use 12 Mb. Of course you can use less when you have less than 4000 local clients. This value is in bytes.

==HAS_FERGUSON_FLUSHER==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

If you have a server with a lot of resources available, this option will cause the server to attempt to flush its internal buffers before dropping clients during a net break. Don't define this if you don't know for certain; if you're not careful this can end up rebooting FreeBSD boxes. For more information, refer to freebsd.txt.

==CLIENT_FLOOD==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 1024
|}

Currently, everything that a client sends to a server is read by the server and stored in a buffer (the clients receive queue). The server will process messages from this queue one by one (running over all clients each time). When a client sends new messages faster than they get processed, and the size of its receive buffer reaches this value, the client is dropped with the error "Excess flood." A reasonable value is 1024 bytes. The maximum size is 8000 bytes.

==SERVER_PORT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 7325
|}

When an IRC operator attempts a connect to another server, he or she may not know which port the connect should go to. In ircd-darenet, that operator may use the special port 0, in which case the server will take the port from the Connect block. If no port is specified in the Connect block, then the port specified by this option will be used instead.

==NODEFAULTMOTD==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Each time a client connects to the server, the full Message of the Day (MOTD), as specified by the motd block or file specified by the MPATH option, is sent to the client. The server sends the MOTD even though many clients permit the user to ignore it (e.g. hide it). Therefore, many users never read the MOTD anyway, making it a huge waste of bandwidth. If "TRUE" is specified here, then the server will not send the MOTD to the client by default; instead, it will only inform the client of when the MOTD was last changed, and give them instructions in how to obtain it by typing /MOTD.

==MOTD_BANNER==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| NULL
|}

If the NODEFAULTMOTD option is enabled, then the one-line banner specified here is sent to the client in addition to the instructions , as mentioned above.

==REMOTE_MOTD==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Controls the use of remote message of the day's.

==PROVIDER==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| NULL
|}

This string is added to the 001 numeric prefixed with "via" before the nick. It's used for providing promotional space to providers.

==GEO_LOCATION==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| NULL
|}

This string as added to the 003 numeric, is used for providing the location of the server, e.g. "Los Angeles, CA, United States."

==KILL_IPMISMATCH==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

When a client connects to your server, the IP address of the client is reverse-resolved to obtain a hostname. Then that hostname is resolved to an IP address and compared with the IP address of the client. If they don't match, the client will appear with the IP address instead of the hostname, unless KILL_IPMISMATCH is "TRUE," in which case the client is simply disconnected.

==IDLE_FROM_MSG==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

The IRC command WHOIS gives an idle time for clients. If you want this idle time to be set to zero only when the client sends a PRIVMSG, then you should specify "TRUE" here. If you specify "FALSE," then the idle time will be nullified on all messages except the server PING/PONG.

==HUB==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

All servers of an IRC "network" are connected in a "tree" (no loops). Servers that are only connected to one other server (called the "uplink") are called "leafs"; servers that are connected to more than one other server are called HUBs. If you specify "FALSE" here then your server will prevent itself from accidentally connecting to two servers at once, thus keeping servers in poor network locations from routing traffic. Note that on DareNET, all newly linked servers are
linked as leafs during their test phase, and should specify "FALSE" here.

==WALLOPS_OPER_ONLY==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Setting this option removes the ability for clients that are not IRC operators to see wallops messages.

==NODNS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

If you are playing with the server off-line, and no DNS is available, then long delays occur before the server starts up because it tries to resolve the name given on the M-line (which usually isn't given in /etc/hosts) and for each connecting client. If you specify "TRUE" here, then a call to gethostbyname() will be done only for the real hostname, and the server will not try to resolve clients that connect to "localhost."

Note that other calls to gethostbyname() are still done if you use VIRTUAL_HOST; also note that the server still tries to resolve clients that connect to the real IP address of the server.

==RANDOM_SEED==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| None
|}

When a client connects, the server sends the client a "cookie," consisting of a random number. The client must return the cookie to the server verbatim. This is done to prevent IP spoofing. The cookie is generated by a pseudorandom number generator included in ircd. This generator must be seeded with a phrase that is kept secret, to ensure that the numbers it generates are not easily guessed.

The value given to RANDOM_SEED may be a string of any length.It should not contain any characters that are considered special by the configuration file system, such as ":" or "#"; the string should be at least 8 characters long, but longer strings are better. The RANDOM_SEED may not be retrieved online.

==DEFAULT_LIST_PARAM==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| NULL
|}

The LIST command takes a single optional argument. If given, that argument is either a channel or a filter. If that argument is not given, then by default, <code>/LIST</code> will list all channels on the network. Needless to say, this can generate a large amount of data on large networks with many channels, as well as chewing up a lot of CPU time. Server administrators can therefore set a default filter to be applied to the channel list if the optional argument to LIST is omitted.

==NICKNAMEHISTORYLENGTH==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 800
|}

This value specifies the length of the nick name history list, which is used for <code>/WHOWAS</code> and some nickname chasing in <code>/KILL</code> and <code>/KICK</code>. It uses about 300 to 400 bytes per entry. Note that at a net break, so many clients disappear that the whole "whowas" list is refreshed a few times (unless you make it rather large). A reasonable value is "total number of clients" / 25.

==HOST_HIDING==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This selects whether local users can set umode +x, thus allowing them to hide their hostname if they have also registered and authenticated with N (i.e. they have the ACCOUNT flag set).

==OPERHOST_HIDING==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

When TRUE any oper setting +x will get the hidden host set via HIDDEN_OPERHOST instead of the host set in HIDDEN_HOST.

==HOST_HIDING_STYLE==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 1
|}

Value 1 will use ircu-style hostmasking. Value 2 uses Ultimate IRCd style hostmangling, such as a43sd.a3523f.isp.tld.

==HIDDEN_HOST==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| user.darenet
|}

This selects the suffix for the hidden hostmask (see HOST_HIDING).

==HOST_HIDING_PREFIX==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| DareNET
|}

This selects the suffix for the hidden hostmask style 2.

==HIDDEN_OPERHOST==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| staff.darenet
|}

This selects the suffix for the hidden hostmask for IRC Operators (see OPERHOST_HIDING).

==HIDDEN_IP==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| 127.0.0.1
|}

This selects a fake IP to be shown on <code>/USERIP</code> and <code>/WHO %i</code> when the target has a hidden host (see HOST_HIDING).

==CONNEXIT_NOTICES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This feature controls the generation of server notices when a user connects to or disconnects from the server. Enabling this feature may have a performance impact. If using this feature make sure you take a look at [[Server Notice Masks (SNOMASK)|SNOMASKs]].

==EXTENDED_ACCOUNTS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This enables 'extended' style AC syntax (used by your service to set the account name.) TRUE uses the subcommand parameter R,M,U,C,A,D to do LOC, rename and removal. FALSE uses old style. Set this to TRUE if you're linking to DareNET / using services-darenet, FALSE for other services.

==LOGIN_ON_CONNECT==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This selects whether local clients can specify a service bot login in the connection phase. Read doc/readme.login-on-connect for details.

==DNSBL_LOC_EXEMPT==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This allows a user who has successfully authed to a service using login on connect (above) to bypass a DNSBL rejection if they get a positive result from the earlier check.

==DNSBL_LOC_EXEMPT_N_ONE==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| If you have an account with DareNET's N then you can bypass the DNSBL ban by logging in like this (where Account is your account name and Password is your password):
|}

If DNSBL_LOC_EXEMPT is enabled and a user matches a dnsbl then they will be sent a notice containing the string for this feature.

==DNSBL_LOC_EXEMPT_N_TWO==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| Type \002/QUOTE PASS N Account :Password\002 to connect
|}

If DNSBL_LOC_EXEMPT is enabled and a user matches a dnsbl then they will be sent a notice containing the string for this feature.

==DNSBL_WALLOPS_ONLY==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

If enabled DNSBL filter matches will be alerted to opers via wallops.

==DNSBL_MARK_FAKEHOST==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

If enabled then users who match DNSBL's will be marked.

==LOC_DEFAULT_SERVICE==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| N
|}

This is what nick on IRC the login-on-connect account verification is sent to. Users can override it (to any service that supports it) using 3 param LOC.

==DEFAULT_UMODE==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| +iw
|}

This defines the user modes set when a local user connects. +x should not be included in this setting if using host hiding style 1, since users cannot later remove that flag.

==KILLCHASETIMELIMIT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 30
|}

If a user changes his or her nickname just before an operator issues a <code>/KILL</code>, the <code>/KILL</code> will be changed to follow the user the operator intended to get. This option specifies the time limit, in seconds, for this nickname change; if the user changed his or her nickname more than this many seconds ago, the <code>/KILL</code> will not be changed. Don't
change this unless you really need to.

==MAXCHANNELSPERUSER==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 50
|}

This is the maximum number of channels a user can be in at a time. The "mandatory" value on DareNET is currently 10. Since it only influences the local server when you decrease it, its up to you to decide if you want to use a smaller value. Do not use a larger value however, because it DOES cost more memory and bandwidth on all other servers when you allow users to join more channels simultaneously.

One of the most important reasons to choose a smaller value is the fact that the "GUI" clients tend to stay on every channel they join (they aren't bothered by flooding in other channels). It DOES take your bandwidth however to send all those messages for 10 different channels to all your users.

==AVEXCEPTLEN==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 40
|}

This is the expected average except mask length. Leave it at 40.

==MAXEXCEPTS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| 100
|}

This is the maximum number of excepts a user may set on a given channel.

==CHANNELLEN==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 200
|}

This is the allowed length of locally created channels. It may not be larger than the CHANNELLEN <nowiki>#define</nowiki>. Like the NICKLEN feature, this is intended to ease changes in channel name length across a network.

==AVBANLEN==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 40
|}

This is the expected average ban mask length. Leave it at 40.

==MAXBANS==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 100
|}

This is the maximum number of bans a user may set on a given channel.

==MAXSILES==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 50
|}

This is the maximum number of masks a user can silence at a time. The silence command allows users to filter messages directed at them from certain users or domains, at the source server. Increasing this number allows users to use up more memory with inefficient use of the command. If you're not sure, don't change this.

==MAXACCEPTS==
{| class="wikitable"
| '''Type'''
| binteger
|-
| '''Default:'''
| 50
|}

This is the maximum number of masks a user can accept at a time. The accept command allows users to "always accept" messages directed at them from certain users or domains when they have callerid enabled (umode +g). Increasing this number allows users to use up more memory with inefficient use of the command. If you're not sure, don't change this.

==HANGONGOODLINK==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 300
|}

Ocassionally the net breaks for a short time and it is useful to try to reestablish the same connection faster than CONNECTFREQUENCY would allow, but to keep from trying again on a bad connection, we require that the connection be open for a certain minimum time. The recommended value is 300 seconds.

==HANGONRETRYDELAY==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 10
|}

When attempting to quickly reestablish a connection to a good link, we give the net a few seconds to calm down. This time must be long enough for the other end to also notice that the connection is broken. The recommended value is 10 seconds.

==CONNECTTIMEOUT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 90
|}

<nowiki>Number of seconds to wait for a connect(2) call to complete.</nowiki>

<nowiki>NOTE: this must be at *LEAST* 10. When a client connects, it has CONNECTTIMEOUT - 10 seconds for its host to respond to an ident lookup query and for a DNS lookup to complete. It is recommended that you not change this value, but if you do, consider the fact that users whose clients do not support NOSPOOF will have to type /QUOTE PING <big number> before registration.</nowiki>

==TIMESEC==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 60
|}

This is the maximum idle time for the server. If no messages are received in TIMESEC seconds, PINGFREQUENCY and CONNECTFREQUENCY are checked. Recommended value is 60 seconds.

==MAXIMUM_LINKS==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 1
|}

This is the maximum number of links for the built-in client class 0. Leave this value at 1.

==PINGFREQUENCY==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 120
|}

If the daemon doesn't receive anything from any of its links within PINGFREQUENCY seconds, then the it will attempt to check for an active link with a PING message. If no reply is received within (PINGFREQUENCY * 2) seconds, then the connection will be closed. This value may be overridden by a Y-line in "ircd.conf" if the connection's I- or C-line in "ircd.conf" assigns a specific class to the connection (recommended).

==CONNECTFREQUENCY==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 600
|}
This is the default frequency that the server attempts to reconnect with its uplink server if it is set to auto connect to it. Note that this value is overridden by a Y-line in ircd.conf if the C-lines in ircd.conf assign a specific class to the connection (recommended).

==DEFAULTMAXSENDQLENGTH==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 40000
|}

This is the default value of the maximum sendQ length of Y-line classes (see doc/example.conf for details on Y-lines). You will probably always override this value in your "ircd.conf" with the Y-lines. The given value used to be an often used value for client sendQs.

==GLINEMAXUSERCOUNT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 20
|}

G-lines that affect too many users have to be set with a special command, to prevent accidental G-lines of large blocks of users. This feature sets that particular threshold.

==MPATH==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| ircd.motd
|}

MPATH is the filename (relative to DPATH) or the full path of the "Message of the Day" file. The contents of this file will be sent to every client that connects to the server, after registration.

==OMPATH==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| ircd.opermotd
|}

OMPATH is the filename (relative to DPATH) or the full path of the "Message of the Day" file. The contents of this file will be sent to every operator upon opering.

==RPATH==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| ircd.motd
|}

RPATH is the filename (relative to DPATH) or the full path of the "Remote Message of the Day" file. The contents of this file will be sent to every remote client that issues a <code>/MOTD</code> <your server name>. Only the first three lines are sent, so you might want to keep that in mind while writing the file.

==PPATH==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| ircd.pid
|}

PPATH is the filename (relative to DPATH) or the full path of the "PID" file. It is used for storing the server's process ID so that a ps(1) isn't necessary.

==TPATH==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| ircd.tune
|}

TPATH is the filename (relative to DPATH) or the full path of the tune data file. The file contains user count information for LUSERS so that if the server has to restart etc for any reason they will not loose their max local/global user counts.

==VIRTUAL_HOST==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This option is only needed when you wish to run multiple IRC servers on the same machine, and they must share at least one port. This will require having multiple IP addresses for the machine that will be hosting the servers. If you specify "TRUE" here, you can cause the server to bind to one of these IP addresses. Use the second field of the M-line (the "password" field) to specify the IP address. If you are unsure, change to "FALSE."

==TOS_SERVER==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 0x08
|}

This option is used to specify the type of service that will be requested for connections to other servers. The value may be given as a hexadecimal integer.

==TOS_CLIENT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 0x08
|}

This option is used to specify the type of service that will be requested for connections to users. The value may be given as a hexadecimal integer.

==POLLS_PER_LOOP==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 200
|}

Some of the engines used by the event interface get a number of events from the kernel at once. Since the number retrieved can impact performance, it can be tuned by modifying this value. The engines enforce a lower limit of 20.

==NICKLEN==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 30
|}

This is the allowed length of the nickname length. It may not be larger than the <code>NICKLEN #define</code>, and should usually be the same length. The real purpose of this feature is to permit easy increases in nickname length for a network.

==IRCD_RES_RETRIES==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 2
|}

This is the number of attempts the irc daemon's resolver will have at trying to solicit a response from the DNS server.

==IRCD_RES_TIMEOUT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 4
|}

When a DNS query is sent, the irc daemon's resolver will wait this many seconds for a reply. After this timeout has expired, it will retry again, for as many retries as IRCD_RES_RETRIES allows. This can be cut short by AUTH_TIMEOUT expiring.

==AUTH_TIMEOUT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 9
|}

This is the maximum number of seconds to wait for the ident lookup and the DNS query to succeed. On older (pre 2.10.11.06) servers this was hard coded to 60 seconds.

==IPCHECK_CLONE_LIMIT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 4
|}

The number of times you are allowed to connect within IPCHECK_CLONE_PERIOD seconds before you are considered abusing the server and throttled.

==IPCHECK_CLONE_PERIOD==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 40
|}

The number of seconds you are allowed to connect IPCHECK_CLONE_LIMIT times within before you are considered abusing the server and throttled.

For instance if you set IPCHECK_CLONE_LIMIT to 1, and IPCHECK_CLONE_PERIOD to 10, then a user is only allowed to connect once in 10s, if they connect again within 10s, then they are considered to be connecting too fast and they are throttled.

==IPCHECK_CLONE_DELAY==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 600
|}

The number of seconds grace after restarting the server before the throttle code kicks in. Even if a user connects repetitively during this period, they will never get throttled. This is so after a restart users on a multiuser box can all connect to a server simultaniously without being considered an attack.

==SOCKSENDBUF==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 61440
|}

The send window size used for connections to other servers.

==SOCKRECVBUF==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 61440
|}

The receive window size used for connections to other servers.

==ANNOUNCE_INVITES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

When a channel operator invites a user to their channel, all other opers will be notified of the invite.

==BADCHAN_REASON==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| This channel has been closed
|}

This is the kick reason for users being autokicked from a channel when it has been bad channel glined.

==OPERFLAGS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Extended oper levels can be enabled. Currently this adds support for a Server Administrator oper level, and a few additional privileges granted through oper flags. See example.conf for enabling these on your O:Line if using this feature.

==POLICY_NOTICE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Controls the display of the policy notice for connecting users.

==LOCAL_CHANNELS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

When enabled local channels (& perfix) can be used.

==OPER_LOCAL_CHANNELS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Only opers can create local channels if LOCAL_CHANNELS is enabled.

==OPER_XTRAOP==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Controls the use of the (Quakenet-style) Xtra Op oper mode (+X).

==XTRAOP_CLASS==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| XtraOp
|}

This is the class an oper must be in to use the Xtra Op mode if it is enabled.

==OPER_HIDECHANS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Controls the use of the oper mode for hiding their channels in their WHOIS output.

==OPER_HIDEIDLE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Controls the use of the oper mode for hiding their idle time in their WHOIS output.

==CHECK==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

When enabled an oper is allowed to use the CHECK command.

==CHECK_EXTENDED==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

When enabled extra information will be displayed for opers who are using CHECK on local clients. Extra information like traffic counts.

==OPER_SINGLELETTERNICK==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This limits single letter nicknames to IRC operators only.

==MAX_CHECK_OUTPUT==
{| class="wikitable"
| '''Type'''
| integer
|-
| '''Default:'''
| 1000
|}

Maximum amount of records displayed in any CHECK query.

==CONFIG_OPERCMDS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Several new oper-only features have been added that involve changes to the server<->server protocol. Until the entire network is running the new version, these features cannot be enabled.

This configuration option provides a single switch to prevent the use of these features until the entire network has been upgraded. It is not required that all servers set this to "TRUE" in order for the features to be used.

==HOST_IN_TOPIC==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

When an channel operator changes the channel topic their full nick!ident@host will be displayed for the person who set the topic. This can eliminate people faking other people when setting the topic.

==TIME_IN_TIMEOUT==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This will display the amount of seconds it took for the user to timeout in their Ping Timeout quit message.

==AUTOCHANMODES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

When a user joins a new channel the modes in AUTOCHANMODES_LIST will be automatically set

==AUTOCHANMODES_LIST==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| nt
|}

If AUTOCHANMODES is enabled then any modes in here will be the modes set for new channels upon join. Modes should be added in this format "nt" etc.

==FAKEHOST==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This enables the FAKEHOST command used for fake hosts (duh).

==DEFAULT_FAKEHOST==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| NULL
|}

This is the default fakehost given to users who are connecting to the server. If it is empty or not set then no hostname is set.

==SETHOST==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This enables the <code>/SETHOST</code> command and user mode +h for opers activating Sethosts.

==SETHOST_USER==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This enabled the <code>/SETHOST</code> command and user mode +h for users activating Sethosts with passwords.

==SETHOST_AUTO==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This enables the automatic application of Sethosts on matching idents and hosts.

==SETHOST_FREEFORM==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This enables opers to set new hostnames that do not have a corresponding S: line in the configuration file, as long as the hostname supplied is reasonably valid. The usage of this is logged via SNOTICE.

==REMOTE_OPER==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Allows remote users to oper up remotly witthout requiring an O:Line on the server they are on.

==BOT_CLASS==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| Bots
|}

Defines the class a bot must be on to be able to use +B bot mode.

NOTE: On DareNET, users in this class will also be exempted from <code>/LIST</code> restrictions. Intended for IRC search crawlers (e.g. SearchIRC, netsplit.de, etc).

==OPERMOTD==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Controls the use of the OPERMOTD command.

==FLEXABLEKEYS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Channel key rules over all modes. Eg a user can join a channel with the correct key and be able to get around modes like limit and invite.

==NOTHROTTLE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Completly disables connection throttling.

==CREATE_CHAN_OPER_ONLY==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Only IRC Operators will be able to create new channels.

==CREATE_CHAN_ACC_ONLY==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Only users authenticated to a services account will be able to create new channels.

==RESTARTPASS==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| NULL
|}

This is the password required for a server to actually restart when the RESTART command is used. If the password is empty then no password is required.

==DIEPASS==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| NULL
|}

This is the password required for a server to actually die when the DIE command is used. If the password is empty then no password is required.

==TARGET_LIMITING==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Limits users to a certain amount of targets in the a certain amount of time.

==DNSBL_CHECKS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Enables DNS blacklist checks controlled via X:Lines.

==DNSBL_EXEMPT_CLASS==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| DNSBL_exempt
|}

Anyone in this class is immune to DNSBL checks if they are enabled.

==HIS_IRCOPS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This removes <code>/IRCOPS</code> from users.

==HIS_IRCOPS_SERVERS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes server names in the <code>/IRCOPS</code> output from users.

==HIS_MAP==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/MAP</code> from users.

==HIS_MAP_SCRAMBLED==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Scrambles the MAP output for normal users, removing hubs and U:lined servers.

==HIS_SNOTICES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes server notices from users entirely.

==HIS_SNOTICES_OPER_ONLY==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This prevents users from receiving server notices.

==HIS_SNOTICES_OPER_AND_BOT==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

This removes server notices from non-opers and non-+B users.

==HIS_DESYNCS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes the ability for users to see desynch notices.

==HIS_DEBUG_OPER_ONLY==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes the ability for users to see debug notices.

==HIS_WALLOPS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes operator wallops from users. They can still see wallusers.

==HIS_LINKS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/LINKS</code> from users.

==HIS_LINKS_SCRAMBLED==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

Scrambles the <code>LINKS</code> output for users, removing hubs and U:Lined servers.

==HIS_TRACE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/TRACE</code> from users.

==HIS_SHUN_REASON==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This HIDES the shun reason from the target when a shun is set on them (when TRUE).

==HIS_STATS_WELCOMES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS A</code> from users.

==HIS_STATS_FORWARDS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS b</code> from users.

==HIS_STATS_MAPPINGS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS B</code> from users.

==HIS_STATS_LINKS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS l</code> from users.

==HIS_STATS_MODULES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS L</code> from users.

==HIS_STATS_CONNECT==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS c</code> from users.

==HIS_STATS_GLINES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS g</code> from users.

==HIS_STATS_KLINES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS k</code> from users.

==HIS_STATS_FILTERS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS f</code> from users.

==HIS_STATS_FEATURES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code/STATS F</code> from users.

==HIS_STATS_ACCESS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS i</code> from users.

==HIS_STATS_HISTOGRAM==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS j</code> from users.

==HIS_STATS_JUPES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS J</code> from users.

==HIS_STATS_COMMANDS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS m</code> from users.

==HIS_STATS_OPERATORS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS o</code> from users.

==HIS_STATS_PORTS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS p</code> from users.

==HIS_STATS_QUARAUNTINES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS q</code> from users.

==HIS_STATS_USAGE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS r</code> from users.

==HIS_STATS_REDIRECTIONS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS R</code> from users.

==HIS_STATS_CRULES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS d</code> from users.

==HIS_STATS_EXCEPTIONS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS E</code> from users.

==HIS_STATS_ENGINE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS e</code> from users.

==HIS_STATS_SPOOFHOSTS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS s</code> from users.

==HIS_STATS_SHUNS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS S</code> from users.

==HIS_STATS_LOCALS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS t</code> from users.

==HIS_STATS_MOTDS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS T</code> from users.

==HIS_STATS_UPTIME==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS u</code> from users.

==HIS_STATS_UWORLD==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS U</code> from users.

==HIS_STATS_VSERVERS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS v</code> from users.

==HIS_STATS_USERLOAD==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS w</code> from users.

==HIS_STATS_WEBIRCS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS W</code> from users.

==HIS_STATS_MEMUSAGE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS x</code> from users.

==HIS_STATS_DNSBLS==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS X</code> from users.

==HIS_STATS_CLASSES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS y</code> from users.

==HIS_STATS_MEMORY==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS z</code> from users.

==HIS_STATS_ZLINES==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| TRUE
|}

This removes <code>/STATS Z</code> from users.

==HIS_WHOIS_SERVERNAME==
* '''Type:''' boolean
* '''Default:''' TRUE

This removes server names in replies to <code>/WHOIS</code>.

==HIS_WHOIS_IDLETIME==
* '''Type:''' boolean
* '''Default:''' TRUE

This removes idle time in replies to <code>/WHOIS</code>.

==HIS_WHOIS_LOCALCHAN==
* '''Type:''' boolean
* '''Default:''' TRUE

This removes local channels in replies to <code>/WHOIS</code>.

==HIS_WHO_SERVERNAME==
* '''Type: boolean
* '''Default:''' TRUE

This removes server names in replies to <code>/WHO</code>.

==HIS_WHO_HOPCOUNT==
* '''Type:''' boolean
* '''Default:''' TRUE

This replaces hopcount to a static 3 in replies to <code>/WHO</code>.

==HIS_BANWHO==
* '''Type:''' boolean
* '''Default:''' TRUE

This doesn't show which server set a ban.

==HIS_EXCEPTWHO==
* '''Type:''' boolean
* '''Default:''' TRUE

This doesn't show which server set an except.

==HIS_KILLWHO==
* '''Type:''' boolean
* '''Default:''' TRUE

This doesn't show which server or oper performed a kill.

==HIS_HIDEWHO==
* '''Type:''' boolean
* '''Default:''' TRUE

This doesn't show which server preformed various functions like mode, opmode kick, etc when server preforms..

==HIS_REWRITE==
* '''Type:''' boolean
* '''Default:''' TRUE

This remaps remote numerics to come from the local server.

==HIS_GLINE==
* '''Type:''' boolean
* '''Default:''' TRUE

This will hide the user who performed the gline in the gline message when enabled.

==HIS_USERGLINE==
* '''Type:''' boolean
* '''Default:''' TRUE

This will disable users using the gline command. (If the nessecary options are enabled, users can query the gline list using the gline command).

==HIS_REMOTE==
* '''Type:''' integer
* '''Default:''' 1

This disallows remote queries from non-opers. (*sob!*)

==HIS_USERIP==
* '''Type:''' boolean
* '''Default:''' FALSE

This will hide the IP of a user in the output of a <code>USERIP</code> command. The real IP will be shown for opers.

==HIS_SCRAMBLED_CACHE_TIME==
* '''Type:''' integer
* '''Default:''' 604800

Amount of seconds a split server is cached for before dissapearing off MAPS and LINKS for normal users.

==HIS_NETSPLIT==
* '''Type:''' boolean
* '''Default:''' TRUE

This removes server names in net break sign-offs. Instead they are shown as (*.net *.split).

==HIS_SERVERNAME==
* '''Type:''' string
* '''Default:''' "*.darenet.org"

This is the "name" of the server shown to users on a <code>/WHOIS</code> of another user.

==HIS_SERVERINFO==
* '''Type:''' string
* '''Default:''' "DareNET Client Server"

This is the "info" of the server shown to users on a <code>/WHOIS</code> of another user.

==HIS_URLSERVERS==
* '''Type:''' string
* '''Default:''' "http://www.darenet.org/servers"

This is the URL shown to users when they do a <code>/MAP</code> or <code>/LINKS</code>.

==NETWORK==
* '''Type:''' string
* '''Default:''' "DareNET"

This defines the network name as reported in the 005 "supported features" numeric, and as used by the "Failed to deliver" message.

==URL_CLIENTS==
* '''Type:''' string
* '''Default:''' "http://wiki.darenet.org/index.php/IRC_Clients"

This defines a URL that users may visit to find compatible IRC clients.

==BADUSER_URL==
* '''Type:''' string
* '''Default:''' "http://wiki.darenet.org/index.php/Why_do_I_get_error_Bad_Username"

This defines a URL that users may visit to fix their username/ident when it is invalid.

==NETWORK_REHASH==
* '''Type:''' boolean
* '''Default:''' FALSE

Allow this server to act upon a network-issued /rehash.

==NETWORK_RESTART==
* '''Type:''' boolean
* '''Default:''' FALSE

Allow this server to act upon a network-issued /restart.

==NETWORK_DIE==
* '''Type:''' boolean
* '''Default:''' FALSE

Allow this server to act upon a network-issued /die.

==MAX_CHECK_OUTPUT==
* '''Type:''' integer
* '''Default:''' 1000

The maximum results in a <code>/CHECK</code> response.

==SWHOIS==
* '''Type:''' boolean
* '''Default:''' TRUE

Allows the IRCd to accept <code>SWHOIS</code> commands from services.

==HOST_HIDING_KEY1==
* '''Type:''' string
* '''Default:''' aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW

One of the 3 unique host hiding keys used to encrypt style 2 hidden hosts. These must all be different.

==HOST_HIDING_KEY2==
* '''Type:''' string
* '''Default:''' sdfjkLJKHlkjdkfjsdklfjlkjKLJ

One of the 3 unique host hiding keys used to encrypt style 2 hidden hosts. These must all be different.

==HOST_HIDING_KEY3==
* '''Type:''' string
* '''Default:''' KJklJSDFLkjLKDFJSLKjlKJFlkjS

One of the 3 unique host hiding keys used to encrypt style 2 hidden hosts. These must all be different.

==CTCP_VERSIONING==
* '''Type:''' boolean
* '''Default:''' FALSE

Enables CTCP versioning for clients on connect.

==CTCP_VERSIONING_KILL==
* '''Type:''' boolean
* '''Default:''' FALSE

Kills clients who match specified versions.

==CTCP_VERSIONING_CHAN==
* '''Type:''' boolean
* '''Default:''' FALSE

If enabled version replies will be sent to the channel set for CTCP_VERSIONING_CHANNAME

==CTCP_VERSIONING_CHANNAME==
* '''Type:''' string
* '''Default:''' #opers

Channel where version replies are sent to if CTCP_VERSIONING_CHAN is enabled (See above).

==CTCP_VERSIONING_USEMSG==
* '''Type:''' boolean
* '''Default:''' FALSE

If enabled version replies sent to the channel set for CTCP_VERSIONING_CHANNAME will be sent using privmsgs instead of notices.

==CTCP_VERSIONING_NOTICE==
* '''Type:''' string
* '''Default:''' <nowiki>***</nowiki> Checking your client version

Message sent to clients during the versioning process on connect.

==DEF_ALIST_LIMIT==
* '''Type:''' integer
* '''Default:''' 30

Maximum responses allowed in a ALIST search output.

==ALIST_SEND_FREQ==
* '''Type:''' integer
* '''Default:''' 300

How often (in seconds) ALIST updates are checked across the server.

==ALIST_SEND_DIFF==
* '''Type:''' integer
* '''Default:''' 600

If the last message for the channel is over the current time minus to setting for ALIST_SEND_DIFF then an ALIST update will be sent out to other servers.

==EXEMPT_EXPIRE==
* '''Type:''' integer
* '''Default:''' 172800

If no one has triggered an exempt within this amount of time (in seconds) then the exempt will expire.

==STRICTUSERNAME==
* '''Type:''' boolean
* '''Default:''' TRUE

If enabled then strict ident/username rules will be applied.

==ZLINEMAXUSERCOUNT==
* '''Type:''' integer
* '''Default:''' 20

Maximum amount of users a Z:line can affect when a Z:line is set via <code>/ZLINE</code>. Zlines set via services or servers will not be affected by this rule.

==NICK_DELAY==
* '''Type:''' integer
* '''Default:''' 30

How often a user can change thier nick (in seconds).

==HELP_PACE==
* '''Type:''' integer
* '''Default:''' 5

How often a user can request /HELP (in seconds).

==IPCHECK==
* '''Type:''' boolean
* '''Default:''' TRUE

Controls the clone and throttle detection system in ircd-darenet. If you disable this then the maximum setting in I-lines will not have any effect. You would need to use clone detection systems in the services you use.

==LUSERS_AUTHED==
* '''Type:''' boolean
* '''Default:''' TRUE

If enabled a count of logged in users (e.g., authed to N) will be shown in <code>/LUSERS</code>.

==SHUNMAXUSERCOUNT==
* '''Type:''' integer
* '''Default:''' 20

Maximum amount of users a Shun can affect when a shun is set via <code>/SHUN</code>. Shuns set via services or servers will not be affected by this rule.

==OPER_WHOIS_PARANOIA==
* '''Type:''' boolean
* '''Default:''' TRUE

Allows the use of the W opermode which will show <code>/WHOIS</code> attempts to opers when they are done on themselves. (*ugh*)

==HIS_SHUN_REASON==
* '''Type:''' boolean
* '''Default:''' TRUE

Will prevent the reason from being shown to a user if enabled.

==HIS_USERSHUN==
* '''Type:''' boolean
* '''Default:''' TRUE

Will prevent normal users from getting shun lists via <code>/SHUN</code> if enabled.

==HIS_ZLINE==
* '''Type:''' boolean
* '''Default:''' TRUE

This will hide the user who issued the zline in the zline message when enabled.

==HIS_USERZLINE==
* '''Type:''' boolean
* '''Default:''' TRUE

Will prevent normal users from getting zline lists via <code>/ZLINE</code> if enabled.

==HIS_ZLINE_REASON==
* '''Type:''' boolean
* '''Default:''' TRUE

Will prevent the reason from being shown to a user if enabled.

==IDENT_CHALLENGE==
* '''Type:''' boolean
* '''Default:''' FALSE

If enabled, and a user does not have ident enabled or the server is unable to retrieve a successful response for whatever reason, the user will be challenged with a cookie prompt, similar to the following:

<code>*** Ident broken or disabled, to continue to connect you must type /QUOTE PASS 1623745</code>

==GLINE_URL==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| http://www.darenet.org/gline
|}

Defines the URL shown, in addition to the G-line reason given, when a G-lined user tries to connect.

==ANTI_SPAMBOT==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Enable/disable spam bot checking.

==ANTI_DRONE_FLOOD==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

Enable/disable channel/message flood checking.

==OPER_BYPASS_CALLERID==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

If TRUE, IRC operators will always be able to send private messages/notices to users who have callerid (umode +g) enabled, regardless if they are on the user's ACCEPT list or not.

==NETCHAN_NOTICE==
{| class="wikitable"
| '''Type'''
| boolean
|-
| '''Default:'''
| FALSE
|}

If TRUE, the server will send a notice to users when they join a channel marked as being network-owned. The actual notice sent is defined in NETCHAN_NOTICE_MSG.

==NETCHAN_NOTICE_MSG==
{| class="wikitable"
| '''Type'''
| string
|-
| '''Default:'''
| is an official network channel.
|}

Defines the actual notice sent to users when NETCHAN_NOTICE is enabled.

[[Category:Technical]]

C/levels

2012-10-12T14:04:11Z

Nitemare: moved ChanServ/levels to C/levels

{{Services|C - Command: LEVELS}}
{{ServicesDesc2 | syntax = /CS LEVELS
|main = C can use either the names (OWNER, COOWNER, MANAGER, OP, HALFOP and GRUNT) or numerical values from 1 to 500 to indicate channel access levels. The LEVELS command displays all levels and their numerical ranges. Advanced users can change their style with NickServ's [[NickServ/set/style|SET STYLE]] command to view the numerical version in commands like [[C/users|USERS]], and may use these numbers instead of names for fine-tuning access.
|see = (NickServ) [[NickServ/set/style|SET STYLE]], [[C/access|ACCESS]], [[C/myaccess|MYACCESS]], [[C/adduser|ADDUSER]]}}
<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

ChanServ/levels

2012-10-12T14:04:11Z

Nitemare: moved ChanServ/levels to C/levels

#REDIRECT [[C/levels]]

Server Commands/SHUN

2012-10-12T02:29:43Z

Nitemare:

'''Syntax:''' <code>SHUN [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]</code>

Shuns prevent users who match them from sending messages to the server, other than PING/PONG responses. They will not be notified they have been shunned.

'''!''' - The "!" prefix is used to forcefully place Shuns that would otherwise be denied by the server for being "too wide" (e.g. affect too many users). The ability to use this prefix has been disabled on DareNET.

'''[+|-]''' - Optional. Specifies whether the Shun is to be activated or deactivated.

'''<$type>''' - The type argument can be used to Shun users whose realname (gcos) matches by using $R.

'''<mask>''' - This may take two forms depending on the type of Shun being placed; user@host for hostnames, and *phrase* for gcos. If not given, or if its not prefixed by "+" or "-", a list of Shuns will be returned. If the "+" or "-" prefixes are used, then the <expiration> and <reason> parameters must also be given, even if the Shun already exists.

'''<target>''' - specifies what server(s) the Shun is to be activated/deactivated on. It may be either a server name or * for global. This is rarely used on DareNET due to the fact that O must be used to place global Shuns.

'''<expiration>''' - The expiration can be specified either in seconds or as a formatted time (e.g. 2d5m3s).

'''<reason>''' - The reason specifies why the user is being Shunned. It will be broadcasted to all IRC operators who have the appropriate SNOMASK.

If the Shun currently exists, a prefix of "+" will cause an inactive Shun to be activated, whereas a prefix of "-" will cause an active Shun to be deactivated. If an attempt is made to modify a Shun set by a U-lined service, such as O, the change will be forced to be local.

[[Server Commands|(Return to Main listing of Server Commands)]]

Server Commands/GLINE

2012-10-12T02:24:17Z

Nitemare:

'''Syntax:''' <code>GLINE [[!][+|-][$<type>]<mask> [[<target>] <expiration> :<reason>]]</code>

G-lines are fairly complicated; therefore, we'll attempt to explain how they work in addition on how to use the command itself.

A G-line can be active or inactive, either locally or globally. It can be a purely local G-line, or global. It can be based on an IP address, hostname or even gcos. In short, there are many variations on the basic G-line. Worse, there is also the concept of a "bad channel", or BADCHAN, that has been tacked onto the G-line subsyetem, when it should have been a separate command in the first place.

'''!''' - The "!" prefix is used to forcefully place G-lines that would otherwise be denied by the server for being "too wide" (e.g. affect too many users). The ability to use this prefix has been disabled on DareNET.

'''[+|-]''' - Optional. Specifies whether the G-line is to be activated or deactivated.

'''<$type>''' - The type argument can be used to G-line user realnames (gcos) by using $R.

'''<mask>''' - This may take several forms depending on the type of G-line being placed; user@host for hostnames, #channel for badchannels, and *phrase* for gcos. If not given, or if its not prefixed by "+" or "-", a list of G-lines will be returned. If the "+" or "-" prefixes are used, then the <expiration> and <reason> parameters must also be given, even if the G-line already exists.

'''<target>''' - specifies what server(s) the G-line is to be activated/deactivated on. It may be either a server name or * for global. This is rarely used on DareNET due to the fact that O must be used to place global G-lines.

'''<expiration>''' - The expiration can be specified either in seconds or as a formatted time (e.g. 2d5m3s).

'''<reason>''' - The reason specifies why the user is being G-lined. It will be broadcasted to all IRC operators who have the appropriate SNOMASK and to user(s) being G-lined.

If the G-line currently exists, a prefix of "+" will cause an inactive G-line to be activated, whereas a prefix of "-" will cause an active G-line to be deactivated. If an attempt is made to modify a G-line set by a U-lined service, such as O, the change will be forced to be local.

[[Server Commands|(Return to Main listing of Server Commands)]]

Conduct

2012-10-12T02:23:45Z

Nitemare:

{{Historical}}

IRC operators are the core of DareNET's staff and are perhaps the single most important factor in how DareNET appears to its users. Because of this the manner in which operators appear is very important to DareNET's image, the whole spirit of the network, and how well DareNET lives up to it's credo of "Personal Touch."

== "On Duty" and "Off Duty" ==

It is recognized by DareNET's network management that operators may be "on duty" and "off duty". Naturally you have greater freedom to act as you choose when you are off duty; however, you should keep in mind that the activities of an operator reflect upon DareNET even when the operator is not acting as a representative of it. When you are on duty, you should always pay special attention to conducting in a professional manner.

When are you on duty, and when are you off duty? The single definite rule is that when you are acting as DareNET's representative or a DareNET staff member, you are on duty. It is actually possible to be on duty and off duty at the same time, for example you can be "on duty" on a help channel and "off duty" in a private channel. In this case, anything you do or say on the help channel should be considered being on duty, while the private channel activity is clearly off duty.

The interpretation, of course, depends upon each situation. If you doubt, it is better to err on the safe side and behave as if you are on duty.

Here is a few indications that you are on duty:

* Usermode +o set, using operator commands.
* Helping users in #support, or helping as a member of DareNET staff (for example, when a user requests help in a private message).
* Having channel ops when doing so as a representative of DareNET staff (for example, in an IRC operator channel, or oped using O).
* Participating in the mediation of a user dispute.
* Monitoring user or channel situations, incognito or not.
* Attending DareNET staff online meetings.
* Posting on DareNET's discussion forums or mailing lists.

== General Conduct Guidelines ==

Here are a few guidelines for general conduct. They should not even need to be included, but nevertheless they are listed here so that nobody can say that they were not clearly stated.

* Always follow DareNET's policies and rules.
* DO NOT abuse your operator privileges.
* Respect and be considerate of ALL users. This include operators and non-operators.

The following should observed when on duty:

* Avoid swearing and derogatory comments. This can be off-putting to some users.
* DO NOT exhibit sexual behavior in public.
* Keep calm -- if you become upset or angry and cannot remain objective, it is a good idea to ask a fellow operator to handle the situation if possible.

== Guidelines for Dealing with Users ==

The manner in which you present yourself may make a difference in how efficiently and effectively you are able to handle any issue with users. You should remain calm, concise and matter of fact at all times when dealing with users. If you become upset or angry, you will be less effective and possibly even unintentionally make the situation worse. It is good to ask someone else to handle the issue for you if you are unable to remain objective. Operators need to work as a team and recognizing our individual strengths or weaknesses is an integral part of good team work. All of us have times when our performance is temporarily diminished. It is better for DareNET to have IRC operators who are able to rely on others for help, than to risk handling a situation badly.

'''DareNET IRC operators should not look down on users, make fun of or ridicule them. It is part of the DareNET principles/credo that users be treated with the utmost respect. If you feel that you are above the network's "normal users", you should seriously rethink your view, as chances are you'll be removed soon. You are an IRC operator on DareNET to serve the network, and thus, its users.'''

When handling situations involving users, the following recommendations will help you handle it in a good, professional manner. Some of them may only apply to specific situations.

* Be polite and respectful.

* Give users the benefit of the doubt. If you have had a complaint about a user, ask them to tell you what the problem is themselves before you confront them about their reported behaviour.

* Be consistent. If you apply DareNET's rules fairly to all users, then you'll have grounds to stand on should any user wish to complain about your actions.

* State the issues clearly, without personal criticism. For example, saying "I received a complaint about someone flooding this channel. Do you know what happened?" will open up communication and the possibility of finding a peaceful solution. Whereas, just saying "I /KILL lamers for flooding.", for example, may result in a escalation of the problem.

* State clearly the rule or policy which was violated. For example, "Flooding is not allowed on DareNET because it interferes with other users' ability to chat and can cause some IRC clients to lose their connection to the network." will be instructional as well as stating the network's position on the issue.

* State clearly what the consequences are. For example, "You are being warned. If I receive one more complaint, I will /KILL your IRC session. Any complaints thereafter may result in an Autokill (for you or your site)." This way everyone knows what to expect and there will be no need to engage in any debate. Make sure you know what the appropriate action is for a particular violation and do not threaten to take action which goes against the network's policy for that particular issue.

* Do not "threaten" action until you are sure it is what you will do. For example, be sure there is cause to /KILL someone before you tell them you are going to do it. While it is good to state that a possible consequence of the action may be a /KILL, it is important for users to know that once we state we will do something, we follow it through. If operators vacillate, it can start to sound like empty threats and the user may "test" repeatedly to see if we really mean what we say. It is better to avoid taking the action until you are sure there is no other option, then doing so quickly without further discussion. Remember to not use profanity or namecalling. Just state the reason based on the offending behaviour.

* Do not criticize or ridicule users. Have patience for typos. Avoid embarrassing a user in front of others. We are here to educate, not humiliate.

* Remember that DareNET is an international forum. For many English is a second (or latter) language and some colloquialisms and slang may be confusing or easily misinterpreted. Please try to use correct grammar and punctuation as this will facilitate ease of communication. If needed, you may attempt to find a translator.

* Try to be sensitive to how others view the role of an IRC operator. Control and privileges are easily misunderstood. Being aware of your own feelings in this regard can be helpful in your interactions with others.

You should also be aware that because IRC operators are perceived as having "power" on the network due to their privileges, some unscrupulous users will attempt to manipulate and exploit operators for their own benefit. Most users on IRC fall outside of this group, but such people are common enough that every operator will eventually meet one sooner or later. Keep this in mind when dealing with help requests and reports of abuse.

== Guidelines for Staff Interaction ==

When dealing with other staff members, how you conduct yourself is very important too. In general, it can have a huge influence in the overall morale, both good or bad. Here are a few guidelines that should be followed when interacting with other staff members.

* Be polite and respectful.

* Help other staff members if they ask for it.

* Utilize your "chain of command." For example, if you are having a problem with some issue, make sure your admin is aware of it, say before going to an EB member. It is better they find out from you, than from when we (the EB) confront them on it.

* If you think someone is doing a good job and have something nice and encouraging to say, say it. Positive input is always welcome, and can make a big difference.

* If you think someone is not acting right, you may try to correct him/her in private, POLITELY. Do not make defaming or derogatory comments about other staff members, especially not in public. It only lowers morale, potentially embarrasses the person and doesn't help to solve the situation. The opers@ mailing list is NOT to be used for this purpose.

* If you want to make a complaint about another staff member, e-mail abuse[at]darenet.org with full details. Do not flame him/her in public, or attempt to "get to" him/her in other ways.

== Staff Misconduct ==

The possible consequences of misbehaviour are decided by the superior of that staff member alone or in conjunction with the Abuse Team. Consequences will be proportional and relevant to the offense and may include:

* Demotion to a "local operator" for a probationary period.
* Personal and public apology.
* Replacing or reconstructing damaged records.
* Removal of channel access; temporarily or permanently for repeated misuse.
* Removal of O access.
* Mailing list moderation or removal.
* Removal of O:line or staff position.
* Refusal of future O:line opportunities.
* Permanent Network Ban.

Support Center

2012-10-11T17:49:52Z

Nitemare:

{{NeedUpdate}}

'''Welcome to DareNET's Support Center!'''

Here you can find help on all of DareNET's wonderful services. We've got step-by-step walk throughs, frequently asked questions (FAQS) and more. If you can't find the help you need here, to report a problem, ask a question, or give us any kind of feedback on any of DareNET's services, please email our Support staff or visit #Support (live, online help, 24x7).
{{Box | 1 = '''DareNET Policy Documents''' |
2 =<table width="500"><tr>
<td>'''All About Chat'''
* [[Chat Slang]]
* [[General Channel Guidelines]] </td>
<td>'''FAQs'''
* [[Bot FAQ]]
* [[Oper FAQ]]
* [[Quit Message FAQ]]
</td>
</tr><tr>
<td>'''DareNET Services'''
* [[C]]
* [[N]]
* [[MemoServ]]
* [[SpamServ]]
* [[H]]
* [[G]]</td>
<td> '''Channel Maintenance'''
* [[Channel Modes]]
* [[Extended Bans]]
* [[Topic Masking Guide]]
* [[The Art of Channel Management]] </td>
</tr></table>
}}

Services Usage

2012-10-11T17:49:05Z

Nitemare:

{{Expand|text=page}}

* [[N CertFP Auth]]
* [[Topic Masking Guide|Guide to using C's topic masking feature]]

'''Services Bots:'''

* [[C]]
* [[G]]
* [[H]]
* [[N]]
* [[S]]
* [[V]]
* [[MemoServ]]
* [[SpamServ]]

Extended Bans

2012-10-11T17:48:34Z

Nitemare:

Extended bans (also known as ban conditionals) allow different checks than the usual nick!user@host match to determine whether someone should be banned, giving channel operators more flexibility and control over their channel's ban list.

On DareNET, extended bans are of the form '''<code>$[!]<type>:<data></code>'''. Where <type> is one character (case sensitive) and determines the type of match that is to be used. If the exclamation mark (!) is used, the result of the check will be negated (discussed below).

The following types of extended bans are currently supported:

{| class="simpletable" width="100%" style="font-size: 90%;"
! style="text-align: center;" | Type
! style="text-align: center;" | Name
! style="text-align: left;" | Purpose
|-
| style="text-align: center;" | $a
| style="text-align: center;" | Account
| If a user's account name matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $c
| style="text-align: center;" | Channel
| If a user is in a channel that matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $j
| style="text-align: center;" | Shared Bans
| If a user matches a ban on the channel who's ban list is being shared, (s)he will be unable to join.
|-
| style="text-align: center;" | $n
| style="text-align: center;" | Nick Change
| If a user matches this ban, (s)he will be unable to change their nickname while in the channel.
|-
| style="text-align: center;" | $q
| style="text-align: center;" | Quiet
| If a user matches this ban, (s)he will be unable to send messages to the channel.
|-
| style="text-align: center;" | $r
| style="text-align: center;" | Realname
| If a user's realname (gecos) matches this ban, (s)he will be unable to join.
|-
| style="text-align: center;" | $t
| style="text-align: center;" | Text
| Allows you to specify text that will be blocked if a user's privmsg or notice to the channel contains it. * and ? wildcards supported.
|-
|} 

== Quiet and Nick Change ==

The $q (quiet) and $n (nick change) types are similar to normal bans, except that they allow you to control what a user can do without preventing them from being able to join the channel. The $q type prevents users matching a given mask from sending messages/notices to the channel, while the $n type prevents them from changing their nickname.

{| class="simpletable" width="55%" style="font-size: 90%;"
! style="text-align: left; width: 25px;" | Type
! style="text-align: left;" | Syntax
|-
| $q
| <code>/mode #channel +b '''$q:nick!user@host'''</code>
|-
| $n
| <code>/mode #channel +b '''$n:nick!user@host'''</code>
|-
|}

'''Examples:'''

A.) If we wanted to allow users connecting from a ".br" host to join the channel, but prevent them from being able to send messages/notices to the channel, we could set the following $q type extended ban:

<html><pre>/mode #ourchannel +b $q:*!*@*.br</pre></html>

B.) If we also wanted to prevent users connecting from a ".br" host from changing their nickname while their in our channel, we could set the following $n type extended ban:

<html><pre>/mode #ourchannel +b $n:*!*@*.br</pre></html>

== Channel ==

The $c (channel) type prevents users who are in a matching channel from joining your channel.

{| class="simpletable" width="55%" style="font-size: 90%;"
! style="text-align: left; width: 25px;" | Type
! style="text-align: left;" | Syntax
|-
| $c
| <code>/mode #channel +b '''$c:#channel'''</code>
|-
|}

'''Example:'''

A.) If we wanted to prevent users who are currently in a channel with the word ''warez'' in its name from joining our channel, we could set the following $c type extended ban:

<html><pre>/mode #ourchannel +b $c:#*warez*</pre></html>

== Realname ==

The $r (realname/gecos) type prevents users with a matching realname from joining your channel.

Note that the $r type treats "_" as both the underscore character and a space.

{| class="simpletable" width="55%" style="font-size: 90%;"
! style="text-align: left; width: 25px;" | Type
! style="text-align: left;" | Syntax
|-
| $r
| <code>/mode #channel +b '''$r:realname'''</code>
|-
|}

'''Example:'''

A.) If we wanted to prevent users who had the word ''bot'' in their realname (gecos) from the joining our channel, we could set the following $r type extended ban:

<html><pre>/mode #ourchannel +b $r:*bot*</pre></html>

== Account Bans ==

The $a (account) type allows you to ban (logged in) users who's username (i.e., account name) matches the specified account mask.

Note, these types of bans can only ever match users logged into their N account.

{| class="simpletable" width="55%" style="font-size: 90%;"
! style="text-align: left; width: 25px;" | Type
! style="text-align: left;" | Syntax
|-
| $a
| <code>/mode #channel +b '''$a:account'''</code>
|-
|}

'''Example:'''

A.) If we wanted to ban all users who's account name contained the word ''joe'', we could set the following $a type extended ban:

<html><pre>/mode #ourchannel +b $a:*joe*</pre></html>

Account type extended bans act identical to the previous method of banning users based on their account name (i.e., <code>/mode #channel +b *!*@accountname.*</code>); however, negation (reverse logic) can also be used with account type extended bans, which cannot presently be done with the old method. We discuss negation a little later in this guide.

== Shared Bans ==

The $j type allows sharing channel ban lists.

{| class="simpletable" width="55%" style="font-size: 90%;"
! style="text-align: left; width: 25px;" | Type
! style="text-align: left;" | Syntax
|-
| $j
| <code>/mode #channel +b '''$j:#channel'''</code>
|-
|}

'''Example:'''

A.) For this example, the name of our channel is ''#ourchannel'' and we want to use ''#shared''<nowiki>'</nowiki>s channel ban list inconjunction with our own. So, to do this we could set the following $j type extended ban:

<html><pre>/mode #ourchannel +b $j:#shared</pre></html>

Now, whenever a user tries to join our channel, ''#ourchannel'', they'll be checked against ''#shared''<nowiki>'</nowiki>s ban list in addition to our own ban list. If a match is found in either ban list, the user will be prevented from joining.

== Text Bans ==

The $t (text) type allows channel operators to specify text (wildcards supported) that will be blocked if (1) the user's message or notice to the channel matches it, and (2) the user's host matches the entry as well.

{| class="simpletable" width="55%" style="font-size: 90%;"
! style="text-align: left; width: 25px;" | Type
! style="text-align: left;" | Syntax
|-
| $t
| <code>/mode #channel +b '''$t:nick!user@host:text'''</code>
|-
|}

'''Examples:'''

A.) Let's say we wanted to block all channel messages and notices that contained the word ''damn'', regardless of the user sending it. To do this we could set the following $t type extended ban:

<html><pre>/mode #ourchannel +b $t:*!*@*:*damn*</pre></html>

B.) Using example A, let's say we only wanted to block such messages from users connected from a ".br" host. To do this we would slightly modify the above $t type extended ban as follows:

<html><pre>/mode #ourchannel +b $t:*!*@*.br:*damn*</pre></html>

== Negation / Reverse Logic ==

If "!" is prepended to the type of an extended ban, then the result of the comparison is negated. In other words, it will have a reversed effect. Negation is currently not possible with quiets. We suggest using excepts in this instance, instead.

'''Example:'''

A.) Let's say we wanted to allow users to join our channel ONLY if they're already present in #darenet. To do this, we would set a $c type extended ban, but prepending "!" to the type flag:

<html><pre>/mode #ourchannel +b $!c:#darenet</pre></html>

== Assistance ==

Should you need assistance using the extended bans feature, feel free to stop by #Support

[[Category:All]] [[Category:Documentation]]

When do accounts and nicks expire

2012-10-11T17:48:10Z

Nitemare:

First, please keep in mind that accounts and IRC nicknames are two different entities, while it is possible to register IRC nicknames to your DareNET account.

That said, we do not ''expire'' accounts. However, we do consider IRC nicknames expired after 60 days without use. Nicknames which are at least two weeks old, and which were last used less than two hours after their creation may also be considered expired. These limits do not apply to staff-reserved nicknames, which are allocated and dropped as needed. Also, if the nickname you want to register is the same as someone's account name, or someone's alternate nickname, and it's the only alternate nickname they have, we may be reluctant to drop it, even if it's expired.

== How do you know the last time an IRC nickname was used? ==

We know this only as a result of your authenticating/identifying to N when you connect to the network. If you don't identify, we'll have no way to know that your nickname is in use, and it will eventually expire.

== How can I take over a registered nickname that hasn't been used in a long time? ==

Nicknames which are considered expired are not dropped automatically on a regular basis. We do drop them when we notice them and, if you ask a support agent in #support, we'll be happy to manually drop the one you want so that you can re-register it.

== I registered my nickname and now someone else has it. Did someone steal it? How do I get it back? ==

To keep your registered nickname, you must continue to use it. If you don't sign onto the network for at least 60 days, or you don't identify to N for at least 60 days, the nickname is considered expired, and someone can ask to have it dropped. When a nickname has been dropped and picked up by some other user, we can't take it back from them. That would be unfair to the user who picked it up.

[[Category:Abuse and Policy]]

FAQ/Account and Password

2012-10-11T17:47:12Z

Nitemare:

__NOTOC__{{FAQ|'''Account and Password'''}}

<h5 class="faqentry expArrow">How do I login to my DareNET account?</h5>
<div class="faqentrya">To access your DareNET account via the web site, visit the [http://www.darenet.org/login Login] page, enter your username and password in the appropriate fields, and click the Login button.

To access your DareNET account via IRC, you will need to authenticate to N. This can be done by using one of the following commands:

* /msg N@services.darenet.org AUTH <username> <password>
* /NickServ AUTH <username> <password>
* /ns AUTH <username> <password>
* /auth <username> <password>
* /identify <username> <password>

Remember, you do not need to include the "<" and ">" brackets. Additionally, if the nickname you are using is registered to the account you're authenticating to, you may omit the username portion of the command and just supply your password.</div>

<h5 class="faqentry expArrow">Can I have more than one account?</h5>
<div class="faqentrya">Unless you exist in two parallel universes at once, unfortunately no. To protect the integrity of the system, our policy is one person, one account. For those wanting to register multiple IRC nicknames, you can do so by using N's REGNICK command, which links them to your account.</div>

<h5 class="faqentry expArrow">When do accounts and nicknames expire?</h5>
<div class="faqentrya">First, please keep in mind that accounts and IRC nicknames are two different entities, while it is possible to register IRC nicknames to your DareNET account.

That said, we do not expire accounts. However, we do consider IRC nicknames expired after 30 days without use (this is done automagically). Nicknames which are at least two weeks old, and which were last used less than two hours after their creation may also be considered expired. These limits do not apply to staff-reserved nicknames, which are allocated and dropped as needed. Also, if the nickname you want to register is the same as someone's account name, or someone's alternate nickname, and it's the only alternate nickname they have, we may be reluctant to drop it, even if it's expired.</div>

<h5 class="faqentry expArrow">How do you know the last time an IRC nickname was used?</h5>
<div class="faqentrya">We know this only as a result of your authenticating/identifying to N when you connect to the network. If you don't identify, we'll have no way to know that your nickname is in use, and it will eventually expire.</div>

<h5 class="faqentry expArrow">How can I take over a registered nickname that has not been used in a long time?</h5>
<div class="faqentrya">Nicknames which are considered expired are automatically dropped after 60 days. Any other nicknames that are considered expired are not dropped on a regular basis. We do drop them when we notice them and, if you ask a support agent in #support, we'll be happy to manually drop the one you want so that you can re-register it.</div>

<h5 class="faqentry expArrow">I registered my nickname and now someone else has it. Did someone steal it? How do I get it back?</h5>
<div class="faqentrya">To keep your registered nickname, you must continue to use it. If you don't sign onto the network for at least 60 days, or you don't identify to N for at least 60 days, the nickname is considered expired, and someone can ask to have it dropped. When a nickname has been dropped and picked up by some other user, we can't take it back from them. That would be unfair to the user who picked it up.</div>

<h5 class="faqentry expArrow">My account was deleted, why?</h5>
<div class="faqentrya">DareNET takes a firm stance against users who violate our [[Policy:Acceptable Use Policy|Acceptable Use Policy]]. This is in order to protect the integrity of our system for the good of our community. Normally we'll issue warnings and/or suspend the account first; however, if the abuse was severe enough, then it will warrant an account removal.</div>

<h5 class="faqentry expArrow">Why was my DareNET account suspended?</h5>
<div class="faqentrya">There are a variety of reasons an account may be suspended or terminated. The most common reason is repeated violation of the Acceptable Use Policy. For severe abuse, it is possible for an account to be terminated on a first offense, such as predatory behavior or spam. Individuals whose accounts have been terminated are prohibited from creating new accounts. If a new account is discovered, it too may be terminated without warning.</div>

<h5 class="faqentry expArrow">How do I reset my password and make sure it’s secure?</h5>
<div class="faqentrya">You can reset your password by using N's RESETPASS or PASSWORD commands on IRC. When choosing a new password, be sure to use a different password than you use for other sites or services, made up of a complex string of numbers, letters, and punctuation marks that is at least six characters in length. Do not use words found in the dictionary.</div>

<h5 class="faqentry expArrow">I am not receiving the email to reset my password.</h5>
<div class="faqentrya">Please follow the steps below to resolve this issue:

* Check your email application's spam or junk folder or filter.
* Please note that some emails may be blocked by your ISP (internet service provider).

If you're still having trouble after the above steps, please submit a report [http://www.darenet.org/forum/sendmessage.php here], or join [http://webchat.darenet.org?channels=support #Support] for further assistance.</div>

How to close my account?

2012-10-11T17:46:24Z

Nitemare:

You can close your DareNET account yourself by using N's UNREGISTER command. Please use <code>/NS HELP UNREGISTER</code> for more information.

Alternatively, you can request to have your DareNET account closed by contacting support@darenet.org. Please keep in mind that you'll need to email us from the email address associated with your DareNET account.

[[Category:Abuse and Policy]]

How to change my account name

2012-10-11T17:46:05Z

Nitemare:

Having an identity crisis? First make sure the new account name is not already in use. You can do that by using the following command: <code>/NS ACCOUNTINFO *accountname</code>. Please note the asterisk (*). Then you can request a change to your account name by joining #Support and stating your request, or by e-mailing support@darenet.org. Make sure to email us from the email address associated with your DareNET account.

[[Category:Abuse and Policy]]

V

2012-10-11T17:45:28Z

Nitemare:

V allows you to set and manage custom titles for your account. For a list of available titles, visit [http://www.darenet.org/titles http://www.darenet.org/titles]

NOTE: You may only change your title once every 14 days.

==Usage==
V may be accessed in the following ways:

* /msg V <nowiki><text></nowiki>
* /msg V@services.darenet.org <nowiki><text></nowiki>
* /hostserv <nowiki><text></nowiki>
* /hs <nowiki><text></nowiki>

For the purpose of this document, we will be using the first two methods listed, as some IRC clients do not readily support server-side aliases without additional setup and/or client commands. However, you can choose to use any of the above methods.

==User Commands==
{| class="srvcscmd" width="100%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[V/accept|ACCEPT]] Accept a group custom host invitation.
| style="width: 310px;"|[[V/pending|PENDING]] View pending custom host invitations.
| style="width: 310px;"|[[V/title|TITLE]] Set a custom title for your account.
|
|-
| style="width: 310px;"|[[V/deny|DENY]] Deny a group custom host invitation.
| style="width: 310px;"|[[V/random|RANDOM]] Set a random title for your account.
|
|
|-
|}

==Group Contact Commands==
{| class="srvcscmd" width="50%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[V/invite|INVITE]] Send a custom host invitation for your group.
| style="width: 310px;"|[[V/uninvite|UNINVITE]] Cancel a pending invitation for your group.
|-
|}

[[Category:All]] [[Category:IRC Services]]

Login On Connect

2012-10-11T17:45:06Z

Nitemare:

{{cleanup}}

{{NeedUpdate}}

=Login-on-Connect (LOC)=

==General==

The Login-on-Connect (LOC) feature allows you to pre-login while connecting to DareNET. Using Login-on-Connect bypasses you from [http://www.darenet.org/rbl RBL] scans and hides your hostname before anyone can see your real IP address. We recommend everyone give it a try.

To use Login-on-Connect, you must first have an DareNET N Account. Register for one here if you don't already have one.

Login-on-connect uses the “server password” feature built into most IRC clients. All you do is put your specially formatted login information into the server password box like this:

username:password (your username, colon, your password)

for example, my username is NiTeMaRe, and if my password was mysecretpass I would put the following into my password box:

NiTeMaRe:mysecretpass

When you connect to DareNET using the new password, you should see a message like the following:

*** Attempting service login to N
*** AUTHENTICATION SUCCESSFUL as NiTeMaRe

==Client Specific Instructions:==

Detailed instructions for [[loc-mirc|mIRC users]].

Detailed instructions for [[loc-xchat|XChat users]].

==Troubleshooting==

*Make sure you can login the normal way to N: /ns auth username password
*If you get a message about /QUOTE PASS that means your username, or password is wrong, or maybe N is down?
*Some people reported having to close mIRC and re-open it before LOC started working.
*You no longer have to have a *@* host (default) set in N since LOC is now aware of your hostname.
*The 'server group' must be the string “DareNET” exactly. mIRC wont send the password if the name doesn't match what the server announces itself as.
*Try typing the password string into notepad so you can see it. Then paste it into the password box.

HostServ/uninvite

2012-10-11T17:44:16Z

Nitemare: moved HostServ/uninvite to V/uninvite

#REDIRECT [[V/uninvite]]

V/uninvite

2012-10-11T17:44:16Z

Nitemare: moved HostServ/uninvite to V/uninvite

{{Related commands|[[V/invite|INVITE]]}}<div class="cmdsyn">UNINVITE <group> <nickname|*account></div>

Removes a pending group custom host invitation for the specified user.

NOTE: you must be on the group's contact list to remove pending custom host invitations.

===Examples===

{| class="srvcscmd" width="80%" style="font-size: 90%;"
| /msg V UNINVITE darenet NiTeMaRe
| Removes NiTeMaRe's custom host invitation for the group ''darenet''
|-
|}

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

V/uninvite

2012-10-11T17:44:10Z

Nitemare:

HostServ/invite

2012-10-11T17:43:53Z

Nitemare: moved HostServ/invite to V/invite

#REDIRECT [[V/invite]]

V/invite

2012-10-11T17:43:53Z

Nitemare: moved HostServ/invite to V/invite

{{Related commands|[[V/uninvite|UNINVITE]]}}<div class="cmdsyn">INVITE <group> <nickname|*account> <title></div>

Sends a group custom host invitation to the specified user. Custom group hosts are in the form of: <code><account>.<title>.<group></code>

Where ''<group>'' is the name of the group the invitation is for, and ''<title>'' is the custom title you would like to grant to the user.

NOTE: you must be on the group's contact list to send custom host invitations.

===Examples===

{| class="srvcscmd" width="80%" style="font-size: 90%;"
| /msg V INVITE darenet *NiTeMaRe staff
| Sends a custom host invitation to the user who's account name is ''NiTeMaRe'' for the title ''staff''
|-
|}

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

V/invite

2012-10-11T17:43:47Z

Nitemare:

HostServ/random

2012-10-11T17:43:17Z

Nitemare: moved HostServ/random to V/random

#REDIRECT [[V/random]]

V/random

2012-10-11T17:43:17Z

Nitemare: moved HostServ/random to V/random

{{Related commands|[[V/title|TITLE]]}}<div class="cmdsyn">RANDOM</div>

Randomly selects a title from the available titles list at [http://www.darenet.org/titles http://www.darenet.org/titles] and sets it for your account.

NOTE: you can only change your title once every 14 days. For assistance, please join [http://www.darenet.org/webchat?channels=support #Support].

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

V/random

2012-10-11T17:43:11Z

Nitemare:

HostServ/title

2012-10-11T17:42:49Z

Nitemare: moved HostServ/title to V/title

#REDIRECT [[V/title]]

V/title

2012-10-11T17:42:49Z

Nitemare: moved HostServ/title to V/title

{{Related commands|[[V/random|RANDOM]]}}<div class="cmdsyn">TITLE <title></div>

Sets a custom title for your account. A list of all available custom titles can be found at [http://www.darenet.org/titles http://www.darenet.org/titles]

NOTE: you can only change your title once every 14 days. For assistance, please join [http://www.darenet.org/webchat?channels=support #Support].

===Examples===

{| class="srvcscmd" width="80%" style="font-size: 90%;"
| /msg V TITLE loves
| Sets the title ''loves'' for your account, making your hidden host: <your-account-name-here>.loves.darenet
|-
|}

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

V/title

2012-10-11T17:42:43Z

Nitemare:

HostServ/deny

2012-10-11T17:42:16Z

Nitemare: moved HostServ/deny to V/deny

#REDIRECT [[V/deny]]

V/deny

2012-10-11T17:42:16Z

Nitemare: moved HostServ/deny to V/deny

{{Related commands|[[V/accept|ACCEPT]] [[V/pending|PENDING]]}}<div class="cmdsyn">ACCEPT <group></div>

Used to deny a group custom host invitation. Where ''<group>'' is the name of the group you are denying the invitation for.

To view a list of pending invitations for your account, you may use the [[V/pending|PENDING]] command.

===Examples===

{| class="srvcscmd" width="80%" style="font-size: 90%;"
| /msg V DENY darenet
| Denies a custom host invitation from the group ''DareNET''.
|-
|}

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

V/deny

2012-10-11T17:42:09Z

Nitemare:

HostServ/pending

2012-10-11T17:41:44Z

Nitemare: moved HostServ/pending to V/pending

#REDIRECT [[V/pending]]

V/pending

2012-10-11T17:41:44Z

Nitemare: moved HostServ/pending to V/pending

{{Related commands|[[V/accept|ACCEPT]] [[V/deny|DENY]]}}<div class="cmdsyn">PENDING</div>

View a list of pending invitations for your account.

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

V/pending

2012-10-11T17:41:39Z

Nitemare:

HostServ/accept

2012-10-11T17:41:08Z

Nitemare: moved HostServ/accept to V/accept

#REDIRECT [[V/accept]]

V/accept

2012-10-11T17:41:08Z

Nitemare: moved HostServ/accept to V/accept

{{Related commands|[[V/deny|DENY]] [[V/pending|PENDING]]}}<div class="cmdsyn">ACCEPT <group></div>

Used to accept a group custom host invitation. Where ''<group>'' is the name of the group you are accepting the invitation for.

To view a list of pending invitations for your account, you may use the [[V/pending|PENDING]] command.

===Examples===

{| class="srvcscmd" width="80%" style="font-size: 90%;"
| /msg V ACCEPT darenet
| Accepts a custom host invitation from the group ''DareNET''.
|-
|}

<html><table align="right"><tr><td><a href="javascript:history.go(-1)">[Go Back]</a></td></tr></table></html>

V/accept

2012-10-11T17:41:00Z

Nitemare:

V

2012-10-11T17:40:34Z

Nitemare:

HostServ allows you to set and manage custom titles for your account. For a list of available titles, visit [http://www.darenet.org/titles http://www.darenet.org/titles]

NOTE: You may only change your title once every 14 days.

==Usage==
V may be accessed in the following ways:

* /msg V <nowiki><text></nowiki>
* /msg V@services.darenet.org <nowiki><text></nowiki>
* /hostserv <nowiki><text></nowiki>
* /hs <nowiki><text></nowiki>

For the purpose of this document, we will be using the first two methods listed, as some IRC clients do not readily support server-side aliases without additional setup and/or client commands. However, you can choose to use any of the above methods.

==User Commands==
{| class="srvcscmd" width="100%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[V/accept|ACCEPT]] Accept a group custom host invitation.
| style="width: 310px;"|[[V/pending|PENDING]] View pending custom host invitations.
| style="width: 310px;"|[[V/title|TITLE]] Set a custom title for your account.
|
|-
| style="width: 310px;"|[[V/deny|DENY]] Deny a group custom host invitation.
| style="width: 310px;"|[[V/random|RANDOM]] Set a random title for your account.
|
|
|-
|}

==Group Contact Commands==
{| class="srvcscmd" width="50%" style="font-size: 90%;"
|-
| style="width: 310px;"|[[V/invite|INVITE]] Send a custom host invitation for your group.
| style="width: 310px;"|[[V/uninvite|UNINVITE]] Cancel a pending invitation for your group.
|-
|}

[[Category:All]] [[Category:IRC Services]]

Services Usage

2012-10-11T17:39:12Z

Nitemare:

{{Expand|text=page}}

* [[NickServ CertFP Auth]]
* [[Topic Masking Guide|Guide to using ChanServ's topic masking feature]]

'''Services Bots:'''

* [[C]]
* [[G]]
* [[H]]
* [[N]]
* [[S]]
* [[V]]
* [[MemoServ]]
* [[SpamServ]]

loc-mirc

2012-10-11T17:36:54Z

Nitemare:

Click View:Options from the mIRC menu, and select the “servers” option from the left box. Select DareNET from IRC Network, and click the “Edit” button. You will then see this:

[[Image:Mirc_loc.png]]

In the password box enter “/username/password” (without quotes).

Note: Replace username and password with your real N username and password. Click “OK” to save the changes. Click “Connect To Server” and look for the authentication successful message.

Can I have more than one account

2012-10-11T17:23:22Z

Nitemare:

Unless you exist in two parallel universes at once, unfortunately no. To protect the integrity of the system, our policy is one person, one account. For those wanting to register multiple IRC nicknames, you can do so by using N's REGNICK command, which links them to your account.

[[Category:Abuse and Policy]]