Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Richard A. Smith" <richard@laptop.org>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Turning off the probe blocker
Date: Thu, 11 Jul 2013 10:40:50 -0700	[thread overview]
Message-ID: <CAA93jw4dqqnDBx-hh7FOr7UoKR_64pC_AJe=P6fQkw9SK58ZHQ@mail.gmail.com> (raw)
In-Reply-To: <51DEEC00.801@laptop.org>

I incidentally got smokeping up and running on a beaglebone black to
monitor latencies better across the whole network at the yurtlab. For
those of you with ipv6, it's currently globally reachable:

http://monitor.lab.taht.net/cgi-bin/smokeping.cgi?target=Campground-5ghz-Radios

There are numerous options (like traceroute, etc) to put into
smokeping, which I'd like to add but haven't wrapped my head around.
Can't get fastcgi to work with it on lighttpd, either.

I have mrtg running on a pi, too, that I will move over to the blacks.
Also have the nifty babelweb utility running on the pi - but the pi
just doesn't have the oomph (nor does it has fq_codel) to do much
more, so...

I had really once hoped to make cerowrt "do everything", but the black
+ debian makes doing "everything" a lot easier when you can easily run
perl and python...

The monitor box is running over a minimum of 3 hops right now before
running across the rest of the mesh network.

... just wish the beaglebone black had a case I could wallmount with
screws rather than velcro...

On Thu, Jul 11, 2013 at 10:31 AM, Richard A. Smith <richard@laptop.org> wrote:
> On 07/11/2013 01:00 PM, Dave Taht wrote:
>>
>> On Thu, Jul 11, 2013 at 9:42 AM, Richard A. Smith <richard@laptop.org>
>> wrote:
>>>
>>> How to I disable the probe blocker?  I'm trying to do some port
>>> forwarding
>>> and every time I nmap my box trying to figure out if its working I get
>>> banned from ssh for 2 hours.
>>
>>
>> Heh. See the relevant telnet (and ftp, I think) entries in
>> /etc/xinetd.d and change them to disable = yes. You can probably do
>> this at a finer grained basis
>
>
> Thanks.  I'll mess with that once I have local access again.
>
>
> --
> Richard A. Smith  <richard@laptop.org>
> One Laptop per Child



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2013-07-11 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 16:42 Richard A. Smith
2013-07-11 17:00 ` Dave Taht
2013-07-11 17:31   ` Richard A. Smith
2013-07-11 17:40     ` Dave Taht [this message]
2013-07-11 18:27       ` Jim Gettys
2013-07-11 18:41         ` Dave Taht
2013-07-11 19:46           ` Robert Bradley
2013-07-11 20:18             ` Dave Taht

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='CAA93jw4dqqnDBx-hh7FOr7UoKR_64pC_AJe=P6fQkw9SK58ZHQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richard@laptop.org \
    /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