Reference: Configuration options
Avira Internet Security - User Manual (Status: 23 Sep. 2011)
123
Warning
When a packet is filtered, the corresponding rules are applied successively,
therefore the rule order is very important. Change the rule order only if you are
completely aware of what you are doing.
Predefined rules for the TCP traffic monitor
Setting
Rules
Low
No incoming data traffic is blocked by the Avira FireWall.
Medium
Allow Established TCP Connections on 135
Allow
TCP packets from address
0.0.0.0
with mask
0.0.0.0
if local ports in
{135}
and remote port is in
{0-65535}
.
Apply for
packets of existing connections
.
Don't log
when packet matches rule.
Advanced: Discard packets that have following bytes
<empty>
with mask
<empty>
at offset
0
.
Deny TCP packets on 135
Deny TCP packets from address
0.0.0.0
with mask
0.0.0.0
if local port is in
{135}
and remote port is in
{0-65535}
.
Apply for
all packets
.
Don't log
when packet matches rule.
Advanced: Discard packets that have following bytes
<empty>
with mask
<empty>
at offset
0
.
TCP healthy traffic Monitor
Allow
TCP packets from address
0.0.0.0
with mask
0.0.0.0
if local port is in
{0-65535}
and remote port is in
{0-65535}
.
Apply for
connection initiation and existing connection packets
.
Don't log
when packet matches rule.
Advanced: Select packets that have following bytes
<empty>
with mask
<empty>
at offset
0
.
Discard TCP traffic
Deny
TCP packets from address
0.0.0.0
with mask
0.0.0.0
if local port is in
{0-65535}
and remote port is in
{0-65535}
.
Apply for
all packets
.
Don't log
when packet matches rule.
Advanced: Select packets that have following bytes
<empty>
with mask
<empty>
at offset
0
.
