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