Services

help of Eggdrop ircd sheel how to install eggdrop and other services

Watch Online Cricket

 

 

join Chat Room Click Here

Join Funnypaki Chat And Discuss Cricket Click Here

bopm.conf unrealircd

/*
  BOPM configuration for irc.rc6.org
*/

options {
	/*
	 * Full path and filename for storing the process ID of the running
	 * BOPM.
	 */
	pidfile = "/var/run/bopm/bopm.pid";

	/*
	 * How many seconds to store the IP address of hosts which are
	 * confirmed (by previous scans) to be secure.  New users from these
	 * IP addresses will not be scanned again until this amount of time
	 * has passed. IT IS STRONGLY RECOMMENDED THAT YOU DO NOT USE THIS
	 * DIRECTIVE, but it is provided due to demand.
	 *
	 * The main reason for not using this feature is that anyone capable
	 * of running a proxy can get abusers onto your network - all they
	 * need do is shut the proxy down, connect themselves, restart the
	 * proxy, and tell their friends to come flood.
	 *     
	 * Keep this directive commented out to disable negative caching.
	 */
  #	negcache = 3600;

	/*
	 * Amount of file descriptors to allocate to asynchronous DNS.  64
	 * should be plenty for almost anyone - previous versions of BOPM only
	 * did one at a time!
	 */
	dns_fdlimit = 64;

	/*
	 * Put the full path and filename of a logfile here if you wish to log
	 * every scan done.  Normally BOPM only logs successfully detected
	 * proxies in the bopm.log, but you may get abuse reports to your ISP
	 * about portscanning.  Being able to show that it was BOPM that did
	 * the scan in question can be useful.  Leave commented for no
	 * logging.
	 */
  #	scanlog = "/var/log/bopm/scan.log";
};

