never thought that samba was broadcast, I thought the destination would be just the server IP , thanks you for the tip on how to debug it, I love linux 
there is everytime something new to learn 
I will try it and see what changes
Thank you very much @subzero79
Sure! my bad..
here is the full ruleset
# Generated by iptables-save v1.4.21 on Mon Aug 21 19:43:20 2017
*nat
:PREROUTING ACCEPT [1061:311024]
:INPUT ACCEPT [25:1290]
:OUTPUT ACCEPT [831:53479]
:POSTROUTING ACCEPT [830:53419]
-A POSTROUTING -s 10.8.0.0/24 -j SNAT --to-source 192.168.1.25
-A POSTROUTING -s 10.8.0.0/24 -j SNAT --to-source 192.168.1.25
-A POSTROUTING -s 10.8.0.0/24 -j SNAT --to-source 192.168.1.25
COMMIT
# Completed on Mon Aug 21 19:43:20 2017
# Generated by iptables-save v1.4.21 on Mon Aug 21 19:43:20 2017
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p icmp -j ACCEPT
-A INPUT -d 192.168.1.25/32 -p udp -m udp --dport 9 -j ACCEPT
-A INPUT -d 192.168.1.25/32 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p udp -m udp --dport 137 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p udp -m udp --dport 138 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p tcp -m tcp --dport 139 -j ACCEPT
-A INPUT -d 192.168.1.25/32 -p tcp -m tcp --dport 443 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p tcp -m tcp --dport 445 -j ACCEPT
-A INPUT -p udp -m udp --dport 1194 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p tcp -m tcp --dport 8096 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p tcp -m tcp --dport 8920 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p tcp -m tcp --dport 9091 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.25/32 -p tcp -m tcp --dport 55413:55414 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -j ACCEPT
COMMIT
# Completed on Mon Aug 21 19:43:20 2017
Can't see why it shouldn't work 
I set up my OMV 3 pretty straight forward and everything seems to works fine since the beginning.
Smb shares worked fine from the start, then I decided to use iptables rules from the browser interface to make my server more secure.
I followed @tekkb instructions for firewall settings to permit samba shares and other services I need.
To be more specific for samba I added:
and added a couple of my own to allow outbound traffic originated locally from the server.
The equivalent to those two rules:
iptables -I OUTPUT -o eth0 -d 0.0.0.0/0 -j ACCEPT
iptables -I INPUT -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPTEverything seemed to work just fine, except then now every time the server reboot samba got disconnected from the network and I cannot access it through my windows machine.
Every other services is working just fine with the firewall rules, so it's just samba acting weird.
As a workaround I have to disable iptables rules and then everything shows up again, then enable them again and everything works fine until next reboot and so on (that's really strange).
I thought those 4 rules where enough for samba to work...am I missing some other ones?
Did anybody have the same problem ever?I would like to solve this problem rather than have iptables disabled.
I think something went bad during the upgrade from omv 3 beta and the stable release, so I went ahead deleted everything and install omv from scratch, everything is back to normal now and works as it should be.
I would just use ext4. xfs is hard to recover files from if something goes wrong or is accidentally deleted. If you are interested about btrfs, try it out in a VM but I don't think compression will do much good with backups (already compressed).
Ok thank you! I will follow the suggestion then everything on ext4, I was thinking btrfs is ready for production now (apart from raid 5\6) but if you suggest me to play with it in a vm, is not really I guess, so back to basics and ext4 then 
Thank you
New shtudown and reboot t's happening again 
.
The samba share doesn't appear on network and again I can see the hard disk mounted through the ssh and files are there....
Anybody have ever experienced this?
Could it be the wd red 2 tb hard disk faulty?! (S.M.A.R.T. seems ok though o.O).
This time neither @ryecoaaron method of omv-mkconf fstab seems to work out to bring samba back.
It also seems not related with the wd red nor the xfs filesystem, I tried to create different share on different hard disks with different filesystems and samba is still not reachable by my other computers on the network...
So it seems a samba problem indeed, still can't understand what's going on
Hi folks,
I would like to rebuild my omv nas with omv 3.0.86, it will be used mainly for stream through plex and backup my home pc so nothing fancy, but I'm a bit stuck on which one filesystem to use to best suits my setup, so I'm looking for suggestions here, anyone would like to share with me different thoughts?
Right now here is my setup and my idea any motivated suggestion on that would be great:
Build:
SSD = Omv os -> EXT4
is the default from the installer can't see any way to change it, it's ok ext4 for main os is good.
2 tb wd red = will store all my movies tv shows etc to stream through plex and will be the base for shared folder with samba aswell -> XFS
I think xfs is a good choice for this type of hard disk usage, am I wrong? do you guys suggest another filesystem for this one?
1 tb wd blue = backup hard disk for my home pc to use with urbackup -> BTRFS
I picked this because I'm interested in all btrfs features for recover compression etc, I also see through urbackup site that btrfs is suggested with urbackup due to compression layer, so I hope to get it right (but again if you have a different idea you are welcome to share)
2 tb wd blue = parity disk of snapraid for both the upper hard disks -> XFS or BTRFS or EXT4
This is the most doubtful, I cannot decide, I thought xfs could be a good choice for something so big that change so few, but then I thought btrfs compression bitrot failsafe and other feature could be great for having parity stored on it (I also read from the main snapraid site that maybe issue could arise with btrfs+snapraid? something related with speed etc.? am I wrong?) or just go with the old ext4. So again any idea about this could be really great!
Indeed I'm aware of btrfs problem with raid 5\6 but I'm not planning to use raid at all, I will use all of them as separated single disks, so I thought the feature of it were worth to be considered instead of going directly to ext4 direction for all of them, but I'm open to any suggestion.
Thank you in advance for your suggestions
After playing with a bit more it seems everything went back as it should 
Looking around the forum I found this thread OMV loss configuration not really my issue, but somewhat similar to the outcome so I just run the command suggeste by ryecoaaron
Display MoreDIdn't see it. People don't use the spoiler type very often
Not sure why your mntent entry is gone since it exists in fstab. Here is what I would do:
omv-mkconf fstab
reboot
The drive shouldn't be mounted now so mount the filesystem in the web interface
create new shared folders.
After reboot everything seems normal.
This is really strange I can't imagine for the life of me what did happened, about the topic what does omv-mkconf fstab really does to fstab? I tried to look at the code, but I didn't really understood it, I'm trying to figure out what was the matter.
Any thoughts or hints in the right direction on this?
Hi folks.
I'm having a weird issue with my omv installation never experienced anything like that.
I was playing around with my little nas with omv and the autoshutdown plugin/wake on lan, after a shutdown and reboot everything went bad.
The hard disk with the samba shares disappeared from my network.
I tried to troubleshoot it without success, what is even weird is that omv weblogin tells me the filesystem is mounted and everything is working fine, moreover if I ssh into my server looking for the mounted drive it's there in the /srv/ directory as it should be and I can see all the files (so I guess is not a problem of hard disk being dead, also is 0day new so..)
I tried also to force umount the hard disk with umount -l /srv/dev-ecc.ecc. and mount again everything went fine, but still I can't access samba on network.
I thought was an issue with iptables but I checked all the rules and they seems all fine.
I'm out of ideas..any help would be great!
some specs:
omv 3.0.86 (erasmus)
kernel: 4.9.0-0.bpo.3-amd64
sda1 ext4 = SSD CORSAIR Force LS -> omv os
sdb1 xfs = WD red 2 tb -> nas files (samba share plex movies and ecc. calibre and transmission download folder) this is the hard disk I'm having issues with
sdc1 btrfs = WD blue 1 tb -> backup
sdd1 xfs = WD blue 2 tb -> snapraid parity
Everything were smooth before the autoshutdown\wake on lan test and now I don't know what did went wrong any ideas?
