> AFAICT the important fact is that the route to 114.23.164.222 has lo0 in the
> Interface column meaning (according to the manual page) that lo0 will be
> used to reach that IP address. In your case, wg0 will be used, which means
> the packet will be transmitted over WireGuard to the remote end.
This is an automatically generated notice of a new failure of the
NetBSD test suite.
The newly failing test case is:
usr.bin/nbperf/t_nbperf:bpz
The above test failed in each of the last 4 test runs, and passed in
at least 26 consecutive runs before that.
The following commits were made
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2023.07.31.17.41.18.
An extract from the build.sh output follows:
36 | if (IOCTL_##rq != IOCTL_NOT_PRESENT) {
Taylor R Campbell writes:
>> Date: Sun, 30 Jul 2023 14:56:53 -0400
>> From: Brad Spencer
>>
>> Taylor R Campbell writes:
>>
>> > Can you please try running with the attached patch and share the
>> > warnings it produces? Should give slightly more information.
>>
>> Caught another one. As
