public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: New wireless adapter breaks nfs exports
Date: Wed, 08 Oct 2014 06:51:14 +0200	[thread overview]
Message-ID: <1641250.DplACruIhQ@andromeda> (raw)
In-Reply-To: <m11tjm$lf0$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]


On Tuesday, October 07, 2014 04:39:32 PM 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.
> 
> Thanks.

I did have it working with my old laptop, but NFS isn't so happy with 
suddenly disappearing network connections.
I ended up using Samba and CIFS to access network shares.

Do you get the same behaviour when using a wired connection?

Also, something I found out when I tried to configure a network printer 
once, some badly designed wireless routers (The el-cheapo consumer 
ones) forget to bridge the LAN and WIFI portions of the network.
Try adding a route to the NFS-server via the IP of the router. That might 
also do the trick.

# route add <NFS-ip> gw <router-ip>

--
Joost


[-- Attachment #2: Type: text/html, Size: 9569 bytes --]

  reply	other threads:[~2014-10-08  4:51 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 [this message]
2014-10-08  6:16     ` Alan McKinnon
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=1641250.DplACruIhQ@andromeda \
    --to=joost@antarean.org \
    --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