Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Fr 09.08.2024 00:00:16 61.977 -1 3.617.019 58,4 Fosstodon 4.2.10 500 Do 08.08.2024 00:00:21 61.978 +1 3.614.789 58,3 Fosstodon 4.2.10 500 Mi 07.08.2024 00:00:08 61.977 +2 3.611.687 58,3 Fosstodon 4.2.10 500 Di 06.08.2024 00:00:37 61.975 +4 3.608.594 58,2 Fosstodon 4.2.10 500 Mo 05.08.2024 00:00:05 61.971 +5 3.606.116 58,2 Fosstodon 4.2.10 500 So 04.08.2024 00:00:02 61.966 +2 3.604.482 58,2 Fosstodon 4.2.10 500 Sa 03.08.2024 00:00:05 61.964 -2 3.602.552 58,1 Fosstodon 4.2.10 500 Fr 02.08.2024 00:00:23 61.966 -4 3.599.813 58,1 Fosstodon 4.2.10 500 Do 01.08.2024 00:01:11 61.970 +3 3.596.601 58,0 Fosstodon 4.2.10 500 Mi 31.07.2024 00:00:00 61.967 0 3.593.593 58,0 Fosstodon 4.2.10 500
Peter van Dijk (@habbie) · 11/2022 · Tröts: 540 · Folger: 391
Fr 09.08.2024 23:40
Guess who just spent an hour debugging all the wrong things because 0.0.0.0/24 (wireguard allowed ips) does NOT match any of the IPs he was trying to ping.
It's me, hi. I'm the problem, it's me.
ping did manage to emit "ping: sendmsg: Required key not available" which, in hindsight, is absolutely the right message (wireguard uses allowedIPs to pick the right key, if I understand correctly), and now I'm wondering whether ENOKEY existed before Wireguard.
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0