linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: NFS <linux-nfs@vger.kernel.org>
Subject: Should "mount -o proto=udp" be usable against an IPv6 only server?
Date: Tue, 18 Sep 2012 11:54:50 +1000	[thread overview]
Message-ID: <20120918115450.5c65973f@notabene.brown> (raw)

[-- Attachment #1: Type: text/plain, Size: 667 bytes --]



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"??

Thanks,
NeilBrown 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

             reply	other threads:[~2012-09-18  1:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  1:54 NeilBrown [this message]
2012-09-18  5:28 ` Should "mount -o proto=udp" be usable against an IPv6 only server? Chuck Lever
2012-09-18  6:29   ` NeilBrown
2012-09-18 15:31     ` Chuck Lever
2012-09-18 23:19       ` NeilBrown
2012-09-19  1:00         ` Chuck Lever
2012-10-02  5:24           ` NeilBrown
2012-10-02 14:24             ` Chuck Lever
2012-10-03  3:11               ` NeilBrown
  -- strict thread matches above, loose matches on Subject: below --
2012-10-04  4:15 Chuck Lever
2012-10-08  3:35 ` NeilBrown
2012-10-08 15:51   ` Chuck Lever
2012-10-08 23:48     ` NeilBrown
2012-10-09 15:01       ` Chuck Lever
2012-10-11  0:01         ` NeilBrown
2012-10-15 17:13         ` Steve Dickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120918115450.5c65973f@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).