Openvpn legacy service что это

Openvpn legacy service что это

In order to get OpenVPN GUI to auto-start and auto-connect on boot, we need to pick a single configuration for a particular location that we wish to connect on every boot.

For the purpose of this guide, I am going to use PrivateVPN’s OpenVPN-TUN-UDP configuration for India.

Step 1 — Editing your OpenVPN client configuration

Open .ovpn file in Notepad application, look for # Crypto section and make the following changes as seen in the image below:

Save and close the .ovpn file.

Step 2 — Storing your PrivateVPN.com credentials in a file

Open Notepad application and type your PrivateVPN username in first line and password in second, save the file as user.auth.

Step 3 — Import edited .ovpn file and user.auth file to OpenVPN config folder

Navigate to Program files — OpenVPN — config folder of your main Windows installation. Copy your edited .ovpn file and user.auth there. When prompted for Administrative permission, grant it to Continue.

Step 4 — Configuring OpenVPN service to start automatically on boot

Start Run application from Start Menu or by using keyboard shortcut combination Ctrl+R and input services.msc in the text field there and click OK.

Locate OpenVpnService (Not OpenVPN Legacy Service or OpenVPN Interactive Service) and double-click on it.

A dialog box appears, change Startup type to Automatic, and click Apply followed by OK. That is all. OpenVPN configuration file should connect right away and on every boot automatically.

Note: You are not required to use OpenVPN GUI client any more. ‘OpenVpnService’ would automatically connect you to respective PrivateVPN OpenVPN server on boot.

OpenVPN Support Forum

2.4.3 installed, but did proper service get started

2.4.3 installed, but did proper service get started

Post by brrrknee » Sun Jul 30, 2017 11:08 pm

2.4.3 creates 3 windows 10 service entries, and I found no wiki/howto/man page description related to the service programs noted herein

openvpn interactive service is created for openvpnserv.exe, [«C:\Program Files\OpenVPN\bin\openvpnserv.exe»] automatic start
and from wiki brief, it enables non-privileged users to use the GUI for openVPN

openvpn legacy service is also created for openvpnserv.exe manual start

openvpnservice is created for openvpnserv 2 .exe [«C:\Program Files\OpenVPN\bin\openvpnserv 2 .exe»] and also automatic start

I think one of these 2 automatic start services ought not be.
I’d cleared all of the prior openvpn service entries (I’d tried 2.4.3, thought it was wrong, then installed 2.3.17 over it, making it a mess) using the windows service tools to ensure I was starting clean after uninstalling openVPN 2.3.17 and Tap-windows to ensure everything was a fresh slate.

After again installing 2.4.3 the above is what I ended up with. it was a long day, and I cannot say for sure if I set one of those 2 to auto start or not.

ultimately, what are the services supposed to be configured as?
is the OpenVPNService openvpnserv 2 .exe the one to use/autostart? Or,
should I be using (auto starting) the Interactive openvpnserv.exe?

is the Interactive meant to be used/ installed on client systems, and the OpenVPNService intended for the server?

and why is there a dupe «legacy» over openvpnserv.exe?

thanks.
Still trying to figure out why Win10 firewall is dropping the UDP forwarded port requests, even with explicit «allow» over the port for UDP and no blocking rules that would affect this port.

Re: 2.4.3 installed, but did proper service get started

Post by brrrknee » Mon Jul 31, 2017 4:26 am

Appears that the OpenVPN Interactive Service is intended to be automatic, allowing GUI connect to work without issue; I’ve left the other 2 to be Manual start.

An update Regarding the perplexing loss of OpenVPN packets in the Win10 firewall ether:
I found an excellent hint to discover the source of the problem in
https://superuser.com/questions/1130078 . ng-traffic
which allowed me to identify a Windows Filtering Platform Filter named «Port Scanning Prevention Filter»
Looking into MS’ documentation on that filter, WFP found that there was no process listening on the inbound destination (my server) UDP port , and as such, regards the packet to be from a port scanner and silently drops the packet .
That’s the killer: Such packets are silently dropped, so they do not show up in any logs! That’s why the above article was so key on using the Windows audit tools vs the WFP , I’d never have found this without it.

Now I have been seeing Firewall log entries showing some of these UDP port packets as explicitly dropped, which means WFP at times sees a listening process, and at times does not! These explicitly dropped packets are found by WFP to be malformed in some manner (the MS documentation didn’t expound upon these broken forms).
So how does an internet browser request of «mysite.dyndns.com: myport# » end up malformed upon delivery? This one is outside of OpenVPN, outside of the router, possibly an issue with the Dyn DNS service I use, possibly an issue w Windows’ WFP .
Included here only as a heads up, head-scratcher that we all soooo enjoy.

