The PF User's Guide still refers to 5.5 in web-manual-page URLs and
in the text in the last paragraph of index.html.  (In fact, that last
paragraph also still refers to 5.4.)

Here's a suggested patch to change all of these to 5.6:

Index: anchors.html
===================================================================
RCS file: /cvs/www/faq/pf/anchors.html,v
retrieving revision 1.37
diff -u -r1.37 anchors.html
--- anchors.html        1 May 2014 15:03:50 -0000       1.37
+++ anchors.html        23 Nov 2014 00:51:30 -0000
@@ -58,7 +58,7 @@
 <h2>Introduction</h2>
 In addition to the main ruleset, PF can also evaluate sub rulesets.
 Since sub rulesets can be manipulated on the fly by using 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a>, they provide a convenient way of dynamically
 altering an active ruleset.
 Whereas a <a href="tables.html">table</a> is used to hold a dynamic
@@ -110,7 +110,7 @@
 <ul>
 <li>using a <tt>load</tt> rule
 <li>using 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a>
 <li>specifying the rules inline of the main ruleset
 </ul>
@@ -215,7 +215,7 @@
 point from the main ruleset does not destroy the anchor or any child
 anchors that are attached to that anchor. An anchor is not
 destroyed until it's flushed of all rules using
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> and there are no child anchors within the anchor. 
 
 <a name="options"></a>
@@ -293,7 +293,7 @@
 
 <p>
 For a full list of commands, please see
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a>.
 
 <p>
Index: authpf.html
===================================================================
RCS file: /cvs/www/faq/pf/authpf.html,v
retrieving revision 1.37
diff -u -r1.37 authpf.html
--- authpf.html 30 Jul 2014 21:57:19 -0000      1.37
+++ authpf.html 23 Nov 2014 00:51:30 -0000
@@ -64,7 +64,7 @@
 
 <a name="intro"></a>
 <h2>Introduction</h2>
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=authpf&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=authpf&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >Authpf(8)</a> is a user shell for authenticating gateways. An
 authenticating gateway is just like a regular network gateway (a.k.a. a
 router) except that users must first authenticate themselves to the
@@ -76,7 +76,7 @@
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=csh&amp;sektion=1";
 >csh(1)</a>, etc) and the user logs in using SSH, authpf will make the
 necessary changes to the active  
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pf(4)</a> ruleset so that the user's traffic is passed through the
 filter and/or translated using Network Address Translation or
 redirection. Once the user logs out or their session is disconnected,
@@ -136,7 +136,7 @@
 <h2>Configuration</h2>
 The basic steps needed to configure authpf are outlined here. For a
 complete description of authpf configuration, please refer to the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=authpf&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=authpf&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >authpf man page</a>.
 
 <a name="enable"></a>
Index: carp.html
===================================================================
RCS file: /cvs/www/faq/pf/carp.html,v
retrieving revision 1.37
diff -u -r1.37 carp.html
--- carp.html   1 May 2014 15:03:50 -0000       1.37
+++ carp.html   23 Nov 2014 00:51:31 -0000
@@ -141,7 +141,7 @@
 <a name="carpconfig"></a>
 <h2>Configuring CARP</h2>
 Each redundancy group is represented by a
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=carp&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=carp&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >carp(4)</a> virtual network interface. As such, CARP is configured
 using
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ifconfig&amp;sektion=8";
@@ -296,9 +296,9 @@
 <a name="pfsyncintro"></a>
 <h2>Introduction to pfsync</h2>
 The
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfsync&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfsync&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pfsync(4)</a> network interface exposes certain changes made to the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pf(4)</a> state table.
 By monitoring this device using
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=tcpdump&amp;sektion=8";
@@ -715,10 +715,10 @@
 
 <ul>
 <li>
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=carp&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=carp&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >carp(4)</a>
 <li>
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfsync&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfsync&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pfsync(4)</a>
 <li>
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ifconfig&amp;sektion=8";
@@ -727,7 +727,7 @@
 <a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=hostname.if&amp;sektion=5";
 >hostname.if(5)</a>
 <li>
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.6";
 >pf.conf(5)</a>
 <li>
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ifstated&amp;sektion=8";
Index: config.html
===================================================================
RCS file: /cvs/www/faq/pf/config.html,v
retrieving revision 1.41
diff -u -r1.41 config.html
--- config.html 1 May 2014 15:03:50 -0000       1.41
+++ config.html 23 Nov 2014 00:51:31 -0000
@@ -67,7 +67,7 @@
 
 <p>
 You can also manually activate and deactivate PF by using the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> program:
 
 <blockquote>
