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
CONFIGURE THE FILTER ON PFSENSE DEVICES
To activate the content filtering service on Pfsense devices, follow these instructions:
Register for free at this link: Click here to register.
Log into your router Pfsense and configure Dynamic DNS client in this way:
– Select Custom as Service type.
– Choose WAN as Interface to monitor and to send update from.
-
Username: Type the email/username used for the registration.
-
Password: Digit your password.
-
Update URL: Copy and paste the following instruction:
-
Click on [Diagnostic] and, after that, on [Edit File].Click on [Browse] and, in the list below, open the directory etc. Finally, open the file called crontab and modify it as follows:
-
In the line ending with the string /etc/rc.dyndns.update, edit the first column by entering */5 (the number after */ indicates the time period between every forced synchronization process expressed in minutes). Then edit the second column by inserting *.
This way, synchronization is forced every 5 minutes.
-
After that, click on [Save] to apply the changes.
NB: In order to use the DNS service correctly, the changes so far described are not enough. If you reboot the device, the change in the crontab file will be lost, because the file gets overwritten during rebooting. To overcome this problem, do as follows:
-
Click again on [Browse] and open the file called rc.bootup.
-
Look for the command configure_cron(); and comment it by adding the # symbol at the beginning of the line (as you can see in the image above).
-
Click on [Save] to apply the changes.
Finally, it is also necessary to change the file rc.dyndns.update. To do that, follow the instructions below:
-
Search for the line /* Interface IP address has changed */ and add this command below it: unlink(‘/conf/dyndns_wancustom’checkip’0.cache’);
-
IMPORTANT: in our example the WAN name is wancustom, so you have to type the correct command, based on your WAN interface name.
-
Click on [Save] to apply the changes.
Either manually or through a DHCP server, set the following IP addresses as the primary and secondary DNS respectively on the internal devices inside the network:
– 185.236.104.104
– 185.236.105.105
Congratulations!
You have correctly activated the filter on your Network.