├── .gitignore ├── .hugo_build.lock ├── Dockerfile ├── LICENSE ├── README.md ├── archetypes └── default.md ├── assests └── diagram_source │ ├── Omni-only_Install.drawio.gz │ ├── README.md │ └── typical_install_Litebeam_Omni.drawio.gz ├── config.toml ├── content ├── _index.md ├── diagrams │ ├── _index.md │ ├── typical_install_Litebeam_Omnitik.md │ └── typical_install_Omni_Only.md ├── diy │ ├── _index.md │ └── troubleshooting.md ├── firmware │ ├── _index.md │ ├── custom.md │ ├── mikrotik.md │ ├── mikrotik_netinstall_recovery.md │ └── ubiquiti.md ├── glossary │ └── _index.md ├── hardware │ ├── 60ghz.md │ ├── LTU.md │ ├── _index.md │ ├── chromebook.md │ ├── config.md │ ├── epr6.md │ ├── ethernet.md │ ├── liteap.md │ ├── litebeamac.md │ ├── mikrotiknetpower15fr.md │ ├── mikrotikomnitik5ac.md │ ├── mikrotikpowerboxpro.md │ ├── mikrotikspecifics.md │ ├── newHardware.md │ ├── nsm5.md │ ├── sxtsqg5acd.md │ ├── tplink.md │ └── unifi-ap.md ├── installs │ ├── Crimping.md │ ├── _index.md │ ├── documents │ │ └── Installation_Member-Form.pdf │ ├── equipment.md │ ├── etiquette.md │ ├── fiberSafety.md │ ├── fiberSplicingPresentationNotes_07192022.md │ ├── fiberSplicingTutorial.md │ ├── fiberToTheApartment.md │ ├── install-wiki.md │ ├── linknyc.md │ ├── memberform.md │ ├── nn.md │ ├── panoramas.md │ ├── problems.md │ ├── query.md │ ├── safety.md │ └── surveys.md ├── intro │ ├── _index.md │ ├── additional-resources.md │ ├── gettingstarted.md │ └── typical Installs.md ├── networking │ ├── 10-69-net-network.md │ ├── _index.md │ ├── bgp.md │ ├── classes.md │ ├── dns.md │ ├── hubs.md │ ├── ipmappingidea.md │ ├── mesh.md │ ├── nn.md │ ├── ntp.md │ ├── ospf.md │ ├── peering.md │ ├── supernode-architecture.md │ ├── vpn.md │ ├── vpnl2tpipsec.md │ ├── vpnl2tpipsecid.md │ ├── vpnwireguard.md │ └── vpnwireguardospf.md ├── nodes │ ├── Grand Street.md │ ├── _index.md │ ├── hub-231-SunsetParkLibrary.md │ ├── hub-231-sunsetparklibrary │ │ └── nycmesh-231-SunsetParkLibrary-drawing.pdf │ ├── node-1340.md │ ├── supernode1.md │ ├── supernode2.md │ ├── supernode3.md │ └── supernode4.md ├── organization │ ├── _index.md │ ├── culture.md │ ├── documents.md │ ├── outreach │ │ ├── 2019-08 One page flyer.pdf │ │ ├── 2019-08-One-page-flyer.pdf │ │ ├── Brochure.pdf │ │ ├── GeneralSticker.png │ │ ├── MeshQRCode.png │ │ ├── NYCMesh_ThankYou.pdf │ │ ├── NYC_Mesh_Brochure_01.jpg │ │ ├── NYC_Mesh_Brochure_02.jpg │ │ ├── NYC_Mesh_Member_Guide.pdf │ │ ├── NYC_Mesh_Member_Guide_print.pdf │ │ ├── NYC_Mesh_Trifold_5.17.23.pdf │ │ ├── PowerSupplySticker.png │ │ ├── Priorities-One-Pager.pdf │ │ ├── SiteSurveyLetter-Community-Template.pdf │ │ ├── TEMPLATE - Landlord Letter .docx │ │ ├── building-leaflet.pdf │ │ ├── building-leaflet.rtfd.zip │ │ ├── building-leaflet.rtfd │ │ │ ├── TXT.rtf │ │ │ └── nycmesh-logo.png │ │ ├── card.png │ │ ├── church.pdf │ │ ├── cut-the-cord.pdf │ │ ├── flyer-bw.jpg │ │ ├── flyer-chinese.jpg │ │ ├── flyer.jpg │ │ ├── index.md │ │ ├── leaflet-bw.pdf │ │ ├── leaflet-rtfd.zip │ │ ├── leaflet-rtfd │ │ │ ├── leaflet b&w.rtfd │ │ │ │ ├── TXT.rtf │ │ │ │ └── splash-b&w.png │ │ │ └── leaflet.rtfd │ │ │ │ ├── TXT.rtf │ │ │ │ └── nycmesh-logo.png │ │ ├── logo.png │ │ ├── logo.svg │ │ ├── meshmail.pdf │ │ └── nycmesh buzzcard │ │ │ ├── nycmesh-bizcard-02-outlined.pdf │ │ │ ├── nycmesh-bizcard-02.pdf │ │ │ ├── nycmesh-flyer-3up-03.pdf │ │ │ ├── nycmesh-stickers-2.63x1-outlined.pdf │ │ │ └── nycmesh-stickers-2.63x1.pdf │ ├── plan.md │ ├── protecting.md │ └── workflow.md ├── security │ ├── _index.md │ └── ca.md ├── services │ └── _index.md └── software │ ├── _index.md │ ├── nsm5-flash.md │ └── watchdog.md ├── layouts ├── _default │ ├── baseof.html │ ├── section.html │ └── single.html ├── index.html └── partials │ ├── footer.html │ ├── github.html │ ├── header.html │ ├── join.html │ ├── sidebar.html │ ├── timestamp.html │ └── title.html ├── netlify.toml └── static ├── admin ├── config.yml └── index.html ├── android-chrome-192x192.png ├── android-chrome-512x512.png ├── apple-touch-icon.png ├── browserconfig.xml ├── css ├── main.css └── tachyons.min.css ├── download ├── LiteAP.cfg ├── WA-788A206CD449.cfg ├── lbe-LR.cfg ├── liteap.html ├── mesh-watchdog.sh ├── sn1.cfg ├── sn1.html ├── sn2.cfg └── sn2.html ├── favicon-16x16.png ├── favicon-32x32.png ├── favicon.ico ├── img ├── diagrams │ ├── Omni-only_Install.png │ └── typical_install_Litebeam_Omni.png ├── equipment │ ├── RJ45.jpg │ ├── batterypack.jpg │ ├── blank.jpg │ ├── boot.jpg │ ├── cable staples.jpg │ ├── cable.jpg │ ├── cablestripper.jpg │ ├── cabletester.jpg │ ├── chargedcellphone.jpg │ ├── cobalt.jpg │ ├── coldweather.jpg │ ├── concnail2.jpg │ ├── concscrew.jpg │ ├── concscrew_field.jpg │ ├── crimper.jpg │ ├── drill.jpg │ ├── edgepoint.jpg │ ├── electape.jpg │ ├── ethernetadapter.jpg │ ├── firstaid.jpg │ ├── garbsmall.jpg │ ├── hammmer.jpg │ ├── handtruck.jpg │ ├── hexsocket.jpg │ ├── hoseclamp_large.jpg │ ├── hoseclamp_large_field.jpg │ ├── hoseclamp_small.jpg │ ├── hoseclamp_small_field.jpg │ ├── j pipe.jpg │ ├── jpipe_field.jpg │ ├── l pipe field.jpg │ ├── l pipe.jpg │ ├── laptop.jpg │ ├── masonrybit.jpg │ ├── outdoorrouter.jpg │ ├── patchcable.jpg │ ├── phillips.jpg │ ├── pliers.jpg │ ├── poe.jpg │ ├── safetyglasses.jpg │ ├── scissors.jpg │ ├── sealant.jpg │ ├── sun protection.jpg │ ├── tinybroom.jpg │ ├── tplink.jpg │ ├── visegrip.jpg │ ├── washer.jpg │ ├── watersnack.jpg │ ├── wd40.jpg │ ├── weatherstrip.jpg │ ├── wrench.jpg │ ├── ziptie.jpg │ └── ziptie_field.jpg ├── ethernet │ └── T-568B.gif ├── hardware │ ├── 60ghz │ │ ├── AF60.png │ │ ├── AF60LR.png │ │ ├── AF60_LR.png │ │ ├── GBE-Plus.png │ │ ├── GBE.png │ │ ├── GBELR.png │ │ ├── LHG.jpg │ │ └── ML1.jpg │ ├── AF60.png │ ├── mikrotik_netpower15fr.jpg │ ├── mikrotik_omnitik5poeac_front.jpg │ ├── mikrotik_omnitik5poeac_ports.jpg │ ├── mikrotik_powerboxpro.jpg │ ├── mikrotik_sxtsq5ac.jpg │ ├── uap │ │ ├── uap-ac-m-pro.jpg │ │ └── uap-ac-m.png │ ├── ubiquity_edgepointr6_front.png │ ├── ubiquity_edgepointr6_ports.png │ ├── ubiquity_liteap.png │ ├── ubiquity_litebeam5acgen2.png │ └── ubiquity_nanostationm5.png ├── icon-hires.png ├── image_from_ios.jpg ├── installs │ ├── fiberSafety │ │ ├── chair_scrap_1000x1000.JPG │ │ ├── scrap_across_table_1000x1000.JPG │ │ └── table_scrap_closeup_1000x1000.JPG │ ├── fiberSplicingTutorial │ │ ├── 01_strip_12cm_outerjacket_SWS.JPG │ │ ├── 02_strip_2cm_innerjacket_SWS.JPG │ │ ├── 03_position_SWS_in_cleaver_closeup.JPG │ │ ├── 04_position_SWS_in_splicer.JPG │ │ ├── 05_strip_5cm_outerjacket_2cm_innerjacket_SWOS.JPG │ │ ├── 06_position_SWOS_in_splicer_closeup.JPG │ │ ├── 07_fiber_fused.JPG │ │ ├── 08_optical_power_meter_1550nm_reading_neg320dBm.JPG │ │ ├── 09_place_fused_fiber_with_shrinksleeve_in_heating_compartment.JPG │ │ ├── 10_shrunk_sleeve_wrapping_bare_fiber.JPG │ │ ├── 11_fused_cable_on_ruler_15cm_between_outerjackets.JPG │ │ ├── cleaver_pads_under_ruler.JPG │ │ ├── edu_template.JPG │ │ ├── shrinksleeve_on_ruler.JPG │ │ └── splicer_measurement.JPG │ └── wallONT.jpg ├── logo.png ├── logo.svg ├── ltu │ ├── Speed-infographics_1328x792.jpg │ └── nycmesh-1340-LTUsectorwest.png ├── nsm5 │ ├── bracket-200.jpg │ ├── nanobracket.jpg │ ├── pipe.jpg │ ├── roof-87.jpg │ ├── tree.jpg │ ├── ubiquiti-universal-mount.jpg │ ├── ubiquiti-window-wall-mount.jpg │ ├── velcro.jpg │ ├── wall-201.jpg │ ├── wall.jpg │ ├── window-cup-inside.jpg │ ├── window-cup-outside.jpg │ ├── window-velcro-off.jpg │ ├── window-velcro-on.jpg │ ├── windowwall.jpg │ └── windowwall2.jpg ├── nycmesh-1340-coverage.png ├── nycmesh-1340-enclosure-0.jpg ├── nycmesh-1340-enclosure-1.jpg ├── nycmesh-1340-enclosure-2.jpg ├── nycmesh-1340-mounting.png ├── nycmesh-1340-powerline.png ├── nycmesh-1340-prototype.png ├── nycmesh-1340-schematic.jpg ├── nycmesh-1340-view.png ├── nycmesh-1340-wide-area-ap.png ├── nycmesh-1340-wide-area-station.png ├── nycmesh-1340-wide.jpg ├── nycmesh-1934-Panorama.png ├── nycmesh-1934-Panorama2.png ├── nycmesh-1934-diagram.png ├── nycmesh-1934-fiber1.png ├── nycmesh-1934-fiber2.jpg ├── nycmesh-1934-fiber2.png ├── nycmesh-1934-fiber3.png ├── nycmesh-1934-fiber4.png ├── nycmesh-1934-lightpole1.png ├── nycmesh-1934-lightpole2.png ├── nycmesh-1934.png ├── nycmesh-231-SunsetParkLibrary-DCBox.jpg ├── nycmesh-231-SunsetParkLibrary-EastMast.jpg ├── nycmesh-231-SunsetParkLibrary-NorthEast.jpg ├── nycmesh-231-SunsetParkLibrary-NorthWest.jpg ├── nycmesh-231-SunsetParkLibrary-SouthEast.jpg ├── nycmesh-231-SunsetParkLibrary-SouthWest.jpg ├── nycmesh-231-SunsetParkLibrary-WestMast.jpg ├── nycmesh-231-SunsetParkLibrary-building.jpg ├── nycmesh-231-SunsetParkLibrary-drawing.png ├── nycmesh-231-SunsetParkLibrary-rack.jpg ├── nycmesh-570-227-link-2.png ├── nycmesh-570-227-link.png ├── nycmesh-570-battery.png ├── nycmesh-570-coverage.jpg ├── nycmesh-570-radios.png ├── nycmesh-570-router.png ├── nycmesh-570-schematic.png ├── nycmesh-hubsandhoods.png ├── nycmesh-intersn-20180103a.png ├── nycmesh-intersn-20180103b.png ├── nycmesh-ospfexample.png ├── nycmesh-sn1-1.jpg ├── nycmesh-sn1-coverage.png ├── nycmesh-sn3-1.jpg ├── nycmesh-sn3-2.jpg ├── nycmesh-sn3-3.jpg ├── nycmesh-sn3-pano1-north.jpg ├── nycmesh-sn3-pano2-south.jpg ├── nycmesh-sn4-1.jpg ├── nycmesh-sn4-2.jpg ├── nycmesh-sn4-coverage.png ├── sitesafety │ ├── equipmentclosetoedge.jpg │ ├── lockingdoor.jpg │ ├── loosecables.jpg │ └── survey.jpg ├── supernodediagram-2017121501.png └── typicalInstall │ ├── 1unit.jpg │ ├── 2units.jpg │ ├── OmniAlone.jpg │ ├── diagram_lbeOmni_textside.jpg │ ├── diagram_lbeonly_textbottom.jpg │ ├── hub-1350.jpg │ ├── hub-greenpoint.jpg │ ├── hub-sn4.jpg │ ├── hub100AVA.jpg │ ├── lbe+Omni.jpg │ ├── lbe+OmniPipe.jpg │ ├── lbe+OmniPole.jpg │ ├── lbe+Omniwall.jpg │ ├── lbeinfrastructure.jpg │ ├── lbejpipe.jpg │ ├── lbejpipe2.jpg │ ├── lbelongpole.jpg │ ├── lbeventpipe.jpg │ ├── sxt-1.jpg │ ├── sxt-2.jpg │ └── sxt-3.jpg ├── mstile-144x144.png ├── mstile-150x150.png ├── mstile-310x150.png ├── mstile-310x310.png ├── mstile-70x70.png ├── safari-pinned-tab.svg └── site.webmanifest /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | public 3 | -------------------------------------------------------------------------------- /.hugo_build.lock: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/.hugo_build.lock -------------------------------------------------------------------------------- /Dockerfile: -------------------------------------------------------------------------------- 1 | FROM alpine:latest as builder 2 | WORKDIR /build 3 | ADD . /build/ 4 | RUN wget https://github.com/gohugoio/hugo/releases/download/v0.62.2/hugo_0.62.2_Linux-64bit.tar.gz 5 | RUN tar -xzvf hugo_0.62.2_Linux-64bit.tar.gz 6 | RUN ./hugo 7 | 8 | FROM nginx:latest 9 | COPY --from=builder /build/public /usr/share/nginx/html 10 | ENV NGINX_PORT 80 11 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # NYC Mesh Docs 2 | 3 | This repository contains an archived version of NYC Mesh documentation. It previously was used to generate the docs.nycmesh.net section of the website. The documentation has since been moved to the [NYC Mesh Wiki](https://wiki.nycmesh.net) and this respository is now unused. 4 | 5 | Continued edits to this repository will not be applied. It is maintained as a record and archive of the previous state of the docs prior to the move to the wiki. 6 | 7 | For more information, please see the [Wiki explanation page](https://wiki.nycmesh.net/link/169#bkmrk-page-title) or reach out in #website or #docs on slack for more information. 8 | -------------------------------------------------------------------------------- /archetypes/default.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "{{ replace .Name "-" " " | title }}" 3 | date: {{ .Date }} 4 | draft: true 5 | --- 6 | 7 | -------------------------------------------------------------------------------- /assests/diagram_source/Omni-only_Install.drawio.gz: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/assests/diagram_source/Omni-only_Install.drawio.gz -------------------------------------------------------------------------------- /assests/diagram_source/README.md: -------------------------------------------------------------------------------- 1 | All files needed to re-create diagrams go here. Please compress (gzip 7zip etc.) any base64-encoded files so the git diffs/logs are easier to read. 2 | 3 | app.diagrams.net, formerly draw.io, is used to create and edit diagrams with the `.drawio` extention. 4 | -------------------------------------------------------------------------------- /assests/diagram_source/typical_install_Litebeam_Omni.drawio.gz: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/assests/diagram_source/typical_install_Litebeam_Omni.drawio.gz -------------------------------------------------------------------------------- /config.toml: -------------------------------------------------------------------------------- 1 | baseurl = "" 2 | relativeurls = true 3 | languageCode = "en-us" 4 | title = "NYC Mesh Docs" 5 | pluralizeListTitles = false 6 | hrefTargetBlank = true 7 | enableGitInfo = true 8 | 9 | # Markdown config 10 | [blackfriday] 11 | fractions = false 12 | hrefTargetBlank = true 13 | [markup.goldmark.renderer] 14 | unsafe= true 15 | -------------------------------------------------------------------------------- /content/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Documentation" 3 | --- 4 | 5 | Hello and welcome to the documentation website for [NYC Mesh](https://nycmesh.net/)! 6 | 7 | ## About NYC Mesh 8 | 9 | We are a community network offering fast, affordable, and fair access to the Internet for all New Yorkers. By [joining](https://nycmesh.net/join) NYC Mesh, you can access the Internet while simultaneously helping your neighbors get better, safer Internet access, too. Adding an NYC Mesh connection to your apartment or building can serve as a backup Internet connection in case your commercial Internet service goes down. 10 | 11 | As a community network, city residents such as yourself take it upon themselves to maintain and grow the network. This means that in addition to accessing the Internet, you can also make friends, meet neighbors, and learn valuable technical and computer skills by participating in our active community, either in-person or online. We regularly host [face-to-face meetups](https://www.meetup.com/nycmesh/), and you can join our [Slack chat](https://slack.nycmesh.net/). Both are great places to ask questions and otherwise connect with our active community. 12 | 13 | ## About this Website 14 | 15 | The NYC Mesh Docs website is the central clearinghouse for technical information about our network. Here, we describe the implementation of specific [nodes]({{< relref "nodes" >}}), document [installation procedures]({{< relref "installs" >}}), and more. This website is not a networking tutorial, so readers are expected to have some basic familiarity with computer internetworking concepts to take full advantage of the material we present here, but we do strive to provide links to good educational resources for newcomers where it makes sense to do so. 16 | 17 | There are a couple of different ways that you can make use of this website. 18 | 19 | - **Like a book:** You can read the entire website "front to back." Use the navigation menu to proceed from one section to the next, in order. This will give you a good idea of how our network works and how you can help us improve and maintain it. 20 | - **Like a reference:** You can skip directly to a section that interests you, or use this website to look up answers to specific questions that you have. This comes in particularly handy during an install or when troubleshooting issues. 21 | 22 | Moreover, this website itself is part of the community network and is maintained by volunteers. That means you can help us improve it by adding missing information, clarifying confusing points, or even just fixing typos you notice while you're reading. To learn more about how you can contribute to and edit this website, see our [`docs` README](https://github.com/nycmeshnet/docs/blob/master/README.md) file. 23 | -------------------------------------------------------------------------------- /content/diagrams/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Diagrams 3 | weight: 900 4 | --- 5 | -------------------------------------------------------------------------------- /content/diagrams/typical_install_Litebeam_Omnitik.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Typical Node Install - LiteBeamAC + OmniTik5ac 3 | weight: 800 4 | --- 5 | 6 | The purpose of this diagram is to give a technical overview of the typical LiteBeam + Omnitik5ac install described in the [Typical Installations page]({{< ref "/intro/typical installs" >}}) - scenario 2

