5 May
2014
5 May
'14
10:46 a.m.
Hey folks,
Last week at the meeting we talked a bunch about the necessity of
getting some basic node monitoring/error reporting up. Chris J mentioned
that NRPE w/ an Icinga (nagios fork) monitor server would be a
potentially quick and easy way to bootstrap some basic reporting. Alex
said that he was going to try to install the openWRT NRPE package on a
node and try to get a monitor server build receiving info from that test
node.
Are there any status updates on this? Alex, I realized I don't have your
email, so this is kind of my overly-public way of getting in touch. I
have some time this week to work on this, but I thought I'd check in to
see where other folks were at to prevent any duplication of efforts.
Also, I realized that if you need github write access, I can provide you
with that.
Awesome - keep on meshin!
Max
5 May
5 May
10:59 a.m.
On 05/05/14 14:46, Max B wrote:
Hey folks,
Last week at the meeting we talked a bunch about the necessity of
getting some basic node monitoring/error reporting up. Chris J mentioned
that NRPE w/ an Icinga (nagios fork) monitor server would be a
potentially quick and easy way to bootstrap some basic reporting. Alex
said that he was going to try to install the openWRT NRPE package on a
node and try to get a monitor server build receiving info from that test
node.
we've been having a great experience so far with observium, it works
surprisingly well considering it works over SNMP (!) (*_*)
and the setup is absurdly dead simple, after deploying the server with
LAMP and a 5-min cronjob, all it needs is
for host in {ham,spam,egg}.domain.com ; do ./add_node.php $host ; done
and it will autodiscover everything by itself.
there's also an "agent" of some sort that runs on the monitored hosts,
that would also need some openwrt-makefile-love AFAIR
have you considered that possibility?
cheers!
http://status.deltalibre.org.ar/
http://status.quintanalibre.org.ar/
Are there any status updates on this? Alex, I realized I don't have your
email, so this is kind of my overly-public way of getting in touch. I
have some time this week to work on this, but I thought I'd check in to
see where other folks were at to prevent any duplication of efforts.
Also, I realized that if you need github write access, I can provide you
with that.
Awesome - keep on meshin!
Max
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
11:15 a.m.
We're open to all possibilities! In fact, wlan slovenija has been
working on a project Nodewatcher
https://dev.wlan-si.net/wiki/Nodewatcher for a while now that we'd
ultimately love to just use out of the box (more or less). It just
doesn't seem quite ready yet and we're more and more realizing that we
need something sooner than later that can just tell us if the nodes are
up and able to route peoplesopen.net traffic out to the internet. I
think NRPE is relatively similar to SNMP (I need to understand the
protocols better...), and I believe there's already an openwrt package
for NRPE clients, so we'll just have to see what we can do...
On Mon 05 May 2014 10:59:30 AM PDT, Gui Iribarren wrote:
On 05/05/14 14:46, Max B wrote:
Hey folks,
Last week at the meeting we talked a bunch about the necessity of
getting some basic node monitoring/error reporting up. Chris J mentioned
that NRPE w/ an Icinga (nagios fork) monitor server would be a
potentially quick and easy way to bootstrap some basic reporting. Alex
said that he was going to try to install the openWRT NRPE package on a
node and try to get a monitor server build receiving info from that test
node.
we've been having a great experience so far with observium, it works
surprisingly well considering it works over SNMP (!) (*_*)
and the setup is absurdly dead simple, after deploying the server with
LAMP and a 5-min cronjob, all it needs is
for host in {ham,spam,egg}.domain.com ; do ./add_node.php $host ; done
and it will autodiscover everything by itself.
there's also an "agent" of some sort that runs on the monitored hosts,
that would also need some openwrt-makefile-love AFAIR
have you considered that possibility?
cheers!
http://status.deltalibre.org.ar/
http://status.quintanalibre.org.ar/
Are there any status updates on this? Alex, I realized I don't have your
email, so this is kind of my overly-public way of getting in touch. I
have some time this week to work on this, but I thought I'd check in to
see where other folks were at to prevent any duplication of efforts.
Also, I realized that if you need github write access, I can provide you
with that.
Awesome - keep on meshin!
Max
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh 
8:59 p.m.
Hey all,
So I've been messing around with the collectd daemon, which
I think will work quite well for collecting statistics from the mesh
nodes.
Specifically, I was able to set up two copies of the daemon
and have a "client" (a PicoStation) transmit data to a "server"
(my laptop), which stores the data in RRD files (circular
databases of time-series data). From there, there appear
to be many tools that can produce pretty graphics (cacti,
cricket, drraw), but I haven't really explored this too much.
It is easy to set up and pretty lightweight and I believe it can
also be made to scale rather well. I didn't find a BATMAN module,
but there is one for OLSR which we could pillage. It uses a push
model (clients initiate the sending of data), which might be a good
fit for a decentralized network.
If we go this route we're going to need a machine on the mesh
running a web server that receives the RRD data from all the
nodes (and optionally syslog data).
Alex
On 05/05/2014 10:46 AM, Max B wrote:
Hey folks,
Last week at the meeting we talked a bunch about the necessity of
getting some basic node monitoring/error reporting up. Chris J mentioned
that NRPE w/ an Icinga (nagios fork) monitor server would be a
potentially quick and easy way to bootstrap some basic reporting. Alex
said that he was going to try to install the openWRT NRPE package on a
node and try to get a monitor server build receiving info from that test
node.
Are there any status updates on this? Alex, I realized I don't have your
email, so this is kind of my overly-public way of getting in touch. I
have some time this week to work on this, but I thought I'd check in to
see where other folks were at to prevent any duplication of efforts.
Also, I realized that if you need github write access, I can provide you
with that.
Awesome - keep on meshin!
Max
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
16 May
16 May
2:05 a.m.
On Mon, May 5, 2014 at 8:59 PM, Alexander Papazoglou <papazoga(a)gmail.com>wrote;wrote:
Hey all,
So I've been messing around with the collectd daemon, which
I think will work quite well for collecting statistics from the mesh
nodes.
Specifically, I was able to set up two copies of the daemon
and have a "client" (a PicoStation) transmit data to a "server"
(my laptop), which stores the data in RRD files (circular
databases of time-series data). From there, there appear
to be many tools that can produce pretty graphics (cacti,
cricket, drraw), but I haven't really explored this too much.
It is easy to set up and pretty lightweight and I believe it can
also be made to scale rather well. I didn't find a BATMAN module,
but there is one for OLSR which we could pillage. It uses a push
model (clients initiate the sending of data), which might be a good
fit for a decentralized network.
If we go this route we're going to need a machine on the mesh
running a web server that receives the RRD data from all the
nodes (and optionally syslog data).
Looks pretty good. I'll try to set it up on a node. I also ordered a couple
of microcontrollers with microsd card slots that we can hook up to the
serial interface on nodes to log crashes.
Alex
On 05/05/2014 10:46 AM, Max B wrote:
Hey folks,
Last week at the meeting we talked a bunch about the necessity of
getting some basic node monitoring/error reporting up. Chris J mentioned
that NRPE w/ an Icinga (nagios fork) monitor server would be a
potentially quick and easy way to bootstrap some basic reporting. Alex
said that he was going to try to install the openWRT NRPE package on a
node and try to get a monitor server build receiving info from that test
node.
Are there any status updates on this? Alex, I realized I don't have your
email, so this is kind of my overly-public way of getting in touch. I
have some time this week to work on this, but I thought I'd check in to
see where other folks were at to prevent any duplication of efforts.
Also, I realized that if you need github write access, I can provide you
with that.
Awesome - keep on meshin!
Max
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
7:06 p.m.
Sorry I've been of little help only attending a few meetings. I've been working on
finishing touches to a gift economy web page.
One aspect I'm trying to build on is a peer sharing feature that allows a shared gift
service (eg internet) to be easily duplicated and reviewed by peers, users who would like
to be notified of similar services based on keywords can opt in. There is also mapping
features.
The main issue is promoting the service while privacy and net neutrality is being struck
down.
So my question is: can we load balance, efficiently route traffic, and provide tor on the
back end to multiple uplinks - ie business line t1's, sonic and other sharable
connections.
I think this would be a good way to promote what many users want.
This would be pursued under Creative Commons/Sweat Equity provisions unless someone has a
better idea?
Mario
On May 16, 2014, at 2:05 AM, Marc Juul
<juul(a)labitat.dk> wrote:
On Mon, May 5, 2014 at 8:59 PM, Alexander
Papazoglou <papazoga(a)gmail.com> wrote:
Hey all,
So I've been messing around with the collectd daemon, which
I think will work quite well for collecting statistics from the mesh
nodes.
Specifically, I was able to set up two copies of the daemon
and have a "client" (a PicoStation) transmit data to a "server"
(my laptop), which stores the data in RRD files (circular
databases of time-series data). From there, there appear
to be many tools that can produce pretty graphics (cacti,
cricket, drraw), but I haven't really explored this too much.
It is easy to set up and pretty lightweight and I believe it can
also be made to scale rather well. I didn't find a BATMAN module,
but there is one for OLSR which we could pillage. It uses a push
model (clients initiate the sending of data), which might be a good
fit for a decentralized network.
If we go this route we're going to need a machine on the mesh
running a web server that receives the RRD data from all the
nodes (and optionally syslog data).
Looks pretty good. I'll try to set it up on a node. I also ordered a couple of
microcontrollers with microsd card slots that we can hook up to the serial interface on
nodes to log crashes.
Alex
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh On 05/05/2014 10:46 AM, Max B wrote:
Hey folks,
Last week at the meeting we talked a bunch about the necessity of
getting some basic node monitoring/error reporting up. Chris J mentioned
that NRPE w/ an Icinga (nagios fork) monitor server would be a
potentially quick and easy way to bootstrap some basic reporting. Alex
said that he was going to try to install the openWRT NRPE package on a
node and try to get a monitor server build receiving info from that test
node.
Are there any status updates on this? Alex, I realized I don't have your
email, so this is kind of my overly-public way of getting in touch. I
have some time this week to work on this, but I thought I'd check in to
see where other folks were at to prevent any duplication of efforts.
Also, I realized that if you need github write access, I can provide you
with that.
Awesome - keep on meshin!
Max
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/mesh
3664
days inactive
3676
days old
5 comments
5 participants
participants (5)
-
Alexander Papazoglou -
Gui Iribarren -
Marc Juul -
Max B -
tropical rain