Bug#433881: Regression: no longer handles port and mountport
Package: nfs-common Version: 1:1.1.0-6 Severity: normal In /etc/fstab, I use this line to mount an NFS drive behind a firewall that forwards ports with iptables: system:/esb /mnt/esb1 nfs noauto,user,exec,rw,rsize=16k,wsize=16k,hard,intr,port=4000,mountport=5000 0 0 Version 1:1.1.0-5 works and versions 1:1.1.0-6 through 11 all fail. Though I'm concerned that downgrading after all the changes in 1:1.1.0-10 could create further errors, downgrading to 1:1.1.0-5 appears to be unproblematic and restores the functionality. I was still tempted to label the bug important, as it breaks important core functionality. Nice work on the package by the way; it's a complicated transition. This looks like an upstream bug. Cheers, Dave -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.1 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.100 Add and remove users and groups ii libc62.6-2 GNU C Library: Shared libraries ii libcomer 1.39+1.40-WIP-2006.11.14+dfsg-1 common error description library ii libevent 1.3b-0 An asynchronous event notification ii libgssap 0.10-4 A mechanism-switch gssapi library ii libkrb53 1.6.dfsg.1-4MIT Kerberos runtime libraries ii libnfsid 0.18-0 An nfs idmapping library ii librpcse 0.14-2 allows secure rpc communication us ii libwrap0 7.6.dbs-11 Wietse Venema's TCP wrappers libra ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip ii netbase 4.28Basic TCP/IP networking system ii portmap 5-24The RPC portmapper ii ucf 2.0021 Update Configuration File: preserv nfs-common recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#433881: Regression: no longer handles port and mountport
On Thu, Jul 19, 2007 at 07:53:25PM -0700, David Liontooth wrote: > In /etc/fstab, I use this line to mount an NFS drive behind a firewall that > forwards ports with iptables: > > system:/esb /mnt/esb1 nfs > noauto,user,exec,rw,rsize=16k,wsize=16k,hard,intr,port=4000,mountport=5000 0 0 Could you try giving the "tcp" or "udp" flags as well as "nfsvers=3" or similar? It might be that it simply isn't reaching the portmapper. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#433881: Regression: no longer handles port and mountport
On Thu, Jul 19, 2007 at 07:53:25PM -0700, David Liontooth wrote: > In /etc/fstab, I use this line to mount an NFS drive behind a firewall that forwards ports with iptables: > > system:/esb /mnt/esb1 nfs noauto,user,exec,rw,rsize=16k,wsize=16k,hard,intr,port=4000,mountport=5000 0 0 Could you try giving the "tcp" or "udp" flags as well as "nfsvers=3" or similar? It might be that it simply isn't reaching the portmapper. Baseline: mount: mount to NFS server 'esb' failed: RPC Error: Success. nfsvers=3 makes no difference: mount: mount to NFS server 'esb' failed: RPC Error: Success. tcp fails in a new way: mount.nfs: Input/output error That failure is explained by the current iptables rule on the gateway, which only forwards udp for nfs: iptables -t nat -A PREROUTING -p udp -d 122.47.72.148 --dport 4000 -j DNAT --to 192.168.0.5:2049 upd: works! Please close -- but this should be documented (or the default changed to what used to be in effect before nfs-common 1.1.0-6). Tested and confirmed to work on 1.1.0-6, 1.1.0-10, and 1.1.0-11. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#433881: Regression: no longer handles port and mountport
On Fri, Jul 20, 2007 at 07:26:09AM -0700, David Liontooth wrote: > Please close -- but this should be documented (or the default changed to > what used to be in effect before nfs-common 1.1.0-6). Thanks, closing. BTW, it seems upstream thinks it is not a bug that there's no fallback to UDP, as it was never documented that there would be one. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
