From owner-freebsd-questions  Thu Apr 16 08:55:34 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA02652
          for freebsd-questions-outgoing; Thu, 16 Apr 1998 08:55:34 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from garnet.dgms.com (pc-algier-p.dgms.com [206.67.30.153])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02646
          for <freebsd-questions@freebsd.org>; Thu, 16 Apr 1998 15:55:23 GMT
          (envelope-from gaa@dgms.com)
Received: from dgms.com (localhost [127.0.0.1])
	by garnet.dgms.com (8.8.8/8.8.8) with ESMTP id MAA01766
	for <freebsd-questions@freebsd.org>; Thu, 16 Apr 1998 12:54:23 -0400 (EDT)
	(envelope-from gaa@dgms.com)
Message-ID: <353637BF.DF7FA19E@dgms.com>
Date: Thu, 16 Apr 1998 12:54:23 -0400
From: Gary Algier <gaa@dgms.com>
X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386)
MIME-Version: 1.0
To: freebsd-questions@FreeBSD.ORG
Subject: Who's Broken: Sun or FreeBSD?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have FreeBSD 2.2.6 running on my desktop machine here at work.  It is
on one of the two subnets and I am trying to nfs mount our file server
and it hangs forever.  (FreeBSD can't even reboot.  It hangs right after
syncing the disks.)  I ran tcpdump & tcpshow and found out that someone
is messed up: either Sun or FreeBSD.

A few (faked to protect the guilty) details:
    Client:
	Hostname:	client
	OS:		FreeBSD 2.2.6
	IP1:		192.168.2.10 (client)
    Server:
	Hostame:	server
	IP1:		192.168.1.1 (server)
	IP2:		192.168.2.1 (xxx-server)
	Yes, the server is also configured to forward.  It is our "router".

If I mount with:
	mount xxx-server:/home /mnt
It works just fine.When I try to mount with:
	mount server:/home /mnt
It hangs forever.

By looking at the packets I can see the following conversation:
	Source ip/port		Dest ip/port
	192.168.2.10/971	192.168.1.1/111 	portmapper request
	192.168.2.1/111		192.168.2.10/971	portmapper reply
This goes on forever.

It looks like the sun is replying using the wrong interface ip address
and freebsd is ignoring it.

Who is wrong?  (I think Sun) How do I get it fixed?  How do I get
freebsd to accept the bad data?  Hummingbird NFS on the NT PCs here
works just fine with bad responses.

Using the "xxx-server" name is not a good option.  I am trying to use amd
and it can't differentiate when someone types "ls /h/server/home/me".

-- 
Gary Algier, WB2FWZ       gary.algier@dgms.com              +1 609 608 2758
DGM&S Telecom, 1025 Briggs Rd, Mt. Laurel, NJ 08054     Fax:+1 609 866 8850
        Paul Petzoldt on the renaming of Mount Washington:
"I Call it the New England Booby Trap.  We see Ph.D.'s from private schools
taking kids up there in shorts.  People die like flies up there!"

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