Sudo Room - User contributions [en]

Mesh/Minutes

2018-08-08T05:59:14Z

Bengo: add 8/7

<center>'''Sudo Mesh Meeting Minutes'''</center>

<DynamicPageList>
category = Mesh/Minutes
order = descending
</DynamicPageList>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/07 August 2018

2018-08-08T05:58:00Z

Bengo: add august 7 notes. We didn't scribe much.... there were lots of new people who learned about the meeting from the Saturday conference (aweomse!) and a reporter so we had a more informal q&a.

'''People's Open Network Weekly Meeting - 7 August 2018 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

* Last Meeting Minutes aren't published, but should be here: https://sudoroom.org/wiki/Mesh/31_July_2018

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Discussion Z (15 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcement

Marc
Benny
Cassidy: went on sat and am intrigued
Brenna: she her, hanging out with cassidy and imtrigird
Bengo: he him. They them. Been coming for 6 months starting to figure things out.
Celine: kalw. Doing story. Chatted with jenny. Lovd to talk to anyone from project. Found out from mushroom workshop
Devon: came for cyber wizard institute. Came back because been in blockchain world. Good to be around
Null: net sec web sec. Live on boat. Js hw hack.
Tina: new. She her they them. Built priv p2p messaging system
Ten

NOTE: This meeting was mostly explaining the projects to new people since we had lots of new people, a reporter from KALW and only three people from the projects.

=== Meeting Roles ===
* Facilitator/s:
* Stacktaker:
* Timekeeper:
* Notetaker/s:
** URL of this pad: https://peoplesopen.net/notes

Juul Spield
=====
* marc: meeting is sudomesh. Meetings usually about peoplesopen.net, which is one of the projects we work on. Disaster.radio is another project that is newer and also cool.
peoples open network has been going for several years. and is about building lsat-mile infrastructure for people to build and own their own internet infrastructure. we use long range wireless links--directional gear mounted on rooftops.

* We use a mesh routing protocol called babel. And we use an open linux distribution for routers called OpenWRT. We have a fork of that called sudowrt-firmware, which is what we run on our routers. It tries to make these a bit easier, e.g. there is a web dashboard that shows off what your router is doing and connected to.
Firmware lets you share a slice of your internet connection publicly for your neighbors to benefit from. This way only one house on your block needs line-of-sight to another neighborhood, and the other houses can link through that one to the res tof the mesh.
These routers all show a 'peoplesopen.net' wifi network.

...

ten: East Oakland has lots of good community-owned warehouses that could be good
guifi - similar, bigger, network in Barcelona

Open Q&A
======

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and past action items below:
*

== Updates & Reportbacks ==
=== Bugs/Technical ===
Priority bugs we need help with are located at: http://peoplesopen.net/helpwanted - For a high-level overview of recent Github activity, see the Trello: https://trello.com/invite/b/r9l5ouQ4/3b2eecd83bb9e7a57a339cf1ee038288/sudo-mesh-github-repos
*

Software WG Announcements (bengo + benny today)
* bengo: shout out to bennie for organizing to make Software WG happen today
* We fixed peoplesopen.net/notes (by deleting and recreating the pad) https://github.com/sudomesh/bugs/issues/38
* `curl "https://peoplesopen.net/pad/api/1/deletePad?apikey=$apikey&padID=notes"`
* apikey is in ssh://peoplesopen.net:/opt/etherpad/local/etherpad/etherpad-lite/APIKEY.txt
* https://github.com/sudomesh/exitnode/pull/14
* merged!
* followup work identified: https://github.com/sudomesh/exitnode/issues/17
* Bug #33
* moved from "Ready for Review" to "Done".
* Bennie is knowledgeable about some good followup work. We created exitnode #16 test bug #33. https://github.com/sudomesh/exitnode/issues/16
* monitor/#23 https://github.com/sudomesh/monitor/pull/23
* Closed issue. It's good code but for the wrong repo. Should consider it for sudowrt-firmware.
* Might make sense for https://github.com/sudomesh/sudowrt-firmware/issues/144
* https://github.com/sudomesh/meshnode-database/pull/8
* merged it!
* bug 34
* 'travis.yml' column is all green https://github.com/sudomesh/bugs/issues/34#issue-322457296

* Grant made some sudowrt-firmware local builds more than 1000% faster! https://github.com/sudomesh/sudowrt-firmware/issues/137
* bengo: Amazing work. Will you please open a PR next time so we can follow along instead of committing directly to master?

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
*

== Next Sunday ==
=== Node Mount ===
We try to arrange a rooftop node mount every Sunday afternoon. Ongoing spreadsheet is located at: https://peoplesopen.net/sundays
* Next Sunday's mount:

=== Office Hours ===
We host office hours every Sunday from 1-2pm in Sudo Room. To sign up for a shift, fill in your name here: https://ethercalc.org/byoi_office_hours
* Next Sunday's volunteer:
* Notes from this past Sunday's session:

== Example Proposal ==
Please add any proposal needing consent from or action by the group below:
*
* '''Consenso?'''

== Example Discussion Item ==
*

== Action Items ==
*

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* link to previous meeting minutes

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/DD_MM_YYYY
* then please erase the contents of this pad
* then please cut & paste a blank template from here: https://sudoroom.org/mediawiki/index.php?title=Mesh/Mesh_Meeting_Notes_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/10 July 2018

2018-07-11T18:11:53Z

Bengo: Created page with "'''People's Open Network Weekly Meeting - 10 July 2018 7:30pm-9pm''' * https://omnicommons.org/wiki/Safer_Space_Policy === Agenda === * Introductions and Meeting Roles (10 mi..."

