Date: Tue, 25 Oct 2022 16:19:54 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 267301] nfs uses udp for portmapper even when proto=tcp specified Message-ID: <bug-267301-227-pgfUyue0VA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267301-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267301 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |rmacklem@FreeBSD.org --- Comment #2 from Rick Macklem <rmacklem@FreeBSD.org> --- Created attachment 237626 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=237626&action=edit Modify rpcb_getaddr() so that it might use TCP for the Portmapper This patch comments out the code in rpcb_getaddr() that forces use of UDP. Although not yet tested, I believe this will make the function use TCP if the nconf argument specifies TCP. (I am working on getting a build done to test this.) I did this instead of deleting -DPORTMAP from Makefile.inc because Linux still uses Portmapper Version 2 protocol and deleting -DPORTMAP would disable Version 2. As such, this patch results in less change and, therefore, less likelyhood of causing a POLA violation. Hopefully the reporter can test this for the Azure mount case? -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267301-227-pgfUyue0VA>