Date: Thu, 20 Dec 2001 18:57:23 +0000 From: Ian Dowse <iedowse@maths.tcd.ie> To: Andy Dills <andy@xecu.net> Cc: freebsd-questions@freebsd.org Subject: Re: NFS Question Message-ID: <200112201857.aa80522@salmon.maths.tcd.ie> In-Reply-To: Your message of "Thu, 20 Dec 2001 13:41:35 EST." <Pine.GSO.4.32.0112201339510.22899-100000@shell.xecu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.GSO.4.32.0112201339510.22899-100000@shell.xecu.net>, Andy Dill s writes: >Doing that yields: > >13:37:24.143946 216.127.136.208.966 > server.ip.111: udp 56 >13:37:24.144705 216.127.136.208.2224826569 > server.ip.2049: 40 null > >I've worked with tcpdump a fair amount, but I must admit that I'm not sure >what this indicates. Any ideas or suggestions? Hmm, the server responses should have appeared there - is the server multi-homed or something - could it be sending the replies using the wrong source address? Try tcpdump -np -s 1600 udp port 2049 and see if you see anything that looks like it might be a response to the 216.127.136.208.xid > server.ip.2049: 40 null packet. The "NFSPROC_NULL: RPC: Timed out." error means that mount_nfs didn't get a response from the server nfsd, and the tcpdump trace doesn't show any reply either. However, no reply is shown from the server portmap (port 111) service yet it looks as if the client received a reply because it immediately sent a request to nfsd. This would tie in with a source-address problem, because in FreeBSD the code for talking to nfsd is fussy about getting the right source address in replies, but the code for talking to portmap isn't. The FreeBSD nfsd has a '-h' option to force it to bind to multiple addresses for multi-homed hosts. I'm not sure if Solaris has anything similar. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <200112201857.aa80522>