Hello, In the Message; Subject : Yast-Firewall - shouldn't it restart firewall when changes are made? Message-ID : <a3c9310a-3203-4bd8-a295-6bb5b5a48a8e@gmail.com> Date & Time: Sun, 14 Jul 2024 18:07:33 -0500 [DCR] == "David C. Rankin" <drankinatty@gmail.com> has written: [...] DCR> I used Yast firewall to put the wireless connection on "home", set it as DCR> default and added postgresql to the allowed services and clicked DCR> "Accept". The remote connections continued to fail, so I used DCR> netstat to check whether the port was open with: DCR> $ sudo netstat -tulpn | grep LISTEN DCR> Neither postgresql or port 5432 was shown. This seemed DCR> bizarre. So I manually restarted firewalld (e.g. sudo systemctl DCR> restart firewalld) and bingo, the port was open. DCR> Isn't Yast-Firewall supposed to restart firewalld after DCR> changes are made? It's a hassle, though. On YaST2, System --> Service Manager --> restart Firewalld service. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --