pf.conf.5: minor improvements

* Align 'on <interface>' parameter with the BNF, so use 'on <ifspec>'
* Clarify etherprotospec BNF, to make it clearer that only numbers are
  supported.

Suggested by:	Christian McDonald
Sponsored by:	Rubicon Communications, LLC ("Netgate")
This commit is contained in:
Kristof Provost 2023-04-21 09:16:53 +02:00
parent 444c661545
commit 4bfffd8cf5

View File

@ -28,7 +28,7 @@
.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
.\" POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd November 24, 2022
.Dd April 21, 2023
.Dt PF.CONF 5
.Os
.Sh NAME
@ -702,7 +702,7 @@ If a packet matches a rule which has the
option set, this rule
is considered the last matching rule, and evaluation of subsequent rules
is skipped.
.It Ar on Aq Ar interface
.It Ar on Aq Ar ifspec
This rule applies only to packets coming in on, or going out through, this
particular interface or interface group.
For more information on interface groups,
@ -3197,7 +3197,8 @@ route = ( "route-to" | "reply-to" | "dup-to" )
[ pooltype ]
af = "inet" | "inet6"
etherprotospec = "proto" ( proto-number | "{" proto-list "}" )
etherprotospec = "proto" ( proto-number | "{" etherproto-list "}" )
etherproto-list = proto-number [ [ "," ] etherproto-list ]
protospec = "proto" ( proto-name | proto-number |
"{" proto-list "}" )
proto-list = ( proto-name | proto-number ) [ [ "," ] proto-list ]