Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!grumpy.fl.net.au!news.webspan.net!news.intersurf.net!hunter.premier.net!news.algonet.se!hammer.uoregon.edu!news-xfer.netaxs.com!gryphon.phoenix.net!alpha1.phoenix.net!pflores
From: Paul Flores <pflores@phoenix.net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: NFS struggles
Date: Mon, 10 Mar 1997 15:41:43 -0600
Organization: C-Com/Phoenix Data Net (281) 486-8337/ http://www.phoenix.net
Lines: 50
Message-ID: <Pine.OSF.3.95.970310153518.2362A-100000@alpha1.phoenix.net>
References: <5flph7$dmb@delphi.cs.ucla.edu> <Pine.OSF.3.95.970309163850.7119B-100000@alpha1.phoenix.net> <5g1n68$sqr@news.aero.org>
NNTP-Posting-Host: alpha1.phoenix.net
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: Scott Michel <scottm@tommyc>
In-Reply-To: <5g1n68$sqr@news.aero.org>
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36878
-----BEGIN PGP SIGNED MESSAGE-----
On 10 Mar 1997, Scott Michel wrote:
> Paul Flores (pflores@phoenix.net) wrote:
> : On 6 Mar 1997, Scott Michel wrote:
>
> : What is the server machine running? I ran into a similar problem
> : trying to mount a NFS drive off a DecSafe cluster.
>
> Both the client and the server are running FreeBSD 2.1.6. The server
> has more than one interface (semi-obviously).
I assume one of these is an aliased address on the same interface?
Or if they are 2 physical interfaces, which one has the default gateway?
>
> : Try mounting to server-intfs2 instead. I think you may be
> : confusing the poor NFS daemon! (if it IS a DecSafe system,
> : look into amd to solve your problem.)
>
> I tried this hack, and it works. It should not be necessary, unless of
> course there's a good reason for it. It makes the automount maps look
> really nasty - you have to put 'wire==' selectors all over the place.
>
I have noticed that with some UDP-based services (like time ) that the
system will reply from the 'real' IP address of the interface, as
opposed to replying from the 'alias' IP address. Since it does not affect
every service the same way, I tend to think it is a problem with the
application more than the OS. Somewhere in the dusty source of NFS, is
probably a call to an interface, and it doesn't know/understand how to
respond via an alias interface...
Paul Flores
"Show me an Ethernet collision and I'll show you a network that
could do with one user fewer" --BOFH
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMySABl+1EJlsVhPxAQHZrwP+MOMJg3dsTRsy2hqfm03AJneQI4bV2Gqq
6XaCRG9s2qOBUHqwkIunkJIeZJ+TqaB+8CogtqGtLzm3JObn7buYB6rvjMm5DXFq
A45gz7c/jXiV8QOPGju+c5HKh06YUINTy+gabpUOiZ4uMdm8ydUVZEvXzk+zVDc/
TgMEoz9yd1Y=
=fK7P
-----END PGP SIGNATURE-----