Hi, installed today " dreambox-image-dm8000-20131014.nfi " on my dm8000 and wanted to set up nfsserver but I am unable to connect to it from my linux clients after executing following commands on my dm8000 ( see below ). Can one hint me so this will work again. TiA!

opkg update
opkg install nfs-utils

vi /etc/exports contains " /media/hdd *(rw,async,nohide,fsid=0,no_subtree_check,no_root_squash) "

/etc/init.d/nfsserver restart

stopping mountd: done
stopping statd: done
starting mountd: done
starting statd: /usr/sbin/rpc.statd is already running
654
done

/etc/init.d/portmap restart
/etc/init.d/portmap: line 56: pmap_dump: not found
Stopping portmap daemon...
Starting portmap daemon...
/etc/init.d/portmap: line 56: pmap_set: not found

exportfs -ra

ps ax | grep -e nfsd -e portmap -e mountd
20927 ? Ss 0:00 /usr/sbin/rpc.mountd -f /etc/exports
21137 ? Ss 0:00 /sbin/portmap
21360 pts/0 R+ 0:00 grep -e nfsd -e portmap -e mountd

showmount -e
Export list for dm8000:
/media/hdd *

Clients say:

:~# mount -a
mount: 192.168.10.11:/media/hdd failed, reason given by server: Permission denied
mount: RPC: Remote system error - No route to host

Hmm I assume there is no firewall active as localhost gives same headache ?

1/ * or 192.168.10.0/24 did not solve

2/

:~# telnet 192.168.10.11 111
^C
Console escape. Commands are:


 l    go to line mode
 c    go to character mode
 z    suspend telnet
 e    exit telnet
root@xp1000:~# telnet 192.168.10.11 1110
telnet: can't connect to remote host (192.168.10.11): Connection refused
root@xp1000:~# telnet 192.168.10.11 2049
telnet: can't connect to remote host (192.168.10.11): Connection refused
root@xp1000:~# telnet 192.168.10.11 4045
telnet: can't connect to remote host (192.168.10.11): Connection refused

on dm8000:

root@dm8000:/media/hdd/dm8000# telnet localhost 4045
telnet: can't connect to remote host (127.0.0.1): Connection refused
root@dm8000:/media/hdd/dm8000# telnet localhost 2049
telnet: can't connect to remote host (127.0.0.1): Connection refused
root@dm8000:/media/hdd/dm8000# telnet localhost 1110
telnet: can't connect to remote host (127.0.0.1): Connection refused
root@dm8000:/media/hdd/dm8000# telnet localhost 111

of course I can telnet and ssh - no problem -

~ $ telnet 192.168.10.11 22
Trying 192.168.10.11...
Connected to 192.168.10.11.
Escape character is '^]'.
SSH-2.0-dropbear_2012.55
^]q


telnet> q
Connection closed.

~ $ telnet 192.168.10.11
Trying 192.168.10.11...
Connected to 192.168.10.11.
Escape character is '^]'.


opendreambox 2.0.0 dm8000




dm8000 login:

now nfs:

:~# mount -t nfs 192.168.10.11:/media/hdd /media/lan/wd
mount: 192.168.10.11:/media/hdd failed, reason given by server: Permission denied
mount: mounting 192.168.10.11:/media/hdd on /media/lan/wd failed: Bad file descriptor


:~# mount -t nfs4 192.168.10.11:/media/hdd /media/lan/wd
mount: 192.168.10.11:/media/hdd failed, reason given by server: Permission denied
mount: mounting 192.168.10.11:/media/hdd on /media/lan/wd failed: Bad file descriptor

And finally:

# /etc/init.d/nfsserver start
creating NFS state directory: done
starting 8 nfsd kernel threads: rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory).
Please try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem
done
starting mountd: /usr/sbin/rpc.mountd is already running
23717
done
starting statd: /usr/sbin/rpc.statd is already running
654
done


root@dm8000:/media/hdd/dm8000# ps aux | grep nfsd
root 	27694  0.0  0.3   2708   564 pts/0	S+   20:36   0:00 grep nfsd
root@dm8000:/media/hdd/dm8000# ps aux | grep 'portman'
root 	27710  1.0  0.3   2712   572 pts/0	S+   20:36   0:00 grep portman
root@dm8000:/media/hdd/dm8000# ps aux | grep 'mountd'
root 	23717  0.0  0.5   2392   772 ?    	Ss   20:13   0:00 /usr/sbin/rpc.mountd -f /etc/exports 
root 	27725  0.0  0.3   2712   572 pts/0	S+   20:36   0:00 grep mountd

ok this shows some interesting thoughts as module " kernel-module-nfsd " is not being downloaded automatically when you execute :

opkg update
opkg install nfs-utils

Guess this is something to add as a dependency for our convenience
After adding the kernel module things start to move finally ...

Case closed