The dropped packets are received on the «router internal LAN» IP of the LAN OpenVPN server’s Ethernet & port ; they come directly from the router to the server on the Ethernet link from the WAN/internet.
Externally I can enter into a browser «mysite.dyndns.com:myport#» which gets anonymously to my dynamic IP from the ISP; there my WAN-facing router intercepts that port, maps and forwards it to my internal LAN server IP, 192.168.xxx.xxx form.
This is the IP:Port that windows will see on the network, so WFP needs to see OpenVPN server [some process] actively listening to this UDP port to process these packets .

As the OpenVPN server is starting per the server.ovpn config, it listens on the LAN IP & Port, then sets up the internal VPN 10.8.0.0 set of virtual IPs. The server-listening must be on the LAN 192.168.xxx.xxx and not the virtual 10.8.0.xxx IPs.

Why would OpenVPN server not be recognized by WFP as listening on this UDP port ?
Using MS’ resmon.exe (resource monitor) you can explicitly see that openvpn.exe is listening on this UDP port . and on the IPv4 loopback port, TCP 25340 (so I added an ALLOW inbound and outbound rule for that too; didn’t help!)

It’s started, running, and both the IP and port are set in the server.ovpn file.

The hunt for final resolution continues. if I find anything else I’ll update it here for others to see ; running out of threads to follow.

Name already in use

a / Configure OpenVPN client as service on Windows — PrivateVPN.md

• Go to file T
• Go to line L
• Copy path
• Copy permalink

• Open with Desktop
• View raw
• Copy raw contents Copy raw contents

Copy raw contents

Copy raw contents

Configure OpenVPN client as service on Windows

In order to get OpenVPN GUI to auto-start and auto-connect on boot, we need to pick a single configuration for a particular location that we wish to connect on every boot.

For the purpose of this guide, I am going to use PrivateVPN’s OpenVPN-TUN-UDP configuration for India.

Step 1 — Editing your OpenVPN client configuration

Open .ovpn file in Notepad application, look for # Crypto section and make the following changes as seen in the image below:

Save and close the .ovpn file.

Step 2 — Storing your PrivateVPN.com credentials in a file

Open Notepad application and type your PrivateVPN username in first line and password in second, save the file as user.auth.

Step 3 — Import edited .ovpn file and user.auth file to OpenVPN config folder

Navigate to Program files — OpenVPN — config folder of your main Windows installation. Copy your edited .ovpn file and user.auth there. When prompted for Administrative permission, grant it to Continue.

Step 4 — Configuring OpenVPN service to start automatically on boot

Start Run application from Start Menu or by using keyboard shortcut combination Ctrl+R and input services.msc in the text field there and click OK.

Locate OpenVpnService (Not OpenVPN Legacy Service or OpenVPN Interactive Service) and double-click on it.

A dialog box appears, change Startup type to Automatic, and click Apply followed by OK. That is all. OpenVPN configuration file should connect right away and on every boot automatically.

Note: You are not required to use OpenVPN GUI client any more. ‘OpenVpnService’ would automatically connect you to respective PrivateVPN OpenVPN server on boot.

Openvpn legacy service что это

Как я могу исправить проблемы запуска OpenVPN в Windows 10?

1. Отключить брандмауэр Windows
2. Отключить стороннее антивирусное программное обеспечение
3. Перезапустите адаптер TAP
4. Переустановите и обновите драйвер TAP-Windows
5. Проверьте, работает ли служба DHCP
6. Очистить DNS
7. Сброс Winsock

1. Отключите брандмауэр Windows

• Нажмите кнопку Cortana на панели задач, чтобы открыть это приложение.
• Введите ключевое слово «Брандмауэр Windows» в поле поиска и выберите, чтобы открыть Брандмауэр Защитника Windows .

• Нажмите Включить или выключить брандмауэр Защитника Windows, чтобы открыть настройки, показанные на снимке ниже.

• Выберите оба параметра « Отключить брандмауэр Защитника Windows» .
• Нажмите кнопку ОК .

• Щелкните правой кнопкой мыши панель задач Windows и выберите « Диспетчер задач» в открывшемся контекстном меню.
• Откройте вкладку «Автозагрузка» в окне «Диспетчер задач».

• Выберите антивирусное программное обеспечение и нажмите кнопку « Отключить» .
• Затем перезагрузите свой ноутбук или рабочий стол.

3. Перезапустите адаптер TAP.

