{"id":89276,"date":"2020-07-21T13:42:28","date_gmt":"2020-07-21T11:42:28","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1"},"modified":"2026-07-05T10:59:44","modified_gmt":"2026-07-05T08:59:44","slug":"kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1","title":{"rendered":"Cum s\u0103 accesezi IPVPN Beeline prin IPSec. Partea 1","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Bun\u0103! \u00cen <a href=\"https:\/\/habr.com\/ru\/company\/beeline\/blog\/498450\/\" rel=\"nofollow\">postarea anterioar\u0103<\/a> am descris func\u021bionarea serviciului nostru MultiSIM \u00een ceea ce prive\u0219te <a href=\"https:\/\/moskva.beeline.ru\/business\/mobile-and-internet\/office-internet\/rezervirovanie-internet-soedineniia\/?utm_source=habr\" rel=\"nofollow\">rezervarea<\/a> \u0219i <a href=\"https:\/\/moskva.beeline.ru\/business\/mobile-and-internet\/office-internet\/obedinenie-mobilnih-setey\/?utm_source=habr\" rel=\"nofollow\">balansarea<\/a> canalelor. A\u0219a cum a fost men\u021bionat, clien\u021bii sunt conecta\u021bi la re\u021bea prin VPN, iar ast\u0103zi voi povesti pu\u021bin mai mult despre VPN \u0219i posibilit\u0103\u021bile noastre \u00een aceast\u0103 privin\u021b\u0103.<\/p>\n<p>Trebuie s\u0103 men\u021bionez c\u0103 avem, ca operator de telecomunica\u021bii, o re\u021bea MPLS vast\u0103, care pentru clien\u021bii de telefonie fix\u0103 este \u00eemp\u0103r\u021bit\u0103 \u00een dou\u0103 segmente principale \u2014 cel utilizat pentru accesul la internet \u0219i cel utilizat pentru crearea de re\u021bele izolate \u2014 \u0219i anume, prin acest segment MPLS circul\u0103 traficul IPVPN (L3 OSI) \u0219i VPLAN (L2 OSI) pentru clien\u021bii no\u0219tri corporativi.<\/p>\n<p><a href=\"https:\/\/habr.com\/ru\/company\/beeline\/blog\/510154\/\" rel=\"nofollow\"><img decoding=\"async\" style=\"display: block; margin: 0 auto;\" src=\"\/wp-content\/uploads\/2020\/07\/b5b3d5c28266d1916b7ac93e94d2fe5b.jpg\" alt=\"Cum s\u0103 accesezi IPVPN Beeline prin IPSec. Partea 1\" \/><\/a><a rel=\"nofollow\" name=\"habracut\"><\/a><br \/>\n\u00cen mod obi\u0219nuit, conectarea unui client se face astfel.<\/p>\n<p>Se traseaz\u0103 o linie de acces p\u00e2n\u0103 la biroul clientului de la cel mai apropiat punct de prezen\u021b\u0103 a re\u021belei (nod MEN, PPRL, BSSS, FTTB etc.) \u0219i apoi, canalul este configurat prin re\u021beaua de transport p\u00e2n\u0103 la routerul corespunz\u0103tor RE-MPLS, pe care \u00eel extragem \u00eentr-un VRF creat special pentru client, av\u00e2nd \u00een vedere profilul de trafic necesar clientului (etichetarea profilului este aleas\u0103 pentru fiecare port de acces, \u00een baza valorilor ip precedence 0, 1, 3, 5).<\/p>\n<p>Dac\u0103 din diverse motive nu putem organiza complet ultima mil\u0103 pentru client, de exemplu, biroul clientului se afl\u0103 \u00eentr-un centru de afaceri unde un alt furnizor este prioritar, sau nu exist\u0103 pur \u0219i simplu punctul nostru de prezen\u021b\u0103 \u00een apropiere, atunci anterior clien\u021bii erau nevoi\u021bi s\u0103 creeze mai multe re\u021bele IPVPN cu diferi\u021bi furnizori (nu cea mai avantajoas\u0103 arhitectur\u0103 din punct de vedere al pre\u021bului) sau s\u0103 rezolve singuri problemele de acces la propriul VRF pe re\u021beaua internet.<\/p>\n<p>Mul\u021bi f\u0103ceau acest lucru instal\u00e2nd un gateway IPVPN pentru internet \u2014 instala un router de margine (hardware sau o solu\u021bie pe baz\u0103 de Linux), conecta un port la canalul IPVPN \u0219i altul \u2014 la canalul de internet, lansau pe acesta <a href=\"https:\/\/prohoster.info\/ro\/vpn\/\">un server VPN<\/a> \u0219i conectau utilizatorii prin propriul lor gateway VPN. Evident, o astfel de schem\u0103 genereaz\u0103 \u0219i probleme: o astfel de infrastructur\u0103 trebuie construit\u0103 eficient \u0219i, ceea ce este cel mai incomod \u2014 \u00eentre\u021binut\u0103 \u0219i dezvoltat\u0103.<\/p>\n<p>Pentru a simplifica via\u021ba clien\u021bilor no\u0219tri, am instalat un hub VPN centralizat \u0219i am organizat suport pentru conexiunile deasupra internetului folosind IPSec, astfel c\u0103 acum clien\u021bii trebuie doar s\u0103 configureze routerul lor pentru a func\u021biona cu hub-ul nostru VPN printr-un tunel IPSec peste orice internet public, iar noi vom rula traficul acestui client \u00een VRF-ul s\u0103u.<\/p>\n<h2>Pentru cine este util<\/h2>\n<p>&nbsp;<\/p>\n<ul>\n<li>Pentru cei care au deja o re\u021bea IPVPN mare \u0219i au nevoie de noi conect\u0103ri \u00eentr-un timp scurt.<\/li>\n<li>Pentru to\u021bi cei care din diverse motive doresc s\u0103 transfere o parte din traficul de pe internetul public \u00een IPVPN, dar s-au confruntat anterior cu limit\u0103ri tehnice legate de mai mul\u021bi furnizori de servicii.<\/li>\n<li>Pentru cei care au \u00een prezent mai multe re\u021bele VPN dispersate pe diferite re\u021bele de telecomunica\u021bii. Exist\u0103 clien\u021bi care au organizat cu succes IPVPN at\u00e2t cu Beeline, c\u00e2t \u0219i cu Megafon, \u0219i cu Rostelecom etc. Pentru a simplifica lucrurile, pot r\u0103m\u00e2ne doar pe re\u021beaua noastr\u0103 unic\u0103, <a href=\"https:\/\/prohoster.info\/ro\/vpn\/\">VPN<\/a>, iar toate celelalte canale ale altor operatori s\u0103 fie redirec\u021bionate c\u0103tre internet, dup\u0103 care s\u0103 se conecteze la IPVPN Beeline prin IPSec \u0219i internetul acestor operatori.<\/li>\n<li>Pentru cei care au deja o re\u021bea IPVPN suprapus\u0103 pe internet.<\/li>\n<\/ul>\n<p>Dac\u0103 desf\u0103\u0219ura\u021bi totul la noi, clien\u021bii ob\u021bin at\u00e2t suport complet pentru VPN, c\u00e2t \u0219i o infrastructur\u0103 rezistent\u0103, precum \u0219i set\u0103ri standard care vor func\u021biona pe orice router cu care sunt obi\u0219nui\u021bi (indiferent dac\u0103 este vorba de Cisco sau Mikrotik, important este s\u0103 suporte corect IPSec\/IKEv2 cu metode standardizate de autentificare). Apropo de IPSec \u2014 \u00een prezent sprijinim doar acesta, dar avem \u00een plan s\u0103 lans\u0103m func\u021bionarea complet\u0103 \u0219i pentru OpenVPN \u0219i Wireguard, astfel \u00eenc\u00e2t clien\u021bii s\u0103 nu depind\u0103 de protocol \u0219i s\u0103 fie \u0219i mai u\u0219or s\u0103 mute totul la noi; de asemenea, vrem s\u0103 \u00eencepe\u021bi s\u0103 conecta\u021bi clien\u021bi de pe computer \u0219i dispozitive mobile (solu\u021bii \u00eencorporate \u00een sistemele de operare, Cisco AnyConnect \u0219i strongSwan \u0219i altele similare). Cu aceast\u0103 abordare, de facto construirea infrastructurii poate fi \u00eencredin\u021bat\u0103 operatorului, l\u0103s\u00e2nd doar configurarea CPE sau a gazdei.<\/p>\n<p>Cum decurge procesul de conectare pentru modul IPSec:<\/p>\n<ol>\n<li>Client submits a request to their manager specifying the required connection speed, traffic profile, and IP addressing parameters for the tunnel (by default, a subnet with a mask \/30) and the type of routing (static or BGP). To transmit routes to the client\u2019s local networks in the connected office, IKEv2 mechanisms of the IPSec protocol phase are used with appropriate settings on the client router, or they are announced via BGP in MPLS from the private BGP AS specified by the client in the request. Thus, information about the client networks' routes is fully controlled by the client through the client router settings.<\/li>\n<li>In response from their manager, the client receives accounting data to include in their VRF as follows:\n<ul>\n<li>IP address of VPN-HUB<\/li>\n<li>Login<\/li>\n<li>Authentication password<\/li>\n<\/ul>\n<\/li>\n<li>Configures CPE, below, for example, two variants of basic configuration:<b class=\"spoiler_title\">Option for Cisco:<\/b><br \/>\ncrypto ikev2 keyring BeelineIPsec_keyring<br \/>\npeer Beeline_VPNHub<br \/>\naddress 62.141.99.183 <i> \u2013VPN hub Beeline<\/i><br \/>\npre-shared-key<br \/>\n!<br \/>\n<i>For the static routing option, routes to networks accessible through the VPN hub can be specified in the IKEv2 settings and will automatically appear as static routes in the CPE's routing table. These settings can also be made using the standard method for setting static routes (see below).<\/i><\/p>\n<p>crypto ikev2 authorization policy FlexClient-author<\/p>\n<p><i>The route to networks behind the CPE router is a mandatory configuration for static routing between CPE and PE. Data transmission of routes to PE is done automatically when the tunnel is established via the IKEv2 interaction.<\/i><\/p>\n<p>route set remote ipv4 10.1.1.0 255.255.255.0 <i> \u2013Local office network<\/i><br \/>\n!<br \/>\ncrypto ikev2 profile BeelineIPSec_profile<br \/>\nidentity local<br \/>\nauthentication local pre-share<br \/>\nauthentication remote pre-share<br \/>\nkeyring local BeelineIPsec_keyring<br \/>\naaa authorization group psk list group-author-list FlexClient-author<br \/>\n!<br \/>\ncrypto ikev2 client flexvpn BeelineIPsec_flex<br \/>\npeer 1 Beeline_VPNHub<br \/>\nclient connect Tunnel1<br \/>\n!<br \/>\ncrypto ipsec transform-set TRANSFORM1 esp-aes 256 esp-sha256-hmac<br \/>\nmode tunnel<br \/>\n!<br \/>\ncrypto ipsec profile default<br \/>\nset transform-set TRANSFORM1<br \/>\nset ikev2-profile BeelineIPSec_profile<br \/>\n!<br \/>\ninterface Tunnel1<br \/>\nip address 10.20.1.2 255.255.255.252 <i> \u2013Tunnel address<\/i><br \/>\ntunnel source GigabitEthernet0\/2 <i> \u2013Internet access interface<\/i><br \/>\ntunnel mode ipsec ipv4<br \/>\ntunnel destination dynamic<br \/>\ntunnel protection ipsec profile default<br \/>\n!<br \/>\n<i>Routes to the client\u2019s private networks, accessible via the Beeline VPN hub, can be specified statically.<\/i><\/p>\n<p>ip route 172.16.0.0 255.255.0.0 Tunnel1<br \/>\nip route 192.168.0.0 255.255.255.0 Tunnel1<\/p>\n<p><b class=\"spoiler_title\">Option for Huawei (ar160\/120):<\/b><br \/>\nike local-name<br \/>\n#<br \/>\nacl name ipsec 3999<br \/>\nregula 1 permite ip surs\u0103 10.1.1.0 0.0.0.255 <i> \u2013Local office network<\/i><br \/>\n#<br \/>\naaa<br \/>\nschema-serviciu IPSEC<br \/>\nsetare rut\u0103 acl 3999<br \/>\n#<br \/>\npropunere ipsec ipsec<br \/>\nalgoritm de autentificare esp sha2-256<br \/>\nalgoritm de criptare esp aes-256<br \/>\n#<br \/>\npropunere ike implicit\u0103<br \/>\nalgoritm de criptare aes-256<br \/>\ngrup dh2<br \/>\nalgoritm de autentificare sha2-256<br \/>\nmetod\u0103 de autentificare pre-share<br \/>\nalgoritm de integritate hmac-sha2-256<br \/>\nprf hmac-sha2-256<br \/>\n#<br \/>\npartener ike ipsec<br \/>\ncheie pre-partajat\u0103 simpl\u0103<br \/>\ntip id-local fqdn<br \/>\ntip id-remote ip<br \/>\nadres\u0103-remote 62.141.99.183 <i> \u2013VPN hub Beeline<\/i><br \/>\nschema-serviciu IPSEC<br \/>\ncerere schimb de configura\u021bie<br \/>\nsetare schimb de configura\u021bie accept<br \/>\nsetare schimb de configura\u021bie trimite<br \/>\n#<br \/>\nprofil ipsec ipsecprof<br \/>\npartener ike ipsec<br \/>\npropunere ipsec<br \/>\n#<br \/>\ninterfa\u021b\u0103 Tunnel0\/0\/0<br \/>\nip address 10.20.1.2 255.255.255.252 <i> \u2013Tunnel address<\/i><br \/>\nprotocol tunel ipsec<br \/>\nsurs\u0103 GigabitEthernet0\/0\/1 <i> \u2013Internet access interface<\/i><br \/>\nprofil ipsec ipsecprof<br \/>\n#<br \/>\n<i>Rutele c\u0103tre re\u021belele private ale clientului, disponibile prin concentratorul VPN Beeline, pot fi stabilite static<\/i><\/p>\n<p>ip rut\u0103-static 192.168.0.0 255.255.255.0 Tunnel0\/0\/0<br \/>\nip rut\u0103-static 172.16.0.0 255.255.0.0 Tunnel0\/0\/0<\/li>\n<\/ol>\n<p>Schema de comunicare rezultat\u0103 arat\u0103 astfel:<\/p>\n<p><img decoding=\"async\" style=\"display: block; margin: 0 auto;\" src=\"\/wp-content\/uploads\/2020\/07\/8083e9190bdcdd816ac3014d7b7f5de4.jpg\" alt=\"Cum s\u0103 accesezi IPVPN Beeline prin IPSec. Partea 1\" \/><\/p>\n<p>Dac\u0103 clientul nu are exemple de configurare de baz\u0103, de obicei \u00eel ajut\u0103m s\u0103 le creeze \u0219i le facem disponibile pentru ceilal\u021bi.<\/p>\n<p>R\u0103m\u00e2ne doar s\u0103 conect\u0103m CPE la Internet, s\u0103 facem ping c\u0103tre partea opus\u0103 a tunelului VPN \u0219i c\u0103tre un anumit host din interiorul VPN, \u0219i totul poate fi considerat conectat.<\/p>\n<p>\u00cen articolul urm\u0103tor, vom explica cum am combinat aceast\u0103 schem\u0103 cu rezervarea IPSec \u0219i MultiSIM folosind CPE Huawei: instal\u0103m CPE-ul nostru Huawei la clien\u021bi, care poate utiliza nu doar un canal de internet prin fir, ci \u0219i 2 SIM-uri diferite, iar CPE-ul reconstruie\u0219te automat tunelul IPSec fie prin WAN prin fir, fie prin radio (LTE#1\/LTE#2), realiz\u00e2nd o rezilien\u021b\u0103 ridicat\u0103 a serviciului final.<\/p>\n<p>Un mare mul\u021bumesc pentru preg\u0103tirea acestui articol (\u0219i, de fapt, autorilor acestor solu\u021bii tehnice) colegilor din RnD!<\/p>\n<p>Sursa: <a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/beeline\/blog\/510154\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u0432\u0435\u0442! \u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u043c \u043f\u043e\u0441\u0442\u0435 \u044f \u043e\u043f\u0438\u0441\u0430\u043b \u0440\u0430\u0431\u043e\u0442\u0443 \u043d\u0430\u0448\u0435\u0433\u043e \u0441\u0435\u0440\u0432\u0438\u0441\u0430 MultiSIM \u0432 \u0447\u0430\u0441\u0442\u0438 \u0440\u0435\u0437\u0435\u0440\u0432\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0438 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u043a\u0438 \u043a\u0430\u043d\u0430\u043b\u043e\u0432. \u041a\u0430\u043a \u0431\u044b\u043b\u043e \u0443\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u043e, \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u0432 \u043a \u0441\u0435\u0442\u0438 \u043c\u044b \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0430\u0435\u043c \u0447\u0435\u0440\u0435\u0437 VPN, \u0438 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u044f \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0431\u043e\u043b\u044c\u0448\u0435 \u043f\u0440\u043e VPN \u0438 \u043d\u0430\u0448\u0438 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0432 \u044d\u0442\u043e\u0439 \u0447\u0430\u0441\u0442\u0438. \u041d\u0430\u0447\u0430\u0442\u044c \u0441\u0442\u043e\u0438\u0442 \u0441 \u0442\u043e\u0433\u043e, \u0447\u0442\u043e \u0443 \u043d\u0430\u0441 \u043a\u0430\u043a \u0443 \u043e\u043f\u0435\u0440\u0430\u0442\u043e\u0440\u0430 \u0441\u0432\u044f\u0437\u0438 \u0435\u0441\u0442\u044c \u0441\u0432\u043e\u044f \u043e\u0433\u0440\u043e\u043c\u043d\u0430\u044f MPLS-\u0441\u0435\u0442\u044c, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":89277,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-89276","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.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442!\" \/>\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\/ro\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\udd47\u041a\u0430\u043a \u043f\u043e\u043f\u0430\u0441\u0442\u044c \u0432 IPVPN \u0411\u0438\u043b\u0430\u0439\u043d \u0447\u0435\u0440\u0435\u0437 IPSec. \u0427\u0430\u0441\u0442\u044c 1 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442!\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1\" \/>\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=\"2020-07-21T11:42:28+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-07-05T08:59:44+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\udd47Cum s\u0103 accesa\u021bi IPVPN Beeline prin IPSec. Partea 1 | ProHoster","description":"Bun\u0103!","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\udd47\u041a\u0430\u043a \u043f\u043e\u043f\u0430\u0441\u0442\u044c \u0432 IPVPN \u0411\u0438\u043b\u0430\u0439\u043d \u0447\u0435\u0440\u0435\u0437 IPSec. \u0427\u0430\u0441\u0442\u044c 1 | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442!","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1","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":"2020-07-21T11:42:28+00:00","article:modified_time":"2026-07-05T08:59:44+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"89276","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 13:13:28","updated":"2022-09-30 17:39:06","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/89276","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=89276"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/89276\/revisions"}],"predecessor-version":[{"id":182465,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/89276\/revisions\/182465"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/89277"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=89276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=89276"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=89276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}