diff --git a/commotionwireless.net/docs/cck/installing-configuring/advanced-hardware-setups/index.md b/commotionwireless.net/docs/cck/installing-configuring/advanced-hardware-setups/index.md index a50bcb56..5b04659d 100644 --- a/commotionwireless.net/docs/cck/installing-configuring/advanced-hardware-setups/index.md +++ b/commotionwireless.net/docs/cck/installing-configuring/advanced-hardware-setups/index.md @@ -3,285 +3,345 @@ layout: cck title: Advanced Hardware Setups site_section: docs sub_section: [cck,cck-installing] -pdf: cck/installing-configuring/CCK-Advanced_Hardware_Setups.pdf -pdf-all: true -categories: +pdf: cck/installing-configuring/Advanced_Hardware_Setups.pdf created: 2014-08-13 -changed: 2014-08-13 +changed: 2015-09-16 post_author: andygunn lang: en --- -Common Configurations graphic +![Common Configurations graphic](/files/CCK_CommonConfigs_Intro2.png) -
-

Introduction

+## Introduction -

For most community wireless networks, installing a few rooftop and window nodes will fit the needs of the neighborhood or town. For others, more complex installations and configurations will be required. This guide follows and is an advanced companion to Common Hardware Setups, which covers the most common and basic Commotion configurations.

- -

Sometimes you will need to connect multiple nodes together at a single site, and this guide will help you do that. Some of the instructions below require some familiarity with networking concepts, so we recommend reading through Learn Networking Basics first.

-

-
- - -
-

Materials + Supplies needed

- -
    -
  1. A printout of the configuration you need, including specific information for the node you are working on.
    2. -
  2. Information about the configuration for other nodes in the network.
    3. -
- -

Time required: Varies depending on the complexity - from 20 minutes to an hour.

-
- - -
-

Meshing with Ethernet, with a gateway to the Internet using DHCP for automatic assignment of IP addresses

- -

If you want to provide a gateway connection to the Internet on your mesh network, it helps to use several nodes at the location hosting that connection. This should reduce bottlenecks that would occur if there were only one node connected to that gateway.

-

- -

In the diagram above:

- - -

The diagram below demonstrates what this would look like with equipment installed on a building:

-

- -

Steps to Configure:

-

First, ensure the Commotion nodes mesh with wireless neighbors. Run the Setup Wizard on the first boot, with the same:

- - -

The nodes connected to the modem or router should receive IP addresses and configure themselves as gateways. To ensure the nodes are receiving IP addresses, make sure each node is plugged into the switch, then reboot each node after running Setup Wizard:

- -
    -
  1. Browse to Advanced -> System -> Reboot.
    2. -
  2. Click “Perform reboot” and wait for the device to restart.
    3. -
- -

Second, set the nodes to “gateway only” to prevent issues with the nodes booting before the modem.

- -
    -
  1. Browse to the Administration panel on the node.
    2. -
  2. Navigate to the Basic Configuration -> Network Settings -> Additional Network Interfaces menu.
    3. -
  3. In the “Gateway Configuration” pull-down menu, select “This device should ALWAYS try to acquire a DHCP lease”, and make sure “Advertise your gateway to the mesh” is checked.
    4. -
  4. "Save and apply" these settings.
    5. -
- -

Third, enable meshing over Ethernet for the nodes connected to the switch.

- -
    -
  1. Browse to the Administration panel on the node.
    2. -
  2. Navigate to to the Advanced -> Services -> OLSR menu.
    3. -
  3. At the bottom of the page, under the interfaces section, click on the "Add" button.
    4. -
  4. On the next page, click radio button for the "WAN" interface under "Network".
    5. -
  5. In the “Mode” pull down menu, select "Ether".
    6. -
  6. Scroll to the bottom of the page and "Save and Apply" these changes.
    7. -
- -

Do these steps for each Commotion node connected to the switch. When all the nodes have been configured, you can confirm that they are meshing over the wired Ethernet connections by connecting to one of the nodes and browsing to the Basic Menu -> Status. Then click on “Nearby Mesh Devices” and look under the “OLSR Links” section. You should see entries for all of the nodes connected to the switch, and they should have IP addresses on the same subnet, as given out by the modem or router. These will look like 192.168.x.y, or 10.0.x.y, or something similar. That entry will have an ETX value of 0.100. If this is the case, the nodes are successfully meshing with Ethernet.

- -

 Mounting wireless routers very close to each other can cause interference. For best performance, we recommend:
-1. Mounting equipment on separate poles, with two or three meters (6 to 10 feet) between them.
-2. Using metal shields on the back of directional nodes. These reduce the wireless signal radiated from the back of the equipment, reducing the interference. You can buy these commercially, or make your own from metal building studs.

