Turns out that Samba and activating the possibility to connect to it from the WAN in the router opens port UDP 137. I got an email form my ISP telling me my connection could be put in quarantine if I didn’t resolve the issue. I also found this topic on the forum Stop nmbd (i.e. ports 137/138)
Shouldn’t it be wiser to comment out the netbios daemon in the start script of samba4?
This in order to prevent such issues happening to new users in the future who don’t have a deep understanding of networking but do like to tinker
Hi,
Sorry for the delayed reply.
We strongly recommend using “Allow Access Samba from WAN” only within a trusted, private WAN environment — for example, when our device is placed behind another router within a home network as a secondary router.
If you need remote access to Samba, we strongly recommend using a VPN rather than exposing Samba directly to the internet.
You can follow our guide on Setting up a WireGuard Home Server to bridge safely into your local network.
That said, we will discuss this with the product team and see how this can be improved — for example, whether there could be a more convenient way to disable NetBIOS.