Hi George, Yes, Version 1.15.0 works just fine.
Ray -----Original Message----- From: George Thessalonikefs <geo...@nlnetlabs.nl> Sent: 30 May 2022 16:58 To: RayG <rgs...@btinternet.com>; Unbound - Bugs <unbound-b...@nlnetlabs.nl>; unbound-users@lists.nlnetlabs.nl Subject: Re: unbound_1.16.0rc1 fails to start Hi Ray, Was any previous version working and 1.16.0rc1 introduced this issue? Best regards, -- George On 29/05/2022 16:56, RayG wrote: > Installingunbound_1.16.0rc1over the top of the current > install(unbound_1.15.0) itfails when started > > 29/05/2022 15:32:12 C:\Program Files\Unbound\unbound.exe[12244:0] error: > setsockopt(..., IPV6_MTU, ...) failed: Bad protocol option. > > 29/05/2022 15:38:02 C:\Program Files\Unbound\unbound.exe[1192:0] error: > setsockopt(..., IPV6_MTU, ...) failed: Bad protocol option. > > 29/05/2022 15:40:01 C:\Program Files\Unbound\unbound.exe[9700:0] error: > setsockopt(..., IPV6_MTU, ...) failed: Bad protocol option. > > With verbosity 4: > > [1653835814] C:\Program Files\Unbound\unbound.exe[12340:0] debug: > winservice - apply cfg > > 29/05/2022 15:50:14 C:\Program Files\Unbound\unbound.exe[12340:0] debug: > setup SSL certificates > > 29/05/2022 15:50:14 C:\Program Files\Unbound\unbound.exe[12340:0] debug: > Adding Windows certificates from system root store to CA store > > 29/05/2022 15:50:14 C:\Program Files\Unbound\unbound.exe[12340:0] debug: > Completed adding Windows certificates to CA store successfully > > 29/05/2022 15:50:14 C:\Program Files\Unbound\unbound.exe[12340:0] debug: > winservice - open ports > > 29/05/2022 15:50:14 C:\Program Files\Unbound\unbound.exe[12340:0] debug: > creating udp6 socket ::1 53 > > 29/05/2022 15:50:14 C:\Program Files\Unbound\unbound.exe[12340:0] error: > setsockopt(..., IPV6_MTU, ...) failed: Bad protocol option. > > Edition Windows 10 Pro > > Version 21H2 > > Installed on 04/04/2022 > > OS build 19044.1708 > > Experience Windows Feature Experience Pack 120.2212.4170.0 > > RayG >
