@MSGID: 1:266/625 bfa3f612
@REPLY: 2:250/5 71729cb9
@TID: Mystic BBS 1.12 A48
@TZUTC: -0400
On 02 Jul 2024, Christian Sacks said the following...
 CS> I think on the whole this is a nice approach, however what happens when
 CS> Mystic accidentally blacklists your own IP, or it`self? Then you have
 CS> iptables blocking you out and you won`t be able to get back in =)

 Understood, and Mystic already has a solution built-in. Just be sure
to add the addresses you commonly connect from to the
mystic/data/allowlist.txt; that way the system will never lock you out. And, if you are
using the 4 connections in 120 secs suggested setting, the likelihood of
locking yourself out is pretty small. (unless of course your are testing
ssh settings and you keep trying options that fail..., ask me how I
know?!? :) )

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: <=-{ The Digital Post }-=> (1:266/625)
SEEN-BY: 1/120 10/0 1 18/0 50/109 90/1 102/401
103/1 705 105/81 106/201
SEEN-BY: 116/116 120/616 123/0 10 25 180 200 525
755 1185 3001 124/5009 5016
SEEN-BY: 128/260 129/12 102 125 160 165 215 305
328 135/115 153/757 7715
SEEN-BY: 154/10 30 50 700 203/0 214/22 218/0 1
215 601 700 720 810 840 850
SEEN-BY: 218/860 870 880 930 940 220/6 90 221/0
6 222/2 226/30 50 70 227/114
SEEN-BY: 229/110 111 112 113 206 275 300 307 310
317 400 426 428 470 550 664
SEEN-BY: 229/700 240/1120 1120 5832 250/1 261/1
220 266/75 215 512 618 625
SEEN-BY: 267/152 154 275/1000 280/464 5003 282/1038
291/111 292/854 8125
SEEN-BY: 301/1 1 320/219 322/757 341/66 234
342/200 396/45 423/120 460/58
SEEN-BY: 467/888 633/280 712/848 1321 770/1
2320/105 3634/0 12 27 56 57 58
SEEN-BY: 3634/119 5000/111 5001/100 5005/49 5019/40
5020/329 400 715 830 848
SEEN-BY: 5020/1042 4441 12000 5030/49 1081 5053/51
5054/8 5061/133 5075/35
SEEN-BY: 5075/128 5083/1 444
@PATH: 266/625 512 229/426 218/700 103/705 280/464
154/10 3634/12 5020/1042
@PATH: 5020/4441