SECURITY
LOG
• Echo/Chargen/Quote/Snork protection – a packet has been blocked
due to Echo/Chargen/Quote/Snork protection.
• Firewall internal – from the firewall internal mechanism, event type
is recorded and an accompanying explanation will be added.
• Firewall rules were changed – the rule set has been modified.
• Firewall status changed – the firewall status changed from up to
down or vice versa, as specified in the event type description.
• First packet in connection is not a SYN packet – a packet has been
blocked due to a TCP connection that started without a SYN packet.
• Fragmented packet – a fragment has been rejected.
• Fragmented packet, bad align – a packet has been blocked because,
after defragmentation, the packet was badly aligned.
• Fragmented packet, header too big – a packet has been blocked
because, after defragmentation, the header was too big.
• Fragmented packet, header too small – a packet has been blocked
because, after defragmentation, the header was too small.
• Fragmented packet, no memory – a packet has been blocked
because there is no memory for fragments.
• Fragmented packet, overlapped – a packet has been blocked
because, after defragmentation, there were overlapping fragments.
• Fragmented packet, packet exceeds – a packet has been blocked
because, after defragmentation, the packet exceeded.
104
You can modify the type of events that display in the security log. This
does not modify the event itself. It simply changes the information that
displays in the log.
6.6a/ EVENT TYPES
The security log records the following event types:
• Access control – a packet has been accepted/blocked due to an
access control rule.
• Advance filter rule – a packet has been accepted/blocked due to an
advanced filter rule.
• ARP – an ARP packet has been accepted.
• AUTH:113 request - an outbound packet for AUTH protocol has
been accepted (for maximum security level).
• Broadcast/Multicast protection – a packet with a broadcast/
multicast source IP has been blocked.
• Default policy – a packet has been accepted/blocked according to
the default policy.
• Defragmentation failed – the fragment has been stored in memory
and blocked until all fragments have arrived and defragmentation
can be performed.
• DHCP request – your Gateway sent a DHCP request (depends on the
distribution).
• DHCP response - your Gateway sent a DHCP response (depends on
the distribution).
SECURITY SETTINGS
06 / CONFIGURING
verizon.com/fios | ©2014 Verizon. All Rights Reserved.