Bug#737679: autofs does not appear to support IPv6 hostname lookups for NFS mounts

[Kevin Otte]

Now that this bug has a patch, is there any chance we can get it pushed
in time for the next Ubuntu LTS release? It would be a shame to go
another two years without this fix.

Bug#737679: autofs does not appear to support IPv6 hostname lookups for NFS mounts

[Stefan Potyra]

Package: autofs
Followup-For: Bug #737679

Hi,

thanks for maintaining autofs.

Attached is a debdiff that fixes the bug for me.
Great thanks for everyone who previously commented on the BR and pointed out the
solution.

Cheers,
  Stefan.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages autofs depends on:
ii  init-system-helpers  1.49
ii  libc62.24-14
ii  libtirpc10.2.5-1.2
ii  libxml2  2.9.4+dfsg1-3
ii  ucf  3.0036

Versions of packages autofs recommends:
ii  kmod24-1
ii  nfs-common  1:1.3.4-2.1

autofs suggests no packages.

-- no debconf information
diff -Nru autofs-5.1.2/debian/changelog autofs-5.1.2/debian/changelog
--- autofs-5.1.2/debian/changelog   2016-12-23 00:34:46.0 +0100
+++ autofs-5.1.2/debian/changelog   2017-08-03 20:01:39.0 +0200
@@ -1,3 +1,12 @@
+autofs (5.1.2-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control: Add libtirpc-dev to build-depends.
+  * debian/rules: Add option --with-libtirpc to configure
+(Closes: #737679)
+
+ -- Stefan Potyra   Thu, 03 Aug 2017 20:01:39 +0200
+
 autofs (5.1.2-1) unstable; urgency=medium
 
   * New upstream release [June 2016] (Closes: #846054).
diff -Nru autofs-5.1.2/debian/control autofs-5.1.2/debian/control
--- autofs-5.1.2/debian/control 2016-12-23 00:30:11.0 +0100
+++ autofs-5.1.2/debian/control 2017-08-03 20:01:07.0 +0200
@@ -14,7 +14,8 @@
  libsasl2-dev,
  libssl-dev,
  libxml2-dev,
- sssd-common
+ sssd-common,
+ libtirpc-dev
 Homepage: http://www.kernel.org/pub/linux/daemons/autofs/v5/
 VCS-Browser: https://anonscm.debian.org/cgit/collab-maint/autofs.git
 VCS-Git: https://anonscm.debian.org/git/collab-maint/autofs.git
diff -Nru autofs-5.1.2/debian/rules autofs-5.1.2/debian/rules
--- autofs-5.1.2/debian/rules   2016-12-22 23:53:33.0 +0100
+++ autofs-5.1.2/debian/rules   2017-08-03 20:01:37.0 +0200
@@ -33,7 +33,8 @@
--with-fifodir=/var/run --with-flagdir=/var/run \
--with-hesiod \
--with-openldap \
-   --with-sasl
+   --with-sasl \
+   --with-libtirpc
 # Always define HAVE_SLOPPY_MOUNT (mount -s).  Also a hack and
 # the same comment as above applies: upstream should use it unconditionally.
 # Even busybox mount understands -s.

Bug#737679: autofs does not appear to support IPv6 hostname lookups for NFS mounts

[Arne Nordmark]

For the record: Version 5.1.2-1 (currently in stretch), still shows this 
problem, and building --with-libtirpc still resolves the problem.


Are there any known downsides to using libtirpc?

Arne

Bug#737679: autofs does not appear to support IPv6 hostname lookups for NFS mounts

[Russell Phillips]

On Sat, 24 Oct 2015 16:48:37 -0400 Kevin Otte  wrote:
> I just encountered this on an Ubuntu 15.04 machine running autofs
> 5.0.8-1ubuntu3.2. Since Debian is upstream and this bug is still open, I
> figured I'd mention it here.
>
> My workaround has been to use Samba since it has UNIX extensions, which
> is less than optimal with all its forays into userspace, but at least it
> supports IPv6.
>
>
>

I also encountered this on ubuntu 16.04. I installed autofs from this 
PPA, which is built with libtirpc:


https://blueprints.launchpad.net/~raven-au/+archive/ubuntu/autofs-ppa

Everything worked after that.

This Ubuntu ticket appears to be the same problem. The symptoms are 
slightly different, but the scenario looks the same and proposed patch 
enables libtirpc.


https://bugs.launchpad.net/linuxmint/+bug/1101779

Bug#737679: autofs does not appear to support IPv6 hostname lookups for NFS mounts

[Kevin Otte]

I just encountered this on an Ubuntu 15.04 machine running autofs
5.0.8-1ubuntu3.2. Since Debian is upstream and this bug is still open, I
figured I'd mention it here.

My workaround has been to use Samba since it has UNIX extensions, which
is less than optimal with all its forays into userspace, but at least it
supports IPv6.

Bug#737679: autofs does not appear to support IPv6 hostname lookups for NFS mounts

[Roger Leigh]

Package: autofs
Version: 5.0.7-3
Severity: important
Tags: ipv6

Current setup:

% host amys.codelibre.net
amys.codelibre.net has IPv6 address 2001:8b0:860:ddbd:3aea:a7ff:feab:6153
% cat /etc/auto.nfs 
amys -fstype=nfs4 amys.codelibre.net:/
% cat /etc/auto.master 
/nfs /etc/auto.nfs
% ls /nfs/amys/
ls: reading directory /nfs/amys/: Input/output error

Feb  4 21:48:59 ravenclaw automount[5931]: handle_packet: type = 3
Feb  4 21:48:59 ravenclaw automount[5931]: handle_packet_missing_indirect: 
token 13, name amys, request pid 5967
Feb  4 21:48:59 ravenclaw automount[5931]: attempting to mount entry /nfs/amys
Feb  4 21:48:59 ravenclaw automount[5931]: lookup_mount: lookup(file): looking 
up amys
Feb  4 21:48:59 ravenclaw automount[5931]: lookup_mount: lookup(file): amys - 
-fstype=nfs4,rw,hard,intr amys.codelibre.net:/
Feb  4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun): expanded 
entry: -fstype=nfs4,rw,hard,intr amys.codelibre.net:/
Feb  4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun): gathered 
options: fstype=nfs4,rw,hard,intr
Feb  4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun): 
dequote(amys.codelibre.net:/) - amys.codelibre.net:/
Feb  4 21:48:59 ravenclaw automount[5931]: parse_mount: parse(sun): core of 
entry: options=fstype=nfs4,rw,hard,intr, loc=amys.codelibre.net:/
Feb  4 21:48:59 ravenclaw automount[5931]: sun_mount: parse(sun): mounting root 
/nfs, mountpoint amys, what amys.codelibre.net:/, fstype nfs4, options 
rw,hard,intr
Feb  4 21:48:59 ravenclaw automount[5931]: mount_mount: mount(nfs): root=/nfs 
name=amys what=amys.codelibre.net:/, fstype=nfs4, options=rw,hard,intr
Feb  4 21:48:59 ravenclaw automount[5931]: mount_mount: mount(nfs): nfs 
options=rw,hard,intr, nobind=0, nosymlink=0, ro=0
Feb  4 21:49:00 ravenclaw automount[5931]: mount(nfs): no hosts available
Feb  4 21:49:00 ravenclaw automount[5931]: dev_ioctl_send_fail: token = 13
Feb  4 21:49:00 ravenclaw automount[5931]: failed to mount /nfs/amys

