Come posso impostare il client VPN per accedere a un server VPN remoto?

Un client VPN è un dispositivo terminale o un software utilizzato per stabilire una connessione sicura tra un utente e un server VPN.

 

Che cos'è la VPN?

VPN (Virtual Private Network) ti aiuta ad accedere alle risorse Internet in remoto, in modo sicuro e privato con la tecnologia di tunneling. La VPN crittografa le tue informazioni personali e nasconde il tuo indirizzo IP al pubblico quando usi Internet. Agli utenti della VPN sembrerà che i computer fossero direttamente collegati tra loro.

 

Topologia di rete comune:

 

 

Qui prendiamo WR2100 come dimostrazione.

 

Passaggio 1:  Apri un browser web e vai a http://cudy.net o http://192.168.10.1. 

Per i dettagli, fare riferimento a Come accedere all'interfaccia web di Cudy Router?

Passaggio 2: fai clic su Impostazioni generali->VPN e attiva VPN.

Regola predefinita: Consenti a tutti i dispositivi o Blocca a tutti i dispositivi di utilizzare la VPN.

Per specificare il dispositivo, fare clic su Stato del sistema- > Dispositivi->VPN per attivarlo o disattivarlo.

Da sito a sito: < /strong>Consenti ai dispositivi in ​​due siti di comunicare tra loro.

Politica VPN: 

Disabilita: nessuna impostazione aggiuntiva.

Kill switch VPN: Disattiva la connettività Internet quando si perde la connessione VPN.

Dominio: specifica quali domini passano attraverso la VPN e che non lo fanno

Sottorete remota: specifica quali sottoreti passano attraverso la VPN e quali no

Passaggio 3: Nella Protocollo , seleziona quello che ti serve e inserisci le informazioni sulla VPN fornite dal tuo provider VPN.

 

• VPN PPTP

Inserisci l'indirizzo del server VPN (ad esempio, 113.92.73.163) e il nome utente e la password VPN fornito dal tuo provider VPN.

 

• VPN L2TP

Inserisci l'indirizzo del server VPN (ad esempio 113.92.73.163), nome utente e password VPN e chiave precondivisa forniti dal tuo Fornitore VPN.

Se il tuo provider VPN ti fornisce anche l'IP del tunnel che si collega all'account, puoi abilitare Utilizza l'opzione IP tunnel personalizzato.

 

• OpenVPN < /span>

Fare clic su Browser per importare il file di configurazione fornito da il tuo provider VPN.

 

 

• WireGuard VPN

 

Fare clic su Browser per importare il file di configurazione fornito da il tuo provider VPN.

L'interfaccia e Peer si sincronizzerà automaticamente dal file CONF del tuo provider VPN.

 

 

 

• ZeroTier Slave

Digita ID rete ZeroTier e Gateway fornito da ZeroTier Master. Il gateway è disponibile nella parte Stato VPN.

 

 

Articolo correlato: Come connettere in remoto Cudy Router tramite Zerotier?-Cudy Home

Torna al blog

201 commenti

Thanks, now It works like a charm.

Íñigo Ortega

আমার উয়াইফাই অন্য কারো হাতে

MD Hamim

@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."

support

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.

Inigo Ortega

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.

Karel

Lascia un commento