{"id":38422,"date":"2019-10-31T22:23:40","date_gmt":"2019-10-31T19:23:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros\/"},"modified":"2020-12-15T02:12:35","modified_gmt":"2020-12-15T00:12:35","slug":"tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros","title":{"rendered":"TR-069 in Mikrotik. Testing Freeacs as a configuration server for RouterOS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

In this article, I will attempt to describe step by step the process of setting up a test server for a wonderful project. Freeacs<\/a><\/noindex> to a fully operational state, and show practical techniques for working with Mikrotik: configuration through parameters, running scripts, updates, installation of additional modules, etc.<\/p>\n

The goal of the article is to encourage colleagues to abandon the management of network devices using dreadful hacks and crutches, such as custom scripts, Dude, Ansible, etc. And, in this regard, to spark celebrations and mass rejoicing in the squares.
\n<\/a><\/noindex><\/p>\n

0. Selection<\/h4>\n

Why Freeacs and not Genie-Acs, mentioned in mikrotik-wiki<\/a><\/noindex>, as a more active option?
\nBecause there are publications by Spanish authors on Genie-Acs with Mikrotik. Here are their pdf<\/a><\/noindex> and video<\/a><\/noindex> from last year's MUM. Auto-sharing in slides is cool, but I would like to move away from the concept of writing scripts to run scripts to run scripts...<\/p>\n

1. Installing Freeacs<\/h4>\n

We will install on Centos7, and since devices transmit quite a lot of data, and ACS actively interacts with the database, we won't skimp on resources. For comfortable operation, we will allocate 2 CPU cores, 4GB RAM, and 16GB of fast SSD RAID10 storage. I will install Freeacs in a Proxmox VE LXC container, but you can work with any tool you prefer.
\nDon't forget to set the correct time on the ACS machine.<\/p>\n

The system will be a test one, so we won't complicate things and will simply use the kindly provided installation script as is.<\/p>\n

wget https:\/\/raw.githubusercontent.com\/freeacs\/freeacs\/master\/scripts\/install_centos.sh\nchmod +x install_centos.sh\n.\/install_centos.sh<\/code><\/pre>\n
As soon as the script completes \u2014 you will immediately have access to the web interface via the machine's IP, with the credentials admin\/freeacs.<\/p>\n
\"TR-069
\nHere is such a nice minimalist interface, and how great and quickly everything turned out.<\/i><\/p>\n
2. Initial Setup of Freeacs<\/h4>\n
The basic unit of management for ACS is the unit or CPE (Customer Premises Equipment). The most important thing we need to manage the units is their Unit Type, i.e., the model of the equipment that defines the set of configurable parameters for the unit and its software. But since we don't yet know how to properly register a new Unit Type, it's best to ask the unit itself by enabling Discovery Mode.<\/p>\n
This mode should categorically not be used in production, but we need to start the engine and see the system's capabilities. All main configurations are stored in \/opt\/freeacs-*. Therefore, let's open<\/p>\n
 vi \/opt\/freeacs-tr069\/config\/application-config.conf <\/code><\/pre>\n
, we find<\/p>\n
discovery.mode = false<\/code><\/pre>\n
and change to<\/p>\n
discovery.mode = true<\/code><\/pre>\n
Additionally, we should increase the maximum file sizes that nginx and mysql will work with. For mysql, add the line to \/etc\/my.cnf<\/p>\n
max_allowed_packet=32M<\/code><\/pre>\n
, and for nginx, in \/etc\/nginx\/nginx.conf, add<\/p>\n
client_max_body_size 32m;<\/code><\/pre>\n
to the http section. Otherwise, we will only be able to work with firmware sizes up to 1M.<\/p>\n
We restart, and we are ready to work with devices.<\/p>\n
And the device (CPE) will be our little workhorse hAP AC lite<\/a><\/noindex><\/b>.<\/p>\n
Before the test connection, it is advisable to manually configure the CPE to the minimal working configuration so that the parameters you wish to configure in the future are not empty. For the router, at a minimum, you can enable the dhcp client on ether1, install the tr-069client package, and set passwords.<\/p>\n
3. Connect Mikrotik<\/h4>\n
It is advisable to connect all units using a valid serial number as the login. This way, everything in the logs will be clear. Some recommend using WAN MAC \u2014 do not believe them. Some use a shared login\/password for all \u2014 avoid them.<\/p>\n
Open the tr-069 log to monitor the \"conversations\"<\/p>\n
tail -f \/var\/log\/freeacs-tr069\/tr069-conversation.log<\/code><\/pre>\n
Open winbox, menu item TR-069.
\nACS URL: http:\/\/10.110.0.109\/tr069\/prov<\/code> (replace with your IP)
\nUsername: 9249094C26CB (copy the serial number from system>routerboard)
\nPassword: 123456 (not needed for discovery, but it should be there)
\nWe do not change the Periodic inform interval. This setting will be provided through our ACS<\/p>\n
Below are the settings for remote initialization of connection, but I couldn\u2019t get Mikrotik to work with this straight away. However, with phones, the remote request works \"out of the box.\" We will need to look into it.<\/p>\n
\"TR-069<\/p>\n
After clicking the Apply button \u2014 data exchange will start in the terminal, and in the Freeacs web interface, we will be able to see our router with the automatically created Unit Type \"hAPaclite.\"<\/p>\n
\"TR-069<\/p>\n
The router is connected. You can look at the automatically created Unit Type. Open Easy Provisioning > Unit Type > Unit Type Overview > hAPaclite<\/code>. There isn't much there! A total of 928 parameters (I checked in the shell). Whether that\u2019s a lot or a little \u2014 we will figure out later, but for now, let\u2019s take a quick look. This is what the Unit Type means. It\u2019s a list of supported parameters with keys but without values. Values are set in lower levels \u2014 Profiles and Units.<\/p>\n
4. Configure Mikrotik<\/h4>\n
It\u2019s time to download the web interface manual<\/a><\/noindex> This manual is from 2011 \u2014 like a bottle of good, aged wine. Let\u2019s open it and let it breathe.<\/p>\n
Now, in the web interface, let's click on the pencil icon next to our unit and proceed to the unit configuration mode. It looks like this:<\/p>\n
\"TR-069<\/p>\n
Let's briefly go over what interesting things are on this page:<\/p>\n
Unit Configuration Block<\/i><\/p>\n