Project

General

Profile

Actions

Bug #877

closed

share_nfs cannot share to IPv6 subnets

Added by River Tarnell about 12 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
nfs - NFS server and client
Start date:
2011-04-03
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
External Bug:

Description

It is currently impossible to export an NFS filesystem to an IPv6 network (rather than a single host), because share_nfs has no way to accept literal IPv6 addresses; instead ":" is used to separate hosts, e.g.: share_nfs -orw=host1:host2:host3

Sharing to a named network doesn't work either, because /etc/networks doesn't accept IPv6 network addresses.

The only workaround is to share to everyone, or individual named hosts (using DNS or /etc/hosts), which is particularly annoying in the face of IPv6 address autoconfig.

The fix is that share_nfs should accept the following notation:

# share_nfs -orw='[2a01:348:56::]/64' /some/fs

The [] notation is the standard way to "escape" IPv6 addresses in situations like this.


Related issues

Related to illumos gate - Bug #1592: NFS access checks shouldn't fail if client address can't be resolvedResolvedYuri Pankov2011-10-02

Actions
Actions #1

Updated by Vitaliy Gusev almost 12 years ago

  • Assignee set to Vitaliy Gusev
  • Difficulty set to Medium
  • Tags set to needs-triage
Actions #2

Updated by Yuri Pankov over 11 years ago

  • Assignee changed from Vitaliy Gusev to Yuri Pankov

Hi River, could you please try the following patch if you are still interested in this?
https://www.xvoid.org/illumos/webrev/cifs-nfs-ipv6-hostchecks/cifs-nfs-ipv6-hostchecks.patch

Actions #3

Updated by Rich Lowe over 11 years ago

  • Category changed from cmd - userland programs to nfs - NFS server and client
  • Status changed from New to Resolved
  • % Done changed from 0 to 100
  • Tags deleted (needs-triage)

Resolved in r13500 commit:f077aa5fa57c

Actions

Also available in: Atom PDF