Dashboard
Network detail
Network throughput
Routers — live traffic
Top consumers
Radio backhauls
Saturation risks
Latency by client
Where the delay comes from (by segment: access, next hop, internet)
Load by node
Queues by node
Selection
Health over time
Who consumes
Which services the traffic comes from
Where the traffic goes
Who talks to whom, client by client
Destinations reached
Find an IP
Restrictions on destinations (block or cap a service for some clients) have their own page: Rules.
Service catalogue
Advanced: NetFlow exporters
Rules in force
Write a new rule
Links: throughput, capacity, source
The plan belongs to each client. A site (PoP)
is only a connection point: it has a capacity, not a plan. A client's plan is pushed by
your billing through the API (PUT /model/v1/services, as often as
needed), or set here. The last one written wins. A client pushed without a
rate gets the default plan; a client only detected on a router is observed, not
capped, unless Settings applies the default plan to detected clients too.
Default plan
Clients
Waiting for first connection
Plans received for logins that have never been seen connected yet (a subscriber created in your management interface before its first PPPoE session). Each plan is applied by itself as soon as the subscriber connects. A login that stays here may be misspelt.
Packages pushed by the API
Commercial reading of the measurements: who is likely to cancel (poor experience, usage collapsing, silent line), who is ready to be sold a bigger plan (lives at its ceiling with a good experience), and how many more subscribers each site can take before quality drops. It compares the chosen period with the one before, so it needs history.
At risk of leaving
Ready for a bigger plan
Sites and access points: room for more subscribers
Every subscriber: plan, usage, experience
Bandwidth schedules
New schedule
All modes
New mode
Add a client
Declared static-IP clients
Clients by VLAN
Router health
Connect a router (PoP)
Ubiquiti UISP
Ubiquiti antennas (radio capacity)
Radio health: access points and their CPEs
Add an antenna
Inventory
Known sites
Polled routers
Create a key
Documentation
Authentication, adding a router, client plans, forced limits and boosts, static-IP clients, billing integration (Preseem-compatible), consumption, measurements, errors, and the full reference of every endpoint. Examples are ready to copy, with the address of this server.
How freeQoS works, end to end: architecture, required resources, step-by-step installation, network flows, measurements, NetFlow, CAKE shaping, security, operations, troubleshooting and every setting. Also as a PDF to send or print.