After the most recent zypper dup to the latest Tumbleweed snapshot, I tried running firewall from yast2, and after installing a couple of packages, the firewalld utility started up instead of the SuSEfirewall2 GUI I was expecting.
Have I made a mistake or has Tumbleweed moved away from the old firewall tools?
If I’ve made a mistake (it’s possible: I was on the phone when I tried to edit my firewall settings) how can I revert to the old system? If this is part of a broader move away from SuSEfirewall2, then I guess I’m cool with that.
Either way, I’d really appreciate if someone could let me know.
I couldn’t find anything TW-specific, but it does indeed appear there is a move from SuSEfirewall2 to firewalld being worked on for SLE 15 (and hence Leap), so that would explain why TW is moving to it already I guess.
So it seems like SUSEfirewall2 is still the default firewall which gets started on boot, but when I try to change firewall settings in YaST, it launches the firewalld GUI, which is annoying because I actually wanted to change my firewall settings - which are far too stringent by default on my University’s WiFi network. Anyone have any advice?
Ever since the introduction of the new GUI in YaST (even though firewalld wasn’t enabled) I’ve found that things which worked fine before (e.g. torrents and video calls in Wire messenger) no longer function as expected. Enabling firewalld and disabling SuSEfirewall2 doesn’t seem to help. A little frustrating.
Torrents should not involve any real unusual functionality, so you may need to verify that your torrent app’s port is configured properly in your firewall (firewalld’s public zone by default).
VoIP on the other hand can be implemented using a variety of protocols, so you’ll likely need to start with identifying the protocol used, and then the locations of each machine communicating each other, paying particular attention if you traverse any NAT.