public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: New wireless adapter breaks nfs exports
Date: Wed, 08 Oct 2014 08:16:21 +0200	[thread overview]
Message-ID: <5434D6B5.8050905@gmail.com> (raw)
In-Reply-To: <m11tjm$lf0$1@ger.gmane.org>

On 08/10/2014 01:39, walt 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.


nfs3 over wifi works just fine for me, I use it all the time at home.
Setting it up was no different to setting up a wired interface - set
exports on the server, mount from the client.

I suspect the problems you are having are unrelated to wifi as such and
are probably something more mundane. I take it you've checked all the
usual suspects such as your current IP is allowed to connect to the
server, there's no access rules blocking you and so on?




-- 
Alan McKinnon
alan.mckinnon@gmail.com



  parent reply	other threads:[~2014-10-08  6:16 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 [this message]
2014-10-15 19:57     ` Tom H
2014-10-16 23:23       ` walt

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=5434D6B5.8050905@gmail.com \
    --to=alan.mckinnon@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