OESF Forums > NFS in pdaxrom?

Xumbi

Oct 12 2004, 06:02 PM

I have two boxes running Debian that I would like to connect my Z to with NFS, but I've never actually used NFS before. Can someone point me to some good documentation?

blakeyez

Oct 12 2004, 06:06 PM

NFS is pretty easy to setup... Easy to leave very insecure, too, so unless you really want to read a lot, my suggestion is to run it behind a firewall.

Anyway, the NFS HowTo should do you for good documentation about NFS usage in Linux in general. The implementation in pdaXrom shouldn't be too different from the norm.

Dave

Xumbi

Oct 12 2004, 06:21 PM

Thanks for the reply. I have read that howto, but unfortunately it seems like Debian does things differently (I couldn't find some of the rpc.* commands for example). So I guess I need to find documentation specific to Debian, but google searches so far haven't turned up anything.

wizzro

Oct 13 2004, 02:07 AM

First you need a kernel with NFS filesystem support (or modules) and some packages installed :
dpkg -l nfs-\* | grep ii
ii nfs-common 1.0.6-3 NFS support files common to client and serve
ii nfs-kernel-ser 1.0.6-3 Kernel NFS server support

Next you add a line like this and you replace with your own sttings :
/data 192.168.10.2(rw,no_root_squash,sync)

And finally you restart nfs (with root) with the command /etc/init.d/nfs-kernel-server restart

On the zaurus
mount -t nfs -o hard,intr,nolock,nfsvers=2 192.168.10.1:/data /tmp/p

I hope this help you

Xumbi

Oct 13 2004, 04:47 AM

QUOTE(wizzro @ Oct 13 2004, 05:07 AM)

First you need a kernel with NFS filesystem support (or modules) and some packages installed :
dpkg -l nfs-\* | grep ii
ii nfs-common 1.0.6-3 NFS support files common to client and serve
ii nfs-kernel-ser 1.0.6-3 Kernel NFS server support

Next you add a line like this and you replace with your own sttings :
/data 192.168.10.2(rw,no_root_squash,sync)

And finally you restart nfs (with root) with the command /etc/init.d/nfs-kernel-server restart

On the zaurus
mount -t nfs -o hard,intr,nolock,nfsvers=2 192.168.10.1:/data /tmp/p

I hope this help you

Thanks for the thorough reply. From your instructions, and from google searches, I eventually figured it out. I pretty much did everything you said, except I couldn't get it to work with nfs-kernel-server, so I removed that and installed nfs-user-server instead, and that worked.

This is great, now I can get to my entire music collection on my Z! Wirelessly!!

alan

Nov 30 2004, 12:39 AM

QUOTE

This is great, now I can get to my entire music collection on my Z! Wirelessly!!

lucky you are, dear Xumbi...

on the Zaurus side, i keep stuck in

CODE

# mount /mnt/cdrom
mount: RPC: Port mapper failure - RPC: Unable to recieve

I don't understand...

by the way, i can ssh from the Z to my linux box, but i can't ssh from the pc to the zaurus. Dunno if it's related,but maybe...

wizzro

Nov 30 2004, 10:34 AM

QUOTE

on the Zaurus side, i keep stuck in

CODE

# mount /mnt/cdrom
mount: RPC: Port mapper failure - RPC: Unable to recieve

I don't understand...

Can you try with all the options :
mount -t nfs -o hard,intr,nolock,nfsvers=2

and especially nolock

alan

Dec 1 2004, 02:57 AM

QUOTE

Can you try with all the options :
mount -t nfs -o hard,intr,nolock,nfsvers=2

i did

CODE

mount -t nfs -o hard,intr,nolock,nfsvers=2 192.168.129.200:/mnt/cdrom /mnt/cdrom

but i have the same error

pgas

Dec 1 2004, 05:42 AM

QUOTE

# mount /mnt/cdrom
mount: RPC: Port mapper failure - RPC: Unable to recieve

for me it looks like something is wrong with the server not started for example.

how do you start the nfs server?

About your ssh problems what happens when you ssh to your Z?

alan

Dec 1 2004, 07:38 AM

hi !

i have a mandrake 10.0 and nfs is launched at boot.

i think it may be related to my firewall but i am not sure. what port should i leave open ?

CODE

# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 992 status
100024 1 tcp 995 status
391002 2 tcp 32768 sgi_fam
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 udp 32771 nlockmgr
100021 3 udp 32771 nlockmgr
100021 4 udp 32771 nlockmgr
100021 1 tcp 32769 nlockmgr
100021 3 tcp 32769 nlockmgr
100021 4 tcp 32769 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

and about this ssh trouble:

CODE

# ssh root@192.168.129.201
ssh: connect to host 192.168.129.201 port 22: Connection refused

pgas

Dec 1 2004, 08:27 AM

hmm, it seems you use the usb cable for ip connection to the zaurus.

It can also be a routing problem, like packets for 192.168.129.201 are sent through eth0 and not through usb0. Can you ping 192.168.129.201?

For the firewall you can try to open everything, just to see if it is the pb.

alan

Dec 1 2004, 09:53 AM

QUOTE(pgas @ Dec 1 2004, 08:27 AM)

It can also be a routing problem, like packets for 192.168.129.201 are sent through eth0 and not through usb0. Can you ping 192.168.129.201?

you're right ! i can't ping the zaurus... but the strange thing if that i can access the net via my usb connection

I thought every kind of connection would follow the same route... Do you know what i shoul do ?

pgas

Dec 1 2004, 10:27 AM

do an ifconfig and check the mask for eth0.
it the mask is 255.0.0.0 or 255.255.0.0 then this might be the cause of the problem because then
linux will route all packet targeted 192.*.*.* or 192.168.*.* to eth0.

you could try

ifconfig eth0 netmask 255.255.255.0

(if I remember well)

otherwise you need to check the routing with route

Not I am no network admin so....