[Bug 300563] rpcbind(8): UDP GETADDR returns the wrong address since 9f48eea36607; lockd fails

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 08 Nov 2026 20:25:21 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=300563

Steve Rikli <sr@genyosha.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sr@genyosha.net

--- Comment #3 from Steve Rikli <sr@genyosha.net> ---
I was referred here by des@ in freebsd-hackers thread,
  https://lists.freebsd.org/archives/freebsd-hackers/2026-November/007030.html

and I believe I have a pretty simplistic reproduce of this issue on a
stable-15 NFS server:

$ uname -v
FreeBSD 15.1-STABLE stable/15-n285074-750cc0502912 GENERIC

$ ifconfig -lu
igb0 em0 lo0

igb0: 172.16.4.9/24
em0: 172.16.0.9/24

The NFSv3 client is only connected to 172.16.0.0/24, while 172.16.4.0/24 is
not routed and unreachable. When client tries to write to the server it
hangs, and "lockd not responding" is returned.

If I temporarily reconfigure (swap) the NFS server network and cables like so:

igb0: 172.16.0.9/24
em0: 172.16.4.9/24

the NFSv3 client on 172.16.0.0/24 writes normally. FYI, in this case the
FreeBSD 15 upgrade from the mailing list thread was likely not root cause,
I think the real trigger was the network hardware connection change we did
during the upgrade.

I'll see if I can work out the patch also.

-- 
You are receiving this mail because:
You are the assignee for the bug.