From Fedora Project Wiki
(Created page with 'IPv6 Testing on NFS should be similar to IPv4 NFS, and when specifying ipv6 address, it needs to be enclosed in square brackets. Link-local and site-local IPv6 addresses must b...') |
No edit summary |
||
(7 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
IPv6 Testing on NFS should be similar to IPv4 NFS, and when specifying ipv6 address, it needs to be enclosed in square brackets. Link-local and site-local IPv6 addresses must be accompanied by an interface identifier. | {{QA/Test_Case | ||
|description=IPv6 Testing on NFS should be similar to IPv4 NFS, and when specifying ipv6 address, it needs to be enclosed in square brackets. Link-local and site-local IPv6 addresses must be accompanied by an interface identifier. See the <code>nfs(5)</code> manpage for details: | |||
|setup= | |||
# Prepare an NFS server that is accessible via IPv6 networking | |||
# On the NFS server, setup a mount point in the file {{filename|/etc/exports}} | |||
|actions= | |||
<ol> | |||
<li>First, attempt to mount an IPv6-based NFS mount using the {{command|mount}} command. The example below demonstrates mounting a share called {{filename|/export}} hosted by the NFS server accessible by it's IPv6 address <code>[2001:470:8:c53:20e:cff:fec6::1]</code>: | |||
<pre> | |||
# mount -t nfs '[2001:470:8:c53:20e:cff:fec6::1]:/export' /mnt/foo | |||
</pre> | |||
{{admon/tip|Note|If putting the IPv6 address in brackets does not work, try without brackets.}} | |||
<li>Next, update {{filename|/etc/fstab}} and specify an IPv6 NFS server and mount point. An example is included below for reference: | |||
<pre> | |||
[2001:470:8:c53:20e:cff::1]:/export /mnt nfs defaults 0 0 | |||
</pre> | |||
<li>Using the example above, attempt to mount the IPv6 NFS mount point with the {{command|mount}} command. | |||
<pre> | |||
# mount /mnt | |||
</pre> | |||
<li> Repeat the previous step, but this time modify the file {{filename|/etc/exports}} on the NFS server to restrict access by subnet. The following example shows restricting access by subnet for both IPv4 and IPv6 addresses. | |||
<pre> | |||
/home 192.168.10.0/24(rw,insecure) 2001:470:8:c53::/64(rw,insecure) | |||
</pre> | |||
</ol> | |||
|results= | |||
# Mounting an IPv6-based NFS mount using the {{command|mount}} command must work | |||
# Mounting an IPv6-based NFS mount using the {{command|mount}} command and {{filename|/etc/fstab}} must work | |||
# Mounting an IPv6-based NFS volume succeeds even when the server restricts access by subnet | |||
}} |
Latest revision as of 13:28, 21 June 2011
Description
IPv6 Testing on NFS should be similar to IPv4 NFS, and when specifying ipv6 address, it needs to be enclosed in square brackets. Link-local and site-local IPv6 addresses must be accompanied by an interface identifier. See the nfs(5)
manpage for details:
Setup
- Prepare an NFS server that is accessible via IPv6 networking
- On the NFS server, setup a mount point in the file
/etc/exports
How to test
- First, attempt to mount an IPv6-based NFS mount using the
mount
command. The example below demonstrates mounting a share called/export
hosted by the NFS server accessible by it's IPv6 address[2001:470:8:c53:20e:cff:fec6::1]
:# mount -t nfs '[2001:470:8:c53:20e:cff:fec6::1]:/export' /mnt/foo
- Next, update
/etc/fstab
and specify an IPv6 NFS server and mount point. An example is included below for reference:[2001:470:8:c53:20e:cff::1]:/export /mnt nfs defaults 0 0
- Using the example above, attempt to mount the IPv6 NFS mount point with the
mount
command.# mount /mnt
- Repeat the previous step, but this time modify the file
/etc/exports
on the NFS server to restrict access by subnet. The following example shows restricting access by subnet for both IPv4 and IPv6 addresses./home 192.168.10.0/24(rw,insecure) 2001:470:8:c53::/64(rw,insecure)
Expected Results
- Mounting an IPv6-based NFS mount using the
mount
command must work - Mounting an IPv6-based NFS mount using the
mount
command and/etc/fstab
must work - Mounting an IPv6-based NFS volume succeeds even when the server restricts access by subnet