[Hosting] NFS Help

Jon Carnes hosting@trilug.org
Wed, 7 Aug 2002 17:09:09 -0400


Try

/home		192.168.77.0/24(rw,insecure,no_auth_nlm,root_squash)

That generally works for me no matter what the architecture of the client
machine is.
Is ypbind running on the client machine?

-----Original Message-----
From: hosting-admin@trilug.org [mailto:hosting-admin@trilug.org]On
Behalf Of Tanner Lovelace
Sent: Wednesday, August 07, 2002 4:23 PM
To: hosting@trilug.org
Subject: [Hosting] NFS Help


On Wed, 2002-08-07 at 16:09, Jon Carnes wrote:
> Sound good.  Let me know if you need help with NFS.

Actually, now that you mention it.. :-)

Okay, so all the machines now have two interfaces, a public interface
with public ip addresses, and a private interface with addresses
in the 192.168.77.0 network.  I've set fatalpha up to export
/home like this (in /etc/exports):

/home           192.168.77.0/24(rw,root_squash)

I've verified that I can ping and ssh between computers
using the 192.168.77.n addresses.  I've also run
showmount -e from the ftp server to see what it could
see that fatalpha was exporting.

[root@dargo root]# showmount -e 192.168.77.1
Export list for 192.168.77.1:
/home 192.168.77.0/24

However, when I try to mount the disk, it hangs. :-(

[root@dargo root]# mount -t nfs 192.168.77.1:/home /mnt/home

On fatalpha, I see the following in the log:

Aug  7 16:00:49 fatalpha rpc.mountd: authenticated mount request from
192.168.77.2:1008 for /home (/home)

On dargo, though, I get the following:

Aug  7 11:51:20 dargo kernel: nfs: server 192.168.77.1 not responding,
still trying

It appears I may be firewalling nfs (or possibly portmap?).

Other things.  In /etc/hosts.deny on both machines, I have

portmap: ALL
161.58.165.78

(I don't know what the ip address is, it was there beforehand.
and it's only on fatalpha, not dargo.)

In /etc/hosts.allow, I have

portmap: 192.168.77.0/255.255.255.0

In the ipchains setup on dargo I have:

-A input -s 0/0 -d 0/0 -i eth1 -j ACCEPT

to tell it that eth1 is a "trusted" interface.  On fatalpha,
we have

-A input -s 192.168.77.0/255.255.255.0 -d 192.168.77.0/255.255.255.0 -i
eth1 -j ACCEPT

in the ipchains file.

So, any thoughts?  I'm pretty sure it's getting firewalled somewhere,
but I'm not sure where.  I'm about to try it between dargo and
moya because their ipchains configurations are much simpler
than fatalpha's (which is enormous).

Thanks,
Tanner
--
Tanner Lovelace | lovelace@wayfarer.org | http://wtl.wayfarer.org/
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
GPG Fingerprint = A66C 8660 924F 5F8C 71DA  BDD0 CE09 4F8E DE76 39D4
GPG Key can be found at http://wtl.wayfarer.org/lovelace.gpg.asc
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
          Si hoc legere scis, nimium eruditionis habes.

_______________________________________________
Hosting mailing list
Hosting@trilug.org
http://www.trilug.org/mailman/listinfo/hosting