System Log & Connection Tracking
The System Log section provides real-time logging and connection monitoring tools. It lets administrators track system events, keep a record of network connections, and forward logs to an external Syslog server. This page explains each feature and how to configure it.
Features
- Log Timezone – Set the timezone used for log timestamps, automatically or manually.
- Traffic Monitor – Log every new connection passing through the gateway, filtered by protocol, port and interface.
- Syslog Server Integration – Forward logs to a remote Syslog server for long-term storage and compliance.
- Real-Time Log View – View live logs and filter them by category.
Configuring Log Timezone
Log timestamps are only as accurate as the device clock. If you keep logs as records, make sure the time is set correctly under Time & Region.
What is Traffic Monitor (Conntrack)?
Conntrack (connection tracking) is the gateway's table of active network connections. The firewall, NAT and the hotspot all depend on it, so it is always running. On its own it keeps no history: each entry disappears when its connection closes.
Traffic Monitor adds logging on top of it. When enabled, the gateway writes a log entry for each new connection that matches your filters, giving you a record of which device connected to which address, and when. These entries appear under the Conntrack log category.
Is Connection Logging Legally Required?
It depends on where the network is installed and who uses it. Some countries require businesses that offer internet access to the public, such as hotels, restaurants and cafés, to keep records that identify the source of each connection for a fixed period. Others have no such requirement, or apply it only to telecom operators and regulated sectors. Where rules exist, they often treat access offered to the public differently from networks used only by employees.
Connection logs identify devices and the people using them, so in many countries they count as personal data. If you keep them, state what you keep and for how long in your privacy notice.
Administrators are responsible for knowing and complying with the regulations that apply where the network is deployed. If you are unsure, ask a local legal advisor before deciding whether to keep connection logs and for how long.
If you need to keep connection records:
- Enable Traffic Monitor with All Ports on an interface that includes the guest network. Filtering by port gives an incomplete record.
- Forward the Conntrack, Hotspot and DHCP logs to a Syslog server. Together they show which device and guest session used an IP address at a given time.
- Define a retention period based on legal and organizational requirements, and delete logs when it ends.
- Avoid collecting or keeping more data than you need.
Enabling Traffic Monitor
-
Navigate to System > System Log.
-
Under Traffic Monitor, toggle Enable Traffic Monitor.
-
Select a Protocol (TCP, UDP, or both).
-
Choose a Port Option:
- All Ports
- HTTP only (port 80)
- HTTPS only (port 443)
- Custom Ports (enter specific ports manually)
-
Select an Interface (All Interfaces, Guest only, or Local only).
-
Click Save to apply changes.
Traffic Monitor writes one log entry for every new connection, so on busy networks it can increase CPU and memory load. Narrow the ports or interface if you only need part of the traffic.
What a Log Entry Contains
Each Traffic Monitor entry is stored with its date and time and describes the first packet of a new connection, for example:
forward: in:hotspot-bridge out:ether1, src-mac 1a:1c:ed:73:7d:10, proto TCP (SYN), 10.0.0.240:43634->157.240.234.61:443, len 60
- in / out – the interface the connection came from (here the guest network) and the one it left through.
- src-mac – the MAC address of the guest's device.
- proto – the protocol (TCP or UDP).
- source → destination – the device's IP address and port, followed by the destination IP address and port.
What is not recorded:
- Website addresses (URLs), page content, or anything the guest sends or receives. Traffic Monitor records addresses and ports only.
- The public IP address seen on the internet. The log shows the device's private address on your network. If the gateway is installed behind another router that also performs NAT, that router's records may be needed to match a request that refers to a public IP address and port.
To find out which guest used an IP address at a given time, match the source IP and time against the Hotspot log (logins and logouts) and the DHCP log (IP lease assignments).
Configuring Syslog Server for Remote Logging
Syslog is sent over UDP, which does not confirm delivery: entries sent while the server is unreachable are lost. For records you are required to keep, use a server that is always on, keeps its clock synchronized, and deletes logs at the end of your retention period.
Viewing and Filtering Logs in Real Time
Troubleshooting & FAQs
Logs not updating
- Refresh the page or wait for the next update cycle (30 seconds).
High CPU usage after enabling Traffic Monitor
- Limit monitoring to specific ports or to a single interface.
- Disable Traffic Monitor if you don't need connection records. This only stops the logging: connection tracking keeps running, so the firewall, NAT and hotspot are not affected.
Does Traffic Monitor record the websites guests visit?
- No. It records IP addresses and ports only, never URLs or content. See "What a Log Entry Contains" above.
Important Notes
- Logs on the device are kept in memory and are lost when it restarts.
- For long-term storage, audits or compliance, forward logs to a Syslog server.
- Filter logs by category to focus on specific events or troubleshooting needs.




