disable TCP-FASTOPEN

Wed May 31 16:40:48 UTC 2017

Am 31.05.2017 um 14:15 schrieb A. Schulze via Unbound-users:

>> Below is a patch, but I don't know if it works, it makes the code fallthrough
>> to try normal TCP writes when FASTOPEN writes fail.
> 
> I'll try the patch and report results...

compiled and installed but no change.

...
2017-05-31 18:36:16.868823500 [1496248576] unbound[22766:0] error: tcp writev: Broken pipe for 2001:310:6000:f::1fc7:1
2017-05-31 18:36:16.874287500 [1496248576] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:161:3ec::53
2017-05-31 18:36:17.143379500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 203.137.119.119
2017-05-31 18:36:17.405554500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 203.137.119.119
2017-05-31 18:36:17.411117500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:161:3ec::53
2017-05-31 18:36:17.416440500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:150:1095::53
2017-05-31 18:36:17.422345500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:150:1095::53
2017-05-31 18:36:17.422347500 [1496248577] unbound[22766:0] info: Missing DNSKEY RRset in response to DNSKEY query.
2017-05-31 18:36:17.422348500 [1496248577] unbound[22766:0] info: Missing DNSKEY RRset in response to DNSKEY query.
2017-05-31 18:36:17.422349500 [1496248577] unbound[22766:0] info: Missing DNSKEY RRset in response to DNSKEY query.
2017-05-31 18:36:17.422351500 [1496248577] unbound[22766:0] info: Missing DNSKEY RRset in response to DNSKEY query.
2017-05-31 18:36:17.422360500 [1496248577] unbound[22766:0] info: Missing DNSKEY RRset in response to DNSKEY query.
2017-05-31 18:36:17.422361500 [1496248577] unbound[22766:0] info: Missing DNSKEY RRset in response to DNSKEY query.
2017-05-31 18:36:17.422363500 [1496248577] unbound[22766:0] info: Could not establish a chain of trust to keys for kernel-error.com. DNSKEY IN
2017-05-31 18:36:17.422364500 [1496248577] unbound[22766:0] info: validation failure <kernel-error.com. MX IN>: No DNSKEY record for key kernel-error.com. while building chain of trust
2017-05-31 18:36:17.422368500 [1496248577] unbound[22766:0] info: ::1 kernel-error.com. MX IN SERVFAIL 16.122824 0 34
2017-05-31 18:36:17.422369500 [1496248577] unbound[22766:0] info: Could not establish a chain of trust to keys for kernel-error.com. DNSKEY IN
2017-05-31 18:36:17.422376500 [1496248577] unbound[22766:0] info: validation failure <kernel-error.com. MX IN>: No DNSKEY record for key kernel-error.com. while building chain of trust
2017-05-31 18:36:17.422378500 [1496248577] unbound[22766:0] info: ::1 kernel-error.com. MX IN SERVFAIL 16.979449 0 34
2017-05-31 18:36:17.422379500 [1496248577] unbound[22766:0] info: resolving kernel-error.com. DNSKEY IN
2017-05-31 18:36:17.671634500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2001:310:6000:f::1fc7:1
2017-05-31 18:36:17.677029500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:150:1095::53
2017-05-31 18:36:17.682693500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:161:3ec::53
2017-05-31 18:36:17.682694500 [1496248577] unbound[22766:0] info: Capsforid: timeouts, starting fallback
2017-05-31 18:36:17.687988500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:150:1095::53
2017-05-31 18:36:17.693575500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 176.9.109.53
2017-05-31 18:36:17.699173500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 176.9.109.53
2017-05-31 18:36:17.704899500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:161:3ec::53
2017-05-31 18:36:17.710267500 [1496248577] unbound[22766:0] error: tcp writev: Broken pipe for 2a01:4f8:161:3ec::53
...

I just also set "use-caps-for-id: no" to exclude that but (this time expected) no change.

Andreas