A VPN client is a terminal device or software used to establish a secure connection between a user and a VPN server.
What is VPN?
VPN (Virtual Private Network) helps you access internet resources remotely, securely, and privately with tunneling technology. The VPN encrypts your personal information and hides your IP address from the public when you use the internet. To the users of the VPN, it will look like the computers were directly connected to each other.
Common Network Topology:
Here we take WR2100 as a demonstration.
Step 1: Open a web browser and go to http://cudy.net or http://192.168.10.1.
For details, please refer to How to log into the web interface of Cudy Router?
Step 2: Click on General Settings->VPN and enable VPN.
Default Rule: Allow all devices or Ban all devices to use VPN.
To specify the device, click on System Status-> Devices->VPN to enable or disable it.
Site-to-Site: Allow the devices in two sites to communicate with each other.
VPN Policy:
Disable: No additional setting.
VPN kill switch: Turn off the Internet connectivity when the VPN connection is lost.
Domain: Specify which domains go through the VPN and which don't
Remote Subnet: Specify what subnets go through the VPN and which don't
Step 3: In the Protocol list, select the one you need and enter the VPN information provided by your VPN provider.
• PPTP VPN
Enter the VPN server address (for example, 113.92.73.163) and the VPN Username and password provided by your VPN provider.
• L2TP VPN
Enter the VPN server address (for example 113.92.73.163), VPN username and password, and pre-shared key provided by your VPN provider.
If your VPN provider also provides you the tunnel IP which binds with the account, you can enable the Use custom tunnel IP option.
• OpenVPN
Click on Browser to import the configuration file provided by your VPN provider.
• WireGuard VPN
Click on Browser to import the configuration file provided by your VPN provider.
The Interface and Peer will synchronize automatically from your VPN Provider's CONF File.
• ZeroTier Slave
Type in the ZeroTier Network ID and Gateway provided by the ZeroTier Master. The Gateway can be found on VPN Status part.
Related Article: How to remote connect Cudy Router via Zerotier?-Cudy Home
138 comments
@Уважаемый Дмитрий,
К сожалению, в настоящее время у нас нет таких планов.
“Добрый день. Подскажите:
1. Планируется ли добавление VPN протокола AmneziaWG на ваши роутеры.
2. Планируется ли введение более “гибких” настроек VPN (например, фильтры по MAC, расписание работы и тд).
3. Планируется ли добавление возможности настройки Proxy.
Спасибо."
Добрый день. Подскажите:
1. Планируется ли добавление VPN протокола AmneziaWG на ваши роутеры.
2. Планируется ли введение более “гибких” настроек VPN (например, фильтры по MAC, расписание работы и тд).
3. Планируется ли добавление возможности настройки Proxy.
Спасибо.
Hopefully you’ve received the requested screenshots etc. by mail a week ago regarding “WR3000E FW 2.4.7 doesn’t auto-reconnect dropped WireGuard and may leak IP despite VPN kill switch (in WISP at least)”. If you need any further information, please let me know.
@Dear Martin,
You need to set routing rules on the VPN server. The target is the LAN subnet of LT12, The next hop is the VPN tunnel IP address. You can have a try.
Is the VPN Server set on a Cudy router? If yes, you can set the remote subnet when creating wireguard config.
“I have a configuration where I’m running a WireGuard server, and I connect to it as a client using an LT12 router.
The tunnel is established, the handshake is exchanged, and “data is being transferred.”
I even managed to route all LAN traffic through the WireGuard VPS server’s WAN.
I can successfully ping the WireGuard server (data is going properly do Lt12, i did tcp dump)
However, for some reason, I’m unable to reach the WireGuard client on the LT12 from the VPS server.
I’ve tried many things — I have the exact same configuration on another client, and it works.
In the VPN settings, I also have the Site-to-Site option enabled. Should I change something in the routing?
What I want is a setup where I can access both the WireGuard server and Client B (on a laptop that’s also a WireGuard client)."
I have a configuration where I’m running a WireGuard server, and I connect to it as a client using an LT12 router.
The tunnel is established, the handshake is exchanged, and “data is being transferred.”
I even managed to route all LAN traffic through the WireGuard VPS server’s WAN.
I can successfully ping the WireGuard server (data is going properly do Lt12, i did tcp dump)
However, for some reason, I’m unable to reach the WireGuard client on the LT12 from the VPS server.
I’ve tried many things — I have the exact same configuration on another client, and it works.
In the VPN settings, I also have the Site-to-Site option enabled. Should I change something in the routing?
What I want is a setup where I can access both the WireGuard server and Client B (on a laptop that’s also a WireGuard client).