Thanks for your reply. My problem, however, is that the NFS servers I'm
dealing with run a plethora of OSs. Believe you me, I'd love to run FreeBSD
on all of 'em, but that is simply out of my control. The '-h' option for
nfsd that was introduced v4.0 would be a great fix for this. What I really
need is a means to make the FreeBSD client not be so picky about where the
return packets are coming from. I've since learned that this is a
long-standing issue with FreeBSD:
http://www.freebsd.org/cgi/query-pr.cgi?pr=2858
http://www.freebsd.org/cgi/query-pr.cgi?pr=16239
Thanks,
-G
/*
Glen R. J. Neff
[EMAIL PROTECTED]
919-248-6145
Dirty deeds done for a meager 20% markup. . .
*/
-----Original Message-----
From: Matthew Dillon [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 09, 2000 22:25
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Problem mouting NFS exports from multi-homed servers
:The one problem standing in the way of my being able to implement this
:solution is a very specific problem with mounting NFS exports from
:multi-homed servers on our network. We have this problem both from the
:FreeBSD box itself and from the "NAT'ed" clients on the 10.x.x.x networks
it
:serves.
There are two solutions to this problem, both involving fixing the
NFS server.
The problem is that the FreeBSD NFS server would respond to UDP NFS
packets using a different source IP then they were sent to.
The solution is to either use TCP NFS mounts, or to use the -h option
to nfsd (see 'man nfsd') to force nfsd to bind to and respond
to UDP packets using the same interface IP.
'man nfsd' should give you enough information to fix this on your
NFS server. You should not have to mess with the clients at all.
I'm pretty sure I backported this feature to 3.x.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
