Hi guys!
Thanks for publish us on your calendar! (I just saw it)
https://sudoroom.org/events/sudo-mesh-wifi-hack-night-2014-09-18/
But please add two things:
We're two: "Griselda and Al" and we're going to speak about guifi.net
itself and a data center we're building on core of guifi.net optic fiber
(and please add URL http://marsupi.org/barrahome/en/ ).
This new project is a cooperative data center for the people. Is based
on data can be accessible 100% across free community mesh network
managed by the people, without NSA surveillance (and also, of course,
accessible in the whole internet). So here we're getting in touch with
projects that wants to collaborate in making it real hosting here.
In some days we're going to launch a crowd funding campaign :)
...and if you want to know something concrete about guifi.net project,
please you can say us before in order to prepare a dedicated time in our
speech, 'cos is a very big project and we can focus more in protocols,
antennas, management, installations, routers, maps, organization, bands,...
See you on Thursday!
Howdy mesh crew -
I've sort have been out of commission for the past month or so and was
wondering if the Tuesday mesh meetups were still happening. If so, will
anyone be around tonight? If not I will see you all Thursday.
Dan
Howdy mesh crew -
I've sort have been out of commission for the past month or so and was
wondering if the Tuesday mesh meetups were still happening. If so, will
anyone be around tonight? If not I will see you all Thursday.
Dan
Want to have our own networked radiation monitoring station? The Global
Radiation Monitoring Network is looking to add nodes to their network
<http://www.uradmonitor.com/join-the-network/>.
They only have two dozen or so nodes around the world so far, and none in
California. "In this early phase of the project, there is only a minimal,
non-profit cost, to cover the hardware components used and the shipping."
The nodes are weatherproofed, and only need 5V power and an ethernet cable.
Is this something that could potentially be piggy-backed on to the sudo
mesh nodes as well? One of their node models has a barometric pressure
sensor as well. Not sure to what extent this is an open source project, but
we could find out.
They were just featured as one of the semifinalists for the Hackaday prize
<http://hackaday.com/2014/09/11/global-radiation-monitoring-network-update/>,
so I expect they'll be getting an influx of new node requests...
Patrik
here's the text translated from the attached HTML:
Hi all,
There is a small, urgent gig in the next few days for an activist
organization fighting climate change.
Pay is about $1000, and needs to be ready for Sep 8th.
It involves the following:
We need a DD-WRT router to be configured to serve a captive portal (our
static campaign page) *without* a WAN connection. We can supply the router.
We need you to configure it. Specifically: Installing and configuring a
lightweight web server on the router (lighttpd seems to work) to host our
page. Configuring the router's firewall to forward all incoming
requests on ports 80 and 443 to the web server. Configuring the
router's DNS and DHCP handling to redirect requests back to the router.
This thread should offer useful guidance for someone who's skilled on
the UNIX command line.
That's the basics.
Useful bells and whistles include logging how many users see the page, and
configuring the web server to (securely) log entries to a form on the page
(our campaign petition).
Contact Brant Olson with any interest - brant(a)engagementlab.org
4115-596-6581.
Thanks all,
--
Aaron Lifshin | CTO
Mayday PAC c: (857) 231-6921
--
You received this message because you are subscribed to the Google Groups
"H4D Hack for Democracy" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hackfordemocracy+unsubscribe(a)googlegroups.com.
To post to this group, send email to hackfordemocracy(a)googlegroups.com.
Visit this group at http://groups.google.com/group/hackfordemocracy.
For more options, visit https://groups.google.com/d/optout.
---------- Forwarded message ----------
From: Danny Spitzberg <stationaery(a)gmail.com>
Date: Thu, Sep 4, 2014 at 7:00 PM
Subject: [sudo-discuss] Fwd: [H4D] Router configuration gig
To: sudo-discuss <sudo-discuss(a)lists.sudoroom.org>
Passing along a good opportunity with good folks!
---------- Forwarded message ----------
From: Aaron Lifshin <aaron(a)mayday.us>
Date: Thu, Sep 4, 2014 at 9:05 PM
Subject: [H4D] Router configuration gig
To: "H4D Hack for Democracy <hackfordemocracy(a)googlegroups.com>" <
hackfordemocracy(a)googlegroups.com>
>
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/sudo-discuss
Hey all,
What do ya'll think about setting up a couple of development VPSs from the
sudo mesh budget?
I'd like to go for one or two of something like this:
- http://www.ftpit.com/
- ~$2 / mo for (either)
- 2 CPU Core | 512 MB RAM | 30 GB Storage | 1 TB Bandwidth | 1
IPv4 | OpenVZ & SolusVM
- 2 CPU Core | 512 MB RAM | 20 GB Storage (SSD) | 1 TB Bandwidth |
1 IPv4 | OpenVZ & SolusVM
I'm putting some attention in on the exitnode provisioning (and therefore
server provisioning in general).
I was thinking about setting up some in-person machines at sudo room for
developer training, development environments, testing before deployment,
etc. Marc pointed out that the power consumption of such a machine would
probably not be worth it given the low cost of a VPS. However, I still want
to streamline the process for facilitating new developers to build a
smaller version of peoplesopen.net network, and to provide testing
infrastructure to maintain reliability and up-time.
I updated this page on the wiki, please contribute:
https://sudoroom.org/wiki/Virtual_Private_Server
// Matt
made some minor updates, cleanup:
https://github.com/sudomesh/exitnode/pull/1
Next steps:
* Configure & deploay a sample exitnode for testing
* Also configure a test node (2.4ghz wireless device)
* Perform tests to verify system functions, use for testing before
deploying to live server.
* Configure such a system at sudo room for regular usage
// Matt
