Advertisement
Annex Communications Server R10.0B and Annex Host Tools R14.2 Release Notes
Example 3
out exclude proto udp port_pair router router netact
out include proto tcp dst_port smtp no_start
Packets generated by RIP are not considered activity and cannot start
the link. Packets destined for SMTP (email) are considered activity
and will keep an active link up, but will not start a dial. All other
packets are considered activity and will start a dial. (The second filter
could have also specified netact, but that is unnecessary because the
exclude implies that netact is the default.)
Example 4
out exclude dst_address 132.245.33.0/24 netact
out exclude dst_address 132.245.11.0/24 netact
Packets sent to either the 33 or 11 subnets will not be considered
activity. All other packets sent will constitute activity. This
demonstrates how excludes are logically ANDed together.
Example 5
out exclude proto tcp dst_address 132.245.66.0/24 netact
in include proto tcp dst_address 132.245.33.0/24 netact
Packets which the Annex sends over the link that are destined for the
66 subnet are not considered activity. All other packets sent are
considered activity. Packets the Annex receives that are addressed to
the 33 subnet are also considered activity. No other packets received
are considered activity. (This example is included to illustrate how
input and output filters do not interact.)
Setting a specific include with netact when there is an exclude with
netact for the same destination (in or out) has no effect. The exclude
with netact implies that everything else is activity (so no specific
include is needed) and, if the exclude matches the same packet as an
include, the exclude takes precedence (thus no specific include is
possible).
302565-A Rev. 00
5
Advertisement
