27 Sep
2021
27 Sep
'21
4:02 a.m.
Yes it would be worthwile to research (with the IP address as information) what could
be the reason behind this. Assuming it was not 44.0.0.1 but some amateur's IP, it
could
be some retaliation against that person and they may be able to identify a likely source
and legal action may be possible.
Aside from that, I think there is too little headroom on this connection and it needs
to be upgraded to 10Gbit or some teamed 1Gbit links when that is more practical.
The background noise already takes up 650Mbit/s of the 1Gbit/s available...
Rob
On 9/27/21 9:33 AM, Marius Petrescu via 44Net wrote:
Tnx. Chris for the update.
I'm still wondering what the goal of such an attack is...
On 27/09/2021 10:30, Chris Smith via 44Net wrote:
So, it was a TCP port 80 attack directed against
one IP address.
I passed this on to my contacts at CAIDA who passed it onto the UCSD NOC who have got the
IP blocked.
The traffic has now returned to normal.
Chris - G1FEF
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net