Skip to content

Instantly share code, notes, and snippets.

@otakup0pe

otakup0pe/mounting-workshop.md

Last active February 5, 2018 02:08
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save otakup0pe/b960646d3f6b41927dbab2f00a6bb24a to your computer and use it in GitHub Desktop.
Save otakup0pe/b960646d3f6b41927dbab2f00a6bb24a to your computer and use it in GitHub Desktop.
Download ZIP
Mesh Workshop Notes
Raw
mounting-workshop.md

Mounting Workshop

Overview / Errata

  • Where do you want to mount things? Where is your endpoint?
  • Where do you organize your equipment / tools
  • How are you going to do this?
    • Do you have rooftop access
    • Is tehre an HOA or zoning issue
  • BYOI is for the theory and the process and the concept wheras peoplesopen is the local implementation
  • Who are you doing this with - try and make sure there is someone who has done this before with you
  • Periodic safety training at sudoroom.
    • Build a checklist
    • Basics - watch out for electric cables, ladder safety, closed toe shoes
    • Borrow best practices from OSHA guidelines
  • Document a site install some time. Make sure to seek consent prior to actually doing this.
  • Check out battery powered POE injectors. "u-installer" and also USB-POE converters (running off a laptop or battery)
  • After the installation is done, the property owner owns the equipment. The equipment is effectively donated in exchange for a suggested donation and helping provide the mesh.
    • There should be some kind of explcit wording about how this is done
    • Three categories
      • Completely willing do do it themselves
      • Willing to do it themselves after a workshop
      • Not willing to do it themselves
  • Suggested donations
    • $20 for the mesh routers
    • $60-$80 for the node2node
  • Long term administration - there are three developers who can access all nodes which have not had the default access removed
    • They are able to do "patch upgrades" (discuss after)
    • Remote logging needs to be explicit
  • Patch management!
    • Ideally there would be some kind of OTA update process - this requires infrastructure
      • Unknown as to whteher remote flasihng can be done
    • There is some kinda patching which can be done over the air but seems limited to configuration changes
  • People can contact in case of issuesa
    • Mailing list
    • Potential desire for a voip answering line
    • Signal (group) but not many people use that
    • Gitter / Slack / Riotchat / Matrix / actually telling people about IRC
      • Preference for things which do not involve maintaining more infrastructure
  • Build up screenshot history when flashing routers
  • Flashing party to ensure there are plenty of routers ready to go
  • Update wiki/docs to be more clear about the network topology.
    • Exit nodes
    • How your own internet connection is uesd (if it is)

Crimping

  • Having multiple sets of tools can help create an assembly line.
    • Example - wire snips, crimpers

Flashing

  • Flash routers prior to getting on site. Running the makenode aspect is optional prior to being on site, but is recommended.
  • Configuration involves a bunch of details that will vary site to site such as
    • Contact information
    • Bandwidth limits
  • Test after you have flashed.
    • Also with makenode
    • Can you run makenode multiple times without re-flashing?
  • Extedner nodes are done with an ubiquity thing, so telnet / tftp
  • Mesh nodes are done with dropbear / sftp
  • In order to upgrade the extender nodes need to downgrade AirOS prior to upgrading
  • Make sure you have the right power adapter for your node. Pay attention to both not only polarity but also voltage/amperage
  • Make sure you download the right firmware for your router
  • peopelsopen.net/walkthrough
  • Once you've downloaded the firmware, reset the modem. Hold down the reset button generally.
  • Update wiki docs to include the "blink patterns" that show up during flashing on a N600
  • Put the router into "Restore mode" (with a N600 that is by holding down the button until the blue light comes on)
  • Plug into any of the "non yellow" ports for a post factory default update. For non N600 just make sure you are plugged into the LAN
  • It is expected that once the N600 has been properly flashed that the connection to the firmware page will drop
  • The default network for the sudowrt firmware is different than in the N600 recovery mode
  • Note that when you connect to the freshly flashed system there will be a warning about the ssl cert (probably because it's self signed)
    • Maybe restrict the admin page to the private network
  • Update wiki to refer to installing build-essential not just gcc
  • The makenode process will request an IP from some managed infrastructure and then will update the router
    • For this process it is important to be plugged into the right node
    • Prior to specifying the bandwidth you may wish to run a speedtest to see what your connection is
  • Now let's flash the extender!
  • If it is a nanobridge received as a donation from monkeybrains then it has been reset to defaults. Should always test before using / going on site tho.
  • Key difference with the extenders is they are POE
  • First step is to determine which version of AirOS exists
  • Set the proper manual local ip address and login to the AirOS page
    • Note that you will need to ignore the self signed cert warning
  • Need to be on v6.0.3 XM - this is very important
    • If you are on version 6.0.4 XM then you must downgrade via CLI
  • all of the extender firmwares can be found on build.sudomesh.org
  • You then should be able to log back into the router but note that there will be another self signed cert warning
  • Note that the some POE injectors have their own reset button
  • After the flash is done note that unlike the home nodes there is no dashboard, there is an empty directory index tho
  • You should be able to see the thing via the CLI on a home node tho
  • Should see messages in /var/log/messages about DHCP ACK's
  • At this point you should be able to ping the extender node itself from other parts of the mesh

Mounting - prep

  • Try and make sure to have everything you need prior to leaving
    • Cable testers
    • Rattle gun / hammer drill - this will depend on what you are mounting to
    • Extra bridge / router
  • Scout the location! IS there actually access to the roof and line of sight to the other end. Walk person through process, and seek consent for expected changes.
  • Is the property owner OK with the installation, insurance, etc
  • Is there a good place to mount the jpole / mast. Keep in mind extreme weather events.
  • Do you have enough people? Three to four people would be good. Two would be minimum. Too many can get chaotic.
  • You should be able to see a peoplesopen node2node ssid
  • Use existing GIS / Lidar data (how dow access it?)

Mounting - onsite

  • List of pending mount points https://peoplesopen.net/sundays (this should be locked down)
    • Tracks people who are waiting to have mounts
    • Also tracks people who are willing to help (sometimes)
  • It is a good idea to have someone who has done this before with you, tribal knowledge, etc
  • Two people working on the actual install, one as a spotter, one to engage the person on site (social acculturation)
    • Ideally one of the people would have participated in the scouting
  • Walk property owner / representative through what will happen. Seek consent (again) prior to modifying property in order to confirm.
  • Test kit once again prior to actually mounting
    • Both the mesh router and backhaul kit
  • Plot the cable run. Figure out how you are going to get from the mast to the hole into the house (through a wall, not a roof) and then start crimping.
  • Keep in mind max cat5 lengths - might differ for poe vs non (citation needed). Generally aim for 300' max. Use shielded cable outside.
    • Can often crimp one end first before begining the run
    • Keep 5-10' extra (also measure twice)
    • Leave a drip line (curve down) where the cable goes into the house (help reduce water damage)
    • Maybe use conduit / squareish cable covering (panduit)
  • If you are crawling around in peoples attics then probably wear a N95
  • Note that when you install extenders, the POE sheath should be pointing down. Also the LED's should not be pointing up unless you want birds to peck out the LED's
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment