Re: [Cerowrt-devel] Turning off the probe blocker

[Jim Gettys <jg@freedesktop.org>]

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

On Thu, Jul 11, 2013 at 1:40 PM, Dave Taht <dave.taht@gmail.com> wrote:

> 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...
>

Very cool.

What frequency is smoke ping probing at?  This is tunable, you know.

It's also possible to configure smokeping to report from multiple probing
locations, and have the rollup on a central web site; I dunno if you had
come across that in your adventures.

Jim

>
> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

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