{"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\/et\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1","title":{"rendered":"Kuidas p\u00e4\u00e4seda Beline IPVPN-i l\u00e4bi IPSec. Osa 1","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Tere! A <a href=\"https:\/\/habr.com\/ru\/company\/beeline\/blog\/498450\/\" rel=\"nofollow\">t\u00f5in v\u00e4lja, et satelliidid ja praht, mis asuvad alla 600 km, kukuvad orbitaalilt paariaastaga \u2014 atmosf\u00e4\u00e4ri takistuse t\u00f5ttu, v\u00e4hendades oluliselt Kessleri s\u00fcndroomi v\u00f5imalusi. SpaceX'i tegevus prahi osas tundub, nagu nad ei m\u00f5tleks \u00fcldse kosmosereostusele. Vaadates Starlinki elluviimise detaile, on mul raske ette kujutada paremat moodust prahi hulga v\u00e4hendamiseks orbiidil.<\/a> ma kirjeldasin meie MultiSIM teenuse t\u00f6\u00f6d osas <a href=\"https:\/\/moskva.beeline.ru\/business\/mobile-and-internet\/office-internet\/rezervirovanie-internet-soedineniia\/?utm_source=habr\" rel=\"nofollow\">reservatsioon<\/a> ja <a href=\"https:\/\/moskva.beeline.ru\/business\/mobile-and-internet\/office-internet\/obedinenie-mobilnih-setey\/?utm_source=habr\" rel=\"nofollow\">tasakaalustamine<\/a> kanalid. Nagu mainitud, \u00fchendame kliente v\u00f5rguga l\u00e4bi VPN-i ja t\u00e4na r\u00e4\u00e4gin natuke rohkem VPN-ist ja meie v\u00f5imalustest sellel alal.<\/p>\n<p>Alustada tasub sellest, et meil kui sideteenuse osutajal on oma suur MPLS-v\u00f5rk, mis on fikseeritud side klientide jaoks jagatud kaheks peamiseks segmendiks \u2014 see, mis on m\u00f5eldud otse Internetti juurdep\u00e4\u00e4suks, ja see, mida kasutatakse isoleeritud v\u00f5rkude loomiseks \u2014 ja just l\u00e4bi selle MPLS-segmendi liigub IPVPN (L3 OSI) ja VPLAN (L2 OSI) liiklus meie \u00e4riklientide jaoks.<\/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=\"Kuidas p\u00e4\u00e4seda Beline IPVPN-i l\u00e4bi IPSec. Osa 1\" \/><\/a><a rel=\"nofollow\" name=\"habracut\"><\/a><br \/>\nTavaliselt toimub kliendi \u00fchendamine j\u00e4rgmiselt.<\/p>\n<p>Kliendi b\u00fcroosse paigaldatakse juurdep\u00e4\u00e4suliin l\u00e4himast v\u00f5rgusoleku punktist (NODE MEN, P\u0420L, B\u0421\u0421\u0421, FTTB jne) ning edasi, kanal m\u00e4\u00e4ratakse transpordiv\u00f5rgus vastava RE-MPLS marsruuterini, kus toome selle v\u00e4lja kliendi jaoks spetsiaalselt loodud VRF-i, arvesse v\u00f5ttes liiklusprofiili, mis kliendile vajalik (profiilim\u00e4rgid valitakse iga juurdep\u00e4\u00e4su porte jaoks, tuginedes ip precedence v\u00e4\u00e4rtustele 0,1,3,5).<\/p>\n<p>Kui mingil p\u00f5hjusel ei suuda me kliendile viimase miili t\u00e4ielikult korraldada, n\u00e4iteks kui kliendi b\u00fcroo asub \u00e4rihoones, kus eelistatakse m\u00f5nda teist teenusepakkujat, v\u00f5i l\u00e4heduses ei ole meie v\u00f5rgusoleku punkti, siis pidid kliendid varem looma mitu IPVPN-v\u00f5rku erinevates teenusepakkujates (mitte k\u00f5ige kasumlikum arhitektuur) v\u00f5i iseseisvalt lahendama ligip\u00e4\u00e4su k\u00fcsimused oma VRF-i juurde \u00fcle Interneti.<\/p>\n<p>Paljud tegid seda IPVPN-interneti v\u00e4rava paigaldamisega \u2014 paigaldasid piiriv\u00f5rgu marsruuteri (seadmestiku v\u00f5i m\u00f5ne lahenduse Linuxi baasil), \u00fchendasid \u00fcks port IPVPN-kanali ja teise \u2014 Interneti-kanali, k\u00e4ivitasid seal oma <a href=\"https:\/\/prohoster.info\/et\/vpn\/\">VPN-serveri<\/a> ja \u00fchendasid kasutajad l\u00e4bi oma VPN-v\u00e4rava. Loomulikult tekitab selline skeem ka koormusi: sellist infrastruktuuri tuleb osata \u00fcles ehitada ja, mis k\u00f5ige ebamugavam \u2014 kasutada ja arendada.<\/p>\n<p>Kliendi elu lihtsustamiseks oleme loonud keskse VPN-hubi ja korraldanud toetuse interneti kaudu \u00fchenduste tegemiseks, kasutades IPSec'i. See t\u00e4hendab, et n\u00fc\u00fcd peavad kliendid lihtsalt seadistama oma ruuteri, et kasutada meie VPN-hubi IPSec-tunneli kaudu mistahes avalikus internetis, ning me suuname selle kliendi liikluse tema VRF-i.<\/p>\n<h2>Kellele see on kasulik<\/h2>\n<p>&nbsp;<\/p>\n<ul>\n<li>Neile, kellel juba on suur IPVPN-v\u00f5rk ja kes vajavad uusi \u00fchendusi kiiresti.<\/li>\n<li>K\u00f5igile, kes mingil p\u00f5hjusel soovivad viia osa liiklust avalikust internetist IPVPN-i, kuid on varem kokku puutunud tehniliste piirangutega, mis on seotud mitmete teenusepakkujatega.<\/li>\n<li>Neile, kellel on praegu mitu eraldiseisvat VPN-v\u00f5rku erinevatelt sideettev\u00f5tetelt. On kliente, kellel on edukalt korraldatud IPVPN nii Beeline'i, MegaFoni kui ka Rostelekoma jt poolt. Lihtsuse huvides v\u00f5iks j\u00e4\u00e4da ainult meie \u00fchtsesse <a href=\"https:\/\/prohoster.info\/et\/vpn\/\">VPN<\/a>, k\u00f5ik teised kanalid teiste operaatorite kaudu suunatakse internetti, p\u00e4rast mida \u00fchendatakse IPVPN Beeline'iga IPSec'i ja nende operaatorite interneti kaudu.<\/li>\n<li>Neile, kellel on juba IPVPN-v\u00f5rk, mis on asetatud interneti peale.<\/li>\n<\/ul>\n<p>Kui k\u00f5ik meie juurde \u00fcles seada, saavad kliendid t\u00e4ieliku toe VPN-i osas, t\u00f5sise infrastruktuuri reserveerimise ning t\u00fc\u00fcpilised seadistused, mis t\u00f6\u00f6tavad igas tuntud ruuteris (olgu see siis Cisco v\u00f5i Mikrotik, peaasi, et see toetaks normaalselt IPSec\/IKEv2 ja standardiseeritud autentimismeetodeid). Muide, IPSec'i toetame praegu ainult seda, kuid plaanis on k\u00e4ivitada ka OpenVPN ja Wireguard, et kliendid saaksid protokollist s\u00f5ltumatud ja veelgi lihtsamalt k\u00f5ik meie juurde viia, samuti soovime hakata \u00fchendama kliente arvutite ja mobiilsete seadmetega (s\u00fcsteemi sisseehitatud lahendused, Cisco AnyConnect ja strongSwan ning sarnased). Sellise l\u00e4henemisega v\u00f5ib de facto infrastruktuuri julgelt operaatorile usaldada, j\u00e4ttes alles ainult CPE v\u00f5i hosti seadistamise.<\/p>\n<p>Kuidas toimub \u00fchendamise protsess IPSec-re\u017eiimis:<\/p>\n<ol>\n<li>Klient esitab oma juhile taotluse, milles n\u00e4itab vajalikku \u00fchenduse kiirus, liiklusprofiil ja IP-aadressi parameetrid tunnelile (vaikimisi alajaotus maskiga \/30) ja marsruutimise t\u00fc\u00fcp (staatiline v\u00f5i BGP). Klientide kohalike v\u00f5rkude marsruutide edastamiseks \u00fchendatud b\u00fcroodes kasutatakse IPSec protokolli IKEv2 faasi mehhanisme koos vastavate seadistustega kliendi ruuteris v\u00f5i kuulutatakse need BGP kaudu MPLS-is, l\u00e4htudes kliendi esitatud privaatsetest BGP AS-idest. Seega kontrollib klient oma v\u00f5rkude marsruutide teavet t\u00e4ielikult oma kluster-ruuteri seadete kaudu.<\/li>\n<li>Oma juhilt saab klient arveldamisandmed, mida saab lisada oma VRF-i, n\u00e4iteks:\n<ul>\n<li>VPN-HUBi IP-aadress<\/li>\n<li>Kasutajanimi<\/li>\n<li>Autentimise parool<\/li>\n<\/ul>\n<\/li>\n<li>Seadistab SRV, allpool on n\u00e4ha kaks baas \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430atsiooni varianti:<b class=\"spoiler_title\">Cisco variant:<\/b><br \/>\ncrypto ikev2 keyring BeelineIPsec_keyring<br \/>\npeer Beeline_VPNHub<br \/>\naddress 62.141.99.183 <i> \u2013 Beeline VPN-keskus<\/i><br \/>\npre-shared-key<br \/>\n!<br \/>\n<i>Staatilise marsruutimise variandi puhul v\u00f5ivad marsruudid, mis on saadaval VPN-hubi kaudu, olla m\u00e4\u00e4ratud IKEv2 seadistuses ning need ilmuvad automaatselt staatiliste marsruutidena SRV marsruuditabelis. Need seadistused on v\u00f5imalik teha ka standardsel viisil staatiliste marsruutide m\u00e4\u00e4ramisel (vt allpool).<\/i><\/p>\n<p>crypto ikev2 authorization policy FlexClient-author<\/p>\n<p><i>Marsruut tagasi v\u00f5rgustike k\u00fcljest, mis on SRV ruuteri taga, on staatilise marsruutimise kohustuslik seadistus SRV ja PE vahel. Marsruutide andmete edastamine PE-le toimub automaatselt tunnelite t\u00f5usmise ajal IKEv2 interaktsiooni kaudu.<\/i><\/p>\n<p>route set remote ipv4 10.1.1.0 255.255.255.0 <i> \u2013 Kohalik b\u00fcroo v\u00f5rk<\/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> \u2013 Tunneliaadress<\/i><br \/>\ntunnel source GigabitEthernet0\/2 <i> \u2013 Interneti-\u00fchenduse liides<\/i><br \/>\ntunnel mode ipsec ipv4<br \/>\ntunnel destination dynamic<br \/>\ntunnel protection ipsec profile default<br \/>\n!<br \/>\n<i>Marsruute privaatsete klientide v\u00f5rkudesse, mis on kergestatud Beeline VPN-keskuse kaudu, saab m\u00e4\u00e4rata staatiliselt.<\/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\">Huawei (ar160\/120) variant:<\/b><br \/>\nike local-name<br \/>\n#<br \/>\nacl name ipsec 3999<br \/>\nreegl 1 lubab ip allika 10.1.1.0 0.0.0.255 <i> \u2013 Kohalik b\u00fcroo v\u00f5rk<\/i><br \/>\n#<br \/>\naaa<br \/>\nteenuse-skeem IPSEC<br \/>\nmarsruut seadista acl 3999<br \/>\n#<br \/>\nipsec ettepanek ipsec<br \/>\nesp autentimise-algoritm sha2-256<br \/>\nesp kr\u00fcpteerimise-algoritm aes-256<br \/>\n#<br \/>\nike ettepanek vaikimisi<br \/>\nkr\u00fcpteerimise-algoritm aes-256<br \/>\ndh grupp2<br \/>\nautentimise-algoritm sha2-256<br \/>\nautentimise-viis eelhulga<br \/>\npuhtuse-algoritm hmac-sha2-256<br \/>\nprf hmac-sha2-256<br \/>\n#<br \/>\nike partner ipsec<br \/>\neelhulga v\u00f5ti lihtne<br \/>\nkohalik-id-tyyp fqdn<br \/>\nkaug-id-tyyp ip<br \/>\nkaug-aadress 62.141.99.183 <i> \u2013 Beeline VPN-keskus<\/i><br \/>\nteenuse-skeem IPSEC<br \/>\nconfig-vahetus p\u00e4ring<br \/>\nconfig-vahetus seadista aktsepteeri<br \/>\nconfig-vahetus seadista saada<br \/>\n#<br \/>\nipsec profiil ipsecprof<br \/>\nike-partner ipsec<br \/>\nettepanek ipsec<br \/>\n#<br \/>\nliides Tunnel0\/0\/0<br \/>\nip address 10.20.1.2 255.255.255.252 <i> \u2013 Tunneliaadress<\/i><br \/>\ntunnel-protokoll ipsec<br \/>\nallikas GigabitEthernet0\/0\/1 <i> \u2013 Interneti-\u00fchenduse liides<\/i><br \/>\nipsec profiil ipsecprof<br \/>\n#<br \/>\n<i>Klientide privaatsete v\u00f5rkude marsruudid, mis on kergesti ligip\u00e4\u00e4setavad Beeline'i VPN keskuse kaudu, saab m\u00e4\u00e4rata staatiliselt<\/i><\/p>\n<p>ip marsruut-statiline 192.168.0.0 255.255.255.0 Tunnel0\/0\/0<br \/>\nip marsruut-statiline 172.16.0.0 255.255.0.0 Tunnel0\/0\/0<\/li>\n<\/ol>\n<p>Saadud side skeem n\u00e4eb v\u00e4lja umbes j\u00e4rgmiselt:<\/p>\n<p><img decoding=\"async\" style=\"display: block; margin: 0 auto;\" src=\"\/wp-content\/uploads\/2020\/07\/8083e9190bdcdd816ac3014d7b7f5de4.jpg\" alt=\"Kuidas p\u00e4\u00e4seda Beline IPVPN-i l\u00e4bi IPSec. Osa 1\" \/><\/p>\n<p>Kui klientidel puuduvad m\u00f5ned p\u00f5hikonfiguratsiooni n\u00e4ited - siis aitame tavaliselt nende v\u00e4ljat\u00f6\u00f6tamisel ja teeme need kergesti kergesti ligip\u00e4\u00e4setavaks teistele.<\/p>\n<p>J\u00e4\u00e4nud on \u00fchendada CPE internetti, teha ping vastava VPN tunneli ja mingisuguse hosti sisse VPN-i ning k\u00f5ik, saab juba \u00f6elda, et \u00fchendus on loodud.<\/p>\n<p>J\u00e4rgmises artiklis r\u00e4\u00e4gime, kuidas me kombineerisime selle skeemi IPSec ja MultiSIM varundamisega CPE Huawei abil: seame klientidele meie CPE Huawei, milles saab kasutada mitte ainult juhtme interneti kanalit, vaid ka 2 erinevat SIM-kaarti, ning CPE kohandab automaatselt IPSec-tunneli kas juhtme WAN kaudu v\u00f5i raadio (LTE#1\/LTE#2) kaudu, saavutades l\u00f5ppteenuse k\u00f5rge usaldusv\u00e4\u00e4rsuse.<\/p>\n<p>Eriline t\u00e4nu selle artikli koostamise eest (ja tegelikult nende tehniliste lahenduste autoritele) meie RnD kolleegidele!<\/p>\n<p>Allikas: <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.1.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\/et\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\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\/et\/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\udd47Kuidas p\u00e4\u00e4seda Beeline'i IPVPN-i l\u00e4bi IPSec. Osa 1 | ProHoster","description":"Tere!","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/kak-popast-v-ipvpn-bilajn-cherez-ipsec-chast-1","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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\/et\/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\/et\/wp-json\/wp\/v2\/posts\/89276","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=89276"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/89276\/revisions"}],"predecessor-version":[{"id":182465,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/89276\/revisions\/182465"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/89277"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=89276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=89276"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=89276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}