IRC {
	/*
	 * IP to bind to for the IRC connection.  You only need to use this if
	 * you wish BOPM to use a particular interface (virtual host, IP
	 * alias, ...) when connecting to the IRC server.  There is another
	 * "vhost" setting in the scan {} block below for the actual
	 * portscans.  Note that this directive expects an IP address, not a
	 * hostname.  Please leave this commented out if you do not
	 * understand what it does, as most people don't need it.
	 */
  #	vhost = "0.0.0.0";

	/*
	 * Nickname for BOPM to use.
	 */
	nick = "bopm";

	/*
	 * Text to appear in the "realname" field of BOPM's /whois output.
	 */
	realname = "Blitzed Open Proxy Monitor";

	/*
	 * If you don't have an identd running, what username to use.
	 */
	username = "bopm";

	/*
	 * Hostname (or IP) of the IRC server which BOPM will monitor
	 * connections on.
	 */
	server = "127.0.0.1";

	/*
	 * Password used to connect to the IRC server (PASS)
	 */

  #	password = "secret";

	/*
	 * Port of the above server to connect to.  This is what BOPM uses to
	 * get onto IRC itself, it is nothing to do with what ports/protocols
	 * are scanned, nor do you need to list every port your ircd listens
	 * on.
	 */
	port = 6667;

	/*
	 * Command to execute to identify to NickServ (if your network uses
	 * it).  This is the raw IRC command text, and the below example
	 * corresponds to "/msg nickserv identify password" in a client.  If
	 * you don't understand, just edit "password" in the line below to be
	 * your BOPM's nick password.  Leave commented out if you don't need
	 * to identify to NickServ.
	 */
  nickserv = "privmsg nickserv :identify XXXXXX";

	/*
	 * The username and password needed for BOPM to oper up.
	 */
	oper = "bopm XXXXXX";

	/*
	 * Mode string that BOPM needs to set on itself as soon as it opers
	 * up.  This needs to include the mode for seeing connection notices,
	 * otherwise BOPM won't scan anyone (that's usually umode +c).  It's
	 * often also a good idea to remove any helper modes so that users
	 * don't try to talk to the BOPM.
	 *
	 * REMEMBER THAT IRCU AND LATER VERSIONS OF UNREAL DO NOT USE A SIMPLE
	 * +c !!
	 */

  /*
   * These modes show ALL connections, and helper mode is disabled to stop people 
   * from talking to the bot.
   * other options: "+sc" and "+c-h"
   */
   mode = "+s +cF -h"; 

	/*
	 * If this is set then BOPM will use it as an /away message as soon as
	 * it connects.
	 */
	away = "I'm a bot.  Your messages will be ignored.";

	/*
	 * Info about channels you wish BOPM to join in order to accept
	 * commands.  BOPM will also print messages in these channels every
	 * time it detects a proxy.  Only IRC operators can command BOPM to do
	 * anything, but some of the things BOPM reports to these channels
	 * could be soncidered sensitive, so it's best not to put BOPM into
	 * public channels.
	 */
	channel {
	   /*
	    * Channel name.  Local ("&") channels are supported if your ircd
	    * supports them.
	    */
	   name = "#bopm";

	   /*
	    * If BOPM will need to use a key to enter this channel, this is
	    * where you specify it.
	    */
	   key = "XXXXXX";

	   /*
	    * If you use ChanServ then maybe you want to set the channel
	    * invite-only and have each BOPM do "/msg ChanServ invite" to get
	    * itself in.  Leave commented if you don't, or if this makes no
	    * sense to you.
	    */
     # invite = "privmsg chanserv :invite #bopm";
	};

	/*
	 * You can define a bunch of channels if you want:
	 *
	 * channel { name = "#other"; }; channel { name="#channel"; }
	 */

	/*
	 * connregex is a POSIX regular expression used to parse connection
	 * (+c) notices from the ircd. The complexity of the expression should
	 * be kept to a minimum.
	 *  
	 * Items in order MUST be: nick user host IP
	 *
	 * BOPM will not work with ircds which do not send an IP in the
	 * connection notice.
	 *
	 * This is fairly complicated stuff, and the consequences of getting
	 * it wrong are the BOPM does not scan anyone.  Unless you know
	 * absolutely what you are doing, please just uncomment the example
	 * below that best matches the type of ircd you use.
	 *
	 * !!! NOTE !!! If a connregex for your ircd does not appear here and the
	 * hybrid connregex does not appear to work, check the BOPM FAQ at 
	 * http://wiki.blitzed.org/BOPM before contacting our lists for help.
	 *
	 */

	/* Hybrid / Bahamut / Unreal (in HCN mode) */
	# connregex = "\\*\\*\\* Notice -- Client connecting: ([^ ]+) \\(([^@]+)@([^\\)]+)\\) \\[([0-9\\.]+)\\].*"; #regular
  # connregex = "\\*\\*\\* Notice -- Client connecting.*: ([^ ]+) \\(([^@]+)@([^\\)]+)\\) \\[([0-9\\.]+)\\].*"; # far connects
    connregex = "\\*\\*\\* Notice -- Client connecting[.A-Za-z0-9 ]*: ([^ ]+) \\(([^@]+)@([^\\)]+)\\) \\[([0-9\\.]+)\\].*";

	/*
	 * "kline" controls the command used when an open proxy is confirmed.
	 * We suggest applying a temporary (no more than a few hours) KLINE on the host.
	 *
	 * <WARNING>
         * Make sure if you need to change this string you also change the
         * kline command for every DNSBL you enable below.
	 *
         * Also note that some servers do not allow you to include ':' characters
         * inside the KLINE message (e.g. for a http:// address).
	 *
	 * Users rewriting this message into something that isn't even a valid
	 * IRC command is the single most common cause of support requests and
	 * therefore WE WILL NOT SUPPORT YOU UNLESS YOU USE ONE OF THE EXAMPLE
	 * KLINE COMMANDS BELOW.
	 * </WARNING>
	 *
	 * That said, should you wish to customise this text, several
	 * printf-like placeholders are available:
	 *
	 *  %n     User's nick
	 *  %u     User's username
	 *  %h     User's irc hostname
	 *  %i     User's IP address
	 *
	 */
	# kline = "KLINE *@%h :Open Proxy found on your host. Please visit www.blitzed.org/proxy?ip=%i for more information.";

	/* A GLINE example for IRCu: */
  # kline = "GLINE +*@%i 1800 :Open proxy found on your host. Please visit www.blitzed.org/proxy?ip=%i for more information.";

  /* An AKILL example for services with OperServ
   * Your BOPM must have permission to AKILL for this to work! */
  # kline = "PRIVMSG OpenServ :AKILL +3h *@%h Open proxy found on your host. Please visit www.blitzed.org/proxy?ip=%i for more information.";

  /* default kline
   *  %n User's nick
   *  %u User's username     - REMEMBER!
   *  %h User's irc hostname - bots (& blacklists) don't necessarily have (contain) hostnames
   *  %i User's IP address   - but they ALWAYS have IPs */
  kline = "gline +*@%i 7d :Open Proxy found on your host.";

	/*
	 * Text to send on connection, these can be stacked and will be sent in this order
	 * 
	 * !!! UNREAL USERS PLEASE NOTE !!!
	 * Unreal users will need PROTOCTL HCN to force hybrid connect
	 * notices.
	 *
	 * Yes Unreal users!  That means you!  That means you need the line
	 * below!  See that thing at the start of the line?  That's what we
	 * call a comment!  Remove it to UNcomment the line.
	 */
	perform = "PROTOCTL HCN";

};

/*
 * OPM Block defines blacklists and information required to report new proxies
 * to a dns blacklist.  DNS-based blacklists store IP addresses in a DNS zone
 * file. There are several blacklist that list IP addresses known to be open
 * proxies or other forms of IRC abuse. By checking against these blacklists,
 * BOPMs are able to ban known sources of abuse without completely scanning them.
 */

OPM {

  blacklist {
    name = "dnsbl.dronebl.org";
    type = "A record reply";
    reply {
      3 = "IRC Drone";
      4 = "Tor";
      5 = "Bottler";
      6 = "Unknown spambot or drone";
      7 = "DDOS Drone";
      8 = "SOCKS Proxy";
      9 = "HTTP Proxy";
      10 = "ProxyChain";
    };
   ban_unknown = no;
   kline = "gline +*@%i 7d :DroneBL dronebl.org/lookup_branded.do?ip=%i";
  };

  blacklist {
    name = "tor.dnsbl.sectoor.de";
    type = "A record reply";
    reply {
      1 = "Tor exit server";
    };
    ban_unknown = no;
    kline = "KLINE *@%h :Tor exit server detected. See www.sectoor.de/tor.php?ip=%i";
  };

};

