* x3 does not set the host suffix for users, but must know it when making
* things like bans, where it should not show the user's real hostname. */
"numeric" "51"; // hint: If you get collisions on link, CHANGE THIS.
- "type" "4"; // Only change this to 5 if you are using Nefarious 0.5.0 off SVN
+ /* Type handles some changes in nefarious 1.0 (was 0.5.0)
+ * 4 - nefarious 0.4.x and other ircds
+ * 5 - nefarious 1.0.x and higher
+ */
+ "type" "5";
+ "host_in_topic" "1"; //Set to 1 if your Nefarious server have the HOST_IN_TOPIC F:line set to TRUE.
"max_users" "256"; // You can save a little memory by setting this to a lower value.
"force_n2k" "1"; // Use extended (5-digit) numnick for self, even if 3 are possible.
"ping_freq" "60";
"Support Staff <support@afternet.org>"
);
/* extended_accounts -
- * enable this for nefarious 0.4.x and higher. Sends 'AC R nick account'instead of
- * 'AC nick account' and allows for renames etc. */
+ * enable this for nefarious 0.4.x and higher and in ircd.conf add F:EXTENDED_ACCOUNTS:TRUE.
+ * Sends 'AC R nick account' instead of 'AC nick account' and allows
+ * for renames, login-on-connect, etc. If you use stock ircu set to 0. */
"extended_accounts" "1";
+
/* the following two settings are for ircu's HEAD_IN_SAND features, and are equivelent to
* the F: lines in ircu's ircd.conf. both can be disabled by commenting them out. */
//"his_servername" "*.AfterNET.org"; // hidden server name, shown in remote /whois requests
"valid_account_regex" "^[-_a-z0-9A-Z]{2,15}$";
"valid_nick_regex" "^[-_a-z][-_a-z0-9]*$";
+ // Whats a valid hostname look like for fakehosts?
+ "valid_fakehost_regex" "^[-_a-zA-Z0-9.]+$";
+
// "Nickserv" networks, set this to 0. "Authserv" networks,
// set it to 1.
"disable_nicks" "1";
// What to do when someone uses the NickServ "reclaim" command?
// This can be one of "none", "warn", "svsnick", or "kill", but
- // stock ircu does not support svsnick -- you need Bahamut or
- // nefarious.
+ // stock ircu does not support svsnick -- you need nefarious.
"reclaim_action" "none";
// What (else) to do when someone uses a registered nick?
// how long to keep an illegal channel locked down (seconds)?
"purge_lock_delay" "60";
+ // ------------------------------------------------------------------
+ // Defcon Settings
+ //
+ // No new channel registrations 1
+ // No New Nick Registrations 2
+ // No Channel Mode changes 4
+ // Force Chan Mode 8
+ // Use Reduced Session Limit 16
+ // KILL any new clients trying to connect 32
+ // Services will ignore everyone but opers 64
+ // Services will silently ignore everyone but opers 128
+ // GLINE all new clients trying to connect 256
+ // No new memos sent to block MemoServ attacks 512
+ // SHUN all new clients trying to connect 1024
+ //
+ // These are the values are added together to determine each defcon setting:
+ "DefCon1" "415";
+ "DefCon2" "159";
+ "DefCon3" "31";
+ "DefCon4" "23";
+
+ // Default defcon level, 5 is running all normally
+ "DefConLevel" "5";
+
+ // If defcon is limiting sessions then how many sessions should O3 allow?
+ "DefConSessionLimit" "2";
+
+ // Length of glines and shuns set on newly connecting clients, if defcon is glining
+ // or shunning newly connecting clients
+ "DefConGlineExpire" "5m";
+
+ // Mode to set on all channels if defcon is forcing channel modes on all channels
+ "DefConChanModes" "+r";
+
+ // If not set to 0, defcon will set back to level 5 after this time
+ "DefConTimeOut" "15m";
+
+ // Set to 1 to send a notice to all users when defcon levels are changed
+ "GlobalOnDefcon" "0";
+
+ // If set to 1 along with the notice that the levels are changing an extra
+ // notice will be sent
+ "GlobalOnDefconMore" "0";
+
+ // GlobalOnDefconMore notice.
+ "DefconMessage" "Put your message to send your users here. Dont forget to uncomment GlobalOnDefconMore";
+
+ // This notice will be used if GlobalOnDefcon and GlobalOnDefconMore are off
+ "DefConOffMessage" "Services are now back to normal, sorry for any inconvenience";
+
+ // Reason placed in defcon Glines and Shuns.
+ "DefConGlineReason" "This network is currently not accepting connections, please try again later";
+
+ // ------------------------------------------------------------------
+
+ // To use geoip support in Opserv WHOIS then you will need to install
+ // the c GeoIP api. Its available on http://www.maxmind.com, also on
+ // apt on debian and ubuntu. The dat files can also be obtained
+ // from the earlier URL. Place them in your X3 dir and away you go.
+ // X3 will need a recompile once you install the c api. If there is a
+ // GeoIP City Data file then the GeoIP data file will be ignored. However
+ // bear in mind that the city data file is a lot larger than the plain
+ // country data file so it does eat more cpu. The city dat file is ~25mb
+ // compared to the country file being ~900KB. Choose carefully.
+ "geoip_data_file" "./GeoIP.dat";
+ "geoip_city_data_file" "";
+
// The join-flood policer code goes off all the time when a server
// goes down (and everyone reconnects) so i don't reccomend using it.
// Automatically moderate join flooded channels?
"chanserv" {
"nick" "X3";
+ // The umodes - add +d if you use nefarious 1.0 and you added 'b:lines'
+ // to pass cmdchar through to chanserv anyway.
+ "modes" "+iok";
+
// The off_channel setting takes one of three numerical values:
// 0 = off
// 1 = use a registered channel mode, have services op themselves