@@ -88,18 +88,18 @@
 <h2>Configuration</h2>
 <p>
 PF reads its configuration rules from 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.6";
 ><tt>/etc/pf.conf</tt></a> at boot
 time, as loaded by the
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rc&amp;sektion=8";
 >rc scripts</a>.  Note that while 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.6";
 ><tt>/etc/pf.conf</tt></a> is the default and is
 loaded by the system rc scripts, it is just a text file loaded and interpreted
 by 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> and inserted into
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pf(4)</a>.  For some applications, other rulesets may be loaded from other
 files after boot.  As with any well designed Unix application, PF offers great
 flexibility.
@@ -130,7 +130,7 @@
 <a name="control"></a>
 <h2>Control</h2>
 After boot, PF operation can be managed using the 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> program.  Some example commands are:
 
 <pre>
@@ -145,7 +145,7 @@
 
 <p>
 For a complete list of commands, please see the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8) man page</a>.
 
 <p>
Index: example1.html
===================================================================
RCS file: /cvs/www/faq/pf/example1.html,v
retrieving revision 1.56
diff -u -r1.56 example1.html
--- example1.html       1 May 2014 15:03:50 -0000       1.56
+++ example1.html       23 Nov 2014 00:51:31 -0000
@@ -134,7 +134,7 @@
 >sysctl(3)</a> variables <tt>net.inet.ip.forwarding</tt> and/or 
 <tt>net.inet6.ip6.forwarding</tt> to "<tt>1</tt>".
 You must also have enabled PF using 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> or by setting the appropriate variable in
 <tt>/etc/rc.conf.local</tt>.
 PF is enabled by default on OpenBSD 4.6 and newer releases.
@@ -211,7 +211,7 @@
 <h3>Firewall Rules</h3>
 
 We will start with rules to support the use of
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >ftp-proxy(8)</a> so that FTP clients on the local network can
 connect to FTP servers on the Internet.
 This works by dynamically inserting rules when an ftp connection
@@ -240,7 +240,7 @@
 
 <p>
 Note that both the <a href="anchors.html">anchor</a> and the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >ftp-proxy(8)</a> divert rule need to be located before any
 <tt>match</tt> rules for NAT or the ftp-proxy(8) will not work
 as expected.
