From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 326F31387CA for ; Thu, 16 Oct 2014 23:23:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BC540E0852; Thu, 16 Oct 2014 23:23:38 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 86D6AE0838 for ; Thu, 16 Oct 2014 23:23:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 4FB863403BB for ; Thu, 16 Oct 2014 23:23:35 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: 0.601 X-Spam-Level: X-Spam-Status: No, score=0.601 tagged_above=-999 required=5.5 tests=[AWL=1.137, BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_NUMERIC_HELO=1.164, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FSL_HELO_BARE_IP_2=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdZsLQ7Zbv3P for ; Thu, 16 Oct 2014 23:23:29 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 9268233BF59 for ; Thu, 16 Oct 2014 23:23:29 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XeuOC-0004Ol-1G for gentoo-user@gentoo.org; Fri, 17 Oct 2014 01:23:24 +0200 Received: from 64.69.39.92 ([64.69.39.92]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Oct 2014 01:23:24 +0200 Received: from w41ter by 64.69.39.92 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 17 Oct 2014 01:23:24 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: walt Subject: [gentoo-user] Re: New wireless adapter breaks nfs exports Date: Thu, 16 Oct 2014 16:23:10 -0700 Message-ID: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 64.69.39.92 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 In-Reply-To: X-Archives-Salt: 7fca6767-a92f-4023-ac61-ad1934a8f052 X-Archives-Hash: c5fcddb8b909cfc650c6f58fb99b4f91 On 10/15/2014 12:57 PM, Tom H wrote: > On Tue, Oct 7, 2014 at 7:39 PM, walt wrote: >> On 10/05/2014 08:31 PM, Tom H wrote: >>> On Sat, Oct 4, 2014 at 2:52 PM, walt wrote: >>>> >>>> This machine (my nfsv3 file server) just got a new wireless adapter, which >>>> works fine for everything except serving files :( >>>> >>>> mount.nfs: requested NFS version or transport protocol is not supported >>>> >>>> google shows me lots about slow nfs connections over wireless but nothing >>>> about non-support. I'm using only nfs3 ATM because I've had so many problems >>>> with nfs4 in the past. I thought I'd ask here if nfs4 might fix the problem >>>> before changing everything. >>> >>> NFS works over wifi. >>> >>> Have you tried mounting with "-v" and/or "-o nfsvers=3"? >> >> Yes, about 30 seconds ago :) >> >> #mount -v -t nfs -o nfsvers=3 a6://usr/portage /mnt >> mount.nfs: timeout set for Tue Oct 7 16:35:39 2014 >> mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.75' >> mount.nfs: prog 100003, trying vers=3, prot=6 >> mount.nfs: trying 192.168.1.75 prog 100003 vers 3 prot TCP port 2049 >> mount.nfs: prog 100005, trying vers=3, prot=17 >> mount.nfs: trying 192.168.1.75 prog 100005 vers 3 prot UDP port 36168 >> mount.nfs: mount(2): Protocol not supported >> mount.nfs: Protocol not supported >> >> I have nfsv4 working correctly so the urgency is gone but I'm still >> curious if nfsv3 really should work over wifi as well as nfsv4. > > Both nfsv3 and nfsv4 work over wifi. > > Do both the client's and the server's kernels have nfsv3 enabled? > > From the output above I'd check the client's kernel config. The problem turned out to be incorrect nfs useflags, not kernel config, and nfsv3 is working now, thanks much.