Re: [PATCH 0/2] command line IPv6 support for exportfs

[Steve Dickson <SteveD@redhat.com>]

On 03/12/2014 01:47 PM, Chuck Lever wrote:
> Though /etc/exports can contain IPv6 literals as client names, the
> exportfs command doesn't allow an IPv6 literal when adding or
> removing a temporary export.
> 
>   exportfs [-u] client:/path
> 
> If "client" is an IPv6 presentation address, it contains colons.
> The problem is that exportfs already uses a colon to separate the
> client identifier from the export pathname.
> 
> To escape colons in the client name, adopt the same mechanism that
> is used for mount.nfs.  Users wrap IPv6 literals in square brackets.
> 
> exportfs has to be a little more complicated than mount.nfs,
> however.  It must still be able to distinguish hostname wildcards
> that use brackets, and be able to deal with network address
> prefixes.
> 
> With this patch series,
> 
>   [abc]-machine.example.org:/export
> 
>   192.168.76.16:/share
> 
>   [2604:8800:100:81fc:82ee:73ff:fe43:d64f]:/export/home
> 
>   [fe80::]/64:/var/tmp
> 
> are now all accepted by exportfs.
> 
> ---
> 
> Chuck Lever (2):
>       exportfs: Refactor exportfs() and unexportfs()
>       exportfs: Support raw IPv6 addresses with "client:/path"
Both were committed...

steved.

> 
> 
>  utils/exportfs/exportfs.c   |  134 ++++++++++++++++++++++++++++++++++++-------
>  utils/exportfs/exportfs.man |   16 +++++
>  2 files changed, 127 insertions(+), 23 deletions(-)
>