Dave Howorth wrote:
Ah. Google finds it: "susefirewall2-to-firewalld"
I read the README as they suggested but am now confused. It says it is a simple script but it talks about 'start/stop/restart firewalld and SuSEfirewall2 services'. That doesn't sound simple to me.
Hi Dave it really is very simple. A firewall is merely a set of rules of what to allow and what not to allow. stop firewall = "delete rules", start firewall = "set rules".
I'd have thought a simple script would migrate a configuration by editing some configuration scripts? I'd be happy to do that, against the event that I might find some reason to use firewalld in the future.
When you install firewalld (at some point in the future), it'll no doubt come a useful set of default rules. There is no need to do anything now.
OTOH, if I just start firewalld as a new installation, I would hope there's a graphical first-time-run program to guide me through setting it up? In which case, there wouldn't be much point in preserving a configuration I already know has some problem.
Exactly.
If you are sure you do not want to migrate settings, then just delete SuSEfirewall2 packages, then enable and start firewalld.service, then open the needed ports.
But if I don't want a firewall, why not just delete it?
Yup. If it is running, maybe stop it. -- Per Jessen, Zürich (20.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org