/*
 * The short explanation:
 *
 * This is where you define what ports/protocols to check for.  You can have
 * multiple scanner blocks and then choose which users will get scanned by
 * which scanners further down.
 *
 * The long explanation:
 *
 * Scanner defines a virtual scanner.  For each user being scanned, a scanner
 * will use a file descriptor (and subsequent connection) for each protocol.
 * Once connecting it will negotiate the proxy to connect to
 * target_ip:target_port (target_ip MUST be an IP).
 *
 * Once connected, any data passed through the proxy will be checked to see if
 * target_string is contained within that data.  If it is the proxy is
 * considered open. If the connection is closed at any point before
 * target_string is matched, or if at least max_read bytes are read from the
 * connection, the negotiation is considered failed.
 */

scanner {

	/*
	 * Unique name of this scanner.  This is used further down in the
	 * user {} blocks to decide which users get affected by which
	 * scanners.
	 */
	name="default";

	/*
	 * HTTP CONNECT - very common proxy protocol supported by widely known
	 * software such as Squid and Apache.  The most common sort of
	 * insecure proxy and found on a multitude of weird ports too.  Offers
	 * transparent two way TCP connections.
	 */
	protocol = HTTP:80;
	protocol = HTTP:8080;
	protocol = HTTP:3128;
	protocol = HTTP:6588;

	/*
	 * SOCKS4/5 - well known proxy protocols, probably the second most
	 * common for insecure proxies, also offers transparent two way TCP
	 * connections.  Fortunately largely confined to port 1080.
	 */
	protocol = SOCKS4:1080;
	protocol = SOCKS5:1080;

	/*
	 * Cisco routers with a default password (yes, it really does happen).
	 * Also pretty much anything else that will let you telnet to anywhere
	 * else on the internet.  Fortunately these are always on port 23.
	 */
	protocol = ROUTER:23;

	/*
	 * WinGate is commercial windows proxy software which is now not so
	 * common, but still to be found, and helpfully presents an interface
	 * that can be used to telnet out, on port 23.
	 */
	protocol = WINGATE:23;

	/*
	 * The HTTP POST protocol, often dismissed when writing the access
	 * controls for proxies, but sadly can still be used to abused.
	 * Offers only the opportunity to send a single block of data, but
	 * enough of them at once can still make for a devastating flood.
	 * Found on the same ports that HTTP CONNECT proxies inhabit.
	 *
	 * Note that if your ircd has "ping cookies" then clients from HTTP
	 * POST proxies cannot actually ever get onto your network anyway.  If
	 * you leave the checks in then you'll still find some (because some
	 * people IRC from boxes that run them), but if you use BOPM purely as
	 * a protective measure and you have ping cookies, you need not scan
	 * for HTTP POST.
	 */
	protocol = HTTPPOST:80;

	/*
	 * IP this scanner will bind to.  Use this if you need your scans to
	 * come FROM a particular interface on the machine you run BOPM from.
	 * If you don't understand what this means, please leave this
	 * commented out, as this is a major source of support queries!
	 */
#	vhost = "127.0.0.1";

	/* Maximum file descriptors this scanner can use.  Remember that there
	 * will be one FD for each protocol listed above.  As this example
	 * scanner has 8 protocols, it requires 8 FDs per user.  With a 512 FD
	 * limit, this scanner can be used on 64 users _at the same time_.
	 * That should be adequate for most servers.
	 */
	fd = 512;

	/*
	 * Maximum data read from a proxy before considering it closed.  Don't
	 * set this too high, some people have fun setting up lots of ports
	 * that send endless data to tie up your scanner.  4KB is plenty for
	 * any known proxy.
	 */
	max_read = 4096;

	/*
	 * Amount of time (in seconds) before a test is considered timed out.
	 * Again, all but the poorest slowest proxies will be detected within
	 * 30 seconds, and this helps keep resource usage low.
	 */
	timeout = 30;

	/* 
	 * Target IP to tell the proxy to connect to
	 * 
	 * !!! THIS MUST BE CHANGED !!!
	 *
	 * You cannot instruct the proxy to connect to itself! The easiest
	 * thing to do would be to set this to the IP of your ircd and then
	 * keep the default target_strings.
	 *
	 * Please use an IP that is publically reachable from anywhere on the
	 * Internet, because you have no way of knowing where the insecure
	 * proxies will be located.  Just because you and your BOPM can
	 * connect to your ircd on some private IP like 192.168.0.1, does not
	 * mean that the insecure proxies out there on the Internet will be
	 * able to.  And if they never connect, you will never detect them.
	 *
	 * Remember to change this setting for every scanner you configure.
	 *
	 */
	target_ip     = "85.17.184.215"; # rc6 was "127.0.0.1";

	/*
	 * Target port to tell the proxy to connect to.  This is usually
	 * something like 6667.  Basically any client-usable port.
	 */
	target_port   = 6667;

	/* 
	 * Target string we check for in the data read back by the scanner.
	 * This should be some string out of the data that your ircd usually
	 * sends on connect.  The example below will work on most
	 * hybrid/bahamut ircds.  Multiple target strings are allowed.
	 *
	 * NOTE: Try to keep the number of target strings to a minimum. Two
	 *       should be fine. One for normal connections and one for throttled
	 *       connections. Comment out any others for efficiency.
	 */

	/* Usually first line sent to client on connection to ircd. 
	 * If your ircd supports a more specific line (see below),
	 * using it will reduce false positives.
	 */
	target_string = "*** Looking up your hostname...";

	/* Some ircds give a source for the NOTICE AUTH (bahamut for example).
	 * It is recommended you use the following instead of the generic
	 * "*** Looking up your hostname..." if your ircd supports it. 
	 * This will reduce the chances of false positives.
	 */
#	target_string = ":server.yournetwork.org NOTICE AUTH :*** Looking up your hostname...";

	/* If you try to connect too fast, you'll be throttled by your own
	 * ircd.  Here's what a hybrid throttle message looks like:
	 */
	target_string = "ERROR :Trying to reconnect too fast.";

	/* And the same for bahamut (comment this out if you're not using bahamut): */
	target_string = "ERROR :Your host is trying to (re)connect too fast -- throttled.";
};

