Um cliente VPN é um dispositivo terminal ou software usado para estabelecer uma conexão segura entre um usuário e um servidor VPN.
O que é VPN?
Uma VPN (Rede Privada Virtual) permite que você acesse recursos da internet remotamente, com segurança e privacidade, utilizando a tecnologia de tunelamento. A VPN criptografa suas informações pessoais e oculta seu endereço IP do público quando você usa a internet. Para os usuários da VPN, parecerá que os computadores estavam conectados diretamente uns aos outros.
Topologia de rede comum:
Aqui usamos o WR2100 como demonstração.
Passo 1:Abra um navegador da web e vá parahttp://cudy.netouhttp://192.168.10.1.
Para mais detalhes, consulteComo fazer login na interface web do roteador Cudy?
Passo 2:Clique emConfigurações gerais->VPNe habilitarVPN.
Regra padrão: Permitir todos os dispositivosouBanir todos os dispositivospara usar VPN.
Para especificar o dispositivo, clique emStatus do sistema->Dispositivos->VPNpara habilitá-lo ou desabilitá-lo.
Site para site:Permitir que os dispositivos em dois locais se comuniquem entre si.
Política de VPN:
Desabilitar:Nenhuma configuração adicional.
Interruptor de segurança de VPN:Desligue a conectividade com a Internet quando a conexão VPN for perdida.
Domínio:Especifique quais domínios passam pela VPN e quais não
Sub-rede remota:Especifique quais sub-redes passam pela VPN e quais não
Etapa 3:NoProtocololista, selecione o que você precisa e insira as informações de VPN fornecidas pelo seu provedor de VPN.
•VPN PPTP
Digite o endereço do servidor VPN (por exemplo, 113.92.73.163) e o nome de usuário e a senha VPN fornecidos pelo seu provedor de VPN.
•VPN L2TP
Digite o endereço do servidor VPN (por exemplo, 113.92.73.163), nome de usuário e senha da VPN e a chave pré-compartilhada fornecida pelo seu provedor de VPN.
Se o seu provedor de VPN também fornecer o IP do túnel que se vincula à conta, você pode habilitar oUsar IP de túnel personalizadoopção.
•OpenVPN
Clique emNavegadorpara importar o arquivo de configuração fornecido pelo seu provedor de VPN.
• WireGuard VPN
Clique emNavegadorpara importar o arquivo de configuração fornecido pelo seu provedor de VPN.
OInterfaceeParserá sincronizado automaticamente com o provedor de VPNArquivo CONF.
• Escravo ZeroTier
Digite oID da rede ZeroTierePortalfornecido pelo ZeroTier Master. O Gateway pode ser encontrado na seção "Status da VPN".
Artigo relacionado: Como conectar remotamente o roteador Cudy via Zerotier? - Cudy Home
201 comentários
Thanks, now It works like a charm.
আমার উয়াইফাই অন্য কারো হাতে
@Dear Inigo Ortega,
We have tested this situation in our office. Here is normal. If the problem remains, please check the following methods:
1. If you ping the device’s IP address of the computer in the Lan area of the P5. Please make sure you have disable the Firewall of the computer.
2. Please check if the computer’s gateway IP address is 192.168.10.1.
3. Please try to login to the web page of the router, Go to “Advanced Settings” —“Firewall” page and disable the SPI Firewall and check again.
“Hello,
I am experiencing a problem with WireGuard Site-to-Site on my Cudy P5 that appears to be very similar to other cases reported on your support website.
My setup is:
Cudy P5 with 5G SIM (Lowi) Firmware: 2.4.27 (latest available) Cudy LAN: 192.168.10.0/24 Cudy LAN IP: 192.168.10.1 ASUS TUF-AX5400 running Asuswrt-Merlin/Gnuton ASUS LAN: 192.168.50.0/24 ASUS LAN IP: 192.168.50.1
The ASUS is configured as the WireGuard server and the Cudy P5 as the WireGuard client.
On the Cudy:
WireGuard Client: enabled Site-to-Site: enabled Default rule: Allow all devices VPN policy: Remote Subnet Remote subnet: 192.168.50.0/24 WireGuard tunnel IP: 10.6.0.2 Endpoint port: 51820
The problem is asymmetric:
1. From a device connected to the Cudy LAN (192.168.10.x), I can access devices on the ASUS LAN (192.168.50.x) correctly.
2. From the ASUS LAN, I can ping 10.6.0.2 and even access the Cudy web interface through 10.6.0.2.
3. However, from the ASUS LAN I cannot access the Cudy LAN:
192.168.10.1 does not respond. Devices behind the Cudy, for example 192.168.10.121, do not respond.
4. Therefore, the WireGuard tunnel itself is working, but traffic arriving through WireGuard is apparently not being forwarded from the VPN interface to the Cudy LAN.
I have already upgraded the P5 from firmware 2.4.25 to the latest 2.4.27, but the behaviour is exactly the same.
I have also found previous Cudy support cases describing what appears to be the same asymmetric Site-to-Site behaviour, where the remote LAN can access the VPN server LAN but the reverse direction does not work.
Could you please confirm:
1. Is this a known limitation or bug in the P5 WireGuard Site-to-Site implementation?
2. Has the problem reported in the previous support cases been fixed in firmware 2.4.27?
3. If it is not fixed, is there a recommended configuration to allow traffic from the WireGuard tunnel (10.6.0.0/…) to be forwarded to the P5 LAN (192.168.10.0/24)?
4. Is there a way to enable the required forwarding/NAT manually, or is this something that requires a firmware update?
5. If possible, could you provide the exact configuration required to make the connection fully bidirectional?
I would be happy to provide screenshots or configuration details if needed.
Thank you."
Hello,
I am experiencing a problem with WireGuard Site-to-Site on my Cudy P5 that appears to be very similar to other cases reported on your support website.
My setup is:
Cudy P5 with 5G SIM (Lowi) Firmware: 2.4.27 (latest available) Cudy LAN: 192.168.10.0/24 Cudy LAN IP: 192.168.10.1 ASUS TUF-AX5400 running Asuswrt-Merlin/Gnuton ASUS LAN: 192.168.50.0/24 ASUS LAN IP: 192.168.50.1The ASUS is configured as the WireGuard server and the Cudy P5 as the WireGuard client.
On the Cudy:
WireGuard Client: enabled Site-to-Site: enabled Default rule: Allow all devices VPN policy: Remote Subnet Remote subnet: 192.168.50.0/24 WireGuard tunnel IP: 10.6.0.2 Endpoint port: 51820The problem is asymmetric:
1. From a device connected to the Cudy LAN (192.168.10.x), I can access devices on the ASUS LAN (192.168.50.x) correctly.
192.168.10.1 does not respond. Devices behind the Cudy, for example 192.168.10.121, do not respond.2. From the ASUS LAN, I can ping 10.6.0.2 and even access the Cudy web interface through 10.6.0.2.
3. However, from the ASUS LAN I cannot access the Cudy LAN:
4. Therefore, the WireGuard tunnel itself is working, but traffic arriving through WireGuard is apparently not being forwarded from the VPN interface to the Cudy LAN.
I have already upgraded the P5 from firmware 2.4.25 to the latest 2.4.27, but the behaviour is exactly the same.
I have also found previous Cudy support cases describing what appears to be the same asymmetric Site-to-Site behaviour, where the remote LAN can access the VPN server LAN but the reverse direction does not work.
Could you please confirm:
1. Is this a known limitation or bug in the P5 WireGuard Site-to-Site implementation?
2. Has the problem reported in the previous support cases been fixed in firmware 2.4.27?
3. If it is not fixed, is there a recommended configuration to allow traffic from the WireGuard tunnel (10.6.0.0/…) to be forwarded to the P5 LAN (192.168.10.0/24)?
4. Is there a way to enable the required forwarding/NAT manually, or is this something that requires a firmware update?
5. If possible, could you provide the exact configuration required to make the connection fully bidirectional?
I would be happy to provide screenshots or configuration details if needed.
Thank you.
Mám CUDY R700 a vypadává mi připojení do Internetu. Běží několik hodin (různě) a pak dojde k přerušení spojení. Zařízení je nutné restartovat, aby se opět rozběhlo. Zkoušel jsem i VPN tunel pomocí IPSEC a OpenVPN proti zařízení ARCHER VX1800v VPN. Nedaří se mi VPN zprovoznit.