1 |
On Tue, Oct 7, 2014 at 7:39 PM, walt <w41ter@×××××.com> wrote: |
2 |
> On 10/05/2014 08:31 PM, Tom H wrote: |
3 |
>> On Sat, Oct 4, 2014 at 2:52 PM, walt <w41ter@×××××.com> wrote: |
4 |
>>> |
5 |
>>> This machine (my nfsv3 file server) just got a new wireless adapter, which |
6 |
>>> works fine for everything except serving files :( |
7 |
>>> |
8 |
>>> mount.nfs: requested NFS version or transport protocol is not supported |
9 |
>>> |
10 |
>>> google shows me lots about slow nfs connections over wireless but nothing |
11 |
>>> about non-support. I'm using only nfs3 ATM because I've had so many problems |
12 |
>>> with nfs4 in the past. I thought I'd ask here if nfs4 might fix the problem |
13 |
>>> before changing everything. |
14 |
>> |
15 |
>> NFS works over wifi. |
16 |
>> |
17 |
>> Have you tried mounting with "-v" and/or "-o nfsvers=3"? |
18 |
> |
19 |
> Yes, about 30 seconds ago :) |
20 |
> |
21 |
> #mount -v -t nfs -o nfsvers=3 a6://usr/portage /mnt |
22 |
> mount.nfs: timeout set for Tue Oct 7 16:35:39 2014 |
23 |
> mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.75' |
24 |
> mount.nfs: prog 100003, trying vers=3, prot=6 |
25 |
> mount.nfs: trying 192.168.1.75 prog 100003 vers 3 prot TCP port 2049 |
26 |
> mount.nfs: prog 100005, trying vers=3, prot=17 |
27 |
> mount.nfs: trying 192.168.1.75 prog 100005 vers 3 prot UDP port 36168 |
28 |
> mount.nfs: mount(2): Protocol not supported |
29 |
> mount.nfs: Protocol not supported |
30 |
> |
31 |
> I have nfsv4 working correctly so the urgency is gone but I'm still |
32 |
> curious if nfsv3 really should work over wifi as well as nfsv4. |
33 |
|
34 |
Both nfsv3 and nfsv4 work over wifi. |
35 |
|
36 |
Do both the client's and the server's kernels have nfsv3 enabled? |
37 |
|
38 |
From the output above I'd check the client's kernel config. |