Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added new Common and Advanced Hardware Setups modules to CCK #222

Merged
merged 5 commits into from
Aug 21, 2014
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
<ul class="submenu">
<li {% if page.url contains '/docs/cck/installing-configuring/install-ubiquiti-router' %} class="active" {% endif %}><a href="{% if page.lang != 'en' %}/{{ page.lang }}{% endif %}/docs/cck/installing-configuring/install-ubiquiti-router">Install on a Ubiquiti Router</a></li>
<li {% if page.url contains '/docs/cck/installing-configuring/configure-commotion' %} class="active" {% endif %}><a href="{% if page.lang != 'en' %}/{{ page.lang }}{% endif %}/docs/cck/installing-configuring/configure-commotion">Configure Commotion</a></li>
<li {% if page.url contains '/docs/cck/installing-configuring/common-configuration' %} class="active" {% endif %}><a href="{% if page.lang != 'en' %}/{{ page.lang }}{% endif %}/docs/cck/installing-configuring/common-configuration">Common Configurations</a></li>
<li {% if page.url contains '/docs/cck/installing-configuring/common-hardware-setups' %} class="active" {% endif %}><a href="{% if page.lang != 'en' %}/{{ page.lang }}{% endif %}/docs/cck/installing-configuring/common-hardware-setups">Common Hardware Setups</a></li>
<li {% if page.url contains '/docs/cck/installing-configuring/advanced-hardware-setups' %} class="active" {% endif %}><a href="{% if page.lang != 'en' %}/{{ page.lang }}{% endif %}/docs/cck/installing-configuring/advanced-hardware-setups">Advanced Hardware Setups</a></li>
<li {% if page.url contains '/docs/cck/installing-configuring/troubleshoot-your-wireless-node' %} class="active" {% endif %}><a href="{% if page.lang != 'en' %}/{{ page.lang }}{% endif %}/docs/cck/installing-configuring/troubleshoot-your-wireless-node">Troubleshoot Your Wireless Node</a></li>
<li {% if page.url contains '/docs/cck/installing-configuring/install-and-recover-tftp' %} class="active" {% endif %}><a href="{% if page.lang != 'en' %}/{{ page.lang }}{% endif %}/docs/cck/installing-configuring/install-and-recover-tftp">Install and Recover with TFTP</a></li>
</ul>
5 changes: 3 additions & 2 deletions commotionwireless.net/docs/cck/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,9 @@ lang: en
<ul>
<li><a href="/docs/cck/installing-configuring/install-ubiquiti-router">Install on a Ubiquiti Router</a>: A step-by-step process for installing Commotion Wireless on Ubiquiti routers, which are amenable to changing operating systems.</li>
<li><a href="/docs/cck/installing-configuring/configure-commotion">Configure Commotion</a>: Instructions on configuring a Commotion wireless node through the Commotion Setup Wizard and through the administration interface.</li>
<li><a href="/docs/cck/installing-configuring/common-configuration/">Common Configurations</a>: How a node should be configured depends on how it needs to funtion on the mesh network. Learn about different ways to configure a Commotion node.</li>
<li><a href="/docs/cck/installing-configuring/troubleshoot-your-wireless-node">Troubleshoot Your Wireless Node</a>: Includes&nbsp;steps to identify and&nbsp;solve the most common problems that may arise with your Commotion router or wireless network.</li>
<li><a href="/docs/cck/installing-configuring/common-hardware-setups/">Common Hardware Setups</a>: How a node should be configured depends on how it needs to funtion on the mesh network. Learn about the most common Commotion configurations.</li>
<li><a href="/docs/cck/installing-configuring/advanced-hardware-setups/">Advanced Hardware Setups</a>: For hardware configurations that involve multiple nodes at a single site, or other unique situations, this guide provides instructions.</li>
<li><a href="/docs/cck/installing-configuring/troubleshoot-your-wireless-node">Troubleshoot Your Wireless Node</a>: Includes steps to identify and solve the most common problems that may arise with your Commotion router or wireless network.</li>
<li><a href="/docs/cck/installing-configuring/install-and-recover-tftp">Install and Recover with TFTP</a>: An alternate installation process if the regular approach does not work or there is a problem with installing Commotion Wireless.</li>
</ul>

Expand Down

Large diffs are not rendered by default.

This file was deleted.

Original file line number Diff line number Diff line change
@@ -0,0 +1,204 @@
---
layout: cck
title: Common Hardware Setups
site_section: help
sub_section: [cck,cck-installing]
pdf: cck/installing-configuring/CCK-Common_Hardware_Setups.pdf
pdf-all: true
categories:
created: 2013-11-06
changed: 2014-08-13
post_author: andygunn
lang: en
---

