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