TZUTC: -0500
MSGID: 14175.dove-sync_sys@723:320/1 2cd15fbb
REPLY: 58297.sync_sys@1:103/705 2cd11378
PID: Synchronet 3.20a-Linux master/acc19483f Apr 26 202 GCC 12.2.0
TID: SBBSecho 3.28-Linux master/e2705e616 Jul 05 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: CP437 2
FORMAT: flowed
> I just opened my ports for telnet and ssh from the internet to Sync through
my
> router, and instantly it started getting hit with jokers running scripts
tryin
> to get in.  Crazy how fast these things hit.  I only have four nodes, but
it's
> constantly tying up the first two.  I guess this is the new normal?  I have
> OpenSSH setup on a non standard port, but I bet it's only time before this
get
> found too.

When I had my SSH set to the standard port, it got hammered the hardest --
a lot more than the telnet port.  My telnet port is still standard and yes,
it does get hit pretty regular, but not usually enough to tie all the nodes up
like the SSH port did.

Yes, that is the new normal.  With synchronet, it will put temp bands on
IPAs if you get too many hits from the same one, and you can add IPAs or
ranges into the ip-silent.can file if you notice some that are nothing but
trouble makers.  That has helped a lot here.


 * SLMR 2.1a * Spelling is a sober man's game
---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 1/19 16/0 19/37 103/13 705 105/81 106/201 123/130 124/5016
SEEN-BY: 128/187 129/14 142/104 153/757 7715 154/10 30 110 203/0 218/700
SEEN-BY: 221/0 1 6 226/30 227/114 229/110 206 317 400 426 428 550
SEEN-BY: 229/700 705 240/1120 5832 263/1 266/512 280/464 5003 5006
SEEN-BY: 291/111 292/8125 301/1 320/119 219 319 2119 322/757 762 326/101
SEEN-BY: 341/66 234 342/200 396/45 423/81 120 460/58 467/888 633/280
SEEN-BY: 712/848 770/1 902/26 5020/400 5075/35
PATH: 103/705 280/464 221/1 320/219 229/426