-
- - -
-

Meshing with Ethernet, without a gateway to the Internet

- -

Even if a tall or centrally located site doesn’t have a gateway to the Internet, it may help to mount several wireless nodes there to act as a “supernode” on the network. This can increase throughput on the network and reduce bottlenecks for very busy nodes or nodes with many, many connections on the mesh.

-

- -

In the diagram above:

- - -

The diagram below demonstrates what this would look like with equipment installed on a building:

-

- -

Steps to Configure:

-

First, ensure the Commotion nodes mesh with wireless neighbors. Run the Setup Wizard on the first boot, with the same:

- - -

The nodes connected to the switch will not receive IP addresses, since there is no modem or router. If the node was previously connected to a router with a DHCP server, disconnect each node and reboot them after running Setup Wizard. This will ensure the nodes do not have incorrect IP address information.

-
    -
  1. Browse to Advanced -> System -> Reboot.
    2. -
  2. Click “Perform reboot” and wait for the device to restart.
    3. -
- -

Next, Browse to the Administration panel on the node first node.

-
    -
  1. Go to the Advanced -> Network -> Interfaces menu
    2. -
      -
    1. Under “Interface Overview”, select “Edit” next to the WAN interface.
      2. -
    2. Under “Common Configuration”, in the "Protocol" pull down menu, change "Commotion Interface" to "Static Address".
      3. -
    3. Click “Switch Protocol” under the prompt “Really switch protocol?”
      4. -
    4. Set the static IP on the interface to a private subnet not already in use in the mesh network. For instance, you could set the IP address to 172.16.100.1 and the Netmask to 255.255.255.0. You can leave the gateway and other fields blank.
      5. -
    5. Scroll down and “Save and Apply” the settings.
      6. -
    -
  2. Add the WAN port to the proper firewall zone.
    3. -
      -
    1. SSH into the node and type the following commands, hitting the Enter key after each line:
      2. -
      -uci add_list firewall.@zone[2].network=wan
-uci commit firewall
-
      -
    2. Log off the node with the command “exit”.
      3. -
    -
  3. In Services -> OLSR, on the General Settings tab, scroll to the bottom and click “Add” in the "Interface" section.
    4. -
      -
    1. In the new page that comes up, click the radio button for the "WAN" interface.
      2. -
    2. In the “Mode” pull down menu, select "Ether".
      3. -
    3. Scroll to the bottom and “save and apply” the settings.
      4. -
    -
- -

Finally, plug each node into the switch and reboot the node one more time. This will ensure the IP address configurations are in the correct state.

- -
    -
  1. Browse to Advanced -> System -> Reboot.
    2. -
  2. Click “Perform reboot” and wait for the device to restart.
    3. -
- -

Do these steps for each Commotion node connected to the switch. When you set the IP on those nodes, you must set it to a different address in the same subnet you configured above. In the example given, you would set the addresses to 172.16.100.2, 172.16.100.3, and so on.

- -

Do these steps for each Commotion node connected to the switch. When all the nodes have been configured, you can confirm that they are meshing over the wired Ethernet connections by connecting to one of the nodes and browsing to the Basic Menu -> Status. Then click on “Nearby Mesh Devices” and look under the “OLSR Links” section. You should see entries for all of the nodes connected to the switch, and they should have IP addresses on the same subnet, as given out by the modem or router. These will look like 192.168.x.y, or 10.0.x.y, or something similar. That entry will have an ETX value of 0.100. If this is the case, the nodes are successfully meshing with Ethernet.

- -

 Mounting wireless routers very close to each other can cause interference. For best performance, we recommend:
-1. Mounting equipment on separate poles, with two or three meters (6 to 10 feet) between them.
-2. Using metal shields on the back of directional nodes. These reduce the wireless signal radiated from the back of the equipment, reducing the interference. You can buy these commercially, or make your own from metal building studs.

-
- - -
-

Meshing with Ethernet, with a gateway to the Internet using Static IP addressing

- -

This example is similar to the other example with a gateway above, but the gateway to the Internet does not provide IP addresses automatically using DHCP. You must configure the addresses for the Commotion nodes manually. In this example the gateway IP address is 192.168.50.1, but you will need to obtain the proper IP address information from your Internet service provider.

-

- -

In the diagram above:

- - -

The diagram below demonstrates what this would look like with equipment installed on a building:

-

- -

Steps to Configure:

-

First, ensure the Commotion nodes mesh with wireless neighbors. Run the Setup Wizard on the first boot, with the same:

- - -

The nodes connected to the switch will not receive IP addresses, since there is no DHCP server. If the node was previously connected to a router with a DHCP server, disconnect each node and reboot them after running Setup Wizard. This will ensure the nodes do not have incorrect IP address information.

-
    -
  1. Browse to Advanced -> System -> Reboot.
    2. -
  2. Click “Perform reboot” and wait for the device to restart.
    3. -
- -

Second, you must configure them with static addresses and a static route to the Internet.

-
    -
  1. While connected to the node over its WiFi access point, browse to the Administration panel on the first node.
    2. -
  2. Go to the Advanced -> Network -> Interfaces menu and select “Edit” on the WAN interface.
    3. -
      -
    1. Under “Common Configuration”, in the "Protocol" pull down menu, change "Commotion Interface" to "Static Address".
      2. -
    2. Click “Switch Protocol”.
      3. -
    3. Set the static IP on the interface to the address assigned by the ISP. In our example, the ISP’s modem has the IP address 192.168.50.1. The items to set are:
      4. -
        -
      1. IPv4 IP Address (Given to you by your ISP, one for each node)
        2. -
      2. IPv4 Netmask (normally 255.255.255.0, but may vary)
        3. -
      -
    4. Save and apply these settings.
      5. -
    -
  3. Add the WAN interface it to the proper firewall zone.
    4. -
      -
    1. SSH into the node and type the following commands, hitting the Enter key after each line:
      2. -
      -uci add_list firewall.@zone[2].network=wan
-uci commit firewall
-
      -
    2. Log off the node with the command “exit”.
      3. -
    -
  4. Finally, go to the Network -> Static Routes menu.
    5. -
      -
    1. Click “Add” in the “Static IPv4 Routes” section.
      2. -
    2. In the entry that comes up, select “WAN” in the first pull-down menu.
      3. -
    3. In the “Target” field, enter 0.0.0.0
      4. -
    4. In the “IPv4-Netmask” field, enter 0.0.0.0
      5. -
    5. In the “IPv4-Gateway” field, enter the IP address for the gateway modem or router from the ISP. In our example this is 192.168.50.1
      6. -
    6. Save and apply these settings.
      7. -
    -
  5. Go to Services -> OLSR:
    6. -
      -
    1. At the bottom of the page, under the interfaces section, click on the "Add" button.
      2. -
    2. On the next page, click radio button for the "WAN" interface under "Network".
      3. -
    3. In the “Mode” pull down menu, select "Ether".
      4. -
    4. Scroll to the bottom and “Save and apply” the settings.
      5. -
    -
- -

Finally, plug each node into the switch and reboot the node one more time. This will ensure the IP address configurations are in the correct state.

-
    -
  1. Browse to Advanced -> System -> Reboot.
    2. -
  2. Click “Perform reboot” and wait for the device to restart.
    3. -
- -

Do these steps for each Commotion node connected to the switch. When you set the IP on those nodes, you must set it to a different address in the same subnet you configured above. In the example given, you would set the addresses to 192.168.50.3, 192.168.50.4, and so on.

- -

Do these steps for each Commotion node connected to the switch. When all the nodes have been configured, you can confirm that they are meshing over the wired Ethernet connections by connecting to one of the nodes and browsing to the Basic Menu -> Status. Then click on “Nearby Mesh Devices” and look under the “OLSR Links” section. You should see entries for all of the nodes connected to the switch, and they should have IP addresses on the same subnet, as given out by the modem or router. These will look like 192.168.x.y, or 10.0.x.y, or something similar. That entry will have an ETX value of 0.100. If this is the case, the nodes are successfully meshing with Ethernet.

- -

 Mounting wireless routers very close to each other can cause interference. For best performance, we recommend:
-1. Mounting equipment on separate poles, with two or three meters (6 to 10 feet) between them.
-2. Using metal shields on the back of directional nodes. These reduce the wireless signal radiated from the back of the equipment, reducing the interference. You can buy these commercially, or make your own from metal building studs.

- -
- -
-

Definitions

