On 2019 Jun 21 09:38:06, you wrote to me:
the line given above is not the "bad actor"... it is an example only...
plus the "bad actor" is hosted on a cloud network that provides VMs...
i don't want to block the whole thing because i know that some other
BBS operators are on the same network... that's why i've chosen to
grab the IPs and add them to my block list...
Ah, fair enough... most of the blocking I do tends to be "Oh, Russia? China? buh-bye..."
yeah, i do that in smaller blocks as needed depending on the attack/probe being
seen...
Were you able to get the log management sorted to your liking?
yup! it is a lot easier now to grab the domain and IP together and split them out...
sudo zgrep -E -e "^.* sestar sbbs: .*Hostname: .*BADACTORDOMAINHERE.* \
\[([0-9]{1,3}[\.]){3}[0-9]{1,3}\]" /var/log/syslog* | \
cut -d "[" -f 2 | cut -d "]" -f 1 | sort -V | uniq
that'll walk through all your syslogs, live and archived, find the BADACTORDOMAIN matches and then cut out everything except the IPs which come out in a nice sorted list...
before i was having to use -B1 on the grep line to get the line before the match and then cross my fingers that it was the line with the IP but that was a
crapshoot since the logging may have lines from other sbbs services mixed and interleaved... this new format means i won't miss any anymore :)
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Happy Holidays and a Wonderful 2009 to you and yours!
---
* Origin: (1:3634/12.73)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net