'''People's Open Network Weekly Meeting - 10 July 2018 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Proposal: Stale Issues Bot https://github.com/sudomesh/projects/issues/2 (10min)
* Proposal: Reimbursements for conference registrations
* Next Sunday (5 mins)
* Discussion: BYOI / Decentralized Web Summit Unconference (15 mins)
* Discussion: Brainstorm best ways to improve peoplesopen-monitor (15 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: What's your favorite Danish thing?
* bengo - they/them or he/him - My favorite dutch thing is "going dutch."
** isn't that a dutch thing?
*** dane - It's a dutch thing.
****
* marc - he/him - all the free education
* seth - he/him/they - fleas and lice - old band from Holland. I think they're from Amsterdam.
** mai - so, favorite thing that's either danish or dutch?
* cecilia - he/him/they/she - pastry! Danishes!
** bengo - plain or fruity?
** Fruity!
* eve - she/her - a tv show called broen.
* mai - she/her or they/them - Kierkegaard. Enjoyed his existentialist critique of organized religion in high school.
** marc - his name literally means graveyard. He's in a beautiful graveyard.
* eenblam (ben) - he/they, these bitters are pretty good. But I was gonna say Marc.

eve: cecilia is here because she is on the board of internet society like me, and came all the way from hayward

=== Meeting Roles ===
* Facilitator/s: eenblam
* Stacktaker: mai
* Timekeeper: n/a; small group
* Notetaker/s: bengo
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and past action items below:
* start a wiki page for decentralized web unconference [jenny]
** https://sudoroom.org/wiki/Mesh/MTP2018
* follow up on insurance quote [jenny]
* ping Beneficial re: bank account [jenny]
* add lolspace mount details to trello and CC Mai - [jenny]
** others available on Sunday - Mai, Eve, ?
*** even: I think I dropped the ball.
*** mai: no you didn't. Jnny was out of town. It just slipped. We were gonna do a diff node mount. I will follow up on that with Jnny about lolspace
* follow up with Jonah and Devi (cc Mai and Marc) [jenny]
** ben: is that the same Devi (sp?) at lolspace?
** marc: no, internet archive
** mai: jnny had heard from him about if we want to pu tgear on their tower, then soonish would be good because they'r eworking with people in Richmond on an open wifi project.
** marc: you can follow up with me too. Are you connected with Jonah yet?
** mai: I met him but not really. I didn't wanna go around Jnny since she's in touch already
* draft e-mail to hackerspaces about what we are looking for to connect to Internet Archive (grant)
** ben: grant is out of town but there's a pad so awesome thanks grant!
** started for others to hack https://peoplesopen.net/pad/p/ia-email-blast
* add benny to info@peoplesopen (grant)
** done (
* see who wants to meet about organizing the byoi-unconference (benny)
** https://sudoroom.org/wiki/Mesh/MTP2018
** marc: decentralized web summit is coming up at internet archive. Happened two years ago for free. Can volunteer for discount. 800-900 people. Costs more this year so they can rent the Mint as a venue. Because so many people are flying in, we are having this unconference, and they will announce it at the DWS event so everyone can come hang out at this unconference.
** mai: On Saturday, August 4th, in the morningish, we could do lightning talks, intro to project, and in afternoon have hackathon 1-6. Have a party at night, show what we made, party. Good to have time to show off what you made as incentive to work on things. Could do fundraiser. To be continued in agenda slot

== Updates & Reportbacks ==
=== Bugs/Technical ===
Priority bugs we need help with are located at: http://peoplesopen.net/helpwanted - For a high-level overview of recent Github activity, see the Trello: https://trello.com/invite/b/r9l5ouQ4/3b2eecd83bb9e7a57a339cf1ee038288/sudo-mesh-github-repos
* marc - not formally logged, but seems like there's no documentation on the 24 hour password reset bug with autoconf.
** cronjob runs every 24 hours
** Idea: log in before then and change password. Otherwise, cronjob changes it for you.
** Problem: If you don't remove the cronjob when you change your password, it just changes it again to something you don't know.
** eenblam - let's just fix that tonight.
** marc - have a tiny script for installing your ssh public key onto a node to bypass these quirks https://gist.github.com/Juul/726d85b429b394e2bdde375ef7de2e71

== About ISOC ==
* marc: cecelia, eve, would you like to talk about the internet society?
** cecilia: We recently had several people ask for grants about agri-internet. A lot of cali/US is rural, and don't have goo dintenret access in rural areas. e.g. a place in Santa Barbara wanted a grant to provide affordable connectivity. We thought that is a great project, did'nt get grant this time, but they should stick with it for next year, as should sudomesh, and stay aware of what other groups in California and usa are working on. e.g. some people want 'tele-health' solutions so peopl ein remote areas have connectivity to use the internet to talk with a doctor even when hostpitals are far away. Such solutions could be shared with whole US and world. ACM Compass conference, we were invited to. I attended at Facebook HQ for a copule days, one day at SJ Tech Museum. A lot of programmers, coders came together to talk about their projects. Much academia. Cool health care analytics project coming out of Chicago. Talked about how to make the conference bigger, get academics more publicity for their work. We want to build out the ISOC brand in San Francisco to get more people involved and understand this bigger ecosystem of increasing internet connectivity. We want to hold more events, thinking about what kinds. We were hoping that we could partner with sudomesh to hold a two day workshop on how to build you rown internet. Maybe even more hands on. Just presentations don't engage as much as more hands-on stuff. ISOC could partner with sudomesh on that. We're envisioning a joint conference with ISOC, sudomesh, etc.
** eve: last time I talked for a few minutes about what ISOC is.
** ISCO is: a civil society org based here and in geneva: ensuring a free and open internet and home of IETF but overall not necessarily technical. sends members to the board of ICANN. In america there are a bunch of chapter. Even the bay area chapter feels too spread out. Partly why we had trouble putting events together. Eve: hard to decide where to hold ISOC events in Bay Area where people from all over the Bay will attend (SV, SF, East Bay all). I had this plan: My ISOC project would be to have an internet governance talk to people who know nothing about it. And have that discussion not in a coworking space but where 'ordinary' people would come to learn about 'who is in charge' of the internet. The types of questions Ted Cruz would ask.
* Marc: People Centered Internet (Vint cerf's group) would be interested in this> All about recentering the internet toward the people that are using it.
* Eve: I had an idea bout a teach-in. I don't know if it would make sense to combine with the BYOI but partnering around it somehow.
* Cecilia: Help each-other bring visibility to each-others organizations
* Mai: Totaly relevant to net neutrality debate. That would engage people. Talk about last mile connectivity. There are certain ways in which content and platform providers are coming into that conversation. I heard that Facebook is starting to work on meshy stuff.
* Cecilia: it's not about just the talks. bridging the lecture / presentation and maybe the next part of it is more interactive where they can kinda see it in play. maybe that can help people getting involved with the organizations presenting. i work in the tech industry as well and i know that that's the kinda thing that people will go out and see (when they do go out).
* bengo: when the isoc group is cooridnating and planning, how is that comms happening.
* cecilia: it's a combination: we have distribution list for member swhere we send things out over eventbrite. we have a events again on meetup. we don't have a list of events yet because we're planning right now. if we do partner we're hoping to send out each-others events.
* bengo: is that public?
* cecilia: for meetups is public. eventbrite only goes out to members but it's free to be a member.
* eve: ISOC gives out a grant every year
* cecilia: planning session in washington dc every year where different chapters come together to talk about how ISOC can collaborate.
* cecilia: the reason i'm bringing it up is: every large company has an org that does venture capitalism/funds/entrepeneurship and through that i learned that there are a lot of peoplein the are bay area opening up last mile network. they really want to compete with the big guys. no-one can really understand why it costs so much (there must be a better way). several startups are working on this.
* mai: we're doing an even august so maybe if we can plan it two months in advance. maybe october?
* bengo: for next week's agenda we should discuss this again

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* Reed Bros
** bengo: notes from last Thursday: https://docs.google.com/document/d/1w1v7Cn4RzylpPsbICfBlPkDdOmP9gf9FcJUdNJXyGA0/edit
** eenblam: We didn't do reed bros mount because we are losing sight of the reed bros building. A tree is growing in the way. There are also power lines. We should still try to link to Reed Bros, but it's not a great long term thing, especially as a path to get Paxio bandwidth. So we should look for another path to Paxio. I don't advise working a lot more on Reed Bros.
** eve: what would the ideal path to paxio be?
** ben: A tallish tower on Omni that can see over the thing sin the way.
** jehan: i got in touch with retail leasing folks at MacArthur Commons. They forwarded me to management, but also mentioned that another *taller* building is going up in the lot next door. Also managed by them.
** mai - I emailed Paxio explaining that StorQuest is asking us for too much money. Asked if they'd be okay with us using other sites. Didn't hear back, so I followed up again yesterday. Hopefully the donation isn't contingent on securing StorQuest.
* <discussion about alternatives>
* LOLspace?
* West Oakland
** Hearth - Need to coordinate with Jake.
** Tom - standing by as we coordinate with Rolf and coordinate materials
** Rolf - need contact info

* bengo: If we had paxio bandwidth, what would we do with it. What could that unblock?

* Disaster Radio nodes

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
* BYOI / DWeb summit Unconference - Sat Aug 4 (discussions)

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* mai - we need ladders for node mounts. We would normally discussion this via #accounting-wg, but we're taking a break. Can we spend some cash on a ladder
** consenso

== Next Sunday ==
=== Node Mount ===
We try to arrange a rooftop node mount every Sunday afternoon. Ongoing spreadsheet is located at: https://peoplesopen.net/sundays
* Next Sunday's mount: stay tuned in rocket.chat for irregularly scheduled mounts this week. Maybe Tom/Rolf, pending comms.

=== Office Hours ===
We host office hours every Sunday from 1-2pm in Sudo Room. To sign up for a shift, fill in your name here: https://ethercalc.org/byoi_office_hours
* Next Sunday's volunteer: Seth
* Notes from this past Sunday's session:
* mai - related - on Sunday afternoon, Mary Jo & Terry will be meeting Chuck, who provides their internet! People mesh!

== Proposal (bengo.is): Add stale issues bot to sudomesh repos ==
https://github.com/sudomesh/projects/issues/2
* to close stale issues
** bengo: when I see a project with a github repo that has LOTS of issues that haven't been update for a long time I get a bad impression of the project
* increase engagement on non-stale issues
* automate administrative work
* Make github repos look maintained
* ben: why can't we have a "stale" tag so it can be differentiated from closed issues? It would still send notifications to people who were collaborating on the issue. Poke both issue filer and collaborators if filer is not a collaborator.
* bengo: the poking aspect can be different from the "stale" tagging
* jehan: Issues should only be closed for good reason.

Desired outcome: Move this proposal from 'New' to either 'Backlog' or 'Up Next' on this kanban board https://github.com/orgs/sudomesh/projects/2 and assign project shepherd (or close the issue as #wont)
* ACTION (bengo.is): update that issue on the kanban

== Proposal: Reimburse conference registration fees ==
* Several members of PON are attending conferences this summer (specifically Our Networks and DWeb Summit). We have a line item in our annual budget to pay for event registration, and several Accounting WG members have approved this reimbursement.
* Can we get a vote to approve the reimbursement of registration fees paid by those attending Our Networks and Dweb Summit?
* eenblam - don't feel like we have quorum tonight. Can we use loomio to determine if we can cover those costs retroactively?
** mai - Sure, although advance compensation would be preferable.
* bengo - if folks go on the organization's dime, I think it's reasonable for us to expect members to evangelize for us and follow up with a debriefing for our group and/or a blog post
* mai - I signed up for a table at the dweb science fair. Hopefully folks that attend will help evangelize.

== Discussion: BYOI / Decentralized Web Summit Unconference ==
* We're planning to have a BYOI following the DWeb summit on August 4th and/or 5th. Let's discuss and hack on the schedule/programming!
** mai - I can start a thread on rocket.chat. We already have the wiki page for the unconference https://sudoroom.org/wiki/Mesh/MTP2018
** would be good to set a time for those interested to jam on that.
** seth/bengo - good theme for office hours

== Discussion (bengo.is): brainstorm ways to improve https://peoplesopen.herokuapp.com/ ==
* monitor has been one of the more active projects recently
* what can you come up with as ways to improve it and make it more useful?
* e.g.
** What information would be useful to see on there?
** What do you want to 'monitor' about the network at any point?
* format: 5 minutes of silent brainstorming, then round-robin to hear everyone's ideas
** share: what is your idea? On a scale of 1-10, how impactful/urgent do you think it is (to inform prioritization)?
* bengo - seeing data over time would be good
** eenblam - see #???
https://peoplesopen.herokuapp.com/
* mai: translatin gthis jargon. What do these terms mean? Why does it matter?
* eve: are there privacy concerns with IP addresses?
* ben: Seeing if some node goes down? Did an exit node go up/down
* bengo: Could be good to have an 'admin' section that requires authentication by a board member for prvacy-concerned thing
* mai: what order are the table rows?
* mai: could
* seth: list services on the mesh
** mai: how often they're being used
** mai: let people opt out of being monitored
*** eve: that could make it hard to debug/run the network
** ben: it is also commons infra.

Desired outcome: Have fun. Document ideas in the repo itself to inspire others who find repo online. Create project proposals and/or issues for high impact items.

== Action Items ==
* Share idea re: holding a BYOI with ISOC sometime in October 2018 (eve)
* #software-wg on 07/17 (bengo)
** Hack on StaleBot
** Triage open issues
* Create Loomio vote re: reimbursing people for conference reg fees (mai)

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* link to previous meeting minutes

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/DD_MM_YYYY
* then please erase the contents of this pad
* then please cut & paste a blank template from here: https://sudoroom.org/mediawiki/index.php?title=Mesh/Mesh_Meeting_Notes_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/WalkThrough

2018-07-06T00:24:56Z

Bengo:

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with Sudo Mesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by Sudo Mesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to ensure your router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use Sudo Mesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
[[File:Router_reset_mynet.png|200px|thumb|right|Reset hole location!]]
Instructions to reset / default a WD MyNet N600 or N750 router:
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin / paperclip / tiny screwdriver into the reset hole and hold it for at least 15 seconds.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Configure =
A freshly flashed node automatically sets its IP address to 172.30.0.xx. You will need to configure your laptop to use the following network settings to communicate with the node:

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

== Autoconf (v.0.3.0) ==
'''''Note: If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you will not need to use makenode ([[#Makenode_.28v.0.2.3_and_earlier.29|instructions further down]]) after flashing the sudowrt-firmware to your router to configure it to work on People's Open Network.'''''

[[File:Nodeports titles.png|400px|thumb|right|Plug into port 3 to access the private network from your laptop. Port 2 connects to the public 'peoplesopen.net' network]] Connect your newly-flashed MyNet N600 to your existing Internet router via ethernet from your existing router's LAN port to your new node's Internet port. Wait a few minutes for your new node to connect to the Internet and obtain its private IP address. Once this happens, the node will broadcast a new WiFi network starting with 'peoplesopen.net' (and ending with a unique IP address). This is the public network, has no password, and is suitable for day-to-day internet access.

There is also a wireless network called 'pplsopen-admin'. This is the private network, and you can use it to access a web dashboard to configure some settings. The default WiFi password is 'meshtheworld'. Try connecting to it (you can also connect to the private network using an ethernet cable connected to port 3 on an N600).

While connected to the ''private'' network, try connecting to the home node's web dashboard by opening a web browser and navigating to http://172.30.0.1

If the flash was successful you should be brought to the following screen:

[[File:Peoplesopen-dash.jpg|frame|center|upright=2]]

The default password is 'meshtheplanet'.

Here you can set the amount of downstream and upstream bandwidth you're willing to share (default is set to 4096kb, or roughly 4 megabits/second):
[[File:homeScreen.jpg|frame|center|upright=2]]

[[File:WifiSettings.jpg|frame|left|upright=2|Set your private SSID and password via the 'WIFi Settings' tab. NOTE: When you first set your private SSID name and hit 'Save', you will have to reconnect to the newly-named SSID using the original default password ('meshtheworld') and then reconnect again with the new password after setting it in the dashboard]] [[File:Connections.jpg|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]
 

'''''Note: If you would like to be able to change these settings in the future, or ssh into your router, you will need to change the admin and root passwords within 12 hours.'''''

To do so, open a terminal while connected to the 'pplsopen-admin' SSID:
ssh root@172.30.0.1
Enter the following password: meshtheplanet

Set the root password.
passwd
Now set the admin password for logging into the web dashboard:
passwd admin

== Makenode (v.0.2.3 and earlier) ==
After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

=== Install Dependencies ===
You first will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

==== Linux ====

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

===== OS Compatibility checklist =====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

==== Mac ====

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

==== Windows 10 (Experimental)====

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

=== Install and run makenode ===
From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, upload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

[[Category:Mesh]]

Mesh/WalkThrough

2018-07-05T23:43:10Z

Bengo: Mention that accessing the web dashboard requires port 3 on an n600

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with Sudo Mesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by Sudo Mesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to ensure your router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use Sudo Mesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
[[File:Router_reset_mynet.png|200px|thumb|right|Reset hole location!]]
Instructions to reset / default a WD MyNet N600 or N750 router:
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin / paperclip / tiny screwdriver into the reset hole and hold it for at least 15 seconds.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Configure =
A freshly flashed node automatically sets its IP address to 172.30.0.xx. You will need to configure your laptop to use the following network settings to communicate with the node:

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

== Autoconf (v.0.3.0) ==
'''''Note: If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you will not need to use makenode ([[#Makenode_.28v.0.2.3_and_earlier.29|instructions further down]]) after flashing the sudowrt-firmware to your router to configure it to work on People's Open Network.'''''

[[File:Nodeports titles.png|400px|thumb|right|Plug into port 3 to access the private network from your laptop. Port 2 connects to the public 'peoplesopen.net' network]] Connect your newly-flashed MyNet N600 to your existing Internet router via ethernet from your existing router's LAN port to your new node's Internet port. Wait a few minutes for your new node to connect to the Internet and obtain its private IP address. Once this happens, the node will broadcast a new WiFi network starting with 'peoplesopen.net' (and followed by the node's new unique IP address).

Once you see this WiFi network, you can unplug your node from your existing router. Then:
* reconnect the newly flashed node to your computer via ethernet like it was in previous steps (be sure to use port 3 on an N600)
* make sure you are connecting as 172.30.0.10
* try connecting to the home node's web dashboard by opening a web browser and navigating to http://172.30.0.1

If the flash was successful you should be brought to the following screen:

[[File:Peoplesopen-dash.jpg|frame|center|upright=2]]

The default password is 'meshtheplanet'.

Here you can set the amount of downstream and upstream bandwidth you're willing to share (default is set to 4096kb, or roughly 4 megabits/second):
[[File:homeScreen.jpg|frame|center|upright=2]]

[[File:WifiSettings.jpg|frame|left|upright=2|Set your private SSID and password via the 'WIFi Settings' tab. NOTE: When you first set your private SSID name and hit 'Save', you will have to reconnect to the newly-named SSID using the original default password ('meshtheworld') and then reconnect again with the new password after setting it in the dashboard]] [[File:Connections.jpg|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]
 

'''''Note: If you would like to be able to change these settings in the future, or ssh into your router, you will need to change the admin and root passwords within 12 hours.'''''

To do so, open a terminal while connected to the 'pplsopen-admin' SSID:
ssh root@172.30.0.1
Enter the following password: meshtheplanet

Set the root password.
passwd
Now set the admin password for logging into the web dashboard:
passwd admin

== Makenode (v.0.2.3 and earlier) ==
After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

=== Install Dependencies ===
You first will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

==== Linux ====

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

===== OS Compatibility checklist =====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

==== Mac ====

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

==== Windows 10 (Experimental)====

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

=== Install and run makenode ===
From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, upload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

[[Category:Mesh]]

Mesh/WalkThrough

2018-07-05T23:39:14Z

Bengo: Clarify Autoconf steps and default password

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with Sudo Mesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by Sudo Mesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to ensure your router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use Sudo Mesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
[[File:Router_reset_mynet.png|200px|thumb|right|Reset hole location!]]
Instructions to reset / default a WD MyNet N600 or N750 router:
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin / paperclip / tiny screwdriver into the reset hole and hold it for at least 15 seconds.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Configure =
A freshly flashed node automatically sets its IP address to 172.30.0.xx. You will need to configure your laptop to use the following network settings to communicate with the node:

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

== Autoconf (v.0.3.0) ==
'''''Note: If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you will not need to use makenode ([[#Makenode_.28v.0.2.3_and_earlier.29|instructions further down]]) after flashing the sudowrt-firmware to your router to configure it to work on People's Open Network.'''''

[[File:Nodeports titles.png|400px|thumb|right|Plug into port 3 to access the private network from your laptop. Port 2 connects to the public 'peoplesopen.net' network]] Connect your newly-flashed MyNet N600 to your existing Internet router via ethernet from your existing router's LAN port to your new node's Internet port. Wait a few minutes for your new node to connect to the Internet and obtain its private IP address. Once this happens, the node will broadcast a new WiFi network starting with 'peoplesopen.net' (and followed by the node's new unique IP address). Once you see this WiFi network, you can unplug your node from your existing router, reconnect it to your laptop like it was in previous steps, make sure you are connecting as 172.30.0.10, and then try connecting to the home node's web dashboard by opening a web browser and navigating to http://172.30.0.1

If the flash was successful you should be brought to the following screen:

[[File:Peoplesopen-dash.jpg|frame|center|upright=2]]

The default password is 'meshtheplanet'.

Here you can set the amount of downstream and upstream bandwidth you're willing to share (default is set to 4096kb, or roughly 4 megabits/second):
[[File:homeScreen.jpg|frame|center|upright=2]]

[[File:WifiSettings.jpg|frame|left|upright=2|Set your private SSID and password via the 'WIFi Settings' tab. NOTE: When you first set your private SSID name and hit 'Save', you will have to reconnect to the newly-named SSID using the original default password ('meshtheworld') and then reconnect again with the new password after setting it in the dashboard]] [[File:Connections.jpg|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]
 

'''''Note: If you would like to be able to change these settings in the future, or ssh into your router, you will need to change the admin and root passwords within 12 hours.'''''

To do so, open a terminal while connected to the 'pplsopen-admin' SSID:
ssh root@172.30.0.1
Enter the following password: meshtheplanet

Set the root password.
passwd
Now set the admin password for logging into the web dashboard:
passwd admin

== Makenode (v.0.2.3 and earlier) ==
After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

=== Install Dependencies ===
You first will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

==== Linux ====

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

===== OS Compatibility checklist =====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

==== Mac ====

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

==== Windows 10 (Experimental)====

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

=== Install and run makenode ===
From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, upload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

[[Category:Mesh]]

User:Bengo

2018-04-18T06:20:41Z

Bengo: Created page with "bengo is https://bengo.is I am '''Ben'''jamin '''Go'''ering. bengo is shorter, and there are many bens. I participate in Sudo Mesh and attend most Tuesday meetings...."

bengo is https://bengo.is

I am '''Ben'''jamin '''Go'''ering. bengo is shorter, and there are many bens.

I participate in [[Mesh|Sudo Mesh]] and attend most Tuesday meetings.

I live close to Noisebridge in San Francisco.

Mesh/17 Apr 2018

2018-04-18T04:19:41Z

Bengo: Created page with "People's Open Network Weekly Meeting - 17 April 2018 7:30pm-9pm * https://omnicommons.org/wiki/Safer_Space_Policy If you'd like to join remotely via Zoom: https://zoom.us/j/6..."

People's Open Network Weekly Meeting - 17 April 2018 7:30pm-9pm
* https://omnicommons.org/wiki/Safer_Space_Policy

If you'd like to join remotely via Zoom: https://zoom.us/j/6547775473

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Proposal: Accounting / Fundraising Working Group (15 mins)
* Discussion: Group decisionmaking / Establishing our relationship with the Omni (15 min)
* Discussion: Equipment Purchasing Process (15 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: What is the best fast food place?
* Bengo: he/him, cheap falafel
* Doug: pizza, he'him
* Seth: In&Out Burger!
* Grant: falafel
* Jenny: she/her, In&Out
* Mai: she/her or they/them - In&Out or Chipotle

=== Meeting Roles ===
* Facilitator/s: Bengo
* Stacktaker: Bengo
* Notetaker/s: Jenny, all of us
** URL of this pad: https://peoplesopen.net/notes
* Next meeting's facilitator(s): TBD

== Check in on previous action items ==
* solar powered extender nodes?
** Ocean Max not present
* Talk to other wireless companies re: how they do general liability insurance - jnny + ben
** ben - MonkeyBrains suggested we reach out to Detroit and Red Hook. http://redhookwifi.org/
*** Max or Jnny to reach out to Red Hook and/or insurer that Omni uses
*** Doug: look into medical insurance. trying to protect the organization in general and the board specifically
*** Doug: in lieu of anything else, only people with their own health insurance should be on the roof
* order items to order - jnny
** have ___ in the ebay cart. waiting on a few more specific budget requests (ideally links) and then will place order
* open zeroconf tunneldigger issue - grant
** it's working! almost, now digs tunnel, but is having trouble babeling with other nodes, they can see eachother, but is having trouble routing over one ,
** issue number? or no issue? #129 sudowrt-firmware
** grant: next steps: make web portal have more admin features, eg bandwidth percentage to share. nightly builds (set up a cron on my home computer which is on the mesh) til we figure out Travis. Still trying to figure out Travis. Ideas re: how we work on firmware and do releases, mebbe a breakout session?
* get in touch with Reed Brothers - grant, will?
** grant: not done yet. contingent on paxio. me, will & jehan went on omni roof on sunday to scout. pretty sure we can see paxio from western corner of omni roof, but in-construction condo @ macarthur may eventually block. best to talk w/ reed brothers anyways.
* be in touch with Paxio re: gigabit link - mai
** jehan and i touched base w/ storquest. they want money for roof rental. should go w/ free options.
*** grant: storquest can see lotsa stuff, might be worth it eventually - put a ton of antennas pointing in every direction mebbe
*** mai: really great how responsive paxio has been, just need to get our equipment together

= Updates & Reportbacks ==
=== Bugs/Technical ===
Priority bugs we need help with are located at: http://peoplesopen.net/helpwanted - For a high-level overview of recent Github activity, see the Trello: https://trello.com/invite/b/r9l5ouQ4/3b2eecd83bb9e7a57a339cf1ee038288/sudo-mesh-github-repos
* Bug 27: grant - dns issue introduced by Bug #23. temp solution to add a static dns + a backup. psychz & hurricane electric IPs now static in there - 2 exitnodes instead of one. not a priority until we have more exit nodes
** mai: fam is very psyched. "you're geniuses! this is magic!" slow but fast enough for them to stream the NBA playoffs

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* Devi from SOL/LOLspace/Peacock Rebellion
** emails were going to wrong addresses. Now should be good further communication this week
* Hooking up some encampments in Berkeley
** Jenny and Robb talked with Betsy Morris at the Peace & Life Fund awards ceremony the other night. Camps at Aquatic Park, Berkeley Marina, and the re-established FTCFTH (First They Came For The Homeless) camp at Here & There could hella use internetz. Leads: David&Niki's could potentially reach Here&There, however the following properties have better line of sight (tho are renters not owners): sally at adeline & alcatrez - street spirit publisher - tiny home village project; Inter-City Services; Biketopia; another bix right across the street i'm forgetting the name of
** Aquatic Park (ashby side) & Dare To Change (rehab camp next door) have LOS to Urban Ore. Something about an old abandoned radio tower in vicinity...?!

*Ed's place - this Sunday? safety party at Ed's? sierk mentioned BBQ
** ben - has Doug seen photos? I didn't send them
** grant - yes, showed him the long shot, sierk isn't here to share more photo's (if he has any) (Cool :D )
** Ed not present this Sunday. Requests another Sunday

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
* CityCamp, April 21, 2018 @ Oakland City Hall
** https://www.eventbrite.com/e/citycamp-oakland-2018-our-city-our-future-tickets-43679460442
** Mai, Ben, and you! Come to CityCamp
* Decentralized Web Summit, August 1â€“2, 2018 @ Internet Archive
** https://decentralizedweb.net/
** mai: happened in 2016, mostly blockchain-based. they invite the "fathers of the internet" <insert eye roll> they asked us what we wanted to propose. largely web-based not last-mile infrastructure
* State of our Networks, July 13â€“18, 2018 in Toronto, Ontario w/ Toronto Mesh
** https://ournetworks.ca/2018
** Call for Participation due April 30th
** grant: talked with Dawn of TO Mesh this evening. interested in having people do talks/workshops. sprints the following 3 days, they have a space where you can hack w/ folx. might be going, not sure yet. will put draft proposal on an etherpad and share it
* Brief reportback from NAB: anka and jenny got kicked out of the conference for holding a banner that stated "SAVE NET NEUTRALITY!" during Ajit Pai's keynote speech. **golf claps**

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* Strategic Plan Meeting Summary / Reportback
** https://peoplesopen.net/pad/p/pon-strategic-plan-2
** bengo - didn't leave with consensus on priorities. conversations happened that needed to happen and were useful. wuz a little emotional toward the end
** mai: bigger conversations that needed to happen about what PON is about - just doing demos and encouraging people to learn, or actually building a network. most agreed upon the latter. there was consensus on the latter.
*** ben: there was confusion over what people wanted project scope to be, but I think it was really a matter of Jorrit wanting to ask, "what does it take to move past being a demo? what does it take for us to move past that and what are our current limitations?" Do feel like there was consensus on going big.
** mai: looked at notes from our last strategic meeting and realized there were a lot of things we had made progress on.
** bengo: user story mapping as a way of creating flows re: what someone impacted this project. well-defined projects as opposed to themes, agile-style backlog of priorities for the legal entity, that can reflect any changes in priority. for new folks the top of that list is a good place to start.
* Purchasing requests
- 24gHz airFiber ($$)
- box cutter
- large zip ties
- chimney mount Grant purchased
- harnesses and rope // climbing gear
- gloves
- shielded ethernet ends in mounting bin on shelvesDo we have non-ez though? hmmm
- PVC
- socket wrench set
- metal snips
- binoculars
- walkie talkies
** ben - I can go to Graybar tomorrow to pick up a lot of this.
* mai: maybe a ladder?
** ben - yes please
* grant: research ecommerce site idea. how to organize and sell our swag.

== Next Sunday ==
=== Node Mount ===
We try to arrange a rooftop node mount every Sunday afternoon. Ongoing spreadsheet is located at: https://peoplesopen.net/sundays
* Next Sunday's mount: Jenny will ping Robb re: Diane's

=== Office Hours ===
We host office hours every Sunday from 1-2pm in Sudo Room. To sign up for a shift, fill in your name here: https://ethercalc.org/byoi_office_hours
* Notes from this past Sunday's session:
** debugging bug #27 by reproducing in Omni
** getting test bed up and running again
** grant: 100.65.42.65 and 100.65.42.1 accessible to those on the mesh (omni mesh nodes) - can play w/ an extender node testbed
* Next Sunday's volunteer: no more party :(
** Safety Party w/ Doug at Omni

== Proposal: Accounting / Fundraising Working Group==
Please add any proposal needing consent from or action by the group below:
* mai: Proposal to create a working group to reconfigure our account/finance situation
** For example, to understand our current financial situation, establish protocols around purchasing, and explore options for pursuing a self-sustaining income model for the project (which would likely entail a spin-off enterprise)
* jnny: +1! also, working fiscal policies & procedures draft: https://docs.google.com/document/d/1PeFoJUe4X3ww4mFKUMvbC4A-Yc_6sh5qbYdEgTdJpYQ/edit# & budget request form: https://docs.google.com/spreadsheets/d/13XzQBoRTMiMhZLPc8Ikuf14ur1JSSAHWNICFdpszPis/edit#gid=4
* participants: mai, jenny, ben, bengo, grant (mebbe)
** mai - consistent time to work on stuff, figuring out stuff like passpack for purchases, formalizing procurement processes. This process might be reflective of how we make decisions together in general. Discussion item, moving on!
** bengo - Indefinite working group, or is it just to accomplish this reorganization in the shortterm?
** jnny - I think an extended working group would be good.
* jnny - went to Beneficial State Bank today! They allow infinity check-signers, infinity sub-accounts, which has been the main barrier with Unify (sp?) which is the credit union we've been working with. Only like 10 of either.
* bengo: is this the first working group? should be a wiki page that delineates working groups and how people can plug into different working groups
* ben - doodle for times?
* '''Consenso?'''

== Discussion: Group decisionmaking / Establishing our relationship with the Omni ==
* Decision re: how we want to officially establish our relationship with the Omni brings to light larger questions about how we make decisions as group
* Currently, our bylaws state that the Board makes consensus decisions about financial decisions and legal agreements
** Does this work? How could we incorporate input from those who have dedicated a lot of time and energy to the project?
*** jnny: historically, we don't follow our own bylaws. decisions have always been made with consenso of active volunteers. also, this reminds me we're due for our annual board meeting and nomination of new officers & directors! all a-board! :p
** blake: having anonymity in a consensus process seems like a really bad idea
**mai: should decide and write out how we do this, it's not written anymore. we want everyone who's core agree, or at least live with the decision. loomio has thumbs up, down, and sideways for instance
** bengo: maybe that can be an axtion item for finance wg - to make a formal proposal to the board/sudomesh crew, give them a chance to veto.
** ben: do we feel like we do have consensus for a payment, eg half of $100 or $100 flat? With the caveat that discussion about additional donations can continue
** jnny - Omni is now moving to require all groups to apply for use of ballroom, which includes discussing a percentage donation.
** mai - In that case, most folks seem to be in favor of donating the flat rate modulo the percentage part. So, can we move forward on the flat donation?

== Discussion: Accounting and Purchases ==
* Mai - push topic to working group?
** (consenso)

* How do we keep track of inflows and outflows of money?
** jnny: Quickbooks login infoz in passpack, but if we use sthg like cobudget (see below), we could easily make all income and expenses openly transparent
* How do we decide to spend and receive funds?
** jnny: been playing around with cobudget (though it's yet another communication platform... >_<) - invited mai, grant, ben, benny, jorrit - anyone else want to play around wit it? https://cobudget.co
*** ben - isn't sierkje building something like this from scratch? Y'all might wanna chat.

== Action Items ==
* Grant: Make moves on plan for PON e-commerce revenue stream (e.g. shirts, hats, stickers)
* grant: setup nightly builds of zeroconf firrmware (debug travis further) and tighen up openwrt build process
* ben: Jorrit and I are aso discussing CI for monitoring tools. I think zeroconf is higher priority, though
* grant: follow-up with Paxio to confirm 24Ghz antenna situation, suggest LOS from Omni (how do we align with their equipment?)
* mai: schedule meeting for Account/Finances Working Group
* jenny: buy some shit ^_^
* jenny: follow up with devi / lolspace
* jenny & ben: more work into vehicle procurement

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
* Extended Node Whispering Discussion / Stable Release Definition(s)

== Last Meeting Notes ==
* https://sudoroom.org/wiki/Mesh/10_Apr_2018

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki
* then please erase the contents of this pad
* then please cut & paste a blank template from here: https://sudoroom.org/mediawiki/index.php?title=Mesh/Mesh_Meeting_Notes_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes