github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

review of standalone-howto

master
Serg G. Brester 2016-11-14 17:08:18 +01:00 committed by sbrester
parent fc044efe4d
commit c647d94ce5
1 changed files with 18 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
How-to-test-newer-fail2ban-version-resp.-use-fail2ban-standalone-instance.md

@ -1,11 +1,20 @@
To test it, you do not need to install fail2ban at all.
Sometimes you'll need to test a fix for some issue, new functionality or some features provided only in the newer version, another different fail2ban configuration, etc.
To test another version of fail2ban, you do not need to install it at all.
You can create a standalone or test instance parallel to your stock fail2ban (fail2ban works basically without installation).
Below you'll find an example, how to create such test instance without installation, e. g. 0.10-th version of fail2ban, regardless of original fail2ban version, that may be installed parallel on the same host:
You can create a standalone test instance parallel to your stock fail2ban (fail2ban works without installation):
- download or git checkout a 10th branch, e. g. to directory `/tests/f2b10`:
```bash
git clone --branch 0.10 https://github.com/fail2ban/fail2ban.git /tests/f2b10
```
- `cd /tests/f2b10`
- enter your new fail2ban directory:
```bash
cd /tests/f2b10
f2b10dir="$(pwd)"
```
- if you will use python3, first execute `./fail2ban-2to3` (don't do that if `python --version` returns 2.x)
- if you want, you can execute the test suite (works only on clean copy, as long as you do not made some customisation, resp. no *.local files was created):
```bash
@ -37,10 +46,12 @@ enabled = true
```bash
cp /var/lib/fail2ban/fail2ban.sqlite3 /tests/f2b10/run/fail2ban.sqlite3
```
- [important] stop original stock fail2ban `service fail2ban stop` or `fail2ban-client stop`
- :warning: [important] stop original stock fail2ban `service fail2ban stop` or `fail2ban-client stop`<br/>
Note: If you want to leave your original stock fail2ban running, see warning at end of this article for more informations.
- define alias for your new test fail2ban instance:
```bash
alias f2b10="sudo PYTHONPATH=$(pwd) $(pwd)/bin/fail2ban-client -c $(pwd)/config/"
alias f2b10="sudo PYTHONPATH=$f2b10dir $f2b10dir/bin/fail2ban-client -c $f2b10dir/config/"
```
- start your test fail2ban instance:
```bash
@ -57,4 +68,5 @@ f2b10 stop
Easy and without any installation...
**[Important] you should always shutdown your original version before you start this standalone instance and vice versa**
**:warning: [Important] you should normally always shutdown your original version before you start this standalone instance and vice versa**
But you can leave your original stock fail2ban running, and try to run this test (standalone) version parallel side by side with original version of fail2ban. In this case you should never use the same jail names as configured in `jail.local` (`jail.conf`) from `/etc/fail2ban/`, because otherwise, through equal name convention, you may get conflict in tables, chains or rules in your system actions (like iptables, etc.)