Index: filter.html
===================================================================
RCS file: /cvs/www/faq/pf/filter.html,v
retrieving revision 1.70
diff -u -r1.70 filter.html
--- filter.html 1 May 2014 15:03:50 -0000       1.70
+++ filter.html 23 Nov 2014 00:51:31 -0000
@@ -67,7 +67,7 @@
 <h2>Introduction</h2>
 Packet filtering is the selective passing or blocking of data
 packets as they pass through a network interface. The criteria that 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pf(4)</a> uses when inspecting packets are based on the Layer 3 
 (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ip&amp;sektion=4";
 >IPv4</a> and 
@@ -124,7 +124,7 @@
 
 <dt><tt>log</tt>
 <dd>Specifies that the packet should be logged via
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pflogd(8)</a>. If the rule creates state then only the
 packet which establishes the state is logged. 
 To log all packets regardless, use <tt>log (all)</tt>.
@@ -768,7 +768,7 @@
 <dl>
 <dt><tt>log</tt>
 <dd>Specifies that matching packets should be logged via
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pflogd(8)</a>.
 
 <dt><tt>quick</tt>
@@ -895,7 +895,7 @@
 <a href="options.html#fingerprints">fingerprints file</a>, which by
 default is 
 <a
-href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.os&amp;sektion=5&amp;manpath=OpenBSD+5.5";
+href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.os&amp;sektion=5&amp;manpath=OpenBSD+5.6";
 ><tt>/etc/pf.os</tt></a>. 
 Once PF is enabled, the current fingerprint list can be viewed with this
 command:
Index: ftp.html
===================================================================
RCS file: /cvs/www/faq/pf/ftp.html,v
retrieving revision 1.42
diff -u -r1.42 ftp.html
--- ftp.html    24 Jun 2014 13:42:23 -0000      1.42
+++ ftp.html    23 Nov 2014 00:51:31 -0000
@@ -113,7 +113,7 @@
 rules to PF system and removing them when done, by means of the PF
 <a href="anchors.html">anchors</a> system. 
 The FTP proxy used by PF is
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=ftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >ftp-proxy(8)</a>.
 
 <p>
@@ -261,7 +261,7 @@
 Trivial File Transfer Protocol (TFTP) suffers from some of the same
 limitations as FTP does when it comes to passing through a firewall.
 Luckily, PF has a helper proxy for TFTP called
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=tftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=tftp-proxy&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >tftp-proxy(8)</a>.
 
 <p>
Index: index.html
===================================================================
RCS file: /cvs/www/faq/pf/index.html,v
retrieving revision 1.65
diff -u -r1.65 index.html
--- index.html  1 May 2014 15:03:50 -0000       1.65
+++ index.html  23 Nov 2014 00:51:31 -0000
@@ -105,20 +105,20 @@
 <p>
 For a complete and in-depth view of what PF can do, please start by
 reading the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pf(4)</a> man page.
 
 <p>
 As with the rest of the FAQ, this set of documents is focused on users of
-<a href="../../55.html">OpenBSD 5.5</a>.
+<a href="../../56.html">OpenBSD 5.6</a>.
 As PF is always growing and developing, there are changes and
 enhancements between the
-5.4-release
+5.6-release
 version and the version in
 <a href="../../plus.html">OpenBSD-current</a>
 as well as differences
 between
-5.4 
+5.6 
 and earlier versions.
 The reader is advised to see the man pages for the version of OpenBSD
 they are currently working with.
Index: logging.html
===================================================================
RCS file: /cvs/www/faq/pf/logging.html,v
retrieving revision 1.51
diff -u -r1.51 logging.html
--- logging.html        1 May 2014 15:03:50 -0000       1.51
+++ logging.html        23 Nov 2014 00:51:31 -0000
@@ -58,14 +58,14 @@
 <a name="intro"></a>
 <h2>Introduction</h2>
 When a packet is logged by PF, a copy of the packet header is sent to a
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflog&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflog&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pflog(4)</a> interface along with some additional data such as the
 interface the packet was transiting, the action that PF took (pass or
 block), etc.
 The pflog(4) interface allows user-space applications to receive PF's
 logging data from the kernel.
 If PF is enabled when the system is booted, the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pflogd(8)</a> daemon is started.
 By default pflogd(8) listens on the <tt>pflog0</tt> interface and writes
 all logged data to the <tt>/var/log/pflog</tt> file.
Index: macros.html
===================================================================
RCS file: /cvs/www/faq/pf/macros.html,v
retrieving revision 1.35
diff -u -r1.35 macros.html
--- macros.html 1 May 2014 15:03:50 -0000       1.35
+++ macros.html 23 Nov 2014 00:51:31 -0000
@@ -61,7 +61,7 @@
 
 <p>
 When
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> encounters a list during loading of the ruleset, it
 creates multiple rules, one for each item in the list. For example:
 <blockquote>
Index: nat.html
===================================================================
RCS file: /cvs/www/faq/pf/nat.html,v
retrieving revision 1.49
diff -u -r1.49 nat.html
--- nat.html    30 Jul 2014 21:57:19 -0000      1.49
+++ nat.html    23 Nov 2014 00:51:31 -0000
@@ -219,7 +219,7 @@
 
 <dt><tt>log</tt>
 <dd>Log matching packets via
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pflogd&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pflogd(8)</a>.
 Normally only the first packet that matches will be logged.
 To log all matching packets, use <tt>log (all)</tt>.
@@ -467,7 +467,7 @@
 <a name="status"></a>
 <h2>Checking NAT Status</h2>
 To view the active NAT translations
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> is used with the <tt>-s state</tt> option. This option will list
 all the current NAT sessions:
 
Index: options.html
===================================================================
RCS file: /cvs/www/faq/pf/options.html,v
retrieving revision 1.32
diff -u -r1.32 options.html
--- options.html        1 May 2014 15:03:50 -0000       1.32
+++ options.html        23 Nov 2014 00:51:31 -0000
@@ -168,7 +168,7 @@
 </ul>
 <dd>Starting in OpenBSD 4.2, the default is <tt>basic</tt>.
 See
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.6";
 >pf.conf(5)</a> for a more complete description.
 </dl>
 
Index: pools.html
===================================================================
RCS file: /cvs/www/faq/pf/pools.html,v
retrieving revision 1.39
diff -u -r1.39 pools.html
--- pools.html  30 Jul 2014 21:57:19 -0000      1.39
+++ pools.html  23 Nov 2014 00:51:31 -0000
@@ -84,7 +84,7 @@
 The key that is fed to the hashing algorithm can optionally be specified
 after the <tt>source-hash</tt> keyword in hex format or as a string. By
 default,
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> will generate a random key every time the ruleset is
 loaded.
 <li><tt>round-robin</tt> - loops through the address pool in
Index: queueing.html
===================================================================
RCS file: /cvs/www/faq/pf/queueing.html,v
retrieving revision 1.49
diff -u -r1.49 queueing.html
--- queueing.html       15 May 2014 16:06:49 -0000      1.49
+++ queueing.html       23 Nov 2014 00:51:31 -0000
@@ -68,7 +68,7 @@
 remain unchanged, but actual queue configuration ("altq ..." and
 "oldqueue ... bandwidth" lines) will be replaced.
 Until this page can be updated, please see
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.5";>pf.conf(5)</a>
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.6";>pf.conf(5)</a>
 for current information.<p>
 
 <a name="queueing"></a>
@@ -353,7 +353,7 @@
 
 <p>
 Queueing is configured in <tt>
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.6";
 >pf.conf</a></tt>. There are two types of directives that are used
 to configure queueing:
 <ul>
Index: shortcuts.html
===================================================================
RCS file: /cvs/www/faq/pf/shortcuts.html,v
retrieving revision 1.36
diff -u -r1.36 shortcuts.html
--- shortcuts.html      30 Jul 2014 21:57:19 -0000      1.36
+++ shortcuts.html      23 Nov 2014 00:51:31 -0000
@@ -171,7 +171,7 @@
 <p>
 Note that macros and lists simplify the <tt>pf.conf</tt> file, but
 the lines are actually expanded by 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> into multiple rules.  So, the above example actually
 expands to the following rules:
 <blockquote>
@@ -191,7 +191,7 @@
 As you can see, the PF expansion is purely a convenience for the writer
 and maintainer of the <tt>pf.conf</tt> file, not an actual
 simplification of the rules processed by 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4&amp;manpath=OpenBSD+5.6";
 >pf(4)</a>.
 
 <p>
Index: tables.html
===================================================================
RCS file: /cvs/www/faq/pf/tables.html,v
retrieving revision 1.38
diff -u -r1.38 tables.html
--- tables.html 30 Jul 2014 21:57:19 -0000      1.38
+++ tables.html 23 Nov 2014 00:51:31 -0000
@@ -72,9 +72,9 @@
 
 <p>
 Tables are created either in 
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf.conf&amp;sektion=5&amp;manpath=OpenBSD+5.6";
 ><tt>pf.conf</tt></a> or by using
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a>.
 
 <a name="config"></a>
@@ -84,7 +84,7 @@
 <ul>
 <li><tt>const</tt> - the contents of the table cannot be changed once the
 table is created. When this attribute is not specified,
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> may be used to add or remove addresses from the
 table at any time, even when running with a
 <a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=securelevel&amp;sektion=7";
@@ -145,7 +145,7 @@
 <a name="manip"></a>
 <h2>Manipulating with <tt>pfctl</tt></h2>
 Tables can be manipulated on the fly by using
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a>. For
 instance, to add entries to the &lt;spammers&gt; table created above:
 <blockquote>
@@ -170,7 +170,7 @@
 <p>
 For more information on manipulating tables with <tt>pfctl</tt>,
 please read the
-<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.5";
+<a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&amp;sektion=8&amp;manpath=OpenBSD+5.6";
 >pfctl(8)</a> manpage.
 
 <a name="addr"></a>



-- 
-- "Jonathan Thornburg [remove -animal to reply]" 
<jth...@astro.indiana-zebra.edu>
   Dept of Astronomy & IUCSS, Indiana University, Bloomington, Indiana, USA
   "There was of course no way of knowing whether you were being watched
    at any given moment.  How often, or on what system, the Thought Police
    plugged in on any individual wire was guesswork.  It was even conceivable
    that they watched everybody all the time."  -- George Orwell, "1984"

Reply via email to