[NFS] mount:RPC:Timed Out

[tophinus]

Hi everybody,

It's far from 2 months i try to set the nfs server working on my wl-500g deluxe (IP:192.168.0.2 and working in AP mode). But, each time i tried to mount it, I had this error :


mount: RPC: Timed Out

I have no firewall, I set the /etc/exports file as this (from the web) :


# automagically generated from web settings
/tmp/harddisk/home 192.168.0.4(rw)
/tmp/harddisk/home 192.168.0.3(rw)

I put lines in hosts.allow and hosts.deny and i try also with nothing in it. This is my files :


/etc/hosts.allow :
ALL:192.168.0.3
ALL:192.168.0.4

/etc/hosts.deny:
ALL:ALL


I'm using The 1.9.2.7-5a Oleg's Firmware.

The options I have tried are :


mount -t nfs 192.168.0.2:/tmp/harddisk/home /mnt/data -o nolock,noatime,wsize=8192,rsize=8192


Is someone manage to use the nfs server ? How did you use it ? What are your config files ?

Thank you for your help :)

Note : I search in the forum but i don't find an answer to my problem

[rolano]

..give this exports a try: /tmp/harddisk/ (rw,async,no_root_squash)

[tophinus]

I try but it still doesn't work. I always have the same error. Did you use hosts.allow and hosts.deny files ? And if so, what do you put in it ? Which command do you use to mount your nfs ?

I also tried this with your suggestion :


pcfixe:/home/toph# mount -t nfs 192.168.0.2:/tmp/harddisk/home /mnt/data -o rw,async,no_root_squash
unknown nfs mount option: no_root_squash


Thanks for you help :)

Note : I have 2 computers at home and the nfs server between us works properly.

[rolano]

Which command do you use to mount your nfs ?
Mountoptions:
mount - t nfs -o rw,soft,udp,nolock,noatime,async,rsize=32768,wsize =32768 192.168.0.10:/tmp/harddisk /mnt

exports (WL):
/tmp/harddisk/ (rw,async,no_root_squash)

[tophinus]

Argh, always the same error with both my computers (one wired, another wireless) :mad:

Did you launch special daemons on the computer which execute the mount command ??? (I'm under debian and the portmap and nfs-common daemons are running)

When I execute this command on my computer, I have this :


pcfixe:/home/toph# rpcinfo -p 192.168.0.2
program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 1024 nlockmgr
100021 3 udp 1024 nlockmgr
100021 4 udp 1024 nlockmgr
100005 1 udp 720 mountd
100005 1 tcp 723 mountd
100005 2 udp 720 mountd
100005 2 tcp 723 mountd
100005 3 udp 720 mountd
100005 3 tcp 723 mountd

Do you have another daemon on wl (its ip is 192.168.0.2 for me) that is running ?

Thank you again :)

[Oleg]

Do you've portmap running on your PC?

[tophinus]

Yes, I tried with only portmap running, portmap & nfs-common running on my PC but nothing works. I wonder why does it works from one PC to another and not from my wl to either one of my PCs.

[Oleg]

Perhaps your PCs use outdated software. You should have portmap running all the time.
Anyway, everything works fine for me with Fedora Core 3.

[tophinus]

I don't think my portmap version is outdated. I update my system every 3 days. My portmap version is 5-9.
I wonder if something is not missing with what I have done.
I set hostname
I put this line into /etc/exports : "/tmp/harddisk/ (rw,async,no_root_squash)" Then add, apply, and Finish. My usb disks is connected before the system reboot.
Then i try to mount it and I always grab the delay error.

Here is the "ps -A" result on my wl-deluxe :


PID Uid VmSize Stat Command
1 admin 560 S /sbin/init
2 admin SW [keventd]
3 admin SWN [ksoftirqd_CPU0]
4 admin SW [kswapd]
5 admin SW [bdflush]
6 admin SW [kupdated]
7 admin SW [mtdblockd]
77 admin 308 S telnetd
82 admin 436 S httpd
85 admin 384 S syslogd -m 0 -O /tmp/syslog.log -S -l 7
87 admin 340 S klogd
88 admin SW [khubd]
97 admin 276 S lpd
99 admin 260 S p9100d -f /dev/usb/lp0 0
102 admin 344 S waveservermain
104 admin 344 S rcamdmain
108 admin SW [usb-storage-0]
109 admin SW [scsi_eh_0]
115 1 376 S /usr/sbin/portmap
118 admin SW [nfsd]
120 admin SW [lockd]
121 admin SW [rpciod]
122 admin 576 S /usr/sbin/mountd
125 admin 316 S infosvr br0
126 admin 472 S watchdog
128 admin 336 S ntp
137 admin SW [kjournald]
139 admin 404 S stupid-ftpd
141 admin 520 S -sh
142 admin 384 R ps -A


Thank for your help Oleg :)

[Oleg]

wl500g works fine, the problem is your client for sure.
Do you've anything in the System Log on every connect attempt?

[tophinus]

I've searched in all my log files and found nothing.

I launch ethereal and see that a packet has a problem :


No. Time Source Destination Protocol Info
11 6.157022 192.168.0.3 192.168.0.2 MOUNT V3 MNT Call

