Page 3
D-Link reserves the right to revise this publication and to make changes from time to time in the content hereof without any obligation to notify any person or parties of such revision or changes.
Preface Audience The target audience for this reference guide consists of: • Administrators that are responsible for configuring and managing a NetDefendOS installation. • Administrators that are responsible for troubleshooting a NetDefendOS installation. This guide assumes that the reader is familiar with NetDefendOS and understands the fundamentals of IP network security.
Page 23
Abbreviations Preface Table 1. Abbreviations Abbreviation Full name Application Layer Gateway Address Resolution Protocol DHCP Dynamic Host Configuration Protocol Domain Name System Encapsulating Security Payload File Transfer Protocol High Availability HTTP Hyper Text Transfer Protocol ICMP Internet Control Message Protocol Intrusion Detection Prevention System Internet Protocol IPSec...
Chapter 1. Introduction • Log Message Structure, page 24 • Context Parameters, page 26 • Severity levels, page 30 This guide is a reference for all log messages generated by NetDefendOS. It is designed to be a valuable information source for both management and troubleshooting. 1.1.
Page 25
1.1. Log Message Structure Chapter 1. Introduction is never actually included in the log message. Explanation A detailed explanation of the event. Note that this information is only featured in this reference guide, and is never actually included in the log message. Gateway Action A short string, 1-3 words separated by _, of what action NetDefendOS will take.
1.2. Context Parameters Chapter 1. Introduction 1.2. Context Parameters In many cases, information regarding a certain object is featured in the log message. This can be information about, for example, a connection. In this case, the log message should, besides all the normal log message attributes, also include information about which protocol is used, source and destination IP addresses and ports (if applicable), and so on.
Page 27
Connection Chapter 1. Introduction [srcport] The source port. Valid if the protocol is TCP or UDP. [destport] The destination port. Valid if the protocol is TCP or UDP. [tcphdrlen] The TCP header length. Valid if the protocol is TCP. [udptotlen] The total UDP data length.
Dropped Fragments Chapter 1. Introduction Specifies the name and a description of the signature that triggered this event. Note For IDP log messages an additional log receiver, an SMTP log receiver, can be configured. This information is only sent to log receives of that kind, and not included in the Syslog format.
Page 29
Route Chapter 1. Introduction from Originating router process. Destination router process. Route Additional information about a route. route Route network. routeiface Route destination interface. routegw Route gateway. routemetric Route metric (cost).
1.3. Severity levels Chapter 1. Introduction 1.3. Severity levels An event has a default severity level, based on how serious the event is. The following eight severity levels are possible, as defined by the Syslog protocol: 0 - Emergency Emergency conditions, which most likely led to the system being unusable.
2.1. ALG Chapter 2. Log Message Reference • TRANSPARENCY, page 333 • USERAUTH, page 338 Sort Order All log messages are sorted by their category and then by their ID number. 2.1. ALG These log messages refer to the ALG (Events from Application Layer Gateways) category. 2.1.1.
2.1.4. alg_session_allocation_failure Chapter 2. Log Message Reference (ID: 00200009) connection will be closed. Gateway Action close Recommended Action If the maximum line length is configued too low, increase it. Revision Parameters Context Parameters ALG Module Name ALG Session ID 2.1.4. alg_session_allocation_failure (ID: 00200009) Default Severity CRITICAL Log Message...
2.1.7. unknown_client_data_received Chapter 2. Log Message Reference (ID: 00200105) ALG name: <algname>. Explanation The unit failed parsing the requested URL. The reason for this is problaby because the requested URL has an invalid format, or it contains invalid UTF8 formatted characters. Gateway Action close Recommended Action...
2.1.9. invalid_chunked_encoding (ID: Chapter 2. Log Message Reference 00200107) Context Parameters ALG Module Name ALG Session ID 2.1.9. invalid_chunked_encoding (ID: 00200107) Default Severity WARNING Log Message HTTPALG: The server sent invalid chunked encoding. Closing connection. ALG name: <algname>. Explanation The data received from the server was sent in chunked mode, but it was not properly formatted.
2.1.12. max_http_sessions_reached Chapter 2. Log Message Reference (ID: 00200110) be closed. Gateway Action close Recommended Action Research the source of this, and try to find out why the server is sending compressed data. Revision Parameters algname Context Parameters ALG Module Name ALG Session ID 2.1.12.
2.1.15. content_type_mismatch (ID: Chapter 2. Log Message Reference 00200113) Log Message HTTPALG: Failed to connect to the HTTP Server. Closing connection. ALG name: <algname>. Explanation The unit failed to connect to the HTTP Server, resulting in that the ALG session could not be successfully opened. Gateway Action close Recommended Action...
2.1.20. out_of_memory (ID: 00200118) Chapter 2. Log Message Reference ALG Session ID 2.1.20. out_of_memory (ID: 00200118) Default Severity CRITICAL Log Message HTTPALG: Failed to allocate memory Explanation The unit does not have enough available RAM. WCF could not allocate memory for override functionality. Gateway Action none Recommended Action...
2.1.23. wcf_server_unreachable (ID: Chapter 2. Log Message Reference 00200121) 2.1.23. wcf_server_unreachable (ID: 00200121) Default Severity ERROR Log Message HTTPALG: Failed to connect to web content server <failedserver> Explanation Web Content Filtering was unable to connect to the Web Content Filtering server. The system will try to contact one of the backup servers.
2.1.27. request_url (ID: 00200125) Chapter 2. Log Message Reference 2.1.26. wcf_primary_fallback (ID: 00200124) Default Severity INFORMATIONAL Log Message HTTPALG: Falling back from secondary servers to primary server Explanation Web Content Filtering falls back to primary server after 60 minutes or when a better server has been detected.
2.1.29. wcf_server_auth_failed (ID: Chapter 2. Log Message Reference 00200127) Parameters categories audit override algname Context Parameters Connection Connection ALG Module Name ALG Session ID 2.1.29. wcf_server_auth_failed (ID: 00200127) Default Severity ERROR Log Message HTTPALG: Failed to authenticate with WCF server Explanation The WCF service could not authenticate with the WCF server.
2.1.35. url_reclassification_request Chapter 2. Log Message Reference (ID: 00200133) Log Message HTTPALG: User requests the forbidden URL <url>, eventhough Restricted Site Notice was applied. ALG name: <algname>. Explanation The URL has been requested and the categories are forbidden. Restricted Site Notice was applied. Gateway Action allow Recommended Action...
2.1.39. restricted_site_notice (ID: Chapter 2. Log Message Reference 00200138) user algname Context Parameters Connection Connection ALG Module Name ALG Session ID 2.1.39. restricted_site_notice (ID: 00200138) Default Severity WARNING Log Message HTTPALG: User requests the forbidden URL <url>, eventhough Restricted Site Notice was applied. ALG name: <algname>. Explanation The URL has been requested and the categories are forbidden.
2.1.41. wcf_mem_optimized (ID: Chapter 2. Log Message Reference 00200140) ALG Session ID 2.1.41. wcf_mem_optimized (ID: 00200140) Default Severity DEBUG Log Message HTTPALG: Optimizing WCF memory usage Explanation The Web Content Filtering subsystem has optimized its memory usage and freed up some memory. This is a normal condition and does not affect functionality nor performance.
2.1.50. some_recipient_email_ids_are_in_blocklist Chapter 2. Log Message Reference (ID: 00200160) Recommended Action None. Revision Parameters sender_email_address recipient_email_addresses Context Parameters ALG Module Name ALG Session ID 2.1.50. some_recipient_email_ids_are_in_blocklist (ID: 00200160) Default Severity WARNING Log Message SMTPALG: Some recipients email id are in Black List Explanation Since some "RCPT TO:"...
2.1.53. blocked_filetype (ID: 00200166) Chapter 2. Log Message Reference Default Severity ERROR Log Message SMTPALG: Base 64 decode failed. Attachment is allowed Explanation The data sent to Base64 decoding failed. This can occur if the email sender sends incorrectly formatted data. Fail-mode is set to allow so date will be forwared.
2.1.57. all_recipient_email_ids_are_in_blocklist Chapter 2. Log Message Reference (ID: 00200172) ALG Session ID 2.1.57. all_recipient_email_ids_are_in_blocklist (ID: 00200172) Default Severity WARNING Log Message SMTPALG: All recipients e-mail addresses are in Black List Explanation Since "RCPT TO:" email ids are in Black List, SMTP ALG rejected the client request.
2.1.60. dnsbl_init_error (ID: 00200177) Chapter 2. Log Message Reference Parameters sender_email_address recipient_email_addresses Context Parameters ALG Module Name ALG Session ID 2.1.60. dnsbl_init_error (ID: 00200177) Default Severity ERROR Log Message DNSbl internal error Explanation The email could not be checked for spam. Email will be processed without spam checks.
2.1.67. smtp_state_violation (ID: Chapter 2. Log Message Reference 00200190) 2.1.66. cmd_pipelined (ID: 00200186) Default Severity ERROR Log Message SMTPALG: Received pipelined request. Explanation The SMTP ALG does not support pipelined requests. The appearance of this log message indicates that the client used PIPELINING even though it was removed from capability list.
2.1.69. illegal_data_direction (ID: Chapter 2. Log Message Reference 00200202) Context Parameters ALG Module Name ALG Session ID 2.1.69. illegal_data_direction (ID: 00200202) Default Severity ERROR Log Message FTPALG: TCP data from <peer> not allowed in this direction. Closing connection Explanation TCP Data was sent in an invalid direction, and the connection will be closed.
2.1.72. illegal_chars (ID: 00200210) Chapter 2. Log Message Reference Revision Context Parameters ALG Module Name ALG Session ID Rule Information Connection 2.1.72. illegal_chars (ID: 00200210) Default Severity WARNING Log Message FTPALG: 8 bit characters in control channel from <peer> not allowed. Closing connection Explanation 8 bit characters were discovered in the control channel.
2.1.75. illegal_command (ID: Chapter 2. Log Message Reference 00200213) Default Severity WARNING Log Message FTPALG: Failed to parse command from <peer> as a FTP command. String=<string>. Closing connection Explanation An invalid command was received on the control channel. This is not allowed, and the connection will be closed.
2.1.77. illegal_command (ID: Chapter 2. Log Message Reference 00200215) Recommended Action If the client should be allowed to do active FTP, modify the FTPALG configuration. Revision Parameters peer Context Parameters ALG Module Name ALG Session ID Connection 2.1.77. illegal_command (ID: 00200215) Default Severity WARNING Log Message...
2.1.79. illegal_port_number (ID: Chapter 2. Log Message Reference 00200217) 2.1.79. illegal_port_number (ID: 00200217) Default Severity CRITICAL Log Message FTPALG: Illegal PORT command from <peer>, port <port> not allowed. String=<string>. Rejecting command Explanation An illegal "PORT" command was received from the client. It requests that the server should connect to a port which is out of range.
2.1.82. illegal_direction1 (ID: Chapter 2. Log Message Reference 00200220) rejected. Gateway Action rejecting_command Recommended Action If the client should be allowed to do issue "SITE EXEC" commands, modify the FTPALG configuration. Revision Parameters peer Context Parameters ALG Module Name ALG Session ID Connection 2.1.82.
2.1.84. illegal_option (ID: 00200222) Chapter 2. Log Message Reference 2.1.84. illegal_option (ID: 00200222) Default Severity WARNING Log Message FTPALG: Invalid OPTS argument from <peer>. String=<string>. Rejecting command. Explanation An invalid OPTS argument was received. The argument does not start with an alphabetic letter, and the command will be rejected. Gateway Action rejecting_command Recommended Action...
2.1.90. illegal_reply (ID: 00200230) Chapter 2. Log Message Reference 2.1.89. illegal_reply (ID: 00200228) Default Severity WARNING Log Message FTPALG: Illegal numerical reply (<reply>) from <peer>. String=<string>. Closing connection. Explanation An illegal numerical reply was received from server, and the connection will be closed. Gateway Action close Recommended Action...
2.1.94. bad_ip (ID: 00200234) Chapter 2. Log Message Reference ALG Session ID Connection 2.1.94. bad_ip (ID: 00200234) Default Severity CRITICAL Log Message FTPALG: Invalid IP <ip4addr>, Server IP is <ip4addr_server>. String=<string>. Closing connection. Explanation The FTP Server requests that the client should connect to another IP that it's own.
2.1.100. max_ftp_sessions_reached Chapter 2. Log Message Reference (ID: 00200241) Default Severity ERROR Log Message FTPALG: Internal Error - failed to merge conns. Closing connection Explanation An internal error occured when two connections were being merged into one, and the connection will be closed. Gateway Action close Recommended Action...
2.1.103. content_type_mismatch (ID: Chapter 2. Log Message Reference 00200250) Default Severity ERROR Log Message FTPALG: Failed to connect to the FTP Server. Closing connection Explanation The unit failed to connect to the FTP Server, resulting in that the ALG session could not be successfully opened. Gateway Action close Recommended Action...
2.1.106. blocked_filetype (ID: Chapter 2. Log Message Reference 00200253) Log Message FTPALG: The file <filename> (File type: <filetype> ) cannot be sent to antivirus scan engine. Explanation The data cannot be sent to AVSE for scanning since file transfer begins from within the middle of the file. The scanning process will fail for compressed files.
2.1.119. option_not_sent (ID: Chapter 2. Log Message Reference 00200360) ALG Session ID Connection 2.1.119. option_not_sent (ID: 00200360) Default Severity WARNING Log Message TFTPALG: The received option <option> was not sent Explanation The received option was not sent.Closing connection. Gateway Action close Recommended Action None.
2.1.125. invalid_packet_received (ID: Chapter 2. Log Message Reference 00200366) Explanation An attempt to create a new TFTPALG session failed, because the unit is out of memory. Gateway Action close Recommended Action Decrease the maximum allowed TFTPALG sessions, or try to free some of the RAM used.
2.1.136. failed_connect_pop3_server Chapter 2. Log Message Reference (ID: 00200382) Recommended Action Decrease the maximum allowed POP3ALG sessions, or try to free some of the RAM used. Revision Context Parameters ALG Module Name 2.1.136. failed_connect_pop3_server (ID: 00200382) Default Severity ERROR Log Message POP3ALG: Failed to connect to the POP3 Server.
2.1.142. command_blocked_invalid_len Chapter 2. Log Message Reference (ID: 00200388) Log Message POP3ALG: Possible invalid end of mail "\\n.\\n" received. Explanation The client is sending possible invalid end of mail. Gateway Action allow Recommended Action Research how the client is sending possible invalid end of mail. Revision Parameters sender_email_address...
2.1.145. content_type_mismatch_mimecheck_disabled Chapter 2. Log Message Reference (ID: 00200391) 2.1.144. content_type_mismatch (ID: 00200390) Default Severity NOTICE Log Message POP3ALG: Content type mismatch in file <filename>. Identified filetype <filetype> Explanation The filetype of the file does not match the actual content type. As there is a content type mismatch, data is discarded.
2.1.150. invalid_line_endings (ID: Chapter 2. Log Message Reference 00200397) Explanation Unexpected end of mail received while parsing mail content.. Gateway Action block Recommended Action Research if mail is not complete. Revision Parameters sender_email_address retrigs Context Parameters ALG Module Name ALG Session ID 2.1.150.
2.1.153. failed_create_new_session Chapter 2. Log Message Reference (ID: 00200451) Log Message TLSALG: Maximum number of TLS sessions (<max_sessions>) for service reached. Closing connection Explanation The maximum number of concurrent TLS sessions has been reached for this service. No more sessions can be opened before old sessions have been released.
2.1.158. tls_cipher_suite_certificate_mismatch Chapter 2. Log Message Reference (ID: 00200456) Context Parameters ALG Module Name ALG Session ID 2.1.158. tls_cipher_suite_certificate_mismatch (ID: 00200456) Default Severity ERROR Log Message TLSALG: The negotiated cipher suite can not be used with the configured certificate. Explanation The negotiated cipher suite, which is an exportable cipher suite, does not permit using the certificate's key to perform the key exchange.
2.1.161. tls_invalid_message (ID: Chapter 2. Log Message Reference 00200459) spent on key exchanges. This system is controlled by the advanced setting SSL_ProcessingPriority. Gateway Action close Recommended Action Investigate the source of this, and try to find out if it is a part of a possible attack, or normal traffic.
2.1.164. tls_out_of_memory (ID: Chapter 2. Log Message Reference 00200462) Default Severity WARNING Log Message TLSALG: No shared cipher suites. Explanation A connecting TLS peer does not share any cipher suites with the unit. The TLS ALG session will be closed. Gateway Action close Recommended Action...
2.1.169. failed_connect_pptp_server Chapter 2. Log Message Reference (ID: 00200603) Revision Context Parameters ALG Module Name 2.1.169. failed_connect_pptp_server (ID: 00200603) Default Severity ERROR Log Message PPTPALG: Failed to connect to the PPTP Server. Closing the connection. Explanation The PPTP ALG could not connect to the receiving PPTP server, resulting in that the ALG session could not be successfully opened.
2.1.172. pptp_tunnel_removed_server Chapter 2. Log Message Reference (ID: 00200606) ALG Module Name 2.1.172. pptp_tunnel_removed_server (ID: 00200606) Default Severity NOTICE Log Message PPTPALG: PPTP tunnel between server and security gateway removed Explanation A PPTP tunnel has been removed betweem the PPTP server and the PPTP-ALG.
2.1.176. pptp_tunnel_established_server Chapter 2. Log Message Reference (ID: 00200610) 2.1.175. pptp_malformed_packet (ID: 00200609) Default Severity WARNING Log Message Malformed packet received from <remotegw> on <iface> Explanation A malformed packet was received by the PPTP-ALG. Gateway Action drop Recommended Action None. Revision Parameters iface...
2.2. ANTIVIRUS Chapter 2. Log Message Reference 2.2. ANTIVIRUS These log messages refer to the ANTIVIRUS (Anti-virus related events) category. 2.2.1. virus_found (ID: 05800001) Default Severity WARNING Log Message Virus found in file <filename>. Virus Name: <virusname>. Signature: <virussig>. Advisory ID: <advisoryid>. Explanation A virus has been detected in a data stream.
2.2.3. excluded_file (ID: 05800003) Chapter 2. Log Message Reference 2.2.3. excluded_file (ID: 05800003) Default Severity NOTICE Log Message File <filename> is excluded from scanning. Identified filetype: <filetype>. Explanation The named file will be excluded from anti-virus scanning. The filetype is present in the anti-virus scan exclusion list. Gateway Action allow_data_without_scan Recommended Action...
2.2.6. compression_ratio_violation Chapter 2. Log Message Reference (ID: 05800006) Explanation The file could not be scanned by the anti-virus module since the decompression of the compressed file failed. Since anti-virus is running in audit mode, the data transfer will be allowed to continue. Gateway Action allow_data Recommended Action...
2.2.10. out_of_memory (ID: 05800010) Chapter 2. Log Message Reference Connection 2.2.10. out_of_memory (ID: 05800010) Default Severity ERROR Log Message Out of memory Explanation Memory allocation failed. Since anti-virus is running in protect mode, the data transfer will be aborted in order to protect the receiver. Gateway Action block_data Recommended Action...
2.2.13. no_valid_license (ID: Chapter 2. Log Message Reference 05800015) running in audit mode, the data transfer will be allowed to continue. Gateway Action allow_data Recommended Action None. Revision Parameters filename [layer7_srcinfo] [layer7_dstinfo] Context Parameters ALG Module Name ALG Session ID Connection 2.2.13.
2.2.16. out_of_memory (ID: 05800018) Chapter 2. Log Message Reference initialization. Explanation Anti-virus scanning is aborted since the scan engine returned a general error during initialization. Gateway Action av_scanning_aborted Recommended Action Try to restart the unit in order to solve this issue. Revision Context Parameters ALG Session ID...
2.2.19. unknown_encoding (ID: Chapter 2. Log Message Reference 05800184) Log Message SMTPALG: Content transfer encoding is unknown or not present. Explanation Antivirus module cannot scan the attachment since the transfer encoding is missing or unknown. Fail Mode is allow so data is allowed without scanning.
2.3. ARP Chapter 2. Log Message Reference 2.3. ARP These log messages refer to the ARP (ARP events) category. 2.3.1. already_exists (ID: 00300001) Default Severity NOTICE Log Message An entry for this IP address already exists Explanation The entry was not added as a previous entry for this IP address already exists in the ARP table.
2.3.5. arp_response_multicast (ID: Chapter 2. Log Message Reference 00300005) 2.3.4. arp_response_broadcast (ID: 00300004) Default Severity NOTICE Log Message ARP response is a broadcast address Explanation The ARP response has a sender address which is a broadcast address. Allowing. Gateway Action allow Recommended Action If this is not the desired behaviour, modify the configuration.
2.3.8. hwaddr_change (ID: 00300008) Chapter 2. Log Message Reference Default Severity NOTICE Log Message ARP hw sender does not match Ethernet hw sender. Dropping Explanation The hardware sender address specified in the ARP data does not match the Ethernet hardware sender address. Dropping packet. Gateway Action drop Recommended Action...
2.3.11. arp_access_allowed_expect Chapter 2. Log Message Reference (ID: 00300050) 2.3.10. invalid_arp_sender_ip_address (ID: 00300049) Default Severity WARNING Log Message Failed to verify ARP sender IP address. Dropping Explanation The ARP sender IP address could not be verfied according to the "access" section, and the packet is dropped. Gateway Action drop Recommended Action...
2.3.14. arp_response_multicast_drop Chapter 2. Log Message Reference (ID: 00300053) Default Severity WARNING Log Message ARP response is a broadcast address. Dropping Explanation The ARP response has a sender address which is a broadcast address. Dropping packet. Gateway Action drop Recommended Action If this is not the desired behaviour, modify the configuration.
2.3.16. hwaddr_change_drop (ID: Chapter 2. Log Message Reference 00300055) 2.3.16. hwaddr_change_drop (ID: 00300055) Default Severity NOTICE Log Message <knownip> has a different address <newhw> compared to the known hardware address <knownhw>. Dropping packet. Explanation A known dynamic ARP entry has a different hardware address than the one in the ARP packet.
2.4. AVUPDATE Chapter 2. Log Message Reference 2.4. AVUPDATE These log messages refer to the AVUPDATE (Antivirus Signature update) category. 2.4.1. av_db_update_failure (ID: 05000001) Default Severity ALERT Log Message Update of the Anti-virus database failed, because of <reason> Explanation The unit tried to update the anti-virus database, but failed. The reason for this is specified in the "reason"...
2.4.5. av_detects_invalid_system_time Chapter 2. Log Message Reference (ID: 05000005) Log Message Anti-virus database could not be updated, as no valid subscription exist Explanation The current license does not allow the anti-virus database to be updated. Gateway Action None Recommended Action Check the system's time and/or purchase a subscription.
2.6.8. no_new_conn_for_this_packet Chapter 2. Log Message Reference (ID: 00600012) 2.6.7. out_of_connections (ID: 00600011) Default Severity WARNING Log Message Out of connections. Dropping connection attempt Explanation The connection table is currently full, and this new connection attempt will be dropped. Gateway Action drop Recommended Action None.
2.6.10. no_return_route (ID: 00600014) Chapter 2. Log Message Reference Parameters protocol Context Parameters Rule Name Packet Buffer 2.6.10. no_return_route (ID: 00600014) Default Severity WARNING Log Message Failed to open a new connection since a return route to the sender address cant be found. Dropping packet Explanation There was no return route found to the sender address of the packet.
2.6.13. udp_src_port_0_illegal (ID: Chapter 2. Log Message Reference 00600021) Recommended Action None. Revision Context Parameters Rule Name Packet Buffer 2.6.13. udp_src_port_0_illegal (ID: 00600021) Default Severity WARNING Log Message UDP source port is set to 0. Dropping Explanation The UDP source port was set to 0. This can be used by UDP streams not expecting return traffic.
2.7. DHCP Chapter 2. Log Message Reference 2.7. DHCP These log messages refer to the DHCP (DHCP client events) category. 2.7.1. offered_ip_occupied (ID: 00700001) Default Severity NOTICE Log Message Interface <iface> received a lease with an offered IP that appear to be occupied (<ip4addr>) Explanation Received a DHCP lease which appears to be in use by someone else.
2.7.13. ip_collision (ID: 00700014) Chapter 2. Log Message Reference Log Message Interface <iface> received a lease where the offered broadcast equals the offered gateway Explanation An interface received a lease where the offered broadcast address is equal with the offered gateway address. Gateway Action drop Recommended Action...
2.8. DHCPRELAY Chapter 2. Log Message Reference 2.8. DHCPRELAY These log messages refer to the DHCPRELAY (DHCP relayer events) category. 2.8.1. unable_to_save_dhcp_relay_list (ID: 00800001) Default Severity WARNING Log Message Unable to auto save the DHCP relay list to disk Explanation Unable to autosave the DHCP relay list to disk.
2.8.14. bad_inform_pkt_with_mismatching_source_ip_and_client_ip Chapter 2. Log Message Reference (ID: 00800014) 2.8.14. bad_inform_pkt_with_mismatching_source_ip_and_client_ip (ID: 00800014) Default Severity WARNING Log Message INFORM packet did not pass through a relayer but the packet source ip and the client ip doesnt match. Dropping Explanation Received non relayed INFORM DHCP packet with illegally mismatching source and client IP.
2.8.26. relayed_dhcp_reply (ID: Chapter 2. Log Message Reference 00800026) Default Severity WARNING Log Message A host route for <dest_ip> already exists which points to another interface. Dropping Explanation An ambiguous host route indicating another interface was detected trying to setup a dynamic hostroute for a client. Gateway Action drop Recommended Action...
2.9. DHCPSERVER Chapter 2. Log Message Reference 2.9. DHCPSERVER These log messages refer to the DHCPSERVER (DHCP server events) category. 2.9.1. unable_to_send_response (ID: 00900001) Default Severity WARNING Log Message Failed to get buffer for sending. Unable to reply Explanation Unable to get a buffer for sending. Gateway Action None Recommended Action...
2.9.5. dhcp_packet_too_small (ID: Chapter 2. Log Message Reference 00900005) Gateway Action None Recommended Action None. Revision 2.9.5. dhcp_packet_too_small (ID: 00900005) Default Severity WARNING Log Message Received DHCP packet which is smaller then the minimum allowed 300 bytes. Dropping Explanation Received a DHCP packet which is smaller then the minimum allowed 300 bytes.
2.10. FRAG Chapter 2. Log Message Reference 2.10. FRAG These log messages refer to the FRAG (Fragmentation events) category. 2.10.1. individual_frag_timeout (ID: 02000001) Default Severity WARNING Log Message Individual fragment timed out. Explanation A fragment of an IP packet timed out, and is dropped. Gateway Action drop Recommended Action...
2.10.14. frag_offset_plus_length_not_in_range Chapter 2. Log Message Reference (ID: 02000014) Default Severity WARNING Log Message Dropping duplicate fragment Explanation A duplicate fragment of an IP packet was received. Dropping the duplicate fragment. Gateway Action drop Recommended Action None. Revision Context Parameters Rule Name Packet Buffer 2.10.14.
2.10.26. drop_frag_failed_suspect_packet Chapter 2. Log Message Reference (ID: 02000026) Log Message Dropping extraneous fragment of completed packet Explanation A completed reassembled IP packet contains a extraneous fragment, which is dropped. Gateway Action drop Recommended Action None. Revision Context Parameters Rule Name Packet Buffer 2.10.26.
2.11.12. idp_evasion (ID: 01300012) Chapter 2. Log Message Reference Log Message Failed to reassemble data. ID Rule: <idrule>. Source IP: <srcip>. Source Port: <srcport>. Destination IP: <destip>. Destination Port: <destport>. Closing connection. Explanation The unit failed to reassemble data. The reason for this is problaby due to an IDP engine evasion attack.
2.12.5. idp_detects_invalid_system_time Chapter 2. Log Message Reference (ID: 01400005) Default Severity NOTICE Log Message Intrusion Detection & Prevention database could not be updated, as no valid subscription exist Explanation The current license does not allow Intrusion Detection & Prevention database to be updated. Gateway Action None Recommended Action...
2.13. IGMP Chapter 2. Log Message Reference 2.13. IGMP These log messages refer to the IGMP (IGMP events) category. 2.13.1. querier_election_won (ID: 04200001) Default Severity NOTICE Log Message Taking on the role of Querier at interface <iface>. Explanation This router is now the IGMP Querier at the specified interface. Gateway Action none Recommended Action...
2.13.7. invalid_query_group_address Chapter 2. Log Message Reference (ID: 04200008) Revision Parameters recv_if Context Parameters Packet Buffer 2.13.7. invalid_query_group_address (ID: 04200008) Default Severity ERROR Log Message IGMP group specific query at interface <recv_if> about group <grp> (<grp_sat> after being SAT'ed) includes unicast ip address. Explanation Unicast IP address found inside group specific query.
2.13.12. packet_includes_aux_data Chapter 2. Log Message Reference (ID: 04200013) Gateway Action allow Recommended Action None. Revision Parameters igmpver sgrp ssrc name action 2.13.12. packet_includes_aux_data (ID: 04200013) Default Severity WARNING Log Message IGMP Group record <grp> from interface <recv_if> contains auxilliary data. Explanation This software support IGMPv1, IGMPv2 and IGMPv3 and none of them support the feature known as "Auxilliary Data".
2.13.14. bad_grp (ID: 04200015) Chapter 2. Log Message Reference Context Parameters Packet Buffer 2.13.14. bad_grp (ID: 04200015) Default Severity WARNING Log Message Bad IGMP Member Report at interface <iface>: Group record request group <grp> (which is not a multicast group). Explanation This is most likely a faulty IGMP config.
2.13.17. igmp_ruleset_rejects_report Chapter 2. Log Message Reference (ID: 04200018) Parameters igmpver sat_grp sat_src name 2.13.17. igmp_ruleset_rejects_report (ID: 04200018) Default Severity WARNING Log Message Rule <name> drops multicast sender <src> for group record <grp> in Member Report at interface <iface>. Explanation IGMP Member Report contains an unwanted IP sender.
2.13.20. max_if_requests_per_second_reached Chapter 2. Log Message Reference (ID: 04200021) Explanation Too many IGMP requests received per second. Possible IGMP DoS attack. Gateway Action drop Recommended Action Increase global IGMPMaxReqs per second limit if more requests are wanted. Revision Parameters ipsrc iface 2.13.20.
2.13.23. older_querier_present (ID: Chapter 2. Log Message Reference 04200024) Log Message Dropped IGMP message with unknown type. Explanation Invalid IGMP message type received. Gateway Action drop Recommended Action None, but keep an eye open for malfunctional software/hardware on the network. Revision Parameters MSGType...
2.14.42. peer_is_dead (ID: 01800317) Chapter 2. Log Message Reference Explanation No policymanager to free tunnel from!!! IPsec does not work properly. Gateway Action ipsec_out_of_work Recommended Action Restart. Revision 2.14.42. peer_is_dead (ID: 01800317) Default Severity INFORMATIONAL Log Message Peer <peer> has been detected dead Explanation A remote peer have been detected as dead.
2.14.59. recieved_packet_to_disabled_IPsec Chapter 2. Log Message Reference (ID: 01800500) Default Severity NOTICE Log Message Returned a dynamic cfg mode IP <ip> to the IP pool Explanation A dynamically allocated ip used for IKE cfg mode was returned to the IP pool. Gateway Action None Recommended Action...
2.14.62. no_remote_gateway (ID: Chapter 2. Log Message Reference 01800503) Recommended Action This is usualy a consequence of low memory or a bad configuration. Look for previous log messages to find the cause for the interface being disabled. Revision Parameters ipsec_connection 2.14.62.
2.14.79. ipsec_sa_negotiation_completed Chapter 2. Log Message Reference (ID: 01802040) Default Severity WARNING Log Message Type of the local ID <localid> is not KEY-ID for the mamros-pskeyext negotiation. The negotiation might fail. Explanation Type of the local ID is not KEY-ID for the mamros-pskeyext negotiation.
2.14.92. no_authentication_method_specified Chapter 2. Log Message Reference (ID: 01802100) rule protocol Explanation Failed to insert rule since forced NAT protocol do not match rule protocol. Gateway Action VPN_tunnel_disabled Recommended Action Reconfigure_IPsec. Revision 2.14.92. no_authentication_method_specified (ID: 01802100) Default Severity ERROR Log Message Neither pre-shared keys nor CA certificates nor EAP are specified for a tunnel Explanation...
2.14.95. invalid_rule_setting (ID: Chapter 2. Log Message Reference 01802105) Revision 2.14.95. invalid_rule_setting (ID: 01802105) Default Severity ERROR Log Message Both REJECT and PASS defined for a rule Explanation Can not specify both pass and reject for a rule. Gateway Action None Recommended Action None.
2.14.109. out_of_memory_for_tunnel Chapter 2. Log Message Reference (ID: 01802211) Revision Parameters tunnel 2.14.109. out_of_memory_for_tunnel (ID: 01802211) Default Severity ERROR Log Message Out of memory. Could not allocate memory for tunnel name! <tunnel> Explanation Out of memory. Could not allocate memory for tunnel name!. Gateway Action VPN_tunnel_disabled Recommended Action...
2.14.120. max_phase1_sa_reached Chapter 2. Log Message Reference (ID: 01802400) Gateway Action None Recommended Action None. Revision Parameters info int_severity 2.14.120. max_phase1_sa_reached (ID: 01802400) Default Severity NOTICE Log Message The maximum number of active Phase-1 SAs reached Explanation Maximum number of active Phase-1 SAs reached. Gateway Action negotiation_aborted Recommended Action...
2.14.124. could_not_convert_certificate Chapter 2. Log Message Reference (ID: 01802601) Default Severity WARNING Log Message Could not decode Certificate to pem format. The certificate may be corrupted or it was given in unrecognized format. Explanation Could_not_decode_certificate. Gateway Action certificate_invalid Recommended Action None.
2.14.127. could_not_force_cert_to_be_trusted Chapter 2. Log Message Reference (ID: 01802604) Gateway Action certificate_not_usable_if_no_valid_CRLs Recommended Action None. Revision 2.14.127. could_not_force_cert_to_be_trusted (ID: 01802604) Default Severity WARNING Log Message Could not force CA certificate as a point of trust Explanation Could not force CA certificate as a point of trust. Gateway Action certificate_disabled Recommended Action...
2.14.131. could_not_loack_certificate Chapter 2. Log Message Reference (ID: 01802608) corrupted or it was given in unrecognized format. Explanation Could_not_decode_certificate. Gateway Action certificate_invalid Recommended Action None. Revision 2.14.131. could_not_loack_certificate (ID: 01802608) Default Severity WARNING Log Message Could not lock certificate in cache Explanation Could not lock certificate in cache.
2.14.177. failed_to_select_ike_sa (ID: Chapter 2. Log Message Reference 01803002) Log Message Could not select policy rule Explanation Could not select policy rule. Gateway Action None Recommended Action None. Revision 2.14.177. failed_to_select_ike_sa (ID: 01803002) Default Severity INFORMATIONAL Log Message Could not select SA from IKE SA proposal Explanation Could not select SA from IKE SA proposal.
2.14.197. audit_event (ID: 01803200) Chapter 2. Log Message Reference Default Severity NOTICE Log Message Negotiation aborted due to license restrictions: IKE responder mode not available. Explanation A negotiation was aborted because it was not initiated by the correct side in accordance with license restrictions. Gateway Action ike_negotiation_aborted Recommended Action...
2.15. IP_ERROR Chapter 2. Log Message Reference 2.15. IP_ERROR These log messages refer to the IP_ERROR (Packet discarded due to IP header error(s)) category. 2.15.1. too_small_packet (ID: 01500001) Default Severity WARNING Log Message Packet is too small to contain IPv4 header Explanation The received packet is too small to contain an IPv4 header, and will be dropped.
2.15.4. invalid_ip_length (ID: Chapter 2. Log Message Reference 01500004) Revision Parameters iptotlen iphdrlen Context Parameters Rule Name Packet Buffer 2.15.4. invalid_ip_length (ID: 01500004) Default Severity WARNING Log Message Invalid IP header length, IPTotLen=<iptotlen>, RecvLen=<recvlen> Explanation The received packet IP total length is larger than the received transport data.
2.16. IP_FLAG Chapter 2. Log Message Reference 2.16. IP_FLAG These log messages refer to the IP_FLAG (Events concerning the IP header flags) category. 2.16.1. ttl_low (ID: 01600001) Default Severity WARNING Log Message Received packet with too low TTL of <ttl>. Min TTL is <ttlmin>. Ignoring Explanation The received packet has a TTL (Time-To-Live) field which is too low.
2.17. IP_OPT Chapter 2. Log Message Reference 2.17. IP_OPT These log messages refer to the IP_OPT (Events concerning the IP header options) category. 2.17.1. source_route (ID: 01700001) Default Severity NOTICE Log Message Packet has a source route Explanation The packet has a source route. Ignoring. Gateway Action ignore Recommended Action...
2.18. IP_PROTO Chapter 2. Log Message Reference 2.18. IP_PROTO These log messages refer to the IP_PROTO (IP Protocol verification events) category. 2.18.1. multicast_ethernet_ip_address_missmatch (ID: 07000011) Default Severity WARNING Log Message Received packet with a destination IP address <ip_multicast_addr> that does match Ethernet multicast...
2.18.4. ttl_low (ID: 07000014) Chapter 2. Log Message Reference which is not allowed. Dropping packet. Gateway Action drop Recommended Action None. Revision Context Parameters Rule Name Packet Buffer 2.18.4. ttl_low (ID: 07000014) Default Severity WARNING Log Message Received packet with too low TTL of <ttl>. Min TTL is <ttlmin>. Dropping Explanation The received packet has a TTL (Time-To-Live) field which is too low.
2.18.13. oversize_gre (ID: 07000050) Chapter 2. Log Message Reference 2.18.12. multicast_ethernet_ip_address_missmatch (ID: 07000033) Default Severity WARNING Log Message Received packet with a destination IP address <ip_multicast_addr> that does match Ethernet multicast address <eth_multicast_addr> Explanation A packet was received with an IP multicast Ethernet address as destination address, but the IP address in the IP header does however not match it.
2.18.18. oversize_ipip (ID: 07000055) Chapter 2. Log Message Reference Recommended Action This can be changed under the Advanced Settings section. Revision Parameters proto Context Parameters Rule Name Packet Buffer 2.18.18. oversize_ipip (ID: 07000055) Default Severity WARNING Log Message Configured size limit for the IPIP protocol exceeded. Dropping Explanation The configured size limit for the IPIP protocol was exceeded.
2.18.21. oversize_ip (ID: 07000058) Chapter 2. Log Message Reference Gateway Action drop Recommended Action This can be changed under the Advanced Settings section. Revision Parameters proto Context Parameters Rule Name Packet Buffer 2.18.21. oversize_ip (ID: 07000058) Default Severity WARNING Log Message Configured size limit for IP protocol exceeded.
2.18.26. invalid_icmp_data_invalid_ip_length Chapter 2. Log Message Reference (ID: 07000074) 2.18.26. invalid_icmp_data_invalid_ip_length (ID: 07000074) Default Severity WARNING Log Message Invalid ICMP data length. ICMPDataLen=<icmpdatalen> ICMPIPDataLen=<icmpipdatalen> ICMPIPDataMinLen=<icmpipdataminlen>. Dropping Explanation The ICMP data length is invalid. The contained IP data must be atleast 8 bytes long.
2.19. L2TP Chapter 2. Log Message Reference 2.19. L2TP These log messages refer to the L2TP (L2TP tunnel events) category. 2.19.1. l2tpclient_resolve_successful (ID: 02800001) Default Severity NOTICE Log Message L2TP client <iface> resolved <remotegwname> to <remotegw> Explanation The L2TP client successfully resolved the DNS name of the remote gateway.
2.19.7. l2tp_session_closed (ID: Chapter 2. Log Message Reference 02800007) Recommended Action Make sure no manually configured routes to the L2TP server interface exists in the configuration. Revision Parameters iface 2.19.7. l2tp_session_closed (ID: 02800007) Default Severity NOTICE Log Message Closed L2TP session. Session ID: <sessionid>, Tunnel ID: <tunnelid> Explanation The L2TP session with the specified session ID has been closed.
2.20. LICUPDATE Chapter 2. Log Message Reference 2.20. LICUPDATE These log messages refer to the LICUPDATE (License update) category. 2.20.1. license_update_failure (ID: 05500001) Default Severity ALERT Log Message License update failed, because of <reason> Explanation The unit tried to update the license, but failed. The reason for this is specified in the "reason"...
2.21. PPP Chapter 2. Log Message Reference 2.21. PPP These log messages refer to the PPP (PPP tunnel events) category. 2.21.1. ip_pool_empty (ID: 02500001) Default Severity WARNING Log Message IPCP can not assign IP address to peer because the IP address pool is empty Explanation IPCP can not assign an IP address to the peer because there are no free...
2.21.4. seconday_dns_address_required_but_not_received Chapter 2. Log Message Reference (ID: 02500004) Revision Parameters tunnel_type 2.21.4. seconday_dns_address_required_but_not_received (ID: 02500004) Default Severity WARNING Log Message Secondary DNS address required but not received. PPP terminated Explanation Peer refuses to give out a secondary DNS address. Since reception of a secondary DNS address is required, PPP is terminated.
2.21.14. username_too_long (ID: Chapter 2. Log Message Reference 02500201) 2.21.13. username_too_long (ID: 02500151) Default Severity WARNING Log Message PPP CHAP username was truncated because it was too long Explanation PPP CHAP username was truncated because it was too long. Gateway Action chap_username_truncated Recommended Action Reconfigure the endpoints to use a shorter username.
2.21.17. password_too_long (ID: Chapter 2. Log Message Reference 02500351) Gateway Action pap_username_truncated Recommended Action Reconfigure the endpoints to use a shorter username. Revision Parameters tunnel_type 2.21.17. password_too_long (ID: 02500351) Default Severity WARNING Log Message PPP PAP password was truncated because it was too long Explanation PPP PAP password was truncated because it was too long.
2.21.20. authdb_error (ID: 02500502) Chapter 2. Log Message Reference 2.21.20. authdb_error (ID: 02500502) Default Severity ERROR Log Message Local database authentication error. PPP Authentication terminated Explanation There was an error while authenticating using a local user database. PPP Authentication terminated. Gateway Action authentication_terminated Recommended Action...
2.22. PPPOE Chapter 2. Log Message Reference 2.22. PPPOE These log messages refer to the PPPOE (PPPoE tunnel events) category. 2.22.1. pppoe_tunnel_up (ID: 02600001) Default Severity NOTICE Log Message PPPoE tunnel on <iface> established to <pppoeserver>. Auth: <auth>, IfaceIP: <ifaceip>, Downtime: <downtime> Explanation The PPPoE tunnel for the interface have been established.
2.23.4. unknown_pptp_auth_source Chapter 2. Log Message Reference (ID: 02700004) Revision Parameters rule remotegw callid 2.23.4. unknown_pptp_auth_source (ID: 02700004) Default Severity WARNING Log Message Unknown PPTP authentication source for <rule>! Remote gateway: <remotegw>, Call ID: <callid> Explanation The authentication source for the specified userauth rule found in the new configuration is unknown to the PPTP server.
2.23.7. mppe_required (ID: 02700007) Chapter 2. Log Message Reference another subsystem. Traffic can only be sent out on the PPTP server using the dynamic routes set up by the interface itself. Gateway Action drop Recommended Action Make sure there are no manually configured routes pointing to the PPTP server interface in the configuration.
2.23.10. unsupported_message (ID: Chapter 2. Log Message Reference 02700010) Explanation An PPTP session request has been sent on the control connection to the specified remote gateway. Gateway Action None Recommended Action None. Revision Parameters remotegw 2.23.10. unsupported_message (ID: 02700010) Default Severity WARNING Log Message Unsupported message type <type>...
2.23.13. pptp_session_up (ID: Chapter 2. Log Message Reference 02700013) Log Message PPP negotiation completed for session <callid> to <remotegw> on <iface>. User: <user>, Auth: <auth>, MPPE: <mppe>, Assigned IP: <assigned_ip> Explanation The PPP negotiation has completed successfully for this session. The specified interface, remote gateway and call ID identify the specific session.
2.23.15. session_idle_timeout (ID: Chapter 2. Log Message Reference 02700015) Parameters iface remotegw 2.23.15. session_idle_timeout (ID: 02700015) Default Severity WARNING Log Message PPTP session <callid> to <remotegw> on <iface> has been idle for too long. Closing it. Explanation A PPTP session has been idle for too long. Session will be closed. Gateway Action close_session Recommended Action...
2.23.25. malformed_packet (ID: Chapter 2. Log Message Reference 02700027) 2.23.24. pptp_no_userauth_rule_found (ID: 02700026) Default Severity WARNING Log Message Did not find a matching userauth rule for the incoming PPTP connection. Interface: <iface>, Remote gateway: <remotegw>. Explanation The PPTP server was unsuccessful trying to find a userauth rule matching the incoming PPTP connection.
2.24. REASSEMBLY Chapter 2. Log Message Reference 2.24. REASSEMBLY These log messages refer to the REASSEMBLY (Events concerning data reassembly) category. 2.24.1. ack_of_not_transmitted_data (ID: 04800002) Default Severity INFORMATIONAL Log Message TCP segment acknowledges data not yet transmitted Explanation A TCP segment that acknowledges data not yet transmitted was received.
2.24.4. memory_allocation_failure (ID: Chapter 2. Log Message Reference 04800005) Context Parameters Connection 2.24.4. memory_allocation_failure (ID: 04800005) Default Severity ERROR Log Message Can't allocate memory to keep track of a packet Explanation The gateway is unable to allocate memory to keep track of packet that was received.
2.24.8. maximum_connections_limit_reached Chapter 2. Log Message Reference (ID: 04800010) Log Message Maximum processing memory limit reached Explanation The reassembly subsystem has reached the maximum limit set on its processing memory. This will decrease the performance of connections that are processed by the reassembly subsystem. Gateway Action drop Recommended Action...
2.25. RULE Chapter 2. Log Message Reference 2.25. RULE These log messages refer to the RULE (Events triggered by rules) category. 2.25.1. ruleset_fwdfast (ID: 06000003) Default Severity NOTICE Log Message Packet statelessly forwarded (fwdfast) Explanation The packet matches a rule with a "fwdfast" action, and is statelessly forwarded.
2.25.4. rule_match (ID: 06000007) Chapter 2. Log Message Reference Packet Buffer 2.25.4. rule_match (ID: 06000007) Default Severity DEBUG Log Message RETURN action trigged Explanation A rule with a special RETURN action was trigged by an IP-rule lookup. This log message only appears if you explicitly requested it for the rule in question, and it is considered of DEBUG severity.
2.25.7. block127net (ID: 06000012) Chapter 2. Log Message Reference Packet Buffer 2.25.7. block127net (ID: 06000012) Default Severity WARNING Log Message Destination address is the 127.* net. Dropping Explanation The destination address was the 127.* net, which is not allowed according to the configuration. The packet is dropped. Gateway Action drop Recommended Action...
2.25.10. directed_broadcasts (ID: Chapter 2. Log Message Reference 06000031) 2.25.10. directed_broadcasts (ID: 06000031) Default Severity NOTICE Log Message Packet directed to the broadcast address of the destination network. Dropping Explanation The packet was directed to the broadcast address of the destination network, and the unit is configured to disallow this.
2.25.14. unhandled_local (ID: Chapter 2. Log Message Reference 06000060) Default Severity WARNING Log Message Packet dropped by rule-set. Dropping Explanation The rule-set is configured to drop this packet. Gateway Action drop Recommended Action If this is not the indended behaviour, modify the rule-set. Revision Context Parameters Rule Information...
2.27. SMTPLOG Chapter 2. Log Message Reference 2.27. SMTPLOG These log messages refer to the SMTPLOG (SMTPLOG events) category. 2.27.1. unable_to_establish_connection (ID: 03000001) Default Severity WARNING Log Message Unable to establish connection to SMTP server <smtp_server>. Send aborted Explanation The unit failed to establish a connection to the SMTP server. No SMTP Log will be sent.
2.27.5. rejected_connect (ID: Chapter 2. Log Message Reference 03000006) 2.27.4. receive_timeout (ID: 03000005) Default Severity WARNING Log Message Receive timeout from SMTP server <smtp_server>. Send aborted Explanation The unit timed out while receiving data from the SMTP server. No SMTP Log will be sent. Gateway Action abort_sending Recommended Action...
2.27.8. rejected_recipient (ID: Chapter 2. Log Message Reference 03000009) Log Message SMTP server <smtp_server> rejected sender <sender>. Send aborted Explanation The SMTP server rejected the sender. No SMTP Log will be sent. Gateway Action abort_sending Recommended Action Verify that the SMTP server is configured to accept this sender. Revision Parameters smtp_server...
2.28.2. demo_mode (ID: 03200021) Default Severity ALERT Log Message This copy of D-Link DFL-160 is in DEMO mode. Firewall core will halt in <time> seconds Explanation The unit is running in DEMO mode, and will eventually expire. Install a license in order to avoid this.
2.28.11. port_hlm_conversion (ID: Chapter 2. Log Message Reference 03200302) Gateway Action None Recommended Action None. Revision Parameters reason localip destip port_base port_end 2.28.11. port_hlm_conversion (ID: 03200302) Default Severity NOTICE Log Message Using High Load Mode for Local IP <localip> Destination IP <destip> pair Explanation Mode for Local IP - Destination IP pair has changed to High Load...
2.28.14. log_messages_lost_due_to_log_buffer_exhaust Chapter 2. Log Message Reference (ID: 03200401) Explanation Due to extensive logging, a number of log messages was not sent. Gateway Action None Recommended Action Examine why the unit sent such a large amount of log messages. If this is normal activity, the "LogSendPerSec"...
2.28.17. disk_cannot_remove_file (ID: Chapter 2. Log Message Reference 03200601) would cause bi-directional communication failure. Revision Parameters localcfgver remotecfgver timeout 2.28.17. disk_cannot_remove_file (ID: 03200601) Default Severity CRITICAL Log Message Failed to remove <file>, bi-directional communication will now probably be impossible Explanation The unit failed to remove the new, faulty, configuration file.
2.28.20. disk_cannot_rename (ID: Chapter 2. Log Message Reference 03200604) Parameters old_cfg 2.28.20. disk_cannot_rename (ID: 03200604) Default Severity ERROR Log Message Failed to rename <cfg_new> to <cfg_real> Explanation The unit failed to rename the new configuration file to the real configuration file name. Gateway Action None Recommended Action...
2.28.24. shutdown (ID: 03201000) Chapter 2. Log Message Reference Default Severity NOTICE Log Message Configuration <localcfgver><remotecfgver> verified for bi-directional communication Explanation The new configuration has been verified for communication back to peer, and will now be used as the active configuration. Gateway Action None Recommended Action...
2.28.27. config_activation (ID: Chapter 2. Log Message Reference 03201020) Log Message Shutdown aborted. Core file <core> missing Explanation The unit was issued a shutdown command, but no core executable file is seen. The shutdown process is aborted. Gateway Action shutdown_gateway_aborted Recommended Action Verify that the disk media is intact.
2.28.35. activate_changes_failed (ID: Chapter 2. Log Message Reference 03204000) Gateway Action disallow_admin_access Recommended Action None. Revision Parameters authsystem username [server_ip] [server_port] [client_ip] [client_port] 2.28.35. activate_changes_failed (ID: 03204000) Default Severity NOTICE Log Message Bidirectional confirmation of the new configuration failed, previous configuration will be used Explanation The unit failed to establish a connection back to peer, using the new...
2.28.38. date_time_modified (ID: Chapter 2. Log Message Reference 03205000) <config_system> <client_ip>. Explanation The new configuration has been rejected. Gateway Action reconfiguration_using_old_config Recommended Action None. Revision Parameters username userdb" client_ip config_system 2.28.38. date_time_modified (ID: 03205000) Default Severity NOTICE Log Message The local Date and Time has been modified by <user>. Time and Date before change: <pre_change_date_time>.
2.28.41. admin_login_internal_error Chapter 2. Log Message Reference (ID: 03206002) Default Severity WARNING Log Message Administrative user <username> not allowed access via <authsystem> Explanation The user does not have proper administration access to the configuration system. Gateway Action disallow_admin_access Recommended Action None.
2.29. TCP_FLAG Chapter 2. Log Message Reference 2.29. TCP_FLAG These log messages refer to the TCP_FLAG (Events concerning the TCP header flags) category. 2.29.1. tcp_flags_set (ID: 03300001) Default Severity NOTICE Log Message The TCP <good_flag> and <bad_flag> flags are set. Allowing Explanation The possible combinations for these flags are: SYN URG, SYN PSH, SYN RST, SYN FIN and FIN URG.
2.29.7. tcp_flag_set (ID: 03300009) Chapter 2. Log Message Reference Recommended Action If any of these combinations should either be ignored or having the bad flag stripped, specify this in configuration, in the "Settings" sub system. Revision Parameters good_flag bad_flag Context Parameters Rule Name Packet Buffer 2.29.7.
2.29.12. rst_out_of_bounds (ID: Chapter 2. Log Message Reference 03300015) Context Parameters Rule Name Connection Packet Buffer 2.29.12. rst_out_of_bounds (ID: 03300015) Default Severity WARNING Log Message Originator RST seq <seqno> is not in window <winstart>...<winend>. Dropping Explanation The RST flag sequence number is not within the receiver window. Dropping packet.
2.29.15. rst_without_ack (ID: Chapter 2. Log Message Reference 03300018) Log Message TCP acknowledgement <ack> is not in the acceptable range <accstart>-<accend>. Dropping Explanation A TCP segment with an unacceptable acknowledgement number was received during state SYN_SENT. The packet will be dropped. Gateway Action drop Recommended Action...
2.29.17. tcp_recv_windows_drained Chapter 2. Log Message Reference (ID: 03300022) Context Parameters Rule Name Connection Packet Buffer 2.29.17. tcp_recv_windows_drained (ID: 03300022) Default Severity CRITICAL Log Message large receive windows. Maximum windows: <max_windows>. Triggered <num_events> times last 10 seconds. Explanation The TCP stack could not accept incomming data since it has run out of large TCP receive windows.
2.29.20. tcp_seqno_too_low_with_syn Chapter 2. Log Message Reference (ID: 03300025) Gateway Action None Recommended Action None. Revision 2.29.20. tcp_seqno_too_low_with_syn (ID: 03300025) Default Severity DEBUG Log Message TCP sequence number <seqno> is not in the acceptable range <accstart>-<accend>. Dropping Explanation A TCP segment with an unacceptable sequence number was received. The packet will be dropped.
2.30.10. bad_tcpopt_length (ID: Chapter 2. Log Message Reference 03400012) 2.30.9. bad_tcpopt_length (ID: 03400011) Default Severity WARNING Log Message Type <tcpopt> claims length=<len> bytes, avail=<avail> bytes. Dropping Explanation The TCP Option type does not fit in the option space. Dropping packet. Gateway Action drop Recommended Action...
2.31. TIMESYNC Chapter 2. Log Message Reference 2.31. TIMESYNC These log messages refer to the TIMESYNC (Firewall time synchronization events) category. 2.31.1. synced_clock (ID: 03500001) Default Severity NOTICE Log Message The clock at <oldtime>, was off by <clockdrift> second(s) and synchronized with <timeserver>...
2.32. TRANSPARENCY Chapter 2. Log Message Reference 2.32. TRANSPARENCY These log messages refer to the TRANSPARENCY (Events concerning the Transparent Mode feature) category. 2.32.1. impossible_hw_sender_address (ID: 04400410) Default Severity WARNING Log Message Impossible hardware sender address 0000:0000:0000. Dropping. Explanation Some equipment on the network is sending packets with a source MAC address of 0000:0000:0000.
2.32.10. invalid_stp_frame (ID: Chapter 2. Log Message Reference 04400419) 2.32.10. invalid_stp_frame (ID: 04400419) Default Severity WARNING Log Message Incomming STP frame from <recvif> dropped. Reason: <reason> Explanation An incomming Spanning-Tree frame has been dropped since it is either malformed or its type is unknown. Supported Spanning-Tree versions are STP, RSTP, MSTP and PVST+.
Page 337
2.32.13. invalid_mpls_packet (ID: Chapter 2. Log Message Reference 04400422) Default Severity WARNING Log Message Incomming MPLS packet on <recvif> dropped. Reason: <reason> Explanation An incomming MPLS packet has been dropped since it was malformed. Gateway Action drop Recommended Action If the packet format is invalid, locate the unit which is sending the malformed packet.
2.33. USERAUTH Chapter 2. Log Message Reference 2.33. USERAUTH These log messages refer to the USERAUTH (User authentication (e.g. RADIUS) events) category. 2.33.1. accounting_start (ID: 03700001) Default Severity INFORMATIONAL Log Message Successfully received RADIUS Accounting START response from RADIUS Accounting server Explanation The unit received a valid response to an Accounting-Start event from the Accounting Server.
2.33.4. invalid_accounting_start_server_response Chapter 2. Log Message Reference (ID: 03700004) Recommended Action Verify that the RADIUS Accounting server daemon is running on the Accounting Server. Revision Context Parameters User Authentication 2.33.4. invalid_accounting_start_server_response (ID: 03700004) Default Severity ALERT Log Message Received an invalid RADIUS Accounting START response from RADIUS Accounting server.
2.33.7. failed_to_send_accounting_stop Chapter 2. Log Message Reference (ID: 03700007) Accounting-Start event was received from the Accounting Server. Gateway Action logout_user Recommended Action Verify that the RADIUS Accounting server is properly configured. Revision Context Parameters User Authentication 2.33.7. failed_to_send_accounting_stop (ID: 03700007) Default Severity ALERT Log Message...
2.33.10. no_accounting_stop_server_response Chapter 2. Log Message Reference (ID: 03700010) 03700009) Default Severity WARNING Log Message Received a RADIUS Accounting STOP response with an Identifier mismatch. Ignoring this packet Explanation The unit received a response with an invalid Identifier mismatch. This can be the result of a busy network, causing accounting event re-sends.
2.33.12. failure_init_radius_accounting Chapter 2. Log Message Reference (ID: 03700012) Revision Context Parameters User Authentication 2.33.12. failure_init_radius_accounting (ID: 03700012) Default Severity ALERT Log Message Failed to send Accounting Start to RADIUS Accounting Server. Accounting will be disabled Explanation The unit failed to send an Accounting-Start event to the Accounting Server.
2.33.15. user_timeout (ID: 03700020) Chapter 2. Log Message Reference Recommended Action Verify that a route exists from the unit to the RADIUS Accounting server, and that it is properly configured. Revision Context Parameters User Authentication 2.33.15. user_timeout (ID: 03700020) Default Severity NOTICE Log Message User timeout expired, user is automatically logged out...
2.33.21. invalid_accounting_interim_server_response Chapter 2. Log Message Reference (ID: 03700053) Default Severity ALERT Log Message Did not receive a RADIUS Accounting Interim response. User statistics might not have been updated on the Accounting Server Explanation The unit did not receive a response to an Accounting-Interim event from the Accounting Server.
2.33.23. relogin_from_new_srcip (ID: Chapter 2. Log Message Reference 03700100) Context Parameters User Authentication 2.33.23. relogin_from_new_srcip (ID: 03700100) Default Severity WARNING Log Message User with the same username is logging in from another IP address, logging out current instance Explanation A user with the same username as an already authenticated user is logging in.
2.33.26. bad_user_credentials (ID: Chapter 2. Log Message Reference 03700104) Context Parameters User Authentication 2.33.26. bad_user_credentials (ID: 03700104) Default Severity NOTICE Log Message Unknown user or invalid password Explanation A user failed to log in. The entered username or password was invalid. Gateway Action None Recommended Action...
2.33.30. challenges_not_supported Chapter 2. Log Message Reference (ID: 03700108) Default Severity WARNING Log Message Denied access according to UserAuthRules rule-set Explanation The user is not allowed to authenticate according to the UserAuthRules rule-set. Gateway Action None Recommended Action None. Revision Context Parameters User Authentication 2.33.30.
2.33.33. ldap_session_new_out_of_memory Chapter 2. Log Message Reference (ID: 03700401) Explanation A user logged out, and is no longer authenticated. Gateway Action None Recommended Action None. Revision Context Parameters User Authentication 2.33.33. ldap_session_new_out_of_memory (ID: 03700401) Default Severity ALERT Log Message Out of memory while trying to allocate new LDAP session Explanation The unit failed to allocate a LDAP session, as it is out of memory.
2.33.43. disallow_clientkeyexchange Chapter 2. Log Message Reference (ID: 03700501) Parameters client_ip 2.33.43. disallow_clientkeyexchange (ID: 03700501) Default Severity ERROR Log Message SSL Handshake: Disallow ClientKeyExchange. Closing down SSL connection Explanation The SSL connection will be closed because there are not enough resources to process any ClientKeyExchange messages at the moment.
2.33.46. bad_changecipher_msg (ID: Chapter 2. Log Message Reference 03700504) Parameters client_ip 2.33.46. bad_changecipher_msg (ID: 03700504) Default Severity ERROR Log Message SSL Handshake: Bad ChangeCipher message. Closing down SSL connection Explanation The ChangeCipher message (which is a part of a SSL handshake) is invalid, and the SSL connection is closed.
2.33.50. unknown_ssl_error (ID: Chapter 2. Log Message Reference 03700508) 2.33.49. bad_alert_msg (ID: 03700507) Default Severity ERROR Log Message Bad Alert message. Closing down SSL connection Explanation The Alert message (which can be a part of a SSL handshake) is invalid, and the SSL connection is closed. Gateway Action ssl_close Recommended Action...
2.33.53. sent_sslalert (ID: 03700511) Chapter 2. Log Message Reference Default Severity ERROR Log Message Received SSL Alert. Closing down SSL connection Explanation A SSL Alert message was received during an established SSL connection, and the SSL connection will be closed. Gateway Action close Recommended Action...