Please consider some of the following minor changes for faq/pf. I have
several other changes too but need to submit them later.
- add reference to sysctl(8)
- add comma
- use "or" instead of /
- spell out digits in text
- For the scrub.html change below, see pf.conf.5 revision 1.302:
"'random-id' no longer applies only to outgoing packets."
- spell out left angle and right angle brackets
RCS file: /cvs/www/faq/pf/example1.html,v
retrieving revision 1.21
diff -b -u -r1.21 example1.html
--- faq/pf/example1.html 1 Nov 2005 11:35:18 -0000 1.21
+++ faq/pf/example1.html 4 Jan 2006 06:19:14 -0000
@@ -132,7 +132,9 @@
This document assumes that the OpenBSD host has been properly configured
to act as a router, including verifying IP networking setup, Internet
-connectivity, and setting <tt>net.inet.ip.forwarding</tt> to "<tt>1</tt>".
+connectivity, and setting
+variable <tt>net.inet.ip.forwarding</tt> to "<tt>1</tt>".
RCS file: /cvs/www/faq/pf/filter.html,v
retrieving revision 1.34
diff -b -u -r1.34 filter.html
--- faq/pf/filter.html 28 Dec 2005 17:11:25 -0000 1.34
+++ faq/pf/filter.html 4 Jan 2006 06:19:18 -0000
@@ -697,7 +697,7 @@
<h2>TCP SYN Proxy</h2>
-Normally when a client initiates a TCP connection to a server PF will
+Normally when a client initiates a TCP connection to a server, PF will
>handshake</a> packets between the two endpoints as they arrive.
RCS file: /cvs/www/faq/pf/logging.html,v
retrieving revision 1.25
diff -b -u -r1.25 logging.html
--- faq/pf/logging.html 28 Dec 2005 17:12:26 -0000 1.25
+++ faq/pf/logging.html 4 Jan 2006 06:19:19 -0000
@@ -96,7 +96,7 @@
<dd>Causes the UNIX user-id and group-id that owns the socket that the
-packet is sourced from/destined to (whichever socket is local) to be
+packet is sourced from or destined to (whichever socket is local) to be
logged along with the standard log information.
@@ -374,7 +374,7 @@
PF will now log in ASCII to <tt>/var/log/pflog.txt</tt>. If so
configured in <tt>/etc/syslog.conf</tt>, it will also log to a remote
-server. The logging is not immediate but it can take up to about 5-6
+server. The logging is not immediate but it can take up to about five to six
minutes (the cron job interval) before the logged packets appear in the
<dd>Replaces the IP identification field of
-outgoing packets with random values to compensate for operating systems
-that use predictable values. This option only applies to outgoing
+packets with random values to compensate for operating systems
+that use predictable values. This option only applies to
packets that are not fragmented after the optional packet reassembly.