Re: Why can't a WireGuard interface route packets to itself?

2023-07-30 Thread Lloyd Parkes
PPPoE is a point to point protocol and the public IP addresses 114.23.17.255 and 114.23.164.222 are normal IP addresses. 114.23.164.222 is my local IP address and 114.23.17.255 is my ISP's IP address. Both can be treated as /32. AFAICT the important fact is that the route to 114.23.164.222 has

Re: Why can't a WireGuard interface route packets to itself?

2023-07-30 Thread logothesia
> Beware of possible line wrapping. No problem :) > DestinationGatewayFlagsRefs UseMtu > 114.23.17.255 114.23.164.222 UH -- - pppoe0 > 114.23.164.222 pppoe0 UHl -- - lo0 10/8 10.0

Re: Why can't a WireGuard interface route packets to itself?

2023-07-30 Thread Lloyd Parkes
On 31/07/23 02:18, logothesia wrote: Hi folks, I have a very simple WG network with only two machines: 10.0.0.1 (NetBSD), and 10.0.0.2 (linux). Indeed they can ping each other just fine, but attempting to ping 10.0.0.1 from itself yields the following error: % ping 10.0.0.1 PING 10.0.0.1 (10

Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"

2023-07-30 Thread Taylor R Campbell
> 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 far as I know the system is up to date

Re: What to do about "WARNING: negative runtime; monotonic clock has gone backwards"

2023-07-30 Thread 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 far as I know the system is up to date with all of the requested patches: [ 19419.647972] WARNING: lwp 16 (system

Re: i386/openssl on amd64?

2023-07-30 Thread Martin Husemann
On Sun, Jul 30, 2023 at 03:18:32PM +0200, Jan-Hinrich Fessel wrote: > Oh yes: > build.sh command:./build.sh -U -j 2 -M /usr/obj -O /usr/obj -R > /usr/src/releasedir.NetBSD-10.99.6-amd64 -D > /usr/obj/destdir.NetBSD-10.99.6-amd64 -X /usr/xsrc -x -V MKCOMPAT=no release > install-image > > so,

Why can't a WireGuard interface route packets to itself?

2023-07-30 Thread logothesia
Hi folks, I have a very simple WG network with only two machines: 10.0.0.1 (NetBSD), and 10.0.0.2 (linux). Indeed they can ping each other just fine, but attempting to ping 10.0.0.1 from itself yields the following error: % ping 10.0.0.1 PING 10.0.0.1 (10.0.0.1): 56 data bytes ping: sendto: No ro

Re: i386/openssl on amd64?

2023-07-30 Thread Martin Husemann
On Sun, Jul 30, 2023 at 10:05:15AM +0200, Jan-Hinrich Fessel wrote: > Hej there, > > tried that on several fresh installations now with src grabbed via cvs > checkout. No one else seeing this? > I am somewhat lost in how to fix this apart from modifying the source list > (md.amd64 that would be

Re: i386/openssl on amd64?

2023-07-30 Thread Jan-Hinrich Fessel
Hej there, tried that on several fresh installations now with src grabbed via cvs checkout. No one else seeing this? I am somewhat lost in how to fix this apart from modifying the source list (md.amd64 that would be) because i see there: grep openssl lists/base/md.amd64 ./usr/lib/i386/openssl