Am 02.12.2014 um 09:49 schrieb Mathias Homann:
For now I*'ve made the service for firewalld conflict with the SuSEfirewall2 services, so that should be fine. As far as a migration path goes, firewalld comes with a way bigger set of predefined services and zones than SuSEfirewall2 so any "migration path" would be quite straightforward, and not that much different from the initial implementation of any firewall.
The question is how painful the migration path is. SuSEfirewall2 exists for a long time so there are many people with grown configurations. So the premium migration path would be if /etc/sysconfig/SuSEfirewall2 could be converted automatically, at least to some degree. I guess there is no chance for custom rules though. Also, packages that drop stuff in /etc/sysconfig/SuSEfirewall2.d/services need to be adjusted to do the equivalent for firewalld.
I'll see if I can find some time to write up a readme or such, but I don't think I have editing rights on the wiki, so some else would have to put it there.
It's a wiki, you just need to log in with your opensuse account to be able to edit pages :-) cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5; 90409 Nürnberg; Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org