On Sat, Nov 21, 2015 at 8:06 PM, Gert Doering wrote:
> if (sock->info.af == AF_UNSPEC)
> + {
>msg (M_WARN, "Could not determine IPv4/IPv6 protocol.
> Using %s",
> addr_family_name(sock->info.lsa->bind_local->ai_family));
> +
On Sun, Nov 22, 2015 at 1:19 PM, Gert Doering wrote:
> Could you test the patch suggestion I sent yesterday? I think your log
> *should* (before the ASSERT) show the "Could not determine IPv4/IPv6
> protocol. Using..." message...
Ack, will do tomorrow and report.
--
Chris
> weird config like mtu-discovery.
>
> @Christian, how did you manage to trigger the bug?
>
> Arne
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (MingW32)
>
> iEYEARECAAYFAlZQ4EsACgkQe8+cMNS4zRd+cACgxx/d2wY7GdyNkb+/YY93Vxoq
> TZUAoOWgpd0OgR0BtbWhwwpU/ZYzRq8O
> =4VJ
On Tue, Nov 17, 2015 at 1:03 PM, Gert Doering wrote:
> Why are you seeing AF_UNSPEC there? This is actually more interesting
> to me right now than debating possible avenues to fix this :-)
I also see: "Could not determine IPv4/IPv6 protocol. Using AF_INET" in
the logs (which points in an quite
7044e2731eeafcc7f877c7d8b77676fb5d4dbd67 Mon Sep 17 00:00:00 2001
From: Christian Pellegrin
Date: Tue, 17 Nov 2015 12:12:10 +
Subject: [PATCH] Fix info.af == AF_UNSPEC case after commit
2bed089d31a12c2d0277e36a64964ebab6640f75
Signed-off-by: Christian Pellegrin
---
src/openvpn/socket.c | 2 +-
1 file changed, 1 insertion(+), 1
spot as before the mentioned commits. Tested on Linux.
From 55172b6104c47374c062f3581617068840e5b51a Mon Sep 17 00:00:00 2001
From: Christian Pellegrin
Date: Wed, 15 Jul 2015 16:45:58 +0100
Subject: [PATCH] Fix using management interface to get passwords.
Commits
