xref: /freebsd/sbin/pfctl/pfctl.8 (revision a259b98fa211ed87bfee58c575de4e2de94ee0fa)
1.\" $OpenBSD: pfctl.8,v 1.138 2008/06/10 20:55:02 mcbride Exp $
2.\"
3.\" Copyright (c) 2001 Kjell Wooding.  All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\"    notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\" 3. The name of the author may not be used to endorse or promote products
14.\"    derived from this software without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
17.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
18.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
19.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
20.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
21.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
22.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
23.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
24.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
25.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
26.\"
27.Dd April 20, 2026
28.Dt PFCTL 8
29.Os
30.Sh NAME
31.Nm pfctl
32.Nd control the packet filter device
33.Sh SYNOPSIS
34.Nm pfctl
35.Bk -words
36.Op Fl AdeghMmNnOPqRrvz
37.Op Fl a Ar anchor
38.Oo Fl D Ar macro Ns =
39.Ar value Oc
40.Op Fl F Ar modifier
41.Op Fl f Ar file
42.Op Fl i Ar interface
43.Op Fl K Ar host | network
44.Xo
45.Oo Fl k
46.Ar host | network | label | id | gateway | source | nat
47.Oc Xc
48.Op Fl o Ar level
49.Op Fl p Ar device
50.Op Fl s Ar modifier
51.Xo
52.Oo Fl t Ar table
53.Fl T Ar command
54.Op Ar address ...
55.Oc Xc
56.Op Fl x Ar level
57.Ek
58.Sh DESCRIPTION
59The
60.Nm
61utility communicates with the packet filter device using the
62ioctl interface described in
63.Xr pf 4 .
64It allows ruleset and parameter configuration and retrieval of status
65information from the packet filter.
66.Pp
67Packet filtering restricts the types of packets that pass through
68network interfaces entering or leaving the host based on filter
69rules as described in
70.Xr pf.conf 5 .
71The packet filter can also replace addresses and ports of packets.
72Replacing source addresses and ports of outgoing packets is called
73NAT (Network Address Translation) and is used to connect an internal
74network (usually reserved address space) to an external one (the
75Internet) by making all connections to external hosts appear to
76come from the gateway.
77Replacing destination addresses and ports of incoming packets
78is used to redirect connections to different hosts and/or ports.
79A combination of both translations, bidirectional NAT, is also
80supported.
81Translation rules are described in
82.Xr pf.conf 5 .
83.Pp
84When the variable
85.Va pf_enable
86is set to
87.Dv YES
88in
89.Xr rc.conf 5 ,
90the rule file specified with the variable
91.Va pf_rules
92is loaded automatically by the
93.Xr rc 8
94scripts and the packet filter is enabled.
95.Pp
96The packet filter does not itself forward packets between interfaces.
97Forwarding can be enabled by setting the
98.Xr sysctl 8
99variables
100.Em net.inet.ip.forwarding
101and/or
102.Em net.inet6.ip6.forwarding
103to 1.
104Set them permanently in
105.Xr sysctl.conf 5 .
106.Pp
107At least one option must be specified.
108The options are as follows:
109.Bl -tag -width Ds
110.It Fl A
111Load only the queue rules present in the rule file.
112Other rules and options are ignored.
113Can be combined with the
114.Fl N ,
115.Fl O ,
116and
117.Fl R
118flags to load multiple rule types without (re)loading all rules.
119.It Fl a Ar anchor
120Apply flags
121.Fl f ,
122.Fl F ,
123.Fl s ,
124.Fl T ,
125and
126.Fl z
127only to the rules in the specified
128.Ar anchor .
129In addition to the main ruleset,
130.Nm
131can load and manipulate additional rulesets by name,
132called anchors.
133The main ruleset is the default anchor.
134.Pp
135Anchors are referenced by name and may be nested,
136with the various components of the anchor path separated by
137.Sq /
138characters, similar to how file system hierarchies are laid out.
139The last component of the anchor path is where ruleset operations are
140performed.
141.Pp
142Evaluation of
143.Ar anchor
144rules from the main ruleset is described in
145.Xr pf.conf 5 .
146.Pp
147For example, the following will show all filter rules (see the
148.Fl s
149flag below) inside the anchor
150.Dq authpf/smith(1234) ,
151which would have been created for user
152.Dq smith
153by
154.Xr authpf 8 ,
155PID 1234:
156.Bd -literal -offset indent
157# pfctl -a "authpf/smith(1234)" -s rules
158.Ed
159.Pp
160Private tables can also be put inside anchors, either by having table
161statements in the
162.Xr pf.conf 5
163file that is loaded in the anchor, or by using regular table commands, as in:
164.Bd -literal -offset indent
165# pfctl -a foo/bar -t mytable -T add 1.2.3.4 5.6.7.8
166.Ed
167.Pp
168When a rule referring to a table is loaded in an anchor, the rule will use the
169private table if one is defined, and then fall back to the table defined in the
170main ruleset, if there is one.
171This is similar to C rules for variable scope.
172It is possible to create distinct tables with the same name in the global
173ruleset and in an anchor, but this is often bad design and a warning will be
174issued in that case.
175.Pp
176By default, recursive inline printing of anchors applies only to unnamed
177anchors specified inline in the ruleset.
178If the anchor name is terminated with a
179.Sq *
180character, the
181.Fl s
182flag will recursively print all anchors in a brace delimited block.
183For example the following will print the
184.Dq authpf
185ruleset recursively:
186.Bd -literal -offset indent
187# pfctl -a 'authpf/*' -sr
188.Ed
189.Pp
190To print the main ruleset recursively, specify only
191.Sq *
192as the anchor name:
193.Bd -literal -offset indent
194# pfctl -a '*' -sr
195.Ed
196.Pp
197To flush all rulesets and tables recursively, specify only
198.Sq *
199as the anchor name:
200.Bd -literal -offset indent
201# pfctl -a '*' -Fa
202.Ed
203.It Fl D Ar macro Ns = Ns Ar value
204Define
205.Ar macro
206to be set to
207.Ar value
208on the command line.
209Overrides the definition of
210.Ar macro
211in the ruleset.
212.It Fl d
213Disable the packet filter.
214.It Fl e
215Enable the packet filter.
216.It Fl F Ar modifier
217Flush the filter parameters specified by
218.Ar modifier
219(may be abbreviated):
220.Pp
221.Bl -tag -width xxxxxxxxx -compact
222.It Cm nat
223Flush the NAT rules.
224.It Cm queue
225Flush the queue rules.
226.It Cm ethernet
227Flush the Ethernet filter rules.
228.It Cm rules
229Flush the filter rules.
230.It Cm states
231Flush the state table (NAT and filter).
232.It Cm Sources
233Flush the source tracking table.
234.It Cm info
235Flush the filter information (statistics that are not bound to rules).
236.It Cm Tables
237Flush the tables.
238.It Cm osfp
239Flush the passive operating system fingerprints.
240.It Cm Reset
241Reset limits, timeouts and other options back to default settings.
242See the OPTIONS section in
243.Xr pf.conf 5
244for details.
245.It Cm all
246Flush all of the above.
247.El
248.Pp
249If
250.Fl a
251is specified as well and
252.Ar anchor
253is terminated with a
254.Sq *
255character,
256.Cm rules ,
257.Cm Tables
258and
259.Cm all
260flush the given anchor recursively.
261.It Fl f Ar file
262Load the rules contained in
263.Ar file .
264This
265.Ar file
266may contain macros, tables, options, and normalization, queueing,
267translation, and filtering rules.
268With the exception of macros and tables, the statements must appear in that
269order.
270.It Fl g
271Include output helpful for debugging.
272.It Fl h
273Help.
274.It Fl i Ar interface
275Restrict the operation to the given
276.Ar interface .
277.It Fl K Ar host | network
278Kill all of the source tracking entries originating from the specified
279.Ar host
280or
281.Ar network .
282A second
283.Fl K Ar host
284or
285.Fl K Ar network
286option may be specified, which will kill all the source tracking
287entries from the first host/network to the second.
288.It Xo
289.Fl k
290.Ar host | network | label | id | key | gateway | source | nat
291.Xc
292Kill all of the state entries matching the specified
293.Ar host ,
294.Ar network ,
295.Ar label ,
296.Ar id ,
297.Ar key ,
298.Ar gateway,
299.Ar source ,
300or
301.Ar nat.
302.Pp
303For example, to kill all of the state entries originating from
304.Dq host :
305.Pp
306.Dl # pfctl -k host
307.Pp
308A second
309.Fl k Ar host
310or
311.Fl k Ar network
312option may be specified, which will kill all the state entries
313from the first host/network to the second.
314To kill all of the state entries from
315.Dq host1
316to
317.Dq host2 :
318.Pp
319.Dl # pfctl -k host1 -k host2
320.Pp
321To kill all states originating from 192.168.1.0/24 to 172.16.0.0/16:
322.Pp
323.Dl # pfctl -k 192.168.1.0/24 -k 172.16.0.0/16
324.Pp
325A network prefix length of 0 can be used as a wildcard.
326To kill all states with the target
327.Dq host2 :
328.Pp
329.Dl # pfctl -k 0.0.0.0/0 -k host2
330.Pp
331It is also possible to kill states by rule label, state key or state ID.
332In this mode the first
333.Fl k
334argument is used to specify the type
335of the second argument.
336The following command would kill all states that have been created
337from rules carrying the label
338.Dq foobar :
339.Pp
340.Dl # pfctl -k label -k foobar
341.Pp
342To kill one specific state by its key
343(protocol, host1, port1, direction, host2 and port2 in the same format
344of pfctl -s state),
345use the
346.Ar key
347modifier and as a second argument the state key.
348To kill a state whose protocol is TCP and originating from
34910.0.0.101:32123 to 10.0.0.1:80 use:
350.Pp
351.Dl # pfctl -k key -k 'tcp 10.0.0.1:80 <- 10.0.0.101:32123'
352.Pp
353To kill one specific state by its unique state ID
354(as shown by pfctl -s state -vv),
355use the
356.Ar id
357modifier and as a second argument the state ID and optional creator ID.
358To kill a state with ID 4823e84500000003 use:
359.Pp
360.Dl # pfctl -k id -k 4823e84500000003
361.Pp
362To kill a state with ID 4823e84500000018 created from a backup
363firewall with hostid 00000002 use:
364.Pp
365.Dl # pfctl -k id -k 4823e84500000018/2
366.Pp
367It is also possible to kill states created from a rule with the route-to/reply-to
368parameter set to route the connection through a particular gateway.
369Note that rules routing via the default routing table (not via a route-to
370rule) will have their rt_addr set as 0.0.0.0 or ::.
371To kill all states using a gateway of 192.168.0.1 use:
372.Pp
373.Dl # pfctl -k gateway -k 192.168.0.1
374.Pp
375A network prefix length can also be specified.
376To kill all states using a gateway in 192.168.0.0/24:
377.Pp
378.Dl # pfctl -k gateway -k 192.168.0.0/24
379.Pp
380States can also be killed based on their pre-NAT address:
381.Pp
382.Dl # pfctl -k nat -k 192.168.0.1
383.Pp
384To remove a source from a source limiter use:
385.Pp
386.Dl # pfctl -I 1 -k source -k 192.0.2.2
387.Pp
388.It Fl M
389Kill matching states in the opposite direction (on other interfaces) when
390killing states.
391This applies to states killed using the -k option and also will apply to the
392flush command when flushing states.
393This is useful when an interface is specified when flushing states.
394Example:
395.Pp
396.Dl # pfctl -M -i interface -Fs
397.Pp
398.It Fl m
399Merge in explicitly given options without resetting those
400which are omitted.
401Allows single options to be modified without disturbing the others:
402.Bd -literal -offset indent
403# echo "set loginterface fxp0" | pfctl -mf -
404.Ed
405.It Fl N
406Load only the NAT rules present in the rule file.
407Other rules and options are ignored.
408Can be combined with the
409.Fl A ,
410.Fl O ,
411and
412.Fl R
413flags to load multiple rule types without (re)loading all rules.
414.It Fl n
415Do not actually load rules, just parse them.
416.It Fl O
417Load only the options present in the rule file.
418Other rules and options are ignored.
419Can be combined with the
420.Fl A ,
421.Fl N ,
422and
423.Fl R
424flags to load multiple rule types without (re)loading all rules.
425.It Fl o Ar level
426Control the ruleset optimizer, overriding any rule file settings.
427.Pp
428.Bl -tag -width xxxxxxxxx -compact
429.It Cm none
430Disable the ruleset optimizer.
431.It Cm basic
432Enable basic ruleset optimizations.
433This is the default behaviour.
434.It Cm profile
435Enable basic ruleset optimizations with profiling.
436.El
437.Pp
438For further information on the ruleset optimizer, see
439.Xr pf.conf 5 .
440.It Fl P
441Do not perform service name lookup for port specific rules,
442instead display the ports numerically.
443.It Fl p Ar device
444Use the device file
445.Ar device
446instead of the default
447.Pa /dev/pf .
448.It Fl q
449Only print errors and warnings.
450.It Fl R
451Load only the filter rules present in the rule file.
452Other rules and options are ignored.
453Can be combined with the
454.Fl A ,
455.Fl N ,
456and
457.Fl O
458flags to load multiple rule types without (re)loading all rules.
459.It Fl r
460Perform reverse DNS lookups on states and tables when displaying them.
461.Fl S
462and
463.Fl r
464are mutually exclusive.
465.It Fl s Ar modifier Op Fl R Ar id
466Show the filter parameters specified by
467.Ar modifier
468(may be abbreviated):
469.Pp
470.Bl -tag -width xxxxxxxxxxx -compact
471.It Cm nat
472Show the currently loaded NAT rules.
473.It Cm queue
474Show the currently loaded queue rules.
475When used together with
476.Fl v ,
477per-queue statistics are also shown.
478When used together with
479.Fl v v ,
480.Nm
481will loop and show updated queue statistics every five seconds, including
482measured bandwidth and packets per second.
483.It Cm ethernet
484Show the currently loaded Ethernet rules.
485When used together with
486.Fl v ,
487the per-rule statistics (number of evaluations,
488packets, and bytes) are also shown.
489.It Cm rules
490Show the currently loaded filter rules.
491When used together with
492.Fl v ,
493the per-rule statistics (number of evaluations,
494packets, and bytes) are also shown.
495When used together with
496.Fl g
497or
498.Fl vv ,
499expired rules
500.Pq marked as Dq # expired
501are also shown.
502Note that the
503.Dq skip step
504optimization done automatically by the kernel
505will skip evaluation of rules where possible.
506Packets passed statefully are counted in the rule that created the state
507(even though the rule is not evaluated more than once for the entire
508connection).
509.It Cm Anchors
510Show the currently loaded anchors directly attached to the main ruleset.
511If
512.Fl a Ar anchor
513is specified as well, the anchors loaded directly below the given
514.Ar anchor
515are shown instead.
516If
517.Fl v
518is specified, all anchors attached under the target anchor will be
519displayed recursively.
520.It Cm states
521Show the contents of the state table.
522.It Cm Sources
523Show the contents of the source tracking table.
524.It Cm info
525Show filter information (statistics and counters).
526When used together with
527.Fl v ,
528source tracking statistics, the firewall's 32-bit hostid number and the
529main ruleset's MD5 checksum for use with
530.Xr pfsync 4
531are also shown.
532.It Cm Running
533Show the running status and provide a non-zero exit status when disabled.
534.It Cm labels
535Show per-rule statistics (label, evaluations, packets total, bytes total,
536packets in, bytes in, packets out, bytes out, state creations) of
537filter rules with labels, useful for accounting.
538.It Cm timeouts
539Show the current global timeouts.
540.It Cm memory
541Show the current pool memory hard limits.
542.It Cm Tables
543Show the list of tables.
544.It Cm osfp
545Show the list of operating system fingerprints.
546.It Cm Interfaces
547Show the list of interfaces and interface groups available to PF.
548When used together with
549.Fl v ,
550it additionally lists which interfaces have skip rules activated.
551When used together with
552.Fl vv ,
553interface statistics are also shown.
554.Fl i
555can be used to select an interface or a group of interfaces.
556.It Cm LimiterStates
557Show information about state limiters.
558If
559.Fl R Ar id
560is specified as well,
561only the state limiter identified by
562.Ar id
563is shown.
564.It Cm LimiterSrcs
565Show information about source limiters.
566If
567.Fl R Ar id
568is specified as well,
569only the state limiter identified by
570.Ar id
571is shown.
572If
573.Fl v
574is specified,
575the address entries for the source pools are shown too.
576.It Cm all
577Show all of the above, except for the lists of interfaces and operating
578system fingerprints.
579.El
580.Pp
581Counters shown with
582.Fl s Cm info
583are:
584.Pp
585.Bl -tag -width xxxxxxxxxxxxxx -compact
586.It match
587explicit rule match
588.It bad-offset
589currently unused
590.It fragment
591invalid fragments dropped
592.It short
593short packets dropped
594.It normalize
595dropped by normalizer: illegal packets
596.It memory
597memory could not be allocated
598.It bad-timestamp
599bad TCP timestamp; RFC 1323
600.It congestion
601network interface queue congested
602.It ip-option
603bad IP/IPv6 options
604.It proto-cksum
605invalid protocol checksum
606.It state-mismatch
607packet was associated with a state entry, but sequence numbers did not match
608.It state-insert
609state insertion failure
610.It state-limit
611configured state limit was reached
612.It src-limit
613source node/connection limit
614.It synproxy
615dropped by synproxy
616.It map-failed
617address mapping failed
618.It translate
619no free ports in translation port range
620.El
621.It Fl S
622Do not perform domain name resolution.
623If a name cannot be resolved without DNS, an error will be reported.
624.It Fl t Ar table Fl T Ar command Op Ar address ...
625Specify the
626.Ar command
627(may be abbreviated) to apply to
628.Ar table .
629Commands include:
630.Pp
631.Bl -tag -width "expire number" -compact
632.It Cm add
633Add one or more addresses to a table.
634Automatically create a persistent table if it does not exist.
635.It Cm delete
636Delete one or more addresses from a table.
637.It Cm expire Ar number
638Delete addresses which had their statistics cleared more than
639.Ar number
640seconds ago.
641For entries which have never had their statistics cleared,
642.Ar number
643refers to the time they were added to the table.
644.It Cm flush
645Flush all addresses in a table.
646.It Cm kill
647Kill a table.
648.It Cm replace
649Replace the addresses of the table.
650Automatically create a persistent table if it does not exist.
651.It Cm show
652Show the content (addresses) of a table.
653.It Cm test
654Test if the given addresses match a table.
655.It Cm zero Op Ar address ...
656Clear all the statistics of a table, or only for specified addresses.
657.It Cm reset
658Clear statistics only for addresses with non-zero statistics. Addresses
659with counter values at zero and their
660.Dq Cleared
661timestamp are left untouched.
662.It Cm load
663Load only the table definitions from
664.Xr pf.conf 5 .
665This is used in conjunction with the
666.Fl f
667flag, as in:
668.Bd -literal -offset indent
669# pfctl -Tl -f pf.conf
670.Ed
671.El
672.Pp
673For the
674.Cm add ,
675.Cm delete ,
676.Cm replace ,
677and
678.Cm test
679commands, the list of addresses can be specified either directly on the command
680line and/or in an unformatted text file, using the
681.Fl f
682flag.
683Comments starting with a
684.Sq #
685or
686.Sq \;
687are allowed in the text file.
688With these commands, the
689.Fl v
690flag can also be used once or twice, in which case
691.Nm
692will print the
693detailed result of the operation for each individual address, prefixed by
694one of the following letters:
695.Pp
696.Bl -tag -width XXX -compact
697.It A
698The address/network has been added.
699.It C
700The address/network has been changed (negated).
701.It D
702The address/network has been deleted.
703.It M
704The address matches
705.Po
706.Cm test
707operation only
708.Pc .
709.It X
710The address/network is duplicated and therefore ignored.
711.It Y
712The address/network cannot be added/deleted due to conflicting
713.Sq \&!
714attributes.
715.It Z
716The address/network has been cleared (statistics).
717.El
718.Pp
719Each table can maintain a set of counters that can be retrieved using the
720.Fl v
721flag of
722.Nm .
723For example, the following commands define a wide open firewall which will keep
724track of packets going to or coming from the
725.Ox
726FTP server.
727The following commands configure the firewall and send 10 pings to the FTP
728server:
729.Bd -literal -offset indent
730# printf "table <test> counters { ftp.openbsd.org }\en \e
731    pass out to <test>\en" | pfctl -f-
732# ping -qc10 ftp.openbsd.org
733.Ed
734.Pp
735We can now use the table
736.Cm show
737command to output, for each address and packet direction, the number of packets
738and bytes that are being passed or blocked by rules referencing the table.
739The time at which the current accounting started is also shown with the
740.Dq Cleared
741line.
742.Bd -literal -offset indent
743# pfctl -t test -vTshow
744   129.128.5.191
745    Cleared:     Thu Feb 13 18:55:18 2003
746    In/Block:    [ Packets: 0        Bytes: 0        ]
747    In/Pass:     [ Packets: 10       Bytes: 840      ]
748    Out/Block:   [ Packets: 0        Bytes: 0        ]
749    Out/Pass:    [ Packets: 10       Bytes: 840      ]
750.Ed
751.Pp
752Similarly, it is possible to view global information about the tables
753by using the
754.Fl v
755modifier twice and the
756.Fl s
757.Cm Tables
758command.
759This will display the number of addresses on each table,
760the number of rules which reference the table, and the global
761packet statistics for the whole table:
762.Bd -literal -offset indent
763# pfctl -vvsTables
764--a-r-C test
765    Addresses:   1
766    Cleared:     Thu Feb 13 18:55:18 2003
767    References:  [ Anchors: 0        Rules: 1        ]
768    Evaluations: [ NoMatch: 3496     Match: 1        ]
769    In/Block:    [ Packets: 0        Bytes: 0        ]
770    In/Pass:     [ Packets: 10       Bytes: 840      ]
771    In/XPass:    [ Packets: 0        Bytes: 0        ]
772    Out/Block:   [ Packets: 0        Bytes: 0        ]
773    Out/Pass:    [ Packets: 10       Bytes: 840      ]
774    Out/XPass:   [ Packets: 0        Bytes: 0        ]
775.Ed
776.Pp
777As we can see here, only one packet \- the initial ping request \- matched the
778table, but all packets passing as the result of the state are correctly
779accounted for.
780Reloading the table(s) or ruleset will not affect packet accounting in any way.
781The two
782.Dq XPass
783counters are incremented instead of the
784.Dq Pass
785counters when a
786.Dq stateful
787packet is passed but does not match the table anymore.
788This will happen in our example if someone flushes the table while the
789.Xr ping 8
790command is running.
791.Pp
792When used with a single
793.Fl v ,
794.Nm
795will only display the first line containing the table flags and name.
796The flags are defined as follows:
797.Pp
798.Bl -tag -width XXX -compact
799.It c
800For constant tables, which cannot be altered outside
801.Xr pf.conf 5 .
802.It p
803For persistent tables, which do not get automatically killed when no rules
804refer to them.
805.It a
806For tables which are part of the
807.Em active
808tableset.
809Tables without this flag do not really exist, cannot contain addresses, and are
810only listed if the
811.Fl g
812flag is given.
813.It i
814For tables which are part of the
815.Em inactive
816tableset.
817This flag can only be witnessed briefly during the loading of
818.Xr pf.conf 5 .
819.It r
820For tables which are referenced (used) by rules.
821.It h
822This flag is set when a table in the main ruleset is hidden by one or more
823tables of the same name from anchors attached below it.
824.It C
825This flag is set when per-address counters are enabled on the table.
826.El
827.It Fl v
828Produce more verbose output.
829A second use of
830.Fl v
831will produce even more verbose output including ruleset warnings.
832See the previous section for its effect on table commands.
833.It Fl x Ar level
834Set the debug
835.Ar level
836(may be abbreviated) to one of the following:
837.Pp
838.Bl -tag -width xxxxxxxxxxxx -compact
839.It Fl x Cm none
840Do not generate debug messages.
841.It Fl x Cm urgent
842Generate debug messages only for serious errors.
843.It Fl x Cm misc
844Generate debug messages for various errors.
845.It Fl x Cm loud
846Generate debug messages for common conditions.
847.El
848.It Fl z
849Clear per-rule statistics.
850.El
851.Sh FILES
852.Bl -tag -width "/etc/pf.conf" -compact
853.It Pa /etc/pf.conf
854Packet filter rules file.
855.It Pa /etc/pf.os
856Passive operating system fingerprint database.
857.El
858.Sh SEE ALSO
859.Xr pf 4 ,
860.Xr pf.conf 5 ,
861.Xr pf.os 5 ,
862.Xr rc.conf 5 ,
863.Xr services 5 ,
864.Xr sysctl.conf 5 ,
865.Xr authpf 8 ,
866.Xr ftp-proxy 8 ,
867.Xr rc 8 ,
868.Xr sysctl 8
869.Sh HISTORY
870The
871.Nm
872program and the
873.Xr pf 4
874filter mechanism appeared in
875.Ox 3.0 .
876They first appeared in
877.Fx 5.3
878ported from the version in
879.Ox 3.5
880