Шаг 1. Введите в адресной строке браузера http://cudy.net или http://192.168.10.1.
Шаг 2. Перейдите в раздел Общие настройки 🡢 VPN и переведите переключатель Включить в подразделе VPN во включённое положение.
Чтобы включить (отключить) VPN для конкретных устройств, перейдите в раздел Состояние системы 🡢 Устройства и переведите переключатель VPN напротив нужного устройства в нужное положение.
Шаг 3. В выпадающем списке параметра Протокол выберите нужный протокол и настройте параметры согласно указаниям поставщика VPN-услуг.
PPTP
Введите адрес VPN-сервера (например, 113.92.73.163), а также имя пользователя и пароль, предоставленные поставщиком VPN-услуг.
L2TP
Введите адрес VPN-сервера (например, 113.92.73.163), а также имя пользователя, пароль и ключ PSK, предоставленные поставщиком VPN-услуг.
Если поставщик VPN-услуг также предоставляет IP-адрес для привязки учётной записи, активируйте параметр Использовать пользовательский IP-адрес туннеля.
OpenVPN
Нажмите на кнопку Обзор... и импортируйте файл настроек, полученный от поставщика VPN-услуг.
WireGuard
Нажмите на кнопку Обзор... и импортируйте файл настроек, полученный от поставщика VPN-услуг.
Поля подразделов Интерфейс и Одноранговый узел будут заполнены автоматически с помощью файла настроек (CONF) поставщика VPN-услуг.
ZeroTier
Введите нужные значения в поля Идентификатор сети ZeroTier и Шлюз.
Комментариев: 196
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).
Dear TEN, Yes, there is a @. samcudy.com.
“Is an @ supposed to go between your name and your company’s?
Will be happy to provide you with all relevant (redacted) screenshots and logs.
Cannot currently record or live-stream video though, as I am not where the router is, and it is on low bandwidth even when (intermittently) online.”
Is an @ supposed to go between your name and your company’s?
Will be happy to provide you with all relevant (redacted) screenshots and logs.
Cannot currently record or live-stream video though, as I am not where the router is, and it is on low bandwidth even when (intermittently) online.