From owner-freebsd-fs@FreeBSD.ORG Thu Oct 21 21:40:10 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDCBD106566C for ; Thu, 21 Oct 2010 21:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A1DBB8FC14 for ; Thu, 21 Oct 2010 21:40:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9LLeAtc063746 for ; Thu, 21 Oct 2010 21:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9LLeA72063745; Thu, 21 Oct 2010 21:40:10 GMT (envelope-from gnats) Date: Thu, 21 Oct 2010 21:40:10 GMT Message-Id: <201010212140.o9LLeA72063745@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Richard Conto Cc: Subject: Re: kern/147881: [zfs] [patch] ZFS "sharenfs" doesn't allow different "exports" options for different hosts X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Richard Conto List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 21:40:10 -0000 The following reply was made to PR kern/147881; it has been noted by GNATS. From: Richard Conto To: Martin Birgmeier Cc: bug-followup@FreeBSD.org, Richard Conto Subject: Re: kern/147881: [zfs] [patch] ZFS "sharenfs" doesn't allow different "exports" options for different hosts Date: Thu, 21 Oct 2010 17:10:19 -0400 My patch is IPv4/IPv6/DNS agnostic - it ought to work either way. NFSv4 = might be a problem due to the syntax differences in /etc/exports = (/etc/zfs/exports). All my patch does is use ';' as a special character to allow multiple = values (like you want) for each export. Each value is prefixed by the = mount point and written to /etc/zfs/exports. I'm still running it - but it's for a home file server where I want to = restrict "root" access from certain VPNs. Given that all it does is = change the output to /etc/zfs/exports, which is handled by the regular = NFS export mechanism, I don't think that there should be any significant = difference between home and production/enterprise use - unless NFS = exports keel over when there's hundreds of mount points (easy to do with = ZFS) rather than tens. My home set up is exporting only 25 mount = points. --- Richard On Oct 15, 2010, at 3:15 AM, Martin Birgmeier wrote: > Please implement this or a similar patch. I need this in my dual = IPv4/IPv6 setup, where it is necessary to have something like >=20 > /tank/vol -network 192.168.0.0 -mask 255.255.0.0 > /tank/vol -network fec0:0:0:1::/56 >=20 > in /etc/zfs/exports in order to get both IPv4 and IPv6 clients to = work. >=20 > Regards, >=20 > Martin