Skip to content

NAS log formats ​

The collector selects a parser from the registered device's vendor setting and normalizes each event into the same searchable NAT record.

NetElastic ​

NetElastic sends RFC 5424 structured syslog events. The collector stores the timestamp, NAS hostname, event type (PTADD or PTDEL), username, inside IP, public IP and public-port range.

text
<134>1 2026-07-16T20:29:34.312Z Dream-100G NAT 27859 PTDEL [nprng TRIG="AUTO" USERNAME="alindg10" ISADDR="100.64.19.216" XSADDR="144.79.234.13" PORTMN="5000" PORTMX="5999"]

Use TCP for compliance-grade delivery when the device supports it.

MikroTik ​

MikroTik uses firewall logs with a post-NAT NAT (inside:port->public:port) block. Only entries containing that block are stored. Because RouterOS does not report a teardown, each accepted event is stored as PTADD with a single public port.

routeros
/ip firewall filter
add chain=forward action=log log-prefix="CGNAT" connection-state=established \
    connection-nat-state=srcnat connection-bytes=0-2000 src-address-list=dream
add chain=forward action=log log-prefix="CGNAT" connection-state=new \
    connection-nat-state=srcnat src-address-list=dream

/system logging action
add name=SYSLOG target=remote remote=<collector-ip> remote-port=514 \
    remote-log-format=syslog syslog-time-format=iso8601 syslog-facility=daemon
/system logging add topics=firewall action=SYSLOG

Do not add log=yes to these rules: action=log already produces the log entry.

Dream Radius ISP CRM