scanner {
	name = "extended";

	protocol = HTTP:81;
	protocol = HTTP:8000;
	protocol = HTTP:8001;
	protocol = HTTP:8081;

	protocol = HTTPPOST:81;
	protocol = HTTPPOST:6588;
#	protocol = HTTPPOST:4480;
	protocol = HTTPPOST:8000;
	protocol = HTTPPOST:8001;
	protocol = HTTPPOST:8080;
	protocol = HTTPPOST:8081;

	/*
	 * IRCnet have seen many socks5 on these ports, more than on the
	 * standard ports even.
	 */
	protocol = SOCKS4:4914;
	protocol = SOCKS4:6826;
	protocol = SOCKS4:7198;
	protocol = SOCKS4:7366;
	protocol = SOCKS4:9036;

	protocol = SOCKS5:4438;
	protocol = SOCKS5:5104;
	protocol = SOCKS5:5113;
	protocol = SOCKS5:5262;
	protocol = SOCKS5:5634;
	protocol = SOCKS5:6552;
	protocol = SOCKS5:6561;
	protocol = SOCKS5:7464;
	protocol = SOCKS5:7810;
	protocol = SOCKS5:8130;
	protocol = SOCKS5:8148;
	protocol = SOCKS5:8520;
	protocol = SOCKS5:8814;
	protocol = SOCKS5:9100;
	protocol = SOCKS5:9186;
	protocol = SOCKS5:9447;
	protocol = SOCKS5:9578;

	/*
	 * These came courtsey of Keith Dunnett from a bunch of public open
	 * proxy lists.
	 */
	protocol = SOCKS4:29992;
	protocol = SOCKS4:38884;
	protocol = SOCKS4:18844;
	protocol = SOCKS4:17771;
	protocol = SOCKS4:31121;

	fd = 400;

	/* If required you can add settings such as target_ip here
	 * they will override the defaults set in the first scanner
	 * for this and subsequent scanners defined in the config file
	 * This affects the following options:
	 * fd, vhost, target_ip, target_port, target_string, timeout and
	 * max_read.
	 */
};

/*
 * User blocks define what scanners will be used to scan which hostmasks. When
 * a user connects they will be scanned on every scanner {} (above) that
 * matches their host.
 */

user {
	/*
	 * Users matching this host mask will be scanned with all the
	 * protocols in the scanner named.
	 */
	mask = "*!*@*";
	scanner = "default";
};

user {
	/* Connections without ident will match on a vast number of connections
	 * very few proxies run ident though */
#	mask = "*!~*@*";
	mask = "*[email protected]*";
	mask = "*[email protected]*";
	mask = "*[email protected]*";
	mask = "*[email protected]*";
	mask = "*[email protected]*";
	mask = "*!*@*www*";
	mask = "*!*@*proxy*";
	mask = "*!*@*cache*";

	scanner = "extended";
};

/*
 * Exempt hosts matching certain strings from any form of scanning or dnsbl.
 * BOPM will check each string against both the hostname and the IP address of
 * the user.
 *
 * There are very few valid reasons to actually use "exempt".  BOPM should
 * never get false positives, and we would like to know very much if it does.
 * One possible scenario is that the machine BOPM runs from is specifically
 * authorized to use certain hosts as proxies, and users from those hosts use
 * your network.  In this case, without exempt, BOPM will scan these hosts,
 * find itself able to use them as proxies, and ban them.
 */
exempt {
	mask = "*!*@127.0.0.1";
};

How To Install BOPM ?

1. wget http://static.blitzed.org/www.blitzed.org/bopm/files/bopm-3.1.3.tar.gz
2. tar -xvf bopm-3.1.3.tar.gz
3. cd bopm-3.1.3
4. ./configure
5. make
6. make install
7. cd
8. cd bopm/etc
9. pico bopm.conf

/* This is a modified bopm.conf
* http://www.zemra.org
* LAST MODIFIED: 2010-11-20
*/

options {
/* Full path and filename for file storing the process ID */
pidfile = “/home/EviL/bopm/bopm.pid”;

/* seconds to store the IP address of hosts */
# negcache = 3600;

/* Amount of file descriptors to allocate to asynchronous DNS */
dns_fdlimit = 64;

/* full path and filename of scan logfile */
# scanlog = “/home/EviL/bopm/scan.log”;
};

