sharenfs property with IPv6 does not work

[dacianstremtan]

System information

Type	Version/Name
Distribution Name	Rocky Linux
Distribution Version	8.8 (Green Obsidian)
Kernel Version	4.18.0-477.13.1.el8_8.x86_64
Architecture	x86_64
OpenZFS Version	2.1.12

Describe the problem you're observing

I cannot set zfs sharenfs to IPv6. There was a pull request in 2021 (#11939), that made it to the master branch, but the code is not making into in the releases.

Describe how to reproduce the problem

zfs set sharenfs='rw=10.0.0.0/24,rw=[fc00:10:10::]/64,sync,no_root_squash,no_wdelay' tank/shares

Instead of creating an export point for IPv6 address I get the following exports:

[stremtan@zfsnas-node1 ~]$ sudo zfs set sharenfs='rw=10.0.0.0/24,rw=[fc00:10:10::]/64,sync,no_root_squash,no_wdelay' tank/shares
[stremtan@zfsnas-node1 ~]$ sudo exportfs
/tank/shares  	10
/tank/shares  	10.0.0.0/24
/tank/shares  	[fc00
/tank/shares  	<world>

Include any warning/errors/backtraces from the system logs

none

[dacianstremtan]

The same result happens when I use the @ in front of the network addresses:

[stremtan@zfsnas-node1 linux]$ sudo zfs set sharenfs='rw=@10.0.0.0/24,rw=@[fc00:10:10::]/64,sync,no_root_squash,no_wdelay' tank/shares
[stremtan@zfsnas-node1 linux]$ sudo exportfs 
/tank/shares  	10
/tank/shares  	10.0.0.0/24
/tank/shares  	[fc00
/tank/shares  	<world>

[mcilloni]

Can confirm, IPv6 exports are still broken as of 2.1.12 despite the PR and relative issues having being marked as solved since 2021. IMHO it's unacceptable that in the year 2023 IPv6 exports are this broken - IPv6 addresses should either be rejected or properly supported, polluting the NFS export list with random garbage is very bad IMHO.

[markusnasholm]

Can confirm this as well. I stumbled across this while updating an Debian file server. After reboot IPv6 NFS shares no longer work. It was not even a major update. Worked fine before. So to make sure it was not just an old broken version I had to try it on Debian 12 with zfs-2.1.11. Same issue.

Even tried it on Arch running bleeding edge, where I had the same issue until I finally got a working export file by adding brackets to the IPv6 address.

I agree completely with mcilloni. This is completely unbelievable. The fact that something like this has gotten into the master branch and releases without being caught in testing, and then ignored for YEARS is inexcusable.