{"id":91210,"date":"2020-08-10T01:42:13","date_gmt":"2020-08-09T23:42:13","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii"},"modified":"2020-08-10T01:42:13","modified_gmt":"2020-08-09T23:42:13","slug":"1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii","title":{"rendered":"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/34026e07ff4a1fd64227224ca4c96f0d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Situa\u021bia<\/h3>\n<p>\nAm primit versiunea de prob\u0103 a produselor S-Terra VPN 4.3 pe o perioad\u0103 de trei luni. Vreau s\u0103 \u00een\u021beleg dac\u0103 via\u021ba mea profesional\u0103 va fi mai u\u0219oar\u0103 dup\u0103 trecerea la noua versiune.<\/p>\n<p>Ast\u0103zi nu este greu, un plic de cafea solubil 3 \u00een 1 ar trebui s\u0103 fie suficient. Voi explica cum s\u0103 ob\u021bin versiunile demo. Voi \u00eencerca s\u0103 adun schemele GRE-over-IPsec \u0219i IPsec-over-GRE.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Cum s\u0103 ob\u021bii versiunea de prob\u0103<\/h3>\n<p>\n<img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/0c5482e01684b8c7b3e35fb9c473b475.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDin desen reiese c\u0103 pentru a ob\u021bine versiunea de prob\u0103, trebuie:<\/p>\n<ul>\n<li>S\u0103 scrii un e-mail la presale@s-terra.ru de pe adresa de e-mail a companiei;<\/li>\n<li>\u00cen e-mail, s\u0103 specifici codul de identificare fiscal\u0103 al organiza\u021biei tale;<\/li>\n<li>S\u0103 enumeri produsele \u0219i cantitatea acestora.<\/li>\n<\/ul>\n<p>\nVersiunile de prob\u0103 sunt valabile timp de trei luni. Furnizorul nu limiteaz\u0103 func\u021bionalitatea acestora. <\/p>\n<h3>Desfac imaginea<\/h3>\n<p>\nVersiunea de prob\u0103 a gateway-ului de securitate este o imagine a unei ma\u0219ini virtuale. Folosesc VMWare Workstation. Lista complet\u0103 a hipervizorilor \u0219i mediilor de virtualizare suportate este disponibil\u0103 pe site-ul furnizorului. <\/p>\n<p>\u00cenainte de a \u00eencepe ac\u021biunile active, re\u021bine\u021bi c\u0103 \u00een imaginea ma\u0219inii virtuale, \u00een mod implicit, nu exist\u0103 interfe\u021be de re\u021bea: <\/p>\n<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/b1ffa5f27aae9744fc24a91b709794d6.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nLogica este clar\u0103, utilizatorul trebuie s\u0103 adauge at\u00e2tea interfe\u021be c\u00e2te are nevoie. Voi ad\u0103uga imediat patru:<\/p>\n<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/626f2e1ba04babd37373298d650b210d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAcum pornesc ma\u0219ina virtual\u0103. Imediat dup\u0103 pornire, gateway-ul cere un nume de utilizator \u0219i o parol\u0103. <\/p>\n<blockquote><p>\u00cen S-Terra Gateway exist\u0103 mai multe console cu diferite conturi. Voi num\u0103ra num\u0103rul acestora \u00eentr-un articol separat. \u00centre timp:<br \/>\n<code>Conectare ca: administrator<br \/>\nParol\u0103: s-terra<\/code><\/p><\/blockquote>\n<p>\nIni\u021bializez gateway-ul. Ini\u021bializarea este o succesiune de ac\u021biuni: introducerea licen\u021bei, configurarea generatorului biologic de numere aleatorii (antrenor de tastatur\u0103 - recordul meu este de 27 de secunde) \u0219i crearea h\u0103r\u021bii interfe\u021belor de re\u021bea.<\/p>\n<h3>Harta interfe\u021belor de re\u021bea. A devenit mai u\u0219or<\/h3>\n<p>\nVersiunea 4.2 saluta utilizatorul activ cu mesaje:<\/p>\n<p><code>Pornind daemonul IPsec\u2026.. e\u0219uat<br \/>\nEROARE: Nu s-a putut stabili conexiunea cu daemonul<\/code><\/p>\n<p><i>Utilizator activ (conform unui inginer anonim) \u2013 utilizator capabil s\u0103 configureze orice rapid \u0219i f\u0103r\u0103 documenta\u021bie.<\/i><\/p>\n<p>Ceva nu mergea bine, \u00eenc\u0103 \u00eenainte de a \u00eencerca s\u0103 configurez IP-ul pe interfa\u021b\u0103. Totul \u021bine de harta interfe\u021belor de re\u021bea. Era necesar s\u0103 se execute:<\/p>\n<p><code>\/bin\/netifcfg enum &gt; \/home\/map<br \/>\n\/bin\/netifcfg map \/home\/map<br \/>\nserviciul re\u021belei repornire<\/code><\/p>\n<p>\u00cen rezultat, se creeaz\u0103 o hart\u0103 a interfe\u021belor de re\u021bea, care con\u021bine mapparea numelui interfe\u021belor fizice (0000:02:03.0) \u0219i denumirile lor logice \u00een sistemul de operare (eth0) \u0219i consola Cisco-like (FastEthernet0\/0):<\/p>\n<p><code>#Unique ID iface type OS name Cisco-like name<\/p>\n<p>0000:02:03.0 phye eth0 FastEthernet0\/0<\/code><\/p>\n<p>Denumirile logice ale interfe\u021belor se numesc aliasuri. Aliasurile sunt stocate \u00een fi\u0219ierul \/etc\/ifaliases.cf. <br \/>\n\u00cen versiunea 4.3, la prima pornire a ma\u0219inii virtuale, harta interfe\u021belor este creat\u0103 automat. Dac\u0103 schimba\u021bi num\u0103rul de interfe\u021be de re\u021bea \u00een ma\u0219ina virtual\u0103, v\u0103 rug\u0103m s\u0103 crea\u021bi din nou harta interfe\u021belor:<\/p>\n<p><code>\/bin\/netifcfg enum &gt; \/home\/map<br \/>\n\/bin\/netifcfg map \/home\/map<br \/>\nsystemctl restart networking<\/code><\/p>\n<h3>Schema 1: GRE peste IPsec<\/h3>\n<p>\nDesf\u0103\u0219or dou\u0103 gateway-uri virtuale, le conectez a\u0219a cum este ilustrat \u00een imagine:<\/p>\n<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/bf3b085f6874d04043511ef262979a39.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Pasul 1. Configurez adresele IP \u0219i rutele<\/b><\/p>\n<pre><code class=\"plaintext\">VG1(config) #\ninterface fa0\/0\nip address 172.16.1.253 255.255.255.0\nno shutdown\ninterface fa0\/1\nip address 192.168.1.253 255.255.255.0\nno shutdown\nip route 0.0.0.0 0.0.0.0 172.16.1.254<\/code><\/pre>\n<p><\/p>\n<pre><code class=\"plaintext\">VG2(config) #\ninterface fa0\/0\nip address 172.16.1.254 255.255.255.0\nno shutdown\ninterface fa0\/1\nip address 192.168.2.254 255.255.255.0\nno shutdown\nip route 0.0.0.0 0.0.0.0 172.16.1.253<\/code><\/pre>\n<p>\nVerific conectivitatea IP:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# ping 172.16.1.254 -c 4\nPING 172.16.1.254 (172.16.1.254) 56(84) bytes of data.\n64 bytes from 172.16.1.254: icmp_seq=1 ttl=64 time=0.545 ms\n64 bytes from 172.16.1.254: icmp_seq=2 ttl=64 time=0.657 ms\n64 bytes from 172.16.1.254: icmp_seq=3 ttl=64 time=0.687 ms\n64 bytes from 172.16.1.254: icmp_seq=4 ttl=64 time=0.273 ms\n\n--- statistici ping 172.16.1.254 ---\n4 pachete transmise, 4 primite, 0% pierdere de pachete, timp 3005ms\nrtt min\/med\/max\/mdev = 0.273\/0.540\/0.687\/0.164 ms<\/code><\/pre>\n<p><b>Pasul 2. Configurez GRE<\/b><\/p>\n<p>Exemplul de configurare GRE este preluat din scenariile oficiale. Creez fi\u0219ierul gre1 \u00een directorul \/etc\/network\/interfaces.d cu con\u021binutul.<\/p>\n<p>Pentru VG1:<\/p>\n<pre><code class=\"plaintext\">auto gre1\niface gre1 inet static\naddress 1.1.1.1\nnetmask 255.255.255.252\npre-up ip tunnel add gre1 mode gre remote 172.16.1.254 local 172.16.1.253 key 1 ttl 64 tos inherit\npre-up ethtool -K gre1 tx off &gt; \/dev\/null\npre-up ip link set gre1 mtu 1400\npost-down ip link del gre1<\/code><\/pre>\n<p>\nPentru VG2:<\/p>\n<pre><code class=\"plaintext\">auto gre1\niface gre1 inet static\naddress 1.1.1.2\nnetmask 255.255.255.252\npre-up ip tunnel add gre1 mode gre remote 172.16.1.253 local 172.16.1.254 key 1 ttl 64 tos inherit\npre-up ethtool -K gre1 tx off &gt; \/dev\/null\npre-up ip link set gre1 mtu 1400\npost-down ip link del gre1<\/code><\/pre>\n<p>\nActivez interfa\u021ba \u00een sistem:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# ifup gre1\nroot@VG2:~# ifup gre1<\/code><\/pre>\n<p>\nVerific:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# ip address show\n8: gre1@NONE:  mtu 1400 qdisc noqueue state UNKNOWN group default qlen 1\n    link\/gre 172.16.1.253 peer 172.16.1.254\n    inet 1.1.1.1\/30 brd 1.1.1.3 scope global gre1\n       valid_lft forever preferred_lft forever\n\nroot@VG1:~# ip tunnel show\ngre0: gre\/ip remote any local any ttl inherit nopmtudisc\ngre1: gre\/ip remote 172.16.1.254 local 172.16.1.253 ttl 64 tos inherit key 1<\/code><\/pre>\n<p>\n\u00cen S-Terra Gateway exist\u0103 un sniffer de trafic integrat \u2014 tcpdump. Voi salva dump-ul de trafic \u00eentr-un fi\u0219ier pcap:<\/p>\n<pre><code class=\"plaintext\">root@VG2:~# tcpdump -i eth0 -w \/home\/dump.pcap<\/code><\/pre>\n<p>\nExecut ping \u00eentre interfe\u021bele GRE:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# ping 1.1.1.2 -c 4\nPING 1.1.1.2 (1.1.1.2) 56(84) bytes of data.\n64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.918 ms\n64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=0.850 ms\n64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=0.918 ms\n64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=0.974 ms\n\n--- statistici ping 1.1.1.2 ---\n4 pachete transmise, 4 primite, 0% pierdere de pachete, timp 3006ms\nrtt min\/med\/max\/mdev = 0.850\/0.915\/0.974\/0.043 ms<\/code><\/pre>\n<p>\nTunelul GRE este activ \u0219i func\u021bioneaz\u0103:<\/p>\n<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/0b56c02e36d1dd17b42e3fadcffb6193.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Pasul 3. Cript\u0103m GRE cu GOST<\/b><\/p>\n<p>Setez tipul de identificare \u2013 pe adres\u0103. Autentificarea se face printr-o cheie prestabilit\u0103 (conform Regulilor de Utilizare, trebuie folosite certificate digitale):<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\ncrypto isakmp identity address\ncrypto isakmp key KEY address 172.16.1.254<\/code><\/pre>\n<p>\nSet parameters for IPsec Phase I:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\ncrypto isakmp policy 1\nencr gost\nhash gost3411-256-tc26\nauth pre-share\ngroup vko2<\/code><\/pre>\n<p>\nSet parameters for IPsec Phase II:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\ncrypto ipsec transform-set TSET esp-gost28147-4m-imit\nmode tunnel<\/code><\/pre>\n<p>\nCreating an access list for encryption. Target traffic \u2014 GRE:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\nip access-list extended LIST\npermit gre host 172.16.1.253 host 172.16.1.254<\/code><\/pre>\n<p>\nCreating a crypto map and binding it to the WAN interface:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\ncrypto map CMAP 1 ipsec-isakmp\nmatch address LIST\nset transform-set TSET\nset peer 172.16.1.253\ninterface fa0\/0\n  crypto map CMAP<\/code><\/pre>\n<p>\nFor VG2, the configuration is mirrored, with differences:<\/p>\n<pre><code class=\"plaintext\">VG2(config)#\ncrypto isakmp key KEY address 172.16.1.253\nip access-list extended LIST\npermit gre host 172.16.1.254 host 172.16.1.253\ncrypto map CMAP 1 ipsec-isakmp\nset peer 172.16.1.254<\/code><\/pre>\n<p>\nVerific:<\/p>\n<pre><code class=\"plaintext\">root@VG2:~# tcpdump -i eth0 -w \/home\/dump2.pcap<\/code><\/pre>\n<pre><code class=\"plaintext\">root@VG1:~# ping 1.1.1.2 -c 4\nPING 1.1.1.2 (1.1.1.2) 56(84) bytes of data.\n64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=1128 ms\n64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=126 ms\n64 bytes from 1.1.1.2: icmp_seq=3 ttl=64 time=1.07 ms\n64 bytes from 1.1.1.2: icmp_seq=4 ttl=64 time=1.12 ms\n\n--- 1.1.1.2 ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 3006ms\nrtt min\/avg\/max\/mdev = 1.077\/314.271\/1128.419\/472.826 ms, pipe 2\n<\/code><\/pre>\n<p>\nStatistics ISAKMP\/IPsec:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# sa_mgr show\nISAKMP sessions: 0 initiated, 0 responded\n\nISAKMP connections:\nNum Conn-id (Local Addr,Port)-(Remote Addr,Port) State Sent Rcvd\n1 1 (172.16.1.253,500)-(172.16.1.254,500) active 1086 1014\n\nIPsec connections:\nNum Conn-id (Local Addr,Port)-(Remote Addr,Port) Protocol Action Type Sent Rcvd\n1 1 (172.16.1.253,*)-(172.16.1.254,*) 47 ESP tunn 480 480<\/code><\/pre>\n<p>\nNo GRE packet found in the traffic dump:<\/p>\n<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/cf96619cb4224cbf4da7c15db73587c7.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nConclusion: the GRE-over-IPsec scheme works correctly.<\/p>\n<h3>Diagram 1.5: IPsec-over-GRE<\/h3>\n<p>\nI do not plan to use IPsec-over-GRE in the network. I'm assembling it just because I want to. <\/p>\n<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/98909280d82184278e23f2c38b90947d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTo deploy the GRE-over-IPsec scheme in reverse, you need to:<\/p>\n<ul>\n<li>Correct the access list for encryption \u2013 target traffic from LAN1 to LAN2 and vice versa;<\/li>\n<li>Configure routing through GRE;<\/li>\n<li>Attach the crypto map to the GRE interface.<\/li>\n<\/ul>\n<p>\nBy default, in the Cisco-like gateway console, there is no GRE interface. It exists only in the operating system. <\/p>\n<p>I add the GRE interface to the Cisco-like console. For this, I edit the file \/etc\/ifaliases.cf:<\/p>\n<pre><code class=\"plaintext\">interfa\u021b\u0103 (name=\"FastEthernet0\/0\" pattern=\"eth0\")\ninterfa\u021b\u0103 (name=\"FastEthernet0\/1\" pattern=\"eth1\")\ninterfa\u021b\u0103 (name=\"FastEthernet0\/2\" pattern=\"eth2\")\ninterfa\u021b\u0103 (name=\"FastEthernet0\/3\" pattern=\"eth3\")\ninterfa\u021b\u0103 (name=\"Tunnel0\" pattern=\"gre1\")\ninterfa\u021b\u0103 (name=\"default\" pattern=\"*\")<\/code><\/pre>\n<p>\nwhere gre1 is the designation of the interface in the operating system, Tunnel0 is the designation of the interface in the Cisco-like console.<\/p>\n<p>Recalculating the hash of the file:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# integr_mgr calc -f \/etc\/ifaliases.cf\n\nSUCCESS:  Operation was successful.<\/code><\/pre>\n<p>\nNow the Tunnel0 interface has appeared in the Cisco-like console:<\/p>\n<pre><code class=\"plaintext\">VG1# show run\ninterface Tunnel0\nip address 1.1.1.1 255.255.255.252\nmtu 1400<\/code><\/pre>\n<p>\nAdjusting the access list for encryption:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\nip access-list extended LIST\npermit ip 192.168.1.0 0.0.0.255 192.168.3.0 0.0.0.255<\/code><\/pre>\n<p>\nConfiguring routing through GRE:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\nnu ip route 0.0.0.0 0.0.0.0 172.16.1.254\nip route 192.168.3.0 255.255.255.0 1.1.1.2<\/code><\/pre>\n<p>\n\u00cendep\u0103rtez criptocarta de la Fa0\/0 \u0219i o ata\u0219ez la interfa\u021ba GRE:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\ninterfa\u021ba Tunnel0\ncrypto map CMAP<\/code><\/pre>\n<p>\nPentru VG2 similar.<\/p>\n<p>Verific:<\/p>\n<pre><code class=\"plaintext\">root@VG2:~# tcpdump -i eth0 -w \/home\/dump3.pcap<\/code><\/pre>\n<p><\/p>\n<pre><code class=\"plaintext\">root@VG1:~# ping 192.168.2.254 -I 192.168.1.253 -c 4\nPING 192.168.2.254 (192.168.2.254) de la 192.168.1.253 : 56(84) bytes de date.\n64 bytes de la 192.168.2.254: icmp_seq=1 ttl=64 timp=492 ms\n64 bytes de la 192.168.2.254: icmp_seq=2 ttl=64 timp=1.08 ms\n64 bytes de la 192.168.2.254: icmp_seq=3 ttl=64 timp=1.06 ms\n64 bytes de la 192.168.2.254: icmp_seq=4 ttl=64 timp=1.07 ms\n\n--- statistici ping 192.168.2.254 ---\n4 pachete transmise, 4 primite, 0% pierdere de pachete, timp 3006ms\nrtt min\/med\/max\/mdev = 1.064\/124.048\/492.972\/212.998 ms<\/code><\/pre>\n<p>Statistics ISAKMP\/IPsec:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# sa_mgr show\nSesiuni ISAKMP: 0 ini\u021biate, 0 r\u0103spunse\n\nConexiuni ISAKMP:\nNum Conn-id (Adres\u0103 Local\u0103,Port)-(Adres\u0103 Remote,Port) Stare Trimise Primite\n1 2 (172.16.1.253,500)-(172.16.1.254,500) activ 1094 1022\n\nConexiuni IPsec:\nNum Conn-id (Adres\u0103 Local\u0103,Port)-(Adres\u0103 Remote,Port) Protocol Tip Ac\u021biune Trimise Primite\n1 2 (192.168.1.0-192.168.1.255,*)-(192.168.2.0-192.168.2.255,*) * ESP tunn 352 352<\/code><\/pre>\n<p>\n\u00cen dump-ul de trafic, pachetele ESP sunt \u00eencapsulate \u00een GRE:<\/p>\n<p><img decoding=\"async\" alt=\"Schituri 1.5 pe VPN IPsec autohton. Testez versiunile demo\" src=\"\/wp-content\/uploads\/2020\/08\/068865544de126a1673c6fb7b6367ffd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nRezultatul: IPsec-over-GRE func\u021bioneaz\u0103 corect.<\/p>\n<h3>Concluzii<\/h3>\n<p>\nO can\u0103 de cafea a fost suficient\u0103. Am schi\u021bat o instruc\u021biune pentru ob\u021binerea unei versiuni demo. Am configurat GRE-over-IPsec \u0219i am desf\u0103\u0219urat invers.<\/p>\n<p>Harta interfe\u021belor de re\u021bea \u00een versiunea 4.3 este automat\u0103! Testez mai departe.<\/p>\n<p><i>Inginer anonim<br \/>\nt.me\/anonimous_engineer<\/i><br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/514190\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0421\u0438\u0442\u0443\u0430\u0446\u0438\u044f \u042f \u043f\u043e\u043b\u0443\u0447\u0438\u043b \u0434\u0435\u043c\u043e\u0432\u0435\u0440\u0441\u0438\u044e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u043e\u0432 \u0421-\u0422\u0435\u0440\u0440\u0430 VPN \u0432\u0435\u0440\u0441\u0438\u0438 4.3 \u043d\u0430 \u0442\u0440\u0438 \u043c\u0435\u0441\u044f\u0446\u0430. \u0425\u043e\u0447\u0443 \u0440\u0430\u0437\u043e\u0431\u0440\u0430\u0442\u044c\u0441\u044f, \u0441\u0442\u0430\u043d\u0435\u0442 \u043b\u0438 \u043c\u043e\u044f \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u043d\u0430\u044f \u0436\u0438\u0437\u043d\u044c \u043b\u0435\u0433\u0447\u0435 \u043f\u043e\u0441\u043b\u0435 \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0430 \u043d\u0430 \u043d\u043e\u0432\u0443\u044e \u0432\u0435\u0440\u0441\u0438\u044e. \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043d\u0435 \u0441\u043b\u043e\u0436\u043d\u043e, \u043e\u0434\u043d\u043e\u0433\u043e \u043f\u0430\u043a\u0435\u0442\u0438\u043a\u0430 \u0440\u0430\u0441\u0442\u0432\u043e\u0440\u0438\u043c\u043e\u0433\u043e \u043a\u043e\u0444\u0435 3 \u0432 1 \u0434\u043e\u043b\u0436\u043d\u043e \u0445\u0432\u0430\u0442\u0438\u0442\u044c. \u0420\u0430\u0441\u0441\u043a\u0430\u0436\u0443, \u043a\u0430\u043a \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u0434\u0435\u043c\u043e\u0432\u0435\u0440\u0441\u0438\u0438. \u041f\u043e\u043f\u0440\u043e\u0431\u0443\u044e \u0441\u043e\u0431\u0440\u0430\u0442\u044c \u0441\u0445\u0435\u043c\u044b GRE-over-IPsec \u0438 IPsec-over-GRE. \u041a\u0430\u043a \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u0434\u0435\u043c\u043e\u0432\u0435\u0440\u0441\u0438\u044e \u0418\u0437 \u0440\u0438\u0441\u0443\u043d\u043a\u0430 \u0441\u043b\u0435\u0434\u0443\u0435\u0442, \u0447\u0442\u043e\u0431\u044b \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":91211,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-91210","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=\"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\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii\" \/>\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\udd471.5 \u0441\u0445\u0435\u043c\u044b \u043d\u0430 \u043e\u0442\u0435\u0447\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u043c IPsec VPN. \u0422\u0435\u0441\u0442\u0438\u0440\u0443\u044e \u0434\u0435\u043c\u043e\u0432\u0435\u0440\u0441\u0438\u0438 | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii\" \/>\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-08-09T23:42:13+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-08-09T23:42:13+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\udd471.5 scheme pe VPN IPsec autohton. Testez versiunile demo | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii","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\udd471.5 \u0441\u0445\u0435\u043c\u044b \u043d\u0430 \u043e\u0442\u0435\u0447\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u043c IPsec VPN. \u0422\u0435\u0441\u0442\u0438\u0440\u0443\u044e \u0434\u0435\u043c\u043e\u0432\u0435\u0440\u0441\u0438\u0438 | ProHoster","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii","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-08-09T23:42:13+00:00","article:modified_time":"2020-08-09T23:42:13+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"91210","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 12:32:22","updated":"2022-09-28 01:47:27","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\/91210","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=91210"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/91210\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/91211"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=91210"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=91210"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=91210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}