Sudo Room - User contributions [en]

Mesh/WalkThrough

2019-11-20T06:01:21Z

Bennlich: deleted a big unnecessary chunk; reorganized configuration section

'''Congratulations''' on choosing to become part of the [https://peoplesopen.net/ People's Open Network]!

Continue reading to follow these do-it-yourself / do-it-together instructions, or read more about [[Mesh#How_To_Participate|how to participate and get help]].

= Summary =
This is a [[Mesh/WalkThrough#linkback|WalkThrough]] to install a custom operating system on a compatible network device for use as a '''node''' (e.g. your home router) on the network. You will learn how to flash Sudo Mesh's [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware] (a custom build of [https://openwrt.org/ OpenWRT]) and then configure it.

At the end of this walkthrough, you'll be able to plug in your router and join the mesh. '''Note:''' In order to access the internet, you will likely need your own connection with an existing Internet Service Provider (ISP), or otherwise be located near [https://peoplesopen.net/map/ another mesh node with its own route to the internet].

= Prerequisites =

This walkthrough assumes you're using linux or another unix-like operating system (such as Mac OS X, Ubuntu, FreeBSD, etc) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the command-line interface terminal] ('terminal' for short). [https://github.com/sudomesh/sudowrt-firmware/issues/new Contact us] if you can contribute instructions for other systems.

The general idea of building your own mesh node consists of three steps:
# [[#Download/Build|downloading or compiling]] the custom firmware
# [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory '''flash''' memory])
# [[#Configure|configuring the node]] to function as part of a mesh.

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 is compatible to work as a mesh node.

= Download/Build =

Now that you have a node, you can 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 firmware builds:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/sudowrt-firmware/0.3.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory-0.3.0.bin 0.3.0]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though most builds for routers not listed above have not been tested. 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, ([https://github.com/sudomesh/sudowrt-firmware read more on github]).

= 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. Keep another hand free.
* With the pin still 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: <code>192.168.1.10</code> (some devices will only accept from this IP)
* Subnet Mask: <code>255.255.255.0</code>
* Gateway: <code>0.0.0.0</code> (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 <code><eth_interface></code> is the name of your ethernet interface found using the <code>ip addr</code> command (common names include <code>eth0</code>, <code>enp3s0</code>, ...)

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]]
* If your reset was not successful, try debugging your network configuration described in the previous step.
** If you continue to have issues consider reloading network settings or restarting your computer.
** If you are still unable to access this firmware upload page, turn off your router and try to reset it again as instructed above.
* 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]]
* Make sure not to disconnect or lose power at this stage, wait for the timer to complete.

'''Note:''' Sometimes the firmware upload will not complete correctly. 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 =

'''''If you are configuring something other than a WD MyNet N600, or firmware version 0.2.3 or earlier, follow ([[#Makenode_.28v.0.2.3_and_earlier.29|these instructions]])'''''

[[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 cable from your existing router's '''LAN port''' to your new node's '''Internet port'''.
# Wait several minutes for your new node autoconfigure, connect to the Internet, and obtain its private IP address from the sudo mesh build server. When this process is complete, the node should broadcast several WiFi networks with the following SSIDs and purposes:
#* <code>peoplesopen.net</code> - This is the public network broadcast on the 2.4ghz band; it has no password, and is suitable for access to the internet.
#* <code>peoplesopen.net fast</code> - This is the same public network, but broadcast on the 5ghz band, which is more ideal for high-bandwidth activities such as streaming media.
#* <code>peoplesopen.net-node2node</code> - This is the public network used for mesh nodes to discover and communicate with one another. You should not need to connect or use this network, but you will want to verify it is active.
#* <code>pplsopen-admin</code> This is the private network, and you can use it to access a web dashboard to configure some settings, such as its SSID. The default WiFi password is <code>meshtheworld</code>. Try connecting to it (you can also connect to the private network using an ethernet cable connected to '''port 3''' on an N600 -- see diagram for details).

Learn more about the [[Mesh/Network topology|network's topology here]].

== Configuring the Web Dashboard ==

While connected to the ''private'' network (default <code>pplsopen-admin</code>), try connecting to the home node's web dashboard by opening a web browser and navigating to [http://172.30.0.1 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 <code>meshtheplanet</code>.

Here you can set the amount of downstream and upstream bandwidth you're willing to share on the public <code>peoplesopen.net</code> network (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 (<code>meshtheworld</code>) and then reconnect again with the new password after setting it in the dashboard]] [[File:newrouter.png|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]
 

== Changing Admin and Root User Passwords ==

'''''Note: If you would like to be able to change the above wifi 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 <code>pplsopen-admin</code> private network (or whatever new SSID you may have chosen):
ssh root@172.30.0.1
Enter the following password: <code>meshtheplanet</code>

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

== Testing ==

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID (default <code>pplsopen-admin</code>). Additionally the public SSIDs <code>peoplesopen.net <your mesh IP></code> and <code>peoplesopen.net fast <your mesh IP></code> will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A fourth interface named <code>pplsopen.net-node2node</code> will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. Reach out to the [[Mesh#How_To_Participate|rest of the network]]!

== Makenode (v.0.2.3 and earlier) ==
'''''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 do not need to use makenode. See the autoconf instructions above.'''''

Makenode's documentation has been consolidated to [[Mesh/Makenode|its page.]]

= 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

2019-11-20T04:48:31Z

Bennlich: /* Download/Build */

'''Congratulations''' on choosing to become part of the [https://peoplesopen.net/ People's Open Network]!

Continue reading to follow these do-it-yourself / do-it-together instructions, or read more about [[Mesh#How_To_Participate|how to participate and get help]].

= Summary =
This is a [[Mesh/WalkThrough#linkback|WalkThrough]] to install a custom operating system on a compatible network device for use as a '''node''' (e.g. your home router) on the network. You will learn how to flash Sudo Mesh's [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware] (a custom build of [https://openwrt.org/ OpenWRT]) and then configure it.

At the end of this walkthrough, you'll be able to plug in your router and join the mesh. '''Note:''' In order to access the internet, you will likely need your own connection with an existing Internet Service Provider (ISP), or otherwise be located near [https://peoplesopen.net/map/ another mesh node with its own route to the internet].

= Prerequisites =

This walkthrough assumes you're using linux or another unix-like operating system (such as Mac OS X, Ubuntu, FreeBSD, etc) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the command-line interface terminal] ('terminal' for short). [https://github.com/sudomesh/sudowrt-firmware/issues/new Contact us] if you can contribute instructions for other systems.

The general idea of building your own mesh node consists of three steps:
# [[#Download/Build|downloading or compiling]] the custom firmware
# [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory '''flash''' memory])
# [[#Configure|configuring the node]] to function as part of a mesh.

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 is compatible to work as a mesh node.

= Download/Build =

Now that you have a node, you can 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 firmware builds:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/sudowrt-firmware/0.3.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory-0.3.0.bin 0.3.0]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/sudowrt-firmware/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/sudowrt-firmware/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though most builds for routers not listed above have not been tested. 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, ([https://github.com/sudomesh/sudowrt-firmware read more on github]).

= 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. Keep another hand free.
* With the pin still 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: <code>192.168.1.10</code> (some devices will only accept from this IP)
* Subnet Mask: <code>255.255.255.0</code>
* Gateway: <code>0.0.0.0</code> (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 <code><eth_interface></code> is the name of your ethernet interface found using the <code>ip addr</code> command (common names include <code>eth0</code>, <code>enp3s0</code>, ...)

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]]
* If your reset was not successful, try debugging your network configuration described in the previous step.
** If you continue to have issues consider reloading network settings or restarting your computer.
** If you are still unable to access this firmware upload page, turn off your router and try to reset it again as instructed above.
* 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]]
* Make sure not to disconnect or lose power at this stage, wait for the timer to complete.

'''Note:''' Sometimes the firmware upload will not complete correctly. 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 <code>172.30.0.xx</code>. You will need to configure your laptop to use the following network settings to communicate with the node:

* IP address: <code>172.30.0.10</code>
* Subnet mask: <code>255.255.255.0</code>
* Gateway: <code>0.0.0.0</code>

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 <code><eth_interface></code> is the name of your ethernet interface found using <code>ip addr</code> (common names include <code>eth0</code>, <code>enp3s0</code>, ...)

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 [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, your node can be autoconfigured. You will not need to use the previous solution <code>makenode</code>, otherwise you may need to read the ([[#Makenode_.28v.0.2.3_and_earlier.29|instructions further down]])'''''

[[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 cable from your existing router's '''LAN port''' to your new node's '''Internet port'''.
# Wait several minutes for your new node autoconfigure, connect to the Internet, and obtain its private IP address from the sudo mesh build server. When this process is complete, the node should broadcast several WiFi networks with the following SSIDs and purposes:
#* <code>peoplesopen.net</code> - This is the public network broadcast on the 2.4ghz band; it has no password, and is suitable for access to the internet.
#* <code>peoplesopen.net fast</code> - This is the same public network, but broadcast on the 5ghz band, which is more ideal for high-bandwidth activities such as streaming media.
#* <code>peoplesopen.net-node2node</code> - This is the public network used for mesh nodes to discover and communicate with one another. You should not need to connect or use this network, but you will want to verify it is active.
#* <code>pplsopen-admin</code> This is the private network, and you can use it to access a web dashboard to configure some settings, such as its SSID. The default WiFi password is <code>meshtheworld</code>. Try connecting to it (you can also connect to the private network using an ethernet cable connected to '''port 3''' on an N600 -- see diagram for details).

Learn more about the [[Mesh/Network topology|network's topology here]].

=== Configuring the Web Dashboard ===

While connected to the ''private'' network (default <code>pplsopen-admin</code>), try connecting to the home node's web dashboard by opening a web browser and navigating to [http://172.30.0.1 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 <code>meshtheplanet</code>.

Here you can set the amount of downstream and upstream bandwidth you're willing to share on the public <code>peoplesopen.net</code> network (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 (<code>meshtheworld</code>) and then reconnect again with the new password after setting it in the dashboard]] [[File:newrouter.png|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]
 

=== Changing Admin and Root User Passwords ===

'''''Note: If you would like to be able to change the above wifi 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 <code>pplsopen-admin</code> private network (or whatever new SSID you may have chosen):
ssh root@172.30.0.1
Enter the following password: <code>meshtheplanet</code>

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

== Testing ==

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID (default <code>pplsopen-admin</code>). Additionally the public SSIDs <code>peoplesopen.net <your mesh IP></code> and <code>peoplesopen.net fast <your mesh IP></code> will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A fourth interface named <code>pplsopen.net-node2node</code> will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. Reach out to the [[Mesh#How_To_Participate|rest of the network]]!

== Makenode (v.0.2.3 and earlier) ==
'''''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 do not need to use makenode. See the autoconf instructions above.'''''

Makenode's documentation has been consolidated to [[Mesh/Makenode|its page.]]

= 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/05 11 2019

2019-11-13T04:53:48Z

Bennlich: Created page with " '''People's Open Network Weekly Meeting - 05 November 2019 7:30pm-9pm''' * https://omnicommons.org/wiki/Safer_Space_Policy = Attendees = * Jenny - she/her - Part * Radar -..."

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

= Attendees =
* Jenny - she/her - Part
* Radar - amateur radio, excited about disaster.radio and radio projects, he/him
* Nels - he/him - want to install a node and share internets
* seth - he/him/they/them - experienced with node intalls and down to help folks plug in
* Angela - she/her - came last week for hardware hack, found out about the project and want to plug in, software engineer, been looking for a place like this, outside of work stuff to help the community
*juul: can get flexible solar panels now, fairly lightweight, 50W, replace LI battery
* Loren - he/him - outside the door. - setup a mcan plug esh node in my home and figure out how i t
* Tyler - he/him - crazy ham person trying to get more hams involved
* Vanessa - she/her - interested in learning more
* Kevin - he/him - same

== Announcements ==
* DevSummit 2019 - tomorrow through Friday! Contact Jenny for info/access - Sudo Mesh
** Attendees -
**** Name:
* Juul: Hardware for mobile hotspots should be arriving this weekend. Solar panels, chargers, antennae - need to test the setup on Sunday afternoon, ~1pm if anyone wants to join!
** Tasks for completion:
*** Which frequencies are used by Sprint in the East Bay? Different in different areas?
*** TS-9 to antenna adapters (depending on frequencies) - whichever are cheapest
**** Sprint uses LTE bands 25, 26, 41 - is this consistent across bay area?
https://www.cellmapper.net/map

*Radar: According to a Radio Frequency â€“ Electromagnetic Energy (RF-EME) Compliance Report prepared for a Sprint rooftop installation near Regent Street in Berkeley, Sprint utilizes the following three frequencies:
2500.00 MHz - Band 41 (2502-2690 MHz),
800.00 MHz â€“ Band 26 (806-825 MHz & 851-869 MHz),
1900.00 MHZ â€“ Band 25 (1850-1990 MHz)

== FAQs ==
How much power do nodes use?
* https://sudoroom.org/wiki/Mesh/Power
Sonic fiber allow sharing?
* Allow open hotspots, but not direct links.

= Action Items =
* Swag-making for Sunday: Jenny/Seth/you?
* Send paperwork for CoD grant - Jenny/you?

Mesh/Mesh Meeting Notes Template

2019-11-13T04:50:39Z

Bennlich: formatting

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

== Agenda ==
* Introductions and Meeting Roles (15 mins)
* Announcements and Upcoming Events (10 mins)
* When's the Meet-Up This Month?
* Check Ins: Action Items & Active Projects (30 mins)
* Wrap-up meeting (5 min)

== Introductions ==
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question:
*

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

== Announcements and Upcoming Events ==

== When's the Meet-Up This Month? ==
* What:
* When:
* Where:
* Who:
** Bottomliners:

== Check Ins: Action Items & Active Projects ==
Round-robin:
1) What did you do last month?
2) What do you want to do this month?
*
*

== Useful Links ==
* Active Projects: https://trello.com/b/wBKTQKDs/active-projects
* Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications
* Node Mounts: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* Bugs & Technical: Github: https://peoplesopen.net/issues, https://peoplesopen.net/learn/development/
* Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/10_December_1815

== Wrap-up 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_MONTH_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/Mesh Meeting Notes Template

2019-11-13T04:49:13Z

Bennlich: iterating on agenda outline

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

=== Agenda ===
* Introductions and Meeting Roles (15 mins)
* Announcements and Upcoming Events (10 mins)
* When's the Meet-Up This Month?
* Check Ins: Action Items & Active Projects (30 mins)
* Wrap-up meeting (5 min)

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question:
*

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

== Announcements and Upcoming Events ==

=== When's the Meet-Up This Month? ===
* What:
* When:
* Where:
* Who:
** Bottomliners:

== Check Ins: Action Items & Active Projects ==
Round-robin:
1) What did you do last month?
2) What do you want to do this month?
*
*

== Useful Links ==
* Active Projects: https://trello.com/b/wBKTQKDs/active-projects
* Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications
* Node Mounts: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* Bugs & Technical: Github: https://peoplesopen.net/issues, https://peoplesopen.net/learn/development/
* Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/10_December_1815

== Wrap-up 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_MONTH_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/Minutes

2019-10-31T18:30:26Z

Bennlich:

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

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/29_10_2019|2019-10-29]]
| Monthly organizing meeting
|-
| [[Mesh/22_10_2019|2019-10-22]]
| Monthly organizing meeting
|-
| [[Mesh/24_09_2019|2019-09-24]]
| Monthly organizing meeting
|-
| [[Mesh/17_09_2019|2019-09-17]]
| Monthly organizing meeting
|-
| [[Mesh/27_08_2019|2019-08-27]]
| Monthly organizing meeting
|-
| [[Mesh/30_07_2019|2019-07-30]]
| Monthly organizing meeting
|-
| [[Mesh/02_07_2019|2019-07-02]]
| Monthly organizing meeting
|-
| [[Mesh/25_06_2019|2019-06-25]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2019|2019-06-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_June_2019|2019-06-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_May_2019|2019-05-28]]
| Weekly organizing meeting
|-
| 2019-05-21
| Hack night; no notes
|-
| [[Mesh/14_May_2019|2019-05-14]]
| Weekly organizing meeting
|-
| [[Mesh/30_April_2019|2019-04-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_April_2019|2019-04-23]]
| Annual board meeting
|-
| [[Mesh/16_April_2019|2019-04-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_April_2019|2019-04-09]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2019|2019-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/19_March_2019|2019-03-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_March_2019|2019-03-12]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2019|2019-02-26]]
| Weekly organizing meeting
|-
| [[Mesh/19_February_2019|2019-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_February_2019|2019-02-12]]
| Weekly organizing meeting
|-
| [[Mesh/29_January_2019|2019-01-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_January_2019|2019-01-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_January_2019|2019-01-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_January_2019|2019-01-08]]
| Weekly organizing meeting
|-
| [[Mesh/18_December_2018|2018-12-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_December_2018|2018-12-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_December_2018|2018-12-04]]
| Weekly organizing meeting
|-
| [[Mesh/27_November_2018|2018-11-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_November_2018|2018-11-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_November_2018|2018-11-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_November_2018|2018-11-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_October_2018|2018-10-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_October_2018|2018-10-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_October_2018|2018-10-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_October_2018|2018-10-09]]
| Weekly organizing meeting
|-
| [[Mesh/2_October_2018|2018-10-2]]
| Weekly organizing meeting
|-
| [[Mesh/25_September_2018|2018-09-25]]
| Weekly organizing meeting
|-
| [[Mesh/18_September_2018|2018-09-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_September_2018|2018-09-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[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/29 10 2019

2019-10-31T18:29:33Z

Bennlich:

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

=== Agenda ===
* Introductions and Meeting Roles (15 mins)
* Announcements and Upcoming Events (10 mins)
* Check Ins: Action Items & Active Projects (30 mins)
* Check in on ongoing projects (15 mins)
* Discussion items (10 min)
* Wrap-up meeting (5 min)

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* soundtrack to this meeting: magnet:?xt=urn:btih:a97c9afe5d4fccb1439d79ae9612182c7a71ff23
* jenny-she/her- involved since 2013, we recently like a week ago applied for up to $40k from the center for disability which is distroing funds to community-based orgs that are helping. it's governor newsom's bill for emergency prepearedness. we just heard back. they want numbers (how many people are we gonna help by december 2020).
* tom - he/him - interested in the mesh for a long time, done one or two installs, wants to improve their own connectivity
* benny - he/him - just travelled to pbgh so haven't been thinking about the mesh for a little while. There are a lot of hills there and abandoned buildings, and grant said that there's a mesh network there but didn't get in touch with them
* jason - he/him - new here, went to Cal and volunteered at the Open Computing facility and currently live kitty corner from Omni
* mai - she/her/they/them - been involved for two years now w/ peoplesopen but getting more into disaster radio now -- low powered devices that transmit 256 byte messages up to 10 miles. Cheap and solar powered. Lots of interest currently, working on raising money.
* tyler - he/him - mostly involved in ham radio stuff, outreach, been thinking of potential node mounts of high priority. we're having a repeater painting party (at the HAM group) and i will try to squeeze in a site survery. it might happen this saturday.
* dan/radar - he/him - pretty new here, got interested by tyler's presentation to the ham radio club. interested in disaster.radio - was chief engineer of a television station - put up a lot of 13/10GHz radio equipment. here to learn and to help be part of the solution
* seth - he/they - :)
* ibrahim - just left my stuff here by coincidence -- wasn't intending to join this meeting -- studying c++ at laney -- one thing that's been on my mind over the last five years: how to start a network after an earthquake hits, so funny that we ran into each other. also studying deep learning. thinking about using robots to do search and rescue. bay area native. great grand nephew of jimi hendrix, but i cant play guitar.
* marc/juul - he/him - ive been looking at foo over udp -- a different way to do tunneling
* loren - he/him - from berkeley, has been to the meeting a few times, also works at Open Computing Facility, interested to be more involved, maybe node mounts?
* vanessa - she/her - first time here, Loren brought her here

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

== Announcements and Upcoming Events ==
* from Tracy Rosenberg re: Oakland Internet Choice:> It has been a long road, but I'm very pleased to announce that it looks likely that Council president Rebecca Kaplan will champion our Communications Choice effort in early 2020!> In order to support the office, we need to demonstrate community support in the next 60-90 days. Here's a link to send Oakland City Council President Rebecca Kaplan an e-mail in support of this initiative: https://takeaction.salsalabs.org/oicc0

In case you don't already know: the Oakland Internet Choice effort is working on passing a city ordinance that requires landlords of large multi-tenant buildings to allow any qualified Internet service provider to serve their tenants. It's based on a similar ordinance that recently passed in SF, and has already upset giant ISPs who were getting used to making exclusive deals with landlords. More info in the above link.

Please forward to your friends in Oakland. This is huge! It's a necessary step in making it possible for independent (and community) ISPs to compete with the incumbent monopolies.

* DevSummit / Aspiration Tech / Non-profit software development summit is November 6th through 8th this year and it is awesome. It's run very unconf style. One of the best-facilitated conferences. Brings together activists and non-profit folks who intersect with technology in different ways. Gunnar (organizer) sent a code for people interested in going. I guess in turn I was thinking of us donating some amount to co-sponsor the event.* https://aspirationtech.org/events/devsummit19

* The Commons film will be screened November 9th. Saturday. It includes interviews from way back in old sudo room.

* Someone ported psilocybin production into ecoli
** 10.1016/j.ymben.2019.09.009

== Pending Proposals ==
* Vector impedence analyzer - for making and testing out antennas
** https://sudoroom.org/wiki/Mesh/29_10_2019#mini-proposal_for_buying_a_vector_impedance_analyzer_via_juul
** benny of accounting WG says buy it
** jenny ++
** mai +++
* Cheaper 4G hotspot setup -
** https://sudoroom.org/wiki/Mesh/29_10_2019#proposal_for_mini_solar_node_via_juul
** benny of accounting WG says buy it
*** also down to help document the setup
** ++ jenny

== disaster.radio update ==
* one core need right now is help finding best quotes for components - trying to keep nodes to >$50/ea - solar panels, lithium-ion-phosphate batteries
** steven dunnoford (of freeradio.org) would probably help for $$, does this all day
* sheets of pcb that don't have copper on them, so we can use them as canvasses for copper tape ant
* will be making proposals to fund juul and fitz for engineering work, mai and jenny for grantwriting/fundraising

=== When's the Meet-Up This Monennasth? ===
* What: swag making party
* When: Sunday Nov 9 2-4pm
* Where:
* Who:
** Bottomliners:

== Check Ins: Action Items & Active Projects ==
Check https://trello.com/b/wBKTQKDs/active-projects for Blocked items.
*
*

== Trello Boards ==
* Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications
* Node Mounts: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* Bugs & Technical: Github: https://peoplesopen.net/issues, https://peoplesopen.net/learn/development/
* Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/10_December_1815

== Wrap-up 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_MONTH_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/22 10 2019

2019-10-31T18:29:17Z

Bennlich: Created page with "'''People's Open Network Weekly Meeting - 22 October 2019 7:30pm-9pm''' * https://omnicommons.org/wiki/Safer_Space_Policy === Agenda === * Introductions and Meeting Roles (15..."

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

=== Agenda ===
* Introductions and Meeting Roles (15 mins)
* Announcements and Upcoming Events (10 mins)
* Check Ins: Action Items & Active Projects (30 mins)
* Check in on ongoing projects (15 mins)
* Discussion items (10 min)
* Wrap-up meeting (5 min)

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question:
* jenny-she/her- involved since 2013
* mai - involved since 2017 - been doing more organizing side of things, interested in technical side more
*asheem - hardware expert/interest
* johnmark - he him they - wants to work on os
*michael - analog person in a digital world; wizard
*mark - involved since beginning- software-solar nodes
*null - (he/him) first meeting in a while . did inventory
*tyler - ham radio operator. likes electronics, challengs
* dan/radar - ham radio. electronics, hardware
* lauren - 2nd meeting here. interested in long range radio stuff
* seth - he/him/they, been around for a year or so, has done node mounts and more recently been tabling

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

== Announcements and Upcoming Events ==

== Reportback on Emergency Fair ==-
* Distributed over 100 brochures and talked with dozens of primarily Berkele residents interested in and engaged with local neighborhood organizing for disaster resilience.
* Advised to "strike while iron is hot" as many Bay Area residents are currently reacting to the PG&E power shutoffs, wildfire and earthquake risks, and shitty treatment by Comcast (who recently cut power to dozens of residents in the Berkeley Hills without prior notice).
* Met a woman, Nikki, representing Gov. Newsom's initiative funding to the total of $50million for "disaster preparedness and peer-to-peer networking" nonprofits, who seemed confident in funding our projects (Jenny contact).
* BeCERTAINN is a Berkeley GMRS repeater network group we should connect further with. Eve made contact. More: https://www.berkeleyside.com/2018/02/01/berkeley-neighbors-seek-to-widen-grassroots-emergency-radio-system
* Chatted w/ Ivan - longtime sudoroom comrade who works in the library system - about deploying a disaster.radio testbed in Tiburon. They are considered a sort of testbed and this could be an example to other library systems that are more slow-moving , such as Oakland. Jenny & Ivan to collaborate on a Google doc, with imminent invite to present to the board!
* Many email signups and interest in attending meetups and/or workshops!
* Workshop on resiliency hubs that Ajay went to - working with community gardens, NorCal Resiliency Network -

== Check Ins: Action Items & Active Projects ==
Check https://trello.com/b/wBKTQKDs/active-projects for Blocked items.

= Design/print a banner for tabling events proposal from seth / mai / monica =
https://www.loomio.org/d/T7WnSVEz/proposal-design-print-a-banner-for-tabling-events

Approved!

== proposal for mobile solar hotspot node @ People's Park (juul) - https://www.loomio.org/d/P2piLKRI/proposal-buy-equipment-for-pole-mounted-solar-powered-homeless-internet-node from juul ==
https://www.loomio.org/d/P2piLKRI/proposal-buy-equipment-for-pole-mounted-solar-powered-homeless-internet-node
* 6 people approved from Loomio
* juul: maybe there's a cheaper solution

== proposal for mini solar node via juul ==

Another prototype but this one lighter weight, lower power and easier to install.
It uses the existing 4G wifi hotspots we got from mobile citizen.

* Flexible and light-weight solar panel: $50
* Solar charge controller: $30
* Li-ion high capacity battery $50 (probably less actually)
* 4G and WiFi antennas and pigtails: ~$140
* Case: ~$50
* Total: ~$320

< $500 - just needs approval from finance wg folks

== mini-proposal for buying a vector impedance analyzer via juul ==

It will allow us to quickly check if an antenna is good for a specific frequency, so we can DIY antennas and test them as we bend and snip. Works for LoRa and 2.4 GHz wifi frequencies but not 5 GHz wifi.

$180 https://www.ebay.com/itm/N1201SA-UV-RF-Vector-Impedance-ANT-SWR-Antenna-Analyzer-Meter-Tester-USA-Ship/352693851203

< $500 - just needs approval from finance wg folks
* Mai: I approve this
* jnny +1
* null +1

== funding for emergency prep - proposal due asap (jenny) ==
"As we spoke Saturday at the emergency preparedness fair in Berkeley, the Center on Disability at the Public Health Institute has been awarded a grant by the California Governorâ€™s Office of Emergency Services (Cal OES) to provide emergency preparedness training and resources to vulnerable populations through local community-based organizations (CBOs) in Alameda county. The grant will engage a total of 250,000 individuals with Access and Functional Needs through local CBOs in Alameda county through December 2020.

I have attached a Request for Proposals (RFP) and instructions on how to apply for this grant. We think you may be a right candidate for this grant. Please disregard the application dateline we are still taking application. Also, do not be afraid of the total number of people to reach. The agreement is set up so that you will be paid for the number of people you engage up to the maximum of 10,000. So even if you are aiming for 3,000 or less, the payment structure still works. We would like to keep the agreement saying 10,000, because when we get together, and throughout the project period, we will be working with you to maximize the number of people you can reach.
Please feel free to contact me if you have any question. We look forward to working with you."

== disaster.radio prototype (juul/jenny/mai/fitz) ==
https://github.com/LilyGO/TTGO-LORA32-V2.0
$30-40

Next steps:
* New version's main improvement will be 2 LoRa radios to improve meshing capability
* Want to experiment with at least two antennas on a board
* Switching from ESP8266 -> ESP32
* Improving communication between browser and chip
* haven't started working on multi-radio meshing
* handsets powered by USB
* compatability with Outernet (ham project)

Need help with:
* need support with board layout
** asheem and jm interested in helping
* mechanical engineering - enclosure, water/weatherproofed, attracting max sun but also cooling the battery, temperature probe, maybe some air holes to enable cooling from the side?
** shutoff happens at 45 degrees centrigrade - hard weather limitation -
** getting quotes for different possible solutions with both Lithium Ion and Lithium-Ion-Phosphate batteries
** asheem can donate some cycles to this
* explore different solar panel options, compare quotes

Required features
* shutoff happens at 45 degrees centrigrade
* water/weather proof enclosure
* multi-radio meshing
* battery - design that can be used with lithion ion, or lithion ion phosphate battery

Action Items:
* Acquire quotes and post to wiki on Github
** Solar panels
** Batteries
** Enclosure materials

= breakout groups =
* people's open overview / onboarding
* disaster.radio hack sesh

== Trello Boards ==
* Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications
* Node Mounts: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* Bugs & Technical: Github: https://peoplesopen.net/issues, https://peoplesopen.net/learn/development/
* Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/24_September_2019

== Wrap-up 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_MONTH_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/Accounting

2019-10-30T03:25:15Z

Bennlich: /* Purchase Guidelines/Procedures */

The Sudo Mesh Accounting Working Group meets every 2nd and 4th Tuesday from 5-6:30pm.

== Make a Purchase Request ==
[https://peoplesopen.net/buystuff Purchase Requests]

== Purchase Guidelines/Procedures ==
The current guideline comes from a proposal made during the [[Mesh/5_June_2018|June 5 Tuesday meeting]]. There are three purchase categories:
* Up to $500 each Accounting WG member can spend on the card without approval, with their discretion.
* Above $500, you need pre-approval from Accounting WG (see [[#Make_a_Purchase_Request]]).
* Above $2000 we need approval from 5 stewards via signature/loomio/email consent.

== Current Accounting Working Group Members ==
* Robb
* Mai
* Ben (eenblam)
* Bengo
* Grant
* Benny
* Marc

== How to join the Accounting WG ==
Come to an accounting working group meeting and get consensus from the current accounting working group members! (There will probably be an expectation that you have demonstrated some amount of commitment to the project.)

= Meeting Minutes Archive =
<DynamicPageList>
category = Mesh/Accounting
order = descending
</DynamicPageList>

Mesh/Minutes

2019-10-30T02:59:10Z

Bennlich:

2018-09-12T19:43:48Z

Bennlich:

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

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/11_September_2018|2018-09-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[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]
|
|}