<img alt="Commotion Common Configurations graphic" src="/files/CCK_CommonConfigs_Intro.png" style="max-width:600px;" />

<section id="introduction">
<h2>Introduction</h2>

<p>When planning and building a network, you will need to install the wireless node or nodes that make the most sense for each site. In most cases, a single wireless node on a rooftop or in a window will connect to nearby neighbors and form a mesh. In some cases, this wireless node may be connected by Ethernet cable to a gateway connection to the Internet, sharing it with those neighbors. In other cases, the node will be connected by Ethernet cable to one or more computers inside the building, some of which may be sharing local applications. In almost all cases, rooftop or window wireless nodes will have Access Points enabled to allow people to connect to the network wirelessly.</p>

<p>The instructions below are designed to show you how to configure and install the hardware in these different ways. Each configuration listed below describes the settings you should change to make the network work according to your plans. These are the three most common configurations of Commotion nodes - if you have more complex needs or want to install multiple nodes at a single site, please consult the <a href="/docs/cck/installing-configuring/advanced-hardware-setups/">Advanced Hardware Setups</a> guide.</p>
</section>

<section id="materials-and-supplies-needed">
<h3>Materials + Supplies needed</h3>

<ol class="rteindent1">
<li>A printout of the configuration you need, including specific information for the node you are working on.</li>
<li>Information about the configuration for other nodes in the network.</li>
</ol>

<p><strong>Time required: Varies depending on the configuration - from 10 to 30 minutes.</strong></p>
</section>

<section id="nodes-meshed-wirelessly">
<h2>Two or more nodes meshing wirelessly</h2>

<p>The most common configuration of wireless nodes is made up of the nodes themselves, the mesh links between nodes, and any users connected to the network. It involves two or more wireless nodes, installed with the Commotion software. The nodes in the example below are an assortment of omnidirectional nodes, but the specific type doesn’t matter as long as they are within wireless range of each other.</p>

<p><img src="/files/CCK_CommonConfigs_01_Nodes_meshed_wirelessly_building.png" style="max-width:800px;" /></p>

<p>In the diagram above:</p>
<ul class="rteindent1">
<li><strong>(A)</strong> Represents wireless nodes running the Commotion software.</li>
<li><strong>(B)</strong> Represents the wireless mesh links between the nodes.</li>
<li><strong>(C)</strong> Represents the Access Point generated by the Commotion node for users to connect to.</li>
<li><strong>(D)</strong> Represents a person using a laptop, connected to a rooftop node’s Access Point.</li>
</ul>

<p><strong>Steps to Configure:</strong></p>
<p>The Commotion nodes should mesh wirelessly after running the Setup Wizard on the first boot, as long as the nodes were configured with the same:</p>
<ul class="rteindent1">
<li><strong>Mesh network name.</strong> By default, this is set to commotionwireless.net.</li>
<li><strong>Wireless channel.</strong> By default, this is 11 for 2.4GHz wireless devices.</li>
<li><strong>Mesh encryption password.</strong> The passwords must match across the network. You can also disable encryption across the network.</li>
</ul>

<p>After the initial configuration with the Setup Wizard, these settings are all visible and editable in the <strong>Basic Configuration -> Network Settings -> Mesh Network</strong> menu in the Administration panel of your wireless node. If any nodes are not meshing, check that the mesh settings are identical across all the nodes, and the nodes are in wireless range of each other. For a guide on accessing and changing these settings, see the <a href="/docs/cck/installing-configuring/configure-commotion/">Configure Commotion</a> page.</p>
</section>

<section id="nodes-connected-to-gateway">
<h2>One or more nodes connected to a gateway</h2>

<p>Most networks are designed to provide services, with a connection to the global Internet being the most popular! Commotion is designed to share services across the entire mesh network by default, and will attempt to detect a gateway connection to the Internet when a node boots up. If the wireless node receives an IP address via DHCP on the wired Ethernet port, it will set itself up as a gateway.</p>
<p><img src="/files/CCK_CommonConfigs_02_Nodes_with_gateway_building.png" style="max-width:800px;" /></p>

<p>In the diagram above:</p>
<ul class="rteindent1">
<li><strong>(A)</strong> Represents the nodes running the Commotion software.</li>
<li><strong>(B)</strong> Represents the wireless mesh links between the nodes.</li>
<li><strong>(C)</strong> Represents the Access Point generated by the Commotion node for users to connect to.</li>
<li><strong>(D)</strong> Represents a user’s laptop, connected to the second node’s access point.</li>
<li><strong>(E)</strong> Represents the modem or router from the Internet Service Provider (ISP), connected to the Internet. It provides IP addresses on the local port with DHCP.</li>
<li><strong>(F)</strong> Represents the connection to the Internet.</li>
</ul>