IRC {
/* IP to bind to for the IRC connection */
vhost = “72.20.42.110”;

/* Nickname for BOPM to use */
nick = “TheHawk”;

/* Text to appear in the “realname” field of BOPM’s whois output */
realname = “Open Proxy Monitoring”;

/* If you don’t have an identd running, what username to use */
username = “nix”;

/* Hostname (or IP) of the IRC server */
server = “72.20.42.110”;

/* Password used to connect to the IRC server (PASS) */
# password = “secret”;

/* Connect to IRC server via this port */
port = 6667;

/* Command to identify to NickServ */
# nickserv = “privmsg nickserv :identify “;

/* The username and password needed for BOPM to oper up */
oper = “BOPM bopmoperpass”;

/* with the following modes this BOPM will see ALL network Connections
* See Unreal documentation for more information on user modes
*/
mode = “+s +cF”;

/* Specify BOPM control channel(s) */
channel {
/* Channel name. */
name = “#Staff”;

/* Channel key */
key = “”;

/* command used to ask chanserv for invite */
# invite = “privmsg chanserv :invite #bopm”;
};

/* connregex is a POSIX regular expression used to parse connection
* (+c) notices from the ircd. The complexity of the expression should
* be kept to a minimum so load is @ a minimum even during ‘heavy’ traffic */

/* Unreal in HCN mode */
# connregex = “\\*\\*\\* Notice — Client connecting: ([^ ]+) \\(([^@]+)@([^\\)]+)\\) \\[([0-9\\.]+)\\].*”;
connregex = “\\*\\*\\* Notice — Client connecting[.A-Za-z0-9 ]*: ([^ ]+) \\(([^@]+)@([^\\)]+)\\) \\[([0-9\\.]+)\\].*”;

/* default kline
* %n User’s nick
* %u User’s username – REMEMBER!
* %h User’s irc hostname – bots (& blacklists) don’t necessarily have (contain) hostnames
* %i User’s IP address – but they ALWAYS have IPs */
kline = “gline +*@%i 7d :Open Proxy found on your host.”;

/* Text to send on connection. Specify multiple with multiple lines. */
perform = “PROTOCTL HCN”;
};

OPM {

blacklist {
name = “rbl.efnetrbl.org”;
type = “A record reply”;
reply {
1 = “Open proxy”;
2 = “spamtrap666”;
3 = “spamtrap50”;
4 = “TOR exit server”;
5 = “Drones / Flooding”;
};
ban_unknown = no;
kline = “gline +*@%i 0 : 4An open proxy was detected in your host 1 – EFnetRBL “;
};

blacklist {
name = “dnsbl.dronebl.org”;
type = “A record reply”;
reply {
3 = “IRC Drone”;
4 = “Tor”;
5 = “Bottler”;
6 = “Unknown spambot or drone”;
7 = “DDOS Drone”;
8 = “SOCKS Proxy”;
9 = “HTTP Proxy”;
10 = “ProxyChain”;
};
ban_unknown = no;
kline = “gline +*@%i 0 : 4An open proxy was detected in your host 1 – DroneBL”;
};

blacklist {
name = “dnsbl.njabl.org”;
type = “A record reply”;
reply {
2 = “Open Relay”;
4 = “Confirmed Spam Source”;
9 = “Open Proxy”;
};
ban_unknown = no;
kline = “gline +*@%i 0 : 4An open proxy was detected in your host 1 – NJABL”;
};

blacklist {
name = “dnsbl.swiftbl.org”;
type = “A record reply”;
reply {
2 = “SOCKS Proxy”;
3 = “IRC Proxy”;
4 = “HTTP Proxy”;
5 = “IRC Drone”;
6 = “TOR”;
};
ban_unknown = no;
kline = “gline +*@%i 0 : 4An open proxy was detected in your host 1 – SwiftBL”;
};

blacklist {
name = “dnsbl.proxybl.org”;
type = “A record reply”;
reply {
2 = “Open proxy”;
};
ban_unknown = no;
kline = “gline +*@%i 0 : 4An open proxy was detected in your host 1 – ProxyBL”;
};

/* the next two entries might match too many IPs
* so they’re commented out for now
*/

/*
blacklist {
name = “dnsbl-2.uceprotect.net”;
type = “A record reply”;
reply {
2 = “Matched Entry”;
};
ban_unknown = no;
kline = “gline +*@%i 7d :uceprotect”;
};

blacklist {
name = “xbl.spamhaus.org”;
type = “A record reply”;
reply {
4 = “CBL Detected Address”
};
ban_unknown = no;
kline = “gline +*@%i 7d : 4An open proxy was detected in your host 1 – SpamhausXBL”;
};
*/
/* Pretend to send reports FROM */
# dnsbl_from = “[email protected]”;

/* Email address to send reports TO. Specify multiple with multiple lines. */
# dnsbl_to = “[email protected]”;

/* Full path to your sendmail binary */
# sendmail = “/usr/sbin/sendmail”;
};

/* Exempt hosts matching (hostname or IP) strings from any form of scanning or dnsbl */
exempt {http://www.blogger.com/img/blank.gif
mask = “*!*@127.0.0.1”;
};

exempt {
mask = “*!*@72.20.42.*”; # Zemra.Org SHELL IP
};

12. cd ..
13. cd bin
14. ./bopm

Anope: Upgrading

Upgrading Anope Services

————————
1) Log into SSH.

2) Type wget –no-check-certificate https://www.hostchaos.com/library/IRC/anope-1.8.5.tar.gz

tar -zxvf anope-1.8.5.tar.gz

cd ~

cd anope-1.8.5

./Config

What directory – Enter

Data files – Enter

Data files owned – Enter

Default umask – 077

Check for mysql libraries – No

Once it has finished configuring, type “make”

Then “make install”

Now you have installed the latest version of Anope on your server, you now need to copy over the database files and services.conf file. Before copying over the services.conf file, read the changes.conf and add any changes to your services.conf file. If you are upgrading from a much older version (say 1.8.0 or before) it would probably be easier to create a fresh configuration file from the example.conf included in the new version you have just installed (edit example.conf as necessary, save, and rename to services.conf).

1) Log into your server with WinSCP

