Il 01/09/19 19:09, john doe ha scritto:
After seeing some warnings in the system logs, I decided to investigate andIt would help if we could see those warnings as well.
Sep 2 16:59:40 clarisse systemd[1]: openvpn@update-systemd-resolved.service: Service RestartSec=5s expired, scheduling restart. Sep 2 16:59:40 clarisse systemd[1]: openvpn@update-systemd-resolved.service: Scheduled restart job, restart counter is at 266. Sep 2 16:59:40 clarisse systemd[1]: Stopped OpenVPN connection to update-systemd-resolved. Sep 2 16:59:40 clarisse systemd[1]: Starting OpenVPN connection to update-systemd-resolved... Sep 2 16:59:40 clarisse ovpn-update-systemd-resolved[12327]: Options error: --up script fails with '/etc/openvpn/scripts/update-systemd-resolved': No such file or directory (errno=2) Sep 2 16:59:40 clarisse ovpn-update-systemd-resolved[12327]: Options error: Please correct this error. Sep 2 16:59:40 clarisse ovpn-update-systemd-resolved[12327]: Use --help for more information. Sep 2 16:59:40 clarisse systemd[1]: openvpn@update-systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE Sep 2 16:59:40 clarisse systemd[1]: openvpn@update-systemd-resolved.service: Failed with result 'exit-code'. Sep 2 16:59:40 clarisse systemd[1]: Failed to start OpenVPN connection to update-systemd-resolved.
found out that I am supposed to enable this script to integrate the dnsWhich script are you refering to?
In package openvpn-systemd-resolved, there is a config file which also installed under /etc/openvpn. This config references a script to be installed as /etc/openvpn/scripts/update-systemd-resolved
Do I really have to do it if I am not worried about dns leaks? I'm actually ok with using whatever server the local network has, as long as the traffic itself is encrypted I'm fine.If you are happy with how things are working, that is up to you to ignore the warnings. In my view, warnings are to be dealt with! :)
Once I am sure I understand the implications, ignoring them is not a bad idea. That said, my main concern was integrating the config with the n-m gui... now that I think about it, the warnings are proof that this is a non-issue :)
Thanks, Andrea.