* Bjoern Voigt <bjoernv(a)arcor.de> [05-31-19 10:52]:
I recently tried to migrate from SuSEfirewall2 to
FirewallD on my
Tumbleweed desktop. The automatic migration failed completely. No
single port from my SuSEfirewall2 configuration was opened in FirewallD
after the migration.
Now I plan to migrate an openSUSE Leap server (from 42.3 over 15.0 to 15.1).
Networking on both computers (desktop and server) is very similar. Both
computers have a network interface eno1 and a bridge br0, which connects
the hardware interface eno1 with the KVM machines. There are additional
network interfaces to docker containers (docker0) and KVM machines
All docker containers and KVM machines need client access to the
Internet. That's why the firewall for the host needs a routing
I found some blog articles about FirewallD configuration for routing.
But the blog articles I found only mention FirewallD direct rules for
configuring IPTables FORWARD rules. I can't find more high level
How are you configuring routing with FirewallD?
the migration app worked for me ?? but I did have to do a small amount
of tweaking. there is a yast plugin for firewalld and there is
firewall-config (which is for firewalld).
and I did a little goooogggelling for specific examples
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
openSUSE Community Member facebook/ptilopteri
Registered Linux User #207535 @ http://linuxcounter.net
paka @ IRCnet freenode
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org