
On Wed, Dec 3, 2014, at 06:51 AM, Ludwig Nussel wrote:
We had and have enough fun with alternative network manangement and init systems already. No need to extend that to firewalls :-) So I'd prefer one solution properly integrated rather than two half-baked ones.
Let's collect a list of differences/missing features to have proper facts to evaluate whether firewalld can replace SFW2 resp which effort is needed to achieve that. The hint with the logging is already a very good one. Do we have a wiki page for firewalld yet?
'Fun' isn't the 1st word that comes to mind ... But your point's certainly well made. Feature request #1 from us: zero hard dependencies, especially when considering "proper integration" (whatever that ends up being). Our need is to *cleanly* rip-out / disable whatever's native -- SF2 or firewalld -- and implement a different solution. For us, currently, that's Shorewall. Its capabilities, and especially its best-in-class / extensive documentation, are unmatched by either of the 2 solutions being discussed here. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org