[SOLVED] Problem with OpenBSD as nfs client

philippe972 · 04-29-2018, 09:59 AM

Hi,

First, im new with OpenBSD 6.3 that i run in Virtualbox.

I try to setup a NFS share :
server is Fedora workstation 28
- exports file looks like this

Code:

/home/filip/Documents 192.168.1.1238 (rw)
/home/filip/Public 192.168.1.128 (rw)

Of course NFS is active on the server

client is Openbsd 6.3 and i have this message when i try to mount a share :

Code:

filip@openbsd:~$ sudo mount -t nfs 192.168.1.85:/home/filip/Documents /mnt/nfs_Documents/
NFS Portmap: RPC: Program not registered

I will be happy to find a solution after long time on google without succes.
Thanks for help
Philippe.

jggimi · 04-29-2018, 11:16 AM

First, assuming this invalid address is a copy/paste typo both here and in your post on misc@, and is not actually in your exports(5) file:

Quote:

Originally Posted by philippe972

Code:

/home/filip/Documents 192.168.1.1238 (rw)

Please follow this advice from misc@, which requested you use rpcinfo(8) to discover what could be seen by the client on the server at 192.168.1.85.

$ rpcinfo -p 192.168.1.85

When NFS/RPC connections are not blocked, you should obtain output that looks something like this, which I have obtained from a nearby NFS server here.

Code:

   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp    632  mountd
    100005    3   udp    632  mountd
    100005    1   tcp    752  mountd
    100005    3   tcp    752  mountd
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs

philippe972 · 04-29-2018, 12:01 PM

Hi jggimi

My export file on server was correct

Code:

/home/filip/Documents 192.168.1.128 (rw)

probably a mistake by typing my post

And this is the output of rpcinfo :

Code:

filip@openbsd:~$ rpcinfo -p 192.168.1.85
   program vers proto   port
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  51927  status
    100024    1   tcp  46983  status
    100005    1   udp  20048  mountd
    100005    1   tcp  20048  mountd
    100005    2   udp  20048  mountd
    100005    2   tcp  20048  mountd
    100005    3   udp  20048  mountd
    100005    3   tcp  20048  mountd
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    3   tcp   2049
    100021    1   udp  57813  nlockmgr
    100021    3   udp  57813  nlockmgr
    100021    4   udp  57813  nlockmgr
    100021    1   tcp  40445  nlockmgr
    100021    3   tcp  40445  nlockmgr
    100021    4   tcp  40445  nlockmgr

jggimi · 04-29-2018, 12:39 PM

Thank you. This indicates that RPC/Portmap is running, and the services are available.

I will guess that your mount is failing because you are mounting the filesystem as root, using sudo. There is no map for root defined in your posted exports file, and the Fedora NFS server maps root to user "nobody" by default, according to:

https://fedoraproject.org/wiki/Admin...uide_Draft/NFS

But this is a wild guess.

philippe972 · 04-29-2018, 01:21 PM

Acordind to the link below, i modify my exports file to

Code:

/home/filip/Documents 192.168.1.128 (rw,no_root_squash)

and restart the server but this don't solve the problem

Code:

filip@openbsd:~$ mount 192.168.1.85:/home/filip/Documents /mnt/nfs_Documents/
NFS Portmap: RPC: Program not registered

Code:

filip@openbsd:~$ sudo mount 192.168.1.85:/home/filip/Documents /mnt/nfs_Documents/
NFS Portmap: RPC: Program not registered

jggimi · 04-29-2018, 01:22 PM

Some local testing indicates that mounting as root without user mapping should be successful. Sorry for misleading you above.

You might continue by replying to your thread on the misc@ mailing list.

philippe972 · 04-29-2018, 01:39 PM

Thanks for your help jggimi.

I will continue on misc@

philippe972 · 04-30-2018, 08:47 PM

With help of misc@ i found the solution :
just add the TCP option to fstab file on the client

jggimi · 04-30-2018, 09:05 PM

I'm glad you found a solution.