Date: Tue, 24 Oct 1995 18:17:02 -0700 From: David Greenman <davidg@Root.COM> To: mikebo@tellabs.com Cc: hackers@freebsd.org, bugs@freebsd.org Subject: Re: 2.1.0-951020-SNAP: Major bug in NFS again! Message-ID: <199510250117.SAA27638@corbin.Root.COM> In-Reply-To: Your message of "Tue, 24 Oct 95 18:46:50 CDT." <199510242346.SAA13180@sunc210.tellabs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>The following is Solaris snoop output which shows the problem. TOYBOX >is running 2.1.0-951020-SNAP and TELLABK (aka SUNK) is a multi-homed >server running SunOS 4.1.3 and "routed -q". First we do the mount: > ># mount tellabk:/export/home/tellabk-4 /usr/home > > toybox -> tellabk PORTMAP C GETPORT prog=100003 (NFS) vers=2 proto=UDP > sunk -> toybox PORTMAP R GETPORT port=2049 > toybox -> tellabk PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=UDP > sunk -> toybox PORTMAP R GETPORT port=737 > toybox -> tellabk MOUNT C Mount /export/home/tellabk-4 > sunk -> toybox MOUNT R Mount OK F=075B > >Looks like the mount completed OK, even though the replies came from SUNK, >TELLABK's alter-ego. So let's do a "df": Yeah, that's the problem. This doesn't look like a FreeBSD problem to me - it looks like the Sun is replying out a different interface then it received the mount request from. FreeBSD rightfully thinks this is crap coming from some irrelevant machine. I think you should be able to work around it by using the name/address of "sunk" when doing the mount. -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510250117.SAA27638>