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 57D9F1387CA for ; Wed, 15 Oct 2014 19:58:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AAE80E098A; Wed, 15 Oct 2014 19:57:56 +0000 (UTC) Received: from mail-la0-f65.google.com (mail-la0-f65.google.com [209.85.215.65]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 41E59E0871 for ; Wed, 15 Oct 2014 19:57:54 +0000 (UTC) Received: by mail-la0-f65.google.com with SMTP id gm9so448532lab.8 for ; Wed, 15 Oct 2014 12:57:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=wn4Q0hW6LNxyoS3PRc5DCliJI89HX15Ty0RgTfeStSs=; b=0QoMtGoe4Se7PN6QFFl/0vI3k6UXAUdR7/8NOpYXLZFrD4fZUA2rw0WeycOJfR5JXF EfTtZClYbaYBQoYLOgIqhEdi2cPHJ0ZVai5RUKcCDAunKUhIB38ua03YpPPn5ENqsFk9 Bo/MjFkNU0QQA2MsAUQh6xYxcx4N0jMYc/Fr9ktduUl7QYyQ0TF6FsLmuLqyMr5zSk3o vSszujTv2GiQv9jc3LKDfwMVyrF3x4rkVReSSVdcdU992y9O/nfQxR6MPu9nVqBv+jOO TTOAeDGQpkrUs1n2qx28ffYIfTw77dNTSNR8wNl0MqA1IzGVW46rA+svdH/+xIohWKio QxVw== 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 X-Received: by 10.112.144.228 with SMTP id sp4mr14475644lbb.58.1413403073633; Wed, 15 Oct 2014 12:57:53 -0700 (PDT) Received: by 10.152.22.168 with HTTP; Wed, 15 Oct 2014 12:57:53 -0700 (PDT) In-Reply-To: References: Date: Wed, 15 Oct 2014 15:57:53 -0400 Message-ID: Subject: Re: [gentoo-user] Re: New wireless adapter breaks nfs exports From: Tom H To: Gentoo User Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 50228c7b-9f7c-4602-a9bd-f1202aca3483 X-Archives-Hash: 16ea081e76d47006936ac0be5f4cd40e 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.