Sudo Room - User contributions [en]

Mesh/Distributed Services

2016-07-06T05:14:48Z

Redconfetti: /* Mapping */

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:

* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Mesh Connected Hosts ==

Hosts wishing to offer services can simply connect to the public network port of the home node they've setup to connect to the SudoMesh network.

== Externally Hosted ==

Hosts that are not directly connected to a SudoMesh node can make themselves available on the SudoMesh network by establishing a VPN connection into the network via the Exit node (exit.sudomesh.org). This requires use of the [https://github.com/wlanslovenija/tunneldigger tunneldigger] client. As of Ubuntu 14.4, the required kernel modules supporting [https://en.wikipedia.org/wiki/Layer_2_Tunneling_Protocol L2TP] are not included, so you must build a custom kernel that includes the necessary modules, or use the Debian distribution instead. Plans are in place to eventually use a more efficient tunneling method using [https://github.com/sudomesh/foutun Foo Over UDP], which will eliminate this L2TP complication.

Your host will need to use a static IP assigned from the mesh network. Support for obtaining only a static IP assignment will need to be added to the [https://github.com/sudomesh/makenode makenode] utility to accomplish this.

== Active Services ==

The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

== Architecture: Centralized & decentralized services ==

A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

== Storage / File Systems ==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

== Databases and Servers ==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

== Communications ==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

== Mapping ==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform. Provides stats on the uptime and status of every node, mapping them, contact information, access control levels
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==

* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)
* [https://github.com/telehash/telehash.org/blob/master/v3/intro.md Telehash] - "Telehash is a 100% open, secure mesh networking technology with these design principles: full end-to-end encryption, all the time; strict privacy: no content, identity, or metadata is ever revealed to third parties; maximum app/device compatibility: suitable for embedded, mobile, and web usage; making privacy the easy choice for developers; flexible transport protocols, for compatibility with existing layers; native implementations for the widest possible variety of languages/platforms. The telehash team includes collaborators from around the world, many of whom were the principal architects of XMPP. It is intended as a next-generation protocol advancing the original goals of Jabber."

== Social Platforms ==

* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

== Utilities and Misc ==

* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Template:Mesh nav

2016-07-06T05:06:53Z

Redconfetti:

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Help
!External Links
|-
|[[Mesh/Blog|Blog]]
|[[Mesh/Home_and_extender_nodes|Home and Extender Nodes]]
|[[Mesh/Website|Website]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/FAQ|FAQ]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/Oakland|Oakland]]
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Legal|Legal]]
|[[Mesh/How_to_help|How to Help]]
|[http://meshmap.sudoroom.org sudo mesh map]
|-
|[[Mesh/Interviews with other meshers|Interviews]]
|[[Mesh/Firmware|Firmware]]
|[[Mesh/Stickers|Stickers]]
|[[Mesh/Hosting|Hosting]]
|[[Mesh/ToDos|To-Do's]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/Other mesh projects|Other meshes]]
|[[Mesh/MeshApps|MeshApps]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Backup|Backup]]
|[[Mesh/Wishlist|Wishlist]]
|[http://meshthepla.net meshthepla.net!]
|-
|[[Mesh/Documentation|Documentation]]
|[[Mesh/Network topology|Network topology]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Server security|Server security]]
|
|
|-
|[[Mesh/Distributed_Services|Services]]
|[[Mesh/Specs|Specs]]
|[[Ascii Art]]
|[[Mesh/Naming|Naming]]
|
|
|-
|
|[[Mesh/Frequencies|Frequencies]]
|[[Mesh/Communities|Communities]]
|[[Mesh/Marketing|Marketing]]
|
|
|-
|
|[[Mesh/Software tools|Software tools]]
|[[Mesh/Press|Press]]
|[[Mesh/Purchases|Purchases]]
|
|
|-
|
||[[Mesh/Terms|Terms]]
|[[Mesh/Design|Design]]
|[[Mesh/Inventory|Inventory]]
|
|
|-
|
|[[Mesh/Power|Power]]
|
|[[Mesh/Donations|Donations]]
|
|
|-
|
||[[Mesh/Monitoring|Monitoring]]
|
|[[Mesh/Decisions|Decisions]]
|
|
|-
|
||[[Mesh/Freifunk|Freifunk]]
|
|[[Mesh/Challenges|Challenges]]
|
|
|-
|
||[[Mesh/Commotion|Commotion]]
|
|[[Mesh/Checkouts|Checkouts]]
|
|
|-
|
|[[Mesh/Diagrams|Diagrams]]
|
|[[Mesh/Funding|Funding]]
|
|
|-
|
|[[Mesh/Network|Network]]
|
|
|
|-
|
|[[Mesh/History|History]]
|
|
|
|}

Template:Mesh nav

2016-07-06T05:06:19Z

Redconfetti:

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Help
!External Links
|-
|[[Mesh/Blog|Blog]]
|[[Mesh/Home_and_extender_nodes|Home and Extender Nodes]]
|[[Mesh/Website|Website]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/FAQ|FAQ]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/Oakland|Oakland]]
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Legal|Legal]]
|[[Mesh/How_to_help|How to Help]]
|[http://meshmap.sudoroom.org sudo mesh map]
|-
|[[Mesh/Interviews with other meshers|Interviews]]
|[[Mesh/Firmware|Firmware]]
|[[Mesh/Stickers|Stickers]]
|[[Mesh/Hosting|Hosting]]
|[[Mesh/ToDos|To-Do's]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/Other mesh projects|Other meshes]]
|[[Mesh/MeshApps|MeshApps]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Backup|Backup]]
|[[Mesh/Wishlist|Wishlist]]
|[http://meshthepla.net meshthepla.net!]
|-
|[[Mesh/Documentation|Documentation]]
|[[Mesh/Network topology|Network topology]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Server security|Server security]]
|
|
|-
|
|[[Mesh/Specs|Specs]]
|[[Ascii Art]]
|[[Mesh/Naming|Naming]]
|
|
|-
|
|[[Mesh/Frequencies|Frequencies]]
|[[Mesh/Communities|Communities]]
|[[Mesh/Marketing|Marketing]]
|
|
|-
|
|[[Mesh/Software tools|Software tools]]
|[[Mesh/Press|Press]]
|[[Mesh/Purchases|Purchases]]
|
|
|-
|
||[[Mesh/Terms|Terms]]
|[[Mesh/Design|Design]]
|[[Mesh/Inventory|Inventory]]
|
|
|-
|
|[[Mesh/Power|Power]]
|
|[[Mesh/Donations|Donations]]
|
|
|-
|
||[[Mesh/Monitoring|Monitoring]]
|
|[[Mesh/Decisions|Decisions]]
|
|
|-
|
||[[Mesh/Freifunk|Freifunk]]
|
|[[Mesh/Challenges|Challenges]]
|
|
|-
|
||[[Mesh/Commotion|Commotion]]
|
|[[Mesh/Checkouts|Checkouts]]
|
|
|-
|[[Mesh/Distributed_Services|Services]]
|[[Mesh/Diagrams|Diagrams]]
|
|[[Mesh/Funding|Funding]]
|
|
|-
|
|[[Mesh/Network|Network]]
|
|
|
|-
|
|[[Mesh/History|History]]
|
|
|
|}

Mesh/Distributed Services

2016-07-06T05:03:57Z

Redconfetti: adding simple note about how servers can become available through a mesh connected home node

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:

* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Mesh Connected Hosts ==

Hosts wishing to offer services can simply connect to the public network port of the home node they've setup to connect to the SudoMesh network.

== Externally Hosted ==

Hosts that are not directly connected to a SudoMesh node can make themselves available on the SudoMesh network by establishing a VPN connection into the network via the Exit node (exit.sudomesh.org). This requires use of the [https://github.com/wlanslovenija/tunneldigger tunneldigger] client. As of Ubuntu 14.4, the required kernel modules supporting [https://en.wikipedia.org/wiki/Layer_2_Tunneling_Protocol L2TP] are not included, so you must build a custom kernel that includes the necessary modules, or use the Debian distribution instead. Plans are in place to eventually use a more efficient tunneling method using [https://github.com/sudomesh/foutun Foo Over UDP], which will eliminate this L2TP complication.

Your host will need to use a static IP assigned from the mesh network. Support for obtaining only a static IP assignment will need to be added to the [https://github.com/sudomesh/makenode makenode] utility to accomplish this.

== Active Services ==

The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

== Architecture: Centralized & decentralized services ==

A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

== Storage / File Systems ==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

== Databases and Servers ==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

== Communications ==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

== Mapping ==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform.
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==

* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)
* [https://github.com/telehash/telehash.org/blob/master/v3/intro.md Telehash] - "Telehash is a 100% open, secure mesh networking technology with these design principles: full end-to-end encryption, all the time; strict privacy: no content, identity, or metadata is ever revealed to third parties; maximum app/device compatibility: suitable for embedded, mobile, and web usage; making privacy the easy choice for developers; flexible transport protocols, for compatibility with existing layers; native implementations for the widest possible variety of languages/platforms. The telehash team includes collaborators from around the world, many of whom were the principal architects of XMPP. It is intended as a next-generation protocol advancing the original goals of Jabber."

== Social Platforms ==

* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

== Utilities and Misc ==

* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Mesh/Distributed Services

2016-07-06T05:01:22Z

Redconfetti: adds details on hosting services external to the mesh network (e.g. digital ocean)

The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.

Services (such as file sharing, email, contacts, calendar, and phone) should be provided based on existing free/open source software. Orientation & setup could be built into the introductory process for new mesh users.

Some general aspects worth considering:
* Security
* Integration into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]).

== Externally Hosted ==

Hosts that are not directly connected to a SudoMesh node can make themselves available on the SudoMesh network by establishing a VPN connection into the network via the Exit node (exit.sudomesh.org). This requires use of the [https://github.com/wlanslovenija/tunneldigger tunneldigger] client. As of Ubuntu 14.4, the required kernel modules supporting [https://en.wikipedia.org/wiki/Layer_2_Tunneling_Protocol L2TP] are not included, so you must build a custom kernel that includes the necessary modules, or use the Debian distribution instead. Plans are in place to eventually use a more efficient tunneling method using [https://github.com/sudomesh/foutun Foo Over UDP], which will eliminate this L2TP complication.

Your host will need to use a static IP assigned from the mesh network. Support for obtaining only a static IP assignment will need to be added to the [https://github.com/sudomesh/makenode makenode] utility to accomplish this.

== Active Services ==

The service browser is unfinished, but as we're working on building out the network and setting up services on the network, we can document what we currently have running here for now:

== Architecture: Centralized & decentralized services ==

A central philosophical and practical consideration is how services will be provided. Do we fundamentally want the mesh to be a centralized entity which offers certain services to all members? Or a platform on which individual members can offer services? Or a hybrid?

As it stands now (summer 2015), the mesh offers some opportunity for individual members to offer services. For instance, it's possible for anybody on the mesh to offer services that are accessible elsewhere on the mesh. Should there be (for instance) a central, community-curated file server? Or should it just be up to anybody who wants to, to offer up file shares?

Are there certain kinds of sharing we want to discourage or prohibit, and if so, what will be the social and technical means for enforcement? How will we respond if people start openly sharing copyrighted music and movies? Proprietary software? Child porn? It's worthwhile to think through these scenarios, as a successful network that lacks any kind of governance would become an attractive resource for those whose illegal activities cannot be pursued in the open on the Internet. (An example of this dynamic: [http://www.seattletimes.com/seattle-news/crime/state-supreme-court-rules-against-backpagecom-in-sex-trafficking-suit/ State Supreme Court rules against Backpage.com in sex-trafficking suit], Seattle Times, Sept. 2015)

== Storage / File Systems ==

There are several options for a distributed file system and each have there advantages and disadvantages. The distributed file system can be used to offer file storage or reduce latency across the network.

* [http://opensfs.org/lustre/ Lustre] - Used by sixty percent of the top 100 websites.
** Performance: Amazingly fast! I can assert that Lustre can serve a lot of streams and that encoding speed is not affected by accessing files via Lustre.
** [http://en.wikipedia.org/wiki/POSIX POSIX] compatibility: Very good!. No need to modify applications to use luster.
** Replication, Load Balancing and Fail Over: Very bad!. For replication load balancing we and fail over we need to rely on other software such as virtual IPs and DRDB.
** Installation: The worst!. Impossible to install by mere mortals. Requires a very specific combination of kernel, lustre patches and tweaks to get it working. And current luster patches usually work with old kernels that are incompatible with new hardware/software.

* [https://code.google.com/p/mogilefs/ MogileFS]
** Performance: Good for small files but not usable for medium to large files. This is mostly due to HTTP overhead since all files are send/receive via HTTP requests that encode all data in base64 adding a 33% overhead to each file.
** POXIS compatibility: Non existent. All applications require to be modified to use MogileFS that renders it useless for streaming/encoding since most streaming servers and encoding tools do not understand the protocol.
** Replication and failover out of the box and load balancing can be implemented in the application by accessing more than one tracker at a time.
** Installation: Relatively easy and ready to use packages exist in most distributions. The only difficulty I found was setting the database master-slave to eliminate the single point of failure.

* [http://www.gluster.org/ GlusterFS]
** Performance: Very bad for streaming. I cannot reach more than a few Mbps in a 10Gbps network. Clients and Server CPU skyrockets on heavy writes. For encoding works because the CPU is saturated before the network and I/O.
** POXIS: Almost compatible. The tools I use can access gluster mounts as normal folders in disk but in some edge cases things start causing problems. Check gluster mailing lists and you will see there are a lot of problems.
** Replication, Failover and Load balancing: The best! if they actually worked. Gluster is very new and it has a lot of bugs and performance problems.
** Installation is too easy. The management command line is amazing and setting replicated, striped and distributed volumes among several servers can not be any easier.

([http://stackoverflow.com/questions/916902/lustre-gluster-or-mogilefs-for-video-storage-encoding-and-streaming source of above information])

* [http://hadoop.apache.org/ Hadoop] (HDFS) - slow and has a lot of proprietary derivatives (MapR, GPFS, and [http://gigaom.com/2012/07/11/because-hadoop-isnt-perfect-8-ways-to-replace-hdfs/ other alternatives])
* [http://www.xtreemfs.org/ XtreemFS] - slow and we need more research on it.
* Cassandra File System (CFS) - proprietary software made by DataStax and included in the Enterprise Edition of their software.
* [http://en.wikipedia.org/wiki/Network_File_System Network File Sytem] (NFS) - comparable to Lustre, but the [http://wiki.lustre.org/index.php/NFS_vs._Lustre IO bandwidth doesn't scale].

'''Non-distributed file systems'''
There's the option to use a modern file system with [http://en.wikipedia.org/wiki/Rsync rsync].
[http://rudd-o.com/linux-and-free-software/ways-in-which-zfs-is-better-than-btrfs Comparison of ZFS and BTRFS]
[http://porky.linuxjournal.com:8080/LJ/218/11250.html A Quick Introduction to Modern Filesystems]

== Databases and Servers ==

These are decentralized databases and servers that could ultimately be optimized to store data nearest to where people access it. A significant factors with mesh networks, that as "size and complexity continues to grow, mesh networks that contain multiple hops become increasingly vulnerable to problems such as bandwidth degradation, radio interference and network latency.<ref>[http://www.strixsystems.com/products/datasheets/strixwhitepaper_multihop.pdf Solving the Wireless Mesh Multi-Hop Dilemma]</ref>" There are several other methods of improving network latency, but all means should be tested and implemented to improve services.

* [https://cassandra.apache.org/ cassandra] - a decentralized database with asynchronous masterless replication allowing low latency operations for all clients. Cassandra has [http://en.wikipedia.org/wiki/Hadoop Hadoop] integration, with MapReduce support.
* [https://couchdb.apache.org/ CouchDB] - I can tell you that it quickly becomes complicated to write multi-user app with CouchDB. Decent access control means that you need a database per user and likely a few extra databases. You then have to set all of these databases up to synchronize between each other which is further complicated by the limitations on what information is available by the limitations on how synchronization rules and filters can be written. There seem to be no good tools for managing/visualizing these complex relationships so you end up having to roll your own.
* [https://github.com/mirage/irmin irmin] - a distributed database with built-in snapshot, branch and revert mechanisms. (similar to git)
* [http://code.google.com/p/leveldb/ levelDB] - a fast and lightweight key/value database library.
* [http://www.mongodb.org/ mongoDB] - an open-source document database, a NoSQL database. Written in C++.
* [http://nodejs.org/ node.js] - an HTTP server written in javascript.
* [http://pouchdb.com/ PouchDB] - a javascript based couchDB.
* [https://github.com/dominictarr/scuttlebutt scuttlebutt] - a data synchronization protocol, or a peer-to-peer replicable data structure.
* [https://tahoe-lafs.org/trac/tahoe-lafs tahoe-lafs] - a decentralized database.

== Communications ==

*[http://radicale.org/ radicale] - a CalDAV (calendar) and CardDAV (contacts) server.
*[http://keithp.com/blogs/calypso/ calypso] - Radicale fork with a git back-end (by Keith Packard of X11 fame)
*[http://villagetelco.org Village telco] - an initiative to build low-cost community telephone network hardware and software that can be set up in minutes anywhere in the world. No mobile phone towers or land lines are required, it uses the internet. It has a Simple Unified Dashboard (SPUD) for mesh networks.
*[https://ripple.com/currency/ Ripple] (XRP) - a math-based crypto-currency designed to work seamlessly with the Internet. Powered by a global network of computers; a fast, direct, and secure way to send payments on the web. '''It can be used to prevent malious attacks on servers.'''
*[http://openbts.org/ OpenBTS] - open source cell phone tower software.
*[http://www.openmama.org/what-is-openmama OpenMAMA] - a high performance middleware agnostic messaging API that interfaces with a variety of message oriented middleware systems
*an encrypted asynchronous messaging system to replace email
*a module to have collaborative documents, voting, and groups (ie. [http://en.wikipedia.org/wiki/Collaborative_software groupware])
** Read information about the [http://mitar.tnode.com/post/73983101095/peer-to-peer-voting-scheme peer-to-peer voting scheme].
*a module for peer to peer file sharing.
*a module for object-orientated tagging, shareable feeds.
*a module for feeds and posts, such as [http://www.trsst.com/ Trsst].
* [http://www.frontlinesms.com/ Frontline SMS] - a free, open-source desktop application that allows you to send texts.

== Mapping ==

* [http://nodewatcher.readthedocs.org/en/latest/installation.html NodeWatcher] - an open source network planning, deployment, monitoring and maintanance platform.
* [http://wiki.ninux.org/InstallNodeshot NodeShot] - an easy to use wireless community map server.
* [https://github.com/freifunk/openwifimap-html5 OpenWiFiMap] - a database and map for free network WiFi routers (freifunk and others, too!).
* [https://github.com/libremap LibreMap] - a scalable, global and decentralized router database and map visualization for community networks, such as guifi, ninux, etc.
* [http://tidepools.co Tidepools] - collaborative local mapping software
* [http://ediblecities.org/ Edible Cities] - a food mapping project
* Bulletin Board / Local Classified Ads
** Community Asset Mapping (ex. [http://thepyre.org/wiki/Mycelia Mycelia])

== Protocols ==

* [https://tent.io/ Tent] - a method to store all your data in one place that you control. Instead of your digital life being spread across many services.
* [https://www.docker.io/ Docker] - an open-source project to easily create lightweight, portable, self-sufficient containers from any application.
* [http://maidsafe.net/ MaidSafe] - an encrypted, fully distributed data management service. This network manages static and dynamic data as well as communications. (charges money)
* [https://github.com/telehash/telehash.org/blob/master/v3/intro.md Telehash] - "Telehash is a 100% open, secure mesh networking technology with these design principles: full end-to-end encryption, all the time; strict privacy: no content, identity, or metadata is ever revealed to third parties; maximum app/device compatibility: suitable for embedded, mobile, and web usage; making privacy the easy choice for developers; flexible transport protocols, for compatibility with existing layers; native implementations for the widest possible variety of languages/platforms. The telehash team includes collaborators from around the world, many of whom were the principal architects of XMPP. It is intended as a next-generation protocol advancing the original goals of Jabber."

== Social Platforms ==

* [https://joindiaspora.com/ Diaspora] - a decentralized social network
* [https://identi.ca/ Identi.ca] - a high-performance Open Source social engine.
* [http://pump.io/ Pump] - a stream server that does most of what people really want from a social network.
* [http://twister.net.co/ Twister] - a decentralized, peer to peer microblogging platform

== Utilities and Misc ==

* [https://sudoroom.org/wiki/Mesh/Firmware/Zeroconf Avahi] - a mDNS responder that allows you to broadcast services
* [http://localwiki.org/ Local Wiki] - create a local wikipedia (eg; http://oaklandwiki.org)
* a module for sensor data (eg; Temperature, Seismic activity, air pollution)
* [http://dev.wlan-si.net/wiki/PiplMesh PiplMesh] - an open source social networking and info portal for wireless networks used as a welcome page when users connect to the network.
* [https://neocities.org/ Neocities] ([https://github.com/neocities/neocities git]) - create free user sites
* [http://crabgrass.riseuplabs.org/ Crabgrass] - a project out of riseup labs, a ruby rails application for community organizing. It's not the easiest to run your own instance, but very easy to sign up to their server ([https://we.riseup.net/ we.riseup.net])

= References =
<references/>

Template:Mesh nav

2016-07-06T04:40:07Z

Redconfetti:

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Help
!External Links
|-
|[[Mesh/Blog|Blog]]
|[[Mesh/Home_and_extender_nodes|Home and Extender Nodes]]
|[[Mesh/Website|Website]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/FAQ|FAQ]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/Oakland|Oakland]]
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Legal|Legal]]
|[[Mesh/How_to_help|How to Help]]
|[http://meshmap.sudoroom.org sudo mesh map]
|-
|[[Mesh/Interviews with other meshers|Interviews]]
|[[Mesh/Firmware|Firmware]]
|[[Mesh/Stickers|Stickers]]
|[[Mesh/Hosting|Hosting]]
|[[Mesh/ToDos|To-Do's]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/Other mesh projects|Other meshes]]
|[[Mesh/MeshApps|MeshApps]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Backup|Backup]]
|[[Mesh/Wishlist|Wishlist]]
|[http://meshthepla.net meshthepla.net!]
|-
|[[Mesh/Documentation|Documentation]]
|[[Mesh/Network topology|Network topology]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Server security|Server security]]
|
|
|-
|
|[[Mesh/Specs|Specs]]
|[[Ascii Art]]
|[[Mesh/Naming|Naming]]
|
|
|-
|
|[[Mesh/Frequencies|Frequencies]]
|[[Mesh/Communities|Communities]]
|[[Mesh/Marketing|Marketing]]
|
|
|-
|
|[[Mesh/Software tools|Software tools]]
|[[Mesh/Press|Press]]
|[[Mesh/Purchases|Purchases]]
|
|
|-
|
||[[Mesh/Terms|Terms]]
|[[Mesh/Design|Design]]
|[[Mesh/Inventory|Inventory]]
|
|
|-
|
|[[Mesh/Power|Power]]
|
|[[Mesh/Donations|Donations]]
|
|
|-
|
||[[Mesh/Monitoring|Monitoring]]
|
|[[Mesh/Decisions|Decisions]]
|
|
|-
|
||[[Mesh/Freifunk|Freifunk]]
|
|[[Mesh/Challenges|Challenges]]
|
|
|-
|
||[[Mesh/Commotion|Commotion]]
|
|[[Mesh/Checkouts|Checkouts]]
|
|
|-
|
|[[Mesh/Diagrams|Diagrams]]
|
|[[Mesh/Funding|Funding]]
|
|
|-
|
|[[Mesh/Network|Network]]
|
|
|
|-
|
|[[Mesh/History|History]]
|
|
|
|}

Template:Mesh nav

2016-07-06T04:37:35Z

Redconfetti:

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Help
!External Links
|-
|[[Mesh/Blog|Blog]]
|[[Mesh/History|History]]
|[[Mesh/Home_and_extender_nodes|Home and Extender Nodes]]
|[[Mesh/Website|Website]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/FAQ|FAQ]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/Oakland|Oakland]]
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Legal|Legal]]
|[[Mesh/How_to_help|How to Help]]
|[http://meshmap.sudoroom.org sudo mesh map]
|-
|[[Mesh/Interviews with other meshers|Interviews]]
|[[Mesh/Firmware|Firmware]]
|[[Mesh/Stickers|Stickers]]
|[[Mesh/Hosting|Hosting]]
|[[Mesh/ToDos|To-Do's]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/Other mesh projects|Other meshes]]
|[[Mesh/MeshApps|MeshApps]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Backup|Backup]]
|[[Mesh/Wishlist|Wishlist]]
|[http://meshthepla.net meshthepla.net!]
|-
|[[Mesh/Documentation|Documentation]]
|[[Mesh/Network topology|Network topology]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Server security|Server security]]
|
|
|-
|
|[[Mesh/Specs|Specs]]
|[[Ascii Art]]
|[[Mesh/Naming|Naming]]
|
|
|-
|
|[[Mesh/Frequencies|Frequencies]]
|[[Mesh/Communities|Communities]]
|[[Mesh/Marketing|Marketing]]
|
|
|-
|
|[[Mesh/Software tools|Software tools]]
|[[Mesh/Press|Press]]
|[[Mesh/Purchases|Purchases]]
|
|
|-
|
||[[Mesh/Terms|Terms]]
|[[Mesh/Design|Design]]
|[[Mesh/Inventory|Inventory]]
|
|
|-
|
|[[Mesh/Power|Power]]
|
|[[Mesh/Donations|Donations]]
|
|
|-
|
||[[Mesh/Monitoring|Monitoring]]
|
|[[Mesh/Decisions|Decisions]]
|
|
|-
|
||[[Mesh/Freifunk|Freifunk]]
|
|[[Mesh/Challenges|Challenges]]
|
|
|-
|
||[[Mesh/Commotion|Commotion]]
|
|[[Mesh/Checkouts|Checkouts]]
|
|
|-
|
|[[Mesh/Diagrams|Diagrams]]
|
|[[Mesh/Funding|Funding]]
|
|
|-
|
|[[Mesh/Network|Network]]
|
|
|
|}

Mesh/History

2016-07-06T04:33:53Z

Redconfetti: Created page with "= WLAN = Many of the architectural decisions for the SudoMesh project were based on implementations and lessons learned by [https://wlan-si.net/ wlan slovenija] - open wirele..."

= WLAN =

Many of the architectural decisions for the SudoMesh project were based on implementations and lessons learned by [https://wlan-si.net/ wlan slovenija] - open wireless network of Slovenia.

SudoMesh uses [https://en.wikipedia.org/wiki/Babel_(protocol) Babel], a Mesh routing protocol that didn't exist when the WLAN Slovenija project was started.

Technologies shared by both SudoMesh and WLAN Sovenija include:
* [https://github.com/wlanslovenija/tunneldigger tunneldigger] - VPN tunneling
* [https://github.com/wlanslovenija/nodewatcher nodewatcher] - Network monitoring

Mesh/Network topology

2016-07-06T04:19:17Z

Redconfetti: added backbone connections section with note concerning SF and Laney College desired link

[[File:Network topology diagram-hi.png|thumb|png (hi), [[Mesh/Diagrams#Network Topology Diagram|see more]]]]
= peoplesopen.net topology =
For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram|network topology diagram]].

= wifi topology =

[[File:Mesh topology diagram.png|thumb]]

We use 2.4 ghz 802.11g or 802.11n wifi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for the outdoor APs.

A high-speed wireless backbone for the mesh will be provided by 5 ghz 802.11n hardware, usually with point to point or point to multipoint connections mounted in high places such as on rooftops, flagpoles or antenna towers. We currently have a variety of Ubiquiti M5 routers such as airgrids, nanobridges, nanostations and a rocket.

See the [[Mesh/Home and extender nodes|Home and extender nodes]] for more info about how these are setup.

All of the outdoor gear will be Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

= mesh topology =

All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.

The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.

= internet connectivity =

There are four primary types of devices in the mesh:

*Clients: E.g. smart phones or laptops connected to the mesh.
:These do not run the meshing protocol.
*Mesh nodes: Wifi routers running OpenWRT.
:This includes home nodes and their extender nodes
*Relays / [[Mesh/VPuN|VPuN servers]]: Professionally hosted servers that relay mesh traffic over the internet.
:These run the meshing protocol. Mesh nodes are connected to them with L2TP tunnels.
*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.
:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh. A relay can also be an exit server and this may in fact end up being the case in most instances.

Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run Babel and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.

Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

= Backbone Connections =

== Desired ==

* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.

IRC

2016-07-06T04:04:01Z

Redconfetti: /* Managing Process */

NOTE: a lot of people think that you can get on IRC and talk to people right away. That only works if people are in the channel you want at that very moment, and paying attention to that screen on their computer.

The reality is that most conversations in IRC happen over hours or days, so the only way to fully experience a channel such as #sudoroom is to find a way to stay logged into IRC continuously. If you have a desktop computer that stays powered on and connected to the internet, this is easy. Otherwise, you need to connect to a computer that stays on (such as a server) and leave an IRC session running there, using "screen" or "tmux" as described below.

If you log into IRC and say Hello and nobody gets back you to you for an hour, that is totally normal. If you log out five minutes after asking a question, people will make fun of you an hour later when they look at their IRC sessions.

Internet Relay Chat (IRC) is an instant messaging service that has been used on the internet since the early 1990s. IRC is made possible by the [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat Protocol (IRCP)], an application layer protocol. The chat process works on a client/server networking model. IRC clients are computer programs that a user can install on their system. These clients communicate with chat servers to transfer messages to other clients. IRC is mainly designed for group communication in discussion forums, called channels, but also allows one-on-one communication via private messages as well as chat and data transfer, including file sharing.

Many [https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_protocols other instant messaging services] exist, however many services are proprietary and/or rely on a centralized platform. This does not appeal to organizations that wish to establish a channel of communication that can be adopted by users without fear of unwanted regulations by the service/platform provider. Although open source protocols such as [https://en.wikipedia.org/wiki/XMPP XMPP (formerly Jabber)] exist, IRC continues to be used because it is lightweight and stable.

IRC consists of channels. Each channel is like a chat room, and is represented by a name that begins with '#' followed by a string that represents the primary topic of the channel. Examples: #html, #css, #javascript, #go-lang.

== Recommended Clients ==

There are many various IRC clients available for many platforms.

=== Graphical Clients ===

* Cross-platform
** [https://www.pidgin.im/download/ Pidgin]
* Mac OS X
** [https://adium.im/ Adium]

=== Command Line Interface Clients ===

These clients are intended to be used from the command line interface (CLI), also known as the "terminal".

* [https://irssi.org/ irssi]

== Basics ==

For those that are new to IRC, itâ€™s a good idea to become familiar with the [http://www.ircbeginner.com/ircinfo/ircc-commands.html common commands] that IRC programs support. Here are a few:

{| class="wikitable"
! Command !! Example !! Description
|-
| /join #channel_name || /join #sudoroom ||Join a channel
|-
| /me <action> || /me waves hello || Announces some action
|-
| /msg <nickname> <message> || /msg juul Hey! I need some help || Send a direct message to another user
|-
| /ignore <nickname> || /ignore annoyingperson || Block someone that is harassing you
|-
|}

Although the above commands are likely to be supported by all IRC client programs, some only apply to specific clients. The following are supported by [https://irssi.org/ irssi]:

{| class="wikitable"
! Command !! Example !! Description
|-
| /help || /help || View documentation on supported commands
|-
| /help <command> || /help connect || View documentation on a specific supported command
|-
| /connect <server address> <port> || /connect irc.freenode.net 8001 || Connect to an IRC server
|-
| /set nick <nick> || /set nick someGuy2015 || Register your nickname with the IRC server/network
|-
| /set real_name <real name> || /set nick Bill Murray || Register your real name within the IRC server/network
|-
| /quit || /quit || Quits IRC program
|-
| /exit || /exit || Quits IRC program
|-
|}

See [https://irssi.org/documentation/ IRSSI Documentation] for more commands.

== FreeNode ==

Many programming/hacking communities establish a channel on the [https://en.wikipedia.org/wiki/Freenode FreeNode IRC network] to facilitate discussions and provide support to members of their community.

=== Registering with FreeNode ===

The FreeNode IRC network allows you to register your nickname and associate it with your email address. This is done by using the following commands:

/msg nickserv REGISTER <password> <email>

You should receive a message informing you that you need to check your email account and obtain instructions to verify yourself.

To make sure that your email address isnâ€™t revealed to other users, use the following command to ensure that it is hidden.

/msg NickServ SET HIDEMAIL ON

You can verify your information with the NickServ by using:

/msg nickserv info

== Persistent CLI Client ==

This section is a guide to setting up a command line based IRC client on a persistently running machine so that it stays connected within a channel even when you are not connected to the machine via SSH. This results in the ability to reconnect and view the messages in the channel that occurred even when you were not connected.

These instructions assume you are using an Ubuntu machine, and will be using the [https://irssi.org/ irssi] client.

=== Client Machine ===

You can setup a system at home and configure your home network device(s) to make that machine available via the internet, or alternatively gain shell access to a server on the internet. There are services that provide free or paid shell access, with features and support for IRC that varies. Some of these services even provide support for [https://en.wikipedia.org/wiki/IRC_bot IRC bots]. Alternatively you can pay for a [https://en.wikipedia.org/wiki/Virtual_private_server Virtual Private Server (VPS)] for as low as $5 a month through services such as [digitalocean.com DigitalOcean], thus providing you with an entire UNIX-like server environment that you can use as you wish.

=== Install Client ===

Install the irssi client using the following command:

apt-get install irssi

After itâ€™s done installing, simply run the program

irssi

=== Configure ===

There is a configuration file in ~/.irssi/config that you can inspect, but you can use commands from within the program to configure IRSSI to automatically perform when you first open the program.

The following commands will configure IRSSI to connect to the Freenode network with an SSL connection, with automatic joining of the #sudoroom channel.

/network add Freenode
/server add -auto -ssl -ssl_verify -ssl_capath /etc/ssl/certs -network Freenode irc.freenode.net 7000
/channel add -auto #sudoroom Freenode
/save

After youâ€™ve successfully registered your FreeNode nick name, you can run this command to configure IRSSI to login automatically after connecting to FreeNode.

/network add -autosendcmd "/msg nickserv identify <password> ;wait 2000" Freenode

=== Windows ===

irssi support separate "windows" for the different channels you are connected to, or for the different people you are chatting with. If for some reason you do not see information on the screen for a command youâ€™ve run, it may be displayed in another window.

An Ubuntu terminal can use the ALT key combined with a number key (e.g. ALT+1, ALT+2, ALT+3, etc) to switch between the different displays in IRSSI. This will not work via SSH however, so you will need to use the /window command instead.

/WINDOW NEW - Create new split window
/WINDOW NEW HIDE - Create new hidden window
/WINDOW CLOSE - Close split or hidden window

/WINDOW HIDE [<number>|<name>] - Make the split window hidden window
/WINDOW SHOW <number>|<name> - Make the hidden window a split window

/WINDOW SHRINK [<lines>] - Shrink the split window
/WINDOW GROW [<lines>] - Grow the split window
/WINDOW BALANCE - Balance the sizes of all split windows

=== Managing Process ===

You can use [https://en.wikipedia.org/wiki/GNU_Screen GNU screen] or [https://en.wikipedia.org/wiki/Tmux tmux] to maintain a terminal session that will persist even after you disconnect from the SSH session on your client machine.

For example, you can run 'screen' to start a screen session. Once the session is started, run any program you wish. To disconnect from the session press CTRL-A, followed by D key. You can then safely disconnect from your SSH session. When you return, use `screen -r` to reconnect.

See [http://carina.org.uk/screenirssi.shtml How to use screen and irssi] and [https://michael.lustfield.net/linux/irssi-using-screen-and-ssh IRSSI Using Screen and SSH]

IRC

2016-07-06T04:03:24Z

Redconfetti: /* Managing Process */

NOTE: a lot of people think that you can get on IRC and talk to people right away. That only works if people are in the channel you want at that very moment, and paying attention to that screen on their computer.

The reality is that most conversations in IRC happen over hours or days, so the only way to fully experience a channel such as #sudoroom is to find a way to stay logged into IRC continuously. If you have a desktop computer that stays powered on and connected to the internet, this is easy. Otherwise, you need to connect to a computer that stays on (such as a server) and leave an IRC session running there, using "screen" or "tmux" as described below.

If you log into IRC and say Hello and nobody gets back you to you for an hour, that is totally normal. If you log out five minutes after asking a question, people will make fun of you an hour later when they look at their IRC sessions.

Internet Relay Chat (IRC) is an instant messaging service that has been used on the internet since the early 1990s. IRC is made possible by the [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat Protocol (IRCP)], an application layer protocol. The chat process works on a client/server networking model. IRC clients are computer programs that a user can install on their system. These clients communicate with chat servers to transfer messages to other clients. IRC is mainly designed for group communication in discussion forums, called channels, but also allows one-on-one communication via private messages as well as chat and data transfer, including file sharing.

Many [https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_protocols other instant messaging services] exist, however many services are proprietary and/or rely on a centralized platform. This does not appeal to organizations that wish to establish a channel of communication that can be adopted by users without fear of unwanted regulations by the service/platform provider. Although open source protocols such as [https://en.wikipedia.org/wiki/XMPP XMPP (formerly Jabber)] exist, IRC continues to be used because it is lightweight and stable.

IRC consists of channels. Each channel is like a chat room, and is represented by a name that begins with '#' followed by a string that represents the primary topic of the channel. Examples: #html, #css, #javascript, #go-lang.

== Recommended Clients ==

There are many various IRC clients available for many platforms.

=== Graphical Clients ===

* Cross-platform
** [https://www.pidgin.im/download/ Pidgin]
* Mac OS X
** [https://adium.im/ Adium]

=== Command Line Interface Clients ===

These clients are intended to be used from the command line interface (CLI), also known as the "terminal".

* [https://irssi.org/ irssi]

== Basics ==

For those that are new to IRC, itâ€™s a good idea to become familiar with the [http://www.ircbeginner.com/ircinfo/ircc-commands.html common commands] that IRC programs support. Here are a few:

{| class="wikitable"
! Command !! Example !! Description
|-
| /join #channel_name || /join #sudoroom ||Join a channel
|-
| /me <action> || /me waves hello || Announces some action
|-
| /msg <nickname> <message> || /msg juul Hey! I need some help || Send a direct message to another user
|-
| /ignore <nickname> || /ignore annoyingperson || Block someone that is harassing you
|-
|}

Although the above commands are likely to be supported by all IRC client programs, some only apply to specific clients. The following are supported by [https://irssi.org/ irssi]:

{| class="wikitable"
! Command !! Example !! Description
|-
| /help || /help || View documentation on supported commands
|-
| /help <command> || /help connect || View documentation on a specific supported command
|-
| /connect <server address> <port> || /connect irc.freenode.net 8001 || Connect to an IRC server
|-
| /set nick <nick> || /set nick someGuy2015 || Register your nickname with the IRC server/network
|-
| /set real_name <real name> || /set nick Bill Murray || Register your real name within the IRC server/network
|-
| /quit || /quit || Quits IRC program
|-
| /exit || /exit || Quits IRC program
|-
|}

See [https://irssi.org/documentation/ IRSSI Documentation] for more commands.

== FreeNode ==

Many programming/hacking communities establish a channel on the [https://en.wikipedia.org/wiki/Freenode FreeNode IRC network] to facilitate discussions and provide support to members of their community.

=== Registering with FreeNode ===

The FreeNode IRC network allows you to register your nickname and associate it with your email address. This is done by using the following commands:

/msg nickserv REGISTER <password> <email>

You should receive a message informing you that you need to check your email account and obtain instructions to verify yourself.

To make sure that your email address isnâ€™t revealed to other users, use the following command to ensure that it is hidden.

/msg NickServ SET HIDEMAIL ON

You can verify your information with the NickServ by using:

/msg nickserv info

== Persistent CLI Client ==

This section is a guide to setting up a command line based IRC client on a persistently running machine so that it stays connected within a channel even when you are not connected to the machine via SSH. This results in the ability to reconnect and view the messages in the channel that occurred even when you were not connected.

These instructions assume you are using an Ubuntu machine, and will be using the [https://irssi.org/ irssi] client.

=== Client Machine ===

You can setup a system at home and configure your home network device(s) to make that machine available via the internet, or alternatively gain shell access to a server on the internet. There are services that provide free or paid shell access, with features and support for IRC that varies. Some of these services even provide support for [https://en.wikipedia.org/wiki/IRC_bot IRC bots]. Alternatively you can pay for a [https://en.wikipedia.org/wiki/Virtual_private_server Virtual Private Server (VPS)] for as low as $5 a month through services such as [digitalocean.com DigitalOcean], thus providing you with an entire UNIX-like server environment that you can use as you wish.

=== Install Client ===

Install the irssi client using the following command:

apt-get install irssi

After itâ€™s done installing, simply run the program

irssi

=== Configure ===

There is a configuration file in ~/.irssi/config that you can inspect, but you can use commands from within the program to configure IRSSI to automatically perform when you first open the program.

The following commands will configure IRSSI to connect to the Freenode network with an SSL connection, with automatic joining of the #sudoroom channel.

/network add Freenode
/server add -auto -ssl -ssl_verify -ssl_capath /etc/ssl/certs -network Freenode irc.freenode.net 7000
/channel add -auto #sudoroom Freenode
/save

After youâ€™ve successfully registered your FreeNode nick name, you can run this command to configure IRSSI to login automatically after connecting to FreeNode.

/network add -autosendcmd "/msg nickserv identify <password> ;wait 2000" Freenode

=== Windows ===

irssi support separate "windows" for the different channels you are connected to, or for the different people you are chatting with. If for some reason you do not see information on the screen for a command youâ€™ve run, it may be displayed in another window.

An Ubuntu terminal can use the ALT key combined with a number key (e.g. ALT+1, ALT+2, ALT+3, etc) to switch between the different displays in IRSSI. This will not work via SSH however, so you will need to use the /window command instead.

/WINDOW NEW - Create new split window
/WINDOW NEW HIDE - Create new hidden window
/WINDOW CLOSE - Close split or hidden window

/WINDOW HIDE [<number>|<name>] - Make the split window hidden window
/WINDOW SHOW <number>|<name> - Make the hidden window a split window

/WINDOW SHRINK [<lines>] - Shrink the split window
/WINDOW GROW [<lines>] - Grow the split window
/WINDOW BALANCE - Balance the sizes of all split windows

=== Managing Process ===

You can use [GNU screen](https://en.wikipedia.org/wiki/GNU_Screen) or [tmux](https://en.wikipedia.org/wiki/Tmux) to maintain a terminal session that will persist even after you disconnect from the SSH session on your client machine.

For example, you can run 'screen' to start a screen session. Once the session is started, run any program you wish. To disconnect from the session press CTRL-A, followed by D key. You can then safely disconnect from your SSH session. When you return, use `screen -r` to reconnect.

See [http://carina.org.uk/screenirssi.shtml How to use screen and irssi] and [https://michael.lustfield.net/linux/irssi-using-screen-and-ssh IRSSI Using Screen and SSH]

IRC

2016-07-06T03:50:15Z

Redconfetti: /* Client Machine */

NOTE: a lot of people think that you can get on IRC and talk to people right away. That only works if people are in the channel you want at that very moment, and paying attention to that screen on their computer.

The reality is that most conversations in IRC happen over hours or days, so the only way to fully experience a channel such as #sudoroom is to find a way to stay logged into IRC continuously. If you have a desktop computer that stays powered on and connected to the internet, this is easy. Otherwise, you need to connect to a computer that stays on (such as a server) and leave an IRC session running there, using "screen" or "tmux" as described below.

If you log into IRC and say Hello and nobody gets back you to you for an hour, that is totally normal. If you log out five minutes after asking a question, people will make fun of you an hour later when they look at their IRC sessions.

Internet Relay Chat (IRC) is an instant messaging service that has been used on the internet since the early 1990s. IRC is made possible by the [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat Protocol (IRCP)], an application layer protocol. The chat process works on a client/server networking model. IRC clients are computer programs that a user can install on their system. These clients communicate with chat servers to transfer messages to other clients. IRC is mainly designed for group communication in discussion forums, called channels, but also allows one-on-one communication via private messages as well as chat and data transfer, including file sharing.

Many [https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_protocols other instant messaging services] exist, however many services are proprietary and/or rely on a centralized platform. This does not appeal to organizations that wish to establish a channel of communication that can be adopted by users without fear of unwanted regulations by the service/platform provider. Although open source protocols such as [https://en.wikipedia.org/wiki/XMPP XMPP (formerly Jabber)] exist, IRC continues to be used because it is lightweight and stable.

IRC consists of channels. Each channel is like a chat room, and is represented by a name that begins with '#' followed by a string that represents the primary topic of the channel. Examples: #html, #css, #javascript, #go-lang.

== Recommended Clients ==

There are many various IRC clients available for many platforms.

=== Graphical Clients ===

* Cross-platform
** [https://www.pidgin.im/download/ Pidgin]
* Mac OS X
** [https://adium.im/ Adium]

=== Command Line Interface Clients ===

These clients are intended to be used from the command line interface (CLI), also known as the "terminal".

* [https://irssi.org/ irssi]

== Basics ==

For those that are new to IRC, itâ€™s a good idea to become familiar with the [http://www.ircbeginner.com/ircinfo/ircc-commands.html common commands] that IRC programs support. Here are a few:

{| class="wikitable"
! Command !! Example !! Description
|-
| /join #channel_name || /join #sudoroom ||Join a channel
|-
| /me <action> || /me waves hello || Announces some action
|-
| /msg <nickname> <message> || /msg juul Hey! I need some help || Send a direct message to another user
|-
| /ignore <nickname> || /ignore annoyingperson || Block someone that is harassing you
|-
|}

Although the above commands are likely to be supported by all IRC client programs, some only apply to specific clients. The following are supported by [https://irssi.org/ irssi]:

{| class="wikitable"
! Command !! Example !! Description
|-
| /help || /help || View documentation on supported commands
|-
| /help <command> || /help connect || View documentation on a specific supported command
|-
| /connect <server address> <port> || /connect irc.freenode.net 8001 || Connect to an IRC server
|-
| /set nick <nick> || /set nick someGuy2015 || Register your nickname with the IRC server/network
|-
| /set real_name <real name> || /set nick Bill Murray || Register your real name within the IRC server/network
|-
| /quit || /quit || Quits IRC program
|-
| /exit || /exit || Quits IRC program
|-
|}

See [https://irssi.org/documentation/ IRSSI Documentation] for more commands.

== FreeNode ==

Many programming/hacking communities establish a channel on the [https://en.wikipedia.org/wiki/Freenode FreeNode IRC network] to facilitate discussions and provide support to members of their community.

=== Registering with FreeNode ===

The FreeNode IRC network allows you to register your nickname and associate it with your email address. This is done by using the following commands:

/msg nickserv REGISTER <password> <email>

You should receive a message informing you that you need to check your email account and obtain instructions to verify yourself.

To make sure that your email address isnâ€™t revealed to other users, use the following command to ensure that it is hidden.

/msg NickServ SET HIDEMAIL ON

You can verify your information with the NickServ by using:

/msg nickserv info

== Persistent CLI Client ==

This section is a guide to setting up a command line based IRC client on a persistently running machine so that it stays connected within a channel even when you are not connected to the machine via SSH. This results in the ability to reconnect and view the messages in the channel that occurred even when you were not connected.

These instructions assume you are using an Ubuntu machine, and will be using the [https://irssi.org/ irssi] client.

=== Client Machine ===

You can setup a system at home and configure your home network device(s) to make that machine available via the internet, or alternatively gain shell access to a server on the internet. There are services that provide free or paid shell access, with features and support for IRC that varies. Some of these services even provide support for [https://en.wikipedia.org/wiki/IRC_bot IRC bots]. Alternatively you can pay for a [https://en.wikipedia.org/wiki/Virtual_private_server Virtual Private Server (VPS)] for as low as $5 a month through services such as [digitalocean.com DigitalOcean], thus providing you with an entire UNIX-like server environment that you can use as you wish.

=== Install Client ===

Install the irssi client using the following command:

apt-get install irssi

After itâ€™s done installing, simply run the program

irssi

=== Configure ===

There is a configuration file in ~/.irssi/config that you can inspect, but you can use commands from within the program to configure IRSSI to automatically perform when you first open the program.

The following commands will configure IRSSI to connect to the Freenode network with an SSL connection, with automatic joining of the #sudoroom channel.

/network add Freenode
/server add -auto -ssl -ssl_verify -ssl_capath /etc/ssl/certs -network Freenode irc.freenode.net 7000
/channel add -auto #sudoroom Freenode
/save

After youâ€™ve successfully registered your FreeNode nick name, you can run this command to configure IRSSI to login automatically after connecting to FreeNode.

/network add -autosendcmd "/msg nickserv identify <password> ;wait 2000" Freenode

=== Windows ===

irssi support separate "windows" for the different channels you are connected to, or for the different people you are chatting with. If for some reason you do not see information on the screen for a command youâ€™ve run, it may be displayed in another window.

An Ubuntu terminal can use the ALT key combined with a number key (e.g. ALT+1, ALT+2, ALT+3, etc) to switch between the different displays in IRSSI. This will not work via SSH however, so you will need to use the /window command instead.

/WINDOW NEW - Create new split window
/WINDOW NEW HIDE - Create new hidden window
/WINDOW CLOSE - Close split or hidden window

/WINDOW HIDE [<number>|<name>] - Make the split window hidden window
/WINDOW SHOW <number>|<name> - Make the hidden window a split window

/WINDOW SHRINK [<lines>] - Shrink the split window
/WINDOW GROW [<lines>] - Grow the split window
/WINDOW BALANCE - Balance the sizes of all split windows

=== Managing Process ===

Use 'screen' command on the VPS to

CTRL-A, then D - disconnect from the screen instance, and then use `screen -r`.

tmux (terminal multiplexer) is another option

See [http://carina.org.uk/screenirssi.shtml How to use screen and irssi] and [https://michael.lustfield.net/linux/irssi-using-screen-and-ssh IRSSI Using Screen and SSH]

Mesh/Technical Overview

2016-06-01T04:04:40Z

Redconfetti: /* Detailed Documentation */

[[File:Sudomesh home and extender node illustration extra-simplified.png|thumb|Illustration showing how a sudomesh home node can connect to a window-mounted extender node. The device with two antennas is the home node and the device on the outside of the window is an extender node.]]

[[File:Sudomesh home and extender node illustration.png|thumb|Illustration showing a more complicated setup. Here the node operator has connected their personal computer, a small Raspberry Pi computer and two extender nodes: One on the outside of the window and one on the roof (not shown but a can be seen going up and out of the frame). This is definitely an advanced node operator.]]

[[File:Sudomesh home node ethernet ports.png|thumb|A close-up of the wired network ports on the home node and their use.]]

== Home and extender nodes ==

''Note: You can also read the [[home node|non-technical explanation of home nodes and extender nodes]].''

Our mesh has two types of nodes: Home nodes and extender nodes.

The home nodes run the full sudowrt firmware and on its own a bunch of home nodes will make up a fine mesh network. The home node is a normal five-ethernet-port indoor wifi router. An extender node runs a minimal firmware and does nothing on its own. Instead, the extender node basically acts as extra radios when plugged in to a home node. The node operator can put a home node in e.g. their living room and if they later decide they want a high speed directional link to a neighbour then they can put e.g. a Nanobridge M5 running the extender node firmware on their roof and connect it via ethernet to the home node. Or they could put a Nanostation M2 pointed out their window and extend the signal further out into the street or to nearby neighbours. Each extender node extends all three networks (explained in the next section).

For home nodes we are currently only officially supporting the [http://www.tp-link.us/products/details/cat-9_TL-WDR3600.html TP-Link TL-WDR3600]. We are not planning to support anything else for the time being, though if you have a good reason please let us know. For extender nodes we are currently supporting the Ubiquiti Nanobridge M series and the Ubiquiti Nanostation M series.

The mesh is made up mostly of wifi routers using Atheros chipsets and running [https://github.com/sudomesh/sudowrt-firmware our own firmware] based on [http://openwrt.org/ OpenWRT], [http://www.pps.univ-paris-diderot.fr/~jch/software/babel/ Babel] and wlan slovenja's [https://github.com/sudomesh/tunneldigger tunneldigger].

Node-owners can choose to connect the nodes to their existing internet connection using ethernet. If they have Internet access, they can share a portion of it with the mesh. The amount of bandwidth shared is limited with 'tc'. It is chosen at node-configuration time and can be changed using the simple built-in web admin interface.

== The three wifi networks and IP assignment ==

The nodes each run three wifi networks (three SSIDs on the same physical wifi interfaces):

* The Open network with SSID peoplesopen.net is an open access point. Most people will use the network by connecting to this.
* The Mesh network with SSID pplsopen.net-node2node is an ad-hoc network that the nodes use to mesh with each other using Babel
* A private wifi network that is named by the node owner (or a name is generated) and uses WPA2-PSK.

All three of these networks are available on both 2.4 and 5 GHz on the home node. They are also all three available on any extender nodes plugged in to the home node. The three different networks are extended over a single ethernet cable using VLANs.

If a node-owner is sharing internet, then the node will create a layer 2 (L2TP) tunnel to a VPN server on the Internet using tunneldigger. Babel (the mesh routing protocol) will connect over this tunnel to other nodes on the mesh, so the mesh can route traffic over the internet if no wifi path to another node is available (e.g. other nodes are physically too far away). When people connect to the peoplesopen.net access point and try to access the Internet, the traffic will flow through the VPuN, and the source IP of requests will appear to be the VPuN with the sudo mesh organization listed as the abuse contact.

The nodes run DHCP servers and each have a /24 IPv4 subnet in the 100.64.0.0/10 range that is statically assigned by coordination between mesh groups and individuals hosting and administrating their own nodes on People's Open Network (currently only the sudo mesh organization).

The private network does not limit bandwidth and provides access to both direct access to the Internet (if the node owner has hooked the node up to the Internet) and access to the mesh. Each node's private network runs on 172.30.0.0/16 and uses NAT between the private network and the mesh. It does not accept any new incoming connections from the mesh onto the 172.30.0.0/16 subnet.

== Accessing Home Node via SSH ==

Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server on port 22.

The 4 Ethernet ports that are provided with your router should be configured as follows:

# Private network with DHCP of 172.30.0.x network addresses
# Public network with DHCP of 100.64.x.x network addresses (SudoMesh network)
# NotDHCP for Extender 1
# NotDHCP for Extender 2

This may not apply to your router. For instance, the TP-Link N750 uses the opposite port assignment, with port 3 for private network, and port 4 for public SudoMesh/PeoplesOpen.net network.

=== Network Settings ===

=== Default Build Configuration ===

The IP address of your home node is <tt>172.22.0.1</tt> prior to configuration via the [https://github.com/sudomesh/makenode makenode] utility. You can SSH into the node as <tt>root</tt> using the password 'meshtheplanet' after setting up your computer to use an IP on the 172.22.0.0/16 network.

=== Post Makenode Configuration ===

The private network configuration uses a 172.30.0.0/16 network with DHCP available for connected clients. You can configure your workstation to use the following manual network configuration so that you can SSH into your home node.

* IP Address: 172.30.0.9 (or anything other than 172.30.0.1)
* Netmask: 255.255.255.0
* Gateway: 172.30.0.1

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

The IP of your home node on the private network is <tt>172.30.0.1</tt>, with the root password you specified when running <tt>makenode</tt> to configure it.

ssh root@172.30.0.1
The authenticity of host '172.30.0.1 (172.30.0.1)' can't be established.
RSA key fingerprint is b8:9d:4a:2f:1b:f5:e1:ae:b8:19:5b:70:92:8b:7f:34.
Are you sure you want to continue connecting (yes/no)?

After accepting the key by entering 'yes' and pressing ENTER, it will ask you for the root password.

=== SSH Keys ===

If you'd like to add your ssh key to the router (instead of using a root password), add it to the <tt>configs/authorized_keys</tt> file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

== Node flashing and configuration ==

One of our medium-term goals is to be able to sell nodes on our website and minimize the amount of work required to re-flash/configure the nodes and provide documentation for the user. To facilitate this, our current process for new nodes is:

* A new node is flashed either automatically (using e.g. [https://github.com/sudomesh/ubiquiti-flasher ubiquiti-flasher] or [https://github.com/sudomesh/merakiflasher merakiflasher]) or manually with your own tools and the [https://github.com/sudomesh/sudowrt-firmware sudowrt] firmware.
* The node is then configured by a sudo mesh volunteer using our [https://github.com/sudomesh/makenode makenode] software.
* makenode generates SSH keys, SSH root password, web admin password and private wifi password, then it configures the node, saves the info in the [https://github.com/sudomesh/node-database node database] and shuts down the node.
* makenode then automatically [https://github.com/sudomesh/ql570 prints a sticker] containing some basic info including wifi and web admin passwords.
* The sudo mesh volunteer attaches the sticker to the nodes power supply and puts the node back in the box with a set of instructions for how to install and use the node.
* The node is shipped to the new node owner!

== Node management ==

All nodes set up by sudo mesh automatically allow root access using an SSH key held by a few trusted sudo mesh organizers. This is to allow us to update the firmware and troubleshoot network issues. We inform node-owners of this fact and tell them how to prevent sudo mesh from accessing their nodes, but also indicate that they should be ready to manage their own node if they choose to do this.

We don't yet have a solution for node monitoring but we're expecting to use the new version of wlan slovenja's nodewatcher software.

We don't yet have an automatic update solution in place, but we are looking at the software used by Gluon. The Gluon update system is centralized but in the long term we would like to have a decentralized system that works something like this:

* Any number of node-updater servers announce themselves on the mesh and whether or not an update is available.
* The nodes run a future version of mdnssd-min as a daemon that keeps a currently list of node-updaters.
* Once every N hours +/- a random factor, if any node-updaters have updates available, all nodes connect to a randomly chosen node-updater and request an update.
* The node-updaters send the nodes an ipk file with the update and the nodes check the signature and install it if it's signed by a trusted authority.

==Detailed Documentation==
*[[Mesh/Tracking]] - Problems and solutions related to tracking, logging and anonymity
*[[Mesh/WalkThrough]] - Easy how-to for setting up OpenWRT
**[[Mesh/Flashing Extender Antennas]] - How-to for Ubiquiti routers
**[[Mesh/OpenWRT]] - Experiences with the OpenWRT router firmware
*[[Mesh/Firmware]] - Everything related to our firmware
**[[Mesh/Firmware/Overview]] - High level view
**[[Mesh/Firmware/Flash]] - How to install the sudowrt firmware based on openwrt with supported hardware
**[[Mesh/Firmware/Splash page]] - Splash page / Captive Portal
**[[Mesh/Firmware/Bandwidth shaping]] - QoS / Bandwidth shaping
**[[Mesh/Firmware/Zeroconf]] - Issues related to mDNS and DNS-SD
**[[Mesh/Firmware/MTU_issues]] - MTU issues
**[[Mesh/Firmware/Web Admin Development]] - Web admin development
*[[Mesh/Network topology]] - High-level explanation of the mesh network structure
*[[Mesh/Specs]] - Specs sheet on different access points
*[[Mesh/Frequencies]] - Information on different frequencies.
*[[Mesh/Software tools]] - List of useful mesh troubleshooting tools
*[[Mesh/Terms]] - Hidden Node, Fresnal zone, and other jargons
*[[Mesh/Power]] - Stuff about power usage, batteries and solar power.
*[[Mesh/Monitoring]] - notes about how to monitor systems
*[[Mesh/Spectrum]] - Different forms of spectral analysis
*[[Mesh/Hardware support]] - Officially and unofficially supported hardware / routers
*[[Mesh/Relay setup]] - Setting up a relay node
*[[Mesh/Exit setup]] - Setting up an exit node
*[[Mesh/Spectrum mapping]] - The setup we use for mapping local spectrum and wifi usage
**[[Mesh/Spectrum mapping/XO-1 Laptop]] - How to configure an XO-1 laptop for use with our spectrum mapping setup
* [[Mesh/Install]] - physical installation notes/stories
* [[Mesh/Diagrams]] - technical diagrams to support new outreach materials

Sudoroom

2016-05-15T04:54:55Z

Redconfetti: /* Upcoming Events */

__NOTOC__
[[File:SudoMesh-2.jpg|thumb|SudoMesh over Oakland]]
[[File:SudoMesh Node.png|frameless|right|300px]]
[[File:Graph theory lesson.JPG|frameless|right|300px]]
[[File:Cyberwizard Institute Version 2 Flyer.png|frameless|right|300px]]
[[File:Sudo_room_remix_raster.png|frameless|right|300px]]
[[File:Sudoroom people.png|human beings visit SudoRoom along with small animals|right|frameless|300px]]
[[File:Sudo-intro-comic.jpg|frameless|right|300px]]

*We're '''Sudo Room''', a ''free'' hackerspace located at '''[[Directions|4799 Shattuck]]''' in north Oakland, CA!
*We're into '''technology''' and where it intersects with '''social justice''', '''sustainability''', '''education''' and '''solidarity'''.
*We strive to be an '''open''', '''transparent''', '''horizontal''' and '''welcoming''' community where all are supported and free to ''learn'', ''create'', ''gather'', ''collaborate'', ''work'', ''play'' and ''more''! .
*We've got tons of '''tools''' for you to use from a '''3D printer''' to '''public computer terminals''', [[Math]] projects, a '''big huge library''' and '''all kinds of gadgets'''!
*We are exclusively '''volunteer-run''' and supported through '''[[Gittip|donations]]'''!! Learn more about [[Membership|membership]].
*Our slogan is: '''''HACK THE PLANET!'''''
* Check out [[Projects|some of the things we are working on]]!
* Way more details: [[Welcome|Welcome]]

== '''Upcoming Events''' ==
:''See also: [https://sudoroom.org/calendar/ Sudo Room Calendar] and [https://omnicommons.org/calendar/ Omni Commons Global Calendar]''

{| class="wikitable" style=""
! colspan="2"| Weekly Events
|-
| '''[[Fermentation]] Mondays
(5-7p)'''
| collaboration & meet up - come learn Kombucha & other fermentations!
or help us build temperature, humidity and PH monitoring using Raspberry PI to record our brews.
|-
| '''[[HardwareHackNight]] Tuesdays
(6-11p)'''
| [[image:SudoRoom_hardware_hacknight.jpg|thumb|120px|A large animal will lead you through real life stuff, you digital wimps ;)]]
Come hack on hardware. build stuff! take apart small robotic animals, electronics & make things
|-
| '''[[Meetings|Sudoroom Party / Meetings]]
(Wednesdays 7p)'''
| Every 2nd Wednesday is the Official meeting of organization, bureaucracy and fun. All other Wednesdays are an informal [https://sudoroom.org/events/sudoroom-weekly-meeting-2016-05-25/ Party]

We keep our agenda on an [https://pad.riseup.net/ etherpad] and then [[Meetings#Meeting_Notes_Archive|archive the meeting minutes]]. We're a California non-profit. See our [[Articles of Association]].
|-
| '''[https://sudoroom.org/wiki/Javascript Javascript study group]
(Thursdays 6:30p)'''
| [[File:JavasScript Forest at SudoRoom.png|thumb|Sudoroom Javascript forest]] Learn, chat and hack on node.js, frontend, or whatever!
Oakland is [http://oaklandwiki.org/Javascript javascript city].
|-
! colspan="2" | Every other week
|-
| '''[http://oaklandwiki.org/ Oakland Wiki]
(Every other Thursday 7-8:30p)'''
| Come edit Oakland's only open, publicly editable wiki! Oakland Wiki has been used as a platform for [http://oaklandwiki.org/Domain_Awareness_Center citizen journalism], sharing local [http://oaklandwiki.org/Resources resources] and [http://oaklandwiki.org/Oakland_Chicano_Moratorium history], and whatever else you can [http://oaklandwiki.org/tags/fun dream up].
|-
! colspan="2" | Monthly Events
|-
| '''[[Mesh]]
(Last Tuesday of the month 7:30-10p)'''
| [[image:510NetworkDishes.jpg|thumb|120px|the antenna that beamed wireless packets across Lake Merritt]]
A group [[Mesh|working]] on bringing [http://peoplesopen.net/ free wifi] to the East Bay. We hack every week but Last Tuesday's is our open meeting for new folk!
|-
| '''[[Cryptoparty]]
(Third Sundays 2-5p)'''
| Learn & talk about encryption & cybersecurity. Learn how to use GPG, OTR, Tor, Tails, and other anti-surveillance technologies. (currently on hiatus but coming back soon)
|}
Categories of Wiki pages: {{Special:Categories}}

Meetings

2016-05-15T04:50:41Z

Redconfetti: added update regarding 2nd wednesday

[[File:Sudo Room Meeting April 17, 2013.jpg|thumb|right|April 2013 Meeting]]
Sudoroom's official meetings are every 2nd Wednesday of the month at 7pm, or sometimes as late as 7:30. They are bureaucratic, sometimes fun, and usually more functional than rumored. We try to handle conflicts respectfully.

All other Wednesdays are [https://sudoroom.org/events/sudoroom-weekly-meeting-2016-05-25/ parties].

== Etherpad ==

We keep our agenda on an etherpad. The etherpad is projected on a big screen for everyone to see. Anyone who knows the URL can collaboratively edit it on their laptop. After the meeting, its contents are copied to our wiki - that's how we keep record. Then we clear it for the next meeting and people can add items throughout the week. Ideally someone posts a summary to the mailing list, but that doesn't always happen.

Unfortunately, in the past our etherpad has caught the attention of online troll dens who like to overwhelm it and make it unusable. For this reason, we don't post the address online. Sorry! '''These addresses''' had been used in the past, and '''are obsolete''':
* https://pad.riseup.net/p/sudoroom
* https://pad.riseup.net/p/sudoroommeeting

== Archive ==

Each old meeting gets its own page, and we link to them here.

{| class="wikitable sortable collapsible"
! colspan="3"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | new member interviews
! class="unsortable" | comments
|-
| [[Meeting_Notes_2016-04-20|2016-04-20]]
|
|
|-
| [[Meeting_Notes_2016-04-13|2016-04-13]]
| Abhiram Pete Forsyth Dirty Bill Chris Jamie
|
|-
| [[Meeting_Notes_2016-04-06|2016-04-06]]
| Jacob Jason
|
|-
| 2016-03-30
|rowspan=6 colspan=2 align=center|We totally flaked for the entire month of March.
|-
| 2016-03-23
|-
| 2016-03-23
|-
| 2016-03-16
|-
| 2016-03-09
|-
| 2016-03-02
|-
| [[Meeting_Notes_2016-02-24|2016-02-24]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-17|2016-02-17]]
| bstack
|
|-
| [[Meeting_Notes_2016-02-10|2016-02-10]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-02-03|2016-02-03]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-27|2016-01-27]]
| Jay
|
|-
| [[Meeting_Notes_2016-01-20|2016-01-20]]
| ''(none)''
|
|-
| [[Meeting_Notes_2016-01-13|2016-01-13]]
|
| cancelled-ish
|-
| [[Meeting_Notes_2016-01-06|2016-01-06]]
| nathan Nick
|
|-
| [[Meeting_Notes_2015-12-30|2015-12-30]]
| Charley
|
|-
| 2015-12-23
|
| no signs of having happened
|-
| [[Meeting_Notes_2015-12-16|2015-12-16]]
| Daisy
|
|-
| [[Meeting_Notes_2015-12-09|2015-12-09]]
|
|
|-
| [[Meeting_Notes_2015-12-02|2015-12-02]]
| Max
|
|-
| [[Meeting_Notes_2015-11-25|2015-11-25]]
|
| didn't really happen, blame thanksgiving
|-
| [[Meeting_Notes_2015-11-18|2015-11-18]]
| morgan
|
|-
| [[Meeting_Notes_2015-11-11|2015-11-11]]
| Kwaku Gracie Micolah
|
|-
| [[Meeting_Notes_2015-11-04|2015-11-04]]
| dane
|
|-
| [[Meeting_Notes_2015-10-28|2015-10-28]]
| Andrew
|
|-
| [[Meeting Notes 2015-10-21|2015-10-21]]
| Merry
|
|-
| [[Meeting Notes 2015-10-14|2015-10-14]]
| Alex Lef Mari
|
|-
| [[Meeting Notes 2015-10-07|2015-10-07]]
| Tom Daron
|
|-
| [[Meeting Notes 2015-09-30|2015-09-30]]
|
| Insufficient critical mass
|-
| [[Meeting Notes 2015-09-23|2015-09-23]]
| Ari
|
|-
| [[Meeting Notes 2015-09-16|2015-09-16]]
| david
|
|-
| [[Meeting Notes 2015-09-09|2015-09-09]]
|
|
|-
| [[Meeting Notes 2015-09-02|2015-09-02]]
| Benji
|
|-
| [[Meeting Notes 2015-08-26|2015-08-26]]
|
|
|-
| 2015-08-19
|
| nobody showed up
|-
| [[Meeting Notes 2015-08-12|2015-08-12]]
|
|
|-
| [[Meeting Notes 2015-08-05|2015-08-05]]
|
|
|-
| [[Meeting Notes 2015-07-29|2015-07-29]]
|
|
|-
| [[Meeting_Notes_2015-07-22|2015-07-22]]
|
|
|-
| [[Meeting_Notes_2015-07-15|2015-07-15]]
|
|
|-
| [[Meeting_Notes_2015-07-08|2015-07-08]]
|
|
|-
| [[Meeting_Notes_2015-07-01|2015-07-01]]
|
|
|-
| [[Meeting_Notes_2015-06-24|2015-06-24]]
|
|
|-
| [[Meeting_Notes_2015-06-17|2015-06-17]]
|
|
|-
| [[Meeting_Notes_2015-06-10|2015-06-10]]
|
|
|-
| [[Meeting_Notes_2015-06-03|2015-06-03]]
|
|
|-
| [[Meeting_Notes_2015-05-27|2015-05-27]]
|
|
|-
| [[Meeting_Notes_2015-05-20|2015-05-20]]
|
|
|-
| [[Meeting_Notes_2015-05-13|2015-05-13]]
|
|
|-
| [[Meeting_Notes_2015-05-06|2015-05-06]]
|
|
|-
| [[Meeting_Notes_2015-04-29|2015-04-29]]
|
|
|-
| [[Meeting_Notes_2015-04-22|2015-04-22]]
|
|
|-
| [[Meeting_Notes_2015-04-15|2015-04-15]]
|
|
|-
| [[Meeting_Notes_2015-04-08|2015-04-08]]
|
|
|-
| [[Meeting_Notes_2015-04-01|2015-04-01]]
|
|
|-
| [[Meeting_Notes_2015-03-25|2015-03-25]]
|
|
|-
| [[Meeting_Notes_2015-03-18|2015-03-18]]
|
|
|-
| [[Meeting_Notes_2015-03-11|2015-03-11]]
|
|
|-
| [[Meeting_Notes_2015-03-04|2015-03-04]]
|
|
|-
| [[Meeting_Notes_2015-02-25|2015-02-25]]
|
|
|-
| [[Meeting_Notes_2015-02-18|2015-02-18]]
|
|
|-
| [[Meeting_Notes_2015-02-11|2015-02-11]]
|
|
|-
| [[Meeting_Notes_2015-02-04|2015-02-04]]
|
|
|-
| [[Meeting_Notes_2015-01-28|2015-01-28]]
|
|
|-
| [[Meeting_Notes_2015-01-21|2015-01-21]]
|
|
|-
| [[Meeting_Notes_2015-01-14|2015-01-14]]
|
|
|-
| [[Meeting_Notes_2015-01-07|2015-01-07]]
|
|
|-
| [[Meeting_Notes_2014-12-31|2014-12-31]]
|
|
|-
| [[Meeting_Notes_2014-12-24|2014-12-24]]
|
|
|-
| [[Meeting_Notes_2014-12-17|2014-12-17]]
|
|
|-
| [[Meeting_Notes_2014-12-10|2014-12-10]]
|
|
|-
| [[Meeting_Notes_2014-12-03|2014-12-03]]
|
|
|-
| [[Meeting_Notes_2014-11-26|2014-11-26]]
|
|
|-
| [[Meeting_Notes_2014-11-19|2014-11-19]]
|
|
|-
| [[Meeting_Notes_2014-11-12|2014-11-12]]
|
|
|-
| [[Meeting_Notes_2014-11-05|2014-11-05]]
|
|
|-
| [[Meeting_Notes_2014-10-29|2014-10-29]]
|
|
|-
| [[Meeting_Notes_2014-10-27|2014-10-27]]
|
| Board of Directors Meeting
|-
| [[Meeting_Notes_2014-10-22|2014-10-22]]
|
|
|-
| [[Meeting_Notes_2014-10-15|2014-10-15]]
|
|
|-
| [[Meeting_Notes_2014-10-08|2014-10-08]]
|
|
|-
| [[Meeting_Notes_2014-10-01|2014-10-01]]
|
|
|-
| [[Meeting_Notes_2014-09-24|2014-09-24]]
|
|
|-
| [[Meeting_Notes_2014-09-17|2014-09-17]]
|
|
|-
| [[Meeting_Notes_2014-09-10|2014-09-10]]
|
|
|-
| [[Meeting_Notes_2014-09-03|2014-09-03]]
|
|
|-
| [[Meeting_Notes_2014-08-27|2014-08-27]]
|
|
|-
| [[Meeting_Notes_2014-08-20|2014-08-20]]
|
|
|-
| [[Meeting_Notes_2014-08-13|2014-08-13]]
|
|
|-
| [[Meeting_Notes_2014-08-06|2014-08-06]]
|
|
|-
| [[Meeting_Notes_2014-07-30|2014-07-30]]
|
|
|-
| [[Meeting_Notes_2014-07-23|2014-07-23]]
|
|
|-
| [[Meeting_Notes_2014-07-16|2014-07-16]]
|
|
|-
| [[Meeting_Notes_2014-07-09|2014-07-09]]
|
|
|-
| [[Meeting_Notes_2014-07-02|2014-07-02]]
|
| First meeting in our new space @ 4799 Shattuck!
|-
| 2014-06-25
|
| big moving day, no meeting notes
|-
| [[Meeting_Notes_2014-06-18|2014-06-18]]
|
|
|-
| [[Meeting_Notes_2014-06-11|2014-06-11]]
|
|
|-
| [[Meeting_Notes_2014-06-04|2014-06-04]]
|
|
|-
| [[Meeting Notes 2014-05-28|2014-05-28]]
|
|
|-
| [[Meeting Notes 2014-05-21|2014-05-21]]
|
|
|-
| [[Meeting Notes 2014-05-14|2014-05-14]]
|
|
|-
| [[Meeting Notes 2014-05-07|2014-05-07]]
|
|
|-
| [[Meeting Notes 2014-04-30|2014-04-30]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-23|2014-04-23]]
|
| Joint mtg w/ [http://counterculturelabs.org/ CCL]
|-
| [[Meeting Notes 2014-04-16|2014-04-16]]
|
|
|-
| [[Meeting Notes 2014-04-09|2014-04-09]]
|
|
|-
| [[Meeting Notes 2014-04-02|2014-04-02]]
|
| mostly reboot
|-
| [[Meeting Notes 2014-03-26|2014-03-26]]
|
|
|-
| [[Meeting Notes 2014-03-19|2014-03-19]]
|
|
|-
| [[Meeting Notes 2014-03-12|2014-03-12]]
|
|
|-
| [[Meeting Notes 2014-03-05|2014-03-05]]
|
| Special edition on reboot
|-
| [[Meeting Notes 2014-02-26|2014-02-26]]
|
|
|-
| [[Meeting Notes 2014-02-19|2014-02-19]]
|
|
|-
| [[Meeting Notes 2014-02-12|2014-02-12]]
|
|
|-
| [[Meeting Notes 2014-02-05|2014-02-05]]
|
|
|-
| [[Meeting Notes 2014-01-29|2014-01-29]]
|
|
|-
| [[Meeting Notes 2014-01-22|2014-01-22]]
|
|
|-
| [[Meeting Notes 2014-01-15|2014-01-15]]
|
|
|-
| [[Meeting Notes 2014-01-08|2014-01-08]]
|
|
|-
| [[Meeting Notes 2014-01-01|2014-01-01]]
|
|
|-
| [[Meeting Notes 2013-12-25|2013-12-25]]
|
|
|-
| [[Meeting Notes 2013-12-18|2013-12-18]]
|
|
|-
| [[Meeting Notes 2013-12-11|2013-12-11]]
|
|
|-
| [[Meeting Notes 2013-12-04|2013-12-04]]
|
|
|-
| [[Meeting Notes 2013-11-27|2013-11-27]]
|
|
|-
| [[Meeting Notes 2013-11-20|2013-11-20]]
|
|
|-
| [[Meeting Notes 2013-11-13|2013-11-13]]
|
|
|-
| [[Meeting Notes 2013-11-06|2013-11-06]]
|
|
|-
| [[Meeting Notes 2013-10-30|2013-10-30]]
|
|
|-
| [[Meeting Notes 2013-10-23|2013-10-23]]
|
|
|-
| [[Meeting Notes 2013-10-16|2013-10-16]]
|
|
|-
| [[Meeting Notes 2013-10-02|2013-10-02]]
|
|
|-
| [[Meeting Notes 2013-09-25|2013-09-25]]
|
|
|-
| [[Meeting Notes 2013-09-18|2013-09-18]]
|
|
|-
| [[Meeting Notes 2013-09-11|2013-09-11]]
|
|
|-
| [[Meeting Notes 2013-09-04|2013-09-04]]
|
|
|-
| [[Meeting Notes 2013-08-28|2013-08-28]]
|
|
|-
| [[Meeting Notes 2013-08-21|2013-08-21]]
|
|
|-
| [[Meeting Notes 2013-08-14|2013-08-14]]
|
|
|-
| [[Meeting Notes 2013-08-07|2013-08-07]]
|
|
|-
| [[Meeting Notes 2013-07-30|2013-07-30]]
|
|
|-
| [[Meeting Notes 2013-07-24|2013-07-24]]
|
|
|-
| [[Meeting Notes 2013-07-17|2013-07-17]]
|
|
|-
| [[Meeting Notes 2013-07-10|2013-07-10]]
|
|
|-
| [[Meeting Notes 2013-07-03|2013-07-03]]
|
|
|-
| [[Meeting Notes 2013-06-26|2013-06-26]]
|
|
|-
| [[Meeting Notes 2013-06-19|2013-06-19]]
|
|
|-
| [[Meeting Notes 2013-06-12|2013-06-12]]
|
|
|-
| [[Meeting Notes 2013-06-05|2013-06-05]]
|
|
|-
| [[Meeting Notes 2013-05-29|2013-05-29]]
|
|
|-
| [[Meeting Notes 2013-05-22|2013-05-22]]
|
|
|-
| [[Meeting Notes 2013-05-15|2013-05-15]]
|
|
|-
| [[Meeting Notes 2013-05-08|2013-05-08]]
|
|
|-
| [[Meeting Notes 2013-05-01|2013-05-01]]
|
|
|-
| [[Meeting Notes 2013-04-24|2013-04-24]]
|
|
|-
| [[Meeting Notes 2013-04-17|2013-04-17]]
|
|
|-
| [[Meeting Notes 2013-04-11|2013-04-11]]
|
|
|-
| [[Meeting Notes 2013-04-03|2013-04-03]]
|
|
|-
| [[Meeting Notes 2013-03-27|2013-03-27]]
|
|
|-
| 2013-03-20
|
| no notes?
|-
| [[Meeting Notes 2013-03-13|2013-03-13]]
|
|
|-
| [[Meeting Notes 2013-03-06|2013-03-06]]
|
|
|-
| [[Meeting Notes 2013-02-27|2013-02-27]]
|
|
|-
| [[Meeting Notes 2013-02-20|2013-02-20]]
|
|
|-
| [[Meeting Notes 2013-02-13|2013-02-13]]
|
|
|-
| [[Meeting Notes 2013-02-06|2013-02-06]]
|
|
|-
| [[Meeting Notes 2013-01-30|2013-01-30]]
|
|
|-
| [[Meeting Notes 2013-01-23|2013-01-23]]
|
|
|-
| [[Meeting Notes 2013-01-16|2013-01-16]]
|
|
|-
| [[Meeting Notes 2013-01-09|2013-01-09]]
|
|
|-
| [[Meeting Notes 2013-01-02|2013-01-02]]
|
|
|-
| [[Sudo room/12-26-2012 Meetup|2012-12-26]]
|
|
|-
| [[Sudo room/12-19-2012 Meetup|2012-12-19]]
|
|
|-
| [[Sudo room/12-12-2012 Meetup|2012-12-12]]
|
|
|-
| [[Sudo room/12-05-2012 Meetup|2012-12-05]]
|
|
|-
| [[Sudo room/11-28-2012 Meetup|2012-11-28]]
|
|
|-
| [[Sudo room/11-21-2012 Meetup|2012-11-21]]
|
|
|-
| [[Sudo room/11-14-2012 Meetup|2012-11-14]]
|
|
|-
| [[Sudo room/11-7-2012 Meetup|2012-11-07]]
|
|
|-
| [[Sudo room/10-31-2012 Meetup|2012-10-31]]
|
|
|-
| [[Sudo room/10-24-2012 Meetup|2012-10-24]]
|
|
|-
| [[Sudo room/10-17-2012 Meetup|2012-10-17]]
|
|
|-
| [[Sudo room/10-10-2012 Meetup|2012-10-10]]
|
|
|-
| [[Sudo room/10-03-2012 Meetup|2012-10-03]]
|
|
|-
| [[Sudo room/09-26-2012 Meetup|2012-09-26]]
|
|
|-
| [[Sudo room/09-19-2012 Meetup|2012-09-19]]
|
|
|-
| [[Sudo room/09-12-2012 Meetup|2012-09-12]]
|
|
|-
| [[Sudo room/09-05-2012 Meetup|2012-09-05]]
|
|
|-
| [[Sudo room/08-29-2012 Meetup|2012-08-29]]
|
|
|-
| [[Sudo room/08-22-2012 Meetup|2012-08-22]]
|
|
|-
| [[Sudo room/08-13-2012 Meetup|2012-08-13]]
|
|
|-
| [[Sudo room/08-08-2012 Meetup|2012-08-08]]
|
|
|-
| [[Sudo room/08-01-2012 Meetup|2012-08-01]]
|
|
|-
| [[Sudo room/07-25-2012 Meetup|2012-07-25]]
|
|
|-
| [[Sudo room/07-18-2012 Meetup|2012-07-18]]
|
|
|-
| [[Sudo room/07-11-2012 Meetup|2012-07-11]]
|
|
|-
| [[Sudo room/07-04-2012 Meetup|2012-07-04]]
|
|
|-
| [[Sudo room/06-27-2012 Meetup|2012-06-27]]
|
|
|-
| [[Sudo room/06-20-2012 Meetup|2012-06-20]]
|
|
|-
| [[Sudo room/06-13-2012 Meetup|2012-06-13]]
|
|
|-
| [[Sudo room/06-06-2012 Meetup|2012-06-06]]
|
|
|-
| [[Sudo room/05-30-2012 Meetup|2012-05-30]]
|
|
|-
| [[Sudo room/05-23-2012 Meetup|2012-05-23]]
|
|
|-
| [[Sudo room/05-16-2012 Meetup|2012-05-16]]
|
|
|-
| 2012-05-09
|
| no notes?
|-
| 2012-05-02
|
| no notes?
|-
| [[Sudo room/04-25-2012 Meetup|2012-04-25]]
|
|
|-
| 2012-04-18
|
| no notes?
|-
| 2012-04-11
|
| no notes?
|-
| 2012-04-04
|
| no notes?
|-
| 2012-03-28
|
| no notes?
|-
| 2012-03-21
|
| no notes?
|-
| 2012-03-14
|
| no notes?
|-
| 2012-03-07
|
| no notes?
|-
| 2012-02-29
|
| no notes?
|-
| [[Sudo room/02-22-2012 Meetup|2012-02-22]]
|
|
|-
| 2012-02-15
|
| no notes?
|-
| 2012-02-08
|
| no notes?
|-
| [[Sudo room/02-01-2011 Meetup|2012-02-01]]
|
|
|-
| [[Sudo room/01-25-2011 Meetup|2012-01-25]]
|
|
|-
| [[Sudo room/01-18-2011 Meetup|2012-01-18]]
|
|
|-
| [[Sudo room/01-11-2011 Meetup|2012-01-11]]
|
|
|-
| [[Sudo room/01-04-2011 Meetup|2012-01-04]]
|
|
|-
| [[Sudo room/12-28-2011 Meetup|2011-12-28]]
|
|
|-
| [[Sudo room/12-21-2011 Meetup|2011-12-21]]
|
|
|-
| [[Sudo room/12-14-2011 Meetup|2011-12-14]]
|
|
|-
| [[Sudo room/12-07-2011 Meetup|2011-12-07]]
|
|
|-
| [[Sudo room/First Wed Meetup|2011-11-30]]
|
| @ Cafe Mediterraneum
|-
| [[Sudo room/Initial Meeting| Initial Meeting]]
|
| 2011-11-18, 12pm @ Actual Cafe
|}

[[Category:SudoRoom Organization]][[Category:Meetings]]

Mesh/Flashing extender nodes

2016-05-15T04:29:59Z

Redconfetti: /* Serial Communications Program */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-15T04:29:16Z

Redconfetti: /* Serial Communications Program */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-15T04:27:29Z

Redconfetti: /* Order a USB to Serial Converter */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-15T04:26:47Z

Redconfetti: /* Order a USB to Serial Converter */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, a device using a CP210X chip can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

IRC

2016-05-14T21:12:17Z

Redconfetti: /* Configure */

Internet Relay Chat (IRC) is an instant messaging service that has been used on the internet since the early 1990s. IRC is made possible by the [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat Protocol (IRCP)], an application layer protocol. The chat process works on a client/server networking model. IRC clients are computer programs that a user can install on their system. These clients communicate with chat servers to transfer messages to other clients. IRC is mainly designed for group communication in discussion forums, called channels, but also allows one-on-one communication via private messages as well as chat and data transfer, including file sharing.

Many [https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_protocols other instant messaging services] exist, however many services are proprietary and/or rely on a centralized platform. This does not appeal to organizations that wish to establish a channel of communication that can be adopted by users without fear of unwanted regulations by the service/platform provider. Although open source protocols such as [https://en.wikipedia.org/wiki/XMPP XMPP (formerly Jabber)] exist, IRC continues to be used because it is lightweight and stable.

IRC consists of channels. Each channel is like a chat room, and is represented by a name that begins with '#' followed by a string that represents the primary topic of the channel. Examples: #html, #css, #javascript, #go-lang.

== Recommended Clients ==

There are many various IRC clients available for many platforms.

=== Graphical Clients ===

* Cross-platform
** [https://www.pidgin.im/download/ Pidgin]
* Mac OS X
** [https://adium.im/ Adium]

=== Command Line Interface Clients ===

These clients are intended to be used from the command line interface (CLI), also known as the "terminal".

* [https://irssi.org/ irssi]

== Basics ==

For those that are new to IRC, itâ€™s a good idea to become familiar with the [http://www.ircbeginner.com/ircinfo/ircc-commands.html common commands] that IRC programs support. Here are a few:

{| class="wikitable"
! Command !! Example !! Description
|-
| /join #channel_name || /join #sudoroom ||Join a channel
|-
| /me <action> || /me waves hello || Announces some action
|-
| /msg <nickname> <message> || /msg juul Hey! I need some help || Send a direct message to another user
|-
| /ignore <nickname> || /ignore annoyingperson || Block someone that is harassing you
|-
|}

Although the above commands are likely to be supported by all IRC client programs, some only apply to specific clients. The following are supported by [https://irssi.org/ irssi]:

{| class="wikitable"
! Command !! Example !! Description
|-
| /help || /help || View documentation on supported commands
|-
| /help <command> || /help connect || View documentation on a specific supported command
|-
| /connect <server address> <port> || /connect irc.freenode.net 8001 || Connect to an IRC server
|-
| /set nick <nick> || /set nick someGuy2015 || Register your nickname with the IRC server/network
|-
| /set real_name <real name> || /set nick Bill Murray || Register your real name within the IRC server/network
|-
| /quit || /quit || Quits IRC program
|-
| /exit || /exit || Quits IRC program
|-
|}

See [https://irssi.org/documentation/ IRSSI Documentation] for more commands.

== FreeNode ==

Many programming/hacking communities establish a channel on the [https://en.wikipedia.org/wiki/Freenode FreeNode IRC network] to facilitate discussions and provide support to members of their community.

=== Registering with FreeNode ===

The FreeNode IRC network allows you to register your nickname and associate it with your email address. This is done by using the following commands:

/msg nickserv REGISTER <password> <email>

You should receive a message informing you that you need to check your email account and obtain instructions to verify yourself.

To make sure that your email address isnâ€™t revealed to other users, use the following command to ensure that it is hidden.

/msg NickServ SET HIDEMAIL ON

You can verify your information with the NickServ by using:

/msg nickserv info

== Persistent CLI Client ==

This section is a guide to setting up a command line based IRC client on a persistently running machine so that it stays connected within a channel even when you are not connected to the machine via SSH. This results in the ability to reconnect and view the messages in the channel that occurred even when you were not connected.

These instructions assume you are using an Ubuntu machine, and will be using the [https://irssi.org/ irssi] client.

=== Client Machine ===

You setup a system at home and configure your home network device(s) to make that machine available via the internet, or alternatively gain shell access to a server on the internet. There are services that provide free or paid shell access, with features and support for IRC that varies. Some of these services even provide support for [https://en.wikipedia.org/wiki/IRC_bot IRC bots]. Alternatively you can pay for a [https://en.wikipedia.org/wiki/Virtual_private_server Virtual Private Server (VPS)] for as low as $5 a month through services such as [digitalocean.com DigitalOcean], thus providing you with an entire UNIX-like server environment that you can use as you wish.

=== Install Client ===

Install the irssi client using the following command:

apt-get install irssi

After itâ€™s done installing, simply run the program

irssi

=== Configure ===

There is a configuration file in ~/.irssi/config that you can inspect, but you can use commands from within the program to configure IRSSI to automatically perform when you first open the program.

The following commands will configure IRSSI to connect to the Freenode network with an SSL connection, with automatic joining of the #sudoroom channel.

/network add Freenode
/server add -auto -ssl -ssl_verify -ssl_capath /etc/ssl/certs -network Freenode irc.freenode.net 7000
/channel add -auto #sudoroom Freenode
/save

After youâ€™ve successfully registered your FreeNode nick name, you can run this command to configure IRSSI to login automatically after connecting to FreeNode.

/network add -autosendcmd "/msg nickserv identify <password> ;wait 2000" Freenode

=== Windows ===

irssi support separate "windows" for the different channels you are connected to, or for the different people you are chatting with. If for some reason you do not see information on the screen for a command youâ€™ve run, it may be displayed in another window.

An Ubuntu terminal can use the ALT key combined with a number key (e.g. ALT+1, ALT+2, ALT+3, etc) to switch between the different displays in IRSSI. This will not work via SSH however, so you will need to use the /window command instead.

/WINDOW NEW - Create new split window
/WINDOW NEW HIDE - Create new hidden window
/WINDOW CLOSE - Close split or hidden window

/WINDOW HIDE [<number>|<name>] - Make the split window hidden window
/WINDOW SHOW <number>|<name> - Make the hidden window a split window

/WINDOW SHRINK [<lines>] - Shrink the split window
/WINDOW GROW [<lines>] - Grow the split window
/WINDOW BALANCE - Balance the sizes of all split windows

=== Managing Process ===

Use 'screen' command on the VPS to

CTRL-A, then D - disconnect from the screen instance, and then use `screen -r`.

tmux (terminal multiplexer) is another option

See [http://carina.org.uk/screenirssi.shtml How to use screen and irssi] and [https://michael.lustfield.net/linux/irssi-using-screen-and-ssh IRSSI Using Screen and SSH]

Mesh

2016-05-14T21:10:57Z

Redconfetti: /* Join Us */ added link to irc intro

[[File:SudoMesh Node.png|frameless|right|300px]]

You can read about our progress on our [[Mesh/Blog|blog]]. We're in an alpha testing phase, and our monitoring results can be seen on [https://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh smokeping] or [https://monitor.sudomesh.org/cacti/graph.php?action=view&local_graph_id=217&rra_id=all cacti].

Check out the Join Us section below for opportunities to help out!

([[User:Maxb|Maxb]] December 22nd 2015)

----

'''We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.'''

People's Open Network is a [http://en.wikipedia.org/wiki/Mesh_networking mesh network] based out of Oakland, California.

Imagine if the wifi router in your home connected to the wifi routers in your neighbourâ€™s homes and they again connected to their neighbours to form a huge free wireless network spanning the city! That's exactly what a mesh network is, or at least what it can be. Roads and telephone poles are owned government or private interests and laying down cable is expensive but by using wireless signals that hop from building to building we can create a community owned and operated free-as-in-freedom alternative to corporate Internet Service Providers! Community wireless mesh networks are growing around the world, creating local 'internets' that support Net Neutrality and community control of critical infrastructure.

sudo mesh is a non-profit organization consisting of a group of unpaid volunteers who are building People's Open Network. Our mission in building the network is to connect our neighbors, support local businesses, and enable community collaboration and cultural production. In the event of disaster or censorship, a mesh network can be a resilient means of communication and sharing of information.

We are spending a lot of time developing [https://github.com/sudomesh/ software] to make it cheap and easy for anyone to be part of People's Open Network, regardless of technical skill.

[[File:Mesh_Oakland_High_Res.png|225px|right]]

= Join Us =

* Join the [http://lists.sudoroom.org/listinfo/mesh email list]
* Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook].
* Learn more at our general meetings, which are the last Tuesdays of every month at [[Getting_there|sudo room]] at 7:30 pm. We have focus groups and we collaborate on different parts of the project - from design to software development, documentation to community outreach and of course, community outreach and climbing rooftops to mount nodes!
* We have '''weekly meetings'' on Tuesdays and '''weekly hacknights''' on Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]], but at these events we do not spend time introducing new people to the project. If you do not feel ready to jump right in and start contributing, please show up for our general meetings (mentioned above) where we specifically take time to intro new volunteers and answer questions :D
* Chat with us on [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net] (see also [[IRC | IRC Intro]])
* We generally collaborate on [https://pad.riseup.net/p/sudomesh meeting notes] at each meeting. Look at our archive of past [[Mesh/Minutes|meeting minutes]]!
* Contribute to the network by installing a mesh node at your location using our handy [https://sudoroom.org/wiki/Mesh/WalkThrough Mesh Node Setup Walkthrough]. This is especially helpful for those that are within range of an existing node (seen as a wireless SSID named "peoplesopen.net").

= How to Help =

We need more people on the network to improve the quality of the service. When you setup a node, you improve the service for everybody on the network and give more access to your community. We encourage participants to ask their communities to join their networks and create distributed services for them. We have a [[Mesh/User_Guide|user guide]] to help you get on the network!

*Check out our [[Mesh/ToDos|action items]]
*Support us with a small weekly donation on [https://www.gittip.com/sudomesh/ gittip], here's [[Mesh/Purchases|how we spend it]].
*Send bitcoins to our wallet address: {{bitcoin wallet}}
*Check out our [[Mesh/Wishlist|wishlist]], we have requests!
*Come to our meetings in Oakland! (listed above)
*Improve our documentation
*Talk to your community about joining the mesh

== Developers ==

We need hardware and software engineers to help us with our code. We have an overview of [[Mesh/Technical_Overview|technical documentation]] that will be helpful in understanding the network.

If you want to immediately help, check out [https://github.com/sudomesh our code] or [https://github.com/sudomesh/sudowrt-firmware/milestones look at our remaining issues for upcoming milestones].

Here are some of the projects that need attention:

* [[Mesh/Firmware|Firmware]] - The sudowrt firmware
* [https://github.com/sudomesh/sudowrt-web-ui sudowrt-web-ui] - The new and improved web admin UI for sudowrt nodes
* [https://github.com/sudomesh/ubus-https-forwarder ubus-https-forwarder] - Allow management of extender nodes from home node web UI
* [https://github.com/sudomesh/service-browser The Service Browser] - Web UI for browsing mesh services
* [[Mesh/Distributed Services|Mesh Services]] - Which services should we provide?

== Designers ==

We need artists and designers to make things look nice! We have [[Mesh/Design|design schemes]] we already use, but we're always looking to improve it. We need to improve our presentation content and [[Mesh/Diagrams|diagrams]] too! We've been focused on these areas:

* [[Mesh/Presentation|Presentation]]
* [[Mesh/Diagrams|Diagrams]]
* Tutorials and Videos

= Frequently Asked Questions (FAQs)=

* [[Mesh/Challenges|Challenges]] - What sort of challenges and problems do we face?
* [[Mesh/Decisions|Decisions]] - What decisions have we made, and why?
* [[Mesh/Funding|Funding]] - How the heck do we fund this thing?
* [[Mesh/Legal|Legal]] - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
* [[Mesh/Hosting|Hosting]] - How are we hosting and what does it cost?
* [[Mesh/Backup|Backup]] - How do we handle backups?
* [[Mesh/Server security|Server security]] - How do we ensure server security?

= Logistics =

* [[Mesh/Checkouts|Checkouts]] - Who took what gear home.
* [[Mesh/Inventory|Inventory]] - Continually-updated inventory of our hardware and gear.
* [[Mesh/Marketing|Marketing]] - Inspiration and links to marketing materials in progress.
* [[Mesh/Naming|Naming]] - What do we call ourselves? A lineage of bikeshedding.
* [[Mesh/Purchases|Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.
* [[Mesh/Taxes|Taxes]] - Filed taxes for the sudo mesh non-profit

= Research =

We need help improving our documentation about the area and other legalities.

* [[Mesh/Legal|Legal]] - we are becoming a 501(c)3 and there are other legalities of wireless networks
* [[Mesh/Interviews with other meshers|Interviews]] - we interviewed other experienced meshers
* [[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts.
* [[Mesh/Oakland|Oakland]] - information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
* [[Mesh/Other muni networking projects|Municipal projects]] - examples of progressive uses of municipal networks.
* [[Mesh/Decentralized FM/AM radio|Decentralized FM/AM radio]] - Bit of research on adding legal FM/AM transmitters to nodes.

= Other Firmware and Networks =

There are [[Mesh/Other mesh projects|other meshes]] around the world that have inspired us to make our own network! They use software from these projects:

* [[Mesh/Freifunk]] (germany) - the creators of batman-adv (routing protocol we use) and one of the longest-running mesh networks in the world.
* [[Mesh/Commotion]] - a very well-documented project from the Open Technology Institute creating a simple-to-deploy mesh firmware and setup for small community meshes around the world.
* [[Mesh/San Francisco]] Mesh projects in San Francisco

= Web Resources =

* [http://510pen.org 510pen] - East Bay community wireless mesh network spawned in 2009 by [[User:mfb|Mark Burdett]]
* [http://wiki.tidepools.com Tidepools] - [[User:tunabananas|Jenny Ryan]] designed local use cases for a community mobile mapping application built to run on mesh networks.
* [https://wiki.projectmeshnet.org/Main_Page Project Meshnet] - Extensive wiki on the /r/darknet project, including extensive list of [https://wiki.projectmeshnet.org/Projects projects coordinating with them].
* [http://en.wikipedia.org/wiki/Long-range_Wi-Fi#Notable_links Long Range Wifi] - Info on the longest-range wifi connections ever made.
* [https://github.com/adafruit/Adafruit-WebIDE Adafruit's Web IDE built for Raspberry Pi] but probably good for editing code on any device and ensuring it is managed with a code repo. By default it uses [https://bitbucket.org bitbucket.org] but it could probably be configured for Github.

= All Sudo Mesh Wiki Pages =

<center>{{Mesh nav}}</center>

''Please note that all contributions to Sudo Room may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Sudo Room:Copyrights for details). Do not submit copyrighted work without permission!''

[[Category:Projects]][[Category:Mesh]]

IRC

2016-05-14T21:06:33Z

Redconfetti:

Internet Relay Chat (IRC) is an instant messaging service that has been used on the internet since the early 1990s. IRC is made possible by the [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat Protocol (IRCP)], an application layer protocol. The chat process works on a client/server networking model. IRC clients are computer programs that a user can install on their system. These clients communicate with chat servers to transfer messages to other clients. IRC is mainly designed for group communication in discussion forums, called channels, but also allows one-on-one communication via private messages as well as chat and data transfer, including file sharing.

Many [https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_protocols other instant messaging services] exist, however many services are proprietary and/or rely on a centralized platform. This does not appeal to organizations that wish to establish a channel of communication that can be adopted by users without fear of unwanted regulations by the service/platform provider. Although open source protocols such as [https://en.wikipedia.org/wiki/XMPP XMPP (formerly Jabber)] exist, IRC continues to be used because it is lightweight and stable.

IRC consists of channels. Each channel is like a chat room, and is represented by a name that begins with '#' followed by a string that represents the primary topic of the channel. Examples: #html, #css, #javascript, #go-lang.

== Recommended Clients ==

There are many various IRC clients available for many platforms.

=== Graphical Clients ===

* Cross-platform
** [https://www.pidgin.im/download/ Pidgin]
* Mac OS X
** [https://adium.im/ Adium]

=== Command Line Interface Clients ===

These clients are intended to be used from the command line interface (CLI), also known as the "terminal".

* [https://irssi.org/ irssi]

== Basics ==

For those that are new to IRC, itâ€™s a good idea to become familiar with the [http://www.ircbeginner.com/ircinfo/ircc-commands.html common commands] that IRC programs support. Here are a few:

{| class="wikitable"
! Command !! Example !! Description
|-
| /join #channel_name || /join #sudoroom ||Join a channel
|-
| /me <action> || /me waves hello || Announces some action
|-
| /msg <nickname> <message> || /msg juul Hey! I need some help || Send a direct message to another user
|-
| /ignore <nickname> || /ignore annoyingperson || Block someone that is harassing you
|-
|}

Although the above commands are likely to be supported by all IRC client programs, some only apply to specific clients. The following are supported by [https://irssi.org/ irssi]:

{| class="wikitable"
! Command !! Example !! Description
|-
| /help || /help || View documentation on supported commands
|-
| /help <command> || /help connect || View documentation on a specific supported command
|-
| /connect <server address> <port> || /connect irc.freenode.net 8001 || Connect to an IRC server
|-
| /set nick <nick> || /set nick someGuy2015 || Register your nickname with the IRC server/network
|-
| /set real_name <real name> || /set nick Bill Murray || Register your real name within the IRC server/network
|-
| /quit || /quit || Quits IRC program
|-
| /exit || /exit || Quits IRC program
|-
|}

See [https://irssi.org/documentation/ IRSSI Documentation] for more commands.

== FreeNode ==

Many programming/hacking communities establish a channel on the [https://en.wikipedia.org/wiki/Freenode FreeNode IRC network] to facilitate discussions and provide support to members of their community.

=== Registering with FreeNode ===

The FreeNode IRC network allows you to register your nickname and associate it with your email address. This is done by using the following commands:

/msg nickserv REGISTER <password> <email>

You should receive a message informing you that you need to check your email account and obtain instructions to verify yourself.

To make sure that your email address isnâ€™t revealed to other users, use the following command to ensure that it is hidden.

/msg NickServ SET HIDEMAIL ON

You can verify your information with the NickServ by using:

/msg nickserv info

== Persistent CLI Client ==

This section is a guide to setting up a command line based IRC client on a persistently running machine so that it stays connected within a channel even when you are not connected to the machine via SSH. This results in the ability to reconnect and view the messages in the channel that occurred even when you were not connected.

These instructions assume you are using an Ubuntu machine, and will be using the [https://irssi.org/ irssi] client.

=== Client Machine ===

You setup a system at home and configure your home network device(s) to make that machine available via the internet, or alternatively gain shell access to a server on the internet. There are services that provide free or paid shell access, with features and support for IRC that varies. Some of these services even provide support for [https://en.wikipedia.org/wiki/IRC_bot IRC bots]. Alternatively you can pay for a [https://en.wikipedia.org/wiki/Virtual_private_server Virtual Private Server (VPS)] for as low as $5 a month through services such as [digitalocean.com DigitalOcean], thus providing you with an entire UNIX-like server environment that you can use as you wish.

=== Install Client ===

Install the irssi client using the following command:

apt-get install irssi

After itâ€™s done installing, simply run the program

irssi

=== Configure ===

There is a configuration file in ~/.irssi/config that you can inspect, but you can use commands from within the program to configure IRSSI to automatically perform when you first open the program.

The following commands will configure IRSSI to connect to the Freenode network with an SSL connection, with automatic joining of the #sudoroom channel.

/network add Freenode
/server add -auto -ssl -ssl_verify -ssl_capath /etc/ssl/certs -network Freenode irc.freenode.net 7000
/channel add -auto #sudo Freenode
/save

After youâ€™ve successfully registered your FreeNode nick name, you can run this command to configure IRSSI to login automatically after connecting to FreeNode.

/network add -autosendcmd "/msg nickserv identify <password> ;wait 2000" Freenode

=== Windows ===

irssi support separate "windows" for the different channels you are connected to, or for the different people you are chatting with. If for some reason you do not see information on the screen for a command youâ€™ve run, it may be displayed in another window.

An Ubuntu terminal can use the ALT key combined with a number key (e.g. ALT+1, ALT+2, ALT+3, etc) to switch between the different displays in IRSSI. This will not work via SSH however, so you will need to use the /window command instead.

/WINDOW NEW - Create new split window
/WINDOW NEW HIDE - Create new hidden window
/WINDOW CLOSE - Close split or hidden window

/WINDOW HIDE [<number>|<name>] - Make the split window hidden window
/WINDOW SHOW <number>|<name> - Make the hidden window a split window

/WINDOW SHRINK [<lines>] - Shrink the split window
/WINDOW GROW [<lines>] - Grow the split window
/WINDOW BALANCE - Balance the sizes of all split windows

=== Managing Process ===

Use 'screen' command on the VPS to

CTRL-A, then D - disconnect from the screen instance, and then use `screen -r`.

tmux (terminal multiplexer) is another option

See [http://carina.org.uk/screenirssi.shtml How to use screen and irssi] and [https://michael.lustfield.net/linux/irssi-using-screen-and-ssh IRSSI Using Screen and SSH]

IRC

2016-05-14T20:36:06Z

Redconfetti: creating IRC guide page

Internet Relay Chat (IRC) is an instant messaging service that has been used on the internet since the early 1990s. IRC is made possible by the [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat Protocol (IRCP)], an application layer protocol. The chat process works on a client/server networking model. IRC clients are computer programs that a user can install on their system. These clients communicate with chat servers to transfer messages to other clients. IRC is mainly designed for group communication in discussion forums, called channels, but also allows one-on-one communication via private messages as well as chat and data transfer, including file sharing.

Many [https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_protocols other instant messaging services] exist, however many services are proprietary and/or rely on a centralized platform. This does not appeal to organizations that wish to establish a channel of communication that can be adopted by users without fear of unwanted regulations by the service/platform provider. Although open source protocols such as [https://en.wikipedia.org/wiki/XMPP XMPP (formerly Jabber)] exist, IRC continues to be used because it is lightweight and stable.

== Recommended Clients ==

There are many various IRC clients available for many platforms.

=== Graphical Clients ===

* Cross-platform
** [https://www.pidgin.im/download/ Pidgin]
* Mac OS X
** [https://adium.im/ Adium]

=== Command Line Interface Clients ===

These clients are intended to be used from the command line interface (CLI), also known as the "terminal".

* [https://irssi.org/ irssi]

== Basics ==

IRC consists of channels. Each channel is like a chat room, and is represented by a name that begins with '#' followed by a string that represents the primary topic of the channel. Examples: #html, #css, #javascript, #go-lang.

== FreeNode ==

Many programming/hacking communities establish a channel on the [https://en.wikipedia.org/wiki/Freenode FreeNode IRC network] to facilitate discussions and provide support to members of their community.

== Persistent CLI Client ==

This section is a guide to setting up a command line based IRC client on a persistently running machine so that it stays connected within a channel even when you are not connected to the machine via SSH. This results in the ability to reconnect and view the messages in the channel that occurred even when you were not connected.

These instructions assume you are using an Ubuntu machine, and will be using the [https://irssi.org/ irssi] client.

=== Client Machine ===

You setup a system at home and configure your home network device(s) to make that machine available via the internet, or alternatively gain shell access to a server on the internet. There are services that provide free or paid shell access, with features and support for IRC that varies. Some of these services even provide support for [https://en.wikipedia.org/wiki/IRC_bot IRC bots]. Alternatively you can pay for a [https://en.wikipedia.org/wiki/Virtual_private_server Virtual Private Server (VPS)] for as low as $5 a month through services such as [digitalocean.com DigitalOcean], thus providing you with an entire UNIX-like server environment that you can use as you wish.

=== Install Client ===

Install the irssi client using the following command:

apt-get install irssi

After itâ€™s done installing, simply run the program

irssi

=== Getting Started ===

Upon opening the program for the first time IRSSI may connect to a default IRC network. There is a configuration file in ~/.irssi/config that you can inspect, but you can use commands from within the program to configure IRSSI to automatically perform when you first open the program. This includes connecting to Freenode, authenticating using your registered nick name, and joining a default channel.

You can use these commands to get started immediately:

Set your nick name and real name

/set nick <nick>
/set real_name <Real Name>
Connecting to FreeNode

/connect irc.freenode.net 8001
Join Channel

/join #sudoroom

=== Windows ===

irssi support separate "windows" for the different channels you are connected to, or for the different people you are chatting with. If for some reason you do not see information on the screen for a command youâ€™ve run, it may be displayed in another window.

An Ubuntu terminal can use the ALT key combined with a number key (e.g. ALT+1, ALT+2, ALT+3, etc) to switch between the different displays in IRSSI. This will not work via SSH however, so you will need to use the /window command instead.

/WINDOW NEW - Create new split window
/WINDOW NEW HIDE - Create new hidden window
/WINDOW CLOSE - Close split or hidden window

/WINDOW HIDE [<number>|<name>] - Make the split window hidden window
/WINDOW SHOW <number>|<name> - Make the hidden window a split window

/WINDOW SHRINK [<lines>] - Shrink the split window
/WINDOW GROW [<lines>] - Grow the split window
/WINDOW BALANCE - Balance the sizes of all split windows

=== Managing Process ===

Use 'screen' command on the VPS to

CTRL-A, then D - disconnect from the screen instance, and then use `screen -r`.

tmux (terminal multiplexer) is another option

See [http://carina.org.uk/screenirssi.shtml How to use screen and irssi] and [https://michael.lustfield.net/linux/irssi-using-screen-and-ssh IRSSI Using Screen and SSH]

Mesh/Firmware/Web Admin Development

2016-05-11T04:34:58Z

Redconfetti: adding resource links

This used to be a page on our old Luci-based web admin UI, but that UI is being deprecated.

We are now writing [https://github.com/sudomesh/sudowrt-web-ui a new UI] that uses ubus via uhttpd-mod-ubus instead of Luci.

ubus is the system bus for OpenWRT, similar to D-Bus but very light-weight. Using ubus it is possible to configure all OpenWRT config files in the /etc/config directory, and even run scripts on the router. uhttpd-mod-ubus allows access to ubus over http with access restricted by access control lists. More info on this [http://wiki.openwrt.org/doc/techref/ubus#access_to_ubus_over_http here].

The new UI includes a simulator (written in node.js) that pretends to be a sudowrt router, which makes it easy for developers to test their client-side code without having to always have a sudowrt router with them.

== Resource Links ==

* [https://wiki.openwrt.org/doc/techref/ubus#access_to_ubus_over_http OpenWRT.org - Access to ubus over HTTP]
* [https://wiki.openwrt.org/doc/techref/luci2 Luci2 Web Interface Documentation]
* [https://en.wikipedia.org/wiki/XMLHttpRequest Wikipedia - XMLHttpRequest]
* [https://github.com/sudomesh/sudowrt-firmware Github - SudoWRT-Firmware]

Mesh/Flashing extender nodes

2016-05-08T08:13:49Z

Redconfetti: /* Drop into U-Boot Command Prompt */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-08T08:12:24Z

Redconfetti: /* NSM5 Official Firmware */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-08T08:10:56Z

Redconfetti: /* Nanostation M5 */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== NSM5 Official Firmware =====

Press a key to during the boot process to make U-Boot drop into the command line.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-08T08:08:56Z

Redconfetti:

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== NSM5 Official Firmware =====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

Press a key to during the boot process to make U-Boot drop into the command line.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-08T07:56:31Z

Redconfetti: /* Extender Detection */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Nanostation M2 ==

=== Firmware check failure ===

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

== Nanostation M5 ==

=== Firmware check failure ===

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== NSM5 Official Firmware ====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Picostation M2HP ==

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

Mesh/Flashing extender nodes

2016-05-08T07:55:17Z

Redconfetti:

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Nanostation M2 ==

=== Firmware check failure ===

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

== Nanostation M5 ==

=== Firmware check failure ===

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== NSM5 Official Firmware ====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Picostation M2HP ==

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.

There should be a debug message in the log from notdhcpserver concerning the extender node.

Mesh/Flashing extender nodes

2016-05-08T06:37:00Z

Redconfetti: /* Nanostation M2 */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Nanostation M2 ==

=== Firmware check failure ===

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

== Nanostation M5 ==

=== Firmware check failure ===

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== NSM5 Official Firmware ====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Picostation M2HP ==

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.

Mesh/Flashing extender nodes

2016-05-08T06:14:06Z

Redconfetti: adding notes concerning Nanostation M2

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Nanostation M2 ==

=== Firmware check failure ===

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

== Nanostation M5 ==

=== Firmware check failure ===

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== NSM5 Official Firmware ====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Picostation M2HP ==

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.

Mesh/Flashing extender nodes

2016-05-08T05:52:37Z

Redconfetti: adding link to article involving Picostation M2HP

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Nanostation M5 ==

=== Firmware check failure ===

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== NSM5 Official Firmware ====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding `-D /dev/ttyUSB0`, and specify that it should skip initialization by adding `-o`.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including `-b 115200 -8`.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Picostation M2HP ==

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.

Mesh/Flashing extender nodes

2016-05-08T04:57:24Z

Redconfetti: /* Flash the Extender Node */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

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

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Nanostation M5 ==

=== Firmware check failure ===

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== NSM5 Official Firmware ====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding `-D /dev/ttyUSB0`, and specify that it should skip initialization by adding `-o`.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including `-b 115200 -8`.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-08T04:42:14Z

Redconfetti: /* Running TFTPd */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

== Nanostation M5 ==

=== Firmware check failure ===

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== NSM5 Official Firmware ====

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]
* [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding `-D /dev/ttyUSB0`, and specify that it should skip initialization by adding `-o`.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including `-b 115200 -8`.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-08T04:32:14Z

Redconfetti: /* Firmware check failure */ minimizing serial output with firmware check failure, replacing official firmware flash with only links

Mesh/Flashing extender nodes

2016-05-08T04:25:15Z

Redconfetti: adding instructions for using serial to run tftp for successful flash of sudowrt

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Model No. !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M5 || NSM5 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016]
|-
| Ubiquiti Nanostation M2 || NSM2 || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-om2p-squashfs-factory.bin firmware image]
|-
| Ubiquiti Picostation 2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] ||
|-
| Ubiquiti Nanobeam M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] ||
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] ||
|}

== Flash the Extender Node ==

* Configure your wired internet settings to use Manual IPv4 settings with IP: 192.168.1.10, subnet: 255.255.255.0, gateway: 0.0.0.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your antenna on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

== Nanostation M5 ==

=== Firmware check failure ===

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

==== TFTP Serial Output ====

When booting with the reset button held down on a Ubiquity NSM5, the following output is displayed.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

==== TFTP with Official Firmware ====

You can download the official firmware image from Ubiquity - [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4] - [http://dl.ubnt.com/firmwares/XW-fw/v5.6.3/XW.v5.6.3.28591.151130.1735.bin airOS for XW board firmware v5.6.3]

Then you can start the TFTP server

ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |

From your machine, configured as 192.168.1.10, use TFTP to upload the official image

$ tftp 192.168.1.20
tftp> put XW.v5.6.4.28924.160331.1238.bin
Transfer timed out.

The file uploads, and as expected the image does not result in a firmware check error.

Receiving file from 192.168.1.10:56564
Received 7296551 bytes
Firmware Version: XW.ar934x.v5.6.4.28924.160331.1238

This produces no change in the boot output. I try the v5.6.3 firmware.

Receiving file from 192.168.1.10:36771
Received 7293587 bytes
Firmware Version: XW.ar934x.v5.6.3.28591.151130.1735

The TFTP client times out, but I wait for the firmware message on the serial output to change. Nothing happens. Reboot the device. No changes in the image detected.

## Booting image at 9f050000 ...
Image Name: MIPS Ubiquiti Linux-2.6.32.68
Created: 2016-03-31 9:39:16 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 955842 Bytes = 933.4 kB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

Booting Atheros AR934x

=== USB to Serial Connection ===

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface. This may be necessary to manually load firmware onto the device if the web interface or TFTP methods of flashing the firmware become unavailable due to [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html manufacturers disabling these methods] of firmware flashing.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding `-D /dev/ttyUSB0`, and specify that it should skip initialization by adding `-o`.

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including `-b 115200 -8`.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
Hit any key to stop autoboot: 0
ar7240>

This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.

==== Running TFTPd ====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however.

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

Mesh/Flashing extender nodes

2016-05-07T06:47:42Z

Redconfetti: /* TFTP with Official Firmware */

Mesh/Flashing extender nodes

2016-05-07T06:37:34Z

Redconfetti: /* TFTP Serial Output */

Mesh/Flashing extender nodes

2016-05-07T05:38:45Z

Redconfetti: /* Connecting to Serial */

Mesh/Flashing extender nodes

2016-05-07T05:38:00Z

Redconfetti: /* Connecting to Serial */

File:Ubiquity-NSM5-serial-connectors.jpg

2016-05-07T05:37:03Z

Redconfetti: Ubiquiti Nanostation NSM5 - Serial pins with connections

Ubiquiti Nanostation NSM5 - Serial pins with connections

File:CP2102-usb-to-serial-converter.jpg

2016-05-07T05:33:38Z

Redconfetti: KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC

KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC

Mesh/Flashing extender nodes

2016-05-07T05:27:26Z

Redconfetti: /* Nanostation M5 */

Mesh/Flashing extender nodes

2016-05-07T05:26:27Z

Redconfetti: /* TFTP Serial Output */

Mesh/Flashing extender nodes

2016-05-07T05:21:31Z

Redconfetti: /* Interupting Boot */

Mesh/Flashing extender nodes

2016-05-07T05:00:49Z

Redconfetti: /* Interupting Boot */

Mesh/Flashing extender nodes

2016-05-07T05:00:10Z

Redconfetti: /* Interupting Boot */

Mesh/Flashing extender nodes

2016-05-07T04:37:54Z

Redconfetti: /* Interupting Boot */

Mesh/Flashing extender nodes

2016-05-07T04:08:01Z

Redconfetti: /* Serial Communications Program */