On 9/21/23 03:12, Simon Perry wrote:
If you're actively blocking outbound to Hetzner ranges then that is a YOU
problem.
No, outbound was fine, it was the INPUT chain block from the 95.216 ranges
that got me. I have a top-100 script that dumps the address ranges with the
top 100 blocked invali
On 9/21/23 02:38, Lone_Wolf wrote:
Did you have keyring issues before the archlinux-keyring package was
created/added ?
If not , you can disable the timer - like I have done - by executing (as root)
sysctl mask archlinux-keyring-wkd-sync.timer
No,
I didn't have any issues with the keyring
On 2023-09-21 09:52 AM, David C. Rankin wrote:
You helped greatly with your model nftables.conf! Thank you! Things
worked great. I used that to find out how to do the same thing in
iptables.
The problem is Archlinux now uses Hetzner as the cloud provider with
most of the Arch IPs falling
On 21-09-2023 01:52, David C. Rankin wrote:
archlinux-keyring-wkd-sync flies under the RADAR on install as a
dependent package whose service file is automatically. Rather than the
user having to do something more to ensure archlinux-keyring-wkd-sync
can run,
archlinux-keyring-wkd-sync uses
