On 25 January 2021 20:56:36 CET, Klemens Nanni <k...@openbsd.org> wrote:
>On Mon, Jan 25, 2021 at 07:05:40PM +0100, Florian Obser wrote:
>> Unwind / libunbound goes pretty badly off the rails when an address
>> family is not available, it still tries to talk to nameservers with
>an
>> unreachable address family.
>> I don't think it's libunbound's place to figure this out. It can't
>> sensibly do a getifaddrs on every query...
>> So let's help it out a bit.
>Cool, this is pretty much what I had in mind after your reply to the
>other thread.
>
>Have you tested this by adding some IPv4 address? unwind dies on me:
Yes, that's actually the only thing I tried, flipping v4 on and off.
>
> $ ifconfig all inet | grep -w inet
> inet 127.0.0.1 netmask 0xff000000
> $ doas ifconfig tun0 1.2.3.4
>
> check_available_af 3 - 2
> fatal in resolver: new_resolver: invalid resolver state: dead
Pretty sure this isn't a bug in this diff, it just gets exposed more easily. I
also see that I left too much debug code in there...
I'll have a look tomorrow.
> frontend exiting
> waiting for children to terminate
> terminating
--
Sent from a mobile device. Please excuse poor formating.
