Subj : Telnet Ringdown server
To   : Dumas Walker
From : AKAcastor
Date : Thu Feb 29 2024 20:53:12

 DW> One thing I noticed is that if I manually add an address to ringdown.ban 
 DW> and then start ringdown, the dat data
 DW> appears to get emptied out and I am able to connect 
 DW> from the banned address.

 DW> Is this the expected behavior?  

Updated version of ringdown (0.53) on github is now a bit friendlier about reading lines added to ringdown.ban, and also allows for permanent bans.

Also new, ringdown will count the # of times a banned IP attempts to connect (the fourth column in ringdown.ban - connect_attempts).  It doesn't currently do anything with this data but it is saved for us in ringdown.ban.


From README.md:

Entries can be added to ringdown.ban, it is not necessary to include the second, third, or fourth columns if you want to set them all to 0 (permanent ban).  If ringdown.ban is modified while ringdown is running, the change will be detected and new entries in the ban list will be recognized.  Note that ringdown will rewrite ringdown.ban any time a banned IP attempts to connect, be aware of conditions where the file may change while open for editing.

To add a (permanent) ban of 192.168.1.246, you might use:

echo 192.168.1.246 >> ringdown.ban


Chris/akacastor

--- Maximus 3.01
 * Origin: Another Millennium - Canada - another.tel (21:1/162)

.