I thought I would throw this out for discussion based on my recent experience with this particular package. I installed this in my new installation of OpenSuSE15.0. I thought initially this package SuSEfirewall2-fail2ban was a good idea for integration between these two applications. But based on my recent experience with trying to install it I got to say either this package needs to be tossed or fixed, as it stands it seriously breaks SuSEfirewall2 and it is not an easy thing to debug. Some of the problems I had, once it was installed were - 1. It forces the startup of the fail2ban service each time SuSEfirewall service is started, not something you might want sometimes, and not easy to figure out how to discover and stop this relationship. 2. It has/causes dependency errors in the systemd launcher that breaks the ability of the SuSEfirewall service from starting properly. (this problem is widely talked about in other distros as well with their versions of firewalls, bug reports have been submitted, and no fix is yet available) 3. It caused/forced my networks internal NIC card to be relabeled as an external facing NIC, which then caused me to have 2 external facing NIC's and that broke all sorts of other services I had running on my server. (which led me on many wild goose chases trying to track down errors that other services such as Apache2, Tomcat, Apache James and even Named were reporting.) Given all the headaches this package caused me, my recommendation is to get rid of it, it is not really necessary AFAIK and my system seems to be running fine without it. Want to have some fun? Try it yourself, install the fail2ban service and this package also. Then restart the SuSEfirewall2 service and watch it belly ache. If you have two NICs like I do, one ext and one int then you will also see what happens with the int NIC. Yarrg! Marc... -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org