User Tools

Site Tools


Copfilter - Installation and Update

Important Rules

These rules apply to the basic installation, the update installation and all other component updates:

:!: It is absolutely neccessary to apply changes in the respective order.

:!: Prior to making changes, one should have an actual IPCop-backup, including all Copfilter settings!

:!: If not, be prepared to make a new IPCop- and Copfilter installation.

:!: This comes with absolutely no functional guarantees, sorry - but the real world is simply too coloured for that…

:!: We're only human - but working on that point…

  • If for any reason - in spite of the instructions - something is unclear or errors occur: do not hesitate and open a new thread in the Copfilter forum.
  • An exact description of the error and the involved software versions is helpful in every case, the events up to the appearance of the error should be displayed as clearly as possible.
  • Maybe there are existing log outputs or error messages which make error analysis easier: Please copost!

Before describing the different Copfilter installations and their specific features, a few more explanations about the returning installation procedures must be done.

Because these are standardized procedures, they are introduced at this point once in detail - later there will be refered only to this page to avoid constantly recurring instructions.

The installation of the software archives

Important Rules

  • To make Copfilter maintenance easier, we try to keep to an - on the whole - uniform installation procedure.
  • That means, if an installation archive - a component update or similar - should be installed, one must keep an eye only to the rules described and made nothing wrong!
  • If one deviates from it, however, there can be problems.
  • There are still exceptions to this execution - then, however, they are marked accordingly and described separately.

Besides of that, the approach for the installation of Copfilter archive packages is always the same:

Code paragraphs contain always a single command line, the bold formatted words in angular clips in between are standing for the corresponding keystrokes.

1. Login

Log in on the console as 'root' using a suitable client (ssh, PuTTY, …) and initiate the following commands:

cd /tmp 


Please note:

  • IPCop V1 uses SSH port 222 (SSH-V2: 8022; WebGUI-V1: 445, WebGUI-V2: 8443), otherwise this should need no further explanation.
  • Since IPCop V2.x, the '/tmp'-directory uses the TMPFS file system. Therefore on reboot, everything in '/tmp' will be lost.

2. Download

Download the appropriate installation package (e.g. with wget):



If 'wget' does not yet exist, see Part 2 - Tools (wget) or download the package on a client and upload to IPCop using WinSCP or a similar tool, see Part 2 - Tools (WinSCP).

It should look similiar to this:


3. Check MD5 sum

Each installation archive is bundled with the so called MD5-checksum, or MD5SUM.

Using this checksum one can check if the archive has been downloaded complete and undamaged.

This checksum should always be checked!

md5sum [name_of_installation_package]


You can save time by not typing the complete archive name, for example, but by typing only the first three characters and then hitting the [TAB] key. Linux then completes the partial to the full archive name.

To verify the checksum of an installation archive, use the command 'md5sum':

md5sum monit_5.0.3_copfilter.tar.gz
5d2a72a0cb58208ba731a71d2a5f9b0b  monit_5.0.3_copfilter.tar.gz

The checksum of the downloaded file is in this case 5d2a72a0cb58208ba731a71d2a5f9b0b, a comparison with the author-specified checksum (5d2a72a0cb58208ba731a71d2a5f9b0b) is successful, checksums are identical - go for it!

4. Extract the installation archive

If everything is ok, extract the installation archive:

tar xzvf [name_of_installation_package]


The extracted archive:
Extracting monit archive

For those who always wanted to know, the command options used for 'tar' in detail:
x = extract
z = filter the archive through gzip
v = verbose
f = use archive file or device ARCHIVE

5. Change to installation directory

This directory always starts with the same string as the archive file.

cd [name_of_installation_package]


6. Starting the installation

Start the installation in this directory:



7. Installation ok?

Check all outputs for errors!

  • This includes not only tracking the actual installation process, but may also include restarting all Copfilter services, tracking the startup messages and a subsequent, precise control of the various log files.
  • Why should you do this? The Copfilter consists of about a dozen different components, working in parallel, depending on the made selection.
  • If just one necessary component doesn't properly start or is not working as expected, this could lead to unforeseeable consequences, up to complete failure as a result!

8. Deleting the installation directories (optional)

If they are no longer needed, the installation directories and the archives are now removed:

cd /tmp


rm -R [name_of_installation_package]


Please note:

  • There are exceptions, in which the unpacked installation folder - or at least parts of it - should not be completely deleted!

  • Since these installation procedures are always the same - with very few exceptions - on the following pages there'll only be references to this page!
  • Someone who is still uncertain about the right order or the syntax - just print it out.
  • The only things that'll change are the names of the installation packages and the MD5-checksums.
  • Exceptions will be individually noted.

en/copfilter_-_installation_and_update.txt · Last modified: 2016/12/04 12:53 by fischerm