Thanks, so it it like saying "I'll take foreign cultures for 50, Bob" ... or is it a reference to 10 Downing?
I'd use this:
Code:
/media/PrimaryData/Documents 192.160.1.*(rw,async,root_squash,no_subtree_check)
lacking any other information. My actual NFS exports look like this:
Code:
/d/D1 hadar(rw,async,root_squash,no_subtree_check,fsid=1)
because I don't want to blindly export file systems to the world. The fsid number just needs to be unique for each export location, not for each client.
The extra options aren't needed for any Linux NFS server in about 20 yrs. They are negotiated based on the client and server.
My real problem is with the '*' you are using to allow any clients to have access. This can slow things down greatly. Put in the static IP for your firestick. If it doesn't have one, give it one and use that. DNS lookups can be slow and are used in all sorts of calls that nobody really expects. For example, sudo does DNS lookups because the config file might be setup to support many different host systems with different settings, each limited by the hostname/DNS name.
I've had problems with DNS on Ubuntu for about 15 yrs - all started when they added resolvconf, then when they switched to systemd-resolved and mDNS it got worse. You probably want to swap the order of your DNS servers in the config file, so the local one is checked first, before hitting the internet. I run a pair of local DNS to prevent this, but that's beyond what most people would want.
BTW, you could also try using the mDNS name rather than the '*' in the exports file. You'll need to know the firestick's mDNS name .... I have no idea what it may be. Sorry. Hopefully, it is unique and different from everyone else's in the world.
As for the client-side config, There's probably some menu that shows the NFS settings, right? I have Roku, but it won't access NFS storage. Plus, no way would I allow that Roku to be located on the same network as my important systems.
The FBI has been pretty clear that we shouldn't trust any IoT devices on our networks. They suggest putting them onto a different subnet. https://www.fbi.gov/contact-us/field...-of-things-iot is always a good reminder, if we forget. Heck, in the last 2 weeks, huge numbers of IoT devices were found, again, to have been hacked and were bring used in botnets. This stuff isn't going away. It will only get worse and worse for the rest of our lives.
