7:27 a.m.
Hi everyone,
I’m trying to configure IPv6 client access in my NFS-Ganesha setup and was wondering if
wildcard or subnet-style entries are supported in the CLIENT section of the export
configuration.
for examle:
CLIENT {
Clients = fd00:*::;
Access_Type = RW;
}
Is this syntax valid for allowing all clients under the fd00 IPv6 range, similar to how
IPv4 wildcards like 192.168.*.0 work?
Or should IPv6 subnets only be specified using CIDR notation (e.g., fd00::/64)?
I verified it with vfs, but this was giving "Unexpected character" error.
Thanks in advance for any insights!
— Sagar
7:30 a.m.
Note: In title the example is mentioned as e.g., "fd00:*::/64", but it would be
e.g., "fd00:*::".
9:30 p.m.
New subject: Does NFS-Ganesha support IPv6 wildcards (e.g., fd00:*::/64) in CLIENT entries?
Hi Sagar,
On Fri, 10 Oct 2025 12:27:19 -0000, sagaragarwal1995(a)gmail.com wrote:
I’m trying to configure IPv6 client access in my NFS-Ganesha setup
and was wondering if wildcard or subnet-style entries are supported
in the CLIENT section of the export configuration.
for examle:
CLIENT {
Clients = fd00:*::;
Access_Type = RW;
}
Is this syntax valid for allowing all clients under the fd00 IPv6
range, similar to how IPv4 wildcards like 192.168.*.0 work? Or should
IPv6 subnets only be specified using CIDR notation (e.g., fd00::/64)?
I verified it with vfs, but this was giving "Unexpected
character" error.
The documentation says:
wildcarded If the string contains at least one ? or *
character (and is not simply "*"), the string is
used to pattern match host names. Note that [] may
also be used, but the pattern MUST have at least one
? or *
This means that wildcards (apart from "*" to match all clients) can
only be used when matching hostnames.
If wildcards currently work with IPv4 addresses then that would appear
to be accidental. It may depend on features of libcidr, which has
recently been removed from the the code to simplify things.
Both IPv4 and IPv6 subnets should be specified using CIDR notation.
peace & happiness,
martin
11:27 p.m.
We only support wildcards on hostname matches. Subnets are the way to handle wild cards on
IP addresses. We should now properly handle subnets on both IPv4 and IPv6 addresses. Note
also that hostname wildcards are expensive as it forces Ganesha to do reverse DNS to
translate an IP address into a hostname.
Frank
-----Original Message-----
From: sagaragarwal1995(a)gmail.com [mailto:sagaragarwal1995@gmail.com]
Sent: Friday, October 10, 2025 5:27 AM
To: devel(a)lists.nfs-ganesha.org
Subject: [NFS-Ganesha-Devel] Does NFS-Ganesha support IPv6 wildcards (e.g.,
fd00:*::/64) in CLIENT entries?
Hi everyone,
I’m trying to configure IPv6 client access in my NFS-Ganesha setup and was
wondering if wildcard or subnet-style entries are supported in the CLIENT
section of the export configuration.
for examle:
CLIENT {
Clients = fd00:*::;
Access_Type = RW;
}
Is this syntax valid for allowing all clients under the fd00 IPv6 range, similar to
how IPv4 wildcards like 192.168.*.0 work?
Or should IPv6 subnets only be specified using CIDR notation (e.g., fd00::/64)?
I verified it with vfs, but this was giving "Unexpected character" error.
Thanks in advance for any insights!
— Sagar
_______________________________________________
Devel mailing list -- devel(a)lists.nfs-ganesha.org To unsubscribe send an email to
devel-leave(a)lists.nfs-ganesha.org
18
days inactive
20
days old
3 comments
3 participants
participants (3)
-
Frank Filz -
Martin Schwenke -
sagaragarwal1995＠gmail.com