How to make nfs share accessible across subnets?

[Bo Berglund]

On Fri, 11 Feb 2022 18:32:12 -0500, Little Girl <littlergirl at gmail.com> wrote:

>Last, but not least, when something like this happens to me and I
>just simply can't figure out what I'm missing, my strategy is to wipe
>out what I've currently got (remove all traces of NFS from the
>offending machines) and start over. You had it working once before,
>which means you know what you're doing. Perhaps if you go through all
>of the steps again from the ground up, it will sort itself out.
>

Well, I got a tip on using tcpdump to monitor the traffic while failing to
connect and it turned out that for the case of connecting to an NFS share on
another host on the LAN its real IP address was used, but when trying to mount
the NFS share on the server that is also the OpenVPN server the IP address used
was the tunnel specific NAT-ed address! Thus a 10.8.139.xx address.
And therefore the nfs server rejected it...

After adding the tunnel network to exports as well as widening the client spec
for the network to encompass 1024 addresses (which covers both the 117 and 119
networks) the final export command looks like this:

/home/bosse/www/MSNBC -rw,sync,no_subtree_check,insecure  192.168.116.0/22
10.8.139.0/24

The last part covers the tunnel access addresses and the first both of the LANs
(home and remote).

Now working OK.

PS:
Regarding my various use of VIDEO and video:
This was an attempt at hiding the real names MSNBC and msnbc, which is the USA
news network I download nightly (in Sweden) for viewing daytime....
But I finally gave up on that futile hiding action.
DS

-- 
Bo Berglund
Developer in Sweden