Hello Giovanni,
On 08/30/2016 04:22 PM, Giovanni 'ItachiSan' Santini wrote:
Il 30/08/2016 13:58, Thomas Woerner ha scritto:
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_nsYou can manually load the module with
modprobe nf_conntrack_netbios_nsIf your issue is then solved, then the upstream fix will help you.
If not then there is another issue.
The module is properly loaded, lsmod gives me this output: $ lsmod | grep nf_conntrack_netbios_ns nf_conntrack_netbios_ns 16384 0 nf_conntrack_broadcast 16384 1 nf_conntrack_netbios_ns nf_conntrack 90112 8 nf_conntrack_netbios_ns,nf_nat,nf_nat_ipv4,nf_nat_ipv6,xt_conntrack,nf_conntrack_broadcast,nf_conntrack_ipv4,nf_conntrack_ipv6
I am using the home zone for my WiFi connection. The default zone is the public one though. I sincerely have no idea of why Samba is completely blocked. ^^"
More tests are needed now:
1) Are the samba related rules in place for ports 137/udp, 138/udp, 139/tcp and 445/tcp?
2) Is the zone assignment correct in the output of "firewall-cmd --get-active-zones"?
3) Is samba working if firewalld is turned off temporarily?
Regards, Thomas