From: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] blocking probes...
Date: Sun, 13 Jan 2013 11:15:32 +0200 [thread overview]
Message-ID: <50F27B34.503@etorok.net> (raw)
In-Reply-To: <CAA93jw6uY8P0RUMsdGsAHmWSXYu5tsxf1VCpFUT96NFCEn2ZbA@mail.gmail.com>
On 01/13/2013 06:50 AM, Dave Taht wrote:
> one of the underused features of cerowrt is that I stuck a sensor on
> xinetd to detect attempts to telnet or ftp to the router and cut off
> access to some other services, notably ssh.
I don't see this on my cerowrt, is this only in the 3.7.x series?
>
> I would have loved to extend this facility to either do it entirely in
> iptables or leverage xinetd to talk to iptables to (for example)
> disable access to the web server.
>
> I'm curious if anyone elses server logs ever show something like this
> in the Real World:
>
> Jan 12 20:44:02 europa daemon.crit xinetd[3273]: 3273 {process_sensor}
> Adding 190.185.12.121 to the global_no_access list for 120 minutes
>
> And I'm curious as to what more fully blown tools like this already exist.
>
I'm using fail2ban on my server (not the router), and see between 2-7 of these bans/day:
Jan 13 03:34:28 sshd[22392]: Did not receive identification string from 83.231.93.133
Jan 13 04:03:05 sshd[23167]: Invalid user delta from 83.231.93.133
Jan 13 04:03:05 sshd[23170]: Invalid user admin from 83.231.93.133
2013-01-13 04:03:06,376 fail2ban.actions: WARNING [ssh] Ban 83.231.93.133
2013-01-13 07:47:21,738 fail2ban.actions: WARNING [ssh] Unban 66.135.32.170
--Edwin
next prev parent reply other threads:[~2013-01-13 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 4:50 Dave Taht
2013-01-13 5:01 ` Sebastian Moeller
2013-01-13 9:15 ` Török Edwin [this message]
2013-01-28 15:44 ` Török Edwin
2013-01-28 18:49 ` Maciej Soltysiak
2013-01-13 20:22 ` Michael Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50F27B34.503@etorok.net \
--to=edwin+ml-cerowrt@etorok.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox