fail2ban filter for coturn #1379
Replies: 3 comments
-
Hi @un99known99 |
Beta Was this translation helpful? Give feedback.
-
@eakraly 52973: : IPv4. tcp or tls connected to: 91.148.190.158:35466 which are not my calling clients. Currently trying to get them out via fail2ban Any other proposals, am I using the right traces in the logfile? |
Beta Was this translation helpful? Give feedback.
-
@eakraly "311963: : IPv4. tcp or tls connected to: 45.227.254.49:65158" is that the appropriate way? |
Beta Was this translation helpful? Give feedback.
-
Hi,
are there suggestions, on how coturn can be protected by fail2ban?
I can see often entries like
720: : session 001000000000000003: delete: realm=<turn.example.com>, username=<1705345356>
720: : session 001000000000000004: usage: realm=<turn.example.com>, username=<1705345356>, rp=5, rb=200, sp=5, sb=404
720: : session 001000000000000004: peer usage: realm=<turn.example.com>, username=<1705345356>, rp=0, rb=0, sp=0, sb=0
720: : session 001000000000000004: closed (2nd stage), user <1705345356> realm <turn.example.com> origin <>, local 0.0.0.0:8346, remote 177.5.226.23:1486, reason: allocation timeout
720: : session 001000000000000004: delete: realm=<turn.example.com>, username=<1705345356>
nagging my system.
Thanks in advance.
BR,
Mike
Beta Was this translation helpful? Give feedback.
All reactions