public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: New wireless adapter breaks nfs exports
Date: Thu, 16 Oct 2014 16:23:10 -0700	[thread overview]
Message-ID: <m1pk0v$am2$1@ger.gmane.org> (raw)
In-Reply-To: <CAOdo=Szm0Accf1fKFT8JJ9Mn+DQ=h8d9B=pteOk+g7NWiSCvLg@mail.gmail.com>

On 10/15/2014 12:57 PM, Tom H wrote:
> On Tue, Oct 7, 2014 at 7:39 PM, walt <w41ter@gmail.com> wrote:
>> On 10/05/2014 08:31 PM, Tom H wrote:
>>> On Sat, Oct 4, 2014 at 2:52 PM, walt <w41ter@gmail.com> 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.




      reply	other threads:[~2014-10-16 23:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04 18:52 [gentoo-user] New wireless adapter breaks nfs exports walt
2014-10-05 22:53 ` [gentoo-user] Re: New wireless adapter breaks nfs exports [SOLVED] walt
2014-10-06  3:31 ` [gentoo-user] New wireless adapter breaks nfs exports Tom H
2014-10-07 23:39   ` [gentoo-user] " walt
2014-10-08  4:51     ` J. Roeleveld
2014-10-08  6:16     ` Alan McKinnon
2014-10-15 19:57     ` Tom H
2014-10-16 23:23       ` walt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='m1pk0v$am2$1@ger.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox