UISP IP Provisioner (BETA)

Problem Statement

ISP network operators face challenges ensuring that only authorized customer devices ("subscribers") are being admitted to the network via a central source of truth.  The logical source of truth would be a billing and network management system ("NMS"),  such as UISP.  While UISP does have support for 3rd party devices within its NMS,  feature parity support for 3rd party devices compared to native UBNT CPE devices (those that exist in UISP via a "UISP Key") does not exist.  Further,  network authorization is only on "best effort" based on "good intentions" of administrators that ensure all devices on your network are UBNT CPE devices or cumbersome to administer "3rd party devices".  For example, if an unauthorized or untracked device happens to gain a DHCP lease from a broadband network gateway ("BNG", ISP router) there are no checks and balances to ensure that the device is associated with an Internet service  on an account within UISP.  The device is simply granted unaccounted for,  unbilled,  unrestricted,  Internet access once IP addressing is assigned.

Solution: IP Provisioner

Archous Networks recognizes the need to have subscribers tracked and authorized via a central source of truth.  We believe UISP,  with proper plugin development combined with external automation and orchestration,  can be adapted to support central subscriber authorization.  Fundamentally our plugin enables UISP operators to have a single pane of glass for adding subscriber MAC address or PPPoE account information directly to UISP services.  With our solution there's no more need to swivel-chair between the CRM module and NMS module to add 3rd party devices or UISP Keys.  There's no need to ensure that the subscriber's CPE equipment is UBNT and attached to UISP with a UISP Key.  An operator can simply select a device that exists already in the NMS module,  type in the MAC address of an authorized device,  or type in subscriber PPPoE credentials to authorize a device.  The premise is that all features are supported on native UISP and 3rd party devices -- regardless of the type, make, and model. If it has a MAC address it's supported.

From a MAC address perspective some operators prefer to use the MAC address of an upstream bridged CPE device instead of subscriber devices which can change over time.  This is where DHCP option-82 support comes in handy to reduce administrative overhead of having to track customer equipment MAC addresses if that is undesirable.

We also support provisioning static IP address assignment (DHCP reservation  or Framed-IP) as well as route assignment (static route or Framed-Route) via the same CRM pane of glass.  The subscriber's service QoS (upload and download speeds) are also automatically enforced on the IP address and route assignments via rate limiters on the BNG.

For all unknown devices that exist on the network but are not attached to a service in CRM, we enforce subscriber portal redirect, restricted IP lists, and default QoS rate limits.

Current BETA Status: Closed (In Development)

All features are supported on native UISP and 3rd party devices -- regardless of the type, make, and model. If it has a MAC address it's supported.

The IP Provisioner plugin is currently in a closed BETA status. We are actively developing and testing features against the criteria below to deliver a MVP (minimum viable product).

If you are interested in becoming a BETA tester, please email support@archous.tech to sign up.

Supported BNGs (ISP network routers):

Supported features:


Planned For Future

All features are supported on native UISP and 3rd party devices -- regardless of the type, make, and model. If it has a MAC address it's supported.

This is a placeholder for future feature and BNG support. We will release more information as it becomes available as far as timeline and roadmap.

Supported BNGs (ISP network routers):

Supported features: