Culmen RADIUS & Quota Engine

Standalone authentication and fair-use enforcement for MikroTik networks. Deploy alongside your existing billing system.

What it does

• PPPoE authentication via RADIUS, with per-plan rate limits
• Daily fair-use quota with automatic throttle on breach
• Monthly quota layer on top of the daily meter
• Cache-exempt metering — traffic served from local caches runs outside the plan speed and is credited back, daily and monthly. Services you choose to count, such as paid streaming, run at full speed and still count
• Free windows — unmetered hours with their own speed ladder, applied and reverted on schedule
• Live speed changes — windows, upgrades, throttle and release pushed to the running session over RADIUS CoA, without disconnecting anyone
• Separate metering windows per plan type — a 24-hour window anchored at midnight for some plans, a partial-day window for others
• MAC binding, trust-on-first-use, resettable from the panel
• Subscription expiry, simultaneous-use limits and stale-session cleanup — expiry compared in the RADIUS server's own timezone, enforced on the expiry day itself, and disconnected on whichever router holds the session
• New accounts metered from their first minute — no free first day for anyone activated after the daily baseline
• Reject logging — failed authentications are recorded with a reason, and pruned on a schedule

The bit most implementations get wrong

Rate limits normally only apply at authentication time. Change a subscriber's rate in RADIUS and nothing happens until they redial, so the usual fix is to disconnect them, and every speed change becomes a dropped call or a dropped game. This engine pushes the new rate to the live session with a RADIUS CoA instead: plan changes, day and night windows, throttle and release all take effect within a minute with no reconnect, and every session is checked against the router afterwards.

Why the meter is not RADIUS accounting

RADIUS interim updates arrive in five-minute lumps. At 380 Mbps one lump is about 14 GB landing at once — enough to throttle and disconnect a customer on a peak that has gone a minute later. The engine meters from the router's own queue counters every minute, carries the count across redials, and falls back to accounting only when the meter is stale. Usage climbs smoothly, and a throttle only ever lands on real use.