1.1/Making BOPM work with InspIRCd
From the makers of InspIRCd.
| 1.1 Documentation | 1.2 Documentation | 2.0 Documentation | 2.1 Documentation |
This tutorial will instruct you upon how to get BOPM up and running on your inspircd servers.
Contents |
Installation
Firstly and most importantly you need InspIRCd 1.1 Beta 1 or above. This requirement is because BOPM requires the IP address of connecting clients (rather than just the hostname) to be in the connection notice, and the InspIRCd 1.0 Alpha 12 version adds this feature. From InspIRCd 1.1 Beta 1 onwards, the format of the connection notices has changed, hence the requirement for InspIRCd 1.1 Beta 1.
Secondly, you must obtain BOPM from the BOPM website.
Once you have the bopm tarball on your shell, untar it:
tar fpxvz bopm-3.1.2.tar.gz cd bopm-3.1.2
..and configure/make it:
./configure make make install
This usually installs BOPM to your home directory under a 'bopm' directory, e.g. ~/bopm. If you wish to change where BOPM is installed, read the "INSTALL" file (Hint: --prefix). Change to this directory and then to the 'etc' directory within it, where your config files for BOPM are stored:
cd ~/bopm/etc
Configuration
Now open up your config file (bopm.conf) in your favourite editor. The following lines given below are ones which work with inspircd. You must find the existing lines in the configuration, remove them, and replace them with these versions of the lines. Please note that where the example gives the name test.chatspike.net you should edit this to contain your server's name.
mode = "+sn +c"; connregex = "\\*\\*\\* CONNECT: Client connecting on port [0-9]+: ([^ ]+)!([^@]+)@([^\\)]+) \\[([0-9\\.]+)\\].*"; kline = "ZLINE %i 1d :Open Proxy found on your host. Please visit www.blitzed.org/proxy?ip=%i for more information."; target_string = ":test.chatspike.net NOTICE Auth :*** Looking up your hostname...";
Configuration Details
There now follows a quick description of these config settings, for those who are new to BOPM or to inspircd or both. The first config setting, mode=, sets the mode which the bopm client will set on itself when it connects.
The second setting, connregex, is arguably the most important and most difficult setting to understand. This defines a pattern of characters which must be matched so that bopm may perform a scan. This pattern matches inspircd connect notices (and currently to date no other connect notices known to man!). I repeat now the time is right that you must have alpha 12 or this connregex line will not work!.
The kline= line indicates how bopm will ban an open proxy host. You can use KLINE here if you want to set local bans, GLINE saves your network resources by making a network-wide ban. This ban is one day long, you may also change the '1d' to whatever you wish.
The final line is used by bopm to determine wether it has found an open proxy or not. Please note that you should change the server address in these config files to match the server bopm is connecting to. If you do not, BOPM will never find any new proxies and will only detect those which are already in its blacklist!
Oper Configuration for BOPM
One final note, you must prepare an <oper> tag for your bopm. After defining an oper username and password in your bopm config file you may wish to add a group of config tags to your inspircd Configuration file which look like the following:
<class name="BanOnly" commands="ZLINE"> <type name="BOPM" classes="BanOnly"> <oper name="bopm" password="bopmpass" host="*@localhost" type="BOPM">
The reasoning for this is as follows: The bopm bot with these privilages may only see connect/exit notices and ZLINE people. This is the most secure possible config for your BOPM. Remember to set the hostname if neccessary.
