Re: kern/53166: NFS default to UDP; it should really default to TCP

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR kern/53166; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>, gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost
Subject: Re: kern/53166: NFS default to UDP; it should really default to TCP
Date: Sun, 8 Apr 2018 10:04:13 -0400

 On Apr 8, 11:29am, hauke%Espresso.Rhein-Neckar.DE@localhost (Hauke Fath) wrote:
 -- Subject: Re: kern/53166: NFS default to UDP; it should really default to T
 
 | On Sun,  8 Apr 2018 00:45:00 +0000 (UTC), thorpej%me.com@localhost wrote:
 | > NFS defaults to using UDP as a transport.  It really should default=20
 | > to using TCP.  There's really no reason to default to UDP anymore=20
 | > (servers that don't properly support TCP are ancient, at this point).
 | 
 | While I have no opinion on changing the default as long as udp=20
 | transport is an option, I do want to point out that nfs over udp is a=20
 | lot more robust when run through a stateful packet filter.=20
 | 
 | With tcp, crash your router, and you'll have to walk up to and reboot=20
 | all your clients.
 
 Did this (the default change request) came up because you are trying to
 boot over wifi and it is lossy because of the fragmentation? Or there
 was another reason? I thought that the boot code has been changed to do
 rsize=wsize=1024 for that reason...
 
 christos