VPT klients ir termināla ierīce vai programmatūra, ko izmanto, lai izveidotu drošu savienojumu starp lietotāju un VPN serveri.
Kas ir VPN?
VPN (virtuālais privātais tīkls) palīdz piekļūt interneta resursiem attālināti, droši un privāti, izmantojot tuneļošanas tehnoloģiju. VPN šifrē jūsu personisko informāciju un slēpj jūsu IP adresi no sabiedrības, kad izmantojat internetu. VPN lietotājiem tas izskatās tā, it kā datori būtu tieši savienoti viens ar otru.
Kopējā tīkla topoloģija:
Turpmāk mēs paraugam WR2100.
1. solis: Atveriet tīmekļa pārlūkprogrammu un dodieties uz http://cudy.net vai http://192.168.10.1.
Lai iegūtu sīkāku informāciju, lūdzu, skatiet Kā pieteikties Cudy maršrutētāja tīmekļa saskarnē?"
2. solis: Noklikšķiniet uz Vispārējie iestatījumi->VPN un iespējojiet VPN.
No noklusējuma noteikums: Atļaut visām ierīcēm vai Uzdrošināt visām ierīcēm izmantot VPN.
Lai norādītu ierīci, noklikšķiniet uz Sistēmas statuss-> Ierīces->VPN, lai to iespējotu vai aizliegtu.
Site-to-Site:
ļauj divu vietņu ierīcēm sazināties savā starpā.VPN politika:
Aizslēgt: Nav papildu iestatījumu.
VPN izslēgšanas slēdzis: Izslēdz interneta savienojumu, kad VPN savienojums tiek zaudēts.
Domēns:Noteikt, kuri domēni iet caur VPN un kuri ne
Dalītais apakštīkls: Norādiet, kuri apakštīkli iet caur VPN un kuri ne
3. solis: Sarakstā Protokols izvēlieties vajadzīgo un ievadiet VPN pakalpojumu sniedzēja sniegto informāciju par VPN.
- PPTP VPN
Ievadiet VPN servera adresi (piemēram, 113.92.73.163) un VPN lietotājvārdu un paroli, ko nodrošina VPN pakalpojumu sniedzējs.
- L2TP VPN
Ievadiet VPN servera adresi (piemēram, 113.92.73.163), VPN lietotājvārdu un paroli un VPN pakalpojumu sniedzēja nodrošināto iepriekš piešķirto atslēgu
Ja jūsu VPN pakalpojumu sniedzējs nodrošina arī tuneļa IP, kas saistās ar kontu, varat iespējot Izmantot pielāgotu tuneļa IP opciju.
- OpenVPN
Noklikšķiniet uz Browser, lai importētu VPN pakalpojumu sniedzēja sniegto konfigurācijas failu
.
- WireGuard VPN
Noklikšķiniet uz Browser, lai importētu VPN pakalpojumu sniedzēja sniegto konfigurācijas failu.
Interface un Peer tiks sinhronizēti automātiski no jūsu VPN pakalpojumu sniedzēja CONF faila.
- ZeroTier Slave
Ievadiet ZeroTier Network ID un Gateway, ko sniedz ZeroTier Master. Vārteju var atrast VPN statusa daļā.
Saistītais raksts: Kā attālināti pieslēgt Cudy maršrutētāju, izmantojot Zerotier?Cudy Sākums
201 komentārs
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.