-
Notifications
You must be signed in to change notification settings - Fork 2
Requirements
Being realistic here We won't tell you how much computer you need. We just tell you what We had and how was running.
Desktop computer with:
- 4 Core
- 32 GB RAM
- 512 SSD
It was not enough machine to run all software we needed. We had in this machine:
- Microsoft 2012 R2 Hyper-V in the physicall machine.
- Virtualized: Ubuntu Server with Grafana Dashboard with Unifi plugins.
- Virtualized: Ubuntu Server with FreeRadius, DaloRadius, MariaDB.
- Virtualized: Unifi Controller.
- Virtualized: Raspbian with Pi-Hole to block by DNS ads and some websites.
- Virtualized: Ubuntu Server with UNMS to manage all EdgeSwitches and know their status.
- USG which can not handle all request if we activated DPI.
- 104 Unifi APs.
- Ubiquiti EdgeSwitches (Would be better having Unifi switches for unifi network but...).
- We have also 2 Backbone Allied Telesys Switches.
- More than 20 racks with one Allied Telesys Switch and a downlink to EdgeSwitches to inject PoE to APs.
The Network is not he most efficient and clever topology...
We had a 4 Core computer with 16 GB RAM and SSD disk with Hyper-V and was not enough. You have to be worried about clean some information and doing some MariaDB optimizations because the database is the most critical and the most demanding service here. Maybe with no more than 400 concurrent users is enough but you must test. To this machine we designated 2 Cores, 8 GB RAM and 40 Gb Hard disk (you must take care because with 600 users the logs are full in a week due to FreeRadius service). If you have a similar amount of users, consider to have a machine of Hexa or Octacore with at least 16-32 Gb RAM and at least 300 Gb of disk.
Consider also to have separately the Http service in a very lower machine because the critical services here are FreeRadius, Database and Unifi Contoller.
Unifi Controller for 100 APs we had not enough machine to handle this amount of hardware with 2 Cores and 4 Gb RAM. For those you need at least 4 cores and 8 Gb to run the controller fluently. This is important because we will do a lot of API Calls.
Maybe you do not need this so we won't tell you something about this.
In ideal Unifi Wireless network all hardware would be Unifi. So we will keep this stuff out too because, in fact, is not necessary at all.
This not a topic here but consider to have it if you have a Unifi network, it will help a lot.
Official site: https://github.com/unifi-poller/unifi-poller
The FreeRadius logs depends on how many users are heavy, would be a great idea mount another disk for that in the point /var/log
.
Also would be great have the mysql stuff and backups in other disk so consider to have another mount point at /var/lib
and if you will want the backups in a separate disk /var/lib/automysqlbackup
.
- Intention of the project (About this...)
- Requirements
- Network Scenario
- Server Installation
- Database Configuration
- FreeRadius Certificates generation
- FreeRadius Configuration
- Apache and daloRadius Configuration
- Unifi Controller configuration to use RADIUS
- Limit connected devices by users
- Bandwidth and Time Counters creation
- The Bandwidth Counter Problem
- Unifi FreeRaius Scripts complete param configuration
- Fix users that does not exists connected
- Automatically backups
- Alternatives to daloRadius