Re: Connection refusal for an NFS mount
David Kelly wrote: On Thu, Jul 20, 2006 at 07:43:16PM +0200, David Landgren wrote: David Kelly wrote: For starters try showmount -e the.freebsd.ip.address on the Linux box to see if the Linux box sees the NFS daemons on the FreeBSD machine. Hrm. # showmount -e 172.17.0.21 mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive I don't think NFS is going to work until you can get past the above problem. Running showmount -e on your FreeBSD machine should display the essential contents of /etc/exports. I added /var 172.17.0.21 /usr 127.0.0.1 to /etc/exports on the FreeBSD machine, hupped mountd, and when I run showmount -e 172.17.0.21 showmount -e 127.0.0.1 ... either command just hangs indefinitely. Hmm. What does the FreeBSD machine have to say about your attempts to connect from Linux in /var/log/messages? Nothing. Which is reasonable, given the above. So it looks like NFS is hosed on this box. Let's see now, relevant lines from rc.conf firewall_enable=YES firewall_type=open kern_securelevel_enable=NO nfs_access_cache=2 nfs_bufpackets= nfs_reserved_port_only=NO nfs_server_enable=YES nfs_server_flags=-u -t -n 4 mountd_enable=YES ntpd_enable=YES rpc_lockd_enable=NO rpcbind_enable=YES rpc_statd_enable=YES Hmm. I don't what nfs_bufpackets does. Short of rebooting the server, how do I reinitialise the NFS layers? Does the following order sound sane? /etc/rc.d/mountd stop /etc/rc.d/nfsd stop /etc/rc.d/rpcbind stop ... and the the same again with start in the reverse order? Thanks, David -- Much of the propaganda that passes for news in our own society is given to immobilising and pacifying people and diverting them from the idea that they can confront power. -- John Pilger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connection refusal for an NFS mount
David Landgren wrote: Short of rebooting the server, how do I reinitialise the NFS layers? Does the following order sound sane? /etc/rc.d/mountd stop /etc/rc.d/nfsd stop /etc/rc.d/rpcbind stop ... and the the same again with start in the reverse order? rpcbind must be started first in order for mountd and nfsd to register with it correctly. You can force mountd to bind to a specific port, then it should(?) also be possible to get things working without rpcbind. You need only to restart mountd when you change your exports file. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connection refusal for an NFS mount
On Thu, Jul 20, 2006 at 05:16:16PM +0200, David Landgren wrote: List, On an old Redhat box (address 172.17.0.18), I'm trying to mount an NFS export from a FreeBSD (5.2.1-RELEASE) box. Both machines are on the same network segment, and neither have any onboard firewalling rules. [...] (I understand, from reading the handbook, that I should be using rpcbind rather than portmap). This server has been an NFS server in the past, so I know it worked at some point. I'm not sure if I'm missing a daemon in the mix, or if there's something else I've overlooked. Any clues will be most graciously received :) For starters try showmount -e the.freebsd.ip.address on the Linux box to see if the Linux box sees the NFS daemons on the FreeBSD machine. mountd needs to be running on the FreeBSD host (apparently yours is running). When /etc/exports changes mountd needs to be informed: kill -s HUP `cat /var/run/mountd.pid` Also at least in the past Linux distributions defaulted NFS to non-reserved ports. Your Linux may not be talking to the same ports as the FreeBSD machine is listening. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connection refusal for an NFS mount
David Kelly wrote: On Thu, Jul 20, 2006 at 05:16:16PM +0200, David Landgren wrote: List, On an old Redhat box (address 172.17.0.18), I'm trying to mount an NFS export from a FreeBSD (5.2.1-RELEASE) box. Both machines are on the same network segment, and neither have any onboard firewalling rules. [...] (I understand, from reading the handbook, that I should be using rpcbind rather than portmap). This server has been an NFS server in the past, so I know it worked at some point. I'm not sure if I'm missing a daemon in the mix, or if there's something else I've overlooked. Any clues will be most graciously received :) For starters try showmount -e the.freebsd.ip.address on the Linux box to see if the Linux box sees the NFS daemons on the FreeBSD machine. Hrm. # showmount -e 172.17.0.21 mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive mountd needs to be running on the FreeBSD host (apparently yours is running). When /etc/exports changes mountd needs to be informed: kill -s HUP `cat /var/run/mountd.pid` Yup, know about that. Also at least in the past Linux distributions defaulted NFS to non-reserved ports. Your Linux may not be talking to the same ports as the FreeBSD machine is listening. Let's have a look... # nmap 172.17.0.21 Starting nmap V. 3.00 ( www.insecure.org/nmap/ ) Interesting ports on bechet.bpinet.com (172.17.0.21): (The 1584 ports scanned but not shown below are in state: closed) Port State Service 21/tcp openftp 22/tcp openssh 25/tcp opensmtp 37/tcp opentime 80/tcp openhttp 199/tcpopensmux 443/tcpopenhttps 801/tcpopendevice 901/tcpopensamba-swat 1011/tcp openunknown 1020/tcp openunknown 2049/tcp opennfs 3306/tcp openmysql 5308/tcp opencfengine 5432/tcp openpostgres 5999/tcp openncd-conf 8080/tcp openhttp-proxy My god there's a lot of crap on that box! Still, looks like NFS is running. And according to the man page of the linux box: port=n The numeric value of the port to connect to the NFS server on. If the port number is 0 (the default) then query the remote host's portmapper for the port number to use. If the remote hostâs NFS daemon is not regis- tered with its portmapper, the standard NFS port number 2049 is used instead. So that sounds about right. I tried adding port=2049 explictly to the mount command, but same error: Connection refused Well, thanks for your help. Beats me what I've done wrong. Thanks, David -- Much of the propaganda that passes for news in our own society is given to immobilising and pacifying people and diverting them from the idea that they can confront power. -- John Pilger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connection refusal for an NFS mount
On Thu, Jul 20, 2006 at 07:43:16PM +0200, David Landgren wrote: David Kelly wrote: For starters try showmount -e the.freebsd.ip.address on the Linux box to see if the Linux box sees the NFS daemons on the FreeBSD machine. Hrm. # showmount -e 172.17.0.21 mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive I don't think NFS is going to work until you can get past the above problem. Running showmount -e on your FreeBSD machine should display the essential contents of /etc/exports. What does the FreeBSD machine have to say about your attempts to connect from Linux in /var/log/messages? -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
