Hi Neil- On Sep 17, 2012, at 9:54 PM, NeilBrown wrote: > It seems that with current nfs-utils, "proto=udp" (either > in /etc/nfsmount.conf or on the command line) restricts the mount to using > IPv4, not IPv6. > For IPv6 you need "udp6". > > This isn't made crystal clear by the documentation. I could fix the > documentation, but first I wanted to check if this really is appropriate. > Is there a good reason for this, or should we make "udp" mean "udp4 or udp6" > and require either "udp4" or "udp6" if we want a particular IP version. > > i.e. instead of treating the "proto=" value as a "netid", should we treat it > as a "protoname" and match any "netid" in /etc/netconfig with that > "protoname"?? This is working as designed. The meaning of each netid is defined in RFC 5665. "udp" means UDP over IPv4. This matches precisely what "proto=udp" meant before TI-RPC. These netids force a particular protocol family when the server is specified by hostname and not IP address. What's more, we mean this to match the behavior of the Solaris mount command, where "proto=udp" also has this meaning. Which part of the documentation do you think is unclear? -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
