Hi,
How to avoid to see all folders by using NFS protocol?
Is there a way to avoid to see no media folders like trash, .wdtlive and other folders belonging to the server but not useful for media streaming?
Hi,
How to avoid to see all folders by using NFS protocol?
Is there a way to avoid to see no media folders like trash, .wdtlive and other folders belonging to the server but not useful for media streaming?
Mulanee wrote:
Is there a way to avoid to see no media folders like trash, … and other folders belonging to the server but not useful for media streaming?
Why are you exporting those volumes if you don’t want them visible?
If you must export them, then just don’t mount them into the media library.
I want to see them on other Linux clients.
Maybe there is a NFS option allowing not to see them in WDTV and to mount them in Linux client only by selection.
you woudl do this on server side
edit your exports file, so that WD only has permission/access to the one folder
It should be the opposite:
my Linux client sees everything, my WDTV sees only video photo movies folders (or declared as)
that’s my point you do it on the server side by editing the export lines that you want available only to other unix clients
example, 192.168.0.0/28 allows the first 16 IP addresses, from 192.168.0.0 to 192.168.0.15, to access the exported file system, but not 192.168.0.16 and higher.
then you just set some static IP addresses on your WD to make sure it is outside the range, and of coarse make sure your other linux clients are inside the range
so it might look like this
/media/Drives/Photos/Photos 192.168.1.0/24(rw,no_root_squash,sync)
/media/Drives/without/WDaccess 192.168.1.0/28(rw,no_root_squash,sync)
then set your WD to 192.168.1.16
and your other linux client to 192.168.1.10
besides that doing it on the WD side, would require custom firmware
http://forum.wdlxtv.com/viewtopic.php?f=23&t=9048
use xmount and net.mounts scripts to access only the shares you want
192.168.0.0/28 allows the first 16 IP addresses
You mean 29 first addresses?
It looks almost working even without custom firmware, with export like this, where 192.168.1.21 is wdtv
/volume1/video 192.168.1.21(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
But when I add linux client (192.168.1.2) to see IMAGES only and wdtv (192.168.1.21) to see video only, like this, wdtv sees IMAGES as well, it should not.
/volume1/IMAGES 192.168.1.2/10(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
/volume1/video 192.168.1.21(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
no I mean
that
192.168.0.0/28 allows the first 15 IP address
the lapst part /28 gets converted to a binary
which allows 15 ip addresses
here’s an example thread
http://ubuntuforums.org/showthread.php?t=1670845
particularly this part, since he calculated several example ranges
192.168.1.0/28 192.168.1.0 - 192.168.1.15
192.168.1.16/28 192.168.1.16 - 192.168.1.31
192.168.1.32/27 192.168.1.32 - 192.168.1.63
192.168.1.64/26 192.168.1.64 - 192.168.1.127
192.168.1.128/25 192.168.1.128 - 192.168.1.255
so for your example, using /10
I would have to run a binary calculation, but it probably does not mean what you think
if your WD’s ip is 192.168.1.21
then set images to 192.168.1.0/28 and the WD will not be able to access it
but the linux client at 192.168.1.2 will be able to access it
if /__ has to be in hexa, I guess that 21 (10) is equal to 15 (16)
A long time I didn’t thought about that
In fact I just use 2 clients for NFS, one with Linux (arch) IP 192.168.1.2 and the other one WDTV IP 192.168.1.21
arch station needs all the rights, WDTV is read only
Something like that should work
/volume1/IMAGES 192.168.1.2(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
/volume1/video 192.168.1.21(RO,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
Mulanee wrote:
if /__ has to be in hexa, I guess that 21 (10) is equal to 15 (16)
A long time I didn’t thought about that
It’s not hexadecimal. It’s decimal.
This doesn’t work
/volume1/LOGICIELS 192.168.1.2/28(rw,sync,no_root_squash)
/volume1/MOVIES 192.168.1.21/28(ro,sync,no_root_squash)
WDTV (192.168.1.21) sees /volume1/LOGICIELS
Mulanee wrote:
This doesn’t work
/volume1/LOGICIELS 192.168.1.2/28(rw,sync,no_root_squash)
/volume1/MOVIES 192.168.1.21/28(ro,sync,no_root_squash)
WDTV (192.168.1.21) sees /volume1/LOGICIELS
It will SEE it – but it shouldn’t be able to connect to it…
It will SEE it -- but it shouldn't be able to connect to it...
I just doesn’t want to see it
I’m still not convinced your setting the exports file correctly
example provided was 192.168.0.0/28 which is known to only allow 15 ip addresses
but you are using 192.168.0.2/28 the binary calculation will be different
example using 192.168.0.0/24 actually allows any IP address on the network access to the exported directory
as a simple test, do what you already suggested earlier
/volume1/IMAGES 192.168.1.2(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
/volume1/video 192.168.1.21(RO,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=1025,anongid=100)
no binary calculations happening
just 2 exports each one only available to 1 specific IP address
now that said, as for visability, I’ve never had the need or want to try and do this, so Tony very well may be correct in stating that it would still be visable, just not accessable
you will not know unless you try
if Tony is correct, then your final options are
custom firmware
use a different protocol, ie nfs for WD, and samba for everything else, etc …
If you’re constantly navigating share-by-share, then I would suggest that you use the MEDIA LIBRARY instead of simple shares.
Media library is a nightmare, always making wdtv computing and uploading a lot of unwaznted files and folders in the server.
DLNA server should have been a good option if my Syno NAS should have ran correctly.
At the end I will be happy with my NFS shares when I will find the proper tuning.