From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] New wireless adapter breaks nfs exports
Date: Sat, 04 Oct 2014 11:52:02 -0700 [thread overview]
Message-ID: <m0pfkj$tvn$1@ger.gmane.org> (raw)
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.
Any other ideas would be most welcome too.
Thanks.
next reply other threads:[~2014-10-04 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 18:52 walt [this message]
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
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='m0pfkj$tvn$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