VPN-klient on lõppseade või tarkvara, mida kasutatakse turvalise ühenduse loomiseks kasutaja ja VPN-serveri vahel.
Mida on VPN?
VPN (Virtual Private Network) aitab teil tunneltehnoloogia abil kaugelt, turvaliselt ja privaatselt internetiressurssidele ligi pääseda. VPN krüpteerib teie isikuandmed ja varjab teie IP-aadressi avalikkuse eest, kui kasutate internetti. VPN-i kasutajate jaoks näeb see välja, nagu oleksid arvutid omavahel otse ühendatud.
Üldine võrgutopoloogia:
Sealt võtame näitena WR2100.
Sepp 1: Avatakse veebilehitseja ja minnakse veebilehele http://cudy.net või http://192.168.10.1.
Detailide saamiseks vaadake Kuidas sisse logida Cudy Routeri veebiliidesesse?
Sepp 2: Klõpsake Üldised seaded->VPN ja lubage VPN.
Vaikimisi reegel: Luba kõigile seadmetele või Kõikidele seadmetele VPN-i kasutamine keelata.
Süsteemi olek-> seadmed->seadmed->VPN lubamiseks või keelamiseks.
Site-to-Site: Võimaldab kahe saidi seadmetel omavahel suhelda.
VPN-poliitika:
Katkestatud: Ei mingeid täiendavaid seadeid.
VPN kill switch: Katkestab internetiühenduse, kui VPN-ühendus on kadunud.
Domeen: Määrake, millised domeenid lähevad läbi VPN-i ja millised mitte
Remote Subnet: Määrake, millised alamvõrgud lähevad läbi VPN-i ja millised mitte
Sepp 3: Valige Protokoll nimekirjast see, mida vajate, ja sisestage oma VPN-teenuse pakkuja poolt antud VPN-teave.
- PPTP VPN
Sisestage VPN serveri aadress (näiteks 113.92.73.163) ning VPN kasutajanimi ja parool, mille teie VPN teenusepakkuja on andnud.
- L2TP VPN
Sisestage VPN serveri aadress (näiteks 113.92.73.163), VPN kasutajanimi ja parool ning teie VPN teenusepakkuja poolt antud eeljaotatud võti.
Kui teie VPN-teenusepakkuja annab teile ka tunneli IP, mis on seotud kontoga, saate lubada valiku Kasutage kohandatud tunneli IP-d.
- OpenVPN
Klikkige Browser, et importida oma VPN teenusepakkuja poolt pakutud konfiguratsioonifail.
- WireGuard VPN
Klikkige Browser, et importida oma VPN teenusepakkuja poolt pakutud konfiguratsioonifail.
Sinterneti Interface ja Peer sünkroniseeritakse automaatselt teie VPN teenusepakkuja CONF failist.
- ZeroTier Slave
Tabele ZeroTier Network ID ja Gateway, mille ZeroTier Master on andnud. Gateway on leitav VPN Status osast.
Väline artikkel: Kuidas Cudy marsruuteriga Zerotieri kaudu kaugühendust luua?-Cudy Home
201 kommentaari
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.