Hi, On Sun, Nov 22, 2015 at 01:09:48PM +0000, christian pellegrin wrote: > Huh, sorry the segfault.
Nothing to be sorry about - that code is complicated ("has grown over
10+ years, too many options and platforms") and refactoring it for
proper dual-stack support still sees some fallout...
> To solve this specific problem it's enough to
> test for AF_UNSPEC in
> https://github.com/OpenVPN/openvpn/blob/master/src/openvpn/mtu.c#L163,
> I will prepare the patch tomorrow.
I'm not sure what the "right" fix would be at this place - all you can
do is either "do nothing" or "try IPv4 and IPv6 both", which both does
not ring right to me. If we reach this spot, we should know which AF
our socket has...
> I don't think the configuration is too strange. It uses proto udp,
> mode server and sets local address because of LB/HA setup.
> mtu-discovery is set to maybe. What is really strange (and will check
> what is the code flow in this case) is that if I enable multihome and
> IPv6 I don't see the problem.
If you use "proto udp6", you're forcing AF_INET6.
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...
thanks,
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
