Date: Sun, 30 Jun 1996 20:08:45 +0100 From: Gary Palmer <gpalmer@FreeBSD.ORG> To: rhh@ct.picker.com Cc: stable@FreeBSD.ORG Subject: Re: 960627-SNAP - Problem with IPFirewall/portmap Message-ID: <11632.836161725@palmer.demon.co.uk> In-Reply-To: Your message of "Sun, 30 Jun 1996 12:03:50 EDT." <199606301603.MAA19202@elmer.picker.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Randall Hopper wrote in message ID
<199606301603.MAA19202@elmer.picker.com>:
> 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.
This is the defined behaviour of the IPFIREWALL code. Recent versions
have a ``deny everything by default'' behaviour, which even stops
ifconfig from working. IMHO, although being the right choice, it's a
pain in the proverbials, and also breaks diskless booting if the
kernel you are booting has IPFIREWALL in it.
Solution: change the IPFIREWALL rules before you try doing ANYTHING
else with the networking subsystem.
Gary
--
Gary Palmer FreeBSD Core Team Member
FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11632.836161725>