[Commotion-admin] [luci-commotion] Issue 150 (#153)

Seamus Tuohy notifications at github.com
Thu Feb 20 18:01:04 UTC 2014


Fixed firewall issue, and removed extraneous options from additional network interfaces when meshing == true. Testing instructions follow...

# Testing Instructions #

## Router Prep
* Flash two routers with a build that uses the *issue_150* branch of  *luci-commotion*
* In the next step SKIP the additional network interfaces section by pressing the finish button when you get to the section below
* Run setup wizard on both devices configuring their mesh-networks to mesh with each other 

![finish_button](https://f.cloud.github.com/assets/1226247/2221205/1a932822-9a56-11e3-98c4-424c88fe3e26.png)

* Connect to one device using the Wireless AP
* Check the *Status --> Nearby Mesh Devices* page on that device to ensure that both devices are meshed wirelessly.

![wireless_mesh](https://f.cloud.github.com/assets/1226247/2221257/93ccd47c-9a56-11e3-8958-bec7d5b8a4f3.png)

* Connect both devices  to each other using an ethernet cable
*  Using the mesh-ip address of the other given to you on the status page of the first device connect to the second device.

### WIRELESSLY OVER THE MESH ON THE SECOND DEVICE ###

** log in to the *Administration* menu
** go to menu: *Basic Configuration --> Additional Network Interfaces*
** Click the checkbox under "Will you be meshing with other Commotion devices over the ethernet interface?"

![add_eth_gw](https://f.cloud.github.com/assets/1226247/2221285/ebfe950e-9a56-11e3-8026-6a68975bbb0c.png)

** Set the ip address. [ I used 10.0.1.2 ]
** Set the netmask to 255.255.255.0
** The confirmation page should look somthing like the below.

![eth-confirm-changes](https://f.cloud.github.com/assets/1226247/2221304/19cf94d8-9a57-11e3-9bc0-3741ff722018.png)

### ON THE ORIGINAL NODE ###

* go to menu: Basic Configuration --> Additional Network Interfaces
* Click the checkbox under "Will you be meshing with other Commotion devices over the ethernet interface?"
* Set the ip address to one in the same range *BUT NOT THE EXACT SAME IP AS* the ip address on the old node. [ I used 10.0.1.3 ]
* Set the netmask to 255.255.255.0
* Save and confirm the settings

* At this point the mesh viz is going to look weird.

![weird_viz](https://f.cloud.github.com/assets/1226247/2221317/5e25335e-9a57-11e3-9b55-93e7d190fbdd.png)

* On both nodes go to the menu Advanced --> Network --> Firewall 
*  In the zones section on the bottom of the page you should see "wired" listed in the "mesh" zone

![multi_zone](https://f.cloud.github.com/assets/1226247/2221336/a1caec02-9a57-11e3-80a1-99a992004dc5.png)

* On both nodes go to the menu Advanced --> Status --> OLSR --> Routes
* In the overview of currently known routes you should see a route to each other over the ip-address range that you specified. 

![multi_olsr_routes](https://f.cloud.github.com/assets/1226247/2221359/c433ca16-9a57-11e3-8644-68d25fd716bc.png)

* If your node is working at this point you should turn off the wireless meshing on each device.

### ON THE SECOND DEVICE OVER THE WIRELESS MESH ###

** Go to *Basic (if coming from the advanced menu) --> Basic Configuration --> Mesh Network*
** On the upper-right of the mesh interface shown will be a delete button. Click that button.

![delete_mesh](https://f.cloud.github.com/assets/1226247/2221377/02ea202a-9a58-11e3-9be9-909493450d4c.png)

** You will be taken to a changed page which will show the following.

![eth-changed](https://f.cloud.github.com/assets/1226247/2221389/1f8b6658-9a58-11e3-9f20-1bc8e0981f5e.png)

** Click save, and DO NOT wait for the changes to be applied. The connection is about to be broken to that ip address. So, after about 30 seconds you can leave that page

### ON THE FIRST DEVICE ###

* At this point the second device will fall off the mesh network.
* Now you will turn off the wireless meshing on the first device.
* Go to *Basic (if coming from the advanced menu) --> Basic Configuration --> Mesh Network*
* On the upper-right of the mesh interface shown will be a delete button. Click that button.
* Click save. Unlike the device that we changed over the mesh network WAIT for this page to finish applying changes.

### REBOOT BOTH ROUTERS ###

* Once both nodes come back online go to the access point of one node.
* On the status page you will see the other node listed as a neighbor

* At this point you have confirmed that the nodes are meshing over ethernet using the wired-ethernet address you set in the additional network interfaces section.

![eth-connected](https://f.cloud.github.com/assets/1226247/2221405/556e6874-9a58-11e3-965f-3ad768731ca2.png)

* You can also confirm that they are meshed using the following.

======= TRAFFIC TEST ========
* Go to Advanced (if you are in the basic menu) --> Network --> Diagnostics
* Type in the ethernet ip-address of the node that fell off the network in the "ping" field and press the "ping" button.

```
PING 10.0.1.2 (10.0.1.2): 56 data bytes
64 bytes from 10.0.1.2: seq=0 ttl=64 time=0.642 ms
64 bytes from 10.0.1.2: seq=1 ttl=64 time=0.671 ms
64 bytes from 10.0.1.2: seq=2 ttl=64 time=0.441 ms
64 bytes from 10.0.1.2: seq=3 ttl=64 time=0.486 ms
64 bytes from 10.0.1.2: seq=4 ttl=64 time=0.462 ms

--- 10.0.1.2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.441/0.540/0.671 ms
```

======= OLSR STATUS TEST's ========
* Advanced --> Status --> OLSR --> Routes

![eth-olsr-routes](https://f.cloud.github.com/assets/1226247/2221424/9a44670a-9a58-11e3-8410-45bb792983cf.png)

* Advanced --> Status --> OLSR --> Topology

![eth-topo](https://f.cloud.github.com/assets/1226247/2221436/bac4288a-9a58-11e3-9ca9-56a4ce2b97fb.png)

* Basic --> Status --> Mesh Visualizer

![eth-viz](https://f.cloud.github.com/assets/1226247/2221413/7c0227d2-9a58-11e3-8cb0-ea98aa80cea8.png)

If you can confirm two nodes meshing using these properties then you can safely merge this pull request into the master branch of *luci-commotion*

---
Reply to this email directly or view it on GitHub:
https://github.com/opentechinstitute/luci-commotion/pull/153#issuecomment-35650191
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-admin/attachments/20140220/78848fa9/attachment.html>


More information about the Commotion-admin mailing list