• Нажмите сочетание клавиш Windows + R, чтобы открыть аксессуар «Запуск».
• Введите «Панель управления» в «Выполнить» и нажмите кнопку ОК .
• Нажмите « Центруправлениясетями и общим доступом», чтобы открыть настройки панели управления , показанные непосредственно ниже.

• Нажмите Изменить настройки адаптера, чтобы открыть свои подключения, как показано ниже.

• Затем щелкните правой кнопкой мыши Адаптер TAP-Windows и выберите Отключить .
• Щелкните правой кнопкой мыши TAP-Windows Adapter и выберите Enable, чтобы перезапустить адаптер.

4. Переустановите и обновите драйвер TAP-Windows

• Выберите Диспетчер устройств, чтобы открыть окно в кадре прямо ниже.

• Дважды щелкните Сетевые адаптеры, чтобы развернуть список сетевых адаптеров.
• Щелкните правой кнопкой мыши TAP-Windows Adapter и выберите « Удалить устройство» .

• Теперь откройте эту страницу OpenVPN в вашем браузере .
• Прокрутите страницу до конца и нажмите tap-windows-9.21.2.exe, чтобы загрузить последнюю версию драйвера TAP (NDIS 6) для OpenVPN. Драйвер NDIS 5 предназначен для Windows XP.

• Щелкните правой кнопкой мыши исполняемый файл TAP-Windows и выберите « Запуск от имени администратора».
• Перезагрузите Windows после установки драйвера.

5. Проверьте, работает ли служба DHCP

• Введите «services.msc» в «Выполнить» и нажмите кнопку « ОК» .
• Прокрутите вниз до DHCP-клиента, показанного на снимке ниже.

• Дважды щелкните DHCP-клиент, чтобы открыть окно его свойств.

• Выберите « Автоматически» в раскрывающемся меню «Тип запуска».
• Затем нажмите кнопку « Начать обслуживание».
• Если DHCP-клиент уже запущен, нажмите кнопки « Стоп» и « Пуск», чтобы перезапустить его.
• Нажмите кнопку Применить и ОК .

6. Очистите DNS

• Откройте меню Win + X с помощью клавиши Windows + X.
• Нажмите Командная строка (Администратор) в меню Win + X.
• Введите следующие команды отдельно в окне подсказки:

• Закройте командную строку и перезапустите Windows.

7. Сброс Winsock

• Щелкните правой кнопкой мыши Командную строку и выберите Запуск от имени администратора, чтобы открыть ее.
• Затем введите «netsh int ip reset logfile.txt» в командной строке и нажмите клавишу Enter.

• Войдите в каталог сброса netsh winsock и нажмите кнопку возврата.
• Перезагрузите ваш рабочий стол или ноутбук.

OpenVPN GUI «Connection to management interface failed» error for domain user, with no local admin privileges #332

Client = OpenVPN GUI 11.14.0.0/2.4.8 (config and installer generated by pfSense client export plugin)
Server = OpenVPN on up-to-date pfSense
OS = Windows 10 Pro, feature pack 1803
Laptop = Lenovo ThinkPad E550

• User is a domain user with no local admin privileges
• OpenVPN GUI launches on Windows startup
• Config file and TLS key are located at C:\Program Files\OpenVPN\config
• OpenVPN Interactive Service is set to Automatic and is running
• OpenVPNService and OpenVPN Legacy Service are disabled

Issue Description
Sometimes, when double clicking on the OpenVPN GUI, the error message «Connecting to management interface failed» is displayed and no VPN connection is established. However, sometimes the VPN connects normally.

OpenVPN — connecting to management interface failed

My work pc uses openvpn gui and I’ve been randomly having this issue pop up. It will persist for several hours and then randomly I can connect again with seemingly no prompt on either end of the issue. We initially thought it was a firewall issue and turned off the firewall, adjusted the firewall settings, reset the firewall, etc.I attempted to append the config file with the —askpass setting, but I believe I may have entered it incorrectly into the file (if this is indeed a solution, it would be helpful to know how to correctly format it)

I am using openvpn gui 11.25.0.0

Here is the error that pops up:

Here is the text from the log file:

2021-09-16 10:36:14 OpenVPN 2.5.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Jun 17 2021

2021-09-16 10:36:14 Windows version 10.0 (Windows 10 or greater) 64bit

2021-09-16 10:36:14 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10

Enter Management Password:

2021-09-16 10:36:14 MANAGEMENT: TCP Socket listening on [AF_INET](IP ADDRESS)

2021-09-16 10:36:14 Need hold release from management interface, waiting.