Hello,
between yesterday on today I was dealing with setting up the up/down scripts in
a openvpn client config file and it totally escaped me that in the upstream
documentation it uses /etc/openvpn/scripts/ as location of the script while
this package is installed one level higher in
On Thu, Oct 10, 2019 at 9:16 PM Johan Smits wrote:
>
> Yes this solved my warnings. Should this be done by the package? Just
> from a upgrade perspective for other users.
Great!
Well, it's not really an option to remove a conffile (previously
installed into /etc) on package upgrade. Some user
Yes this solved my warnings. Should this be done by the package? Just
from a upgrade perspective for other users.
On Thu, Oct 10, 2019 at 8:40 PM Johan Smits wrote:
>
> Hi Eugene,
>
> Thanks for the quick reply.
>
> I imported a ovpn file but not to my knowledge I configured the path.
> Also when I look in the network manager of the VPN tools I can't find
> anything related to this.
>
> But when I look at
up-restart
down /etc/openvpn/scripts/update-systemd-resolved
down-pre
Is this a package error or a configuration error of the file?
Thanks,
Johan
-Oorspronkelijk bericht-
Van: Eugene Zhukov
Aan: Johan Smits , 942...@bugs.debian.org
Onderwerp: Bug#942068: openvpn-systemd-resolved
Thank you for the bug report, Johan.
Could there be something with the configuration on your side?
update-systemd-resolved is installed under /etc/openvpn not /etc/openvpn/scripts
Thanks,
Eugene
Package: openvpn-systemd-resolved
Version: 1.3.0-3
Severity: normal
Dear Maintainer,
When I check the journal log I see a lot of errors.
It seems like there is a file missing to start the VPN.
But when I start the VPN all works normal (my vpn also uses the same public dns
services)
okt 09
7 matches
Mail list logo