I've added all the example rules (including the ones for Samba) that @tekkb listed and everything is working fine except when I connect via VPN to my server, I am unable to browse my samba shares unless I delete the 'reject all rule'. I can still access OMV's web GUI and all my web apps, but not Samba unless I delete that last rule. Is there a firewall rule I can add that will grant me access to samba via VPN? Also, Ive changed my ssh rule to only allow connections from my LAN (192.168.1.0/24), but with VPN-AS, I am assigned an IP in the 172.x.x.x range. How should I edit my firewall rules to allow ssh via VPN?
Beiträge von sromaiOMV
-
-
Can't believe I forgot to list Tapatalk...even though I was using the app to post this reply. :\ Also, gReader pro is a great RSS reader with very nice widgets.
-
My most used apps:
Titanium backup
Nova launcher
ES File Explorer
Pocket
Poweramp
Pushover
Instagram
Google KeepI don't play too many games, but the Kingdom Rush series of games are pretty awesome.
-
That makes sense. Thanks for the clarification, @subzero79.
-
Also been getting these strange errors during a scan. Not sure what it actually means. Any insight would be greatly appreciated.
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/37: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/36: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/35: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/34: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/33: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/32: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/31: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/30: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/29: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/28: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/27: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/26: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/25: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/24: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/23: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/22: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/14: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/13: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/12: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/11: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/10: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/9: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/8: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/7: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/5: lstat() failed: No such file or directory. ERROR
/media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/var/run/udev/watch/4: lstat() failed: No such file or directory. ERROR -
Hi, guys. I've been getting this alert every time I run a scan on one of my drives:
A virus has been detected: /media/20285e8e-586d-4ae5-97bc-3525787a0cc5/omvbackup/usr/share/phpvirtualbox/rdpweb/RDPClientUI.swf
I've barely even used any of the VMs I've created, so I doubt I've gotten anything infected. Could it be a false positive or should I be concerned and taking precautions? Anyone else using virtualbox plugin experiencing this?
-
It works better then setting a static ip in OMV.
How is it "better" to assign static IPs via the router as opposed to doing it in OMV?
-
create file with same chmod and chown as the omv.css file.
What chmod/chown setting should be used on the custom css file?
-
I remember getting these long quota checks during bootups in previous versions of OMV. But I recently did a clean install of 1.9 and then updated to 1.11 from within the GUI, and now whenever I reboot, it doesnt even seem to do the quota checks anymore. Maybe it's disabled by default now?
Can quota checks be tested in a VM? -
Just wanted to post a follow up and say thanks to everyone in this thread, especially @tekkb for all his input and patience. I was able to get OpenVPN-AS working after a bit of trial and error. At first, I followed the instructions in the openvpnas plugin and set TLS to 1.2, but for some reason, my windows and android clients refused to connect. I then set it to 'default' and everything is working exactly as it should. I couldn't be any happier with my OMV box--except maybe for a little RAM upgrade and more drive space is always good too...but that is another subject entirely.
Thanks again, Everyone. -
Issue resolved after updating to 1.12. Thanks for the excellent work, Volker!
-
Experiencing same issues as OP in my dual nic setup on 1.11 after installing openvpn-as.
-
I had some weird errors in syslog with clamAV, so I uninstalled the plugin. However, I'm still getting cron notifications about scheduled scans telling me about an error in the config file, which is weird cause I dont even have the plugin installed on my system anymore. Even weirder, there's three clamav related updates availble in the updates section (clamav-base, clamav-freshclam and libclamav6...). I tried installing them, but it stalls at 'building dependency tree.' I also tried reinstalling the clamav plugin, which also gets stuck at the 'building dependency tree.' Any ideas what's going on?
-
Hmm...I originally tried it with the default routed setup, but I couldnt access the omv webUI, for some reason, and my android client refused to even connect to the vpn at all. I switched to bridged mode, connected with my laptop and was able to access the webUI. I have all the necessary ports forwarded properly, so im not sure what else I could be doing wrong?
@tekkb, I just gave you your 100th 'Like', BTW! Now, do we get a prize? Lol
-
Ok. The client I will use most with vpn is a windows machine, so that will be fine. But just to clarify, I have to use bridged mode in order to access the OMV webUI from within the VPN, correct?
-
Any thoughts on whether routing or bridging is more secure? I definitely want access to the OMV webUI while using the vpn, so I definitely have to use bridged mode in the AS server, right? Or is this also somehow possible with routing mode?
Thanks for all the feedback, btw. I am learning so much since I discovered OMV. You guys are awesome!
-
Cool. Thanks for the clarification, @davidh2k.
I'll revert to a snapshot and try out the newer version. -
Are system reboots necessary after installing certain updates like OMV/kernel/security updates, etc.? When and how often do you guys reboot your OMV boxes?
-
I just installed OMV 1.9 in a new VM, then installed 'openmediavault-sickbeard_1.0.1_all.deb' from here and everything seems to be working fine. If the issues people are having is with the 1.0.2 package, how come the previous version was removed along with it when it's working just fine?
-
To answer my own questions: yes, u can!
