More specific configuration file to FreeBSD OS and ipfw

[njrizzo]

HI,

I wrote this to more specific on FreeBSD OS and IPFW I created some new variables, because on my system when I ran this by first time, create some problems, like putting a new rule after the last deny rule.

I suggest this variables names to add more functionalities

rulenumber - rule number under all ban IPs will be nic - nic name on no default network interface proto - to choice a better protocol (tcp, udp or both, or others)

TIA

Nilton J. Rizzo

[coveralls]

Coverage increased (+0.009%) to 96.616% when pulling 989166a1f39289abde14bbb4d5993a7ddce9b8f8 on njrizzo:0.10 into 52ed6597b245b13a2e8e10bac7eaddbd8629cb28 on fail2ban:0.10.

[codecov-io]

Codecov Report

Merging #1709 into 0.10 will decrease coverage by 0.01%. The diff coverage is n/a.

@@            Coverage Diff            @@
##             0.10   #1709      +/-   ##
=========================================
- Coverage   94.22%   94.2%   -0.02%     
=========================================
  Files          77      77              
  Lines       11554   11554              
  Branches     1753    1753              
=========================================
- Hits        10887   10885       -2     
  Misses        390     390              
- Partials      277     279       +2

Impacted Files	Coverage Δ
fail2ban/server/utils.py	85.77% <0%> (-0.89%)	:x:

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 52ed659...bf30524. Read the comment docs.

[sebres]

BTW why a new config file? Additionally can you take a look in #1690. Possibly we can combine this to the single file.

[njrizzo]

I'm think that the #1690 is too complex more than necessary All FreeBSD administrator compile into kernel a ipfw module or put it in loader.local.conf. Not is necessary too many complexity

IMHO