{"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\/pt\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii","title":{"rendered":"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/34026e07ff4a1fd64227224ca4c96f0d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Situa\u00e7\u00e3o<\/h3>\n<p>\nRecebi a vers\u00e3o demo dos produtos S-Terra VPN vers\u00e3o 4.3 por tr\u00eas meses. Quero entender se minha vida como engenheiro ficar\u00e1 mais f\u00e1cil ap\u00f3s a migra\u00e7\u00e3o para a nova vers\u00e3o.<\/p>\n<p>Hoje, n\u00e3o \u00e9 dif\u00edcil; um sach\u00ea de caf\u00e9 sol\u00favel 3 em 1 deve ser suficiente. Vou explicar como obter as vers\u00f5es demo. Tentarei montar esquemas GRE-over-IPsec e IPsec-over-GRE.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Como obter a vers\u00e3o demo<\/h3>\n<p>\n<img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/0c5482e01684b8c7b3e35fb9c473b475.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA partir do desenho, fica claro que para obter a vers\u00e3o demo, \u00e9 necess\u00e1rio:<\/p>\n<ul>\n<li>Escrever um e-mail para presale@s-terra.ru a partir do endere\u00e7o corporativo;<\/li>\n<li>No e-mail, indicar o CNPJ da sua organiza\u00e7\u00e3o;<\/li>\n<li>Listar os produtos e suas quantidades.<\/li>\n<\/ul>\n<p>\nAs vers\u00f5es demo s\u00e3o v\u00e1lidas por tr\u00eas meses. O fornecedor n\u00e3o limita sua funcionalidade. <\/p>\n<h3>Estou implantando a imagem<\/h3>\n<p>\nA vers\u00e3o demo do gateway de seguran\u00e7a \u00e9 uma imagem de m\u00e1quina virtual. Estou usando o VMWare Workstation. A lista completa de hipervisores suportados e ambientes de virtualiza\u00e7\u00e3o est\u00e1 dispon\u00edvel no site do fornecedor. <\/p>\n<p>Antes de iniciar as a\u00e7\u00f5es ativas, observe que a imagem da m\u00e1quina virtual n\u00e3o possui interfaces de rede por padr\u00e3o: <\/p>\n<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/b1ffa5f27aae9744fc24a91b709794d6.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nA l\u00f3gica \u00e9 clara; o usu\u00e1rio deve adicionar tantas interfaces quantas forem necess\u00e1rias. Vou adicionar quatro de uma vez:<\/p>\n<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/626f2e1ba04babd37373298d650b210d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAgora estou iniciando a m\u00e1quina virtual. Logo ap\u00f3s a inicializa\u00e7\u00e3o, o gateway solicita login e senha. <\/p>\n<blockquote><p>No S-Terra Gateway, existem v\u00e1rias consoles com diferentes contas. Contarei o n\u00famero delas em um artigo separado. Por ora:<br \/>\n<code>Entrar como: administrador<br \/>\nSenha: s-terra<\/code><\/p><\/blockquote>\n<p>\nEstou inicializando o gateway. A inicializa\u00e7\u00e3o \u00e9 uma sequ\u00eancia de a\u00e7\u00f5es: inser\u00e7\u00e3o da licen\u00e7a, configura\u00e7\u00e3o do gerador biol\u00f3gico de n\u00fameros aleat\u00f3rios (o simulador de teclado \u2013 meu recorde \u00e9 de 27 segundos) e cria\u00e7\u00e3o do mapa de interfaces de rede.<\/p>\n<h3>Mapa de interfaces de rede. Fica mais f\u00e1cil<\/h3>\n<p>\nA vers\u00e3o 4.2 acolhia o usu\u00e1rio ativo com mensagens:<\/p>\n<p><code>Iniciando o daemon IPsec..... falhou<br \/>\nERRO: N\u00e3o foi poss\u00edvel estabelecer conex\u00e3o com o daemon<\/code><\/p>\n<p><i>Um usu\u00e1rio ativo (segundo um engenheiro an\u00f4nimo) \u00e9 aquele capaz de configurar qualquer coisa rapidamente e sem documenta\u00e7\u00e3o.<\/i><\/p>\n<p>Algo estava errado, mesmo antes de tentar configurar o endere\u00e7o IP na interface. Tudo se deve ao mapa de interfaces de rede. Foi necess\u00e1rio realizar:<\/p>\n<p><code>\/bin\/netifcfg enum &gt; \/home\/map<br \/>\n\/bin\/netifcfg map \/home\/map<br \/>\nreiniciar o servi\u00e7o de rede<\/code><\/p>\n<p>Como resultado, \u00e9 criado um mapa de interfaces de rede que cont\u00e9m a correspond\u00eancia dos nomes das interfaces f\u00edsicas (0000:02:03.0) e suas designa\u00e7\u00f5es l\u00f3gicas no sistema operacional (eth0) e no console semelhante ao Cisco (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>As designa\u00e7\u00f5es l\u00f3gicas das interfaces s\u00e3o chamadas de aliases. Os aliases s\u00e3o armazenados no arquivo \/etc\/ifaliases.cf. <br \/>\nNa vers\u00e3o 4.3, ao iniciar a m\u00e1quina virtual pela primeira vez, o mapa de interfaces \u00e9 criado automaticamente. Se voc\u00ea alterar o n\u00famero de interfaces de rede na virtualiza\u00e7\u00e3o, ser\u00e1 necess\u00e1rio criar o mapa de interfaces novamente:<\/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>Diagrama 1: GRE sobre IPsec<\/h3>\n<p>\nEstou implementando dois gateways virtuais, conectando-os conforme mostrado na figura:<\/p>\n<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/bf3b085f6874d04043511ef262979a39.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Passo 1. Configurando endere\u00e7os IP e rotas<\/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>\nVerifico a conectividade 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--- 172.16.1.254 Ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 3005ms\nrtt min\/avg\/max\/mdev = 0.273\/0.540\/0.687\/0.164 ms<\/code><\/pre>\n<p><b>Passo 2. Configurando GRE<\/b><\/p>\n<p>O exemplo de configura\u00e7\u00e3o do GRE \u00e9 retirado dos cen\u00e1rios oficiais. Crio o arquivo gre1 no diret\u00f3rio \/etc\/network\/interfaces.d com o seguinte conte\u00fado.<\/p>\n<p>Para 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>\nPara 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>\nAtivo a interface no sistema:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# ifup gre1\nroot@VG2:~# ifup gre1<\/code><\/pre>\n<p>\nVerifico:<\/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>\nNo S-Terra Gateway, h\u00e1 um sniffer de pacotes embutido \u2014 tcpdump. Vou gravar um dump de tr\u00e1fego em um arquivo pcap:<\/p>\n<pre><code class=\"plaintext\">root@VG2:~# tcpdump -i eth0 -w \/home\/dump.pcap<\/code><\/pre>\n<p>\nIn\u00edcio o ping entre as interfaces 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--- 1.1.1.2 estat\u00edsticas do ping ---\n4 pacotes transmitidos, 4 recebidos, 0% de perda de pacotes, tempo 3006ms\nrtt min\/avg\/max\/mdev = 0.850\/0.915\/0.974\/0.043 ms<\/code><\/pre>\n<p>\nO t\u00fanel GRE est\u00e1 ativo e funcionando:<\/p>\n<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/0b56c02e36d1dd17b42e3fadcffb6193.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<b>Passo 3. Criptografando GRE com GOST<\/b><\/p>\n<p>Defino o tipo de identifica\u00e7\u00e3o \u2013 por endere\u00e7o. A autentica\u00e7\u00e3o \u00e9 feita por chave pr\u00e9-definida (de acordo com as Regras de Uso, \u00e9 necess\u00e1rio usar certificados digitais):<\/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>\nDefinindo os par\u00e2metros da Fase I do IPsec:<\/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>\nDefinindo os par\u00e2metros da Fase II do IPsec:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\ncrypto ipsec transform-set TSET esp-gost28147-4m-imit\nmode tunnel<\/code><\/pre>\n<p>\nCriando a lista de acesso para criptografia. Tr\u00e1fego de destino \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>\nCriando o mapa criptogr\u00e1fico e vinculando-o \u00e0 interface WAN:<\/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>\nPara a VG2, a configura\u00e7\u00e3o \u00e9 espelho, com diferen\u00e7as:<\/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>\nVerifico:<\/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--- Estat\u00edsticas do ping de 1.1.1.2 ---\n4 pacotes transmitidos, 4 recebidos, 0% de perda de pacotes, tempo 3006ms\nrtt min\/avg\/max\/mdev = 1.077\/314.271\/1128.419\/472.826 ms, pipe 2\n<\/code><\/pre>\n<p>\nEstat\u00edsticas ISAKMP\/IPsec:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# sa_mgr show\nSess\u00f5es ISAKMP: 0 iniciadas, 0 respondidas\n\nConex\u00f5es ISAKMP:\nNum Conn-id (Endere\u00e7o Local, Porta)-(Endere\u00e7o Remoto, Porta) Estado Enviado Recebido\n1 1 (172.16.1.253,500)-(172.16.1.254,500) ativo 1086 1014\n\nConex\u00f5es IPsec:\nNum Conn-id (Endere\u00e7o Local, Porta)-(Endere\u00e7o Remoto, Porta) Protocolo A\u00e7\u00e3o Tipo Enviado Recebido\n1 1 (172.16.1.253,*)-(172.16.1.254,*) 47 ESP tunn 480 480<\/code><\/pre>\n<p>\nN\u00e3o h\u00e1 pacotes GRE no dump de tr\u00e1fego:<\/p>\n<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/cf96619cb4224cbf4da7c15db73587c7.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nResultado: o esquema GRE-over-IPsec est\u00e1 funcionando corretamente.<\/p>\n<h3>Esquema 1.5: IPsec-over-GRE<\/h3>\n<p>\nN\u00e3o pretendo usar IPsec-over-GRE na rede. Estou coletando apenas por vontade. <\/p>\n<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/98909280d82184278e23f2c38b90947d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPara inverter o esquema GRE-over-IPsec, \u00e9 necess\u00e1rio:<\/p>\n<ul>\n<li>Corrigir a lista de acesso para criptografia \u2014 tr\u00e1fego de destino do LAN1 para o LAN2 e vice-versa;<\/li>\n<li>Configurar o roteamento atrav\u00e9s do GRE;<\/li>\n<li>Vincular o mapa criptogr\u00e1fico \u00e0 interface GRE.<\/li>\n<\/ul>\n<p>\nPor padr\u00e3o, n\u00e3o h\u00e1 interface GRE no console semelhante ao Cisco. Ela existe apenas no sistema operacional. <\/p>\n<p>Adicionando a interface GRE ao console semelhante ao Cisco. Para isso, edito o arquivo \/etc\/ifaliases.cf:<\/p>\n<pre><code class=\"plaintext\">interface (name=\"FastEthernet0\/0\" pattern=\"eth0\")\ninterface (name=\"FastEthernet0\/1\" pattern=\"eth1\")\ninterface (name=\"FastEthernet0\/2\" pattern=\"eth2\")\ninterface (name=\"FastEthernet0\/3\" pattern=\"eth3\")\ninterface (name=\"Tunnel0\" pattern=\"gre1\")\ninterface (name=\"default\" pattern=\"*\")<\/code><\/pre>\n<p>\nonde gre1 \u00e9 a designa\u00e7\u00e3o da interface no sistema operacional, Tunnel0 \u00e9 a designa\u00e7\u00e3o da interface no console semelhante ao Cisco.<\/p>\n<p>Recalculando o hash do arquivo:<\/p>\n<pre><code class=\"plaintext\">root@VG1:~# integr_mgr calc -f \/etc\/ifaliases.cf\n\nSUCESSO: A opera\u00e7\u00e3o foi bem-sucedida.<\/code><\/pre>\n<p>\nAgora a interface Tunnel0 apareceu no console semelhante ao Cisco:<\/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>\nCorrigindo a lista de acesso para criptografia:<\/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>\nConfigurando o roteamento atrav\u00e9s do GRE:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\nno 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>\nRemovendo o cart\u00e3o criptogr\u00e1fico de Fa0\/0 e vinculando ao interface GRE:<\/p>\n<pre><code class=\"plaintext\">VG1(config)#\ninterface Tunnel0\ncrypto map CMAP<\/code><\/pre>\n<p>\nPara VG2 \u00e9 semelhante.<\/p>\n<p>Verifico:<\/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) from 192.168.1.253 : 56(84) bytes of data.\n64 bytes from 192.168.2.254: icmp_seq=1 ttl=64 time=492 ms\n64 bytes from 192.168.2.254: icmp_seq=2 ttl=64 time=1.08 ms\n64 bytes from 192.168.2.254: icmp_seq=3 ttl=64 time=1.06 ms\n64 bytes from 192.168.2.254: icmp_seq=4 ttl=64 time=1.07 ms\n\n--- 192.168.2.254 ping statistics ---\n4 packets transmitted, 4 received, 0% packet loss, time 3006ms\nrtt min\/avg\/max\/mdev = 1.064\/124.048\/492.972\/212.998 ms<\/code><\/pre>\n<p>Estat\u00edsticas 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 (Endere\u00e7o Local,Porta)-(Endere\u00e7o Remoto,Porta) Estado Enviado Recebido\n1 2 (172.16.1.253,500)-(172.16.1.254,500) ativo 1094 1022\n\nConex\u00f5es IPsec:\nNum Conn-id (Endere\u00e7o Local,Porta)-(Endere\u00e7o Remoto,Porta) Protocolo A\u00e7\u00e3o Tipo Enviado Recebido\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>\nNo dump de tr\u00e1fego, pacotes ESP encapsulados em GRE:<\/p>\n<p><img decoding=\"async\" alt=\"1.5 esquemas em IPsec VPN nacional. Testando vers\u00f5es demo\" src=\"\/wp-content\/uploads\/2020\/08\/068865544de126a1673c6fb7b6367ffd.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSa\u00edda: IPsec-over-GRE funciona corretamente.<\/p>\n<h3>Resultados<\/h3>\n<p>\nUma x\u00edcara de caf\u00e9 foi suficiente. Preparei uma instru\u00e7\u00e3o para obter a vers\u00e3o demo. Configurei GRE-over-IPsec e implementei ao contr\u00e1rio.<\/p>\n<p>O mapa de interfaces de rede na vers\u00e3o 4.3 \u00e9 autom\u00e1tico! Continuo testando.<\/p>\n<p><i>Engenheiro an\u00f4nimo<br \/>\nt.me\/anonimous_engineer<\/i><br \/>\n<br \/>Fonte: <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.3 - 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\/pt\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"pt_PT\" \/>\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\/pt\/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 esquemas em VPN IPsec nacional. Testando vers\u00f5es demo | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/1-5-shemy-na-otechestvennom-ipsec-vpn-testiruyu-demoversii","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pt_PT","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\/pt\/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\/pt\/wp-json\/wp\/v2\/posts\/91210","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/comments?post=91210"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/91210\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media\/91211"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media?parent=91210"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/categories?post=91210"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/tags?post=91210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}