<p>The type of modem will vary depending on the Internet Service provider, but it should have at least two ports:</p>
<p><img src="/files/CCK_CommonConfigs_02_Nodes_with_gateway_modem.png" style="max-width:400px;" /></p>

<ul class="rteindent1">
<li><strong>(G)</strong> Shows the modem LAN port, which is connected to the Commotion WAN port. There may be multiple LAN ports on the modem or router, any should work fine.</li>
<li><strong>(H)</strong> Shows the modem connection to the Internet - via DSL, cable, 3G USB adapter, or other type.</li>
</ul>

<p>The cable from the modem LAN port should run to the WAN port on the Commotion node. On most outdoor routers, there will be a single port on the unit’s PoE power supply. On routers with multiple ports, the WAN port will typically be labeled, and is often a different color - usually blue. These examples are shown below:</p>
<p><img src="/files/CCK_CommonConfigs_02_Nodes_with_gateway_ports.png" style="max-width:600px;" /></p>

<p><strong>Steps to Configure:</strong></p>
<p>The Commotion nodes should mesh wirelessly after running the Setup Wizard on the first boot, as long as the nodes were configured with the same:</p>
<ul class="rteindent1">
<li><strong>Mesh network name.</strong> By default, this is set to <em>commotionwireless.net</em>.</li>
<li><strong>Wireless channel.</strong> By default, this is 11 for 2.4GHz wireless devices.</li>
<li><strong>Mesh encryption password.</strong> The passwords must match across the network. You can also disable encryption across the network.</li>
</ul>

<p>The first Commotion node connected to the modem should receive an IP address and configure itself as a gateway. It will advertise this on the network by default, as long as the “Advertise your gateway to the mesh” is checked in the <strong>Additional Network Interfaces</strong> menu. At this point, the user connecting with the laptop on a mesh node can access the Internet.</p>

<p>After running the Setup Wizard, you can set the node to “gateway only” mode:</p>
<p><img src="/files/CCK_CommonConfigs_02_Nodes_with_gateway_screenshot.png" style="max-width:600px;" /></p>

<ol class="rteindent1">
<li>In the Administration panel, browse to the <strong>Basic Configuration -> Network Settings -> Additional Network Interfaces</strong> menu.</li>
<li>In the “Gateway Configuration” pull-down menu, select “This device should ALWAYS try to acquire a DHCP lease”.</li>
<li>Make sure “Advertise your gateway to the mesh” is checked.</li>
<li>Save and apply these settings.</li>
</ol>
</section>

<section id="node-connected-to-server">
<h2>Node connected to a local application server</h2>

<p>You have a web server hosting a community blog on your computer, and you want to share it with the neighborhood network. Connect the computer to the mesh node using the wired Ethernet port. The laptop will receive an IP address on the mesh, and you can use Commotion’s application portal to add an entry for the blog, which will be advertised to the users on the mesh via the splash page on all the nodes.</p>
<p><img src="/files/CCK_CommonConfigs_03_Nodes_with_server.png" style="max-width:600px;" /></p>

<p>In the diagram above:</p>
<ul>
<li><strong>(A)</strong> Represents a node running the Commotion software.</li>
<li><strong>(B)</strong> Represents the wireless mesh links between the nodes.</li>
<li><strong>(C)</strong> Represents the Access Point generated by the Commotion node for users to connect to.</li>
<li><strong>(D)</strong> Represents a laptop set up as a server, connected to a node’s wired Ethernet port. In this case, one of the LAN ports.</li>
</ul>

<p>The cable will run from the Commotion nodes’ LAN port. On most outdoor routers, there will be a single port on the unit’s PoE power supply. On routers with multiple ports, the LAN ports will typically be labeled, and are often a different color - usually yellow. These examples are shown below:</p>
<p><img src="/files/CCK_CommonConfigs_03_Nodes_with_server_ports.png" style="max-width:600px;" /></p>

<p><strong>Steps to Configure:</strong></p>
<p>The Commotion nodes should mesh wirelessly after running the Setup Wizard on the first boot, as long as the nodes were configured with the same:</p>
<ul class="rteindent1">
<li><strong>Mesh network name.</strong> By default, this is set to commotionwireless.net.</li>
<li><strong>Wireless channel.</strong> By default, this is 11 for 2.4GHz wireless devices.</li>
<li><strong>Mesh encryption password.</strong> The passwords must match across the network. You can also disable encryption across the network.</li>
</ul>

<p>The Commotion node should provide an IP address to the connected computer. To make sure this is always the case, you can set the node to “DHCP server only” mode:</p>
<p><img src="/files/CCK_CommonConfigs_03_Nodes_with_server_screenshot.png" style="max-width:600px;" /></p>

