This is an old revision of the document!


Log Configuration

The log configuration page controls what type of information to record in the unit's different logs and where to send/store those logs.

Severity levels are:

  • Emergency
  • Alert
  • Critical
  • Error
  • Warning
  • Notice
  • Info
  • Debug

System Log

The system log records generic events that have occurred to the unit.

Usually debug level messages are not logged, to keep the system log clean and readable. When support requests you enable Debug messages in system log to record debug level messages too.

If you have the Internet filter enabled you can log web access attempts blocked by it by enabling Log blocked access attempts.

The system log can be viewed on the system log page or forwarded to various receivers, see below.

Firewall Log

The firewall log records information about packets received and sent by the unit.

Usually the firewall log is turned off - no packets are logged.
:!: Enabling the firewall log may affect performance/throughput of the unit, especially when logging all packets and/or extensive details about each packet. At peak load, some packets may be left out from the log.

If you enable firewall logging, you should consider selecting Show rejected packets as that setting will log all packets stopped by the firewall, but not every single packet passing through.

:!: Try to limit logging by selecting as low log level and verbosity level as possible.

You can use the firewall log to see packet data (headers) too. A valuable tool for solving communication problems. You can log up to 64 bytes of packet contents (Log raw data) in hex or ASCII, and exclude common protocol (IP/TCP/UDP) headers so that the 64 logged bytes really are the data you are interested in.

Packets not logged

Multicast UDP packets are not logged, to avoid clogging down the firewall log. One single IPTV multicast channel can contain 500 packets per second! You can enable logging them using Log UDP multicast packets, though.

The communication with Internet Gate's own built-in web server is not logged. It can only be enabled using manually written Additional rules.

The firewall log can be viewed on the firewall log page or forwarded to various receivers, see below.

web_gui/log_configuration_page.1289213135.txt.gz · Last modified: 2010/11/08 11:45 by tibor
CC Attribution-Noncommercial-Share Alike 3.0 Unported
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0