Assp will interpret this '173.213.70.6527' as '173.213.70.65' - a single
IP. How should I know what you want to do - defining a CIDR missing the
slash or writing a comment missing the space ?
because of the large number of possible options, it is impossible to do a
sanity check - for example:
Thomas,
While processing a message, ASSP version 2.2.2(13110) stopped responding
on all ports. The tail of the log contained:
13-Apr-23 08:12:14 [Worker_3] Info: enhanced Originated IP detection
ignored IP's: 69.252.76.7
13-Apr-23 08:12:14 [Worker_3] Info: enhanced Originated IP detection
Thomas,
ASSP version 2.2.2(13110) stopped responding on all ports. The tail of
the log contained:
13-Apr-23 18:34:01 [Main_Thread] Admin connection from user root on host
208.69.48.2:64570; page:/; session-ID:ae759af75cbc3c364a5c4906d6348ab1;
13-Apr-23 18:34:01 [Main_Thread] Adminupdate: [root
Do you use BerkeleyDB for the temporary hashes ? If yes:
- stop assp
- clean the 'tmpDB' folder
- remove all 'griplist' related files from the assp root folder
- start assp
This is the second request I got about this - I'll try to fix this in the
next version. Seems there is a possible deadlock
