Network Engine:

• Prefork design

Database/Storage:

• Database independent design: MySQL, PostgreSQL, Oracle, SQLite3
• Replicated database support
• Custom database queries allowing usage of returned results as macros

Authentication:

• mod_auth_pap: PAP (RFC1334)
• mod_auth_chap: CHAP (RFC1944)
• mod_auth_mschap: MSCHAPv1 & MSCHAPv2, incl. MPPE (RFC2443, RFC2759, RFC2548, RFC3079)

Enhanced features:

• Data & time based capping
• Prepaid users
• Topups
• Account validity periods, including valid start and end dates

Radius Protocol:

• Vendor specific attributes (RFC2865, RFC2866)
• Supported attribute operators include =, :=, ==, +=, !=, >, >=, <, <=, =~, !~, =*, !*
• Extended Radius Practices:
• Packet of disconnect (RFC2882)

Web Control Panels:

• Service provider control panel, including WiSP customizations
• Client control panel for viewing usage and plan details

Enhanced features:

• Plugin: Prepaid accounting based on usage/time
• Plugin: Creation of accounting START records when no START record has been received but an interim update has - helps on slow/lossly links

Forthcoming

• WORK IN PROGRESS - Plugin: Notifications, % based or approximate time based
• NEXT - Radius client utility (Thanks Cornel for this idea)
• Radius proxy - with filtering of requests/values ... etc in both directions + adding items. Persistent storing of radius items so inbound from client NAS is stored and sent back with accounting packet.
• Port 1700 proxy back to NAS.
• Plugin: User blacklists
• Plugin: Grouping of users and usage caps
• Radius proxy - enhancement: round-robin & random proxy destination tries, easy backoff.
• Backstore logs for if proxy destinations go down.
• Plugin: Auto-topups

Ideas:

• E-commerce integration & API - very popular request
• Database load balancing .... none of our largest clients have requested this, we talking 1 million users + ...
• IP Pools (in database)