AKM and archlinux.org (another DDoS attack)

General system Pacman & AUR helpers
1

I use AKM to manage my kernels and over the past couple of days I noticed it was unable to connect to archlinux.

Screenshot_20251226_205043
Screenshot_20251226_205043572×493 76.5 KB

Sadly it turns out our pals over at Arch are under attack again. :pensive_face:

2

Lucky me

ping archlinux.org
PING archlinux.org (2a01:4f9:c013:e0e4::1) 56 data bytes
64 bytes from 2a01:4f9:c013:e0e4::1: icmp_seq=1 ttl=52 time=43.1 ms
64 bytes from 2a01:4f9:c013:e0e4::1: icmp_seq=2 ttl=52 time=40.6 ms
64 bytes from 2a01:4f9:c013:e0e4::1: icmp_seq=3 ttl=52 time=33.7 ms
64 bytes from 2a01:4f9:c013:e0e4::1: icmp_seq=4 ttl=52 time=34.0 ms
^C
--- archlinux.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 33.682/37.833/43.136/4.113 ms
3

Here too, I have ipv6 working :shushing_face:

4

I found out the hard way that my PoS TP-Link router doesn’t work with my ISP and IPv6.

5

IPv4 seems to be working on my end:


ping -4 archlinux.org 
PING archlinux.org (46.62.254.168) 56(84) bytes of data.
64 bytes from archlinux.org (46.62.254.168): icmp_seq=1 ttl=52 time=35.3 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=2 ttl=52 time=38.0 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=3 ttl=52 time=37.6 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=4 ttl=52 time=37.7 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=5 ttl=52 time=37.6 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=6 ttl=52 time=35.6 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=7 ttl=52 time=37.8 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=8 ttl=52 time=37.6 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=9 ttl=52 time=37.5 ms
64 bytes from archlinux.org (46.62.254.168): icmp_seq=10 ttl=52 time=38.2 ms
^C
--- archlinux.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 35.336/37.290/38.210/0.939 ms