Stared at it, and tested, and it's indeed quite useful (v3 had a stray
"%s" which is fixed in v4).
Without the patch, trying with "--local <v6 address>" + "--remote <v4only>"
RESOLVE: Cannot resolve host address: v4only.v6.de:51194 (No address
associated with hostname)
with the patch:
RESOLVE: Cannot resolve host address: v4only.v6.de:51194[AF_INET6] (No
address associated with hostname)
so when trying to diagnose user reports, this immediately points to
"mmmh, something is forcing v6 here, why?".
With no --local and no --proto udp4, nothing is forced, and thus:
RESOLVE: Cannot resolve host address: nix.v6.de:51194 (Name or service not
known)
Your patch has been applied to the master branch.
commit d16781531898b4c5a76cfe6cba02fccce9afb8ad
Author: Arne Schwabe
Date: Tue Mar 25 20:57:43 2025 +0100
Mention address if not unspecific on DNS failure
Signed-off-by: Arne Schwabe <a...@rfc2549.org>
Acked-by: Gert Doering <g...@greenie.muc.de>
Message-Id: <20250325195750.7899-1-g...@greenie.muc.de>
URL:
https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg31237.html
Signed-off-by: Gert Doering <g...@greenie.muc.de>
--
kind regards,
Gert Doering
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
