Re: NFSd not registering on 14.2.

From: Zaphod Beeblebrox <zbeeble_at_gmail.com>
Date: Fri, 22 Nov 2024 05:16:32 UTC
lo0 has 127.0.0.1, ::1 (both first in their lists).  It also has a pile of
other IPs that are used by jails.  This has not changed

On Thu, Nov 21, 2024 at 6:35 PM Rick Macklem <rick.macklem@gmail.com> wrote:

> On Thu, Nov 21, 2024 at 1:22 PM Zaphod Beeblebrox <zbeeble@gmail.com>
> wrote:
> >
> >
> > I've tried a lot of different combinations of rc variables.  On 13.3 and
> 14.1, nfsd in most (non-v4-only) configurations registers to rpcbind as
> expected.  This is true of restarting nfsd and using nfsd -r.
> >
> > However on 14.2, I can't contrive any configuration that registers to
> rpcbind.  Minimally, on one fairly quiet 14.1 server, I simply have
> >
> > nfs_server_enable="YES"
> > mountd_enable="YES"
> > mountd_flags="-h <my ipv6 addr> -S"
> >
> > on another, I have more:
> >
> > mountd_enable="YES"
> > nfs_client_enable="YES"
> > nfs_server_enable="YES"
> > nfsv4_server_enable="NO"
> > #nfs_server_flags="-u -t -n 12" # Flags to nfsd (if enabled).
> > nfsuserd_enable="YES"
> > nfsuserd_flags="-domain daveg.ca"
> > nfscbd_enable="YES"
> > rpc_lockd_enable="YES"
> > rpc_statd_enable="YES"
> >
> > readup for what the 14.2 server has --- but I've tried configurations
> going from the former to the latter.  None of them register.
> >
> All I can suggest is checking lo0 to make sure it is using 127.0.0.1.
> See what
> # ifconfig -a
> shows.
>
> If lo0 is not 127.0.0.1, that would explain it, since the rpcbind stuff
> uses
> 127.0.0.1.
>
> Note that 127.0.0.1 gets added automatically when "-h" is used.
>
> Btw, I don't think I changed anything w.r.t. this between 14.1 and 14.2,
> so it is likely some other network related change.
>
> rick
>