{"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\/sk\/blog\/administrirovanie\/tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros","title":{"rendered":"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>V tomto \u010dl\u00e1nku sa pok\u00fasim krok za krokom pop\u00edsa\u0165 proces in\u0161tal\u00e1cie testovacieho servera v\u00fdnimo\u010dn\u00e9ho projektu <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/freeacs\/freeacs\">Freeacs<\/a><\/noindex> do \u00faplne funk\u010dn\u00e9ho stavu a uk\u00e1za\u0165 praktick\u00e9 techniky pre pr\u00e1cu s mikrotikom: konfigur\u00e1ciu cez parametre, vykon\u00e1vanie skriptov, aktualiz\u00e1ciu, in\u0161tal\u00e1ciu doplnkov\u00fdch modulov at\u010f.<\/p>\n<p>Cie\u013eom \u010dl\u00e1nku je podnieti\u0165 kolegov k zanechaniu spr\u00e1vy sie\u0165ov\u00fdch zariaden\u00ed prostredn\u00edctvom zl\u00fdch prakt\u00edk a barli\u010diek, ako s\u00fa vlastnoru\u010dne p\u00edsan\u00e9 skripty, Dude, Ansible a pod. A na tento \u00fa\u010det vyvola\u0165 oslavy a hromadn\u00fa rados\u0165 na n\u00e1mestiach.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h4>0. V\u00fdber<\/h4>\n<p>Pre\u010do freeacs, a nie genie-acs, spomenut\u00fd v <noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.mikrotik.com\/wiki\/Manual:TR069-client\">mikrotik-wiki<\/a><\/noindex>, ako viac \u017eiv\u00fd?<br \/>\nPreto\u017ee o genie-acs s mikrotikom existuj\u00fa publik\u00e1cie od \u0160panielov. Tu s\u00fa ich <noindex><a rel=\"nofollow\" href=\"https:\/\/mum.mikrotik.com\/presentations\/EU18\/presentation_5202_1523350603.pdf\">pdf<\/a><\/noindex> a <noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=MoywoC8BC0M\">videu<\/a><\/noindex> z minuloro\u010dn\u00e9ho MUM. Automatizovan\u00e9 zdie\u013eanie na slideoch je \u00fa\u017easn\u00e9, ale r\u00e1d by som sa vzdal koncepcie p\u00edsania skriptov na sp\u00fa\u0161\u0165anie skriptov na sp\u00fa\u0161\u0165anie skriptov...<\/p>\n<h4>1. In\u0161tal\u00e1cia freeacs<\/h4>\n<p>In\u0161talova\u0165 budeme na Centos7, a preto\u017ee zariadenia pren\u00e1\u0161aj\u00fa dos\u0165 ve\u013ea d\u00e1t a ACS akt\u00edvne pracuje s datab\u00e1zou \u2014 nem\u00f4\u017eeme by\u0165 skromn\u00ed s prostriedkami. Pre pohodln\u00fa pr\u00e1cu vy\u010dlen\u00edme 2 jadr\u00e1 CPU, 4GB RAM a 16GB r\u00fdchlej SSD RAID10 \u00falo\u017enej kapacity. Ja budem in\u0161talova\u0165 freeacs v lxc-kontajneri Proxmox VE, m\u00f4\u017eete v\u0161ak pracova\u0165 v akomko\u013evek n\u00e1stroji, ktor\u00fd v\u00e1m vyhovuje.<br \/>\nNezabudnite nastavi\u0165 spr\u00e1vny \u010das na stroji s ACS.<\/p>\n<p>Syst\u00e9m bude testovac\u00ed, preto sa nebudeme komplikova\u0165, a jednoducho vyu\u017eijeme l\u00e1skavo poskytnut\u00fd in\u0161tala\u010dn\u00fd skript tak, ako je.<\/p>\n<pre><code class=\"bash\">wget https:\/\/raw.githubusercontent.com\/freeacs\/freeacs\/master\/scripts\/install_centos.sh\nchmod +x install_centos.sh\n.\/install_centos.sh<\/code><\/pre>\n<p>Akon\u00e1hle sa pr\u00e1ca skriptu dokon\u010d\u00ed \u2014 budete sa m\u00f4c\u0165 okam\u017eite dosta\u0165 do webov\u00e9ho rozhrania prostredn\u00edctvom IP stroja s prihlasovac\u00edmi \u00fadajmi admin\/freeacs<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/2725143fa775c7bae02c710eaec05eaf.png\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>Tak\u00e9to pr\u00edjemn\u00e9 minimalistick\u00e9 rozhranie, a ako skvele a r\u00fdchlo to v\u0161etko fungovalo<\/i><\/p>\n<h4>2. Po\u010diato\u010dn\u00e9 nastavenie freeacs<\/h4>\n<p>Z\u00e1kladnou jednotkou spr\u00e1vy pre ACS je jednotka alebo CPE (Customer Premises Equipment). A najd\u00f4le\u017eitej\u0161ie, \u010do potrebujeme na spr\u00e1vu jednotiek \u2014 s\u00fa ich typy jednotiek, t.j. model zariadenia, ktor\u00fd ur\u010duje s\u00fabor konfigurovate\u013en\u00fdch parametrov jednotky a jej softv\u00e9ru. Ale k\u00fdm nevieme, ako spr\u00e1vne zavies\u0165 nov\u00fd typ jednotky, je najlep\u0161ie op\u00fdta\u0165 sa na to samotnej jednotky aktivovan\u00edm re\u017eimu objavovania.<\/p>\n<p>V produk\u010dnom prostred\u00ed je tento re\u017eim kategoricky zak\u00e1zan\u00fd, ale mus\u00edme r\u00fdchlo na\u0161tartova\u0165 motor a presk\u00fama\u0165 mo\u017enosti syst\u00e9mu. V\u0161etky z\u00e1kladn\u00e9 nastavenia s\u00fa ulo\u017een\u00e9 v \/opt\/freeacs-*. Preto otv\u00e1rame<\/p>\n<pre><code class=\"bash\"> vi \/opt\/freeacs-tr069\/config\/application-config.conf <\/code><\/pre>\n<p>, n\u00e1jdeme<\/p>\n<pre><code class=\"bash\">discovery.mode = false<\/code><\/pre>\n<p>a zmen\u00edme na<\/p>\n<pre><code class=\"bash\">discovery.mode = true<\/code><\/pre>\n<p>Okrem toho by sme mali zv\u00fd\u0161i\u0165 maxim\u00e1lne ve\u013ekosti s\u00faborov, s ktor\u00fdmi bud\u00fa pracova\u0165 nginx a mysql. Pre mysql prid\u00e1me do \/etc\/my.cnf riadok<\/p>\n<pre><code class=\"bash\">max_allowed_packet=32M<\/code><\/pre>\n<p>, a pre nginx, do \/etc\/nginx\/nginx.conf prid\u00e1me<\/p>\n<pre><code class=\"bash\">client_max_body_size 32m;<\/code><\/pre>\n<p>do sekcie http. Inak m\u00f4\u017eeme pracova\u0165 len s firmv\u00e9rmi do 1M.<\/p>\n<p>Re\u0161tartujeme a sme pripraven\u00ed pracova\u0165 s zariadeniami.<\/p>\n<p>A ako zariadenie (CPE) budeme ma\u0165 mal\u00e9ho pracanta <b><noindex><a rel=\"nofollow\" href=\"https:\/\/mikrotik.com\/product\/RB952Ui-5ac2nD\">hAP AC lite<\/a><\/noindex><\/b>.<\/p>\n<p>Pred testovac\u00edm pripojen\u00edm je dobr\u00e9 manu\u00e1lne nastavi\u0165 CPE na minim\u00e1lnu pracovn\u00fa konfigur\u00e1ciu, aby parametre, ktor\u00e9 v bud\u00facnosti chcete konfigurova\u0165, boli nezapln\u00e9. Pre router je minim\u00e1lne mo\u017en\u00e9 zapn\u00fa\u0165 dhcp-klienta na ether1, nain\u0161talova\u0165 bal\u00edk tr-069client a nastavi\u0165 hesl\u00e1.<\/p>\n<h4>3. Pripoj\u00edme Mikrotik<\/h4>\n<p>V\u0161etky jednotky je lep\u0161ie pripoji\u0165, pri\u010dom ako prihlasovacie meno pou\u017ei\u0165 platn\u00e9 s\u00e9riov\u00e9 \u010d\u00edslo. Vtedy budete ma\u0165 v logoch v\u0161etko jasn\u00e9. Niektor\u00ed odpor\u00fa\u010daj\u00fa pou\u017ei\u0165 WAN MAC \u2014 neverte tomu. Niektor\u00ed pou\u017e\u00edvaj\u00fa spolo\u010dn\u00e9 prihlasovacie meno\/heslo \u2014 vyh\u00fdbajte sa im.<\/p>\n<p>Otv\u00e1rame log tr-069 na monitorovanie \u201erozhovorov\u201c<\/p>\n<pre><code class=\"bash\">tail -f \/var\/log\/freeacs-tr069\/tr069-conversation.log<\/code><\/pre>\n<p>Otv\u00e1rame winbox, menu TR-069.<br \/>\nACS URL: <code>http:\/\/10.110.0.109\/tr069\/prov<\/code> (nahradi\u0165 va\u0161ou IP)<br \/>\nUsername: 9249094C26CB (skop\u00edrujeme s\u00e9riov\u00e9 \u010d\u00edslo z system&gt;routerboard)<br \/>\nPassword: 123456 (pre discovery nie je potrebn\u00e9, ale aby bolo)<br \/>\nPeriodick\u00fd informa\u010dn\u00fd interval nemenieme. Toto nastavenie vyd\u00e1me cez n\u00e1\u0161 ACS<\/p>\n<p>Ni\u017e\u0161ie s\u00fa nastavenia na vzdialen\u00fa inicializ\u00e1ciu pripojenia, ale na r\u00fdchlo som nezvl\u00e1dol don\u00fati\u0165 mikrotik s t\u00fdmto pracova\u0165. Aj ke\u010f s telef\u00f3nmi funguje remote request \u201ez krabice\u201c. Bude treba sk\u00fama\u0165.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/4ea9279e8e3715ba28ee52638314109f.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Po stla\u010den\u00ed tla\u010didla Apply bude prebieha\u0165 v\u00fdmena d\u00e1t v termin\u00e1li a vo webovom rozhran\u00ed Freeacs bude mo\u017en\u00e9 vidie\u0165 n\u00e1\u0161 router s automaticky vytvoren\u00fdm typom jednotky \u201ehAPaclite\u201c.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/53dc9241200dbee24d958c57adbc0264.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Router je pripojen\u00fd. M\u00f4\u017eete si pozrie\u0165 automaticky vytvoren\u00fd typ jednotky. Otv\u00e1rame <code>Easy Provisioning &gt; Unit Type &gt; Unit Type Overview &gt; hAPaclite<\/code>. \u010co v\u0161etko tu len nie je! Cel\u00fdch 928 parametrov (pozrel som sa do shellu). Je to ve\u013ea alebo m\u00e1lo \u2014 to si povieme nesk\u00f4r, ale zatia\u013e sa len r\u00fdchlo pozrieme. Toto znamen\u00e1 Typ jednotky. Je to zoznam podporovan\u00fdch parametrov s k\u013e\u00fa\u010dmi, ale bez hodn\u00f4t. Hodnoty s\u00fa zadan\u00e9 na ni\u017e\u0161\u00edch \u00farovniach \u2014 Profiloch a Jednotk\u00e1ch.<\/p>\n<h4>4. Konfigurujeme Mikrotik<\/h4>\n<p>Pri\u0161iel \u010das stiahnu\u0165 <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/mortensimon\/web\/blob\/master\/docs\/Fusion%20Web%20User%20Manual.pdf\">pr\u00edru\u010dku k webov\u00e9mu rozhraniu<\/a><\/noindex> Toto je pr\u00edru\u010dka z roku 2011 \u2014 ako f\u013ea\u0161a dobr\u00e9ho, vyzret\u00e9ho v\u00edna. Po\u010fme ju otvori\u0165 a necha\u0165 ju d\u00fdcha\u0165.<\/p>\n<p>A my v webovom rozhran\u00ed klikneme na ceruzku ved\u013ea na\u0161ej jednotky a prejdeme do re\u017eimu konfigur\u00e1cie jednotky. Vyzer\u00e1 to takto:<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/5268ac4e3cece3aae79dd58602c69f61.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Kr\u00e1tko si prejdeme, \u010do je zauj\u00edmav\u00e9 na tejto str\u00e1nke:<\/p>\n<p><i>Blok konfigur\u00e1cie jednotky<\/i><\/p>\n<ul>\n<li>Profil: Toto je profil v r\u00e1mci Typu jednotky. Hierarchia je tak\u00e1to: <code>UnitType &gt; Profil &gt; Jednotka<\/code>. To znamen\u00e1, \u017ee m\u00f4\u017eeme vytvori\u0165 napr\u00edklad profily <code>hAPaclite &gt; hotspot<\/code> a <code>hAPaclite &gt; branch<\/code>, ale v r\u00e1mci modelu zariadenia<\/li>\n<\/ul>\n<p><i>Blok Provisioning<\/i> s tla\u010didlami<br \/>\nN\u00e1povedy nazna\u010duj\u00fa, \u017ee v\u0161etky tla\u010didl\u00e1 v bloku Provisioning m\u00f4\u017eu okam\u017eite aplikova\u0165 konfigur\u00e1ciu cez ConnectionRequestURL. Ale, ako som u\u017e povedal, to nefunguje, preto po stla\u010den\u00ed tla\u010didiel bude treba re\u0161tartova\u0165 tr-069 klienta na mikrotik pre ru\u010dn\u00fd \u0161tart provision.<\/p>\n<ul>\n<li>Freq\/Spread: Ko\u013ekokr\u00e1t za t\u00fd\u017ede\u0148 dod\u00e1va\u0165 konfigur\u00e1ciu \u00b1 %, aby sa zn\u00ed\u017eila z\u00e1\u0165a\u017e na server a komunika\u010dn\u00e9 kan\u00e1ly. Predvolene je nastaven\u00e9 7\/20, t.j. ka\u017ed\u00fd de\u0148 \u00b1 20% a n\u00e1poveda, ako to prebieha v sekund\u00e1ch. Zatia\u013e nem\u00e1 zmysel meni\u0165 frekvenciu dod\u00e1vky, preto\u017ee to sp\u00f4sob\u00ed zbyto\u010dn\u00fd \u0161um v logoch a nie v\u017edy o\u010dak\u00e1van\u00e9 pou\u017eitie nastaven\u00ed.<\/li>\n<\/ul>\n<p><i>Blok hist\u00f3rie provisioning<\/i> (posledn\u00fdch 48 hod\u00edn)<\/p>\n<ul>\n<li>Na poh\u013ead hist\u00f3ria, ako hist\u00f3ria, ale kliknut\u00edm na hlavi\u010dku \u2014 sa dostanete do pohodln\u00e9ho n\u00e1stroja vyh\u013ead\u00e1vania v db, s regexp a vylep\u0161eniami.<\/li>\n<\/ul>\n<p><i>Blok Parametre<\/i><\/p>\n<p>Najv\u00e4\u010d\u0161\u00ed a najd\u00f4le\u017eitej\u0161\u00ed blok, kde sa vlastne zad\u00e1vaj\u00fa a \u010d\u00edtaj\u00fa parametre pre dan\u00fa jednotku. Teraz vid\u00edme len najd\u00f4le\u017eitej\u0161ie syst\u00e9mov\u00e9 parametre, bez ktor\u00fdch pr\u00e1ca ACS s jednotkou nie je mo\u017en\u00e1. Ale my si pam\u00e4t\u00e1me, \u017ee v Typu jednotky ich je \u2014 <i>928<\/i>. Po\u010fme sa pozrie\u0165 na v\u0161etky hodnoty a zist\u00edme, s \u010d\u00edm to v\u0161etko jedia na mikrotiku.<\/p>\n<h4>4.1 \u010c\u00edtame parametre<\/h4>\n<p>V bloku Provisioning stla\u010d\u00edme tla\u010didlo \u010c\u00edta\u0165 v\u0161etko. V bloku \u2014 \u010derven\u00fd n\u00e1pis. Napravo sa objav\u00ed st\u013apec <i>CPE (aktu\u00e1lna) hodnota<\/i>. V syst\u00e9mov\u00fdch parametroch sa ProvisioningMode zmenil na READALL.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/c8e3161270f35955f79cbce576965690.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>A\u2026 ni\u010d sa nestane, okrem spr\u00e1vy v System.X_FREEACS-COM.IM.Message <code>Kick failed at...<\/code>.<\/p>\n<p>Re\u0161tartujte klienta TR-069 alebo re\u0161tartujte router a pokra\u010dujte v obnove str\u00e1nky prehliada\u010da, k\u00fdm nez\u00edskate parametre v vesel\u00fdch \u0161ed\u00fdch obd\u013a\u017enikoch na pravej strane.<br \/>\nAk sa niekto rozhodol ochutna\u0165 star\u00e9 v\u00edno, tento re\u017eim je v manu\u00e1li op\u00edsan\u00fd ako 10.2 Inspection mode. Zap\u00edna sa a funguje tro\u0161ku inak, ale podstata je celkom jasn\u00e1.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/40ca0f85f2635ba84f9c4540464176dd.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Re\u017eim READALL sa s\u00e1m vypne po 15 min\u00fatach, zatia\u013e \u010do sa pok\u00fasime zisti\u0165, \u010do tu m\u00f4\u017ee by\u0165 u\u017eito\u010dn\u00e9 a \u010do m\u00f4\u017eeme upravi\u0165 \"na lete\", k\u00fdm sme v tomto re\u017eime.<\/p>\n<p>M\u00f4\u017eeme meni\u0165 IP adresy, zap\u00edna\u0165\/vyp\u00edna\u0165 rozhrania, pravidl\u00e1 firewallu, ktor\u00e9 s\u00fa s pozn\u00e1mkami (inak by to bol \u00fapln\u00fd chaos), Wi-Fi a podobn\u00e9 drobnosti.<\/p>\n<p>Teda, zatia\u013e nie je mo\u017en\u00e9 rozumne konfigurova\u0165 Mikrotik iba pomocou TR-069. Ale d\u00e1 sa dos\u0165 dobre monitorova\u0165. K dispoz\u00edcii je \u0161tatistika pre rozhrania a ich stav, vo\u013en\u00e1 pam\u00e4\u0165 at\u010f.<\/p>\n<h4>4.2 Dod\u00e1vame parametre<\/h4>\n<p>Teraz sa pok\u00fasime doda\u0165 parametre do routera prostredn\u00edctvom TR-069 \"prirodzen\u00fdm\" sp\u00f4sobom. Prvou obetou bude Device.DeviceInfo.X_MIKROTIK_SystemIdentity. N\u00e1jdeme ho v parametroch jednotky All. Ako vid\u00edte - nie je ur\u010den\u00fd. To znamen\u00e1, \u017ee ktor\u00e1ko\u013evek jednotka m\u00f4\u017ee ma\u0165 ak\u00fako\u013evek identitu. Dos\u0165 u\u017e trpenia!<br \/>\nZa\u0161krtneme pol\u00ed\u010dko v st\u013apci create, nastav\u00edme meno Mr.White a stla\u010d\u00edme tla\u010didlo Update parameters. \u010co sa stane \u010falej, u\u017e tu\u0161\u00edte. Pri \u010fal\u0161ej rel\u00e1cii spojenia s centrom by mal router zmeni\u0165 svoju identitu.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/1ce9ebf23135717abb3c6d0696a8e1b1.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Ale to je pre n\u00e1s m\u00e1lo. Tak\u00fd parameter, ako identita, je dobr\u00e9 ma\u0165 v\u017edy po ruke pri h\u013eadan\u00ed po\u017eadovanej jednotky. Klikneme na n\u00e1zov parametra a za\u0161krtneme pol\u00ed\u010dka Display (D) a Searchable (S). K\u013e\u00fa\u010d parametra sa men\u00ed na RWSD (Pam\u00e4tajte, men\u00e1 a k\u013e\u00fa\u010de sa zad\u00e1vaj\u00fa na najvy\u0161\u0161ej \u00farovni Unit Type).<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/513fb00425c43ab4632491dd9133d624.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Hodnota sa teraz nielen zobrazuje v celkovom zozname vyh\u013ead\u00e1vania, ale je tie\u017e dostupn\u00e1 na vyh\u013ead\u00e1vanie v <code>Support &gt; Search &gt; Advanced form<\/code><\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/bc8b087f3c44fb3a8b7974a204fe1d1f.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Iniciujeme provisioning a pozrieme sa na identitu. Dobr\u00fd de\u0148, Mr.White! Teraz si nebudete m\u00f4c\u0165 sami zmeni\u0165 identitu, k\u00fdm funguje klient TR-069.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/80de1bf2aa0c2295d08da862c67fc90b.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<h4>4.3 Vykon\u00e1vame skripty<\/h4>\n<p>Ke\u010f\u017ee sme zistili, \u017ee bez nich to nejde, po\u010fme ich vykon\u00e1va\u0165.<\/p>\n<p>Ale predt\u00fdm, ne\u017e sa pust\u00edme do pr\u00e1ce s s\u00fabormi, mus\u00edme upravi\u0165 direkt\u00edvu <code>public.url<\/code> v s\u00fabore <code>\/opt\/freeacs-tr069\/config\/application-config.conf<\/code><br \/>\nVe\u010f st\u00e1le m\u00e1me testovaciu konfigur\u00e1ciu, ktor\u00e1 bola nastaven\u00e1 jedn\u00fdm skriptom. Nezabudli ste?<\/p>\n<pre><code class=\"bash\"># --- Public url (used for download f. ex.) ---\npublic.url = \"http:\/\/10.110.0.109\"\npublic.url: ${?PUBLIC_URL}<\/code><\/pre>\n<p>Re\u0161tartujeme ACS a smerujeme priamo do <code>Files &amp; Scripts<\/code>.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/816dad5c374c015d9f8ffcd4d7f416a7.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>To, \u010do sa teraz otv\u00e1ra, patr\u00ed typu zariadenia, t.j. glob\u00e1lne pre v\u0161etky smerova\u010de hAP ac lite, nech u\u017e ide o smerova\u010d pobo\u010dky, hotspot alebo CAPsMAN. Tak\u00fa vysok\u00fa \u00farove\u0148 zatia\u013e nepotrebujeme, preto predt\u00fdm, ako za\u010dneme pracova\u0165 so skriptami a s\u00fabormi, by sme mali vytvori\u0165 profil. M\u00f4\u017eeme si ho nazva\u0165 ako 'funkcia' zariadenia.<\/p>\n<p>Po\u010fme urobi\u0165 n\u00e1\u0161ho chlapca serverom \u010dasu. D\u00f4stojn\u00e1 funkcia s oddelen\u00fdm bal\u00edkom softv\u00e9ru a mal\u00fdm po\u010dtom parametrov. Ideme do <code>Easy Provisioning &gt; Profile &gt; Create Profile<\/code> a vytv\u00e1rame v Unit Type:hAPaclite profil <i>timeserver<\/i>. Parametre v na\u0161om predvolenom profile zatia\u013e neexistovali, tak\u017ee niet \u010do kop\u00edrova\u0165.<i> Kop\u00edrova\u0165 parametre z: \u00abnekop\u00edrova\u0165&#8230;\u00bb<\/i><\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/d2ee21aa2e04caf5b18ae6fe25e96016.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Tu parametre zatia\u013e nie s\u00fa, ale bude mo\u017en\u00e9 zada\u0165 tie, ktor\u00e9 chceme nesk\u00f4r vidie\u0165 na na\u0161ich serveroch \u010dasu, vytvoren\u00fdch z hAPaclite. Napr\u00edklad, spolo\u010dn\u00e9 adresy NTP serverov.<br \/>\nPrejdeme do konfigur\u00e1cie jednotky a presunieme ju do profilu timeserver.<\/p>\n<p>Kone\u010dne ideme do <code>Files &amp; Scripts<\/code>, aby sme robili skripty, a tu n\u00e1s \u010dakaj\u00fa \u00fa\u017easne praktick\u00e9 funkcie.<\/p>\n<p>Aby sme vykonali skript na jednotke, mus\u00edme vybra\u0165 <i>Type:TR069_SCRIPT<\/i> a <i>N\u00e1zov <\/i>a <i>Target Name<\/i> mus\u00ed ma\u0165 koncovku .alter<br \/>\nPri tom, na rozdiel od softv\u00e9ru, sa pre skripty d\u00e1 bu\u010f nahra\u0165 hotov\u00fd s\u00fabor, alebo ho jednoducho nap\u00edsa\u0165\/ Upravi\u0165 v poli <i>Content. <\/i>Po\u010fme sk\u00fasi\u0165 nap\u00edsa\u0165 priamo tam.<\/p>\n<p>Aby sme hne\u010f videli v\u00fdsledok, prid\u00e1me smerova\u010du VLAN na ether1.<\/p>\n<pre><code class=\"bash\">\/interface vlan\nadd interface=ether1 name=vlan1 vlan-id=1<\/code><\/pre>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/f026cf2468f57272afd0be6a964fc874.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Zad\u00e1me, klikneme na <i>Upload<\/i> a je hotovo. N\u00e1\u0161 skript <code>vlan1.alter<\/code> \u010dak\u00e1 na svoj \u010das.<\/p>\n<p>No \u010do, ideme? Nie. E\u0161te treba pre n\u00e1\u0161 profil prida\u0165 skupinu. Skupiny nie s\u00fa s\u00fa\u010das\u0165ou hierarchie zariaden\u00ed, ale s\u00fa potrebn\u00e9 na vyh\u013ead\u00e1vanie jednotiek v Unit Type alebo Profile a s\u00fa povinn\u00e9 na vykonanie skriptov cez Advanced Provisioning. Zvy\u010dajne s\u00fa skupiny spojen\u00e9 s lokalitami a maj\u00fa vnoren\u00fa \u0161trukt\u00faru. Urobme skupinu Russia.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/b9c52bcff93aa197b5ad1bc83d46c533.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Predstavte si, pr\u00e1ve sme dok\u00e1zali z\u00fa\u017ei\u0165 vyh\u013ead\u00e1vanie z 'V\u0161etky servery \u010dasu sveta na hAPaclite' na 'V\u0161etky servery \u010dasu v Rusku na hAPaclite'. Tam je e\u0161te obrovsk\u00e9 mno\u017estvo zauj\u00edmav\u00e9ho s skupinami, ale nem\u00e1me \u010das. Ideme u\u017e do skriptov.<\/p>\n<pre><code class=\"plaintext\">Advanced Provisioning &gt; Job &gt; Create Job<\/code><\/pre>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/ca83378e36cb6e716e489c868601f1f4.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Ke\u010f\u017ee sme v Advanced re\u017eime, m\u00f4\u017eeme tu nastavi\u0165 mno\u017estvo r\u00f4znych podmienok spustenia \u00falohy, spr\u00e1vania pri chyb\u00e1ch, opakovan\u00ed a \u010dasov\u00fdch limitov. Odpor\u00fa\u010dam si to v\u0161etko pre\u010d\u00edta\u0165 v pr\u00edru\u010dk\u00e1ch, alebo to nesk\u00f4r prediskutujeme pri implement\u00e1cii do produkcie. Zatia\u013e len nastav\u00edme n1 v Stop rules, aby sa \u00faloha zastavila, akon\u00e1hle bude vykonan\u00e1 na na\u0161ej 1 jednotke.<\/p>\n<p>Vypln\u00edme potrebn\u00e9 \u00fadaje a ost\u00e1va len spusti\u0165!<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/4c93aa74e152f255c009ee888dfda4b3.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Klikneme na START a \u010dak\u00e1me. Teraz r\u00fdchlo za\u010dne po\u010d\u00edta\u010d po\u010d\u00edtat zabit\u00e9 pr\u00edstroje nedoladen\u00fdm skriptom! Nie, samozrejme. Tak\u00e9to \u00falohy sa zadaj\u00fa na dlh\u0161iu dobu, a to je ich rozdiel od skriptov, Ansible a podobne. Jednotky sa samy p\u00fdtaj\u00fa na \u00falohy pod\u013ea pl\u00e1nu alebo pri ich objaven\u00ed v sieti, ACS sleduje, ktor\u00e9 jednotky u\u017e dostali \u00falohy a ako dopadli, a zapisuje to do parametrov jednotky. V na\u0161ej skupine je 1 jednotka, a keby ich bolo 1001 \u2014 administr\u00e1tor by spustil t\u00fato \u00falohu a i\u0161iel na ryby.<\/p>\n<p>No tak. Re\u0161tartujte u\u017e router alebo re\u0161tartujte TR-069 klienta. V\u0161etko by malo prebehn\u00fa\u0165 hladko a Mr.White dostane nov\u00e9ho vlan. A na\u0161a \u00faloha v Stop rule prejde do stavu PAUSED. To znamen\u00e1, \u017ee ju e\u0161te m\u00f4\u017eete znova spusti\u0165 alebo zmeni\u0165. Ak kliknete na FINISH \u2014 \u00faloha sa ulo\u017e\u00ed do arch\u00edvu.<\/p>\n<h4>4.4 Aktualizujeme softv\u00e9r<\/h4>\n<p>Toto je ve\u013emi d\u00f4le\u017eit\u00fd bod, preto\u017ee firmv\u00e9r Mikrotiku je modul\u00e1rny, ale pridanie modulov nemen\u00ed celkov\u00fa verziu firmv\u00e9ru zariadenia. N\u00e1\u0161 ACS je v poriadku a na tak\u00fdto sp\u00f4sob nie sme zvyknut\u00ed.<br \/>\nTeraz to urob\u00edme v \u0161t\u00fdle quick&amp;dirty a zahrneme modul NTP do celkov\u00e9ho firmv\u00e9ru hne\u010f, ale akon\u00e1hle sa veria na zariaden\u00ed aktualizuje \u2014 nebudeme m\u00f4c\u0165 prida\u0165 \u010fal\u0161\u00ed modul rovnak\u00fdm sp\u00f4sobom.<br \/>\nDo produkcie je lep\u0161ie tak\u00fdto trik nepou\u017e\u00edva\u0165 a in\u0161talova\u0165 volite\u013en\u00e9 moduly pre typy jednotiek iba skriptami.<\/p>\n<p>Tak\u017ee, prv\u00e9, \u010do mus\u00edme urobi\u0165 \u2014 je pripravi\u0165 bal\u00ed\u010dky softv\u00e9ru potrebn\u00fdch verzi\u00ed a architekt\u00fary a da\u0165 ich na nejak\u00fd pr\u00edstupn\u00fd webov\u00fd server. Na testovanie p\u00f4jde ak\u00fdko\u013evek, ku ktor\u00e9mu sa dostane n\u00e1\u0161 Mr.White, a na produkciu je lep\u0161ie zostavi\u0165 autoaktualizovan\u00e9 zrkadlo po\u017eadovan\u00e9ho softv\u00e9ru, ktor\u00e9 nie je hanba vystavi\u0165 na webe.<br \/>\nD\u00f4le\u017eit\u00e9! Nezab\u00fadajte v\u017edy zahrn\u00fa\u0165 do aktualiz\u00e1ci\u00ed bal\u00edk s tr-069client!<\/p>\n<p>Ako sa uk\u00e1zalo, d\u013a\u017eka cesty k bal\u00ed\u010dkom je ve\u013emi d\u00f4le\u017eit\u00e1! Pri mojich pokusoch pou\u017ei\u0165 nie\u010do ako <code>http:\/\/192.168.0.237\/routeros\/stable\/mipsbe\/routeros-mipsbe-6.45.6.npk<\/code>, mikrotik sa dostal do cyklick\u00e9ho spojenia s prostriedkom, vracaj\u00fac v tr-069 log opakuj\u00face sa TRANSFERCOMPLETE. A str\u00e1vil som nejak\u00e9 nervov\u00e9 bunky, sna\u017eiac sa zisti\u0165, \u010do nie je v poriadku. Preto to zatia\u013e d\u00e1me na kore\u0148, k\u00fdm to nevyjasn\u00edme.<\/p>\n<p>Tak\u017ee by sme mali ma\u0165 tri npk s\u00fabory dostupn\u00e9 cez http. Mne sa to podarilo takto:<\/p>\n<pre><code class=\"bash\">http:\/\/192.168.0.241\/routeros-mipsbe-6.45.6.npk\nhttp:\/\/192.168.0.241\/routeros\/stable\/mipsbe\/ntp-6.45.6-mipsbe.npk\nhttp:\/\/192.168.0.241\/routeros\/stable\/mipsbe\/tr069-client-6.45.6-mipsbe.npk<\/code><\/pre>\n<p>Teraz to treba spracova\u0165 do xml s\u00faboru s FileType=\"1 Firmware Upgrade Image\", ktor\u00fd poskytneme mikrotiku. Nech sa vol\u00e1 ros.xml.<\/p>\n<p>Rob\u00edme pod\u013ea pokynov z <noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.mikrotik.com\/wiki\/Manual:TR069-client#RouterOS_Update_.281_Firmware_Upgrade_Image.29\">mikrotik-wiki<\/a><\/noindex>:<\/p>\n<pre><code class=\"xml\">http:\/\/192.168.0.241\/routeros-mipsbe-6.45.6.npk\n        \n        \n            http:\/\/192.168.0.241\/ntp-6.45.6-mipsbe.npk\n        \n        \n            http:\/\/192.168.0.241\/tr069-client-6.45.6-mipsbe.npk<\/code><\/pre>\n<p>Pritiahne pozornos\u0165 nedostatok <code>Username\/Password<\/code> na pr\u00edstup k serveru s\u0165ahovania. M\u00f4\u017eete bu\u010f sk\u00fasi\u0165 zada\u0165 to, ako je uveden\u00e9 v bode A.3.2.8 protokolu tr-069:<\/p>\n<pre><code class=\"xml\">http:\/\/192.168.0.237\/routeros\/stable\/mipsbe\/ntp-6.45.6-mipsbe.npk\nuser\npass<\/code><\/pre>\n<p>Alebo sa op\u00fdta\u0165 priamo ofici\u00e1lnych os\u00f4b mikrotiku, ako aj o maxim\u00e1lnej d\u013a\u017eke cesty k *.npk.<\/p>\n<p>Ideme do zn\u00e1meho <code>Files &amp; Scripts<\/code>, a vytvor\u00edme tam s\u00fabor typu SOFTWARE s <b>N\u00e1zov:<\/b>ros.xml, <b>Cie\u013eov\u00fd n\u00e1zov:<\/b>ros.xml a <b>Verzia:<\/b>6.45.6<br \/>\nPozor! Verzia mus\u00ed by\u0165 uveden\u00e1 presne v takom form\u00e1te, v akom sa zobrazuje na zariaden\u00ed a pren\u00e1\u0161a v parametroch <code>System.X_FREEACS-COM.Device.SoftwareVersion<\/code>.<\/p>\n<p>Vyber\u00e1me na stiahnutie n\u00e1\u0161 xm s\u00fabor a hotovo.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/aad6d1a64c5e81899c67b5bf085cc188.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Teraz m\u00e1me mno\u017estvo sp\u00f4sobov, ako aktualizova\u0165 zariadenie. Cezi Wizard v hlavnej ponuke, cez Advanced Provisioning a \u00falohy typu SOFTWARE, alebo jednoducho vst\u00fapi\u0165 do konfigur\u00e1cie jednotky a stla\u010di\u0165 Upgrade. Vyberieme najjednoduch\u0161iu cestu, inak u\u017e tento \u010dl\u00e1nok nar\u00e1stol.<\/p>\n<p><img decoding=\"async\" alt=\"TR-069 v Mikrotik. Testujeme Freeacs ako server automatickej konfigur\u00e1cie pre RouterOS\" src=\"\/wp-content\/uploads\/2019\/09\/045624f1a1ecc062b7e416c086df62d4.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Stla\u010d\u00edme tla\u010didlo, iniciujeme provision a hotovo. Testovac\u00ed program je ukon\u010den\u00fd. Teraz vieme robi\u0165 s mikrotik viac.<\/p>\n<h4>5. Z\u00e1ver<\/h4>\n<p>Ke\u010f som za\u010dal p\u00edsa\u0165, chcel som najprv op\u00edsa\u0165 pripojenie ip telef\u00f3nu a na jeho pr\u00edklade vysvetli\u0165, ak\u00e9 skvel\u00e9 m\u00f4\u017ee by\u0165, ke\u010f tr-069 funguje jednoducho a bez n\u00e1mahy. Ale nesk\u00f4r, pri postupe a sk\u00faman\u00ed materi\u00e1lov, som si pomyslel, \u017ee pre toho, kto pripojil mikrotik \u2014 u\u017e \u017eiadny telef\u00f3n nebude hrozbou pri samostatnom \u0161t\u00fadiu.<\/p>\n<p>Vo v\u0161eobecnosti je Freeacs, ktor\u00fd sme testovali, u\u017e mo\u017en\u00e9 aplikova\u0165 v predaji, av\u0161ak je potrebn\u00e9 nastavi\u0165 bezpe\u010dnos\u0165, SSL, mikrotiky pre automatick\u00fa konfigur\u00e1ciu po resetovan\u00ed, doladi\u0165 spr\u00e1vne pridanie typu jednotky, rozobra\u0165 \u010dinnos\u0165 webov\u00fdch slu\u017eieb a fusion shell a e\u0161te ove\u013ea viac. Sk\u00fa\u0161ajte, vynaliezajte a p\u00ed\u0161te pokra\u010dovanie!<\/p>\n<p>\u010eakujem v\u0161etk\u00fdm za pozornos\u0165! Budem r\u00e1d za opravy a koment\u00e1re!<\/p>\n<p>Zoznam pou\u017eit\u00fdch materi\u00e1lov a u\u017eito\u010dn\u00e9 odkazy:<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/forum.mikrotik.com\/viewtopic.php?t=116977&amp;start=50\">T\u00e9ma f\u00f3ra, na ktor\u00fa som natrafil na za\u010diatku h\u013eadania t\u00e9my<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.broadband-forum.org\/download\/TR-069_Amendment-6.pdf\">TR-069 CPE WAN Management Protocol Amendment-6<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/freeacs\/freeacs\/wiki\">Wiki Freeacs<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/wiki.mikrotik.com\/wiki\/Manual:TR069-parameters-6.39\">Parametre tr-069 v mikrotiku a ich zodpovedaj\u00face pr\u00edkazy termin\u00e1lu<\/a><\/noindex><\/p>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/468241\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u044f \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u044e \u043f\u043e\u0448\u0430\u0433\u043e\u0432\u043e \u043e\u043f\u0438\u0441\u0430\u0442\u044c \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u0442\u0435\u0441\u0442\u043e\u0432\u043e\u0433\u043e \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u043f\u0440\u0435\u043a\u0440\u0430\u0441\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 Freeacs \u0434\u043e \u043f\u043e\u043b\u043d\u043e\u0441\u0442\u044c\u044e \u0440\u0430\u0431\u043e\u0442\u043e\u0441\u043f\u043e\u0441\u043e\u0431\u043d\u043e\u0433\u043e \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u044f, \u0438 \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u044c \u043f\u0440\u0430\u043a\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u043f\u0440\u0438\u0435\u043c\u044b \u0434\u043b\u044f \u0440\u0430\u0431\u043e\u0442\u044b \u0441 mikrotik: \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u044e \u0447\u0435\u0440\u0435\u0437 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u044b, \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u0441\u043a\u0440\u0438\u043f\u0442\u043e\u0432, \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0443 \u0434\u043e\u043f.\u043c\u043e\u0434\u0443\u043b\u0435\u0439 \u0438 \u0442.\u0434. \u0426\u0435\u043b\u044c \u0441\u0442\u0430\u0442\u044c\u0438 \u2014 \u043f\u043e\u0434\u0442\u043e\u043b\u043a\u043d\u0443\u0442\u044c \u043a\u043e\u043b\u043b\u0435\u0433 \u043a \u043e\u0442\u043a\u0430\u0437\u0443 \u043e\u0442 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0441\u0435\u0442\u0435\u0432\u044b\u043c\u0438 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\u043c\u0438 \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e \u0443\u0436\u0430\u0441\u043d\u044b\u0445 \u0433\u0440\u0430\u0431\u043b\u0435\u0439 \u0438 \u043a\u043e\u0441\u0442\u044b\u043b\u0435\u0439, \u0432 \u0432\u0438\u0434\u0435 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28841,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38422","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.3 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u044f \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u044e \u043f\u043e\u0448\u0430\u0433\u043e\u0432\u043e \u043e\u043f\u0438\u0441\u0430\u0442\u044c \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u0442\u0435\u0441\u0442\u043e\u0432\u043e\u0433\u043e \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u043f\u0440\u0435\u043a\u0440\u0430\u0441\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 Freeacs \u0434\u043e \u043f\u043e\u043b\u043d\u043e\u0441\u0442\u044c\u044e.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47TR-069 \u0432 Mikrotik. \u0418\u0441\u043f\u044b\u0442\u044b\u0432\u0430\u0435\u043c Freeacs \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0430\u0432\u0442\u043e\u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 \u0434\u043b\u044f RouterOS | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u044f \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u044e \u043f\u043e\u0448\u0430\u0433\u043e\u0432\u043e \u043e\u043f\u0438\u0441\u0430\u0442\u044c \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u0442\u0435\u0441\u0442\u043e\u0432\u043e\u0433\u043e \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u043f\u0440\u0435\u043a\u0440\u0430\u0441\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 Freeacs \u0434\u043e \u043f\u043e\u043b\u043d\u043e\u0441\u0442\u044c\u044e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:23:40+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-12-15T00:12:35+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47TR-069 v Mikrotiku. Testujeme Freeacs ako server pre automatick\u00fa konfigur\u00e1ciu pre RouterOS | ProHoster","description":"V tomto \u010dl\u00e1nku sa pok\u00fasim krok za krokom pop\u00edsa\u0165 proces in\u0161tal\u00e1cie testovacieho servera skvel\u00e9ho projektu Freeacs.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47TR-069 \u0432 Mikrotik. \u0418\u0441\u043f\u044b\u0442\u044b\u0432\u0430\u0435\u043c Freeacs \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u0430\u0432\u0442\u043e\u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 \u0434\u043b\u044f RouterOS | ProHoster","og:description":"\u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u044f \u043f\u043e\u043f\u0440\u043e\u0431\u0443\u044e \u043f\u043e\u0448\u0430\u0433\u043e\u0432\u043e \u043e\u043f\u0438\u0441\u0430\u0442\u044c \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u0442\u0435\u0441\u0442\u043e\u0432\u043e\u0433\u043e \u0441\u0435\u0440\u0432\u0435\u0440\u0430 \u043f\u0440\u0435\u043a\u0440\u0430\u0441\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 Freeacs \u0434\u043e \u043f\u043e\u043b\u043d\u043e\u0441\u0442\u044c\u044e.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/tr-069-v-mikrotik-ispytyvaem-freeacs-v-kachestve-servera-avtokonfiguratsii-dlya-routeros","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:23:40+00:00","article:modified_time":"2020-12-15T00:12:35+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38422","title":null,"description":"","keywords":"","keyphrases":null,"primary_term":null,"canonical_url":"","og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 22:00:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:09:23","updated":"2026-01-23 22:00:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/38422","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=38422"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/38422\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/28841"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=38422"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=38422"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=38422"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}