Recorded for posterity at: https://sudoroom.org/wiki/Mesh/28_March_2017
Log of most meeting minutes at: https://sudoroom.org/wiki/Mesh/Minutes
*People's Open Network** - **25 March 2017*
= really quick intros =
* jorrit: I have worked on this thing called babeld-lab. It's a way to
create a mesh network on a single laptop so you can play around with it
easily. So if you have any questions about it please ask Grant. I'm
interested in helping myself getting more familiar with the mesh network by
writing documentation.
* juul: works on firmware dev, ask about low-level stuff. working on a map
that allows the nodes to automap themselves. all projects on
github.com/sudomesh
* andy: i hack on things and make agendas sometimes :)
* mark: work at a coop bike shop in berkeley and matt senate was trying to
set up a mesh node there and encountered a bunch of resistance so is here
to learn more about it. is excited to learn more about mesh networks.
* daniel: no-se on IRC, worked on sudomesh for a long time
* eve: i work at berkeley lab. an IT drone. I'm interested because i think
it's useful and i might learn something.
* jenny: i've been working on peoplesopen.net stuff since the beginning
days and wants to get back into it after working on omni commons
bureaucracy for awhile
* grant: working on mesh for a few months - working on babeld lab if you
have any questions. good place to learn about the mesh, so start there if
you're new! also working on guides for new people w/ jorrit. interested in
firmware & wardriving stuff
* jehan: been working on a dashboard which is almost done, been
procrastinating. working on a model of batman routing protocol in Go,
trying to modify it to give accurate info about routes even when data is
inaccurate.
* patrick - here from santa cruz, electrical engineering student. here to
learn more about networking and interested in starting a project down
there... and beyond..
* arthur: still relatively new. just trying to help out where i can. learn
something new every meeting
= announcements =
* collaboration: Marin Public Library, CCA (California College of the Arts)
** jenny will send an email to Ivan and will cc no-se
* byoi follow-up email
** eve circulated a draft of a promo for the next one
** jorrit: let's have an email huddle around the chess table after the
meeting
* status of guides and intro
** jorrit: jenny did some editing of the guide and i was thinking we just
promote it to the front page of the wiki - "what are we doing and how can
you help and what are our guiding principles": learn, build, teach, improve
** no-se: i can help with that
** jenny: website is on the github if anyone wants to hack on it:
https://github.com/sudomesh/peoplesopen-front
* AS numbers and internet exchanges
** jehan: a friend recommended that we look at sfmix (an SF internet
exchange) and you can basically buy bandwidth from them. they have a data
center. You need an ASN which you get from ARIN.
** some more info @ http://ieeexplore.ieee.org/document/4438278
** juul: as an isp can have your own range of IPs, and some for free in the
IPv6 range... tho hurricane electric also would allow us to have an ipv6
range even without an asm number
** jnny: did a bit of research on exemption issues w/ ISPs last week w/
Kyle (sudo's former lawyer) - need to do more research -
https://www.irs.gov/pub/irs-tege/eotopicc99.pdf
** jehan - if you're an AS you're considered to be running your own tube,
whereas if we go through hurricane we're using their tubes
** juul - can get our internet from hurricane which is hard, or run our vpn
through it.
*** jehan - sfmix is same price for vpn as hurricane
** jehan - issue was re: shutdowns from psychz re: torrenting?
*** juul: not getting those anymore
**** jnny: evan moved...
* Inventory security: status of gate project
** eve: we did measurements... i was going to present prices. HD sells
these panels that are 6x4 for $70, panels with a gate?
*** juul: should we spend the donations from the workshop on this?
** eve: is 6' high enough?
*** andy: if there's barbed wire on top
** eve: will send an email to the list with specs
** jorrit: cheaper to get a closet?
** eve: chain-link fence panel
** juul: human filter
** eve: just to the left of the door.. probably a couple hundred dollars.
*** jnny: can probably scavenge some or all of the materials..
* Planning for annual board meeting
** Date & Time: 3 weeks - April 18th, 7:30pm
** Objectives: nominate & consense on new board members, file annual mtg
minutes, overview of basic gov filings and related; decide on future org
structure (eg; submit 501c3 app?). Most topics can be covered over email -
the meeting is to formally consense / rubber stamp formal decisions
*** Grant: what are the responsibilities of board members?
**** jenny: primarily to sign board resolutions - there are some possible
liability issues - we don't have directors&officers insurance - so if you
have a shit-ton of assets to protect you may not want to be on the board
(can be a benefactor instead ;)
* Presentation on Working Groups proposal: Andy
** Discussion: (andy) most people are here every week. we just had this
workshop which gave a good model for how to bring in people and raise
awareness. and if you look at the political situation there are a lot of
people who are interested in privacy/security and people who are interested
in joining in a project like this. currently the project isn't really
useful to most people and most people don't understand what it is. We have
an opportunity to take this project to another level. To install nodes in
libraries and schools and make relationships and turn this into something
that people use and find value in. And provide an alternative to ISPs, NSA,
etc. I'm not proposing a rigid hierarchy.
** Andy proposes making 3 working groups: installation, infrastructure, and
communications
** jorrit: To me this is not just about making an alternative to a thing.
It's also about making awareness/education around what this internet thing
really is. One of the things we talked about is making this project more
inclusive. And one thing I think is important is no longer using the term
"non-technical people". we need not just techies. we need community
organizers, social engineers, teachers - we need everyone! don't reduce
them to "non-technical people"
** jorrit - most of us work on all three aspects -
** arthur: can hand someone a node who's new, at any given meeting,
important. super easy way to get people on board
*** jenny: last tuesday of the month for new members, so that wg could
focus there
*** jorrit: think everyone should be part of that committee
** juul: what does it mean to be part of a wg?
*** andy: up to the group. firmware hacking could be tues nights, node
installs on sunday afternoons, comms could choose a separate monthly time.
mainly choose someone who could commit to that particular area. installing
nodes - who will facilitate that? facilitate meetings, avenues of
communication
* juul: maybe sunday afternoon could become a secondary meeting - secondary
time for wtvr working group - whoever facilitates could suggest the
upcoming sunday for firmware hacking / node install / etc
** Nomination / volunteering of WG leads
* jorrit nominates grant for education / support / orientation crew
* arthur - would prefer to have a mentor ** eve, ditto
* jehan: been working on the dashboard for awhile, come here @5pm before
the meeting. almost done, need to hook it up to shell scripts in the
backend.
** jnny - could be good to set firmware/software hacking nights at 5 before
the meeting
* jehan - would take lead on frontend stuff
* jenny: jorrit / grant / jenny maybe co-facilitate comms wg?
** grant - beyond intro'ing new people and giving them a pre-flashed node,
cultivating folks who will become local organizers in their own right
* Map
** juul: approx 40 people online, not sure how many are sharing bandwidth
or meshing. working on it. currently hooking up a couple of houses in w
oakland - maybe 5 or 6?
* NPR interview
** juul did a few days ago. also going to be distributed in written form,
should expect some media attention soon.
* New nodes mounted
** two more nodes mounted in w oakland
* We found the outdoor cable again!
* We should have a system that detects IP collisions (can babel tell us?)
* Secret meeting agenda point
* policy around node distribution?
** ask for $20-30 donation
** will flash them for free
** can't just give away all of them, but we did get about ~30 donated
** jehan: prioritize people who are in line of sight?
*** jorrit: i'm here bc i have a node at home - tho an island, learning via
it
** marc: policy generally is to prioritize those who seem really engaged
** andy: $20 is a good threshold
** jenny: could ask $20 suggested donation, $30 if you want to make a node
available to someone who can't afford it for free
** mark: ask could be some sort of work-trade
** juul: have to show up to 2 meetings before you can get your free node
*** jorrit: that or drive all the way from santa cruz..
** daniel: important to let them know the value of each router - eg $60
router for $20 donation, or sliding scale from 20 to 60. also email addy
for tech support.
*** jorrit - or at the next meeting, when you show up and ask people.
= updates =
== updates from juul ==
The official point of contact for the mesh is now info(a)peoplesopen.net so
if you think people aren't interested in joining the mailing list, please
tell them to email that address. If you want to be one of the people who
receive email on info(a)peoplesopen.net then please send an email stating as
much to info(a)peoplesopen.net but please be aware that any email received
there is considered PRIVATE and as such should not be forwarded in part or
in full to the mesh mailing list or posted anywhere in public.
Lately we've had a few people pop into #peoplesopen.net and ask a question
and leave before anyone could answer. I'd love for more people to hang out
in that channel. IRC cloud is a way to do this but if you're comfortable
with a command line and have an always-on server then I suggest running
weechat in a screen. I finally set the channel to greet new people with the
following message: Hello and welcome to the People's Open Network chat.
Feel free to ask questions but please realize that most of are busy, so it
may take hours to get a response. If you aren't planning on hanging around
for that long we suggest sending an email to info(a)peoplesopen.net or
joining our mailing list https://sudoroom.org/lists/listinfo/mesh
The secrets server, which is needed to configure new nodes with makenode,
is now working again but its hostname has changed to secrets.peoplesopen.net.
Remember to run `git pull` in the makenode directory before you use
makenode again. I'm working to switch us over to a minimal configuration
system that will allow us to pre-configure nodes the way Will had been
doing and simply saving the contact info and address in the node database
when we hand them out. It is not a big change so it shouldn't take more
than a few weeks to get it done (i just need a single free weekend day).
jorrit discovered that the free StartCom SSL certs are causing trouble on
some computers so we switched makenode to a letsencrypt cert. We also got a
report on twitter that bleeding edge developer builds of firefox take issue
with the ssl cert on peoplesopen.net, which is also a StartCom cert. We
should stop using StartCom certs.
= breakout sesh's =
* emails out (jorrit / eve / jenny)
* new folks (visitor from santa cruz)
* q&a w/ marc, jehan, grant
* Mark: pci compliance issues @ bike shop
= action items =
* jenny send announcement re: board meeting
= next meeting =
* discuss practicalities of acquiring bandwidth
* tubes - how do they work?
* return to working groups proposal & nomination of wg leads
--
Jenny
Help open a people-powered common space in Oakland, California!
https://omnicommons.org/donate
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson
"Storytelling reveals meaning without committing the error of defining it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
On Wed, Mar 29, 2017 at 7:32 AM, Will Martin <will(a)willmartin.com> wrote:
> Andy, thanks for the proposed work groups - I think these are a great way
> to break it up. Talk with Jenny - she says the meetings used to be broken
> up into a monthly "public" meeting and weekly private meetings.
>
Technically, we still advert (and I still tell new folks) that the last
Tuesdays of the month are general public meetings geared more toward
newbies. Do we want to continue this format?
Throughout 2015, Tuesdays were comms/organizing meetings, Thursdays were
firmware hack nights, and Sunday afternoons were scheduled node installs.
One thing we discussed last night was reserving Sunday afternoons as
'second meetups' - whether they be a firmware hack sesh, a node install, or
a comms/outreach meeting.
> *Here are some ideas for metrics to keep track of based on those work
> groups:*
>
> - *Installation:*
> -
> - Keep a running chart of # of nodes on the network like on
> Guifi.net
> - Keep an updated map on peoplesopen.net showing all of the nodes
> and links
> - *Infrastructure:*
> -
> - Keep a running chart of network uptime % over the last month (as
> measured from the exit node)
> - Put a development roadmap on the blog and update it quarterly
> - *Communications:*
> -
> - Keep track of # of interested new node owners - people who click
> "I want to host a node"
> - Keep track of website traffic and "conversion" to node owners
> -
> - Maybe do A/B testing on peoplesopen.net to with the goal of
> getting people signed up
> - Keep track of social media metrics: # of followers on twitter,
> instagram, facebook
>
> On point to think of metrics! Should we set up an instagram? Was curious
if there was anything on there and found this
https://copysta.com/profile/sudomesh/2334861621/ :D
Just set up a Passpack account for account/password management. lmk if you
want access (will send login info to the Signal group shortly)
> If this is the road we go down I'd be happy to volunteer either as the
> Installation or Communications lead.
>
You'd be great at either!
<3
jnny
On Tue, Mar 28, 2017 at 8:25 PM <mesh-request(a)lists.sudoroom.org> wrote:
>
>> Send mesh mailing list submissions to
>> mesh(a)lists.sudoroom.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://sudoroom.org/lists/listinfo/mesh
>> or, via email, send a message with subject or body 'help' to
>> mesh-request(a)lists.sudoroom.org
>>
>> You can reach the person managing the list at
>> mesh-owner(a)lists.sudoroom.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of mesh digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Working Groups proposal (Andrew Dollard)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Tue, 28 Mar 2017 20:25:16 -0700
>> From: Andrew Dollard <andrewdollard(a)gmail.com>
>> To: mesh(a)lists.sudoroom.org
>> Subject: [Mesh] Working Groups proposal
>> Message-ID: <39A7539A-2EC4-4470-8AD4-D440504014B0(a)gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> A non-text attachment was scrubbed...
>> Name: peoples_open_working_groups.pdf
>> Type: application/pdf
>> Size: 721772 bytes
>> Desc: not available
>> URL: <http://sudoroom.org/pipermail/mesh/attachments/
>> 20170328/395a5326/attachment.pdf>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> mesh mailing list
>> mesh(a)lists.sudoroom.org
>> https://sudoroom.org/lists/listinfo/mesh
>>
>>
>> ------------------------------
>>
>> End of mesh Digest, Vol 50, Issue 25
>> ************************************
>>
>
> _______________________________________________
> mesh mailing list
> mesh(a)lists.sudoroom.org
> https://sudoroom.org/lists/listinfo/mesh
>
>
Dear Sir/Madam,
I am working on a project named - Secure Commissioning(Joining) In Ad Hoc WiFi MESH Networks. I find Sudo MESH as a good platform to implement my project.
I read the documentation of Sudo MESH. But I have doubts. Please help me in clarifying my doubts.
My doubts are :
1. How is the joining of new routers (nodes) to existing MESH network of routers made secure. Is there any key exchange and authentication during the joining process.
2. Understanding document for completely understanding the source code implementation of Sudo MESH.
I want to understand the complete implementation of Sudo MESH functionality and especially from a security perspective. After that I can contribute to make the MESH network more secure. I have good coding skill sets.
When I understand the document well, I can contribute to SudoMESH for preparing good documentation of the implemented MESH network so that interested users/readers will be more benefited.
Looking forward to your help and cooperation.
Thanks and Regards,
Sritam Paltasingh.
Sunday April 26th at 1:35 pm pacific:
"Last year, we thought the FCC was going to ban our operating system. Has
anything changed? As it turns out, plenty. Eric Schultz, one of the leaders
of the Save Wifi Initiative, highlights the changing interests by the FCC
on free software. He’ll also discuss his efforts participating as part of
the FCC’s Technical Advisory Council, Software Configurable Radio sub-group
to advocate for software freedom. Finally, he will detail specific ways in
which we can educate regulators on the benefits of free software-based
wireless and protect user freedom."
Live Stream:
https://libreplanet.org/2017/live/
--
marc/juul
Unsubscribe
Sent from my iPhone
> On Mar 23, 2017, at 1:47 AM, mesh-request(a)lists.sudoroom.org wrote:
>
> Send mesh mailing list submissions to
> mesh(a)lists.sudoroom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://sudoroom.org/lists/listinfo/mesh
> or, via email, send a message with subject or body 'help' to
> mesh-request(a)lists.sudoroom.org
>
> You can reach the person managing the list at
> mesh-owner(a)lists.sudoroom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mesh digest..."
>
>
> Today's Topics:
>
> 1. Re: Google Summer of Code 2017 (Mitar)
> 2. Build Your Own Internet! workshop this Saturday, 1-4pm @ Omni
> Commons (Jenny Ryan)
> 3. Re: Signup for mesh workshop stations (Jenny Ryan)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 16 Mar 2017 02:08:22 -0700
> From: Mitar <mitar(a)tnode.com>
> To: mesh(a)lists.sudoroom.org
> Subject: Re: [Mesh] Google Summer of Code 2017
> Message-ID: <77ade897-e61a-60c1-192f-054ca909a448(a)tnode.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi!
>
> Yes, apply! GSoC is a great way to work on mesh things, and get payed
> for it. You have to be a student though.
>
> I can also mentor you locally, in Bay Area, if you prefer that.
>
> BTW, there are also some mesh related projects for Rocket.Chat:
>
> https://rocket.chat/docs/contributing/google-summer-of-code/#rocket-chat-on…
> https://rocket.chat/docs/contributing/google-summer-of-code/#automatic-chan…
>
>
> Mitar
>
>> Hi everybody,
>>
>> my name is Federico Capoano and I am a contributor of OpenWISP.org (a
>> software project aimed at making it easy to deploy and manage wifi
>> networks) and Ninux.org (an Italian wireless community). Some of you
>> have met me when I came to California in 2014 and at the battlemesh v8
>> in Slovenia.
>>
>> I'm writing here to inform you that these projects are participating to
>> the Google Summer of Code 2017 and there are many opportunities for
>> university grade students to do paid work on open source software
>> related to mesh networking.
>>
>> At these URLs you can find the proposed project ideas:
>>
>> OpenWISP: http://openwisp.org/gsoc/ideas-2017.html
>>
>> Ninux is participating with Freifunk, together with many other
>> organizations (Guifi, Wlan Slovenia, Libremesh, ecc.):
>> https://wiki.freifunk.net/Ideas
>>
>> If you know any student that may be interested, let them know!
>>
>> Thanks
>> Federico
>>
>> _______________________________________________
>> mesh mailing list
>> mesh(a)lists.sudoroom.org
>> https://sudoroom.org/lists/listinfo/mesh
>
> --
> http://mitar.tnode.com/
> https://twitter.com/mitar_m
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 16 Mar 2017 18:32:09 -0700
> From: Jenny Ryan <tunabananas(a)gmail.com>
> To: "mesh(a)lists.sudoroom.org" <mesh(a)lists.sudoroom.org>, sudo-discuss
> <sudo-discuss(a)lists.sudoroom.org>, "discuss(a)lists.omnicommons.org"
> <discuss(a)lists.omnicommons.org>, Noisebridge
> <noisebridge-discuss(a)lists.noisebridge.net>,
> liberationtech(a)lists.stanford.edu, The Spaghetti Night mailing list
> <spaghettinight(a)tentacle.net>, Occupy Oakland List
> <occupyoakland(a)lists.riseup.net>
> Subject: [Mesh] Build Your Own Internet! workshop this Saturday, 1-4pm
> @ Omni Commons
> Message-ID:
> <CAF0yFe5A8rB1fURjnYbss8FUJOeQJHxtoLMWmdTV2TuxBdghJA(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Greetings,
>
> The Peoples Open Network is hosting a skillshare / workshop this Saturday,
> March 18, from 1-4pm at the Omni Commons (home of the Sudo Room
> hackerspace), and we'd love for you to join us!
>
>> From the event page
> <https://www.eventbrite.com/e/build-your-own-internet-workshop-tickets-32460…>
> (plz rsvp so we know how many folks to expect!):
>
> Do you think internet should be a public commons rather than a corporate
> monopoly?
>
> Come over to Omni Commons to learn about the history of the internet, how
> it works, and how to build your own. Meet and mingle with civic hackers and
> organizers behind peoplesopen.net: an open, community-based, network in the
> East Bay.
> Agenda:
>
> 1:00pm - Why/what/how of the internet (< 30 minutes)
>
> 1:30pm - Snack, mingle, share and experiment
>
> 2:00pm - Hands-on workshop with a variety of learning stations such as:
> rooftop mounting techniques, ethernet cable-crimping, live node link
> demoing radio propagation, q&a table & non-tech signup station for
> neighborhood organizers
>
> Donations for pizza and internet are enthusiastically accepted ; )
>
> The Omni Commons' ballroom is wheelchair-accessible via a lift in the
> Entrance Hall, where there is also located a wheelchair-accessible
> single-stall bathroom.
>
> The Peoples Open Network <https://peoplesopen.net> enables anyone to share
> their Internet connection or extend signal from neighboring nodes. Learn
> more at peoplesopen.net.
>
> The Omni Commons <https://omnicommons.org> is a 100% volunteer-run space
> for community organizing, collaboration, and creative production located in
> North Oakland. Learn more at omnicommons.org.
>
> *BYOI Workshop *
>
> *Omni Commons - Ballroom*
>
> *4799 Shattuck, Oakland, California*
>
> *Saturday 18 March 2017 1-4pm*
>
>
> *RSVP at
> https://www.eventbrite.com/e/build-your-own-internet-workshop-tickets-32460…
> <https://www.eventbrite.com/e/build-your-own-internet-workshop-tickets-32460…>
> !*
> --
> Jenny
>
> Help open a people-powered common space in Oakland, California!
> https://omnicommons.org/donate
>
> `~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
> "Technology is the campfire around which we tell our stories."
> -Laurie Anderson
>
> "Storytelling reveals meaning without committing the error of defining it."
> -Hannah Arendt
>
> "To define is to kill. To suggest is to create."
> -Stéphane Mallarmé
> ~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
>
guess sudo's mailman server ran into a bug, so now we are getting all the
mailz.
but this is the last one for mesh, i think.
Jenny
Help open a people-powered common space in Oakland, California!
https://omnicommons.org/donate
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson
"Storytelling reveals meaning without committing the error of defining it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
---------- Forwarded message ----------
From: Paltasingh, S. <s.paltasingh(a)student.tue.nl>
Date: Tue, Mar 21, 2017 at 9:01 AM
Subject: [sudo-info] Ad Hoc MESH WiFi Networks
To: "info(a)sudoroom.org" <info(a)sudoroom.org>
Dear Sir/Madam,
I am working on a project named - Secure Commissioning(Joining) In Ad Hoc
WiFi MESH Networks. I find Sudo MESH as a good platform to implement my
project.
I read the documentation of Sudo MESH. But I have doubts. Please help me in
clarifying my doubts.
My doubts are :
1. How is the joining of new routers (nodes) to existing MESH network of
routers made secure. Is there any key exchange and authentication during
the joining process.
2. Understanding document for completely understanding the source code
implementation of Sudo MESH.
I want to understand the complete implementation of Sudo MESH functionality
and especially from a security perspective. After that I can contribute to
make the MESH network more secure. I have good coding skill sets.
Looking forward to your help and cooperation.
Thanks and Regards,
Sritam Paltasingh.
_______________________________________________
Info mailing list
Info(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/info
---------- Forwarded message ----------
From: Alan Hamlett <alan.hamlett(a)gmail.com>
Date: Thu, Mar 16, 2017 at 9:40 PM
Subject: [sudo-info] intro meeting re dogpatch node
To: info(a)sudoroom.org
Would like to join the network, but would need a long-range connection
since no peoplesopen.net access points nearby (dogpatch). Should we come to
this Saturday's 1pm meeting?
--
Alan Hamlett
ahamlett.com
_______________________________________________
Info mailing list
Info(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/info