<ol class="rteindent1">
<li>In the Administration panel, browse to the <strong>Basic Configuration -> Network Settings -> Additional Network Interfaces</strong> menu.</li>
<li>In the “Gateway Configuration” pull-down menu, select “This device should ALWAYS provide DHCP leases to clients”.</li>
<li>Save and apply these settings.</li>
</ol>
</section>

<section id="node-connected-t0-ap">
<h2>Node connected to an external AP or router</h2>

<p>If there is no Internet connection inside a building, you can connect to the rooftop mesh network to provide access. Connect an indoor Access Point or router with a wireless AP to the wired Ethernet port of the Commotion node on the roof. The node will provide any users connecting to the AP with wireless devices such as smartphones and laptops with IP addresses on the mesh. These non-Commotion routers and Access Points can add wireless coverage to areas not covered by the outdoor mesh nodes. By connecting to these indoor APs, users can access the services and gateways that are on the mesh. Since Commotion isn’t compatible with every router, this method allows you to use routers and Access Points you might already have.</p>
<p><img src="/files/CCK_CommonConfigs_04_Nodes_with_AP.png" style="max-width:600px;" /></p>

<p>In the diagram above:</p>
<ul>
<li><strong>(A)</strong> Represents the nodes running the Commotion software.</li>
<li><strong>(B)</strong> Represents the wireless mesh links between the nodes.</li>
<li><strong>(C)</strong> Represents the Access Point generated by the Commotion node for users to connect to.</li>
<li><strong>(D)</strong> Represents an external Access Point or router, not running Commotion. This is connected to the second node’s wired Ethernet LAN port.</li>
</ul>

<p>The diagram below demonstrates what this would look like with equipment installed on a building:</p>
<p><img src="/files/CCK_CommonConfigs_04_Nodes_with_AP_building.png" style="max-width:600px;" /></p>

<p><strong>Steps to Configure:</strong></p>
<p>The Commotion nodes should mesh wirelessly after running the Setup Wizard on the first boot, as long as the nodes were configured with the same:</p>
<ul>
<li><strong>Mesh network name.</strong> By default, this is set to commotionwireless.net.</li>
<li><strong>Wireless channel.</strong> By default, this is 11 for 2.4GHz wireless devices.</li>
<li><strong>Mesh encryption password.</strong> If you don’t want to encrypt the mesh network, you can leave this blank to disable it.</li>
</ul>

<p>Make sure that the Commotion node’s LAN port is plugged into the “WAN” port of the Access Point or router. The WAN port is the “incoming” connection port, where you would plug in a modem for access to the Internet. The Commotion node should provide an IP address to the AP and any users that connect. To make sure this is always the case, after running the Setup Wizard, you can set the node to “DHCP server only” mode:</p>
<p><img src="/files/CCK_CommonConfigs_03_Nodes_with_server_screenshot.png" style="max-width:600px;" /></p>
<ol class="rteindent1">
<li>In the Administration panel, browse to the <strong>Basic Configuration -> Network Settings -> Additional Network Interfaces</strong> menu.</li>
<li>In the “Gateway Configuration” pull-down menu, select “This device should ALWAYS provide DHCP leases to clients”.</li>
<li>Save and apply these settings.</li>
</ol>
</section>

<section id="section-conclusion">
<h2>Conclusion</h2>
<p>That covers the three most basic setups for installing and configuring Commotion nodes. If you want to see additional configuration examples and the steps to set it up, see the <a href="/docs/cck/installing-configuring/advanced-hardware-setups/">Advanced Hardware Setups</a> guide.
</p>

</section>

<section id="section-definitions">
<h2>Definitions</h2>

<dl>
<dt>AP (Access Point)</dt>
<dd>A device that allows wireless devices to connect to a wired network using Wi-Fi or related standards</dd>
<dt>DHCP: Dynamic Host Configuration Protocol</dt>
<dd>It assigns IP addresses to client devices, such as desktop computers, laptops, and phones, when they are plugged into Ethernet or connect to Wireless networks.</dd>
<dt>Ethernet</dt>
<dd>A type of networking protocol - it defines the types of cables and connections that are used to wire computers, switches, and routers together. Most often Ethernet cabling is Category 5 or 6, made up of twisted pair wiring similar to phone cables.</dd>
<dt>Router</dt>
<dd>A device that determines how messages move through a computer network.</dd>
<dt>Node</dt>
<dd>An individual device in a mesh network.</dd>
<dt>WAN: Wide Area Network</dt>
<dd>Signifies the connection to the global Internet or a different, typically larger, network.</dd>
</dl>

</section>
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Binary file not shown.
Binary file not shown.
Binary file not shown.