The NFS setup does work mounting by hand, so the server and client /can/ work.
In this example, the server is FreeBSD 10.0-RELEASE exporting a set of ZFS
datasets.

# mount -t nfs4 amys.codelibre.net:/home /home
findmnt -lu | grep /home
/homeamys.codelibre.net:/homenfs4   
 
rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=2001:8b0:860:ddbd:62a4:4cff:fe5f:1257,local_lock=none,addr=2001:8b0:860:ddbd:3aea:a7ff:feab:6153
/home/rleigh amys.codelibre.net:/home/rleigh nfs4   
 
rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=2001:8b0:860:ddbd:62a4:4cff:fe5f:1257,local_lock=none,addr=2001:8b0:860:ddbd:3aea:a7ff:feab:6153

If I change the /etc/auto.nfs map to:

amys -fstype=nfs4 amys.lan:/

then the mount /does/ work.  This is because it's using the IPv4
DHCP name and address.  It doesn't work fully (the mount is
exported to a restricted set of IPv6 hosts only), intentionally,
but autofs does its part of the job correctly despite this.


It looks like this is down to autofs not handling names using only
IPv6 addresses.  Not sure why this happens given that I would have
expected it to just pass this directly to mount(8) but it's
presumably doing more than that.  Not sure exactly what the cause
is, though /usr/lib/x86_64-linux-gnu/autofs/mount_nfs.so is using
getaddrinfo and I can't see any obvious defect with a quick glance
over the sources.


Regards,
Roger

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (550, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages autofs depends on:
ii  libc6  2.17-97
ii  libxml22.9.1+dfsg1-3
ii  multiarch-support  2.17-97
ii  ucf3.0027+nmu1

Versions of packages autofs recommends:
ii  kmod   16-2
ii  module-init-tools  16-2
ii  nfs-common 1:1.2.8-5

autofs suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org