Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] blocking probes...
Date: Sun, 13 Jan 2013 15:22:00 -0500	[thread overview]
Message-ID: <1893.1358108520@sandelman.ca> (raw)
In-Reply-To: <CAA93jw6uY8P0RUMsdGsAHmWSXYu5tsxf1VCpFUT96NFCEn2ZbA@mail.gmail.com>


>>>>> "Dave" == Dave Taht <dave.taht@gmail.com> writes:
    Dave> one of the underused features of cerowrt is that I stuck a sensor on
    Dave> xinetd to detect attempts to telnet or ftp to the router and cut off
    Dave> access to some other services, notably ssh.

    Dave> I would have loved to extend this facility to either do it
    Dave> entirely in 
    Dave> iptables or leverage xinetd to talk to iptables to (for example)
    Dave> disable access to the web server.

I didn't know that was there... what version does it start?
I get lots of probes... can I run this detector on port-22 (on the
outside) as well?

With the 3800s having dried up, I'm now really concerned... what if my
device blows up?  and I've got nothing to experiment with.

I was planning to buy more in the new year (now), but I didn't do it
fast enough.  Given that they have dried up now, I'm thinking that I
need to go back and replace my 3800 with something else that can run
cerowrt, or at least can run the QOS scripts.   
I am not happy running my firewall as a VM, but I certainly could do
that... 

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	





      parent reply	other threads:[~2013-01-13 20:22 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
2013-01-13 20:22 ` Michael Richardson [this message]

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=1893.1358108520@sandelman.ca \
    --to=mcr@sandelman.ca \
    --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