Package Details: openvpn-update-systemd-resolved 1.3.0-4

Git Clone URL: https://aur.archlinux.org/openvpn-update-systemd-resolved.git (read-only, click to copy)
Package Base: openvpn-update-systemd-resolved
Description: OpenVPN systemd-resolved Updater
Upstream URL: https://github.com/jonathanio/update-systemd-resolved
Keywords: dns openresolv openvpn resolv resolved systemd
Licenses: GPL
Submitter: jonathanio
Maintainer: max-k
Last Packager: max-k
Votes: 52
Popularity: 0.61
First Submitted: 2016-06-23 21:47 (UTC)
Last Updated: 2021-05-06 15:09 (UTC)

Latest Comments

« First ‹ Previous 1 2 3

aryklein commented on 2017-03-02 14:40 (UTC) (edited on 2017-03-02 14:40 (UTC) by aryklein)

I got a validity check error: ==> ERROR: One or more files did not pass the validity check! I ran 'makepkg -g' and replaced the sha256sums and sha512sums in the PKGBUILD with my output. sha256sums=('0decae4753d0ad36bb7990252ef21fe34d9ff8d00117e09965f4c98bb2c5e26e') sha512sums=('8a415d8727e263f5b47aea914d21a6b4fc04be2a956851b9903b5fe4139123368648c1573651a52f149f03e9a776517fc94ca8ba532ea496695cd5c1c17dd03e')

jonathanio commented on 2016-12-28 13:48 (UTC)

@demoji, Thanks for the feedback. The post_install script was just a copy of the one used in the google-chrome* packages as that was (at the time) the easiest one to get my hands on when I needed to work out how to add the message. I've toned it down to just a simple echo statement and fixed the messages to separate down/down-pre.

demoji commented on 2016-12-28 10:14 (UTC)

Your post_install notes are out of sync with your upstream README.md. And I think colored "===> NOTE: bold text" is trying too much, but whatever.

jonathanio commented on 2016-10-06 09:12 (UTC)

@afiskon, The purpose of the script is not to update /etc/resolve.conf, as that is a backwards compatibility layer provided by systemd-resolved for programs which do not communicate directly with it over DBUS, nor don't use the stand NSS layer in glibc. The preferred method is to update your nsswitch.conf file and replace the "dns" option under "hosts:" to "resolve", or add "resolve" before "dns". DOMAIN and DOMAIN-SEARCH can then be used to route appropriately selected domains to the DNS servers on that link. At least in these cases the DNS requests will only be directed to the servers in question rather than broadcasted to all. Have you tried the following? Maybe as a catch-all, that could work. dhcp-option DOMAIN . Otherwise, I'm not sure atm if system-resolved supports overriding all previously configured DNS servers temporarily for the life of a link.

afiskon commented on 2016-10-06 08:46 (UTC)

Unfortunately, this scripts _adds_ DNS to /etc/resolv.conf, not _replaces_ it. Sometimes DNS specified in servers's config is added to the beginning of the DNS servers list, and sometimes to the end. I.e. you don't know whether ISP's or VPN's DNS servers will be used.

jonathanio commented on 2016-07-07 21:50 (UTC)

@jpala, Many thanks for spotting that error of mine! I have applied the patch and updated the package.

jpala commented on 2016-07-07 10:12 (UTC)

Hi thanks for this script. Small thing I noted in the PKGBUILD that i'm not sure is intentional or not: the script gets installed as "update-system-resolved" (not systemd). Possible patch to update if unintentional is: --- PKGBUILD.orig 2016-07-07 20:01:49.602833728 +1000 +++ PKGBUILD.new 2016-07-07 20:02:20.072668659 +1000 @@ -12,7 +12,7 @@ package() { cd $srcdir/update-systemd-resolved-${pkgver} - install -D -m655 update-systemd-resolved "${pkgdir}/etc/openvpn/update-system-resolved" + install -D -m655 update-systemd-resolved "${pkgdir}/etc/openvpn/update-systemd-resolved" } # vim:set ts=2 sw=2 et:

« First ‹ Previous 1 2 3