User Defined Interface - NBI and UDI Overview

AP uses the control interface to communicate with the controller regarding its configuration. To have a logical separation of UE traffic from the AP control traffic the administrator can create an UDI (User Define Interface).

In case the UDI (using control interface, physical interface and hotspot service as shown in the figure) is configured the AP uses it to DNAT unauthorized UE's requests to the controller's captive portal (otherwise the AP uses the control interface).

The controller's captive portal redirects the UE to the configured portal login page URL. When the UE triggers this portal URL request, the AP will let it go through (it will not DNAT to the controller's captive portal), as it is configured as ACL in AP, directly to the external portal server.

The external portal communicates with the controller's NBI for status/login/logout requests. The interfaces external portal can communicate are the interfaces NBI listens to. NBI is bound by default to the controller's control and management interfaces.

In addition, the administrator can configure UDI interface, which NBI will bind as well. This UDI for NBI can be the same UDI which AP DNAT to the controller's captive portal, or others using control or management physical interfaces and whatever service (Hotspot/not specified) as in the figure. Complete the following steps to define UDI on the controller’s web interface: Navigate to Network > Data Control Plane> Cluster. Click Configure > User Defined Interface and enter the following details:

  • Name of the UDI
  • Physical Interface
  • Service
  • IP Address - (IPv4 or IPv6)
  • Subnet Mask
  • Gateway
  • VLAN

Click Add to add the UDI and click OK to save the configuration details.

Configuring UDI

The figure describes the request flows per interface.

Request flows per interface

Parent topic: User Defined Interface - NBI and UDI