From owner-freebsd-stable  Sun Jun 30 09:07:04 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA23875
          for stable-outgoing; Sun, 30 Jun 1996 09:07:04 -0700 (PDT)
Received: from central.picker.com (central.picker.com [144.54.31.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA23859
          for <stable@freebsd.org>; Sun, 30 Jun 1996 09:07:01 -0700 (PDT)
Received: from ct.picker.com by central.picker.com with smtp
	(Smail3.1.28.1 #3) id m0uaOxb-0004rmC; Sun, 30 Jun 96 12:02 EDT
Received: from elmer.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA27545; Sun, 30 Jun 96 12:02:20 EDT
Received: by elmer.picker.com (SMI-8.6/SMI-SVR4)
	id MAA19202; Sun, 30 Jun 1996 12:03:51 -0400
From: rhh@ct.picker.com (Randall Hopper)
Message-Id: <199606301603.MAA19202@elmer.picker.com>
Subject: 960627-SNAP - Problem with IPFirewall/portmap
To: stable@freebsd.org
Date: Sun, 30 Jun 1996 12:03:50 -0400 (EDT)
Reply-To: rhh@ct.picker.com
Organization:  Picker International, CT Division
X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

     Just installed the 2.1-960627-SNAP, and ran into a system hang-up with
it.  I spent some time narrowing this down, it appears that the presence of
the IPFIREWALL option causes portmap to refuse connections.  rpcinfo -p
just prints an error, and amd can't register with portmap.  This leaves the
kernel in a somewhat strange state on amd's exit, and causes hang-ups when
accessing automount directories.

     Jun 29 16:45:19 stealth amd[98]/fatal: unable to register
     (AMQ_PROGRAM, AMQ_VERSION, udp)

     The GENERIC kernel works fine of course, since it doesn't have
IPFIREWALL built in.

     Without IPFIREWALL, rpcinfo -p behaves as expected, and amd starts up
and works fine.

     I actually haven't ever used IPFIREWALL -- I just pulled over my
2.1-RELEASE config file and tailored it based on the latest LINT.  It's one
of those things I put in to play with later, and adding it didn't cause any
problems with 2.1-RELEASE.  For now, I'll just remove it but I'm curious as
to whether this is a bug or something I don't have set up correctly.

Thanks,

Randall Hopper
rhh@ct.picker.com