Platform CRM & Subscribers Billing & Finance Optical-Fiber NMS RADIUS & Provisioning AI Suite AI Network Planner Services IPTV VoIP & Voice Hotspot XRTG Graphing Syslog Operations Ticketing & Jobs Inventory Resellers Reports & Analytics Notifications Apps Customer App Xelynx TV More Pricing Help Center Sign in Start free 15-day trial

Module — Syslog

Every log, matched to the right subscriber.

Centralised syslog ingestion powered by VictoriaLogs. Every srcnat log lands in one console, and every source IP is resolved to the customer service behind it — so you go from an event to an account in seconds, not spreadsheets.

7d
of searchable range — last 1h, 4h, 24h or 7d, switched in a click
1
destination for every srcnat log, ingested by VictoriaLogs
3
filters — IP address, port and protocol — to isolate any connection

01 — The console

Search every log, fast.

One console for all your srcnat traffic, backed by a purpose-built, high-throughput log store that keeps queries quick as volume grows.

From all traffic to one event

Start broad, then narrow fast. The console reads across everything your routers send and cuts straight to the handful of records that answer the question.

  • Filter by IP, port and protocol — isolate exactly the connections in question
  • Time ranges that match the question — last 1h, 4h, 24h or 7d, one click apart
  • Powered by VictoriaLogs — centralised ingestion with search that stays responsive at scale
Syslog console with IP, port, protocol and time-range filters
Syslog console srcnat entries filtered by IP, port, protocol and time range

02 — Per subscriber

Logs, where you already support the customer.

Every account in the CRM carries its own Syslog tab. Open a customer and the relevant entries are already filtered to that subscriber — no copying IPs between tools, no second system to learn.

  • A Syslog tab on every account — investigation starts where support happens
  • Auto-matched to their service — only this subscriber’s traffic, nothing else
  • Context for support and abuse handling — answer what a connection was without leaving the CRM
Explore the CRM
Per-customer Syslog tab inside the CRM
Customer Syslog tab entries pre-filtered to this subscriber’s service

03 — Setup

From router to record in three steps.

A dedicated Setup Guide tab walks you through pointing routers and NAS at the collector, so srcnat logs start flowing without guesswork.

01

Point your gear at the collector

The Setup Guide covers routers and NAS step by step, built around srcnat logging so subscriber matching works out of the box. One destination to remember.

02

VictoriaLogs ingests centrally

Every entry lands in one purpose-built, high-throughput store — designed so searches stay responsive as your log volume grows.

03

Entries match as they land

Each record is correlated to the active subscriber service at that moment and surfaced on the account’s Syslog tab. There is no spreadsheet step.

04 — CGNAT traceability

One public address, hundreds of subscribers.
One accountable answer.

Behind CGNAT, a source IP alone isn’t an answer. Xelynx logs the full NAT translation — the inside subscriber, the shared public IP and the assigned port — and ties every record back to the account behind it.

Three srcnat log streams funnel into the matcher, where the NAT line 10.8.4.2:4431 to 102.44.x.x is resolved to the subscriber account behind it
NAT → subscriber raw srcnat lines stream into the matcher and come out tied to the one account responsible
T·01

Every translation, logged

Each NATted connection is recorded as it is translated. When hundreds of subscribers share one address, that mapping is the only way to know who was who.

T·02

Public IP + port → subscriber

Take the IP, port and timestamp from an abuse report, court request or upstream notice, and trace it straight to the one subscriber responsible.

T·03

Time-accurate to the session

Matching respects when a service actually held the address, so each record is attributed to whoever was behind the connection at that exact moment.

Why it matters
01 Abuse & legal requests Respond to DMCA, law-enforcement and upstream complaints with an evidence trail that turns “an IP did this” into “this account did this”.
02 Zero manual correlation Entries are matched the moment they land — no cross-referencing lease tables by hand, no guessing which session held an address at a given second.

05 — At a glance

The module, specified.

The store, the filters, the matching and where it all surfaces — everything the Syslog module ships with.

AreaWhat you get
Log storeVictoriaLogs — centralised, high-throughput ingestion that stays fast as volume grows
Log sourcesrcnat translations from your routers and NAS
Search filtersIP address, port and protocol
Time rangesLast 1h, 4h, 24h or 7d
MatchingSource IP resolved to the active subscriber service, accurate to the session
Where it surfacesThe central console and a Syslog tab on every customer account
SetupA guided Setup Guide tab for routers and NAS
VictoriaLogs ingestion srcnat log view Source IP → subscriber matching Filter by IP address Filter by port Filter by protocol Last 1h / 4h / 24h / 7d Per-customer Syslog tab Setup guide for routers & NAS srcnat translation logging CGNAT subscriber traceability Public IP + port → account Abuse & legal response trail

Get started

From a public IP
to the account behind it.

Centralise your syslog, match every connection to a subscriber, and search any range from the last hour to the last week. Free for 15 days, no card required.