Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Maciej Soltysiak <maciej@soltysiak.com>
To: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] blocking probes...
Date: Mon, 28 Jan 2013 19:49:36 +0100	[thread overview]
Message-ID: <CAMZR1YDvbtAdBja80BRWQ8URwV=-+dQYAkNDGS0TUNSCEM0ujA@mail.gmail.com> (raw)
In-Reply-To: <51069CCE.4010504@etorok.net>

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

I've said it before and I'll say it again:
iptables -I zone_wan -j DROP
And if you really need access from wan INSERT a rule before that DROP.

Regards,
Maciej


On Mon, Jan 28, 2013 at 4:44 PM, Török Edwin <edwin+ml-cerowrt@etorok.net>wrote:

> On 01/13/2013 11:15 AM, Török Edwin wrote:
> > 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
>
> With 3.7.4 I see these now on my home router, so its definetely working:
> root@OpenWrt:~# logread|grep xinetd|grep Adding|wc -l
> 20
>
> The IPs are from Russia, Peru, Colombia, Egypt, UK, Kuwait, Turkey,
> Azerbaijan.
>
>
> Best regards,
> --Edwin
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 2297 bytes --]

  reply	other threads:[~2013-01-28 18:49 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
2013-01-28 15:44   ` Török Edwin
2013-01-28 18:49     ` Maciej Soltysiak [this message]
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='CAMZR1YDvbtAdBja80BRWQ8URwV=-+dQYAkNDGS0TUNSCEM0ujA@mail.gmail.com' \
    --to=maciej@soltysiak.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=edwin+ml-cerowrt@etorok.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