Kiwire 3.0 Administrator - Device & Controller Setup Guide
Kiwire 3.0 Administrator - Device & Controller Setup Guide
Cambium Networks Configuration for Kiwire Hotspot
Cambium Networks Configuration for Kiwire Hotspot
Prerequisites
Before integrating the controller with Kiwire, it is necessary that the controller and access point:
-
are connected to the Internet
-
are reachable on the network
-
have an IP address assigned to the a through DHCP or static
Note:
-
Kiwire-hostname or Kiwire-ip can be obtain by contacting our technical support for our cloud customer. For enterprise client the ip will be on premises Kiwire ip address.
-
Social network hostname list can be obtained from Social network whitelist guide
Part 1: Cambium cnMaestro configuration
-
Login to your Cambium cnMaestro controller
-
Go to WLANs > Configuration > AAA Servers
-
Authentication Server
-
Host: Kiwire-hostname or Kiwire-Ip
-
Secret: create a secret pass phrase
-
Port: 1812
-
Timeout: 3 seconds
-
Attempts: 1
-
-
Accounting Server
-
Host: Kiwire-hostname or Kiwire-ip
-
Secret: secret same as authentication server
-
Port: 1813
-
Timeout: 3 seconds
-
Attempts: 1
-
Accounting Mode: Start-Interim-Stop
-
Accounting Packet: ticked
-
Interim Update Interval: 1800 seconds
-
-
Advanced Settings
-
NAS-Identifier: AP MAC address with capital letters and colon
-
Dynamic Authorization: ticked
-
Dynamic VLAN: ticked
-
Called Station ID: AP-MAC:SSID
-
-
Omaya 3.0 Administrator > Quick Setup > Dashboard
Documentation
Kiwire 3.0 Administrator > Integration > LDAP
Kiwire 3.0 Administrator - Integration
Integration - LDAP
Lightweight Directory Access Protocol (LDAP) connector module let you authenticate user credential using a LDAP version 3 server. To access the active directory module click on Integration > LDAP from the navigation. This includes main and mapping for Kiwire platform.
The field and its function description is listed below.
The LDAP integration references an LDAP object by its distinguished name (DN). A DN is a sequence of relative distinguished names (RDN) connected by commas.
An RDN is an attribute with an associated value in the form attribute = value; normally expressed in a UTF-8 string format. The following table lists typical RDN attribute types.
A LDAP entry is made up of a collection of attributes that have a unique identifier called a Distinguished Name (DN). A DN has a unique name that identifies the entry at the respective hierarchy. In the example, John Doe and Jane Doe are different common names (cn) that identify different entries at that same level.
A DN is also a fully qualified path of names that trace the entry back to the root of the tree. For example, the distinguished name of the John Doe entry is:
cn = John Doe, ou = People, dc = myldap.com
A Relative Distinguished Name (RDN) is a component of the distinguished name. For example, cn=John Doe, ou=People is a RDN relative to the root RDN dc=myldap.com.
LDAP Mapping
To access the LDAP module, click on Integration > LDAP from the navigation. On the LDAP mapping listing module, you may search for specific LDAP mapping by using the search field.
The field and its function description is listed below.
Add New Group Mapping
To create a new group mapping, click on “Add Group Mapping” button and populate the required fields. Fill in the field with relevant information to complete the process.
The field and its function description is listed below.
Edit or Delete Group Mapping
Click the edit icon on the listing screen to edit the setting of the group mapping. The edit screen be display which you can edit the setting of the group mapping. Click on the delete icon to delete the group mapping. A prompt will be display to ask for your confirmation to proceed to delete the group mapping. Please exercise with cautions as this not a reversible action.