Add an entry explaining the ``Permission denied'' message associated

with enabling IPFIREWALL.
This commit is contained in:
Alexander Langer 1996-07-07 22:09:24 +00:00
parent 92e6163cd6
commit 2563c5d015
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=409

View file

@ -4,7 +4,7 @@
<title>Frequently Asked Questions for FreeBSD 2.X <title>Frequently Asked Questions for FreeBSD 2.X
<author>The FreeBSD FAQ Team, <tt/FAQ@FreeBSD.ORG/ <author>The FreeBSD FAQ Team, <tt/FAQ@FreeBSD.ORG/
<date> $Id: freebsd-faq.sgml,v 1.47 1996-07-06 14:39:56 joerg Exp $ <date> $Id: freebsd-faq.sgml,v 1.48 1996-07-07 22:09:24 alex Exp $
<abstract> <abstract>
This is the FAQ for FreeBSD systems version 2.X All entries are This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted. assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted.
@ -2641,6 +2641,28 @@ domain foo.bar.edu
</sect1> </sect1>
<sect1>
<heading>I just booted a new kernel and now I'm getting ``Permission denied'' for all networking operations.</heading>
<p>
If you have compiled your kernel with the <tt/IPFIREWALL/
option, you need to be aware that the default policy as of
2.1.5R (this actually changed during 2.1-STABLE development)
is to deny all packets that are not explicitly allowed.
<p>
If you had unintentionally misconfigured your system for
firewalling, you can restore network operability by typing
the following while logged in as root:
<verb>
ipfw add 65534 allow all from any to any
</verb>
For further information on configuring a FreeBSD firewall,
see the <url url="http://www.freebsd.org/handbook/handbook.html" name="FreeBSD Handbook.">
</sect1>
<sect> <sect>
<heading>Serial Communications</heading> <heading>Serial Communications</heading>
<p> <p>