2) Copy over your backed up database files into the Services folder

3) Copy over your EDITED services.conf (if necessary)

Now you need to restart your services. You can do this 2 ways.

1) Restart from your IRC client by typing /msg OperServ restart

2)Restart from SSH

cd services

./anoperc restart

Linking UnrealIRCd servers together

If you are planning to link an UnrealIRCd leaf server to an UnrealIRCd hub server to generate a network this tutorial will take you through the process.

Linking irc.myserver.com to irc.example.com

 

1) Log into your server with WinSCP for help on this click here.

2) You’ll be presented with a list of folders, double click the folder called “Unreal3.2” or “unreal” folder if installed by the auto-installer to enter it.

3) You’ll then be presented with another set of folders and files, click the file called unrealircd.conf and press F4 to open it.

4) The first thing you need to do is edit the server numeric. This must be a number that is not being used by anything else on the server you are linking too. Here is an example:

 

me

{

name “irc.myserver.com”;

info “My-Server-Name”;

numeric 10;

};

 

5)  Scroll down to the section in the configuration where link blocks are added and create a link block for the server to be linked. Here is an example:

 

link            SERVERNAME

{

username *;

hostname  SERVERIP;

bind-ip  *;

port  7000;

hub             *;

password-connect “PASSWORD”;

password-receive “PASSWORD”;

class           servers;

options {

};

};

 

*NEED TO EDIT BITS OF THAT EXAMPLE LINK BLOCK*

 

SERVERNAME – The name of the server to be linked.

– Example – irc.example.com

 

SERVERIP – The server IP to be linked.

– Example – 188.165.64.107

 

PASSWORD – The authentication password between the two servers for linking. These passwords should match both configs.

 

6) Further down the config you need to add the ulines of the server you are linking to. Here is an example:

 

ulines {

services.example.com;

stats.example.com;

};

 

7) Next, you need to edit the names of the services and stats servers. Here is an example:

 

set {

network-name “My-Server-Name”;

default-server “irc.myserver.com”;

services-server “services.myserver.com”;

stats-server “stats.myserver.com”;

 

*NEED TO EDIT BITS OF THAT EXAMPLE LINK BLOCK*

 

NETWORK NAME – This should match the name of the hub server.

– Example – Example-Server

 

SERVICES SERVER – The name of the services server to which you are linking to.

– Example – services.example.com

 

STATS SERVER – The name of the stats server to which you are linking to.

– Example – stats.example.com

 

8) The last bit you need to edit in the unrealircd.conf is the cloak keys. These cloak keys must be the ones of the server you are linking to. Here is an example:

 

cloak-keys {

“jJH3d7Nbg8JMbh76BnB73n5023IKsdnha”;

“35Msh47Jg437H4jhSA830Zqo3J63JHddd”;

“36JKdg3poqJg46G934Jg4Oty4KLgej43J”;

};

 

9) Save and close the unrealircd.conf.

 

Now, the unrealircd.conf of the server you are linking to must add a link block.

 

Follow steps 1-4 from above replacing the server name server IP and password with the details of the server that will be linked. Here is an example:

 

link            SERVERNAME

{

username *;

hostname  SERVERIP;

bind-ip  *;

port  7000;

hub             *;

password-connect “PASSWORD”;

password-receive “PASSWORD”;

class           servers;

options {

};

};

 

*NEED TO EDIT BITS OF THAT EXAMPLE LINK BLOCK*

 

SERVERNAME – The name of the server to be linked.

– Example – irc.myserver.com

 

SERVERIP – The server IP to be linked.

– Example – 188.165.64.100

 

PASSWORD – The authentication password between the two servers for linking. These passwords should match both configs.

 

Now you need to kill anything that is running on your server (irc.myserver.com) that is also running on server you are linking to, to avoid collision. To do this do the following:

 

1) Log into your server using SSH for help setting up SSH click here.

2) Type the following into SSH:

 

FOR SERVICES:

pkill services

 

FOR NEOSTATS

pkill neostats

 

FOR DEFENDER

pkill defender

 

FOR BOPM

pkill bopm

 

For changes to take affect, both servers need to be rehashed. Do this by typing /rehash in your IRC client.

(Please note: You must rehash your unrealircd.conf after killing anything linked to your server for the server numeric change to take affect.)

 

Once this is done, your server is ready to be linked. To do this type /connect THESERVERYOUARELINKINGTO. Here is an example:

/connect irc.example.com

How to install Unreal IRCD

How to install Unreal IRCD with Anope Services

This explains in a few easy steps how to install UnrealIRCD with Anope.
First you need to have a shell with us, and then, wget a file with this command.

wget http://www.unrealircd.com/downloads/Unreal3.2.9.tar.gz

Then do unpacking:

tar -zxvf Unreal3.2.9.tar.gz

Enter in the dir:

cd Unreal3.2

Run this:

./Config

Read the information it gives you.

Keep pressing enter on a default value, if you are not sure what to do, so just keep pressing ENTER

When its done, run this:

make

And you are done! Now copy checkout our unrealircd.conf example, which is already edited, here: unrealircd fileNow do the following:

echo “” > unrealircd.conf; echo “” > ircd.motd; echo “” > ircd.rules

nano unrealircd.conf

Paste all text from our example to this and press CTRL + X and then write: Y and save it!

Then its time to start unreal ircd! Do this:

./unreal start

Thats it and if you have problems running it, you need to install gcc, make, libs etc.. Now lets do for services!

Installing a module in unrealircd

