Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Although Fonz has helped me trying to get NFSv3 to work with CH3SNAS I am in the middle of nowhere....
first of all: UNFSD.SH is working flawlessly, but it's the Kernel enabled NFS I want to get working.
I used mount -t nfs 172.20.0.24:/mnt/HD_a2 /tmp/test
or I used mount -o nolock 172.20.0.24:/mnt/HD_a2 /tmp/test
to start nfsd I did following:
first I have added at the bottom of fun_plug
sh /mnt/HD_a2/ffp/start/nfsd.sh start
now I see that ONLY
1550 root /ffp/sbin/rpc.portmap
1611 root /ffp/sbin/rpc.statd
1674 root [nfsd]
is started. Cause when stopping the script, restarting I get:
1852 root /ffp/sbin/rpc.portmap
1862 root /ffp/sbin/rpc.statd
1874 root [nfsd]
1875 root [nfsd]
1876 root [nfsd]
1877 root [nfsd]
1878 root [nfsd]
1879 root [nfsd]
1880 root [nfsd]
1881 root [nfsd]
1882 root [lockd]
1883 root [rpciod/0]
1893 root /ffp/sbin/rpc.mountd
so there is something wierd.. cause startscript should work flawlessly ..
The issue is following: on all my linux boxes (CentOS, Debian etc.. ) I get following message:
mount: mount to NFS server ‘172.20.0.24′ failed: timed out (retrying).
rcpinfo -p 172.20.0.24 gives all correct info
program vers proto port
100000 2 tcp 111 portmapper
100024 1 udp 1027 status
100024 1 tcp 1028 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100021 1 udp 1028 nlockmgr
100021 3 udp 1028 nlockmgr
100021 4 udp 1028 nlockmgr
100021 1 tcp 1029 nlockmgr
100021 3 tcp 1029 nlockmgr
100021 4 tcp 1029 nlockmgr
100005 1 udp 1029 mountd
100005 1 tcp 1030 mountd
100005 2 udp 1029 mountd
100005 2 tcp 1030 mountd
100005 3 udp 1029 mountd
100005 3 tcp 1030 mountd
showmount -e 172.20.0.24 gives all correct exports
Export list for 172.20.0.24:
/mnt/HD_a4 172.20.0.0/24
/mnt/HD_a2 172.20.0.0/24
/mnt/web_page 172.20.0.0/24
rpcinfo -u 172.20.0.24 gives:
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting
and even syslogd gives on the NFS server (CH3SNAS):
Jun 12 18:33:07 DEVELOPMENT daemon.notice mountd[1868]: authenticated mount request from 172.20.0.10:615 for /mnt/HD_a2 (/mnt/HD_a2)
Portmap is running at server and client!!
I am totally not understanding why I get time-outs. I do not have a firewall, I do not use iptables. Today I tried in another environment the same: always the error:
mount: mount to NFS server ‘192.168.1.60′ failed: timed out (retrying).
So although al tools tells me that everything is correct: I am not getting any mount :-(
Is there anyone with enough NFS knowledge who can tell me why the NFS share is not mounted?
Or maybe there are users with CH3SNAS firmware (1.04RC2 has for sure NFSv3 enabled) able to get it running?
Thanks
Offline
Hi, i checked the nfs support on an ubuntu box with a ch3snas with ffp0.5 (updated maybe 1-2 weeks ago with the new binaries from fonz's site) and fw 1.04RC2.
At console:
sh /mnt/HD_a2/ffp/start/portmap.sh start
sh /mnt/HD_a2/ffp/start/nfsd.sh start
Ps:
9556 root /ffp/sbin/rpc.portmap
9583 root /ffp/sbin/rpc.statd
9595 root [nfsd]
9596 root [nfsd]
9597 root [nfsd]
9598 root [nfsd]
9599 root [nfsd]
9600 root [nfsd]
9601 root [nfsd]
9602 root [nfsd]
9606 root [lockd]
9607 root [rpciod/0]
9614 root /ffp/sbin/rpc.mountd
And after that, issuing mount -t nfs ip:/mnt/HD_a2 /mnd/testdir mounts the share correctly.
If you want to verify something about my setup, just ask.
Offline
Although an unlikely problem on any decent Linux install, you might want to check for properly configured loopback networking (ifconfig lo). I think missing lo results in rpc timeouts (cannot talk to portmap).
Offline
fonz wrote:
Although an unlikely problem on any decent Linux install, you might want to check for properly configured loopback networking (ifconfig lo). I think missing lo results in rpc timeouts (cannot talk to portmap).
I have narrowed the issue down to following ..
Home and Office do share 2 different DSL routers: C54APRA2+ & ZYXEL P2602H, those 2 ADSL modems share the same chipset: TI but the rest: Hey ZyXEL should be a top brand for geeks not?
Both routers have NO firewall installed nothing .. ..
Suddenly 1 of my collegues needed to test a DSL modem with different chipset: Trendchip .. without informing me.
Suddenly all my mounts were valid ... .
I was thinking that a /etc/hosts.allow change I made was the solution, but nope.. if was the change of DSL router ..
So to narrow the issue down: 'something' in the 2 DSL modems is blocking (UDP ? / NETBIOS ? / TCP ?) traffic
causing mounts not to be working. (or very rare it gives a mount ..... (home situation often than office.. cause the Office with ZyXEL never gave me a mount .. (but with the c54apra2+ one time)
Last edited by zeroday (2008-06-17 15:40:34)
Offline
zeroday wrote:
Home and Office do share 2 different DSL routers
Not sure if I understand you correctly, but you should not run NFS over the Internet, or allow access to your NFS services from the Internet. Don't do that, never. Use VPN if you need access from outside your LAN.
PS: If both sides support NFS over TCP, here's a pretty simple approach: http://www.howtoforge.com/nfs_ssh_tunneling http://www.samag.com/documents/s=4072/s … m0203d.htm
Offline
fonz wrote:
zeroday wrote:
Home and Office do share 2 different DSL routers
Not sure if I understand you correctly, but you should not run NFS over the Internet, or allow access to your NFS services from the Internet. Don't do that, never. Use VPN if you need access from outside your LAN.
PS: If both sides support NFS over TCP, here's a pretty simple approach: http://www.howtoforge.com/nfs_ssh_tunneling http://www.samag.com/documents/s=4072/s … m0203d.htm
Yeah .. you do not understand me..
to create a 'network' people (end-user) use cablemodem&router or DSL modem/router
the device is their DHCP server, their DNS server ..
traffic is send to/from LAN ports of that router and a network is created. No internet involved at all ..
so it seems that there is something blocking internal network traffic when using above mentioned DSL modem/router(s).
I switched to another DSL Router and even a normal router and issues were gone....
So asking zyXEL how to fix this could be a valid solution ..
Last edited by zeroday (2008-06-17 17:31:07)
Offline
zeroday wrote:
So asking zyXEL how to fix this could be a valid solution ..
If it blocks NFS (which is just UDP) on the LAN ports, it's broken. You can still try mounting with "-o tcp" (which often is a good idea anyway, especially on wireless lans).
Offline
if someone has an idea...... this is the standard commandline mount -o nolock 192.168.1.60:/mnt/HD_a2 /tmp/development
[root@wb dennis]# /usr/sbin/tcpdump -n host 192.168.1.60
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
18:54:22.361692 IP 192.168.1.100.54939 > 192.168.1.60.sunrpc: S 347314494:347314494(0) win 5840 <mss 1460,sackOK,timestamp 887821734 0,nop,wscale 2>
18:54:22.361843 IP 192.168.1.60.sunrpc > 192.168.1.100.54939: S 3818436619:3818436619(0) ack 347314495 win 5792 <mss 1460,sackOK,timestamp 16361236 887821734,nop,wscale 1>
18:54:22.361894 IP 192.168.1.100.54939 > 192.168.1.60.sunrpc: . ack 1 win 1460 <nop,nop,timestamp 887821735 16361236>
18:54:22.362074 IP 192.168.1.100.54939 > 192.168.1.60.sunrpc: P 1:61(60) ack 1 win 1460 <nop,nop,timestamp 887821735 16361236>
18:54:22.362237 IP 192.168.1.60.sunrpc > 192.168.1.100.54939: . ack 61 win 2896 <nop,nop,timestamp 16361236 887821735>
18:54:22.362565 IP 192.168.1.60.sunrpc > 192.168.1.100.54939: P 1:33(32) ack 61 win 2896 <nop,nop,timestamp 16361236 887821735>
18:54:22.362578 IP 192.168.1.100.54939 > 192.168.1.60.sunrpc: . ack 33 win 1460 <nop,nop,timestamp 887821735 16361236>
18:54:22.362622 IP 192.168.1.100.54939 > 192.168.1.60.sunrpc: F 61:61(0) ack 33 win 1460 <nop,nop,timestamp 887821735 16361236>
18:54:22.362706 IP 192.168.1.100.54940 > 192.168.1.60.nfs: S 351393587:351393587(0) win 5840 <mss 1460,sackOK,timestamp 887821735 0,nop,wscale 2>
18:54:22.362795 IP 192.168.1.60.sunrpc > 192.168.1.100.54939: F 33:33(0) ack 62 win 2896 <nop,nop,timestamp 16361236 887821735>
18:54:22.362814 IP 192.168.1.100.54939 > 192.168.1.60.sunrpc: . ack 34 win 1460 <nop,nop,timestamp 887821735 16361236>
18:54:22.362885 IP 192.168.1.60.nfs > 192.168.1.100.54940: S 3822059319:3822059319(0) ack 351393588 win 5792 <mss 1460,sackOK,timestamp 16361236 887821735,nop,wscale 1>
18:54:22.362903 IP 192.168.1.100.54940 > 192.168.1.60.nfs: . ack 1 win 1460 <nop,nop,timestamp 887821736 16361236>
18:54:22.362942 IP 192.168.1.100.1100358375 > 192.168.1.60.2049: 44 null
18:54:22.363126 IP 192.168.1.60.nfs > 192.168.1.100.54940: . ack 45 win 2896 <nop,nop,timestamp 16361236 887821736>
18:54:22.363328 IP 192.168.1.60.2049 > 192.168.1.100.1100358375: reply ok 28 null
18:54:22.363339 IP 192.168.1.100.54940 > 192.168.1.60.nfs: . ack 29 win 1460 <nop,nop,timestamp 887821736 16361236>
18:54:22.363371 IP 192.168.1.100.54940 > 192.168.1.60.nfs: F 45:45(0) ack 29 win 1460 <nop,nop,timestamp 887821736 16361236>
18:54:22.363478 IP 192.168.1.100.35162 > 192.168.1.60.sunrpc: UDP, length 56
18:54:22.363529 IP 192.168.1.60.nfs > 192.168.1.100.54940: F 29:29(0) ack 46 win 2896 <nop,nop,timestamp 16361236 887821736>
18:54:22.363549 IP 192.168.1.100.54940 > 192.168.1.60.nfs: . ack 30 win 1460 <nop,nop,timestamp 887821736 16361236>
18:54:22.363970 IP 192.168.1.60.sunrpc > 192.168.1.100.35162: UDP, length 28
18:54:22.364044 IP 192.168.1.100.35162 > 192.168.1.60.1036: UDP, length 40
18:54:22.364470 IP 192.168.1.60.1036 > 192.168.1.100.35162: UDP, length 24
18:54:22.364553 IP 192.168.1.100.743 > 192.168.1.60.1036: UDP, length 120
18:54:25.364532 IP 192.168.1.100.743 > 192.168.1.60.1036: UDP, length 120
18:54:26.691140 IP 192.168.1.60.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
18:54:26.697810 arp who-has 192.168.1.60 tell 192.168.1.62
18:54:28.364983 IP 192.168.1.100.743 > 192.168.1.60.1036: UDP, length 120
18:54:31.365489 IP 192.168.1.100.743 > 192.168.1.60.1036: UDP, length 120
18:54:34.365982 IP 192.168.1.100.743 > 192.168.1.60.1036: UDP, length 120
18:54:37.366470 IP 192.168.1.100.743 > 192.168.1.60.1036: UDP, length 120
18:54:40.366972 IP 192.168.1.100.743 > 192.168.1.60.1036: UDP, length 120
18:54:43.370493 IP 192.168.1.100.54941 > 192.168.1.60.sunrpc: S 393419962:393419962(0) win 5840 <mss 1460,sackOK,timestamp 887842747 0,nop,wscale 2>
18:54:43.370636 IP 192.168.1.60.sunrpc > 192.168.1.100.54941: S 3844423562:3844423562(0) ack 393419963 win 5792 <mss 1460,sackOK,timestamp 16363345 887842747,nop,wscale 1>
18:54:43.370681 IP 192.168.1.100.54941 > 192.168.1.60.sunrpc: . ack 1 win 1460 <nop,nop,timestamp 887842747 16363345>
18:54:43.375429 IP 192.168.1.100.54941 > 192.168.1.60.sunrpc: P 1:61(60) ack 1 win 1460 <nop,nop,timestamp 887842752 16363345>
18:54:43.375581 IP 192.168.1.60.sunrpc > 192.168.1.100.54941: . ack 61 win 2896 <nop,nop,timestamp 16363346 887842752>
18:54:43.375875 IP 192.168.1.60.sunrpc > 192.168.1.100.54941: P 1:33(32) ack 61 win 2896 <nop,nop,timestamp 16363346 887842752>
18:54:43.375904 IP 192.168.1.100.54941 > 192.168.1.60.sunrpc: . ack 33 win 1460 <nop,nop,timestamp 887842752 16363346>
18:54:43.376052 IP 192.168.1.100.54941 > 192.168.1.60.sunrpc: F 61:61(0) ack 33 win 1460 <nop,nop,timestamp 887842752 16363346>
18:54:43.376136 IP 192.168.1.100.54942 > 192.168.1.60.nfs: S 396507107:396507107(0) win 5840 <mss 1460,sackOK,timestamp 887842752 0,nop,wscale 2>
18:54:43.376246 IP 192.168.1.60.nfs > 192.168.1.100.54942: S 3849714904:3849714904(0) ack 396507108 win 5792 <mss 1460,sackOK,timestamp 16363346 887842752,nop,wscale 1>
18:54:43.376278 IP 192.168.1.100.54942 > 192.168.1.60.nfs: . ack 1 win 1460 <nop,nop,timestamp 887842752 16363346>
18:54:43.376477 IP 192.168.1.60.sunrpc > 192.168.1.100.54941: F 33:33(0) ack 62 win 2896 <nop,nop,timestamp 16363346 887842752>
18:54:43.376509 IP 192.168.1.100.54941 > 192.168.1.60.sunrpc: . ack 34 win 1460 <nop,nop,timestamp 887842753 16363346>
18:54:43.376688 IP 192.168.1.100.1945128884 > 192.168.1.60.2049: 44 null
18:54:43.376825 IP 192.168.1.60.nfs > 192.168.1.100.54942: . ack 45 win 2896 <nop,nop,timestamp 16363346 887842753>
18:54:43.376948 IP 192.168.1.60.2049 > 192.168.1.100.1945128884: reply ok 28 null
18:54:43.376966 IP 192.168.1.100.54942 > 192.168.1.60.nfs: . ack 29 win 1460 <nop,nop,timestamp 887842753 16363346>
18:54:43.377130 IP 192.168.1.100.54942 > 192.168.1.60.nfs: F 45:45(0) ack 29 win 1460 <nop,nop,timestamp 887842753 16363346>
18:54:43.377214 IP 192.168.1.100.35162 > 192.168.1.60.sunrpc: UDP, length 56
18:54:43.377345 IP 192.168.1.60.nfs > 192.168.1.100.54942: F 29:29(0) ack 46 win 2896 <nop,nop,timestamp 16363346 887842753>
18:54:43.377382 IP 192.168.1.100.54942 > 192.168.1.60.nfs: . ack 30 win 1460 <nop,nop,timestamp 887842754 16363346>
18:54:43.377700 IP 192.168.1.60.sunrpc > 192.168.1.100.35162: UDP, length 28
18:54:43.377886 IP 192.168.1.100.35162 > 192.168.1.60.1036: UDP, length 40
18:54:46.377964 IP 192.168.1.100.35162 > 192.168.1.60.1036: UDP, length 40
18:54:49.378462 IP 192.168.1.100.35162 > 192.168.1.60.1036: UDP, length 40
18:54:52.305460 IP 192.168.1.60.1036 > 192.168.1.100.743: UDP, length 68
18:54:52.305533 IP 192.168.1.100 > 192.168.1.60: icmp 104: 192.168.1.100 udp port 743 unreachable
Offline
Just with two trendchip adsl modem with IC+ lan chipset I am able to mount within ten's of seconds .. where all kind of other routers / switches the NFS server is dropping on UDP port unreachable ..
it's almost unbelievable that a 1 on 1 connection between NAS and PC is not working as well.
and when I connect that stupid dsl router it works ..
and when using another type of dsl router it is randomly sometimes working ..
NFS is stupid .. but I want to know why .. ;-)
Last edited by zeroday (2008-06-20 12:07:36)
Offline
zeroday wrote:
issue is solved ..
if DNS of CH3SNAS is equal to gateway address (router normally) it will not work or work occassionally, when DNS is not entered and or is the DNS of your ISP: working like hell ..
Is your gateway DNS daemon working correctly? I would imagine that there is something not right there.
Offline
Hi,
I am agreeing with skydreamer. I have the the same IP for my CH3SNAS DNS and Gateway. It works like a charm and I am not experiencing any problems. Still, got to know that you solved the problem.
Markus
Offline
skydreamer wrote:
zeroday wrote:
issue is solved ..
if DNS of CH3SNAS is equal to gateway address (router normally) it will not work or work occassionally, when DNS is not entered and or is the DNS of your ISP: working like hell ..Is your gateway DNS daemon working correctly? I would imagine that there is something not right there.
That is something I will have to check later ..
cause as explained before: when using a low low low cost dsl router it's working like a charm,
but using a different kind of router / dsl modem it did not work and only solving it with external DNS it was and is working (2 environments, different kind of network and hardware). Even my direct contacts do not have any issue and try to duplicate what I have .. so determine if it's something in the CH3SNAS or some setting in router.. We want to learn from it ;-)
So I will test later this week some new settings in my dsl modem on DNS level ..
Offline