- -
-
AP (Access Point)
-
A device that allows wireless devices to connect to a wired network using Wi-Fi or related standards
-
DHCP: Dynamic Host Configuration Protocol
-
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.
-
Ethernet
-
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.
-
Router
-
A device that determines how messages move through a computer network.
-
Node
-
An individual device in a mesh network.
-
WAN: Wide Area Network
-
Signifies the connection to the global Internet or a different, typically larger, network.
-
- -
\ No newline at end of file +For most community wireless networks, installing a few rooftop and window nodes will fit the needs of the neighborhood or town. For others, more complex installations and configurations will be required. This guide follows and is an advanced companion to [Common Hardware Setups](/docs/cck/installing-configuring/common-hardware-setups/), which covers the most common and basic Commotion configurations. + +Sometimes you will need to connect multiple nodes together at a single site, and this guide will help you do that. Some of the instructions below require some familiarity with networking concepts, so we recommend reading through [Learn Networking Basics](/docs/cck/networking/learn-networking-basics/) first. + +![Common configs - buildings](/files/CCK_CommonConfigs_buildings.png) + + +### Jump to the solution you need +1. [Mesh with Ethernet with DHCP](#mesh-with-ethernet-with-dhcp) +2. [Mesh with Ethernet with Static IPs](#mesh-with-ethernet-with-static-addressing) +3. [Mesh with Ethernet with a Static Gateway](#mesh-with-ethernet-with-a-static-gateway) + + +## Mesh with Ethernet with DHCP + +### Using a gateway to the Internet with DHCP for automatic assignment of IP addresses + +If you want to provide a gateway connection to the Internet on your mesh network, it helps to use several nodes at the location hosting that connection. This should reduce bottlenecks that would occur if there were only one node connected to that gateway. + +![Meshing over Ethernet with Gateway](/files/CCK_CommonConfigs_05_Nodes_meshed_via_Ethernet_with_gateway.png) + +In the diagram above: + +* **(A)** Represents a node running the Commotion software. +* **(B)** Represents the wireless mesh links between the nodes. +* **(C)** Represents the Access Point generated by the Commotion node for users to connect to. +* **(D)** Represents an Ethernet switch, which transfers data between all connected devices. +* **(E)** Represents Ethernet cabling connecting the modem and nodes to the Ethernet switch. +* **(F)** 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. +* **(G)** Represents the Internet. + + +The diagram below demonstrates what this would look like with equipment installed on a building: +![Mesh over Ethernet on a building](/files/CCK_CommonConfigs_05_Nodes_meshed_via_Ethernet_with_gateway_building.png) + +**Steps to Configure:** +First, ensure the Commotion nodes mesh with wireless neighbors. Run the Setup Wizard on the first boot, with the same **Mesh network name**, **Wireless channel**, and **Mesh encryption password**. + +You should also configure the node to allow connections on the Ethernet port to the Administration interface. Follow the instructions for "Opening the firewall for remote Administration" in [Advanced Commotion mesh settings](/docs/cck/installing-configuring/configure-commotion/#Advanced-Commotion-mesh-settings). + + +#### Set to Receive DHCP only +Now, set the nodes to “gateway only” to prevent issues with the nodes booting before the modem. Browse to the Administration panel on the node. Navigate to the **Basic Configuration -> Network Settings -> Additional Network Interfaces** menu. +![Additional network interfaces](/files/Additional-network-interfaces.png) + +1. In the “Gateway Configuration” pull-down menu, select “This device should ALWAYS try to acquire a DHCP lease”, and make sure “Advertise your gateway to the mesh” is checked. +2. **Save**, then **Save and apply** these settings. + + +#### Enable meshing over the Ethernet port +Next, enable meshing over Ethernet for the nodes connected to the switch. Navigate to to the **Advanced -> Services -> OLSR** menu. + +At the bottom of the page, under the interfaces section, click on the "Add" button. +![Services OLSR page](/files/Services-OLSR.png) + +1. On the next page, click radio button for the "WAN" interface under "Network". +2. In the “Mode” pull down menu, select "Ether". + +![OLSR add WAN interface](/files/Services-OLSR-add-WAN.png) + +Scroll to the bottom of the page and "Save and Apply" these changes. + + +#### Change Firewall Settings +Finally, adjust the Firewall so mesh traffic can pass through in both directions. Navigate to the **Advanced -> Network -> Firewall** menu. Scroll down to the bottom of the page, to the section that is titled "Zones". It should look like this: +![Firewall zones original](/files/firewall-zones-orig.png) + +Click the “Edit” button in the WAN row – it should open up the *Firewall – Zone Settings – Zone +“wan”* page. Scroll down until you see the section that says “Inter-zone forwarding”. It should look +like this: +![Firewall configuration original](/files/firewall-conf-orig.png) + +Under “Allow forward to *destination zones*”, click the boxes next to “lan” and “mesh”. This will enable +traffic to pass from WAN to LAN and MESH. The screen should now look like: +![Firewall configuration changed](/files/firewall-conf-changed.png) + +Hit “Save & Apply”. Click on “General Settings” at the top of the page. You should be returned to the +“Firewall – Zone Settings” page. Scroll down and look at the table of zones. It should look like this: +![Firewall zones changed](/files/firewall-zones-changed.png) + +#### Reboot and Verify +Reboot the router to verify the settings. + +1. Browse to **Advanced -> System -> Reboot.** +2. Click “Perform reboot” and wait for the device to restart. + +Do these steps for each Commotion node connected to the switch. When all the nodes have been configured, you can confirm that they are meshing over the wired Ethernet connections by connecting to one of the nodes and browsing to the **Basic Menu -> Status**. Then click on “Nearby Mesh Devices” and look under the “OLSR Links” section. You should see entries for all of the nodes connected to the switch, and they should have IP addresses on the same subnet, as given out by the modem or router. These will look like 192.168.x.y, or 10.0.x.y, or something similar. That entry will have an ETX value of 0.100. If this is the case, the nodes are successfully meshing with Ethernet. + +*Tip: Mounting wireless routers very close to each other can cause interference. For best performance, we recommend mounting equipment on separate poles, with two or three meters (6 to 10 feet) between them and using metal shields on the back of directional nodes. These reduce the wireless signal radiated from the back of the equipment, reducing the interference. You can [buy these commercially](http://www.rfarmor.com), or [make your own from metal building studs](http://gowasabi.net/content/importance-shielding).* + + +## Mesh with Ethernet with Static addressing + +### Static IP addresses, without a Gateway to the Internet + +Even if a tall or centrally located site doesn’t have a gateway to the Internet, it may help to mount several wireless nodes there to act as a “supernode” on the network. This can increase throughput on the network and reduce bottlenecks for very busy nodes or nodes with many, many connections on the mesh. +![Mesh over Ethernet no gateway](/files/CCK_CommonConfigs_06_Nodes_meshed_via_Ethernet_with_no_gateway.png) + +In the diagram above: + +* **(A)** Represents a node running the Commotion software. +* **(B)** Represents the wireless mesh links between the nodes. +* **(C)** Represents the Access Point generated by the Commotion node for users to connect to. +* **(D)** Represents an Ethernet switch, which transfers data between all connected devices. +* **(E)** Represents Ethernet cabling connecting the modem and nodes to the Ethernet switch. + +The diagram below demonstrates what this would look like with equipment installed on a building: +![Mesh over Ethernet on building](/files/CCK_CommonConfigs_06_Nodes_meshed_via_Ethernet_with_no_gateway_building.png) + +**Steps to Configure:** +First, ensure the Commotion nodes mesh with wireless neighbors. Run the Setup Wizard on the first boot, with the same **Mesh network name**, **Wireless channel**, and **Mesh encryption password**. + +You should also configure the node to allow connections on the Ethernet port to the Administration interface. Follow the instructions for "Opening the firewall for remote Administration" in [Advanced Commotion mesh settings](/docs/cck/installing-configuring/configure-commotion/#Advanced-Commotion-mesh-settings). + +The nodes connected to the switch will not receive IP addresses, since there is no modem or router. If the node was previously connected to a router with a DHCP server, disconnect each node and reboot them after running Setup Wizard. This will ensure the nodes do not have incorrect IP address information. + + +#### Change the WAN port to use Static Addressing +Browse to the Administration panel on the node. + +1. In the Basic Configuration menus, go to the **Network Settings -> Additional Network Interfaces** menu +2. Select the box under “Will you be meshing with other Commotion devices over the Ethernet +interface?”. The page will change and two fields will appear. +3. Put in a static IP address and Netmask for this router. + +![Additional network Interfaces - MoE](/files/Additional-network-interfaces-MoE.png) + +If you are adding the router to the same switch with others that are meshing over Ethernet, use an IP +address in the same range. For example, if a node had the address 172.16.10.5, you could use 172.16.10.6. + +If you are setting up mesh over Ethernet at a new site, use an IP address range that isn't in use +somewhere else. For example, if the 172.16.10.x range is in use somewhere, don't use it again – +this will cause problems on the network. You could use 172.16.11.x, 10.50.0.x, or something else. It is +recommended not to use 192.168.x.x since many home and office routers use these ranges. + +The Netmask will almost always be 255.255.255.0. + + +#### Enable meshing over the Ethernet port +Next, enable meshing over Ethernet for the nodes connected to the switch. Navigate to to the **Advanced -> Services -> OLSR** menu. + +At the bottom of the page, under the interfaces section, click on the "Add" button. +![Services OLSR page](/files/Services-OLSR.png) + +1. On the next page, click radio button for the "WAN" interface under "Network". +2. In the “Mode” pull down menu, select "Ether". + +![OLSR add interface](/files/Services-OLSR-add-WAN.png) + +Scroll to the bottom of the page and "Save and Apply" these changes. + + +#### Change Firewall Settings +Finally, adjust the Firewall so mesh traffic can pass through in both directions. Navigate to the **Advanced -> Network -> Firewall** menu. Scroll down to the bottom of the page, to the section that is titled "Zones". It should look like this: +![Firewall zones original](/files/firewall-zones-orig.png) + +Click the “Edit” button in the WAN row – it should open up the *Firewall – Zone Settings – Zone +“wan”* page. Scroll down until you see the section that says “Inter-zone forwarding”. It should look +like this: +![Firewall configuration original](/files/firewall-conf-orig.png) + +Under “Allow forward to *destination zones*”, click the boxes next to “lan” and “mesh”. This will enable +traffic to pass from WAN to LAN and MESH. The screen should now look like: +![Firewall configuration changed](/files/firewall-conf-changed.png) + +Hit “Save & Apply”. Click on “General Settings” at the top of the page. You should be returned to the +“Firewall – Zone Settings” page. Scroll down and look at the table of zones. It should look like this: +![Firewall zones changed](/files/firewall-zones-changed.png) + + +#### Add a HNA to the Static IP range +Add a Host Network Announcement (HNA) for the Static IP address range for the nodes. This setting lets the rest of the mesh network know where to find anything attached to the switch that might have those Static IPs. + +Go to **Advanced → Services → OLSR**, and click on “HNA Announcements” at the top of the page. +![OLSR menu](/files/OLSR-HNA-menu.png) + +Click the “Add” button to create a new line, and put the following settings into the boxes: + +* Network address: *your static IP range, ending with a zero* +* Netmask: 255.255.255.0 + +![OLSR HNA entry add](/files/OLSR-HNA-entry-add.png) + +At the bottom of the page, hit “Save & Apply”. + + +#### Reboot and Verify +Finally, plug each node into the switch and reboot the node one more time. This will ensure the IP address configurations are in the correct state. + +* Browse to **Advanced -> System -> Reboot**. +* Click “Perform reboot” and wait for the device to restart. + +Do these steps for each Commotion node connected to the switch. When all the nodes have been configured, you can confirm that they are meshing over the wired Ethernet connections by connecting to one of the nodes and browsing to the **Basic Menu -> Status**. Then click on “Nearby Mesh Devices” and look under the “OLSR Links” section. You should see entries for all of the nodes connected to the switch, and they should have IP addresses on the same subnet, as given out by the modem or router. These will look like 192.168.x.y, or 10.0.x.y, or something similar. That entry will have an ETX value of 0.100. If this is the case, the nodes are successfully meshing with Ethernet. + +*Tip: Mounting wireless routers very close to each other can cause interference. For best performance, we recommend mounting equipment on separate poles, with two or three meters (6 to 10 feet) between them and using metal shields on the back of directional nodes. These reduce the wireless signal radiated from the back of the equipment, reducing the interference. You can [buy these commercially](http://www.rfarmor.com), or [make your own from metal building studs](http://gowasabi.net/content/importance-shielding).* + + +## Mesh with Ethernet with a Static Gateway + +### Using Static IP addressing, with a Gateway to the Internet + +This example is similar to the other example with a gateway above, but the gateway to the Internet does not provide IP addresses automatically using DHCP. You must configure the addresses for the Commotion nodes manually. In this example the gateway IP address is 192.168.50.1, but you will need to obtain the proper IP address information from your Internet service provider. +![Mesh over Ethernet static gateway](/files/CCK_CommonConfigs_05_Nodes_meshed_via_Ethernet_with_gateway.png) + +In the diagram above: + +* **(A)** Represents a node running the Commotion software. +* **(B)** Represents the wireless mesh links between the nodes. +* **(C)** Represents the Access Point generated by the Commotion node for users to connect to. +* **(D)** Represents an Ethernet switch, which transfers data between all connected devices. +* **(E)** Represents Ethernet cabling connecting the modem and nodes to the Ethernet switch. +* **(F)** Represents the modem or router from the Internet Service Provider (ISP), connected to the Internet. It is configured with a Static IP address, and does not provide IP addresses to clients automatically via DHCP. +* **(G)** Represents the Internet. + +The diagram below demonstrates what this would look like with equipment installed on a building: +![Mesh over Ethernet static gateway building](/files/CCK_CommonConfigs_05_Nodes_meshed_via_Ethernet_with_gateway_building.png) + +**Steps to Configure:** +First, ensure the Commotion nodes mesh with wireless neighbors. Run the Setup Wizard on the first boot, with the same **Mesh network name**, **Wireless channel**, and **Mesh encryption password**. + +You should also configure the node to allow connections on the Ethernet port to the Administration interface. Follow the instructions for "Opening the firewall for remote Administration" in [Advanced Commotion mesh settings](/docs/cck/installing-configuring/configure-commotion/#Advanced-Commotion-mesh-settings). + +The nodes connected to the switch will not receive IP addresses, since there is no DHCP server. If the node was previously connected to a router with a DHCP server, disconnect each node and reboot them after running Setup Wizard. This will ensure the nodes do not have incorrect IP address information. + +1. Browse to **Advanced -> System -> Reboot.** +2. Click “Perform reboot” and wait for the device to restart. + + +#### Change the WAN port to use Static Addressing +Browse to the Administration panel on the node. + +1. In the Basic Configuration menus, go to the **Network Settings -> Additional Network Interfaces** menu +2. Select the box under “Will you be meshing with other Commotion devices over the Ethernet +interface?”. The page will change and two fields will appear. +3. Put in a static IP address and Netmask for this router. + +![Additional network Interfaces - MoE](/files/Additional-network-interfaces-MoE.png) + +The static IP that you choose should be in the same range as the IP address of the router that has the connection to the Internet. For example, if the gateway's IP is 10.50.0.1, you would choose a static IP for the node in the 10.50.0.x range, where "x" is a number that isn't in use by any other nodes, servers, or devices. + +The Netmask will almost always be 255.255.255.0. + + +#### Set a Static Gateway +Configure the node with a static route to the Internet. Browse to the Administration panel on the first node. Go to the **Advanced -> Network -> Static Routes** menu. + +1. Click “Add” in the “Static IPv4 Routes” section. +2. In the entry that comes up, select “WAN” in the first pull-down menu. +3. In the “Target” field, enter 0.0.0.0 +4. In the “IPv4-Netmask” field, enter 0.0.0.0 +5. In the “IPv4-Gateway” field, enter the IP address for the gateway modem or router. +6. Save and apply these settings. + + +#### Enable meshing over the Ethernet port +Next, enable meshing over Ethernet for the nodes connected to the switch. Navigate to to the **Advanced -> Services -> OLSR** menu. + +At the bottom of the page, under the interfaces section, click on the "Add" button. +![Services OLSR page](/files/Services-OLSR.png) + +1. On the next page, click radio button for the "WAN" interface under "Network". +2. In the “Mode” pull down menu, select "Ether". + +![OLSR add interface](/files/Services-OLSR-add-WAN.png) + +Scroll to the bottom of the page and "Save and Apply" these changes. + + +#### Change Firewall Settings +Finally, adjust the Firewall so mesh traffic can pass through in both directions. Navigate to the **Advanced -> Network -> Firewall** menu. Scroll down to the bottom of the page, to the section that is titled "Zones". It should look like this: +![Firewall zones original](/files/firewall-zones-orig.png) + +Click the “Edit” button in the WAN row – it should open up the *Firewall – Zone Settings – Zone +“wan”* page. Scroll down until you see the section that says “Inter-zone forwarding”. It should look +like this: +![Firewall configuration original](/files/firewall-conf-orig.png) + +Under “Allow forward to *destination zones*”, click the boxes next to “lan” and “mesh”. This will enable +traffic to pass from WAN to LAN and MESH. The screen should now look like: +![Firewall configuration changed](/files/firewall-conf-changed.png) + +Hit “Save & Apply”. Click on “General Settings” at the top of the page. You should be returned to the +“Firewall – Zone Settings” page. Scroll down and look at the table of zones. It should look like this: +![Firewall zones changed](/files/firewall-zones-changed.png) + + +#### Add a HNA to the Static IP range +Add a Host Network Announcement (HNA) for the Static IP address range for the nodes. This setting lets the rest of the mesh network know where to find anything attached to the switch that might have those Static IPs. + +Go to **Advanced → Services → OLSR**, and click on “HNA Announcements” at the top of the page. +![OLSR menu](/files/OLSR-HNA-menu.png) + +Click the “Add” button to create a new line, and put the following settings into the boxes: + +* Network address: *your static IP range, ending with a zero* +* Netmask: 255.255.255.0 + +![OLSR HNA entry add](/files/OLSR-HNA-entry-add.png) + +At the bottom of the page, hit “Save & Apply”. + + +Finally, plug each node into the switch and reboot the node one more time. This will ensure the IP address configurations are in the correct state. + +1. Browse to **Advanced -> System -> Reboot**. +2. Click “Perform reboot” and wait for the device to restart. + +Do these steps for each Commotion node connected to the switch. When all the nodes have been configured, you can confirm that they are meshing over the wired Ethernet connections by connecting to one of the nodes and browsing to the **Basic Menu -> Status**. Then click on “Nearby Mesh Devices” and look under the “OLSR Links” section. You should see entries for all of the nodes connected to the switch, and they should have IP addresses on the same subnet, as given out by the modem or router. These will look like 192.168.x.y, or 10.0.x.y, or something similar. That entry will have an ETX value of 0.100. If this is the case, the nodes are successfully meshing with Ethernet. + +*Tip: Mounting wireless routers very close to each other can cause interference. For best performance, we recommend mounting equipment on separate poles, with two or three meters (6 to 10 feet) between them and using metal shields on the back of directional nodes. These reduce the wireless signal radiated from the back of the equipment, reducing the interference. You can [buy these commercially](http://www.rfarmor.com), or [make your own from metal building studs](http://gowasabi.net/content/importance-shielding).* + + +## Definitions + +AP (Access Point) +: A device that allows wireless devices to connect to a wired network using Wi-Fi or related standards + +DHCP +: Dynamic Host Configuration Protocol. This assigns IP addresses to client devices, such as desktop computers, laptops, and phones, when they are plugged into Ethernet or connect to Wireless networks. + +Ethernet +: 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. + +Router +: A device that determines how messages move through a computer network. + +Node +: An individual device in a mesh network. + +WAN +: Wide Area Network. This signifies the connection to the global Internet or a different, typically larger, network. diff --git a/commotionwireless.net/files/Additional-network-interfaces-MoE.png b/commotionwireless.net/files/Additional-network-interfaces-MoE.png new file mode 100644 index 00000000..0e62d2fc Binary files /dev/null and b/commotionwireless.net/files/Additional-network-interfaces-MoE.png differ diff --git a/commotionwireless.net/files/Additional-network-interfaces.png b/commotionwireless.net/files/Additional-network-interfaces.png new file mode 100644 index 00000000..52d14d29 Binary files /dev/null and b/commotionwireless.net/files/Additional-network-interfaces.png differ diff --git a/commotionwireless.net/files/CCK_tip_icon.png b/commotionwireless.net/files/CCK_tip_icon.png new file mode 100644 index 00000000..e4abed15 Binary files /dev/null and b/commotionwireless.net/files/CCK_tip_icon.png differ diff --git a/commotionwireless.net/files/OLSR-HNA-entry-add.png b/commotionwireless.net/files/OLSR-HNA-entry-add.png new file mode 100644 index 00000000..415b8c65 Binary files /dev/null and b/commotionwireless.net/files/OLSR-HNA-entry-add.png differ diff --git a/commotionwireless.net/files/OLSR-HNA-menu.png b/commotionwireless.net/files/OLSR-HNA-menu.png new file mode 100644 index 00000000..11ca3fcc Binary files /dev/null and b/commotionwireless.net/files/OLSR-HNA-menu.png differ diff --git a/commotionwireless.net/files/Services-OLSR-add-WAN.png b/commotionwireless.net/files/Services-OLSR-add-WAN.png new file mode 100644 index 00000000..54ca0bab Binary files /dev/null and b/commotionwireless.net/files/Services-OLSR-add-WAN.png differ diff --git a/commotionwireless.net/files/Services-OLSR.png b/commotionwireless.net/files/Services-OLSR.png new file mode 100644 index 00000000..2bcd32c4 Binary files /dev/null and b/commotionwireless.net/files/Services-OLSR.png differ diff --git a/commotionwireless.net/files/cck/installing-configuring/CCK-Advanced_Hardware_Setups.pdf b/commotionwireless.net/files/cck/installing-configuring/Advanced_Hardware_Setups.pdf similarity index 59% rename from commotionwireless.net/files/cck/installing-configuring/CCK-Advanced_Hardware_Setups.pdf rename to commotionwireless.net/files/cck/installing-configuring/Advanced_Hardware_Setups.pdf index a31be44e..b077c7ea 100644 Binary files a/commotionwireless.net/files/cck/installing-configuring/CCK-Advanced_Hardware_Setups.pdf and b/commotionwireless.net/files/cck/installing-configuring/Advanced_Hardware_Setups.pdf differ diff --git a/commotionwireless.net/files/firewall-conf-changed.png b/commotionwireless.net/files/firewall-conf-changed.png new file mode 100644 index 00000000..fdf86bb4 Binary files /dev/null and b/commotionwireless.net/files/firewall-conf-changed.png differ diff --git a/commotionwireless.net/files/firewall-conf-orig.png b/commotionwireless.net/files/firewall-conf-orig.png new file mode 100644 index 00000000..73927477 Binary files /dev/null and b/commotionwireless.net/files/firewall-conf-orig.png differ diff --git a/commotionwireless.net/files/firewall-zones-changed.png b/commotionwireless.net/files/firewall-zones-changed.png new file mode 100644 index 00000000..a2806f87 Binary files /dev/null and b/commotionwireless.net/files/firewall-zones-changed.png differ diff --git a/commotionwireless.net/files/firewall-zones-orig.png b/commotionwireless.net/files/firewall-zones-orig.png new file mode 100644 index 00000000..bc7fe1fa Binary files /dev/null and b/commotionwireless.net/files/firewall-zones-orig.png differ