Unreal IRCd has a few modules that add extra functions, or improve on current ones. They only take a minute to install, modules first need to be placed in your Unreal source, and compiled from a source (.c) into a .so before they can be loaded, we will cover this in the steps below:

1. Download the module source file (.c) and place it in src/modules of your unreal install, this will either be unreal/src/modules or Unreal3.2/src/modules if you installed Unreal yourself.

2. Next we need to compile the module, this requires us connecting to the server using SSH, eg. Putty. Connect to your IRCd account using putty, and change directory to your Unreal installation. eg. cd unreal OR cd Unreal3.2

3. Compile the module/s using the following command:
make custommodule MODULEFILE=m_getinfo

The part in italics is the name of the module you’re installing, without any file extension.

4. After compiling you will have a modulename.so file in the src/modules folder, this is the module file we can actually load. We load modules by adding a loadmodule line near the beginning of unrealircd.conf.
Using your preferred ftp client, connect to your IRCd account and open unrealircd.conf.

Use the example below to tell your server to load the module:
loadmodule “src/modules/modulename.so”;

Getting this part wrong will cause errors, so make sure you include the “‘s, spell the module name right and don’t forget the .so and ; at end of line. When you have done this save unrealircd.conf.

5. To load the module just do a /rehash from your irc server, hopefully it will rehash, without any errors. You can check to see if it loaded by typing /module  which will show you a list of loaded modules.

How do i install Anope ?

Here is a guide to installing Anope. If you come across any problems with following this guide or have problems understanding it please feel free to contact us for a little bit more help.

First Download Wincap OR Filezilla by click here

1) First login to the shell you want to install anope on then type:-

wget http://www.funnypaki.net/anope/anope-1.8.7.tar.gz

OR

wget http://www.funnypaki.net/anope/anope-1.9.6-source.tar.gz

Then

tar zxvf anope-1.8.7.tar.gz

OR

tar zxvf anope-1.9.6-source.tar.gz

cd anope-1.8.7

OR

cd anope-1.9.6

./Config

2) You will now be asked a few simple questions, we shall help you answer these as best as we can.

2.1) In what directory do you want the binaries to be installed? – Just press enter
2.2) /home/username/services does not exist. Create it? – Just press enter again
2.3) Where do you want the data files to be installed? – Press enter
2.4) Which group should all Services data files be owned by? (If Services should not force files to be owned by a particular group, just press Return.) – Enter again for this one
2.5) What should the default umask for data files be (in octal)? – Enter again, This should be fine as it is
2.6) Allow anope to automatically check for mysql libraries? unless you get errors with make, there is no need to change this setting. – Just press enter again.

3) After that script has finished doing its thing you now type “make” if that dont work use “gmake”

4) Now you need to install it by typing “make install”

5) Ok so now you have installed Anope onto your server you have to configure it. You do this by going back to your shell root and entering the new folder thats there called “services”

6) Download the Dostiplus Anope config by typing:  wget http://www.funnypaki.net/anope/services.conf

And For  anope-1.9.6  check in services directory example.conf  file and make it

7) Now you can edit services.conf – there’s lots of comments in it intended to help you configure Anope. If you have trouble, feel free to ask any questions either via our IRC channel, or via submitting a support ticket.

8) Ok you are now ready to start your services. You do this by typing:     ./services

Your services should now connect fine if everything has been done correctly. If they dont please come back and request more help from our dedicated staff.

How to setup psybnc

How to setup (compile/install) bnc.

First Download Wincap OR Filezilla by click here

1.) type: wget http://www.funnypaki.net/psybnc/psyBNC-2.3.2-7.tar.gz

2.) type: tar -zxvf psyBNC-2.3.2-7.tar.gz

3.) type: cd psybnc

4.) type: make

Now you will have to edit psybnc.conf file to edit listening port.

5.) type: pico psybnc.conf

MAke Set Your Port And close file by type :   ctrl+x      and then Enjoy by type  :    ./psybnc

( OR  ) may be After performing  make  command you will be asked some questions as below but i hope it will not ask , but if you will be asked then you can see details here

Country Name [DE]:
State/Province [Somewhere]:
Locality Name (eg, city) []:
Organization Name (eg, company) [tCl]:
Organizational Unit Name (eg, section) [psyBNC]:
Common Name (Full domain of your server) []:

LEAVE all field blank if you dont want to answer.

Now you will have to edit psybnc.conf file to edit listening port.

6.) type: pico psybnc.conf

MAke Set Your Port And close file by type :   ctrl+x      and then Enjoy by type  :    ./psybnc

Now you are ready to use your psyBNC

how To Install NeoStats and setting up

NeoStats is a group of bots created for different functionalities such as helping IRC operators, or banning users connecting via a proxy. NeoStats is quite a popular piece of IRC software and you can install it on your server by doing the following:

First Download Wincap OR Filezilla by click here

1) Log into your server using SSH Via Putty.exe

2) Type the following into SSH waiting for each section to finish before proceeding:

wget http://www.funnypaki.net/neostast/NeoStats-3.0.1.tar.gz

OR

wget –no-check-certificate http://www.funnypaki.net/neostast/NeoStats-3.0.1.tar.gz

tar -xvf NeoStats-3.0.1.tar.gz

cd NeoStats-3.0.1

./configure

If the next screen doesn’t load keep pressing enter until it reaches 100% else just go to the next step

make

make install

 

During the installation you may get asked to install the libperls if you have a VPS simply log in as root and type one of the following:

