I thought I had fail2ban in place... It turns out I did, but when I
moved to HAPROXY I broke it. It bypasses the telnet daemon
altogether so no fail2ban action.

It turns out I've been saving the BBS from some level of hammering
by only allowing HAPROXY 2 concurrent logins shared amongst 8 BBS
nodes. Once I noticed that and cranked it up to 8, all of a sudden
I have all nodes busy and HAPROXY sucking its thumb trying to talk
to busy ports.

SO, to try and save re-inventing the wheel, has anyone setup
fail2ban to run on the HAPROXY log or get a decent log out of it actually, it �seems highly resistant to wanting to connection log for me.

I think my short term answer will be to turn concurrent connections
down a bit again, but it would be nice to get to 1:1

Spec


--- SuperBBS v1.17-3 (Eval)
* Origin: (21:3/101)