On 08/30/2016 11:13 AM, Giovanni 'ItachiSan' Santini wrote:
Good morning, I am contacting you as I have a weird issue. I upgraded firewalld from 4.1.2 to 4.3.3; in 4.1.2 I never had problems with Samba shares, but, with the last update, I can't access my Samba server. I tried disabling and re-enabling the samba service in the firewalld configuration, but I didn't have success. The only way I can access my Samba server is to disable firewalld... I can't figure out why it won't work using the proper service. Thanks in advance.
Hello Giovanni,
this might be related to this issue that is already fixed in git repo:
https://github.com/t-woerner/firewalld/commit/42faa017bdf89ea4d050ee7a5d5a28...
Helper modules for services that are enabled in the default zone before starting firewalld are loaded, but not for services that are enabled in an already active zone.
This happened because for these zones the FirewallZoneTransaction is used directly and because of this the added modules are simply not used.
Please verify if the nf_conntrack_netbios_ns is loaded after enabling the samba or sambe-client service:
lsmod | grep nf_conntrack_netbios_ns
You can manually load the module with
modprobe nf_conntrack_netbios_ns
If your issue is then solved, then the upstream fix will help you.
If not then there is another issue.
Regards, Thomas