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 1689F138247 for ; Wed, 8 Oct 2014 04:51:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0667AE0B39; Wed, 8 Oct 2014 04:51:07 +0000 (UTC) Received: from smtpq6.tb.mail.iss.as9143.net (smtpq6.tb.mail.iss.as9143.net [212.54.42.169]) by pigeon.gentoo.org (Postfix) with ESMTP id C6260E0B2D for ; Wed, 8 Oct 2014 04:51:05 +0000 (UTC) Received: from [212.54.42.135] (helo=smtp4.tb.mail.iss.as9143.net) by smtpq6.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1XbjDM-0001tm-Se for gentoo-user@lists.gentoo.org; Wed, 08 Oct 2014 06:51:04 +0200 Received: from 53579160.cm-6-8c.dynamic.ziggo.nl ([83.87.145.96] helo=data.antarean.org) by smtp4.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1XbjDM-0005T3-4D for gentoo-user@lists.gentoo.org; Wed, 08 Oct 2014 06:51:04 +0200 Received: from andromeda.localnet (unknown [10.20.13.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id A60884B for ; Wed, 8 Oct 2014 06:50:56 +0200 (CEST) From: "J. Roeleveld" 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 Message-ID: <1641250.DplACruIhQ@andromeda> Organization: Antarean User-Agent: KMail/4.12.5 (Linux/3.14.14-gentoo; KDE/4.12.5; x86_64; ; ) In-Reply-To: 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: multipart/alternative; boundary="nextPart2613692.OzAaR94gYt" Content-Transfer-Encoding: 7Bit X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.9 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9,HTML_MESSAGE=0.001,PROLO_TRUST_RDNS=-3,RDNS_DYNAMIC=0.982 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: 96f526a1-cf48-4df6-b05b-d48ad1dde56f X-Archives-Hash: 5734d7e4a42c3ad9020d5d0a4e70c083 This is a multi-part message in MIME format. --nextPart2613692.OzAaR94gYt Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 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 gw -- Joost --nextPart2613692.OzAaR94gYt Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii"

 

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

 

--nextPart2613692.OzAaR94gYt--