From owner-freebsd-questions@FreeBSD.ORG Sat Sep 25 08:30:47 2010 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2065A1065674 for ; Sat, 25 Sep 2010 08:30:47 +0000 (UTC) (envelope-from mike.w.meyer@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CE47D8FC1A for ; Sat, 25 Sep 2010 08:30:46 +0000 (UTC) Received: by iwn34 with SMTP id 34so3845175iwn.13 for ; Sat, 25 Sep 2010 01:30:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:organization:x-mailer:face:mime-version:content-type :content-transfer-encoding; bh=g6Fu6LTphE+0WLSMxS3gW2yHXSHGmrraIxczXDZ4vkk=; b=qDY1QVOh+LSs7o1AzJz4TWdMAAxpt86/XG0yOBbaYvbSIDMSGWc2IfaoPGKvZhxN+7 w6ttvR2LtmtieWemYiWGNqDqzIL5V/C/2JihjAGFVbrolm/kGwxI8ShDrjfV9y4ksBQz LgrZytI4CmIhz5i59yVJC29M15ga9xKMz8Bes= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:organization:x-mailer:face :mime-version:content-type:content-transfer-encoding; b=SPGnREkCZ0+mXiyip/dyct6mT+FA3XMjYLS0HJVizlthE2XteWGqTVR9VIxB2hZq0v X5yv/F+Jhu+p3OjkyCudA44oiOnyGT7jY2uNDd+oXcBtoH5LIQVhECWcIqBVLPxucbcs b8apDHU08Tt30Sp5k4PzPTHgA8YKSdj6fQ9BY= Received: by 10.231.31.1 with SMTP id w1mr4830723ibc.162.1285401684751; Sat, 25 Sep 2010 01:01:24 -0700 (PDT) Received: from bhuda.mired.org ([74.143.213.42]) by mx.google.com with ESMTPS id i6sm3332976iba.8.2010.09.25.01.01.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 25 Sep 2010 01:01:24 -0700 (PDT) Date: Sat, 25 Sep 2010 04:01:18 -0400 From: Mike Meyer To: questions@freebsd.org Message-ID: <20100925040118.7a020607@bhuda.mired.org> Organization: Meyer Consulting X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Problems mounting nfs from freebsd to Mac. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2010 08:30:47 -0000 I've got an nfs server that's refusing to mount one client - via one route - and it's driving me crazy. The server is running 8.1-RELEASE, exporting a collection of zfs file systems. All the file systems are exported with the exact same flags. The clients are either FreeBSD or OSX boxes. Most of them work fine. One OSX box - updated to the latest snow leopard while trying to fix this - gets "permission denied" when it tries to mount the interesting fie systems. But only when using it's wired connection. If it connects via wifi to the same router (a cisco WRT610N running dd-wrt) everything works fine. As far as I know, there are only three reasons for an NFS server to refuse a mount request: 1) The exports file is borked somehow, 2) The server insists that the client use a privileged port, or 3) The IP address the request is coming from is disallowed. #1 isn't it - the file systems mount fine on other boxes. And they mount fine on the problem box via Wifi. #2 shouldn't be it - I'm running the server with -n turned on, and the mount works via wifi. #3 seems logical, but I only have one network enabled, and it's a *.0/25. The working addresses include .96, and .106, while the failing address is .105. So I'm not sure what's going on here. Running mountd with a -d flag generates no output at all when the request is denied. This makes me think I'm not looking in the right place. Relevant entries from rc.conf (nothing really fancy): nfs_server_enable="yes" nfs_server_flags="-u -t -n 4 -h $MY_IP" mountd_enable="yes" mountd_flags="-r -n -h $MY_IP" rpcbind_enable="YES" rpcbind_flags="-h $MY_IP" rpc_lockd_enable="YES" rpc_lockd_flags="-h $MY_IP" rpc_statd_enable="YES" rpc_statd_flags="-h $MY_IP" So, questions: if mountd isn't the issue (though it's issuing the denied messages), what is? Is there some reason I've overlooked for the permissions to be denied? Anything I can do to get more information out of mountd (or whatever is causing the problem)? Any other things I might try? Thanks, http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org -- Mike Meyer http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org