forked from extern/shorewall_code
Correct typos (omma -> comma) in the stoppedrules manpages
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
parent
9dd5f73581
commit
2d01af8256
@ -60,7 +60,7 @@
|
|||||||
firewall itself, while <replaceable>interface</replaceable>
|
firewall itself, while <replaceable>interface</replaceable>
|
||||||
specifies packets arriving on the named interface.</para>
|
specifies packets arriving on the named interface.</para>
|
||||||
|
|
||||||
<para>This column may also include a omma-separated list of
|
<para>This column may also include a comma-separated list of
|
||||||
IP/subnet addresses. If your kernel and iptables include iprange
|
IP/subnet addresses. If your kernel and iptables include iprange
|
||||||
match support, IP address ranges are also allowed. Ipsets and
|
match support, IP address ranges are also allowed. Ipsets and
|
||||||
exclusion are also supported. When <option>$FW</option> or interface
|
exclusion are also supported. When <option>$FW</option> or interface
|
||||||
@ -80,7 +80,7 @@
|
|||||||
arriving on the named interface. Neither may be specified if the
|
arriving on the named interface. Neither may be specified if the
|
||||||
target is <option>NOTRACK</option>.</para>
|
target is <option>NOTRACK</option>.</para>
|
||||||
|
|
||||||
<para>This column may also include a omma-separated list of
|
<para>This column may also include a comma-separated list of
|
||||||
IP/subnet addresses. If your kernel and iptables include iprange
|
IP/subnet addresses. If your kernel and iptables include iprange
|
||||||
match support, IP address ranges are also allowed. Ipsets and
|
match support, IP address ranges are also allowed. Ipsets and
|
||||||
exclusion are also supported. When <option>$FW</option> or interface
|
exclusion are also supported. When <option>$FW</option> or interface
|
||||||
|
@ -60,7 +60,7 @@
|
|||||||
firewall itself, while <replaceable>interface</replaceable>
|
firewall itself, while <replaceable>interface</replaceable>
|
||||||
specifies packets arriving on the named interface.</para>
|
specifies packets arriving on the named interface.</para>
|
||||||
|
|
||||||
<para>This column may also include a omma-separated list of
|
<para>This column may also include a comma-separated list of
|
||||||
IP/subnet addresses. If your kernel and iptables include iprange
|
IP/subnet addresses. If your kernel and iptables include iprange
|
||||||
match support, IP address ranges are also allowed. Ipsets and
|
match support, IP address ranges are also allowed. Ipsets and
|
||||||
exclusion are also supported. When <option>$FW</option> or interface
|
exclusion are also supported. When <option>$FW</option> or interface
|
||||||
@ -80,7 +80,7 @@
|
|||||||
arriving on the named interface. Neither may be specified if the
|
arriving on the named interface. Neither may be specified if the
|
||||||
target is <option>NOTRACK</option>.</para>
|
target is <option>NOTRACK</option>.</para>
|
||||||
|
|
||||||
<para>This column may also include a omma-separated list of
|
<para>This column may also include a comma-separated list of
|
||||||
IP/subnet addresses. If your kernel and iptables include iprange
|
IP/subnet addresses. If your kernel and iptables include iprange
|
||||||
match support, IP address ranges are also allowed. Ipsets and
|
match support, IP address ranges are also allowed. Ipsets and
|
||||||
exclusion are also supported. When <option>$FW</option> or interface
|
exclusion are also supported. When <option>$FW</option> or interface
|
||||||
|
Loading…
Reference in New Issue
Block a user