Development Team/ircd-darenet/new config

Below is an example of what the new ircd-darenet configuration file will look like, which will use a bind-style format. It's not the final product; therefore, some blocks may be added, changed or removed.


 * 1) [General]
 * 2) Old M:line
 * 3) Some general information about the server.
 * 4) General {
 * 5)   name = "servername";
 * 6)   vhost = "ipv4vhost";
 * 7)   description = "description";
 * 8)   numeric = numericnumber;
 * 9) };
 * 10) The must contain either a * or a valid IPv4 address in dotted quad
 * 11) notation (e.g. 127.0.0.1). This address MUST be the address of a physical
 * 12) interface on the host. It is used for outgoing connections only. See the
 * 13) Ports blocks for listener virtual hosting. If in doubt, use * or the IP of
 * 14) your primary interface here.
 * 15) The must be unqiue to the server, and must be between 0 and 4095.
 * 16) It is not updated on rehash. On DareNET, numerics are assigned by the
 * 17) Server Management Team. You should always use the numeric assigned to you.
 * 1) The must be unqiue to the server, and must be between 0 and 4095.
 * 2) It is not updated on rehash. On DareNET, numerics are assigned by the
 * 3) Server Management Team. You should always use the numeric assigned to you.
 * 1) Server Management Team. You should always use the numeric assigned to you.

General { name = "name.area.zone.darenet.org"; vhost = "1.2.3.4"; description = "DareNET Client Server"; numeric = "21"; };


 * 1) [Admin]
 * 2) Old A:line
 * 3) This sets information that can be retrieved with the /ADMIN command.
 * 4) Admin {
 * 5)   Location = "Line 1";
 * 6)   Location = "Line 2";
 * 7)   Contact = "Line 3";
 * };
 * 1)   Contact = "Line 3";
 * };

Admin { Location = "DareNET"; Location = "Server Management Team"; Contact = ""; };


 * 1) [CRule]
 * 2) Old D/d line(s)
 * 3) CRule is an advanced, real-time rule-based routing decision making
 * 4) system. For more information, please refer to doc/readme.crules.
 * 5) Including the "all" modifier makes the rule always apply; otherwise,
 * 6) it only applies to outbound autoconnects.
 * 7) CRule "servermask" all connectrule;
 * 8) CRule "servermask" connectrule;
 * 9) Examples:
 * 10) CRule "*.us.darenet.ord" connected("*.us.darenet.org");
 * 11) CRule "*.eu.darenet.org" connected("amsterdam.nl.eu.*");
 * 12) The following CRule is recommended for leaf servers:
 * 1) Examples:
 * 2) CRule "*.us.darenet.ord" connected("*.us.darenet.org");
 * 3) CRule "*.eu.darenet.org" connected("amsterdam.nl.eu.*");
 * 4) The following CRule is recommended for leaf servers:
 * 1) The following CRule is recommended for leaf servers:

CRule "*" directcon("*");


 * 1) [UWorld]
 * 2) Old U:line
 * 3) One of the many great features of DareNET is Services, which is a
 * 4) program that connects to the network as a server. This allows it
 * 5) to broadcast any mode change, thus allowing an oper to, for example,
 * 6) "unlock" a channel that has been taken over.
 * 7) There is one slight problem to this though; the TimeStamp protocol
 * 8) prevents this. So there is a configuration option to allow them
 * 9) anyway from a specific server. This originated on Undernet, hence
 * 10) the UWorld (and U-line) reference.
 * 11) UWorld {
 * 12)   name = "servername";
 * };
 * 1) UWorld {
 * 2)   name = "servername";
 * };

UWorld { name = "services.darenet.org"; name = "services2.darenet.org"; name = "statistics.darenet.org"; };


 * 1) [Jupe]
 * 2) It is posstible to Jupe nicknames on ircd-darenet, thus preventing
 * 3) users from using them.
 * 4) Jupe {
 * 5)   nick = "nick1,nick2,nick3";
 * };
 * 1)   nick = "nick1,nick2,nick3";
 * };

Jupe { nick = "ChanServ,MemoServ,NickServ,HelpServ,SpamServ,OperServ,Global,DareNET"; nick = "GeoServ,HostServ,S,StatServ,NoteServ,O,Oper,Admin,Operator,Administrator"; nick = "login,protocol,pass,newpass,org,LPT1,LPT2,COM1,COM2,COM3,COM4,AUX"; nick = "ChanSvr,ChanSaver,NickSvr,NickSaver,{,},|,},~,-,_,`"; }; more to come...