| |
N2NOV > SYSOP 10.03.20 09:55l 19 Lines 699 Bytes #999 (0) @ WW
BID : 73405_N2NOV
Read: GUEST
Subj: Re: AmprNet DDoS attack
Path: IZ3LSV<IR2UBX<IW2OHX<IR1UAW<I0OJJ<EA2RCF<LU9DCE<LU3DVN<LU9HGS<LU1HVK<
N7HPX<KF5JRV<NS2B<N2NOV
Sent: 200309/1603z @:N2NOV.#RICH.NY.USA.NOAM [NYC] [JNOS] #:73407 $:73405_N2NOV
>From n2nov@n2nov.ampr.org Mon Mar 9 11:03:52 2020
Received: from n2nov.ampr.org by n2nov.ampr.org ([JNOS]) with SMTP
id AA973407 ; Mon, 09 Mar 2020 11:03:52 EDT
Message-Id: <973405@n2nov.ampr.org>
>From: n2nov@n2nov.ampr.org
X-JNOS-User-Port: Telnet (n2nov @ 44.68.41.2) -> Sending message
I noticed this the other day and wound up setting up my JNOS to TCP ACCESS DENY
the entire 1/0 network and only TCP ACCESS ALLOW those IP addresses that I knew.
Months ago it was just the Far East IP addresses causing a major headache, but
now it is wider and I have to adjust things. I already lock out every unknown
at the server level, but now I had to do it at the encap level. Oh well!
Read previous mail | Read next mail
| |
