On 10/27/24 12:57, Georg Pfuetzenreuter via openSUSE Users wrote:
On 10/27/24 8:29 PM, Marc Chamberlin via openSUSE Users wrote:
Hi, I have a system that was upgraded to OpenSuSE 15.6 x64 and now firewalld is whimpering about a service called wsdd. Whenever I try to make a change with firewall-command, such as adding or removing a service to be allowed/disallowed by the firewall, and then trying to update my permanent setting from my runtime settings, I get bitched at by firewall-config and get told to run the following command -
#firewall-offline-cmd --check-config Configuration error: INVALID_SERVICE: Zone 'internal': 'wsdd' not among existing services
Any ideas why firewalld is belly-aching about "wsdd"? My Duck Duck Go searches tells me that wsdd is used to make shared files and directories visible to MS machines, which is a feature I want. Further research shows that there is no package in the repositories for wsdd for OpenSuSE 15.6, is this being dropped? If so, how do I fix this mess and retain the ability to share files with Windoz systems?
As always, many thanks in advance for taking the time to help me out and guiding me back into the OpenSuSE light! Marc..
--
Hi Marc,
first try to remove the service from the "internal" zone (as indicated in the error output) using firewall-cmd:
``` firewall-cmd --zone=internal --remove-service=wsdd --permanent firewall-cmd --reload ```
Should this not be successful, then manually remove it from the configuration. Open the file /etc/firewalld/zones/internal.xml in an editor, and remove the line `<service name="wsdd"/>` (or similar). Then use `systemctl restart firewalld` (reload would normally suffice, but restart might be needed if it's already not responsive to the firewall-cmd operations).
I don't know about what happened to "wsdd".
Best, Georg
Thanks Georg, you proved yourself in the class of gurus! I couldn't remove wsdd using the firewall-cmd, it just kept whining about the invalid configuration and immediately exits. But manually removing the wsdd service with an editor got firewall-cmd purring again like a kitten. I don't grok why this became an issue for me, and worry that I made need this service later on, from what I read in the descriptions about it. Oh well, its a workaround for now and will keep me going forward... Marc...