Frame 11 (134 bytes on wire, 134 bytes captured)
Internet Protocol, Src Addr: 192.168.0.3 (192.168.0.3), Dst Addr: 192.168.0.2 (192.168.0.2)
User Datagram Protocol, Src Port: 1020 (1020), Dst Port: 720 (720)
Remote Procedure Call, Type:Call XID:0x145cc6f5
Mount Service

No. Time Source Destination Protocol Info
14 9.157802 192.168.0.3 192.168.0.2 MOUNT [RPC retransmission of #11]V3 MNT Call

No. Time Source Destination Protocol Info
15 12.161112 192.168.0.3 192.168.0.2 MOUNT [RPC retransmission of #11]V3 MNT Call

No. Time Source Destination Protocol Info
16 15.163642 192.168.0.3 192.168.0.2 MOUNT [RPC retransmission of #11]V3 MNT Call

And so on till number 19.

I have also this with ethereal after :


No. Time Source Destination Protocol Info
21 25.820777 192.168.0.3 192.168.0.2 ICMP Destination unreachable (Port unreachable)

So I test a ping on my wl (from the wired PC) and the results is no problem :


PING 192.168.0.2 (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=64 time=1.8 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.7 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.7 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.7 ms


Why does it works between my 2 PCs and not between WL and PC ??? This is the reason I think the problem doesn't come from my pc.

[tophinus]

Finally, after tries and tries and tries, I manage to mount it but it's fully unstable (and there is no information on /var/log/messages). Here is the trick i must use to enable the mount command not to be timed out :
1) First I telnet to the wl
2) Then I launch a "tcpdump" command and i must wait before there is a "non-stop infos" for the command. I want to say that i have to wait the wl send lines and lines and lines and lines that can't be read because this is very very very very too fast.
3) Then I launch a "mount -t nfs 192.168.0.2:/tmp/harddisk /mnt/data" and it's connected without waiting more than 1 second.

But there's still some problems. The mount command lives 5 minutes approximatively. And If I stop the tcpdump command, after 2 minutes, i can't mount the system (always timed out).
Also, if I try to mount the nfs with my other PC, I have now a timed out error on both my PCs. I must quit the telnet and relaunch a new one....

It's strange, very strange.

I found also with google some informations. To test the RPC connections, You must first launch a "rcpinfo -p ip_of_wl" from the PC.
So I have this as response :


program no_version protocole no_port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 1024 nlockmgr
100021 3 udp 1024 nlockmgr
100021 4 udp 1024 nlockmgr
100005 1 udp 720 mountd
100005 1 tcp 723 mountd
100005 2 udp 720 mountd
100005 2 tcp 723 mountd
100005 3 udp 720 mountd
100005 3 tcp 723 mountd

Now, you take the first number of a line (the program number) and you make a rpcinfo on it with the -t option for tcp protocol and -u option for udp protocol.


toph@pcfixe:~$ rpcinfo 192.168.0.2 -t 100000
program 100000 version 1 ready and waiting
program 100000 version 2 ready and waiting
program 100000 version 3 ready and waiting

But, when i tried the mountd program it works before attemting a mount command.... Else, i have a rpc timed out error (as always)

So, now, i can think easiely that the problem comes from the mountd program (because the another ones works perfectly).

Is there a way to debug it ??? Or to view what do not works ???

Note : I also tried with a knoppix and it still doesn't work too....

[tophinus]

I'm sure now that the problem doesn't come from my PCs.
I telnet to my wl (deluxe version, is that the problem ???)


[admin@asus root]$ insmod nfs
[admin@asus root]$ cat /etc/exports
/tmp/harddisk 192.168.0.3(rw,async,no_root_squash)
/tmp/harddisk 192.168.0.2(rw,async,no_root_squash)
/tmp/harddisk 127.0.0.1(rw,async,no_root_squash)
[admin@asus root]$ mount -t nfs 127.0.0.1:/tmp/harddisk/temp /tmp/harddisk/youpi2
mount: RPC: Timed out
mount: nfsmount failed: Bad file descriptor
mount: Mounting 127.0.0.1:/tmp/harddisk/temp on /tmp/harddisk/youpi2 failed: Invalid argument
[admin@asus root]$ mount -t nfs 127.0.0.1:/tmp/harddisk/temp /tmp/harddisk/youpi2
mount: RPC: Timed out
mount: nfsmount failed: Bad file descriptor
mount: Mounting 192.168.0.2:/tmp/harddisk/temp on /tmp/harddisk/youpi2 failed: Invalid argument


So, there is a problem with mountd or with the network kernel driver I think, or within both, i don't know.

Now, I need your suggestions to correct my problem PLEASE :( I really get mad with it .....

[tophinus]

I found the problem :
My wl was in "Access Point" mode. As I have a modem-router, I don't need other features from the wl expect the "Access Point". So I test my wl with "Home Gateway" and "Router" Modes, and the nfs works. I retry the "Access Point" mode and the error is still present. So I must stand in "Routeur" mode to use NFS Server but it is not a problem.

Now, here's my last question. Is it possible to launch nfs server with tcp protocol ??? when I launch the "rpcinfo -p 192.168.0.2" command (see below), i have only a udp-nfs server.

Thanks for your help to everone :) :cool: