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 > Cloud & Policy > Introduction
Kiwire 3.0 Administrator - Cloud & Policy
Cloud - Introduction
For customer that purchased Kiwire enterprise edition, you will have access to Cloud tenant module. The Kiwire Cloud tenant management module let you manage the multi-tenancy of your system. A multi-tenant architecture allows you to work from a shared solution, but unlock only your own data. Much like an apartment or office building, everyone enters through the same lobby but uses their own keys to access their individual apartments or offices. With Kiwire this multi-tenant architecture let you partition the system and let tenant have full management to their system, devices, functions, analytics and reporting. Each of the tenant have full capability of the Kiwire system and have unlimited administrator access to their own space.
The diagram above illustrates the Kiwire Multi-tenant platform
In Kiwire multi tenancy architecture, the “superuser” account is the master administrator which have the highest level administrator in the hierarchy with full authority, superuser can masquerade a tenant administrator and manage the tenants account on behalf. Kiwire platform partition each tenant with its within its primary database thus each tenant can have its own unique username that will not be shared between tenants as well its own configurations that is unique and tailored to each tenants.
How it Helps?
By aggregating data, processes, infrastructure, connectivity, and stakeholders in the cloud, Kiwire can securely serve multiple clients from an unlimited number of organizations, and provide the highest levels of management functionality at a price point you can’t achieve with single-tenant or on-premises applications.
TIP:
If you wish to restrict the tenant access to some of function of Kiwire platform, you can create the tenant, assign a sub administrator account with a restricted roles.
Important Notice
NOTE:
Any services related to mail services will need to use different ports from 587,465 and 25 due to Google Cloud blocking those ports.
Refer to this link:
https://stackoverflow.com/questions/48916990/cannot-sendmail-myself-from-google-compute-engine