Odd NFS behaviour
Hi there.
I have been having strange a strange problem with NFS on
two machines on my home network.
trell (192.168.0.2 on the internal network)
is a machine running Debian sid, connected to a cable
modem and providing masquerading for the rest of the network through the
ipmasq package.
tripod (192.168.0.5)is another box running woody, which masquerades through
trell for its external connectivity.
Both are running home-compiled 2.4.18 kernels with NFS kernel server support
compiled in on tripod, and client support compiled in on trell, and what
I assume are the requisite client and server debian packages respectively.
I mount my home directory on tripod to a mount directory (/mnt/trihome)
on trell using NFS.
The /etc/hosts.allow on tripod is as follows:
portmap: 192.168.0.
lockd: 192.168.0.
mountd: 192.168.0.
statd: 192.168.0.
/etc/exports is as follows:
/home/rgmerk 192.168.0.2(rw)
When I attempt to mount the exported file system with the following
command:
mount -t nfs tripod:/home/rgmerk /mnt/trihome
the mount command hangs (just sits there and does nothing, and ^C doesn't
kill it) for two or three minutes, then finally completes and the system
mounts successfully.
A google search for people with similar systems gave me a hint that I should
try the nolock option, which I did:
mount -o nolock -t nfrs tripod:/home/rgmerk /mnt/tripod
which works fine.
Reading the documentation, it is suggested that nolock is required only for
old NFS servers that don't support locking. However, the lock daemon seems
to be running on tripod:
<trell> ~ : rpcinfo -p tripod
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 1024 status
100024 1 tcp 1024 status
100003 2 udp 2049 nfs
100021 1 udp 1026 nlockmgr
100021 3 udp 1026 nlockmgr
100021 4 udp 1026 nlockmgr
100005 1 udp 1027 mountd
100005 1 tcp 1025 mountd
100005 2 udp 1027 mountd
100005 2 tcp 1025 mountd
So why do I have to mount with "nolock"? Is it something
weird going on with my hosts.allow on tripod? Some kernel
option I've forgotten to compile in? Some firewall rule
that ipmasq is setting up? (output of iptables -L is below)
Any help would be much appreciated.
output from iptables -L on trell:
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere
LOG all -- 127.0.0.0/8 anywhere LOG level warning
DROP all -- 127.0.0.0/8 anywhere
ACCEPT all -- anywhere 255.255.255.255
ACCEPT all -- 192.168.0.0/24 anywhere
ACCEPT !tcp -- anywhere BASE-ADDRESS.MCAST.NET/4
LOG all -- 192.168.0.0/24 anywhere LOG level warning
DROP all -- 192.168.0.0/24 anywhere
ACCEPT all -- anywhere 255.255.255.255
ACCEPT all -- anywhere CPE-144-132-38-122.vic.bigpond.net.au
ACCEPT all -- anywhere CPE-144-132-39-255.vic.bigpond.net.au
LOG all -- anywhere anywhere LOG level warning
DROP all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT all -- 192.168.0.0/24 anywhere
ACCEPT all -- anywhere 192.168.0.0/24
LOG all -- anywhere 192.168.0.0/24 LOG level warning
DROP all -- anywhere 192.168.0.0/24
LOG all -- anywhere anywhere LOG level warning
DROP all -- anywhere anywhere
Chain OUTPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere 255.255.255.255
ACCEPT all -- anywhere 192.168.0.0/24
ACCEPT !tcp -- anywhere BASE-ADDRESS.MCAST.NET/4
LOG all -- anywhere 192.168.0.0/24 LOG level warning
DROP all -- anywhere 192.168.0.0/24
ACCEPT all -- anywhere 255.255.255.255
ACCEPT all -- CPE-144-132-38-122.vic.bigpond.net.au anywhere
ACCEPT all -- CPE-144-132-39-255.vic.bigpond.net.au anywhere
LOG all -- anywhere anywhere LOG level warning
DROP all -- anywhere anywhere
--
------------------------------------------------------------
Robert Merkel rgmerk@mira.net
Node FLY on Melbourne Wireless : http://www.wireless.org.au
------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: