Everything, in one router
Each part knows about the others: a service creates the VLAN, the address, the DHCP entry, the shaping and the OLT’s service port in one step — and the alarms watch all of it.
Subscribers
The router is the subscribers’ gateway: addresses, leases, speeds and end dates.
IPoE, PPPoE or both
Choose how your subscribers connect when you install: IPoE (DHCP) and PPPoE, with logins kept on the router or asked from your billing’s RADIUS — tested with Splynx and MikroWisp; and both on the same router while you move customers over.
One VLAN per PON port
Each PON port gets its own VLAN inside the OLT’s S-VLAN; each ONT one fixed address, by DHCP Option 82.
DHCPv4 and DHCPv6
Static leases, pools, router advertisements and IPv6 prefix delegation (IA_PD) with routes kept in step.
Plans and speeds
Speed plans enforced on the OLT by default, or by the router per client; a plan change applies at once, everywhere.
Suspend, resume, end dates
Cut or restore a client in one call; a service end date is enforced by the router itself.
Promotions
Saturday 2×, every night 3×, a weekend or a date range: more speed by plan and time, with an optional ceiling — applied on the router, or on a Huawei OLT’s own traffic tables, and back to normal by themselves.
Shaped where you choose
Each client is shaped by the OLT (the default) or by the router — chosen per client through the API or the CLI.
Mass import
Plans, networks, clients and services from CSV files in the router’s own format: every line checked first, then imported in one go.
The OLTs
Huawei OLTs (MA5600T family) controlled over SNMP by the router’s own OLT driver.
ONTs and service ports
ONTs added and removed, with their service and the plan’s speed, by the same call that creates the service.
Kept safe
Changes are saved on the OLT by themselves; its configuration is backed up and versioned.
The fiber, watched
Every ONT’s light and errors are read around the clock, with months of history, and you are warned before clients call.
A live console
Every command sent to an OLT and its reply, live in the browser — nothing hidden; a change made over SNMP shows each of its steps.
Driven over SNMP
Provisioning and reading the OLT go over SNMP, with no CLI login. The CLI stays as the backup.
Guarded
Another operator's ONTs and VLANs on a shared OLT are never touched, and one address is never given to two subscribers.
Carrier features
What a real ISP needs at the edge.
CGNAT with fixed port blocks
Each client gets a fixed public IP and port range; mappings are logged for lawful requests.
NAT pools and port forwarding
Dynamic SNAT pools and inbound DNAT, managed by API.
Anti-spoofing
Each client can only send from the address, VLAN and MAC it was given — IPv4, IPv6 and ARP.
DNS
The resolvers the clients get and the router uses, set in one place.
BGP with your upstreams
Your address blocks announced to one or more upstreams, a primary and a backup with automatic failover, a default route or the full table, and a blackhole for an address under DDoS; BFD sees a dead upstream in under a second, RPKI drops routes with a false origin — only your prefixes can ever go out.
OSPF and iBGP
OSPF with the other routers of your network, and iBGP between several Super Routers. Every routing change is undone by itself unless confirmed within 120 seconds.
Looking glass
Everything a looking glass does, built in — IPv4 and IPv6, in the monitor, the CLI and the API.
Ping and mtr
From the router to any address or name, from any of its own addresses: loss and latency, and every hop with its AS number from your own BGP table.
Any route, every path
For an address or a prefix: every path the router knows, the best one marked, with AS path, communities, local-pref, MED and origin.
Sessions and peers
Each BGP session’s state and routes; what you announce to a peer and what it sends you.
Your prefixes, everywhere
Each of your prefixes checked against every upstream: announced, or — in red — missing.
Only reads, never breaks
No shell, checked targets, time limits, two tests at a time: nothing in the looking glass can change the router.
Public looking glass
Planned: a read-only page for your customers and peers — the address to list in PeeringDB — with your internal routes hidden.
The authorities’ questions
Answered in a second, from the router itself — off until you switch it on.
Who was this IP and port
Public address, port and time: the subscriber who held them, with name, contract, MAC and ONT serial — even months later.
No connection logs needed
The CGNAT gives each subscriber a fixed port block, so only who held which block, and when, is recorded: a few rows a day, not billions. Where the law asks for every connection: level 2, on a DTVSOL Super Keeper — your own server, free with the router.
Tamper-evident
Every record and every search is sealed: any change or removal, even directly in the database, is detected — `dtvsol lawful verify` proves it.
Kept, then deleted
12 months by default (6 to 120), then deleted by itself; every search logged with its case number; never in a backup that leaves the router.
DNS and blocking
The subscribers’ DNS answered by the router, and the authorities’ lists enforced.
Its own resolver
A caching resolver on the router, on from the first start and handed out by DHCP — never an open resolver: only the networks it serves may ask.
Blocked domains
A domain and everything under it answered as not existing, or with your notice page. International names welcome.
Blocked addresses
Addresses, networks and ranges dropped both ways, at full speed however long the list, with a counter per entry.
Any authority’s format
Lines, CSV (its delimiter, its column) or a regular expression; checked line by line before import, fetched again on a timer, every change in the history.
TR-069: inside the ONT
The subscribers’ ONTs and routers report to the router and take its commands — its own ACS, off until you switch it on.
Every device, every parameter
Model, firmware and the whole parameter tree of each ONT, read on its first call and matched to its subscriber by address or serial.
Commands from the office
Wi-Fi name and password, reboot, factory reset, any parameter — from the monitor, the API or your billing, run at once when the device can be woken.
Kept apart
Device management runs apart from the routing: thousands of devices talk to it, never to the part of the router that routes and translates.
Learning new models
A guided page learns an unknown ONT model in a few simple steps and keeps its profile; the model library shares the profiles with every Super Router.
Any ONT registers on the OLT. For TR-069 control (Wi-Fi from your billing), the Super Router uses a shared, DTVSOL-signed library of ONT models. When a client brings a model that isn’t in it yet, the router’s learn mode guides a technician through a few steps at the ONT, finds the right settings itself and proves them, and — if you allow it — sends the result to DTVSOL, which reviews it and shares it with every router.
Operations
Tools for the people who keep the network running.
Alarms by area
OLT, clients’ ONUs, network, server, services: checked every minute, raised and cleared with a history.
The 24/7 wall
A page for a TV in the support room, with display keys that never expire and can be revoked.
Doctor
`dtvsol doctor` checks every part of the router — QinQ MTU, CGNAT port blocks and rules, duplicate addresses, what survives a reboot, the OLT against the router — and says what to type to fix each one.
Backups and versions
Every configuration change is a version; daily backups, and an encrypted copy off the router with the DTVSOL Backup agent.
Notifications
Alarms sent by email, WhatsApp, Telegram and SMS to the people you choose — set in the monitor, the API or the CLI.
Alarm on a failed change
A change the router could not apply raises an alarm at once — nothing fails in silence.
Drift check
The router compares the running network, firewall, DHCP and routing with its database, shows what differs, and one command puts it back.
Speedtest server
An Ookla speed test server on your router, installed on request, with a free Let’s Encrypt certificate (it needs a host name that points to the router) or your own: your clients measure the speed to you. A listing on speedtest.net needs your own registration with Ookla. Switched on from the monitor, the API or the CLI.
Safe network changes
The router’s own network is kept in its database and applied with a safety net.
Shown before it runs
Every change shows exactly what differs and what it would take away.
Undone by itself
Unless you confirm within 120 seconds, the change is put back by itself — even if the router restarts meanwhile.
Cannot lock you out
A change that would remove your own access, an SSH session’s or the default route is refused.
Roles and an audit log
Admins change everything, viewers look, the office works with the clients — enforced by the router; every change is in the audit log with who made it, how and from where.
Integration
Your billing keeps working.
REST API
Clients, services, plans, OLTs, alarms and health — JSON over HTTP, with an API key and an allow-list.
MikroTik-compatible API
Compatible with the RouterOS API, tested with Splynx and MikroWisp.
SNMP
The router’s interfaces and clients for your existing monitoring.
Licence and updates
Licensed per router and renewed automatically — you are warned 14 days ahead if anything needs attention; new versions delivered and tested for you.
Works with Splynx — RADIUS and MikroTik API, tested: logins, speeds from its plans, traffic accounting (RADIUS or NetFlow), and a block in Splynx shows your suspended page. Start with your billing as it is, then move to the native integration. Set up Splynx →
Works with MikroWisp — MikroTik API or RADIUS, tested: PPPoE logins and IPoE leases, speeds from its plans (queues, leases or PCQ), traffic by Traffic Flow (only its own customers), a cut in MikroWisp shows your suspended page and its on-screen notice your notice page. Set up MikroWisp →
Sell your last mile: several operators can share your OLTs, each with its own Super Router. Each gets its own S-VLAN and manages only its own subscribers; the router refuses to touch another operator's ONTs. (Huawei OLTs; ZTE and V-SOL with their drivers.) One router serving several ISPs, and handing a PON over to another ISP's own BNG (bitstream), are on the roadmap.