Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Jan 2002 17:10:01 -0800 (PST)
From:      Ian Dowse <iedowse@maths.tcd.ie>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: bin/33515: amd incorrectly handles multi-homed nfs servers - causing failures 
Message-ID:  <200201040110.g041A1K06147@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/33515; it has been noted by GNATS.

From: Ian Dowse <iedowse@maths.tcd.ie>
To: Eric Anderson <anderson@centtech.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: bin/33515: amd incorrectly handles multi-homed nfs servers - causing failures 
Date: Fri, 04 Jan 2002 01:05:42 +0000

 In message <200201032012.g03KCcX53390@freefall.freebsd.org>, Eric Anderson writ
 es:
 >I have a FreeBSD client on net A, and a multi-homed NFS server (running Linux,
 > or
 >Solaris, take your pick) on nets A and B.  If I attempt to access the server
 >with automounter (amd) via the interface that is NOT on my net (A), it times
 >out, responding with:
 
 This sounds like the common server-side bug where the server responds
 from the wrong IP address. I'm not sure if Linux or Solaris have a
 way to avoid this, but when using FreeBSD as the NFS server, just
 add "-h bindip" options to nfsd for each IP address on the server.
 
 The workaround for servers that cannot be made use the correct
 source address is simply to use the address that works. I don't
 think that FreeBSD can do much more here without resorting to the
 insecure approach of accepting replies from any address at all.
 
 >If, on a client, I try to do a 'cd /net/server1/' to a NIC (on the server) tha
 >t
 >will timeout (as mentioned above), and as soon as it starts timing out, I do
 >ctrl-C to break from it, and open another window and do a 'cd
 >/net/server2/share/', when the first 'cd' command finally breaks, it will drop
 >to a /net/server2/share/ directory, instead of the original working directory.
 >.
 >So it sounds kind of like the NFS handles are being reused too quickly or
 >something like that.
 
 Weird, that is probably a real amd bug.
 
 Ian

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201040110.g041A1K06147>