For operating systems with aptitude such as debian based, including ubuntu – apt-get install libperl-dev

For operating systems such as RedHat, Fedora, CentOS – yum install libperl-devel

However if you have an IRCd server you will need to speak to one of the HostChaos support administrators and ask them to install it for you.

 

Now NeoStats are installed it’s time to configure them and then run them, so to configure NeoStats you’ll need to do the following:

1) Log into your server using WinSCP OR any Ftp program

2) Double click on the NeoStats3.0 folder to enter it.

3) You are presented with a list of folders and files, press F4 on neostats.conf to open.

4) Edit the config as necessary and then save and close it.

 

During the editing of the neostats.conf you will have had to set up a link block, you’ll need to add a link block to the unrealircd.conf and a U:Line. To do this you’ll need to do the following:

1) Go to the unreal folder in WinSCP.

2) Scroll down and open unrealircd.conf (using the F4 button).

3) Scroll down to the section in the configuration where link blocks are added and create a link block for NeoStats. Here is an example:

link            SERVERNAME

{

username *;

hostname  SERVERIP;

bind-ip  *;

port  7000;

hub             *;

password-connect “PASSWORD”;

password-receive “PASSWORD”;

class           servers;

options {

};

};

 

*NEED TO EDIT BITS OF THAT EXAMPLE LINK BLOCK*

SERVERNAME – The name you gave the defender server in defender.conf

– Example – neostats.hostchaos.com

SERVERIP – Your server IP.

– Example – 173.0.52.186

PASSWORD – The authentication password between the two servers for linking, you should have created this in neostats.conf.

– Make up a password, it is recommended to button mash one. Do not use one of your own passwords or one easily guessed.

4) In unrealircd.conf you also need to create a listen block. If you scroll to the section in your unrealircd.conf with a list of listen blocks already there copy and paste one directly underneath the list and change the port to 7000 so it is listening on that port for defender to connect.

Example: Listen   173.0.52.186:7000

5) Last bit you need to add to the unrealircd.conf is the U:Line, scroll to the section of the unrealircd.conf where your U:Lines are and add a U:Line for the NeoStats server. Here’s an example:

ulines {

SERVERNAME;

};

Change SERVERNAME for the name of the NeoStats server in neostats.conf.

OR

Download neostats.conf file from here and config it as per your server

wget http://www.funnypaki.net/neostast/neostats.conf

6) Save and close the unrealircd.conf.

7) On your server when opered type /rehash to update your UnrealIRCd config.

 

Now you need to run NeoStats. To do this do the following:

1) Log into SSH

2) Type either of the following depending on your install doing one stage at a time:

cd

cd NeoStats3.0

./neostats start

OR

cd

cd NeoStats

./neostats start

 

NeoStats should now run in the background, connect to your server and begin working.

 

 

Now Modules :P – I want you get every thing from here so i load alos modules here aswell :)

 

BLSB

 

1. cd NeoStats3.0/modules
2. wget
http://www.funnypaki.net/neostast/BLSB-3.0.a4-66.tar.gz
3. tar -xvf BLSB-3.0.a4-66.tar.gz
4. cd BLSB-3.0.a4-66
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load blsb

 

 FloodServ

 

1. cd NeoStats3.0/modules
2. wget
http://www.funnypaki.net/neostast/FloodServ-3.0.a4-70.tar.gz
3. tar -xvf FloodServ-3.0.a4-70.tar.gz
4. cd FloodServ-3.0.a4-70
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load FloodServ

 

 LogServ

 

1. cd NeoStats3.0/modules
2. wget
http://www.funnypaki.net/neostas/LogServ-3.0.a3.tar.gz
3. tar -xvf LogServ-3.0.a3.tar.gz
4. cd LogServ-3.0.a3
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load LogServ

 

OPSB

 

1. cd NeoStats3.0/modules
2. wget
http://www.funnypaki.net/neostast/OPSB-3.0.a4-230.tar.gz
3. tar -xvf OPSB-3.0.a4-230.tar.gz
4. cd OPSB-3.0.a4-230
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load OPSB

 

 SecureServ

 

1. cd NeoStats3.0/modules
2. wget
http://www.funnypaki.net/neostast/SecureServ-3.0.a4-419.tar.gz
3. tar -xvf SecureServ-3.0.a4-419.tar.gz
4. cd SecureServ-3.0.a4-419
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load SecureServ

 

 SeenServ

 

1. cd NeoStats3.0/modules
2. wget
http://www.funnypaki.net/neostast/SeenServ-3.0.a4-72.tar.gz
3. tar -xvf SeenServ-3.0.a4-72.tar.gz
4. cd SeenServ-3.0.a4-72
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load SeenServ

 

 WarServ

 

1. cd NeoStats3.0/modules
2. wget 
http://www.funnypaki.net/neostast/WarServ-3.0.a3.tar.gz
3. tar -xvf WarServ-3.0.a3.tar.gz
4. cd WarServ-3.0.a3
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load WarServ

 

YahtzeeServ

 

1. cd NeoStats3.0/modules
2. wget
http://www.funnypaki.net/neostast/YahtzeeServ-3.0.a3.tar.gz
3. tar -xvf YahtzeeServ-3.0.a3.tar.gz
4. cd YahtzeeServ-3.0.a3
5. ./configure
6. make
7. make install
8. on IRC type: /msg neostats load YahtzeeServ

 

If You Want any other module then post here in comments in Leave A reply or email me @ [email protected]