Our project status bot has been fixed and is back in operation!
https://status.furrix.zone/status/furrix-stats
Category: Network
Post dealing with changes to how we route packets and configure our network.
I have got the PTR zone setup for 2602:f992:e0::/44 done and loaded into both servers. Reverse DNS lookups will now work for our /44, but be aware that this network isn’t yet completely deployed, so there will be missing records for the time being.
You can check if you are curious by running the command “nslookup -q=ptr 2602:f992:e0::” which should get you an answer with “0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.e.0.0.2.9.9.f.2.0.6.2.ip6.arpa name = 0e.299f.2062.kc.mo.us.furrix.zone”
Just a quick little update on the NMP and our routing stack, we are now dropping traffic from known TOR exit nodes using a public list that is automatically updated once a day. Started seeing a bit of traffic from a few nodes, so went ahead and set this up.
It looks like the amplification attack has let up, so the NOC has restored IPv4 service to IP blocks in the region. We will be keeping an eye on the situation and will reinstate the geoblock if the attack starts up again.