Hello!

Try connect from mac os to nfs share on my fileserver ( runs on slack64 14.0 )

write /etc/exports
/path/to/shared/folder client_ip(rw,sync) another_ip(rw,sync)

start /etc/rc.d/rc.nfsd

open in firewall 111 and 2049 ports on tcp and udp from client_ip


write in macbook ( os x 10.11) finder -> connect to server -> nfs://server_ip:

it find some time ( about minute) , then say "server not found or it turned off".
try open in fw samba ports and connect from mac via smb protocol - it see share and connect, all ok. but in need nfs....

any ideas?

Hi!

http://rlworkman.net/howtos/NFS_Firewall_HOWTO

http://docs.slackware.com/howtos:net...home_nfs_howto

1 members found this post helpful.

EDIT: Read the message above this one. Much better answer than the one that I had here.

Thanks, try read and prove it after work.
PS forget to look in slackdocs.....

readed that doc, take a look at my slackware, and decide not to use NFS.
looks like that protocol not to best for networks with filtering ( firewalling) - so many ports, and serious default slackware reconfiguration, who take a some work, and must preserved and remember to, when i change slackware version at server....

decide to stay on samba. on it sharing can be done throught open 137 - 139 port. minimal effort.

surprised, with what in mind NFS has designed to need so many ports to work? looks like someone want to get thing more and more complicate, instead try to make all simply as possible...

NFS is old tech. Firewalls within corporate networks were not that common when it was developed.

2 members found this post helpful.

yes, but is still evolutioned, as i understand?
and looks like, there is no any "new tech" in linux /unix who can become instead of NFS?

try to read about AFS, but looks like there is maybe problems to get it work on linux?
in OpenAFS project find clients only for mac os x and mswindows....

Well, you can work around the problems by forcing static ports and opening the firewalls accordingly.

https://en.wikipedia.org/wiki/Compar...d_file_systems

The ceph client is part of the kernel. Don't know about the ceph daemon; it's a available from git but not slackbuilds.

Ok, it needs snappy and leveldb from slackbuilds. I had to add a couple of --without-something flags to ./configure to get that to run.

http://ceph.com/


(For your needs, ceph might be using a flamethrower to kill a gnat. I've never used it, but the server actually doesn't compile under Slackware64 14.1 due to a header mismatch. That's git head. I had reported earlier that it appeared to compile; it actually didn't.)

1 members found this post helpful.