7 | 8 | **NOTES** 9 | 10 | * The last two octets of the 10.68.x.x/16 and 10.69.x.x/16 (mesh backbone) addresses [are determined by node number]({{< ref "/networking/10-69-net-network.md" >}}) 11 | 12 | * The last three octets of the 10.x.x.x/26 (member side of the OmniTik) network are also determined by node number and are calculated by the [OmniTik5ac config](https://github.com/nycmeshnet/nycmesh-configs/blob/master/Omnitik5AC/omni-poe-ether5.rsc.tmpl) on line 5. Each NYC Mesh LiteBeam/OmniTik installation has one of these unique /26 networks on the member side of its OmniTik. The OmniTik provides DHCP to this network, with the bottom *and top* 5 usable addresses being left out of the scope (for static assignment to home-routers, LiteBeam management etc). DNS is provided by 10.10.10.10. This 10.x.x.x/26 network is redistributed to the mesh backbone via OSPF. 13 | 14 | * [LiteBeam5AC config here](https://github.com/nycmeshnet/nycmesh-configs/blob/master/LiteBeam5AC/lbe-new-8_7_1.cfg.tmpl) 15 | 16 | * This diagram was created on app.diagrams.net (formerly draw.io). The diagram source is located in /assets/diagram_source/ at the root of this git repository 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /content/diagrams/typical_install_Omni_Only.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Omni-Only Install 3 | weight: 900 4 | --- 5 | 6 | The purpose of this diagram is to give a technical overview of an Omnitik5ac-only install. This type of install should only be done if it is impractical to also install a LightBeamAC (e.g. no line-of-sight to a hub). Both types of installations (with and without LiteBeamAC) are depicted in the [Typical Installations page]({{< ref "/intro/typical installs" >}}) - scenario 2

7 | 8 | 9 | 10 | **NOTES** 11 | 12 | * The last two octets of the 10.68.x.x/16 and 10.69.x.x/16 (mesh backbone) addresses [are determined by node number]({{< ref "/networking/10-69-net-network.md" >}}) 13 | 14 | * The last three octets of the 10.x.x.x/26 (member side of the OmniTik) network are also determined by node number and are calculated by the [OmniTik5ac config](https://github.com/nycmeshnet/nycmesh-configs/blob/master/Omnitik5AC/omni-only.rsc.tmpl) on line 5. Each NYC Mesh LiteBeam/OmniTik installation has one of these unique /26 networks on the member side of its OmniTik. The OmniTik provides DHCP to this network, with the bottom *and top* 5 usable addresses being left out of the scope (for static assignment to home-routers etc). DNS is provided by 10.10.10.10. This 10.x.x.x/26 network is redistributed to the mesh backbone via OSPF. 15 | 16 | * This diagram was created on app.diagrams.net (formerly draw.io). The diagram source is located in /assets/diagram_source/ at the root of this git repository 17 | 18 | 19 | -------------------------------------------------------------------------------- /content/diy/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: DIY & Troubleshooting 3 | weight: 900 4 | --- 5 | 6 | For a DIY ("do it yourself") install we recommend [joining our Slack group](https://slack.nycmesh.net/) where you can chat with us. 7 | 8 | There is a channel in Slack- [#diy-install-support](https://app.slack.com/client/T02MB96L1/CL7BDUTA7/thread/G0FS2EVSQ-1584108413.229000) where you can ask questions. We can guide you on what hardware to buy, and what is likely the best connection to a nearby antenna. 9 | 10 | For DIY, **you must still** [fill in our join form](https://nycmesh.net/join). This will give you an Install Number (or request number) which you will need when you are ready for an install to request a **Network Number** (or **NN**) in order to be able to configure your devices for your install. It will also get you in our system so we can give you advice and look for line-of-sight connections, as well as put you on the map. *(We are working at automating the process so you can use the Install Request number and the system will automatically allocate a Network Number for you. For now you need to request it via #diy-install-suport or via the email your received with your Request Install Number)* 11 | 12 | For a quick check of line-of-sight you can use our [line-of-sight tool](https://los.nycmesh.net). Put in your address and it will show you which hubs you might be able to connect to. 13 | 14 | Here is a [list of equipment we typically use](../installs/equipment/). Remember to use outdoor ethernet cable, and securely mount your antennas on j-pipes or secured masts. Masts should be strong metal as plastic PVC pipes will bend. 15 | 16 | Our general install advice is here in [the docs](../installs/) 17 | 18 | When you are ready, here's how to [configure](../hardware/config) your devices. 19 | 20 | We ask you, if you can, to support NYC Mesh with a [monthly subscription](https://nycmesh.net/donate). Donating helps maintain, operate, and expand NYC Mesh so, just like you, others can benefit from the network. 21 | -------------------------------------------------------------------------------- /content/diy/troubleshooting.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Troubleshooting" 3 | weight: 99 4 | --- 5 | 6 | 7 | ## First step. 8 | 9 | Make sure all the devices are powered on. 10 | You may have two power supplies, one to power your home WiFi router and a second to power the poe (power over Ethernet) which in turn power the device(s) on the roof. 11 | 12 | The poe is a device that power the devices on the roof through the Ethernet cable. 13 | 14 | If you have only a WiFi router, then make sure it is powered and connected to the Ethernet cable coming from the roof. 15 | If you also have a poe, make sure the right power supply power the right device. The power supplies are not interchangeable. They may have different Voltage and if plugged to the wrong device they may damage that device. 16 | 17 | When you test your connection. Connect your computer directly, using an ethernet patch cable, to the router, to bypass the WiFi, or directly to the poe bypassing the router altogether. You want to test the connection first, not the router nor the WiFi. An Ethernet connection is faster than a WiFi connection. 18 | 19 | ## Your Internet and WiFi Speeds 20 | ### What Internet speed is required for your activities? 21 | 22 | Several factors can affect your internet performance: WiFi router location, number of users, the hardware and age of your device(s), the device software (called firmware), and any applications running in the background of your computer. 23 | 24 | There is a perception that Internet services require a lot of bandwidth (speed). Recommended internet speeds for use of third-party products and services depend on the number of devices you're using. See the following speeds required for these common third-party products and services: 25 |

26 | -- Streaming HD 10 Mbps 27 | 28 | -- Skype Call HD 1.5 Mbps 29 | 30 | -- Video Gaming 3.5 Mpbs 31 | 32 | -- Twitch Gaming 4.5-6 Mbps 33 | 34 | -- Netflix 5 Mbps 35 | 36 | -- Amazon Prime HD 15 Mbps 37 |

38 | For more informations please refer to those services' website. 39 | 40 | 41 | ### WiFi Router Location 42 | 43 | If you’re connecting to the Internet via WiFi, make sure your router is placed as close to the middle of your home as possible, away from obstructions (such as cabinets) away from other electronic devices and off the floor. 44 | Wall, metal plate (air-vent), refrigerators or microwave ovens, reduce signal if not block it totally. Other electronic devices (microwave, TV, babymonitor, cordeless phone, etc...) can create interferences. Wi-Fi doesn’t do well around lots of water, either, so stay away from aquariums and domaestic water heater. 45 | 46 | ### Wifi band 47 | 48 | WiFi routers operate in different frequencies. The 5 GHz wireless frequency provides faster data rates at shorter distances and is typically much less "busy" than the 2.4 GHz wireless frequency. If wireless range is your priority, 2.4 GHz performs better than 5 GHz. But 2.4 Ghz is more subject to interferences. 5 GHz wireless frequency doesn’t penetrate solid objects nearly as well as the 2.4 GHz. 49 | A dual band router 2.4/5 Ghz usually perform better than a mono band 2.4Ghz router as your device (smartphone, laptop) picks up the best signal, 2.4 or 5 Ghz. 50 | 51 | Make sure your old or slow devices like printers, use the 2.4Ghz to free up the 5Ghz. 52 | 53 | - Note 1: WiFi 6 and 6 Ghz
54 | WiFi 6 referes to the new standard 802.11ax (or AX WiFi). It works on 2.4, 5, or the newly open band 6 Ghz. WiFi 6 ≠ 6 Ghz 55 | The WiFi 6 improvement will not only affect 5GHz networks, which the industry has largely shifted to, and which provide faster data on shorter distances; it will also make 2.4GHz networks faster, which are typically slower but better at penetrating solid objects like walls. 56 | 57 | - Note 2: the 5GHz band has nothing to do with 5G cellular service. 2 differents things, the latest refers to 5th Generation. 58 | 59 | ### Wifi channels 60 | 61 | Wifi operates on different channels (like cars on different lanes on a highway). Your neighbor's router may operate on the same channel as your router, creating congestions. Try to change your router Wifi channel. There are app that can scan the channels and tell you which is the less occupied. Channel occupation, just like road traffic, depends on time of day and may change from one day to the other, as your neighbors may just do the same, change channel. 62 | 63 | 64 | ### Test the performance 65 | It is a good idea to always use the same tool to test to be able to compare. We use [speedtest.net](https://www.speedtest.net/) against Pilot, NY. 66 | 67 | 68 | ### In video by Bright Side 69 | 70 | 71 | -------------------------------------------------------------------------------- /content/firmware/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Firmware" 3 | weight: 201 4 | aliases: ["/software/firmware"] 5 | --- 6 | 7 | This is a guide the the firmware we use for different vendor products. We are only using factory firmware with custom configs at the moment. 8 | 9 | Slack chat: [#software-firmware](https://nycmesh.slack.com/app_redirect?channel=software-firmware) -------------------------------------------------------------------------------- /content/firmware/custom.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Custom Firmware (old) 3 | weight: 0 4 | --- 5 | 6 | #### Old firmware Repositories 7 | 8 | Old firmware build instructions are in [our nycmeshfeed repo's README file.](https://github.com/nycmeshnet/nycmeshfeed/) 9 | 10 | - [lime-sdk](https://github.com/nycmeshnet/lime-sdk/) 11 | - [nycmeshfeed](https://github.com/nycmeshnet/nycmeshfeed/) 12 | - [network-profiles](https://github.com/nycmeshnet/network-profiles) 13 | 14 | 15 | 16 | -------------------------------------------------------------------------------- /content/firmware/mikrotik.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MikroTik Firmware 3 | aliases: ["/software/mikrotikfirmware"] 4 | weight: 999 5 | --- 6 | 7 | MikroTik routerOS 6 firmware is generally stable. We are currently using 6.49.6. 8 | 9 | **Do not use version 7 (not yet supported) or version 6.47/6.48/6.49.2 (occasional hangs) ** 10 | 11 | **routerOS 6** 12 | 13 | Download 6.49.6 [OmniTik (mipsbe) here](https://download.mikrotik.com/routeros/6.49.6/routeros-mipsbe-6.49.6.npk) and [SXTsq (arm) here](https://download.mikrotik.com/routeros/6.49.6/routeros-arm-6.49.6.npk) 14 | 15 | Remember that OmniTiks use the "mipsbe" firmware and SXT's use the "arm" firmware due to different processors. 16 | 17 | We have documented issues with 6.47/6.48/6.49.2 so don't use them. 18 | 19 | We have many omnitiks running 6.49.6 without any problem. 20 | 21 | 22 | **routerOS 7** 23 | 24 | Don't use it yet - it won't work! 25 | 26 | This has finally been released but it doesn't work with our configuration yet. We keep testing it as we are eager to deploy the newly added WireGuard. 27 | If you are interested in beta-testing the WG setup, post in the #software-firmware channel on Slack. 28 | 29 | If you need to downgrade, read the [instructions here](../../hardware/mikrotikomnitik5ac/) 30 | 31 | --- 32 | 33 | Mikrotik devices come in a variety of architectures and form-factors. Fortunately the firmware versioning and built levels are the same across all platforms. The main variant is the architecture, which might be a different chip for each device model. 34 | 35 | We currently use the stable version of RouterOS 6 (__6.49.6__) 36 | 37 | Below is a table of the 6.49.6 firmware for Mikrotik devices that are in the mesh: 38 | 39 | |Model|Architecture|Firmware link| 40 | |---|---|---| 41 | | OmniTik 5ac | MIPSBE | [Download](https://download.mikrotik.com/routeros/6.49.6/routeros-mipsbe-6.49.6.npk) | 42 | | SXTsq ac | ARM | [Download](https://download.mikrotik.com/routeros/6.49.6/routeros-arm-6.49.6.npk) | 43 | | hAP ac^2 | ARM | [Download](https://download.mikrotik.com/routeros/6.49.6/routeros-arm-6.49.6.npk) | 44 | | CCR Series | TILE | [Download](https://download.mikrotik.com/routeros/6.49.6/routeros-tile-6.49.6.npk) | 45 | | hAP mini | SMIPS | [Download](https://download.mikrotik.com/routeros/6.49.6/routeros-smips-6.49.6.npk) | 46 | | hAP lite | SMIPS | [Download](https://download.mikrotik.com/routeros/6.49.6/routeros-smips-6.49.6.npk) | 47 | 48 | ## Installing firmware 49 | * Login to your Mikrotik box Web UI ( CLI if you know how ) 50 | * Go to WebFig > Files section, upload the firmware file 51 | * Reboot the router 52 | * The firmware version is visible at the top of the Web UI, watch for the new version 53 | -------------------------------------------------------------------------------- /content/firmware/mikrotik_netinstall_recovery.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MikroTik Netinstall Recovery 3 | weight: 0 4 | --- 5 | 6 | ## How to resurrect a bootlooping OmniTIK with `netinstall` 7 | 8 | ### Symptoms 9 | 10 | OmniTIK boots up but continually reboots. The LEDs repeat the pattern: device boots up, power eventually turns blue, then 1-5 turn orange and reboots. Rinse and repeat. 11 | 12 | ### Solution 13 | 14 | Use `netinstall` to flash a fresh firmware on the router. This guide assumes Linux, though both Linux and Windows are supported. This should work for any RouterBOARD based device. 15 | 16 | - [ ] Install `netinstall` on your laptop from mikrotik, and make sure it is in your command line path 17 | - [ ] Download the [firmware](/firmware/mikrotik) you want to reset to (e.g. `routeros-mipsbe-6.47.8.npk`) 18 | - [ ] Plug the data end of PoE injector into your computer's ethernet (e.g. `enp0s13f0u2u4u5`) 19 | - [ ] Press and hold the reset button on the omnitik 20 | - [ ] Plug the poe+data end into ether1 of omnitik 21 | - [ ] Keep holding the reset button until LED 1 is solid orange, and the blue light has stopped flashing and is now off 22 | - [ ] Finally, run `netinstall` and reset the board: 23 | 24 | ``` 25 | ❱ netinstall -p ~/Downloads/routeros-mipsbe-6.47.8.npk -i enp0s13f0u2u4u5 26 | Using server IP: 192.168.88.2 27 | Starting PXE server 28 | Waiting for RouterBOARD... 29 | PXE client: CC:2D:E0:17:55:CB 30 | Sending image: mips 31 | Discovered RouterBOARD... 32 | Formatting... 33 | Sending package routeros-mipsbe-6.47.8.npk ... 34 | Ready for reboot... 35 | Sent reboot command 36 | ``` 37 | 38 | After all this, you should hear a few beeps indicating success. You can now try to connect via ether2 to configure it at 192.168.88.1 as normal. 39 | 40 | -------------------------------------------------------------------------------- /content/firmware/ubiquiti.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Ubiquiti Firmware 3 | weight: 800 4 | --- 5 | 6 | Ubiquiti firmware has some buggy versions that need to be avoided. In general never use a ".0" release. It is beta quality and will probably have serious bugs that may be fixed by .1 or .2 version. 7 | 8 | Ubiquiti have two very separate product lines with different firmware, AirMAX and UniFi 9 | 10 | **Don't use the latest firmware from Ubiquiti!** Use the stable versions below- 11 | 12 | **AirMAX** 13 | 14 | We are currently updating to 8.7.11 on most CPE (like the LiteBeams) 15 | 16 | Version notes: 17 | 8.7.11 (the latest) seems to be working and stable 18 | 8.7.7 and 8.7.9 are good 19 | 8.7.4 and 8.7.5 tend to crash 20 | 8.7.5 has a TDMA bug which causes performance to fail after a few days. 21 | 8.7.1 the management radio disconnects constantly 22 | 23 | Ubiquiti changed the signal to read 5db hotter in versions after 8.7.1, so a -50 24 | So a -55dB in the newer versions would be -60dB in 8.7.1 or earlier 25 | 26 | Download [8.7.11 here](https://dl.ui.com/firmwares/XC-fw/v8.7.11/WA.v8.7.11.46972.220614.0420.bin) 27 | 28 | **For sector AP's we use 8.5.12 for DFS stability** (or 8.7.1 if this is not an issue) 29 | 30 | Download [8.5.12 here](https://dl.ui.com/firmwares/XC-fw/v8.5.12/WA.v8.5.12.40181.190213.1104.bin) 31 | 32 | NEVER UPGRADE A SECTOR WITHOUT ASKING EVERYONE FIRST! 33 | 34 | We disable AirView on sectors to improve CPU performance 35 | 36 | 37 | **UniFi** 38 | 39 | We've found all versions after 4.3.20 to be buggy. Basically meshing broke in the later versions so your network will go down after a day or so, unless all of your AP's are wired. Not only will a meshed AP crash, it will take down the rest of the local network! 40 | 41 | Download 4.3.20 [here](https://dl.ui.com/unifi/firmware/U7PG2/4.3.20.11298/BZ.qca956x.v4.3.20.11298.200704.1347.bin) 42 | -------------------------------------------------------------------------------- /content/hardware/60ghz.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "60 GHz" 3 | --- 4 | 5 | 60 GHz is an unlicensed band that now has some cheap gigabit point to point (p2p) antennas that we are using. 6 | 7 | 60 GHz is extremely susceptible to "rain-fade", which is why it is not used in licensed spectrum 8 | 9 | Often these radios come with a 5GHz backup, which isn't really useful for bandwidth but it will keep your link online during rain. 10 | 11 | # Ubiquiti 12 | 13 | There's a very confusing range of Ubiquiti 60GHz. Basically there's dishes and enclosed headlight looking ones 14 | 15 | ## Ubiquiti Gigabeam 16 | 17 | 18 | - Price: $260 pair 19 | - no quoted range! (assume it's meant for neighboring buildings) 20 | - 5GHz backup: yes but not usable 21 | 22 | ## Ubiquiti Gigabeam Plus GBE-Plus 23 | 24 | 25 | This is a well-designed router that is small and reliable. We have a couple of these at our Rivington hub 26 | 27 | - Price: $360 pair 28 | - Range: "up to 1.5km" 29 | - 5GHz backup: no 30 | 31 | ## Ubiquiti Gigabeam GBE-LR 32 | 33 | 34 | - Price: $400 pair 35 | - Range: "long range"? probably means "up to 2km" like the af60 36 | - 5GHz backup: no 37 | 38 | ## Ubiquiti airFiber 60 39 | 40 | 41 | - Price: $600 pair 42 | - Range: "Long range, up to 2 km" 43 | - 5GHz backup: yes 44 | 45 | ## Ubiquiti airFiber 60 LR (dish) 46 | 47 | 48 | - Price: $800 pair (sold as pair) 49 | - Range: "Long Range, Up to 12 km" (hard to believe!) 50 | - 5GHz backup: no 51 | 52 | We are currently running two links with these. Grand to Navy Yard, and PH to 5283 53 | 54 | The Navy Yard link: 55 | 56 | - 2km and bandwidth decreases in the rain 57 | - "1751" capacity (they are adding up and down capacity together) 58 | 59 | The 5283 link: 60 | 61 | - 2.2km and works ok in rain 62 | - "1951" capacity 63 | - 5GHz: no 64 | 65 | 66 | ## MikroTik LHG 60G 67 | 68 | 69 | - Price $300 pair 70 | - Range 200m 71 | - 5GHs backup: no 72 | - Tested speed: 700 Mbps 73 | 74 | We originally installed these for 800m links but they will go down every time in heavy rain. 200m seems a good distance for them. It's a cheap way to connect neighboring buildings. We use these between the Grand St towers. 75 | 76 | ## IgniteNet Metrolinq One 60-19 77 | 78 | 79 | - Price: $500 pair 80 | - Range: 200m? 81 | - 5GHz backup: yes 82 | - Tested speed: 300 83 | 84 | We use these between Henry and Grand. It never got over 300 Mbps 85 | 86 | - The mount is extremely heavy and obviously designed for the larger antenna 87 | - The lights on the back aren't visible due to the mount 88 | - It is possible to mount on horizontal pipe but you only have ~15 degrees of movement 89 | - Bandwidth is about half of the cheaper Mikrotik 60Ghz 90 | - Maybe we should have used the larger 60 – 35 91 | - The backup 5GHz is strangely very low bandwidth (~20 Mbps) 92 | - The telescope is very good, and great for aligning 93 | - Everything is very well built and feels like a scientific instrument 94 | 95 | 96 | -------------------------------------------------------------------------------- /content/hardware/LTU.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Try the new LTU sector" 3 | aliases: ["/diy/LTU"] 4 | --- 5 | 6 | Ubiquiti has a new "technology" which is the successor to [AirMax](https://dl.ubnt.com/datasheets/airmax/UBNT_DS_airMAX_TDMA.pdf) , called [LTU](https://help.ui.com/hc/en-us/articles/360002759393-LTU-Frequently-Asked-Questions). 7 | (more about [AirMax](https://dl.ubnt.com/AirMax_ppt.pdf) ) 8 | 9 | LTU and AirMax are not compatible. You need a different device/antenna to connect to the LTU sector. 10 | 11 | We have one LTU sector mounted on the west side of [1340-Saratoga](/nodes/node-1340/). Try it.

12 | Here the approximate coverage.

13 | photo 14 | 15 |

16 | The sector is a [LTU-Rocket](https://www.ui.com/products/#ltu) radio and a [AM-5ac21-60](https://www.ui.com/airmax/airmax-ac-sector-antenna/) antenna. 17 | It is positioned about 260o azimut, and it's a 60o angle. 18 | 19 | We have one node using that new LTU sector right now. [944-Flo](https://www.nycmesh.net/map/nodes/944) 20 | It uses a [LTU LR](https://www.ui.com/products/#ltu) antenna and so far is better with a more stable bandwidth then the Litebeam Gen2 to a LiteAP it was using before. 21 | 22 | See the [LTU devices](https://www.ui.com/products/#ltu) available 23 | -------------------------------------------------------------------------------- /content/hardware/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Hardware" 3 | weight: 200 4 | --- 5 | -------------------------------------------------------------------------------- /content/hardware/chromebook.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: page 3 | title: "Chromebook" 4 | category: Hardware 5 | --- 6 | 7 | Chromebooks are good for installs as they are cheap and all you need is a browser and a terminal anyway. 8 | 9 | To get a standard terminal you have to put the Chromebook in developer mode. This will also erase your login info and any local data. 10 | 11 | * Turn the Chromebook off 12 | 13 | * Turn it on while holding esc and ⟳ (escape and reload) 14 | 15 | * Wait for the next screen that says something like "Chrome OS is missing or..." 16 | 17 | * Press Ctrl-D 18 | 19 | * Wait for next screen 20 | 21 | * Press enter 22 | 23 | The Chromebook should restart and you can sign is as guest or enter your gmail etc to set up the laptop. 24 | 25 | * ctrl-T to get a terminal 26 | 27 | * type `shell` at the prompt to get a standard shell 28 | 29 | The next time you start your Chromebook- 30 | 31 | * Press Ctrl-D to continue (don't press the spacebar!) -------------------------------------------------------------------------------- /content/hardware/ethernet.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Ethernet" 3 | aliases: ["/ethernet"] 4 | --- 5 | 6 | You must use black outdoor cable outside. Indoor cable will last about 6 months outside due to UV damage. We mostly use Ubiquiti ToughCable Pro CAT5. 7 | 8 | There is one commonly used standard for crimping ethernet: T-568B. (oO-gB-bG-brBR) 9 | 10 | ![window/wall install](/img/ethernet/T-568B.gif) 11 | [source](https://www.siongboon.com/projects/2006-03-06_serial_communication/) 12 | 13 | A straight cable will work as long as both ends are the same configuration, but to stop confusion we only use the standard T-568B, which is the most common one in this country. 14 | 15 | In 100base-T (100Mbps most old ethernet), orange is data transmit (pins 1 & 2) and green is receive (pins 3 & 6) pins 4,5,7,8 are not used for data. 16 | 17 | In 1000Base-T (gigabit ethernet) all pins are used for data. If pins 4,5,7 & 8 are not connected the speed falls back to 100Mbps. 18 | 19 | For Ubiquiti and Mikrotik 4,5,7,8 are used for 24 volt passive power over ethernet (POE). Pins 4 & 5 are positive and 7 & 8 are negative. Passive POE doesn't negotiate with the other device so it will always send power even if a wrong device is plugged in. If you plug a live POE cable into an adapter or some device that does not expect POE it can break. This is often how ethernet adapters and cable testers break! A cheap USB 100Base-T ethernet adapter will survive as it doesn't use the POE pins. 20 | 21 | There isn't a standard for passive POE so you need to check compatibility (which pins are used) if using a different manufacturer. 22 | 23 | For active POE there are standards PoE 802.3af, PoE+ 802.3at and PoE++ IEEE 802.3bt. Again you need to check which one to use. Active POE negotiates with the device so it shouldn't fry your cable tester. 24 | 25 | Ubiquiti POE is 24V DC, **half the voltage of standard (802.3af/at) 48V DC POE.** If you use standard POE you need to use a [Ubiquiti 8023af-adapter](https://store.ui.com/us/en/collections/uisp-accessory-tech-poe-surge-converters/products/ins-3af-i-g) 26 | 27 | Ethernet cables need to be shorter than 100m (300'). Longer than that you will have data loss and the POE voltage will drop too low. 28 | 29 | 30 | -------------------------------------------------------------------------------- /content/hardware/liteap.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Ubiquiti LiteAP Sector" 3 | --- 4 | The confusingly named LiteAP (LAP-120) is a very good, cheap 120' sector antenna. 120' means you need three to get a full 360'. It used to be called a LiteBeam 5AC AP LBE-5AC-16-120, and is still named that on parts of their website. 5 | 6 | We use it as a sector antenna for most hub and supernode installs. As with all Ubiquiti gear you need to flash it with the latest firmware first. 7 | 8 | The AC in the name is not 802.11ac, it is Ubiquiti's own protocol. These devices can only connect to other Ubiquiti "AC" devices like the LiteBeam we mount on everyone's roof. 9 | 10 | ![Ubiquity LiteAP](/img/hardware/ubiquity_liteap.png) 11 | 12 | Device specs are available at [ubnt.com](https://www.ui.com/airmax/liteap-ac/). 13 | 14 | The default IP is https://192.168.1.20/ with name:ubnt pwd:ubnt 15 | 16 | -------------------------------------------------------------------------------- /content/hardware/mikrotiknetpower15fr.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "MikroTik NetPower 15FR" 3 | --- 4 | 5 | The NetPower 15FR is an outdoor 16 ethernet ports Switch with PoE output on one port. Since the device has a waterproof outdoor case, you can mount it on a tower, or in other outdoor locations. 6 | 7 | It supports passive PoE input on 15 ports and passive PoE output on one. 8 | We successfuly used this device to Power one OmniTik POE 5 ac which in turn powered an SXTsq G-5acD and thus were able to connect 9 apartments to NYC Mesh. 9 | 10 | 11 | ![MikroTik PowerBox Pro](/img/hardware/mikrotik_netpower15fr.jpg) 12 | 13 | Device specs are available at [mikrotik.com](https://mikrotik.com/product/crs318_1fi_15fr_2s_out). 14 | 15 | -------------------------------------------------------------------------------- /content/hardware/mikrotikpowerboxpro.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "MikroTik PowerBox Pro" 3 | --- 4 | 5 | The PowerBox Pro is an outdoor five gigabit ethernet port router with PoE output on four ports. Since the device has a waterproof outdoor case, you can mount it on a tower, or in other outdoor locations. 6 | 7 | It also supports passive PoE input and passive or 802.3af/at PoE output. Ethernet ports 2-5 can power other PoE capable devices with the same voltage as applied to the unit. Less power adapters and cables to worry about! It can power 802.3at and af mode B compatible devices, if 48-57 input voltage is used. 8 | 9 | ![MikroTik PowerBox Pro](/img/hardware/mikrotik_powerboxpro.jpg) 10 | 11 | Device specs are available at [mikrotik.com](https://mikrotik.com/product/RB960PGS-PB). 12 | 13 | -------------------------------------------------------------------------------- /content/hardware/mikrotikspecifics.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "MikroTik Specifics" 3 | --- 4 | 5 | Mikrotik routers have a few interesting things to note in order to understand and use them well. This page documents those interesting pieces and might help clarify some things. 6 | This page will be referenced by other pages and should be Mikrotik general. 7 | 8 | ## Device variants 9 | 10 | ### License 11 | 12 | Mikrotik software usually requires a license, though all Mikrotik devices come with an internal license, which varies with the model. 13 | This router comes with a Level 4 license which is sufficient for its use. 14 | 15 | ### US vs International version 16 | 17 | The US versions of the OmniTik and SXTsq don't support the DFS range of 5GHz WiFi. We use the US version of the OmniTik. The US version of the SXTsq is not compatible with a LinkNYC kiosk. All LinkNYC kiosks are on DFS channels. 18 | 19 | ### PoE vs non-PoE 20 | 21 | There are models that both have PoE and do not. Be sure to buy a PoE model. 22 | 23 | ## Platform how-tos 24 | 25 | ### Reset 26 | 27 | To factory reset a mikrotik router, hold down the reset button (located near the PoE-in port), then plug in the power, until the main power ( or USR led ) light starts flashing, then release the button to reset RouterOS configuration (total 5 seconds). 28 | 29 | ### Connecting 30 | 31 | The initial IP address out of the box is 192.168.88.1, so set you computer’s local IP to something similar ( 192.168.88.5 ). The username is admin and there is no password. 32 | __Note: Many models have ether1 / Port 1 as WAN by default, you may need to connect your computer to a port besides Port 1 for initial configuration__ 33 | 34 | ### Configurations 35 | 36 | Mikrotik devices don't directly work well with the old "restore a file" method of configuration. Instead, you need to generate a script that, when run, alters the config from the default. Technically, yes, it's possible to restore a file, however, the format and ability to restore might change each version, for each devices, and depending what hardware is connected. 37 | 38 | Each device should have a config template which needs some blanks filled in. The result is a script that can be run to setup the device after a factory default. 39 | -------------------------------------------------------------------------------- /content/hardware/newHardware.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "New Hardware" 3 | --- 4 | 5 | ## Title goes here 6 | 7 | Description with [a link](https://google.com) 8 | -------------------------------------------------------------------------------- /content/hardware/tplink.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: page 3 | title: "TP-Link Indoor Router" 4 | category: Hardware 5 | --- 6 | 7 | An indoor router, connected by ethernet cable to the outdoor router, is required for an NYC Mesh member to connect their personal devices to the Internet. For volunteer-led installations, the install team will supply the new member with a [TP-Link Archer A6](https://www.tp-link.com/us/home-networking/wifi-router/archer-a6/) or a [TP-Link Archer A7](https://www.tp-link.com/us/home-networking/wifi-router/archer-a7/). 8 | 9 | ![alt text](https://i.imgur.com/d1S8Q60.png "TP-Link Router") 10 | 11 | 12 | ### Pre-Configuration Best Practices 13 | **For volunteer installers** 14 | 15 | Before configuring, ask the user member to tell you: 16 | 17 | * Whether they would like to use the TP-Link router we supply or their own router 18 | * A username and password for the router 19 | * An SSID and password for the home wireless network 20 | 21 | ### TP-Link Archer A6 or A7 Router Configuration Instructions 22 | **For volunteer installers and DIY installers** 23 | 24 | ![alt text](https://i.imgur.com/oq6yWHZ.png "TP-Link Router") 25 | 26 | 1. Plug the ethernet cable from the outdoor antenna/router into the TP-Link’s blue WAN port. 27 | 1. Plug the power adapter into the wall and the cable into the power socket of the router. The router will turn on automatically. 28 | 1. Connect the installation laptop to the router by plugging an Ethernet patch cable into the yellow LAN port or via Wifi (see the underside of the router for SSID and pwd) 29 | 30 | 1. Navigate to the router dashboard in an Internet browser. The Default IP address is **192.168.0.1** 31 | * Username: **admin** (or whatever it says on the underside of the router) 32 | * Password: **admin** (or whatever is says on the underside of the router) 33 | 34 | 1. Set up the guest WiFi to “**-NYC Mesh guest-**” (including the dashes). 35 | Navigate to “Guest Network” and set as follows: ![alt text](https://i.imgur.com/BXzdita.jpg "Guest Network Configuration Settings") 36 | 37 | 1. Set up the home WiFi. 38 | Navigate to Wireless > Basic Settings 39 | to set the home WiFi network SSID you wish to use and navigate to Wireless > Wireless Security to set the password. 40 | 41 | 1. Replace the router’s admin/admin login with a more secure username and password. 42 | Navigate to System Tools > Password and input a new username and password. 43 | 44 | 1. Please read [Obligations](https://www.nycmesh.net/faq#obligations) 45 | 46 | 47 | ### Optional TP-Link TL-WR841N Firmware Upgrade 48 | **For volunteer installers** 49 | 50 | If you have time you should pre-configure the router as much as possible, including upgrading the firmware to the latest version. To do that the router does not need to be connected to a network. It can be pre-configured following the above steps excluding point 1. 51 | 52 | 1. Download the latest firmware file [here for the A6](https://www.tp-link.com/us/support/download/archer-a6/#Firmware)or [here for the A7](https://www.tp-link.com/us/support/download/archer-a7/#Firmware). 53 | 1. Connect to **192.168.0.1** and log in with the username and password you set for the router. 54 | 1. Go to System Tools > Firmware Upgrade. 55 | 1. Click Choose File to locate the downloaded firmware file, and click Upgrade. 56 | 1. Setting the time is not a necessity but nice to do. Go to System Tools > Time Settings. You can use [apple NTP](http://time.apple.com), [pool.org](http://pool.ntp.org) and/or [Google](http://time1.google.com). 57 | 58 | 59 | ### Support 60 | **For volunteer installers and DIY installers** 61 | 62 | A Quick Installation Guide and User Guide can be downloaded [here for the Archer A6](https://www.tp-link.com/us/support/download/archer-a6/) and [here for the Archer A7](https://www.tp-link.com/us/support/download/archer-a7/). 63 | -------------------------------------------------------------------------------- /content/hardware/unifi-ap.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Unifi Access Points" 3 | --- 4 | 5 | We are using more UNIFI access points on installs these days. These devices are very frustrating to set up, so this document is designed to help. 6 | 7 | As of 2021 the latest firmware 4.3.28 has very short uptime (<30 days), so we are using a stable older version [4.3.20](https://dl.ui.com/unifi/firmware/U7PG2/4.3.20.11298/BZ.qca956x.v4.3.20.11298.200704.1347.bin) (copy this link) 8 | 9 | Never use 4.3.28 or later, as the device will go down and require a site visit to reboot! 10 | 11 | The devices are coming with very old firmware that isn't even compatible with the controller so step one is to SSH into the AP and upgrade it to 4.3.20. 12 | 13 | Adopting wirelessly doesn't work, so we adopt the AP to the controller wired before installing! 14 | 15 | After moving on site, you may need to ssh in and set-inform to tell it the address of the controller 16 | 17 | ## SSH firmware instructions 18 | [Here's Ubiquiti's instructions](https://help.ui.com/hc/en-us/articles/204910064-UniFi-Upgrade-the-Firmware-of-a-UniFi-Device#h_01F8GWSNHCB18N8Z2PKGDXEYDY) 19 | 20 | We usually download the 4.3.20 update and choose the "Updating without internet..." option using scp. 21 | 22 | ## Meshing 23 | 24 | We mostly install these devices with one wired connection for every two or three unwired ("meshed"). It's best to avoid more than one wireless hop. 25 | 26 | Wireless meshing basically doesn't work after version 4.3.20. Apart from later versions being unstable, when one goes down it can take down all the other meshed devices! We're in a very long conversation with Ubiquiti about this. 27 | 28 | ## UAP-AC-M (rabbit ears) 29 | 30 | 31 | - Price $100 (also comes in 3 packs and 5 packs) 32 | 33 | We've installed these at Clemente and they have proved to be reliable when running 4.3.20 34 | 35 | ## UAP-AC-M-PRO 36 | 37 | 38 | - Price $200 (also comes in 5 pack) 39 | 40 | We've installed these at Grand St and Vernon 41 | 42 | They are designed to mount on a wall. We've been mounting them on light poles which means creating your own mount (a lot of work!) 43 | 44 | They seem ok and we haven't had any completely fail yet. The case is just snapped together. I had one randomly come apart before installing. 45 | 46 | 47 | -------------------------------------------------------------------------------- /content/installs/Crimping.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "How to Crimp an Ethernet cable" 3 | aliases: ["/crimping"] 4 | --- 5 | 6 | Here are some helpful videos on crimping. Like nearly everyone we use [the T-568B standard](../../hardware/ethernet) 7 | 8 |
9 |
10 |
11 | 12 | 13 | Video 1
14 | 15 | 16 | 17 | Video 2
18 | 19 | -------------------------------------------------------------------------------- /content/installs/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Installs" 3 | layout: single 4 | aliases: ["/install"] 5 | --- 6 | 7 | The install docs have moved to a new location on the [Wiki!](https://wiki.nycmesh.net/books/install-maintenance-guides) 8 | Please follow the link to view them. -------------------------------------------------------------------------------- /content/installs/documents/Installation_Member-Form.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/installs/documents/Installation_Member-Form.pdf -------------------------------------------------------------------------------- /content/installs/etiquette.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Etiquette Guide" 3 | --- 4 | **for volunteer installers** 5 | 6 | As a volunteer installer, you are the public face of NYCMesh! Courtesy, respect, friendliness and 7 | professionalism will give new members a great first impression of our organization and 8 | will encourage them to become active contributors to our community. 9 | 10 | ## Before the Install 11 | 12 | Check the weather forecast the day before the install. If you have to cancel due to weather 13 | conditions, inform the install team on slack, email the installee member and send them a link to reschedule their appointment. 14 | 15 | Before leaving for the install, hydrate and eat something. Bring bottled 16 | water and a snack with you. 17 | 18 | Turn on push notifications on the slack app to communicate efficiently with your 19 | fellow installers. 20 | 21 | Check MTA delays and allow sufficient time to get to the install. If you can’t help being 22 | late, call or text the installee member and update your co-installers on slack. 23 | 24 | ## When You Arrive at the Node Site 25 | 26 | When meeting the installee member, introduce yourself by name and explain how you plan to carry out 27 | the install. Ask them if they have any questions and confirm that they will be able to 28 | host you for the expected duration of the install. Be polite and friendly! 29 | 30 | Be sensitive to cultural and social differences, such as: 31 | 32 | * Attitudes towards physical contact. For example, some people may not feel comfortable 33 | shaking hands upon meeting. 34 | * Wearing or not wearing outdoor footwear in the apartment. Ask for permission to wear 35 | shoes indoors if in doubt. 36 | * Language barriers. Be patient with members whom you don’t share a first language with. 37 | * Physical abilities. members who are elderly or have a medical condition may not be 38 | able to accompany you to the roof or help move furniture. 39 | 40 | For rooftop installs, ask your installee member to lead you to their roof. If they are unable to do so, ask them to 41 | explain how to access the roof and request that they point out any hazards. 42 | 43 | Ask your installee member to show you around their apartment. Ask where the bathroom is in case you need to use it. Remember to respect the member’s privacy. 44 | 45 | Discuss options for cabling into the apartment with your installee member during your initial tour 46 | of their apartment. Ask for permission before carrying out any drilling. 47 | 48 | Consider taking your boots off inside the apartment. Some apartments insist on this, and also your boots are probably dirty. Molten tar on roofs is a big problem in summer and will stick to everything. Snow in winter will melt. 49 | 50 | ## During the Install 51 | 52 | The install leader will assign tasks as per volunteers abilities. Minimal time should be wasted. 53 | 54 | Maintain a tidy workspace. Clean up as you go. Keep an eye on wire casings you've stripped 55 | off. 56 | 57 | Carry out the install quickly and efficiently but do not rush or compromise safety. Do not goof off or waste time. 58 | 59 | If you need to move anything, ask permission or ask them to help you if they are able. 60 | 61 | If you run into installation issues and feel frustrated, try to maintain a positive 62 | attitude when communicating with the member and with your fellow installers. Resolve issues efficiently and post questions to the #install-team slack channel. 63 | 64 | If the install is taking longer than planned, tell the installee member. Confirm they will be able to host you for the extended install duration. 65 | 66 | If for any reason you need to halt the install (eg. weather, unsafe conditions, night falling), respectfully explain the situation to the installee member. 67 | 68 | ## At the End of the Install 69 | 70 | Take photos of the install setup, the install team and the installee member (make sure to ask permission first). Photos are used to evaluate the install for problems, and the best photos are tweeted. 71 | 72 | After finishing the install, have a friendly conversation with your member about the mission of NYCMesh and encourage them to get involved as a volunteer. Invite them to our next 73 | [meetup](https://www.meetup.com/nycmesh/). Avoid excessive casual conversation during install as this can increase install time by hours. 74 | 75 | Politely remind your member to pay the labor fee and the installation fee. 76 | 77 | Pat yourself on the back! You just helped NYCMesh grow by another node! 78 | 79 | -------------------------------------------------------------------------------- /content/installs/fiberToTheApartment.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Fiber to the apartment" 3 | aliases: ["/fiber"] 4 | --- 5 | 6 | The first step is to screw the ONT into the wall in a convenient place using drywall achors. The ONT we are currently using is the Ubiquiti UF-WiFi6-US 7 | 8 | Only use white fiber inside apartments, never yellow or any other color. This is to better blend in with the wall. We have custom made 3mm white fiber with termination at one end. 9 | 10 | Once the ONT is screwed into the wall, plug in the terminated end of the white fiber. Now you are ready to run the fiber to the exit point (usually above the front door). You first run the fiber down to the top of the baseboard and then along to the nearest corner, attaching it to the wall with silicone or staples. You run the cable up the corner to the ceiling and follow along the corner of the ceiling to the exit point using silicone or staples along the way. 11 | 12 | ![Ufiber ONT](/img/installs/wallONT.jpg) 13 | 14 | As always with fiber, don't do any hard bends! Let the fiber curve around corners. 15 | 16 | There is no loose fiber in the apartment, just a service loop above the door. All the fiber is locked down with silicone or staples the whole way. Any loose fiber will result in service calls. Excess fiber is pulled back into the apartment and left as a service loop above the door. Trim the yellow raceway fiber down before splicing so it one foot from the entry point. Use excess white fiber to enable the splice. 17 | 18 | At the exit point you drill a small hole (6mm?) and feed the unterminated end of the fiber through to the raceway. The fiber will be spliced outside of the apartment either with a fusion splicer or with a mechanical splice. The hole must be sealed after you're finished! 19 | 20 | The new ONT has a built in router so install it near a power outlet and you are done. You will need to log into the OLT to configure the router 21 | 22 | The older model ONT is powered by connecting it to a POE injector, and connecting the data port to a TP-Link/Archer home router. 23 | 24 | **Support** 25 | 26 | [to be expanded!] 27 | 28 | Fiber support is fairly straightforward. First do the usual test of the wifi router to eliminate that as the problem. Next test the signal going into the ONT by unplugging the connector and connecting it to your meter. 29 | 30 | Test db of signal using an OTDR or optical power meter (OPM). The signal should be between -22db to -10db. Less than -24db and the signal is too weak. -8db is the highest limit that will work. 31 | 32 | If the signal is outside of the range of -22 to -10 you need to look for where signal loss is occurring. This is typically the splice in the raceway or damaged fiber that has been bent. 33 | 34 | Light fiber with red test signal using the OPM or OTDR. This is done from the hallway access box. 35 | 36 | Look for loss along the way, especially in the raceway splice. Redo splice if signal loss is there. If the cable is damaged elsewhere, splice around the damage. 37 | -------------------------------------------------------------------------------- /content/installs/install-wiki.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Install Guides" 3 | layout: single 4 | aliases: ["/install-guide"] 5 | --- 6 | The install guides/docs have moved to the Wiki. This is to allow easier editing by all volunteers and members! 7 | Please visit [https://wiki.nycmesh.net/books/install-maintenance-guides](https://wiki.nycmesh.net/books/install-maintenance-guides) to view and edit them. -------------------------------------------------------------------------------- /content/installs/linknyc.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "LinkNYC Kiosk" 3 | --- 4 | 5 | We do not install LinkNYC Kiosk repeaters as they are not as reliable as a mesh connection. We still support DIY kiosk repeaters through our Slack group. 6 | 7 | If you are too far away from an access point to get a good connection, you can use a directional router to connect to [Link NYC](https://link.nyc). We recommend using a [Mikrotik SXTsq G-5acD](/hardware/sxtsqg5acd/) **international version**. The LinkNYC kiosks use [DFS channels](https://en.wikipedia.org/wiki/Dynamic_frequency_selection) which, although legal and FCC approved, aren't supported in some USA versions of hardware. 8 | 9 | To use the SXTsq 5 ac you need to get the international version and configure it according to [our detailed instructions](/hardware/sxtsqg5acd), the simplified [fast config](/hardware/config/#sxtKiosk) or the [VPN config](/hardware/config/#sxtVpn) which connects you to our mesh network. 10 | 11 | [Here is the link to buy the SXTsq.](https://www.multilink.us/SXTsq-5-ac_p_1271.html) Make sure to specify **international**. 12 | 13 | With all these gateways we get lots of questions about security. As always, https (used by most web sites) is a secure way to transmit information across wifi. We recommend our [VPN config](/hardware/config/#sxtVpn) for end-to-end encryption for total security. 14 | -------------------------------------------------------------------------------- /content/installs/memberform.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Member Install Form" 3 | --- 4 | Installers, after completing a new member installation, fill in the form that you previously printed. 5 | Leave the completed "Member Install Form" with the new member. 6 | 7 | 8 | 9 | 10 | [the Form](/installs/documents/Installation_Member-Form.pdf) 11 | 12 | 13 | 15 | 16 | -------------------------------------------------------------------------------- /content/installs/nn.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Network Number Redirect" 3 | aliases: ["/nn"] 4 | --- 5 | 6 | The node number page has moved to the following location - [/networking/nn](/networking/nn) 7 | -------------------------------------------------------------------------------- /content/installs/panoramas.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Panoramas" 3 | aliases: ["/panorama"] 4 | --- 5 | 6 | The panoramas page has moved to the [new wiki](https://wiki.nycmesh.net/books/2-install-maintenance-guides/page/taking-panorama-photos) 7 | -------------------------------------------------------------------------------- /content/installs/problems.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Avoiding problems" 3 | --- 4 | 5 | # Alignment and wind 6 | 7 | We've had many antennas lose alignment in the wind. There's a few simple things you can do to prevent this- 8 | 9 | 1. Use a socket and drill to tighten hose clamps fast. It's hard to get the hose clamp tight with a screw driver. A socket and drill will get it really tight. You'll need a socket set that has both [american and metric sockets](https://www.amazon.com/PANOVOS-Driver-Metric-Socket-Wrench/dp/B01J3O4RYS/ref=sr_1_13?crid=2TECPORUO14Y4). 10 | 11 | 2. Put one layer of electrical tape under the hose clamp. This can help stop slipping, especially on smooth j-pipes like the Ubiquiti ones. 12 | 13 | 3. Make sure pipe mounts can't twist by putting a bolt through them. You'll need a set of metal drill bits (such as titanium) and some 2 1/2" long 1/4" bolts. 14 | 15 | If you can move the LiteBeam with your hands, it will also move in the wind. The LiteBeam LR needs even more care to stop it from moving. 16 | 17 | # Bad crimps 18 | 19 | Ethernet testers aren't perfect so you need to check your crimps visually- 20 | 21 | 1. Wires are in correct order! 22 | 2. All wires are pushed all the way to the end 23 | 3. All pins are pushed down after crimping (important!) 24 | 4. The cable jacket is just inside the RJ-45 25 | 26 | If the first three things are correct the cable will work! The jacket being inside the rj-45 gives it a bit more strength. 27 | 28 | It is possible that the cable tester will wrongly say it is fine even if the wires aren't at the end and the pins aren't all down. 29 | 30 | The crimping tool's job is to push the pins into the wires. Look at the pins before and after crimping and you should see that they are all pushed down by the same amount. Some crimping tools are incompatible with the toughcable jacket and are unable to push the pins down evenly. We recommend [this crimper](https://www.amazon.com/Platinum-Tools-100054C-Clamshell-EZ-RJPRO) 31 | 32 | # Not enough cable 33 | 34 | To save carrying a full box of cable many installers take a roll of cable (and occasionally not enough) 35 | 36 | Here’s a short guide to help: 37 | 38 | 1. Tough cable is marked every meter. Each box is 305m so if the end says 255m you have 50m left 39 | 2. 50 meters of cable is enough to do an average install 40 | 3. Each floor adds about 3 meters to the length 41 | 4. Member’s floor info is now on the schedule to help with calculation 42 | 5. Each extra apartment adds about 20m + floor calculation 43 | 5. 100m is the max length for Cat5 cable. (data loss and voltage loss is too much) 44 | 6. If you have a roll, you can measure one loop and multiply by the number of loops 45 | 46 | 1 meter = 3 feet 47 | 48 | # OmniTik power problems 49 | 50 | The biggest confusion with OmniTiks is that one model has POE out (OmniTik POE) and one doesn't. They both look the same. There is obscure print near the ethernet ports that will tell you if it is ethernet out. OmniTik POE has a much larger power injector and this must be used to power it. If you accidentally power it with a smaller adapter it will work but the LiteBeam will occasionally reboot. 51 | 52 | Sometimes the OmniTik won't automatically power the LiteBeam. You can force on the power by going to Webfig>Interfaces>ether5 and select "PoE Out: forced on". Also check that you are using the correct power injector for the Omni as this can also cause this problem. If the "PoE Out" option is missing you have the wrong kind of OmniTik! 53 | 54 | Use electrical tape to tape the small DC power cable to the white injector after plugging it in. This often comes undone causing all sorts of problems. The DC power cable is the same as the tp-link DC cable, and will break the tp-link if you plug it into that instead. 55 | 56 | The OmniTik should plug directly into a wall, not a power strip 57 | 58 | -------------------------------------------------------------------------------- /content/installs/query.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Query" 3 | aliases: ["/query"] 4 | --- 5 | **This page works best in incognito/private window mode!** 6 | 7 | This is for installers to query our install spreadsheet. This is password protected. 8 | 9 | **If you have trouble running this script, try using an incognito (private) window in your browser** 10 | 11 | This uses simple matching for addresses. Type the number and street name, e.g. "123 Smith St". Don't enter a complete address! For NN, install number and email it uses exact matches. 12 | 13 |
14 | 15 | 16 | 23 |
24 |
25 | 26 | 27 | 28 | 29 |
30 |
31 | 32 | 33 |
34 |
35 | 36 |
37 | 38 | -------------------------------------------------------------------------------- /content/installs/surveys.md: -------------------------------------------------------------------------------- 1 | 2 | --- 3 | title: "Site surveys" 4 | --- 5 | 6 | Site surveys for large buildings help us determine if wireless connection is possible and how we will run cable to apartments. Take photos at each step as you go through the building. 7 | 8 | ### Mounting points on roof 9 | 10 | Identify the best mounting points on the roof. 11 | 12 | ### Bandwidth test 13 | 14 | Take a battery and do a bandwidth test to the hub or hubs that they are planning to connect to 15 | 16 | (This might not be possible if the mounting point is in the water tower) 17 | 18 | 19 | ### Conduit or drop point for cable from roof to basement 20 | 21 | For large buildings we need to run cable from the roof to the basement. Try to identify existing conduits we can use. We can't use ISP's conduits, unless the building owns them. 22 | 23 | ### Telecom closet access 24 | 25 | All large buildings have a telecom closet in the basement. This is one place we might put a panel and run our cables from there. 26 | 27 | ### Raceways into apartments 28 | 29 | Hallways often have conduits running where the wall meets the ceiling. This is called a raceway. See if this is owned by the building and we can use that. 30 | 31 | ### Unused wiring that we could use. 32 | 33 | Often there is unused or abandoned wiring that we can use. This might be ethernet, coax or even fiber. This will save a huge amount of time and money if we can identify that. 34 | 35 | ### Documentation 36 | 37 | When finished, write up a google doc of the survey with embedded photos. We often share these as pdf's with the interested building managers. 38 | 39 | -------------------------------------------------------------------------------- /content/intro/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Introduction" 3 | weight: 99 4 | --- 5 | 6 | [NYC Mesh](https://nycmesh.net/) is a community network. This means that city residents take it upon themselves to maintain and grow the network. A massive amount of cooperation between many different people with many different skills is required to accomplish this, and this website is here to make sure that individuals who want to improve the network can get the knowledge and skills they need to do so. 7 | 8 | ## Who should read this website 9 | 10 | This website contains information about the *technical* implementation of the NYC Mesh network itself, along with ancillary information about the standard operating procedures (SOPs) of various NYC Mesh volunteer teams. **Before reading this website, please read [our FAQ](https://nycmesh.net/faq).** Many common questions are answered there, and this documentation is mostly written with the assumption that readers are already familiar with the answers to our most frequently asked questions. 11 | 12 | Once you have already read our FAQ, then you should consider reading or referring to this website if: 13 | 14 | * you want to help expand the network by physically installing new nodes, 15 | * you have computer networking experience and want to help improve the network's performance or security, 16 | * you plan to volunteer to monitor or otherwise maintain the network and have questions regarding the configuration of various hardware and software components, or 17 | * you are interested in knowing details about how NYC Mesh functions that are not already covered by the FAQ. 18 | 19 | You should *not* read this website if: 20 | 21 | * you want us to connect your apartment, house, or building to the mesh. Instead, please go to our [Get Connected](https://nycmesh.net/join) (join request) form where you will be put in contact with one of our install teams. 22 | * there is a problem with your connection and you need assistance from an NYC Mesh volunteer technician. Please use our [Request Support](https://www.nycmesh.net/support) form to open a trouble ticket to get help with problems you cannot fix on your own. 23 | * you are a member of the press seeking the latest news about NYC Mesh. We publish press releases specifically for journalists on our main website's [Press](https://www.nycmesh.net/press) page. 24 | * you are a member of the general public and are simply curious about our work. For this information, please read [the Frequently Asked Questions (FAQ) page on our main website](https://nycmesh.net/faq), returning here only if the FAQ does not satiate your curiosity. :) 25 | 26 | We are always excited to welcome new volunteers who want to help us continue providing affordable, fair, and fast Internet connectivity to our fair city and so we hope you find this guidebook useful. 27 | -------------------------------------------------------------------------------- /content/intro/gettingstarted.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Getting Started" 3 | --- 4 | 5 | Please read our [FAQ](https://nycmesh.net/faq) if you haven't already. 6 | 7 | **Join the mesh** 8 | First you need to enter a [new node request](https://nycmesh.net/join). This will add your address to our list of requests and put your location on our map. If you have multiple locations enter them separately. If you are within range of a (blue) supernode or hub node, and have line-of-sight, we may be able to connect you. 9 | 10 | The easiest option is for our install team to come out and do the install. After you submit the new node request we will check whether a connection is possible. If so we'll send a link so you can schedule an install. This suggested donation of $290 covers everything needed. 11 | 12 | If you want to DIY it is best to join our [Slack group](https://slack.nycmesh.net) and ask questions in the #install channel 13 | -------------------------------------------------------------------------------- /content/networking/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Networking" 3 | layout: single 4 | --- 5 | 6 | NYC Mesh is a mesh network. 7 | To understand a bit more about our Mesh network design concepts, please see [Mesh Design](/networking/mesh) 8 | 9 | For more information on our networking concepts at a high level, please see: 10 | 11 | * [Mesh Design](/networking/mesh) 12 | * [Supernode Architecture](/networking/supernode-architecture/) 13 | 14 | 15 | We use the following routing protocols: 16 | 17 | * [BGP](/networking/bgp): Hub-to-Hub, some Rooftops, and to the Internet 18 | * [OSPF](/networking/ospf): Hubs to Rooftops, Rooftops to Rooftops, and in some VPNs 19 | * BMX6: Older Openwrt Nodes (c. 2015), (**Write-up pending**) 20 | 21 | You can connect to the network through: 22 | 23 | * Finding a Node. See [Nodes](/nodes) 24 | * VPN to the Mesh. See [VPN](/networking/vpn) 25 | -------------------------------------------------------------------------------- /content/networking/classes.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Classes" 3 | --- 4 | 5 | We have presented a few classes on network concepts and training. Here is a list of slides and videos we have made for reference. 6 | 7 | * Networking 101 version 1, by Zach Giles, Early 2017 [Slides](https://goo.gl/i9Asx4) 8 | 9 | 10 | * Networking 101 version 2, by Zach Giles, December 2018 [Slides](https://goo.gl/dwXSwo), [Video](https://www.youtube.com/watch?v=_Vi-wlEMWOc) 11 | -------------------------------------------------------------------------------- /content/networking/dns.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "DNS" 3 | --- 4 | 5 | ## DNS Infrastructure 6 | NYCMesh maintains an internal DNS with the "fake" top-level domain (TLD) of `.mesh` ( dot mesh ). 7 | Through this, services can be hosted, internal sites, etc. 8 | Use **10.10.10.10** for your DNS server. 9 | 10 | ## DNS configuration 11 | The DNS is hosted using standard DNS zones which are made available through the Knot Resolver and Knot DNS Server. 12 | The zone and scripts are made available via git. Once the master branch is updated, the DNS servers will periodically update and refresh their configuration. 13 | Git Repo: [github.com/nycmeshnet/nycmesh-dns](https://github.com/nycmeshnet/nycmesh-dns) 14 | Git Repo: NYCMesh in-mesh git ( does not exist yet ) 15 | 16 | ## Anycast DNS and IPs 17 | ### Anycast 18 | The DNS system is available through a "trick" called Anycast. Anycast is the number one way DNS is provided on the main public internet. 19 | With anycast, many DNS servers all present the same virtual IP. They announce this IP in the routing table ( mesh routing table, BGP or other protocol ). With this, the clients believe they all have a very short route to the same network, but in fact it is a copy of the same service running many times with the same configuration. Any of the services may answer the request equally well. Reply packets are sent via the normal means. 20 | 21 | ### IPs 22 | **10.10.10.10** - Resolving DNS endpoint for the mesh ( **Use this one** ) 23 | **10.10.10.11** - Authoritative endpoint for dot-mesh TLD. 24 | **199.167.59.10** - Public DNS Resolver for anyone in the world. No Logs, No filtering. 25 | 26 | The reason for two endpoints rather than one is to enable resolving the dot-mesh TLD separately. In-fact, the caching resolver forwards to the dot-mesh TLD server for dot-mesh addresses. 27 | This also allows more than one node to host a resolver, or, a dot-mesh DNS server, or both. 28 | 29 | ## Top Level Domains 30 | * `.mesh` - Internal dot-mesh domain for NYC Mesh. 31 | * `.mesh.nycmesh.net` - Public version of the same domain. Equivilent of `.mesh`. Available on the entire internet 32 | 33 | ## Running a DNS Server 34 | _This is a Work in progress_ 35 | Today there is a DNS server run at Supernode 1 as a VM. More are planned. It would be nice if at least every supernode ran a DNS clone. 36 | In the future it is expected that anyone who wants to run one can do so using a Docker container etc. 37 | To get a jump-start on this, check out the Git repo an take a look at the README. It's an ever-changing process. 38 | -------------------------------------------------------------------------------- /content/networking/mesh.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Mesh Design" 3 | --- 4 | 5 | NYC Mesh is designed and run as a mesh network. As a mesh, various nodes connect to each other in a non-hierarchical way, with traffic flowing in either direction, and rerouting traffic as nodes fail. 6 | 7 | As with all mesh networks, we must balance between becoming too much of a "star" topology vs a "mesh" topology. 8 | Neither is fully practical -- Not literally every node next to each other can all connect to each other, nor can we sustain unlimited nodes connecting to one rooftop. 9 | 10 | ## Design 11 | We propose a design to practically cover our city ( New York City ) which features many tall buildings, regions of short buildings, multiple islands, and a dense urban population. We also want to be able to take advantage of free resources and natural features as they become available. 12 | 13 | In this design, we propose: 14 | 15 | * A number of community-operated sites which will be in good high location to support the mesh backbone. ( Sometimes called high-sites. ) 16 | * Rooftop sites that connect to each other and to one or more hub-nodes. 17 | * Two mesh layers: 18 | - One mesh network between all supernode / hub nodes. This mesh is "the full view" and can "express" you between any two neighborhoods. 19 | - A rooftop-to-rooftop mesh network within neighborhoods. 20 | * The in-neighborhood meshes will collect all local routes and present them to the hubs. 21 | * Hubs will present all routes from other neighborhoods to each other and to other neighborhoods. 22 | 23 | ## Example Diagram 24 | ![nycmesh-hubsandhoods.png](/img/nycmesh-hubsandhoods.png) 25 | 26 | 27 | ## Mesh argument 28 | A number of people have argued for/against this approach, suggesting this is not a valid mesh layout. 29 | While it's true that this is not a traditional "by-the-book" mesh network, it seems mesh communities are all about trying out new things. 30 | 31 | Technically we could have used one mesh standard across the entire network, however, a few concerns led us the other direction: 32 | 33 | * Some longer running mesh networks have problems moving to newer protocols once too many nodes are deployed. We wanted to avoid this problem by creating smaller interconnected meshes. 34 | * We had difficulting finding cheap and available quality routers to continue building the mesh. Additionally, open firmware project were undergoing internal shifts. Using standard / multiple protocols we can leverage off-the-shelf routers with multiple radios and high speeds; and mix with Libre hardware when available. 35 | * We wanted to support experimentation with multiple protocols in different neighborhoods and interconnectivity to other mesh projects. 36 | 37 | 38 | **Our design is not anti-mesh, but rather embraces the fullness of hardware diversity and interconnectivity.** 39 | -------------------------------------------------------------------------------- /content/networking/nn.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Network Number (old form)" 3 | aliases: ["/nn"] 4 | --- 5 | **This page works best in incognito/private window mode!** 6 | 7 | Enter the Install Number* below to get the NN that can be used to configure the rooftop antennas/routers. This can also be used with existing multiple apartment installs to figure out the network number (NN) for the roof/building you are connected to. 8 | 9 |
10 | 11 | 12 | 13 | 14 | 15 | 16 |
17 | 18 |
19 |
20 | 21 | _*The Install Number is the number you received in an email right after you registered. If you can't find the email with your Install Number please [contact us](mailto:install@nycmesh.net)._ 22 |
23 |
24 | 25 | If you have the password you can assign a NN for an install number 26 | 27 |
Install Number: 28 | 29 | 30 | 31 | 32 | 33 | 34 |
35 | 36 |
37 |
38 | 39 | 40 | We have changed the way "Node Numbers" work and we're now using the term NN or "Network Number". 41 | 42 | Previously each registration would receive a **Node Number**. This number would be used to configure the devices. For example used in the litebeam naming and in the OmniTik configuration. The Node Number was used to generate the IP address range used by the OmniTik device. Many registrations do not end up being installed and thus a lot of addresses are being “blocked” as reserved for those Node Numbers, Nodes associated with persons. We gave ourselves a limit of 8192 “nodes”. This in order to “save” the IP range above, for further usage. 43 | 44 | We need now to start using the unused or unassigned IPs in the lower range. 45 | 46 | From now on, when a person registers, they receive an **Install Number** (or install request number). A person can register for several addresses and receive several Install Numbers. An Install Number can be seen a bit like a work-order. 47 | When devices are being configured and installed, they will receive a **Network Number** or **NN**, different from the Install Number. The IPs for an OmniTik device will be generated out of the **Network Number (NN)**. A member thus will have an **Install number** and a **NN**. It is possible that for some installations the Network Number and the Install Number are the same number. The second member connected to the same node (Network Number) will have a different Install number. 48 | 49 | The Install Number is associated with a member. When installed it is linked to a Network Number. The Network Number is associated with a building number (street address / BIN ). A building can have several Network Numbers in the event that it has for technical reasons 2 or more “nodes”. 50 | When a member moves, the Network Number stays with the building (especially when there are other members connected to this Network Number (Node). The moving member will register with their new street address and will receive a new Install Number. 51 |



*Examples*

52 | *John D. Install Number 2000, is connected to node with Network Number 5000*
53 | *Elis W. Insall Number 3000, is also connected to node with Network Number 5000*
54 | *Node with Network Number 5000 is on the building at address 55 Main Street.*

55 | 56 | *John D. has also Install Number 4000, is connected to node with Network Number 6000*
57 | *Node with Network Number 6000 is on the building at address 102 Down Street.*
58 | -------------------------------------------------------------------------------- /content/networking/ntp.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "NTP Network Time Protocol" 3 | --- 4 | 5 | ## NTP Infrastructure 6 | NYCMesh does not have yet a Mesh NTP server but 2 mesh members are providing NTP function on their server. 7 | Use **10.10.10.123** as your NTP server address. 8 | 9 | ## What is NTP 10 | The Netwok Time Protocol is a "network" protocol for devices to sych their clocks. See [Wiki](https://en.wikipedia.org/wiki/Network_Time_Protocol) 11 | 12 | ## IPs 13 | **10.10.10.123** - NTP for the mesh ( **Use this one** ) 14 | 15 | ## NTP stats and status 16 | Here are some stats on the NTP servers:
17 | 18 | [NTP server hosted at SN3](http://ntp1.ny2.ap-gp.net/)
19 | 20 | [NTP server hosted in Manhattan](https://noc.as397444.net/ntpgraphs/) (it has a Stratum 1 receiver). 21 | 22 | ## Alternatives 23 | There are many NTP servers on the Net, google offers it, some hardware maker such as Ubiquiti, etc.. 24 | 25 | [NTP pool project](https://www.ntppool.org/en/) 26 | 27 | [A list of NTP servers](https://gist.github.com/mutin-sa/eea1c396b1e610a2da1e5550d94b0453) 28 | 29 | -------------------------------------------------------------------------------- /content/networking/peering.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Public ASN Peering" 3 | --- 4 | 5 | ### NYC Mesh operates **AS395853** 6 | 7 | ### Our peering Policy is **Yes** 8 | 9 | Please [contact us](mailto:peering@nycmesh.net) to peer with our network. 10 | 11 | Note this this is our Public ASN, not the Mesh Network itself. 12 | This community-run public network supplies NYC Mesh with net-neutral internet connectivity to support the community. If you would like to join the Mesh Network, please visit our [Join Page](/join) make use of this network. 13 | 14 | **Peering Policy** 15 | 16 | * NYC Mesh has an open peering policy. 17 | * We have no requirements in terms of traffic, size, support/SLA, etc. 18 | * We operate both IPv4 and IPv6. Peering via both protocols is appreciated. 19 | 20 | **Locations** 21 | 22 | | Building | Address | Ports | 23 | | -------- | -------------------------- | -------- | 24 | | Sabey | 375 Pearl St, New York, NY | 1G / 10G | 25 | 26 | **Exchanges** 27 | 28 | | Exchange | City | IPv4 | IPv6 | ASNs | Routes | Speed | 29 | | --------- | ------------ | -------------- | --------------------- | ---- | ------ | ----- | 30 | | DE-CIX NY | New York, NY | 206.130.10.151 | 2001:504:36::c2ab:0:1 | 105 | ~122K | 1G | 31 | 32 | **Peering Data** 33 | 34 | ASN: 395853 35 | IRR AS-SET: AS-NYCMESH 36 | Peering Contact: peering@nycmesh.net 37 | Recommended Max Prefix IPv4: 10 38 | Recommended Max Prefix IPv6: 10 39 | PeerDB Page: [https://as395853.peeringdb.com](https://as395853.peeringdb.com) 40 | As we are a non-profit, please consider providing as many routes as possible, including upstream or other routes. 41 | 42 | **Peers** 43 | 44 | We have direct peering sessions with the following networks 45 | Thank you to those who have peered! 46 | 47 | | ASN | Organization | Exchange | 48 | | ------- | ---------------------------------------- | --------- | 49 | | AS42 | WoodyNet / Packet Clearing House | DE-CIX NY | 50 | | AS714 | Apple Inc. | DE-CIX NY | 51 | | AS3856 | Packet Clearing House | DE-CIX NY | 52 | | AS6939 | Hurricane Electric, Inc. | DE-CIX NY | 53 | | AS9009 | M247 Ltd | DE-CIX NY | 54 | | AS15169 | Google LLC | DE-CIX NY | 55 | | AS20940 | Akamai International B.V. | DE-CIX NY | 56 | | AS27257 | Webair Internet Development Company Inc. | DE-CIX NY | 57 | | AS29838 | Atlantic Metro Communications, LLC | DE-CIX NY | 58 | | AS32217 | GPIEX INC | DE-CIX NY | 59 | | AS33891 | Core-Backbone GmbH | DE-CIX NY | 60 | | AS46450 | Pilot Fiber, Inc. | DE-CIX NY | 61 | | AS53988 | Digi Desert LLC | DE-CIX NY | 62 | | AS54825 | Packet Host, Inc. | DE-CIX NY | 63 | -------------------------------------------------------------------------------- /content/networking/supernode-architecture.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Supernode Architecture" 3 | --- 4 | 5 | ## Goals of this documents 6 | 7 | * Supernode routing / goals 8 | * Supernode sample architectures 9 | * Plan to get us to this architecture 10 | 11 | ## Supernode routing / goals 12 | 13 | "If you can get to a supernode, you can get to the rest of the mesh ( and the internet )." 14 | 15 | * A supernode should be the regional authority on how to get to its region, other regions, and the internet. 16 | * Translate region-local rooftop-to-rooftop protocol routes to standard routes for other regions and vice versa. 17 | * All supernodes should have a full view of all mesh routes. 18 | * Each supernode will get a private ASN in a sequential range with its supernode designation number. 19 | * All routers at the supernode should use BGP confederation and act as a route-reflector. 20 | * A supernode might also run mesh-services that will be announced to the mesh as routes. 21 | * A supernode might provide internet access. If it does, it must: 22 | * Announce a default route prefix internally. 23 | * Translate any private IPv4 to public using NAT. May be CGNAT with a pool of addresses, or single IP 24 | * Translate a specific private IPv6 prefix to public using NPTv6. 25 | * Must tag internet connecting with their source using BGP communities. 26 | * Must not log data nor filter data / routes. 27 | * A supernode might participate in the NYCMesh Public Backbone by using BGP Peering if capable. If so, it will do so in accordance with that architecture. 28 | * Links between supernodes will be routed Layer3 using an IPv4 /24 and IPv6 /64. There will be one VLAN for each link ( site-to-site ). VLANs should not be shared across multiple sites. ( Except in extenuating circumstances or testing crazy things. ) 29 | * The reason for this is to allow for multiple routers on each end if appropriate. 30 | 31 | ## Supernode layout 32 | 33 | ![supernodediagram-2017121501](/img/supernodediagram-2017121501.png) 34 | Each supernode has one or more local routers. Each local router has some local subnet, for downstream sector antennas, service nodes, and PtP links. Each router speaks BGP to some of these services and also to neighboring supernodes. 35 | Routers present internet access by passing a NAT layer and consuming some public IP addresses; For example, in a scenario where a single IP connection is handed off, such as Verizon FiOS, the IP is consumed by the NAT services directly. 36 | If the supernode is also a Public Backbone routers, one or more backbone routers provide public access connectivity, with some connectivity being presented to the supernode routers for NAT consumption. 37 | Downstream access can be presented via one or more subnets, one or more antennas, in a mixed fashion for whatever is best for that region. 38 | 39 | ## Plan to get us to this new architecture 40 | 41 | * In our current setup, we present a single subnet directly from our Public Router. 42 | * We should create a second router at Supernode 1 as the supernode router. 43 | * From this new router, we should present several subnets: 44 | * One to Supernode 2 45 | * One to the internal out of band routers 46 | * One or more for downstream client access 47 | * This router should be able to perform NAT for any subnet using a public IP pool 48 | * We should present the Supernode 2 access subnet via a VLAN over the AirFiber 24 49 | * In Brooklyn, we should accept the additional VLAN over the AirFiber and connect it with the router part of the EdgePoint router. 50 | * From there we can setup BGP to accept the routes and also present a default route to Manhattan 51 | * Brooklyn can make several subnets: 52 | * One for internal out of band router access 53 | * One or more for downstream client access 54 | * We can begin to shorten the lease time on the public IPs, switching clients over to private IPs slowly. 55 | * In manhattan, we can begin to use private IPs and public IPs mixed immediately. This subnet will propagate to Brooklyn as well temporarily in-lieu of the Public IPs. As private IPs are found to have no problem, the local private IP subnet can be introduced. 56 | 57 | ## Supernodes interconnecting examples 58 | 59 | ![supernodediagram-2017121501](/img/nycmesh-intersn-20180103a.png) 60 | ![supernodediagram-2017121501](/img/nycmesh-intersn-20180103b.png) 61 | -------------------------------------------------------------------------------- /content/networking/vpnl2tpipsecid.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "VPN - L2TP/IPsec Req." 3 | --- 4 | 5 | NYC Mesh maintains some common VPN infrastructure **for use by active mesh members**. 6 | 7 | Please feel free to use the VPNs. However, please note that NYC Mesh is not a commercial VPN provider or reseller, nor are we trying to achieve an Internet-based darknet. The VPN service is subject to change and/or breakage at any time. Do not rely on NYC Mesh’s VPN service as your primary or critical VPN provider. Also, as with all NYC Mesh resources, **do not abuse the VPN service or the access it provides**. 8 | 9 | 10 | ## Request a vpn account 11 | 12 | 13 | Please write to 14 | "vpn @ nycmesh.net" 15 | and provide the following information, **the same you provided on the join request form**, to register your install 16 | 17 | 18 | * First name: 19 | * Last name: 20 | * Phone number: 21 | * Location (street address, including zip code): 22 | * Email: 23 | * Active Install number: 24 | 25 | * Comment:* 26 | 27 | *_please indicate if it is to be used by you, from your laptop, phone, etc.. Or if it is to be setup on your node, such as for a "remote node" or else._ 28 | -------------------------------------------------------------------------------- /content/networking/vpnwireguard.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "VPN - WireGuard" 3 | --- 4 | 5 | [WireGuard](https://wireguard.com/) is a new, simple, and fast VPN implementation and protocol. For comparison, the older [L2TP/IPsec VPNs]({{< relref "vpnl2tpipsec.md" >}}) typically will achieve about 100Mbps, but WireGuard VPNs may reach speeds upward of 300-400Mbps on the same hardware, or higher on a high-end workstation. 6 | 7 | In addition to its speed, WireGuard has some great features such as [built-in roaming](https://www.wireguard.com/#built-in-roaming) (a single encrypted packet moves the tunnel to your new IP), [cryptokey routing](https://www.wireguard.com/#cryptokey-routing), and formal cryptographic verification. 8 | 9 | On the other hand, it also has some challenges, such as pre-key exchange and a lack of automatic address assignment. Both of these problems require manual configuration on both ends of the tunnel. Cryptokey routing also presents its own challenges in some situations (see [§ A Note on Cryptokey Routing]({{< relref "#a-note-on-cryptokey-routing" >}})). 10 | 11 | A WireGuard VPN is best suited for connecting single end-user devices such as laptops and phones to the mesh over the internet from a location that has no mesh access. 12 | 13 | ## Routing over WireGuard 14 | WireGuard, like other VPNs, can be used in conjuction with a routing protocol, such as [OSPF]( relref "ospf.md") which we use in NYC Mesh. However, there are some challenges with WireGuard and routing. 15 | 16 | These challenge are highlighted on another page, as it is a longer and more technical discussion. 17 | 18 | Please see [VPN - WireGuard + OSPF]({{ relref "vpnwireguardospf.md"}}) 19 | 20 | ## Device support 21 | WireGuard implementations are being developed on a variety of platforms. The following list provides an overview, but see the [WireGuard Installation](https://www.wireguard.com/install/) instructions for further details. 22 | 23 | * Linux: Yes! 24 | * Android devices: Yes, some - See WireGuard website 25 | * OpenWRT: Yes, in LEDE on latest versions, in certain builds 26 | * Apple devices: Yes, some - See Wireguard website 27 | * Mikrotik devices: Starting in RouterOS 7.1beta2 28 | * Ubnt routers: No (well, technically yes, but the module has caused lots of problems, so please don't use it yet) 29 | * Windows devices: Yes, some - See WireGuard website 30 | 31 | ## Endpoints 32 | 33 | ### Supernode 1: 34 | * IPv4/6: `wgvpn.sn1.mesh.nycmesh.net:51820` 35 | * Supported connect methods: 36 | * End Device 37 | * ~~OSPF - _Not Yet_~~ 38 | * ~~BGP Node-Peering - _Now legacy, please do not use_~~ 39 | 40 | ### Supernode 3: 41 | * IPv4/6: `wgvpn.sn3.mesh.nycmesh.net:51820` 42 | * Supported connect methods: 43 | * End Device 44 | * OSPF Node-Peering 45 | 46 | ## How To Connect 47 | 48 | ### Connecting end-devices 49 | 1. Ensure WireGuard will work on your device 50 | 1. Generate a Wireguard public key, and give it to Zach. (https://www.wireguard.com/quickstart/#key-generation) 51 | 1. Zach will give you the server public key and assign you an IP address. _This will change later, but just for now to get the docs out, this is what we currently do._ 52 | -------------------------------------------------------------------------------- /content/nodes/Grand Street.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Nodes 1932/1933/1934 (Grand Street)" 3 | aliases: [/networking/Grand-Street/] 4 | --- 5 |

6 | 7 |
8 | 9 | Grand Street is a group of buildings in the lower east side. These 3 housing towers are run by Grand Street Guild. The partnership between NYCMesh and Grand Street guild has worked out very well, and is something we look forward to duplicating with other complexes in the city. 10 | 11 | Grand Street has a 40gbit fiber line to the 111th 8th Ave datacenter. This datacenter has no room for antennas on the roof, but allows us high bandwidth access to many of our upstream providers. 12 |
13 | 14 | 15 | 16 | ## Fiber Installs 17 | 18 |
19 | 20 | Grand Street has fiber run between 131 Broome and each other building. Each building has Fiber To The Home (FTTH) for all tenants in the building, distributed via a GPON network. Connected appartments each have access to ~1gbps low latency fiber internet. 21 | 22 |
23 | 24 | 25 | 26 |
27 | 28 | 29 | 30 |

31 | 32 | ## Public Wi-Fi 33 | 34 |
35 | 36 | There are also public Wi-Fi access points scattered around the courtyards, community center and Mesh Room which are located in the complex. 37 | We have mesh Wi-Fi access points around the complex mounted on lightpoles. 38 | 39 |
40 | 41 | 42 | 43 | 44 |
45 | 46 | ## Coverage 47 | 48 | Grand street also hosts a variety of sectors and Point-to-Point links. It has direct connections to both Vernon and SN1, along with high bandwidth links to other hubs in Brooklyn and further up the river to Greenpoint. 49 | 50 |
51 | 52 | 53 |
54 | 55 | -------------------------------------------------------------------------------- /content/nodes/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Nodes" 3 | --- 4 | 5 | Notes on NYC Mesh nodes of particular importance or interest. Feel free to document your own node. 6 | -------------------------------------------------------------------------------- /content/nodes/hub-231-SunsetParkLibrary.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Hub 231 - Sunset Park Libary" 3 | aliases: [/networking/sunset-park-library/] 4 | --- 5 | 6 | 7 | [Sunset Park Library](https://www.nycmesh.net/map/nodes/231 "Sunset Park Library") is located in the Sunset Park neighborhood of Brooklyn. The bottom floor is a library, with apartment units above. 8 | 9 | In March of 2023, we began work installing a community hub on the library. The library has Line-Of-Sight to SN3, covers the majority of the surrounding area, and extends mesh coverage further south in Brooklyn. 10 | 11 | 12 | 13 |
14 | 15 | ## Infrastructure 16 | 17 | The site currently hosts 2 antenna masts on the upper roof of the building. 18 | There is a AF24 Point-to-Point(PtP) link back to SN3, 4 AirMax sector antennas for LiteBeam connections from the surrounding buildings and a direct PtP link to Node-9382 full building install. 19 | 20 | A goal during the design process for this hub was to develop a well documented standard hub template that could be replicated at other locations. 21 | The design also includes space for future expansion including apartment connections or a fiber backbone if that is desired in the future. 22 | 23 | The site currently has a CCR1009 main router, EdgePower DC supply and a NetPower 16P rooftop switch. 24 | 25 | 26 | 27 | 28 | [Wiring Diagram Full Size File](nycmesh-231-SunsetParkLibrary-drawing.pdf) 29 | 30 | 31 |

32 | ## Sector Coverage 33 | 34 | 35 | 36 | 37 | 38 |

39 | 40 | ## Photos 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | -------------------------------------------------------------------------------- /content/nodes/hub-231-sunsetparklibrary/nycmesh-231-SunsetParkLibrary-drawing.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/nodes/hub-231-sunsetparklibrary/nycmesh-231-SunsetParkLibrary-drawing.pdf -------------------------------------------------------------------------------- /content/nodes/node-1340.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Saratoga hub" 3 | aliases: [/networking/node-1340/] 4 | --- 5 | 6 | Saratoga hub (1340) is a hub node located at 33 Saratoga Avenue in Brooklyn New York. The installation provides mesh and internet connectivity for building residents as well as large areas of the Bedford Stuyvesant and Bushwick neighborhoods. 7 | 8 | ![Node 1340 wide shot](/img/nycmesh-1340-wide.jpg) 9 | 10 | ## Status 11 | 12 | [https://stats.1340.nycmesh.net](https://stats.1340.nycmesh.net) 13 | 14 | ## Coverage 15 | 16 | 17 | 18 | ## Photos 19 | 20 | 21 | 22 | 23 | 24 | 25 | ## Hardware 26 | 27 | | Description | Model | Manufacturer | Quantity | 28 | | ------------------ | ----------------------- | -------------- | -------: | 29 | | Router | EdgePointR6 | UBNT | 1 | 30 | | Switch | EdgePointR6 | UBNT | 2 | 31 | | Indoor AP | UniFi Mesh | UBNT | 5 | 32 | | Powerline adapter | AV2000 (2-port Gigabit) | TP-LINK | 4 | 33 | | Outdoor AP | SXT | Mikrotik | 1 | 34 | | Outdoor AP | Nanostation M5 | UBNT | 1 | 35 | | Wide area AP | LiteAP 120 | UBNT | 4 | 36 | | Wide area station | Litebeam AC | UBNT | 2 | 37 | | Application server | Raspberry Pi | RPi Foundation | 1 | 38 | 39 | ## Schematic 40 | 41 | 42 | 43 | ## Ethernet over power 44 | 45 | We needed to place wireless access points deep inside the building but did not have permission or budget to run new conduit. We tried at first to backhaul the APs using a wireless mesh approach, but found the concrete walls and floors to be too thick to get acceptable performance. Ethernet and DC power are commonly multiplexed (called PoE or power-over-ethernet), but it's also possible to multiplex ethernet and AC power. This was the technique we settled on as it utilized a pre-existing infrastructure and was able to deliver 100Mbps+ to each of our APs. 46 | 47 | 48 | 49 | ## AP enclosures 50 | 51 | The combination of an access point, PoE injector and EoP adapter resulted a somewhat awkward and exposed deployment - to protect them from damage and improve their appearance, our team designed custom 3d-printed enclosures: 52 | 53 | 54 | 55 | 56 | 57 | ## Mounting 58 | 59 | The mounting brackets shipping with the wide-area access points we deployed at the site are designed to clamp to poles. Unfortunately no appropriate structures predated our installation and given its potentially short term nature we devised a customized non-pentrating bracket using only readily available components from a local industrial electrical supplier. 60 | 61 | 62 | 63 | ## Routing 64 | 65 | 1340 currently uses BGP to exchange routes with its mesh peers. We hope to upgrade this node to support additional dynamic routing protocols soon. 66 | 67 | ## Switching 68 | 69 | 1340 enforces isolation at layer 2 on its public access networks for security reasons. The EP-R6 devices we had on hand have dedicated switching hardware (which is a nice thing) however no controls are exposed that provide a way to isolate ports in the traditional way. To achieve the desired effect we used VLANs to pass each wireless AP's access net though to a linux bridge on the router. This has the unfortunate side effect of causing the router to send multiple identical copies of its broadcast frames over our trunk links, but fortunately the volume of this sort of traffic is currently quite low. 70 | -------------------------------------------------------------------------------- /content/nodes/supernode1.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Supernode 1" 3 | aliases: [/networking/supernode1/] 4 | --- 5 | 6 | Supernode 1 is located at 375 Pearl St, New York, NY. This site is located in lower manhattan on the old Verizon building. 7 | 8 | ![Supernode 1 wide shot](/img/nycmesh-sn1-1.jpg) 9 | 10 | ## Status 11 | 12 | [https://stats.nycmesh.net](https://stats.nycmesh.net) 13 | 14 | ## Coverage 15 | 16 | ![Supernode 1 coverage](/img/nycmesh-sn1-coverage.png) 17 | -------------------------------------------------------------------------------- /content/nodes/supernode2.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Supernode 2 - Decommissioned" 3 | aliases: [/networking/supernode1/] 4 | --- 5 | 6 | ⚠️ **Supernode 2 is no longer active. The sector antennas were moved to [Soft Surplus](https://www.nycmesh.net/map/nodes/1417)** ⚠️ 7 | 8 | Supernode 2 (node 570) was located at 1196 Metropolitan Avenue in Brooklyn New York. On October 7th, 2018 it was taken down due to roof repair. 9 | 10 | The information below is a point of reference for how supernode 2 was configured. 11 | 12 | ![Supernode 2 radios](/img/nycmesh-570-radios.png) 13 | 14 | ## Status 15 | 16 | [https://stats.570.nycmesh.net](https://stats.570.nycmesh.net) 17 | 18 | ## Coverage 19 | 20 | ![Supernode 2 coverage](/img/nycmesh-570-coverage.jpg) 21 | 22 | ## Photos 23 | 24 | ![Point-to-point link to node 227](/img/nycmesh-570-227-link.png) 25 | ![The router](/img/nycmesh-570-router.png) 26 | ![Battery backup](/img/nycmesh-570-battery.png) 27 | 28 | ## Hardware 29 | 30 | | Description | Model | Manufacturer | Quantity | 31 | | -------------------- | ------------ | -------------- | -------: | 32 | | Router | Hex PoE | Mikrotik | 1 | 33 | | Point-to-point radio | AirFiber 24 | UBNT | 1 | 34 | | Point-to-point radio | Nanobeam AC | UBNT | 1 | 35 | | Wide area AP | LiteAP 120 | UBNT | 2 | 36 | | Indoor AP | UniFi AP | UBNT | 1 | 37 | | Application server | Raspberry Pi | RPi Foundation | 1 | 38 | | Inverter/Charger/ATS | APS700HF | Tripp Lite | 2 | 39 | | Battery | EXP12180 | ExpertPower | 1 | 40 | 41 | ## Schematic 42 | 43 | 44 | 45 | ## Backhaul 46 | 47 | A pair of AirFiber 24s was donated to NYC Mesh and was deployed between 227 and 570 to provide Brooklyn with a near 1Gbps backhaul link to Supernode 1, the Manhattan area of the mesh and the internet. 48 | 49 | 50 | 51 | ## Battery backup 52 | 53 | Shortly after initial installation we noticed the node would go down on a somewhat regular basis. After some investigation and discussion with building residents, the culprit was revealed to be a circuit breaker being tripped by power hungry air conditioners. To insulate the node against short power outages like this we built a simple backup power system out of a 12 volt battery and integrated inverter / charger / automatic transfer switch. 54 | 55 | ## Routing 56 | 57 | 570 currently uses BGP to exchange routes with its mesh peers. We hope to upgrade this node to support more dynamic routing protocols soon. 58 | -------------------------------------------------------------------------------- /content/nodes/supernode3.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Supernode 3" 3 | aliases: [/networking/supernode3/] 4 | --- 5 | 6 | The new [Supernode 3](https://www.nycmesh.net/map/nodes/713) is located in Industry City, Brooklyn at the DataVerge (previously known as ColoGuard) datacenter.

7 | 8 | ![Supernode 3](/img/nycmesh-sn3-1.jpg)

9 | 10 | ## Status 11 | 12 | to come

13 | 14 | ## Coverage 15 | ![Supernode 3 coverage](/img/nycmesh-sn3-2.jpg) 16 |

17 | ## Antenna positions 18 | ![Supernode 3 antenna positions](/img/nycmesh-sn3-3.jpg) 19 |

20 | ## SN3 views 21 | 22 | ## North 23 | ![Supernode 3 north](/img/nycmesh-sn3-pano1-north.jpg) 24 |

25 | ## South 26 | ![Supernode 3 north](/img/nycmesh-sn3-pano2-south.jpg) 27 | -------------------------------------------------------------------------------- /content/nodes/supernode4.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Supernode 4 - Decommissioned" 3 | aliases: [/networking/supernode4/] 4 | --- 5 | 6 | ⚠️ Supernode 4 is no longer active. [Supernode 4](https://nycmesh.net/map/?s=1348) was located at St. Francis School for the Deaf. 7 | 8 | 9 | ## Location 10 | 11 | 12 | ## Coverage 13 | 14 | 15 | ## Photo 16 | 17 | 18 | -------------------------------------------------------------------------------- /content/organization/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Organization" 3 | --- 4 | -------------------------------------------------------------------------------- /content/organization/culture.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Culture" 3 | --- 4 | 5 | In a decentralized organization like the Mesh, it is difficult for new people to figure out who does what. 6 | 7 | Basically we work on a system of trust. As we get to know new people we trust that they will do the right thing, and we gradually share access to locations and machines, and let them lead installs. During Covid it is obviously difficult to get to know people since we don't get to socialize with everyone at our meetups, so zooms are the new way. 8 | 9 | The danger of having no official structure is that there becomes an "implicit hierarchy" as certain people look after certain aspects of the organization. To avoid that we need to be welcoming to new people and share our skills and responsibilities. 10 | 11 | If you are new to the Mesh, the best thing is to join our Slack and start participating in some particular activity, like maintaining hubs near you or helping with apartment installs. As people get to know you, they may ask you to help on other mesh projects. 12 | 13 | For some reason most of us are softly spoken, and louder people may have trouble fitting in. (Is this the opposite of most organizations?) We particularly value people from non-technical backgrounds, so we avoid unnecessary jargon and try to answer questions in a common sense way rather than a typical tech way. 14 | 15 | -------------------------------------------------------------------------------- /content/organization/documents.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Documents" 3 | --- 4 | 5 | **NYC Mesh Inc. EIN: 84-2616395** 6 | 7 | In the interest of transparency, NYC Mesh will compile and publish all organizational documents for public review. Many of these documents are posted on the Slack, but can now be easily accessed without needing a Slack account. 8 | 9 | 10 | -------------------------------------------------------------------------------- /content/organization/outreach/2019-08 One page flyer.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/2019-08 One page flyer.pdf -------------------------------------------------------------------------------- /content/organization/outreach/2019-08-One-page-flyer.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/2019-08-One-page-flyer.pdf -------------------------------------------------------------------------------- /content/organization/outreach/Brochure.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/Brochure.pdf -------------------------------------------------------------------------------- /content/organization/outreach/GeneralSticker.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/GeneralSticker.png -------------------------------------------------------------------------------- /content/organization/outreach/MeshQRCode.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/MeshQRCode.png -------------------------------------------------------------------------------- /content/organization/outreach/NYCMesh_ThankYou.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/NYCMesh_ThankYou.pdf -------------------------------------------------------------------------------- /content/organization/outreach/NYC_Mesh_Brochure_01.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/NYC_Mesh_Brochure_01.jpg -------------------------------------------------------------------------------- /content/organization/outreach/NYC_Mesh_Brochure_02.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/NYC_Mesh_Brochure_02.jpg -------------------------------------------------------------------------------- /content/organization/outreach/NYC_Mesh_Member_Guide.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/NYC_Mesh_Member_Guide.pdf -------------------------------------------------------------------------------- /content/organization/outreach/NYC_Mesh_Member_Guide_print.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/NYC_Mesh_Member_Guide_print.pdf -------------------------------------------------------------------------------- /content/organization/outreach/NYC_Mesh_Trifold_5.17.23.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/NYC_Mesh_Trifold_5.17.23.pdf -------------------------------------------------------------------------------- /content/organization/outreach/PowerSupplySticker.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/PowerSupplySticker.png -------------------------------------------------------------------------------- /content/organization/outreach/Priorities-One-Pager.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/Priorities-One-Pager.pdf -------------------------------------------------------------------------------- /content/organization/outreach/SiteSurveyLetter-Community-Template.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/SiteSurveyLetter-Community-Template.pdf -------------------------------------------------------------------------------- /content/organization/outreach/TEMPLATE - Landlord Letter .docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/TEMPLATE - Landlord Letter .docx -------------------------------------------------------------------------------- /content/organization/outreach/building-leaflet.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/building-leaflet.pdf -------------------------------------------------------------------------------- /content/organization/outreach/building-leaflet.rtfd.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/building-leaflet.rtfd.zip -------------------------------------------------------------------------------- /content/organization/outreach/building-leaflet.rtfd/TXT.rtf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/building-leaflet.rtfd/TXT.rtf -------------------------------------------------------------------------------- /content/organization/outreach/building-leaflet.rtfd/nycmesh-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/building-leaflet.rtfd/nycmesh-logo.png -------------------------------------------------------------------------------- /content/organization/outreach/card.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/card.png -------------------------------------------------------------------------------- /content/organization/outreach/church.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/church.pdf -------------------------------------------------------------------------------- /content/organization/outreach/cut-the-cord.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/cut-the-cord.pdf -------------------------------------------------------------------------------- /content/organization/outreach/flyer-bw.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/flyer-bw.jpg -------------------------------------------------------------------------------- /content/organization/outreach/flyer-chinese.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/flyer-chinese.jpg -------------------------------------------------------------------------------- /content/organization/outreach/flyer.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/flyer.jpg -------------------------------------------------------------------------------- /content/organization/outreach/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Outreach Materials" 3 | aliases: ["/leaflet","outreach"] 4 | --- 5 | **Mesh Guide:** 6 | 7 | Mesh Guide given to new members and for general mesh info.
(Paper copies are available in the Mesh Room for mesh installers to distribute) 8 | 9 | [NYC Mesh Member Guide (digital)](NYC_Mesh_Member_Guide.pdf) 10 | 11 | [NYC Mesh Member Guide (print)](NYC_Mesh_Member_Guide_print.pdf) 12 | 13 |
14 | 15 | **Flyers/Brochures:** 16 | 17 | General Information 18 | 19 | [2024 Cut-the-Cord Streaming TV guide](cut-the-cord.pdf) 20 | 21 | [2023 Trifold color](NYC_Mesh_Trifold_5.17.23.pdf) 22 | 23 | [2020 Two page trifold general brochure](Brochure.pdf) 24 | 25 | [One page general flyer](Priorities-One-Pager.pdf) 26 | 27 | [One page narrow brochure: Join NYC Mesh](NYC_Mesh_Brochure_02.jpg) 28 | 29 | [Church handout](church.pdf) -[(source file)](https://docs.google.com/document/d/1duBRyzncVxuODrXyH7ooDki2LEmwcyuOtkZJjcC3loo/edit?usp=sharing) 30 | 31 | [Thank you card](NYCMesh_ThankYou.pdf) 32 | 33 |
34 | 35 | Flyers for distribution to potential new nodes and areas with mesh coverage. 36 | 37 | [Two page trifold neighborhood brochure (English/Spanish)](https://docs.google.com/presentation/d/1mKzGT6Scrkv27Hb_lb7oOLWi_fGDoIHwEBJtcxI64PQ/edit?usp=sharing) 38 | 39 | [One page neighbourhood poster (English/Spanish)](https://docs.google.com/presentation/d/1q-m-aZW4gHhS7vgNDPng7JEV1rOjDPgKGE2j_NEJMXM/edit?usp=sharing) 40 | 41 | [Two page trifold general brochure](Brochure.pdf) 42 | 43 | [One page general flyer](Priorities-One-Pager.pdf) 44 | 45 |
46 | 47 | Flyers and Posters to distribute in buildings with existing mesh connections.
(Can be provided to members to give to their neighbours.) 48 | 49 | [Two page trifold existing building brochure (English/Spanish)](https://docs.google.com/presentation/d/1uVqunqIVR9J9R2hiS4T6pdpfTWMzVqgjBLoIQZ5p8WA/edit?usp=sharing) 50 | 51 | [Building Postcard (English/Spanish)](https://docs.google.com/presentation/d/1WqvYEiE_J_LPH_eGNaouarhXnnWj8nOyKsJ9WlqPBPc/edit?usp=sharing) 52 | 53 | [Building Postcard [Chinese]](flyer-chinese.jpg) 54 | 55 | [Public WiFi Access Poster](https://docs.google.com/presentation/d/1Il80WQlluKZ16T5-gqD9Q7gUfE8dP8xAXhogMp8wvUQ/edit?usp=sharing) 56 | 57 |
58 | 59 | **Letter Templates** 60 | 61 | [Fiber install for building](https://docs.google.com/document/d/1UTLYMidNWN3XWmzXjnmfF_zHWAyIOqoDm1BtRGWhfoQ/edit?usp=sharing) 62 | 63 | [Sample introductory letter for businesses/community organizations](https://docs.google.com/document/d/1_BNWaigV6LNK3PMdgQ8bhw6EDUueLUpRGxrPGZjyl2o/edit?usp=sharing) 64 | 65 | [Proposal to building management/landlord](https://docs.google.com/document/d/1hmB5p-Zebi5frNimiwAoC7E-nAoWJGc49R2tNQW010Q/edit?usp=sharing) 66 | 67 |
68 | 69 | **Stickers** 70 | 71 | Stickers to place on mesh equipment and power supplies. 72 | 73 | [General mesh equipment sticker](GeneralSticker.png) 74 | 75 | [Hub/Node power supply sticker](PowerSupplySticker.png) 76 | 77 | [NYCMesh.net QR Code](MeshQRCode.png) 78 | 79 |
80 | 81 | **Our logo** 82 | 83 | [NYC Mesh logo svg](logo.svg) 84 | [NYC Mesh logo png](logo.png) 85 | -------------------------------------------------------------------------------- /content/organization/outreach/leaflet-bw.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/leaflet-bw.pdf -------------------------------------------------------------------------------- /content/organization/outreach/leaflet-rtfd.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/leaflet-rtfd.zip -------------------------------------------------------------------------------- /content/organization/outreach/leaflet-rtfd/leaflet b&w.rtfd/TXT.rtf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/leaflet-rtfd/leaflet b&w.rtfd/TXT.rtf -------------------------------------------------------------------------------- /content/organization/outreach/leaflet-rtfd/leaflet b&w.rtfd/splash-b&w.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/leaflet-rtfd/leaflet b&w.rtfd/splash-b&w.png -------------------------------------------------------------------------------- /content/organization/outreach/leaflet-rtfd/leaflet.rtfd/TXT.rtf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/leaflet-rtfd/leaflet.rtfd/TXT.rtf -------------------------------------------------------------------------------- /content/organization/outreach/leaflet-rtfd/leaflet.rtfd/nycmesh-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/leaflet-rtfd/leaflet.rtfd/nycmesh-logo.png -------------------------------------------------------------------------------- /content/organization/outreach/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/logo.png -------------------------------------------------------------------------------- /content/organization/outreach/logo.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | background 5 | 6 | 7 | 8 | Layer 1 9 | 10 | 11 | 12 | 13 | 14 | -------------------------------------------------------------------------------- /content/organization/outreach/meshmail.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/meshmail.pdf -------------------------------------------------------------------------------- /content/organization/outreach/nycmesh buzzcard/nycmesh-bizcard-02-outlined.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/nycmesh buzzcard/nycmesh-bizcard-02-outlined.pdf -------------------------------------------------------------------------------- /content/organization/outreach/nycmesh buzzcard/nycmesh-bizcard-02.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/nycmesh buzzcard/nycmesh-bizcard-02.pdf -------------------------------------------------------------------------------- /content/organization/outreach/nycmesh buzzcard/nycmesh-flyer-3up-03.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/nycmesh buzzcard/nycmesh-flyer-3up-03.pdf -------------------------------------------------------------------------------- /content/organization/outreach/nycmesh buzzcard/nycmesh-stickers-2.63x1-outlined.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/nycmesh buzzcard/nycmesh-stickers-2.63x1-outlined.pdf -------------------------------------------------------------------------------- /content/organization/outreach/nycmesh buzzcard/nycmesh-stickers-2.63x1.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/content/organization/outreach/nycmesh buzzcard/nycmesh-stickers-2.63x1.pdf -------------------------------------------------------------------------------- /content/organization/plan.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Master Plan" 3 | --- 4 | 5 | Our basic plan is to create hubs and supernodes across the city so it is easy for any building to connect to our network. We think this will take about 50 tall buildings spread across all neighborhoods. We currently only have 3 supernodes and about 5 major hub nodes, so we are still a few years away from our goal. 6 | 7 | [This is a presentation from early 2018 on the technical side of the master plan](https://docs.google.com/presentation/d/1VVboouxNe0OIjGiqTfW6fwpZZZ9LM5JD-119bJy63Vw/present). Our network has expanded a lot since this presentation and we have now connected over 200 buildings and added another major supernode. 8 | -------------------------------------------------------------------------------- /content/organization/workflow.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Workflow" 3 | --- 4 | 5 | # Overview 6 | 7 | **Join Form** 8 | 9 | Everything begins when a user fills out our [Join Form](https://nycmesh.net/join). 10 | 11 | Submitting it assigns the user a node number, sends a support ticket, and adds a row to a spredsheet in Google Docs we refer to as our "main spreadsheet." 12 | 13 | **Main Spreadsheet** 14 | 15 | New nodes are displayed as gray dots on [our map](https://nycmesh.net/map). They are rendered from the spreadsheet using the [map-nodes](https://github.com/nycmeshnet/map-nodes) code on our Github. 16 | 17 | **Support Ticketing** 18 | 19 | We use OSTicket for support tickets 20 | 21 | **Install viability, panoramas etc** 22 | 23 | A main bottleneck is figuring out which installs are viable. Usually this means line-of-sight to one of our supernodes, or a nearby kiosk. 24 | 25 | **Scheduling an install** 26 | 27 | Once an install is deemed viable we send a link to our calendar so the new member can book an install. 28 | 29 | **Acuity calendar** 30 | 31 | Info to come. 32 | 33 | 34 | **General Workflow Description:** 35 | 36 | 1. User fills out the join form 37 | > Ticket is automatically assigned the help topic "010-join form / rooftop" or "010-join form / standard". 38 | > Row with node number and user info is created in the main spreadsheet. 39 | > Ticket is created in OSTickets to be claimed by a NYC Mesh volunteer ("agent"). 40 | > OSTickets sends auto-response asking for confirmation and a panoramic image of the user's view. 41 | 42 | 2. Ticket is claimed by an agent. 43 | > On the ticket, agent should assign the Help topic “01 waiting for pano” and save. 44 | 45 | 3. If no response from the user (maybe auto-response went to spam) agent sends Spam SMS following this procedure: 46 | * Go to the ticket and copy the phone number. 47 | * Sign into nycmeshmail@gmail.com. 48 | * On the left you’ll see the NYC Mesh icon with a “+”. Click on the plus, and paste in the phone number. Click on “Send SMS”. 49 | * Back at the bottom of the ticket, select the canned response “15-spam sms message”. Copy the generated message. Do not send this message to the user via the ticket. 50 | * Paste this message into the SMS text area and send the SMS. 51 | * Back at the ticket, click on “Post Internal Note” and paste the message there as well. 52 | * Edit the ticket and assign it the Help topic “012-sent spam sms” and save. 53 | * If another week goes by with no response, then close the ticket. 54 | 55 | 4. User responds with a pano. 56 | > Agent should then reassign ticket to Jason Howard to add the pano the map. 57 | > Jason will assign the ticket back to Agent when pano is added. 58 | 59 | 5. Agent should correspond with the user until install type is determined. 60 | 61 | 6. Agent should then encourage the user to schedule an install. 62 | > On the ticket, send the canned response "25-Schedule an Install" 63 | 64 | 7. The user will be directed to Acuity Scheduling where they will select an available install time slot. 65 | * The selected time slot will appear in the "NYC Mesh Community Network" google calendar. 66 | * The event needs to be copied into the "install requests" google calendar. 67 | 68 | 8. Installer volunteers to do install. 69 | 70 | 9. Install info [here](https://docs.google.com/presentation/d/1tIi4QSxitKx6un9pPfzCNJnribGZKAK1y9t8FtPl0gg/edit#slide=id.g3715bd45a8_0_6). 71 | -------------------------------------------------------------------------------- /content/security/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Security 3 | layout: default 4 | category: Security 5 | --- 6 | 7 | ### Security 8 | 9 | The goal of this document is to provide the most useful information for anyone interested in the security of the network. If there is missing information that would help understand and improve our network, please reach out to [contact@nycmesh.net](mailto:contact@nycmesh.net) or [join our slack][]. 10 | 11 | > We are actively looking for ways to improve the security, resiliancy, and ease-of-use of the network to help the widest range of use cases. If you have ideas on how to improve anything, please [join our slack][] 12 | 13 | Our current threat landscape is most concerned with in-mesh security - once traffic is routed over an IXP, provider gateway, or peer, its equivalent to what people are used to. 14 | 15 | In mesh threats include: 16 | 17 | * DoS by announcement of bogus routes 18 | * MiTM attacks on SSL servers using letsencrypt (should be alleviated by multiroute verification if we interconnect in more places) 19 | * Visibility of _who_ you talk to when using unencrypted HTTP, DNS queries, SNI, etc for someone along the route chain 20 | 21 | ### Data 22 | 23 | * We do not keep logs of anything in-mesh. However anyone along the route chain could view unencrypted data or metadata (just like any ISP can). 24 | * The organizers of nyc mesh can see a spreadsheet of signup information volunteered by participants on the [join nycmesh][] page (name, email, phone, address all but email are optional) 25 | * We [create a map](https://nycmesh.net/map) using [map-nodes][], from the above spreadsheet 26 | 27 | ### Wifi 28 | 29 | A typical home install creates two wireless networks - one open 802.11 access point (with a captive portal), and one WPA2 encrypted upstream gateway. You can change the open access point to be encrypted if you wish. 30 | 31 | ### DNS 32 | 33 | The default setup routes `.mesh` tld DNS requests to 10.10.10.10, which is anycast. Multiple people are running our [knot-dns setup available on github](https://github.com/nycmeshnet/nycmesh-dns) (including supernode 1 at 10.10.10.11), but a malicious actor that is closer could take advantage of this. 34 | 35 | [map-nodes]: https://github.com/nycmeshnet/map-nodes 36 | [join our slack]: https://slack.nycmesh.net/ 37 | [join nycmesh]: https://nycmesh.net/join/ 38 | -------------------------------------------------------------------------------- /content/security/ca.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "NYC Mesh Certificate Authority" 3 | draft: true 4 | --- 5 | 6 | 7 | -------------------------------------------------------------------------------- /content/services/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Services" 3 | 4 | --- 5 | 6 | This page intends to list the services "hosted" on NYC Mesh and available directly to NYC Mesh members. Some may be available only to NYC Mesh members while some may as well be available from the Internet via a Public IP address (or through Public DNS) 7 | 8 | They are different type of services. Some are network specific or meant for devices, such as DNS or NTP, others are more people oriented such as an email server or video chat server. 9 | 10 | If you do host a service that you would like to make available to the Mesh Community please let us know so we can add it here. 11 | 12 | You can also discuss services on our slack channel [#mesh-services](https://slack.nycmesh.net/) 13 | 14 | ### **Network services** 15 | 16 | - [DNS](/networking/dns/) 17 | - [NTP](/networking/ntp/) 18 | 19 | 20 | ### **Public services** 21 | 22 | - [NYC Mesh Meet](https://meet.nycmesh.net/) by @Zach 23 | - [ExcellentFiles](https://excellent.nyc) by @Eric Zhu. 24 | > It is a free file host hosted on sn3. Anyone can get 10G of free storage. It can support around ~25 users for now. 25 | *"I choose Nextcloud because it is very user friendly, and there is a nice mobile app, and desktop sync app. I have also enabled contacts + calendar sync. I use it myself coz i want to rely on other services less; to be more autonomous :)"* 26 | - [Mastodon](https://mastodon.nycmesh.net) on @Daniel Heredia's server at SN3, open to all. 27 | - [NYC Building KML Tool](https://dantonio.tech/programs/nyckml/) by @Daniel Heredia, takes two address and uses NYC DCP and DOB databases to create a KML line between the rooftops to determine LoS ([code](https://github.com/danielhmetro/nyckml)). 28 | 29 | ### **Projects** *Services that are in development...* 30 | 31 | - [Support Bot](https://github.com/nycmeshnet/nycmesh-support-bot) on Slack to automatically respond to [#support](https://app.slack.com/client/T02MB96L1/C679UKBUK) channel inquiries 32 | - [Chat app](https://github.com/maybejustmaybe/mesh-chat) by @George on [slack](https://slack.nycmesh.net/) 33 | -------------------------------------------------------------------------------- /content/software/_index.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Software" 3 | --- 4 | 5 | ### Projects 6 | 7 | Our community's source repositories are hosted on Github in the [nycmeshnet organization.](https://github.com/nycmeshnet) 8 | 9 | #### Router Firmware 10 | 11 | We are working to improve our router firmware, which is a fork of LibreMesh with a few modifications specific to our network. 12 | 13 | * [lime-sdk](https://github.com/nycmeshnet/lime-sdk) 14 | * [nycmeshfeed](https://github.com/nycmeshnet/nycmeshfeed) 15 | 16 | #### Website 17 | 18 | * [nycmesh.net](https://github.com/nycmeshnet/nycmesh.net) - Our public website is hosted by Github and its full source is available here. 19 | * [map-nodes](https://github.com/nycmeshnet/map-nodes) - This script pulls from our node spreadsheet and renders the data which powers the node map on our website. 20 | -------------------------------------------------------------------------------- /layouts/_default/baseof.html: -------------------------------------------------------------------------------- 1 | {{ if isset .Params "title" }} 2 | {{ .Scratch.Set "title" .Title }} 3 | {{ .Scratch.Add "title" " - " }} 4 | {{ end }} 5 | {{ .Scratch.Add "title" .Site.Title }} 6 | {{ $title := .Scratch.Get "title" }} 7 | 8 | 9 | 10 | 11 | {{ $title }} 12 | 13 | 14 | 15 | 16 | 17 | 18 | {{ if .IsPage }} 19 | 20 | 21 | {{ else }} 22 | 23 | {{ end }} 24 | 25 | 26 | 27 | {{ if .Params.thumbnail }} 28 | 29 | {{ end }} 30 | {{ range .Params.tags }} 31 | 32 | {{ end }} 33 | 34 | 35 | {{ if .Site.Params.twitter_card_whitelisted }} 36 | {{ if .Params.twitter_summary }} 37 | 38 | {{ else if .Description }} 39 | 40 | {{ else }} 41 | 42 | {{ end }} 43 | {{ end }} 44 | 45 | 46 | {{ if .Params.thumbnail }} 47 | 48 | {{ end }} 49 | 50 | 51 | 52 | {{ if .IsHome }} 53 | 54 | {{ end }} 55 | 56 | 57 |
58 | {{ partial "sidebar" . }} 59 |
60 | {{ partial "header" . }} 61 | {{ block "main" . }} 62 | {{ end }} 63 |
64 |
65 | 66 | 67 | {{ if .IsHome }} 68 | 79 | {{ end }} 80 | 81 | 82 | -------------------------------------------------------------------------------- /layouts/_default/section.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
3 |
4 |
5 | {{ partial "title" . }} 6 |
7 | {{ partial "timestamp" . }} 8 | {{ .Content }} 9 |

Section Contents

10 |
    11 | {{ range .Data.Pages }} 12 |
  1. 13 | 14 | {{ .Title }} 15 | 16 |
    2. 17 | {{ end }} 18 |
19 |
20 |
21 |
22 |
23 | {{ end }} 24 | -------------------------------------------------------------------------------- /layouts/_default/single.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
3 |
4 |
5 | {{ partial "title" . }} 6 |
7 | {{ partial "timestamp" . }} 8 | {{ .Content }} 9 |
10 |
11 |
12 |
13 | {{ end }} 14 | -------------------------------------------------------------------------------- /layouts/index.html: -------------------------------------------------------------------------------- 1 | {{ define "main" }} 2 |
3 |
4 |
5 | {{ partial "title" . }} 6 |
7 | {{ .Content }} 8 |
9 |
10 |
11 |
12 | {{ end }} -------------------------------------------------------------------------------- /layouts/partials/footer.html: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /layouts/partials/github.html: -------------------------------------------------------------------------------- 1 | 2 |
3 | 4 | 5 | 6 | Edit on GitHub 7 |
8 | 9 | -------------------------------------------------------------------------------- /layouts/partials/header.html: -------------------------------------------------------------------------------- 1 |
2 |
3 | 6 |
7 |
-------------------------------------------------------------------------------- /layouts/partials/join.html: -------------------------------------------------------------------------------- 1 |
2 |

Request an install

3 |
4 |
5 |
6 | 7 | 8 |
9 | 10 |
11 | 12 | 13 |
14 |
15 | 16 |
17 | 18 | 19 |
20 | 21 |
22 | 23 | 24 |
25 | 26 |
27 |
28 |
29 | 30 |

I agree to the Network Commons License

31 |
32 | 33 |
34 | 35 |

I might have roof access!

36 |
37 |
38 | 39 | 40 | 41 |
42 | 43 |
44 |
-------------------------------------------------------------------------------- /layouts/partials/sidebar.html: -------------------------------------------------------------------------------- 1 | {{ $currentPage := . }} 2 |
3 |
4 |
5 | 6 | 7 | NYC Mesh 8 | Docs 9 | 10 |
11 |
12 | 13 |
14 |
15 | 16 |
17 |
18 |
    19 | {{ range .Site.Sections }} 20 |
  • 21 |
    22 | {{ if eq $currentPage . | or (eq $currentPage.Parent .) }} 23 | 24 | 25 | 26 | {{ else }} 27 | 28 | 29 | 30 | {{ end }} 31 | {{ .Title }} 32 |
    33 | {{ if eq $currentPage . | or (eq $currentPage.Parent .) }} 34 | 41 | {{ end }} 42 |
    • 43 | {{ end }} 44 |
45 |
46 |
47 |
48 | -------------------------------------------------------------------------------- /layouts/partials/timestamp.html: -------------------------------------------------------------------------------- 1 |
2 |

3 | Last updated 4 | {{/* Go-specific layout string that looks like a time, don't change. */}} 5 | {{- .Lastmod.Format "January 2, 2006" }} by {{ if .GitInfo }}{{ .GitInfo.AuthorName -}}{{else}} unknown {{end}} 6 |

7 |
8 | 9 | -------------------------------------------------------------------------------- /layouts/partials/title.html: -------------------------------------------------------------------------------- 1 |
2 |

3 | {{ .Title }} 4 |

5 | {{ partial "github" . }} 6 |
-------------------------------------------------------------------------------- /static/admin/config.yml: -------------------------------------------------------------------------------- 1 | backend: 2 | name: github 3 | repo: nycmeshnet/docs 4 | media_folder: "static/img" 5 | public_folder: "/img" 6 | collections: 7 | - name: "hardware" # Used in routes, e.g., /admin/collections/blog 8 | label: "Hardware" # Used in the UI 9 | folder: "content/hardware" # The path to the folder where the documents are stored 10 | create: true # Allow users to create new documents in this collection 11 | fields: # The fields for each document, usually in front matter 12 | - { label: "Title", name: "title", widget: "string" } 13 | - { label: "Description", name: "body", widget: "markdown" } 14 | - name: "installs" 15 | label: "Installs" 16 | folder: "content/installs" 17 | create: true 18 | fields: 19 | - { label: "Title", name: "title", widget: "string" } 20 | - { label: "Body", name: "body", widget: "markdown" } 21 | - name: "intro" 22 | label: "Intro" 23 | folder: "content/intro" 24 | create: true 25 | fields: 26 | - { label: "Title", name: "title", widget: "string" } 27 | - { label: "Body", name: "body", widget: "markdown" } 28 | - name: "networking" 29 | label: "Networking" 30 | folder: "content/networking" 31 | create: true 32 | fields: 33 | - { label: "Title", name: "title", widget: "string" } 34 | - { label: "Body", name: "body", widget: "markdown" } 35 | - name: "nodes" 36 | label: "Nodes" 37 | folder: "content/nodes" 38 | create: true 39 | fields: 40 | - { label: "Title", name: "title", widget: "string" } 41 | - { label: "Body", name: "body", widget: "markdown" } 42 | - name: "organization" 43 | label: "Organization" 44 | folder: "content/organization" 45 | create: true 46 | fields: 47 | - { label: "Title", name: "title", widget: "string" } 48 | - { label: "Body", name: "body", widget: "markdown" } 49 | - name: "security" 50 | label: "Security" 51 | folder: "content/security" 52 | create: true 53 | fields: 54 | - { label: "Title", name: "title", widget: "string" } 55 | - { label: "Body", name: "body", widget: "markdown" } 56 | - name: "software" 57 | label: "Software" 58 | folder: "content/software" 59 | create: true 60 | fields: 61 | - { label: "Title", name: "title", widget: "string" } 62 | - { label: "Body", name: "body", widget: "markdown" } 63 | -------------------------------------------------------------------------------- /static/admin/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | Content Manager 7 | 8 | 9 | 10 | 11 | 12 | -------------------------------------------------------------------------------- /static/android-chrome-192x192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/android-chrome-192x192.png -------------------------------------------------------------------------------- /static/android-chrome-512x512.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/android-chrome-512x512.png -------------------------------------------------------------------------------- /static/apple-touch-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/apple-touch-icon.png -------------------------------------------------------------------------------- /static/browserconfig.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | #ffffff 7 | 8 | 9 | 10 | -------------------------------------------------------------------------------- /static/download/liteap.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | LiteAP sector config 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | Automatic download for LiteAP sector config 13 |
14 | 15 | 20 | 21 | 22 | -------------------------------------------------------------------------------- /static/download/mesh-watchdog.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | # mesh-watchdog v1.1.1, NYC Mesh, Brian Hall 3 | 4 | restartWifi() 5 | { 6 | wifi down 7 | sleep 5 8 | wifi up 9 | } 10 | 11 | restartNetwork() 12 | { 13 | /etc/init.d/network restart 14 | if /etc/init.d/gwck enabled; then 15 | /etc/init.d/gwck restart 16 | fi 17 | /etc/init.d/bmx6 restart 18 | sleep 4 19 | killall dnsmasq 20 | /etc/init.d/dnsmasq start 21 | } 22 | 23 | #gets date-time from log and exit if recently run. date-time is first two words of last line 24 | exitIfRecentRestart() 25 | { 26 | if [ -e $LOG ]; then 27 | set -- `tail -1 $LOG` 28 | LASTRUN=`date --date="$1 $2" +%s` 29 | if [ "$?" = "0" ]; then 30 | #don't run for 1200s (20 minutes) 31 | NEXTRUN=$(($LASTRUN + 1200)) 32 | NOW=`date +%s` 33 | es=$(($NOW - $LASTRUN)) 34 | printf "time since last restartNetwork: " 35 | printf '%dd %dh:%dm:%ds\n' $(($es/86400)) $(($es%86400/3600)) $(($es%3600/60)) $(($es%60)) 36 | if [ $NOW -lt $NEXTRUN ]; then 37 | echo "waiting $(($NEXTRUN - $NOW)) seconds, use option -f to force" 38 | exit 1 39 | else 40 | echo "run tests-" 41 | fi 42 | else 43 | echo "invalid date from log, run tests-" 44 | fi 45 | else 46 | echo "no log, run tests-" 47 | fi 48 | } 49 | 50 | LOG="/tmp/log/mesh-watchdog.log" 51 | FORCE=0 52 | 53 | if [ "$1" = "-n" ]; then 54 | echo "restartNetwork" 55 | restartNetwork 56 | exit 1 57 | elif [ "$1" = "-f" ]; then 58 | echo "force tests-" 59 | FORCE=1 60 | elif [ "$1" = "-w" ]; then 61 | echo "restartWifi" 62 | restartWifi 63 | exit 1 64 | elif [ "$1" = "-b" ]; then 65 | echo "restart wifi, wait, restart network" 66 | restartWifi; wait 60; restartNetwork 67 | exit 1 68 | elif [ "$1" != "" ]; then 69 | echo -e "Usage: `basename $0` [OPTION]\n\nTests wifi and internet connections and restarts if necessary (default)\n\n\t-f\tforce test\n\t-n\trestart network\n\t-w\trestart wifi\n\t-b\trestart both wifi and network\n\t-h\toptions\n" 70 | exit 1 71 | fi 72 | 73 | if [ $FORCE != 1 ]; then 74 | exitIfRecentRestart 75 | fi 76 | 77 | DATE=`date +%Y-%m-%d\ %H:%M:%S` 78 | IWINFO=`iwinfo` 79 | 80 | # find lines containing "ESSID"|get name (previous word)|replace return with "," 81 | WI=`echo "$IWINFO" | grep ESSID | grep -Eo '^[^ ]+' | sed ':a;N;$!ba;s/\n/, /g` 82 | # count the number of wlan interfaces, and number of wlans with 'no signal' 83 | WLAN=`echo "$WI" | wc -w` 84 | NOSIGNAL=`echo "$IWINFO" | grep 'Signal: unknown' | wc -l` 85 | 86 | if [ $WLAN -eq 0 ]; then 87 | echo "no wlan interfaces, wifi is probably disabled" 88 | elif [ $WLAN -eq $NOSIGNAL ]; then 89 | # all wlan interfaces are down, so restart wifi 90 | echo "$DATE restart wifi- wlans:$WLAN no-signal:$NOSIGNAL interfaces:$WI" | tee -a $LOG 91 | restartWifi 92 | sleep 60 93 | restartNetwork 94 | exit 1 95 | else 96 | echo "wifi:ok wlans:$WLAN no-signal:$NOSIGNAL interfaces:$WI" 97 | fi 98 | 99 | # restart network if ping google.com && 8.8.8.8 fails 4 times 100 | count=1 101 | while [ "$count" -le 4 ] 102 | do 103 | if /bin/ping -c 1 google.com >/dev/null && /bin/ping -c 1 8.8.8.8 >/dev/null; then 104 | echo "wan:ok ping-count:$count" 105 | exit 0 106 | fi 107 | let count++ 108 | done 109 | echo "$DATE network restart" | tee -a $LOG 110 | restartNetwork 111 | -------------------------------------------------------------------------------- /static/download/sn1.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | LiteBeam config SN1 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | Automatic download for SN1 LiteBeam config 13 |
14 | 15 | 20 | 21 | 22 | -------------------------------------------------------------------------------- /static/download/sn2.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | LiteBeam config SN2+ and hubs 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | Automatic download for SN2+ and hub LiteBeam config 13 |
14 | 15 | 20 | 21 | 22 | -------------------------------------------------------------------------------- /static/favicon-16x16.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/favicon-16x16.png -------------------------------------------------------------------------------- /static/favicon-32x32.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/favicon-32x32.png -------------------------------------------------------------------------------- /static/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/favicon.ico -------------------------------------------------------------------------------- /static/img/diagrams/Omni-only_Install.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/diagrams/Omni-only_Install.png -------------------------------------------------------------------------------- /static/img/diagrams/typical_install_Litebeam_Omni.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/diagrams/typical_install_Litebeam_Omni.png -------------------------------------------------------------------------------- /static/img/equipment/RJ45.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/RJ45.jpg -------------------------------------------------------------------------------- /static/img/equipment/batterypack.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/batterypack.jpg -------------------------------------------------------------------------------- /static/img/equipment/blank.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/blank.jpg -------------------------------------------------------------------------------- /static/img/equipment/boot.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/boot.jpg -------------------------------------------------------------------------------- /static/img/equipment/cable staples.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/cable staples.jpg -------------------------------------------------------------------------------- /static/img/equipment/cable.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/cable.jpg -------------------------------------------------------------------------------- /static/img/equipment/cablestripper.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/cablestripper.jpg -------------------------------------------------------------------------------- /static/img/equipment/cabletester.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/cabletester.jpg -------------------------------------------------------------------------------- /static/img/equipment/chargedcellphone.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/chargedcellphone.jpg -------------------------------------------------------------------------------- /static/img/equipment/cobalt.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/cobalt.jpg -------------------------------------------------------------------------------- /static/img/equipment/coldweather.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/coldweather.jpg -------------------------------------------------------------------------------- /static/img/equipment/concnail2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/concnail2.jpg -------------------------------------------------------------------------------- /static/img/equipment/concscrew.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/concscrew.jpg -------------------------------------------------------------------------------- /static/img/equipment/concscrew_field.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/concscrew_field.jpg -------------------------------------------------------------------------------- /static/img/equipment/crimper.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/crimper.jpg -------------------------------------------------------------------------------- /static/img/equipment/drill.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/drill.jpg -------------------------------------------------------------------------------- /static/img/equipment/edgepoint.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/edgepoint.jpg -------------------------------------------------------------------------------- /static/img/equipment/electape.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/electape.jpg -------------------------------------------------------------------------------- /static/img/equipment/ethernetadapter.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/ethernetadapter.jpg -------------------------------------------------------------------------------- /static/img/equipment/firstaid.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/firstaid.jpg -------------------------------------------------------------------------------- /static/img/equipment/garbsmall.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/garbsmall.jpg -------------------------------------------------------------------------------- /static/img/equipment/hammmer.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/hammmer.jpg -------------------------------------------------------------------------------- /static/img/equipment/handtruck.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/handtruck.jpg -------------------------------------------------------------------------------- /static/img/equipment/hexsocket.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/hexsocket.jpg -------------------------------------------------------------------------------- /static/img/equipment/hoseclamp_large.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/hoseclamp_large.jpg -------------------------------------------------------------------------------- /static/img/equipment/hoseclamp_large_field.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/hoseclamp_large_field.jpg -------------------------------------------------------------------------------- /static/img/equipment/hoseclamp_small.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/hoseclamp_small.jpg -------------------------------------------------------------------------------- /static/img/equipment/hoseclamp_small_field.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/hoseclamp_small_field.jpg -------------------------------------------------------------------------------- /static/img/equipment/j pipe.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/j pipe.jpg -------------------------------------------------------------------------------- /static/img/equipment/jpipe_field.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/jpipe_field.jpg -------------------------------------------------------------------------------- /static/img/equipment/l pipe field.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/l pipe field.jpg -------------------------------------------------------------------------------- /static/img/equipment/l pipe.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/l pipe.jpg -------------------------------------------------------------------------------- /static/img/equipment/laptop.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/laptop.jpg -------------------------------------------------------------------------------- /static/img/equipment/masonrybit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/masonrybit.jpg -------------------------------------------------------------------------------- /static/img/equipment/outdoorrouter.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/outdoorrouter.jpg -------------------------------------------------------------------------------- /static/img/equipment/patchcable.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/patchcable.jpg -------------------------------------------------------------------------------- /static/img/equipment/phillips.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/phillips.jpg -------------------------------------------------------------------------------- /static/img/equipment/pliers.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/pliers.jpg -------------------------------------------------------------------------------- /static/img/equipment/poe.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/poe.jpg -------------------------------------------------------------------------------- /static/img/equipment/safetyglasses.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/safetyglasses.jpg -------------------------------------------------------------------------------- /static/img/equipment/scissors.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/scissors.jpg -------------------------------------------------------------------------------- /static/img/equipment/sealant.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/sealant.jpg -------------------------------------------------------------------------------- /static/img/equipment/sun protection.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/sun protection.jpg -------------------------------------------------------------------------------- /static/img/equipment/tinybroom.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/tinybroom.jpg -------------------------------------------------------------------------------- /static/img/equipment/tplink.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/tplink.jpg -------------------------------------------------------------------------------- /static/img/equipment/visegrip.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/visegrip.jpg -------------------------------------------------------------------------------- /static/img/equipment/washer.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/washer.jpg -------------------------------------------------------------------------------- /static/img/equipment/watersnack.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/watersnack.jpg -------------------------------------------------------------------------------- /static/img/equipment/wd40.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/wd40.jpg -------------------------------------------------------------------------------- /static/img/equipment/weatherstrip.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/weatherstrip.jpg -------------------------------------------------------------------------------- /static/img/equipment/wrench.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/wrench.jpg -------------------------------------------------------------------------------- /static/img/equipment/ziptie.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/ziptie.jpg -------------------------------------------------------------------------------- /static/img/equipment/ziptie_field.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/equipment/ziptie_field.jpg -------------------------------------------------------------------------------- /static/img/ethernet/T-568B.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/ethernet/T-568B.gif -------------------------------------------------------------------------------- /static/img/hardware/60ghz/AF60.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/AF60.png -------------------------------------------------------------------------------- /static/img/hardware/60ghz/AF60LR.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/AF60LR.png -------------------------------------------------------------------------------- /static/img/hardware/60ghz/AF60_LR.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/AF60_LR.png -------------------------------------------------------------------------------- /static/img/hardware/60ghz/GBE-Plus.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/GBE-Plus.png -------------------------------------------------------------------------------- /static/img/hardware/60ghz/GBE.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/GBE.png -------------------------------------------------------------------------------- /static/img/hardware/60ghz/GBELR.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/GBELR.png -------------------------------------------------------------------------------- /static/img/hardware/60ghz/LHG.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/LHG.jpg -------------------------------------------------------------------------------- /static/img/hardware/60ghz/ML1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/60ghz/ML1.jpg -------------------------------------------------------------------------------- /static/img/hardware/AF60.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/AF60.png -------------------------------------------------------------------------------- /static/img/hardware/mikrotik_netpower15fr.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/mikrotik_netpower15fr.jpg -------------------------------------------------------------------------------- /static/img/hardware/mikrotik_omnitik5poeac_front.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/mikrotik_omnitik5poeac_front.jpg -------------------------------------------------------------------------------- /static/img/hardware/mikrotik_omnitik5poeac_ports.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/mikrotik_omnitik5poeac_ports.jpg -------------------------------------------------------------------------------- /static/img/hardware/mikrotik_powerboxpro.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/mikrotik_powerboxpro.jpg -------------------------------------------------------------------------------- /static/img/hardware/mikrotik_sxtsq5ac.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/mikrotik_sxtsq5ac.jpg -------------------------------------------------------------------------------- /static/img/hardware/uap/uap-ac-m-pro.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/uap/uap-ac-m-pro.jpg -------------------------------------------------------------------------------- /static/img/hardware/uap/uap-ac-m.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/uap/uap-ac-m.png -------------------------------------------------------------------------------- /static/img/hardware/ubiquity_edgepointr6_front.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/ubiquity_edgepointr6_front.png -------------------------------------------------------------------------------- /static/img/hardware/ubiquity_edgepointr6_ports.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/ubiquity_edgepointr6_ports.png -------------------------------------------------------------------------------- /static/img/hardware/ubiquity_liteap.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/ubiquity_liteap.png -------------------------------------------------------------------------------- /static/img/hardware/ubiquity_litebeam5acgen2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/ubiquity_litebeam5acgen2.png -------------------------------------------------------------------------------- /static/img/hardware/ubiquity_nanostationm5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/hardware/ubiquity_nanostationm5.png -------------------------------------------------------------------------------- /static/img/icon-hires.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/icon-hires.png -------------------------------------------------------------------------------- /static/img/image_from_ios.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/image_from_ios.jpg -------------------------------------------------------------------------------- /static/img/installs/fiberSafety/chair_scrap_1000x1000.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSafety/chair_scrap_1000x1000.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSafety/scrap_across_table_1000x1000.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSafety/scrap_across_table_1000x1000.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSafety/table_scrap_closeup_1000x1000.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSafety/table_scrap_closeup_1000x1000.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/01_strip_12cm_outerjacket_SWS.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/01_strip_12cm_outerjacket_SWS.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/02_strip_2cm_innerjacket_SWS.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/02_strip_2cm_innerjacket_SWS.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/03_position_SWS_in_cleaver_closeup.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/03_position_SWS_in_cleaver_closeup.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/04_position_SWS_in_splicer.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/04_position_SWS_in_splicer.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/05_strip_5cm_outerjacket_2cm_innerjacket_SWOS.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/05_strip_5cm_outerjacket_2cm_innerjacket_SWOS.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/06_position_SWOS_in_splicer_closeup.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/06_position_SWOS_in_splicer_closeup.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/07_fiber_fused.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/07_fiber_fused.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/08_optical_power_meter_1550nm_reading_neg320dBm.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/08_optical_power_meter_1550nm_reading_neg320dBm.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/09_place_fused_fiber_with_shrinksleeve_in_heating_compartment.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/09_place_fused_fiber_with_shrinksleeve_in_heating_compartment.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/10_shrunk_sleeve_wrapping_bare_fiber.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/10_shrunk_sleeve_wrapping_bare_fiber.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/11_fused_cable_on_ruler_15cm_between_outerjackets.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/11_fused_cable_on_ruler_15cm_between_outerjackets.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/cleaver_pads_under_ruler.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/cleaver_pads_under_ruler.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/edu_template.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/edu_template.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/shrinksleeve_on_ruler.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/shrinksleeve_on_ruler.JPG -------------------------------------------------------------------------------- /static/img/installs/fiberSplicingTutorial/splicer_measurement.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/fiberSplicingTutorial/splicer_measurement.JPG -------------------------------------------------------------------------------- /static/img/installs/wallONT.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/installs/wallONT.jpg -------------------------------------------------------------------------------- /static/img/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/logo.png -------------------------------------------------------------------------------- /static/img/logo.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | -------------------------------------------------------------------------------- /static/img/ltu/Speed-infographics_1328x792.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/ltu/Speed-infographics_1328x792.jpg -------------------------------------------------------------------------------- /static/img/ltu/nycmesh-1340-LTUsectorwest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/ltu/nycmesh-1340-LTUsectorwest.png -------------------------------------------------------------------------------- /static/img/nsm5/bracket-200.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/bracket-200.jpg -------------------------------------------------------------------------------- /static/img/nsm5/nanobracket.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/nanobracket.jpg -------------------------------------------------------------------------------- /static/img/nsm5/pipe.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/pipe.jpg -------------------------------------------------------------------------------- /static/img/nsm5/roof-87.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/roof-87.jpg -------------------------------------------------------------------------------- /static/img/nsm5/tree.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/tree.jpg -------------------------------------------------------------------------------- /static/img/nsm5/ubiquiti-universal-mount.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/ubiquiti-universal-mount.jpg -------------------------------------------------------------------------------- /static/img/nsm5/ubiquiti-window-wall-mount.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/ubiquiti-window-wall-mount.jpg -------------------------------------------------------------------------------- /static/img/nsm5/velcro.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/velcro.jpg -------------------------------------------------------------------------------- /static/img/nsm5/wall-201.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/wall-201.jpg -------------------------------------------------------------------------------- /static/img/nsm5/wall.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/wall.jpg -------------------------------------------------------------------------------- /static/img/nsm5/window-cup-inside.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/window-cup-inside.jpg -------------------------------------------------------------------------------- /static/img/nsm5/window-cup-outside.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/window-cup-outside.jpg -------------------------------------------------------------------------------- /static/img/nsm5/window-velcro-off.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/window-velcro-off.jpg -------------------------------------------------------------------------------- /static/img/nsm5/window-velcro-on.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/window-velcro-on.jpg -------------------------------------------------------------------------------- /static/img/nsm5/windowwall.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/windowwall.jpg -------------------------------------------------------------------------------- /static/img/nsm5/windowwall2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nsm5/windowwall2.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-1340-coverage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-coverage.png -------------------------------------------------------------------------------- /static/img/nycmesh-1340-enclosure-0.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-enclosure-0.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-1340-enclosure-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-enclosure-1.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-1340-enclosure-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-enclosure-2.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-1340-mounting.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-mounting.png -------------------------------------------------------------------------------- /static/img/nycmesh-1340-powerline.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-powerline.png -------------------------------------------------------------------------------- /static/img/nycmesh-1340-prototype.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-prototype.png -------------------------------------------------------------------------------- /static/img/nycmesh-1340-schematic.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-schematic.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-1340-view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-view.png -------------------------------------------------------------------------------- /static/img/nycmesh-1340-wide-area-ap.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-wide-area-ap.png -------------------------------------------------------------------------------- /static/img/nycmesh-1340-wide-area-station.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-wide-area-station.png -------------------------------------------------------------------------------- /static/img/nycmesh-1340-wide.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1340-wide.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-1934-Panorama.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-Panorama.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-Panorama2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-Panorama2.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-diagram.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-fiber1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-fiber1.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-fiber2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-fiber2.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-1934-fiber2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-fiber2.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-fiber3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-fiber3.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-fiber4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-fiber4.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-lightpole1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-lightpole1.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934-lightpole2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934-lightpole2.png -------------------------------------------------------------------------------- /static/img/nycmesh-1934.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-1934.png -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-DCBox.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-DCBox.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-EastMast.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-EastMast.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-NorthEast.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-NorthEast.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-NorthWest.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-NorthWest.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-SouthEast.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-SouthEast.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-SouthWest.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-SouthWest.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-WestMast.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-WestMast.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-building.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-building.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-drawing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-drawing.png -------------------------------------------------------------------------------- /static/img/nycmesh-231-SunsetParkLibrary-rack.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-231-SunsetParkLibrary-rack.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-570-227-link-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-570-227-link-2.png -------------------------------------------------------------------------------- /static/img/nycmesh-570-227-link.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-570-227-link.png -------------------------------------------------------------------------------- /static/img/nycmesh-570-battery.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-570-battery.png -------------------------------------------------------------------------------- /static/img/nycmesh-570-coverage.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-570-coverage.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-570-radios.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-570-radios.png -------------------------------------------------------------------------------- /static/img/nycmesh-570-router.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-570-router.png -------------------------------------------------------------------------------- /static/img/nycmesh-570-schematic.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-570-schematic.png -------------------------------------------------------------------------------- /static/img/nycmesh-hubsandhoods.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-hubsandhoods.png -------------------------------------------------------------------------------- /static/img/nycmesh-intersn-20180103a.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-intersn-20180103a.png -------------------------------------------------------------------------------- /static/img/nycmesh-intersn-20180103b.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-intersn-20180103b.png -------------------------------------------------------------------------------- /static/img/nycmesh-ospfexample.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-ospfexample.png -------------------------------------------------------------------------------- /static/img/nycmesh-sn1-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn1-1.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn1-coverage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn1-coverage.png -------------------------------------------------------------------------------- /static/img/nycmesh-sn3-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn3-1.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn3-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn3-2.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn3-3.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn3-3.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn3-pano1-north.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn3-pano1-north.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn3-pano2-south.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn3-pano2-south.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn4-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn4-1.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn4-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn4-2.jpg -------------------------------------------------------------------------------- /static/img/nycmesh-sn4-coverage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/nycmesh-sn4-coverage.png -------------------------------------------------------------------------------- /static/img/sitesafety/equipmentclosetoedge.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/sitesafety/equipmentclosetoedge.jpg -------------------------------------------------------------------------------- /static/img/sitesafety/lockingdoor.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/sitesafety/lockingdoor.jpg -------------------------------------------------------------------------------- /static/img/sitesafety/loosecables.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/sitesafety/loosecables.jpg -------------------------------------------------------------------------------- /static/img/sitesafety/survey.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/sitesafety/survey.jpg -------------------------------------------------------------------------------- /static/img/supernodediagram-2017121501.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/supernodediagram-2017121501.png -------------------------------------------------------------------------------- /static/img/typicalInstall/1unit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/1unit.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/2units.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/2units.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/OmniAlone.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/OmniAlone.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/diagram_lbeOmni_textside.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/diagram_lbeOmni_textside.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/diagram_lbeonly_textbottom.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/diagram_lbeonly_textbottom.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/hub-1350.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/hub-1350.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/hub-greenpoint.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/hub-greenpoint.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/hub-sn4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/hub-sn4.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/hub100AVA.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/hub100AVA.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbe+Omni.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbe+Omni.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbe+OmniPipe.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbe+OmniPipe.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbe+OmniPole.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbe+OmniPole.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbe+Omniwall.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbe+Omniwall.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbeinfrastructure.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbeinfrastructure.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbejpipe.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbejpipe.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbejpipe2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbejpipe2.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbelongpole.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbelongpole.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/lbeventpipe.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/lbeventpipe.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/sxt-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/sxt-1.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/sxt-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/sxt-2.jpg -------------------------------------------------------------------------------- /static/img/typicalInstall/sxt-3.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/img/typicalInstall/sxt-3.jpg -------------------------------------------------------------------------------- /static/mstile-144x144.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/mstile-144x144.png -------------------------------------------------------------------------------- /static/mstile-150x150.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/mstile-150x150.png -------------------------------------------------------------------------------- /static/mstile-310x150.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/mstile-310x150.png -------------------------------------------------------------------------------- /static/mstile-310x310.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/mstile-310x310.png -------------------------------------------------------------------------------- /static/mstile-70x70.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nycmeshnet/docs/73d74a452d05628870f10ea5ff64d8061b3f3ae0/static/mstile-70x70.png -------------------------------------------------------------------------------- /static/safari-pinned-tab.svg: -------------------------------------------------------------------------------- 1 | 2 | 4 | 7 | 8 | Created by potrace 1.11, written by Peter Selinger 2001-2013 9 | 10 | 12 | 17 | 23 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /static/site.webmanifest: -------------------------------------------------------------------------------- 1 | { 2 | "name": "NYC Mesh Docs", 3 | "short_name": "NYC Mesh Docs", 4 | "icons": [ 5 | { 6 | "src": "/android-chrome-192x192.png?v=BG7GElY88J", 7 | "sizes": "192x192", 8 | "type": "image/png" 9 | }, 10 | { 11 | "src": "/android-chrome-512x512.png?v=BG7GElY88J", 12 | "sizes": "512x512", 13 | "type": "image/png" 14 | } 15 | ], 16 | "theme_color": "#ffffff", 17 | "background_color": "#ffffff", 18 | "display": "standalone" 19 | } 20 | --------------------------------------------------------------------------------