<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<p><b style="font-weight:normal;"
id="docs-internal-guid-4f4ac7a7-7d5d-4744-af54-546856b273bf">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Here's
an initial reportback from the AMC conference. A more
detailed report will likely follow. Thanks Andy for the help
on this!<b><br>
</b></span></p>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><br>
tl;dr: it had a rough start, but <a
href="https://docs.google.com/file/d/0B0hY7epZlXFaYjhaRVBPZGpxeUU/edit?usp=sharing">turned
out awesome!</a> <br>
</span></p>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><br>
</span></p>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">-Dan<br>
</span></p>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><br>
----<br>
</span></p>
</b></p>
<p><b style="font-weight:normal;"
id="docs-internal-guid-4f4ac7a7-7d5d-4744-af54-546856b273bf">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span></p>
</b></p>
<p><b style="font-weight:normal;"
id="docs-internal-guid-4f4ac7a7-7d5d-4744-af54-546856b273bf">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span></p>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">At
the 2013 Allied Media Conference (AMC), the Open Technology
Institute partnered with local Detroit Digital Stewards and
Red Hook Digital Stewards to construct a conference-wide
mesh network. The purpose was to provide network and
Internet access to the conference attendees, provide an
additional training opportunity for the Detroit and Red Hook
Digital Stewards, and serve as a testing opportunity for
Commotion DR1.1.</span></p>
</b></p>
<b style="font-weight:normal;"
id="docs-internal-guid-4f4ac7a7-7d5d-4744-af54-546856b273bf"><br>
<span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:bold;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Process</span></p>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">The
construction process for the network was reminiscent of the
process from the previous AMC, as detailed in the </span><a
href="https://docs.google.com/document/d/1rf8VETPlJwbgM9p9cU2evIPPjwqOdhP_S9xlsxdGFFo/edit?usp=sharing"
style="text-decoration:none;"><span style="font-size: 16px;
font-family: 'Times New Roman'; color: rgb(17, 85, 204);
background-color: transparent; font-weight: normal;
font-style: normal; font-variant: normal; vertical-align:
baseline; white-space: pre-wrap;">AMC 2012 Commotion
Deployment Report</span></a><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">.</span></p>
<ul style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:disc;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Detroit
Digital Stewards spent Wednesday afternoon from around 3PM
until 5PM installing Commotion DR1.1 on PicoStation M2
(PS) and NanoStation M2 (NS) units.</span></p>
</li>
<ul style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:circle;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Basic
information was recorded for each node - it’s name, mesh
IP address, and label.</span></p>
</li>
<li dir="ltr"
style="list-style-type:circle;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Several
customizations were made - changing the Administrator
password, changing the splash page timeout to 24 hours,
updating the splash text, and changing the node name and
SSID to match it’s location. Nodes were left “stock”
otherwise.</span></p>
</li>
</ul>
<li dir="ltr"
style="list-style-type:disc;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Installations
were conducted on Thursday, the day prior to the official
start of the conference sessions. This consisted of a tour
of the sites to be installed by the team, which included
OTI staff and Detroit Digital Stewards. In the afternoon
the team was expanded as the Red Hook Digital Stewards
arrived.</span></p>
</li>
<ul style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:circle;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Four
nodes were installed in McGregor conference center, two
in the Education building, two in the Arts building, two
in the Hilberry Student Center, and one in the
Auditorium.</span></p>
</li>
</ul>
<li dir="ltr"
style="list-style-type:disc;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Jonathan
set up a Tidepools instance for the conference that
included a map, session browser, and twitter feed. It was
added to the nodes' application portal. It received
excellent feedback!</span></p>
</li>
</ul>
<br>
<span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span><br>
<span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:bold;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Challenges
Discovered</span></p>
<br>
<span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Several
challenges were discovered through the process of building the
network.</span></p>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Changing
a node's WiFi channel in the presence of other Ad-Hoc
nodes </span><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:bold;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">does
not work</span><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">This
was discovered by Will Hawkins and Dan Staples while
preparing for the AMC.</span></p>
</li>
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">The
problem occurs if you have two nodes meshing on channel
A, and then try to change one of them to channel B, it
will go to channel B and then right back to channel A a
few seconds later. This is due to the way adhoc cells
try to converge. We were unable to coerce iw into
staying on a channel when upping the adhoc interface.
This is unsolved.</span></p>
</li>
</ol>
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">We
found immediately that the nodes in McGregor, which were
all connected via wire to the WSU LAN, were not getting
DHCP leases from the gateway.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">This
issue was solved by increasing the DHCP timeout in the
/lib/netifd/proto/commotion.sh script. We had to
increase it to 60 seconds in order to get DHCP leases
from the WSU gateway. A feature has been added in the
LuCI interface to set the DHCP timeout .</span></p>
</li>
</ol>
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">The
first major issue discovered during the conference was
high packet loss and long ping times to the access points.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">This
was first seen when connecting to any of the access
points in the McGregor building, but was not seen in the
other buildings.</span></p>
</li>
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">At
first we thought this was a problem of RF interference.
We first tried turning down the TX power on all of the
nodes, and sometimes even turning off nodes. This would
help for a short period of time, but eventually the
problems returned.</span></p>
</li>
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Finally,
we turned off the wireless adhoc interfaces on all the
McGregor nodes, put all their APs on different channels,
and had them mesh over Ethernet. This solved the
latency/packet loss issues within McGregor.</span></p>
</li>
</ol>
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Another
major problem was establishing good mesh wireless links
between the buildings. This proved to be an extremely
challenging problem, and consumed several hours of
troubleshooting.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">The
initial task was to get two NanoStations in McGregor to
wirelessly mesh with Picostations in the adjacent
buildings. The NanoStations were aimed from second floor
windows towards the adjacent buildings. The signal
strength at the neighboring buildings was marginal or
nonexistent. This was first thought to be an aiming
problem, or interference between the nodes.</span></p>
</li>
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">To
combat the possible interference or RF saturation, one
of the NS units was powered off. We then optimized the
output power of the remaining NS and PS units nearby, so
that each would show a received signal strength of
around -40 to -50 dBm (very strong). We then replaced
the NanoStation with a PicoStation, thinking DR1 might
have compatibility problems with the NS units, or issues
with MIMO streams. After this change and the TX power
optimization, the packet loss and ping times (~5
seconds) were still excessively high.</span></p>
</li>
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Andy
Gunn determined that the building's windows through
which we were trying to mesh were shielded, and were
attenuating the RF signal. To verify, a NanoStation was
extended to the outside of the building, and the link
immediately improved. One way to diagnose this
consistently was discussed: look at your cell phone's
reception as you go from outside the building to inside;
if reception drops significantly, even next to a window,
the windows are likely shielded.</span></p>
</li>
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">The
underlying problem was linked to the NS or PS node that
was meshing via Ethernet and Ad-Hoc wireless to bridge
from McGregor to the adjacent buildings. After meshing
on Ethernet was disabled, packet loss and latency
disappeared. Will Hawkins suggested the olsrd-dnssd
plugin was also causing problems - once that was
disabled on </span><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:bold;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">all</span><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">
the nodes, meshing over Ethernet was re-enabled and
everything worked fine. It is still unclear what exactly
about the dnssd plugin caused the problems.</span></p>
</li>
</ol>
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Since
the McGregor nodes were connected to a LAN, the default
firewall rules blocked incoming connections to their web
interface from the LAN.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Firewall
exceptions to allow WAN connections to port 80 needed to
be manually added in order to access the nodes' web
interfaces from the WSU LAN. Since ssh connections from
the WAN zone are allowed by default, it is probably no
less secure to allow http connections from the WAN zone.
It is worth considering changing this in the default
firewall config.</span></p>
</li>
</ol>
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">It
was not possible to disable the AP, but leave the wireless
ad-hoc interface in place. However, disabling the Ad-Hoc
interface while leaving the AP up does work.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">This
is due to when the AP is disabled from the web
interface, it adds a 'disabled' flag to the AP in
/etc/config/wireless, then restarts the wifi interfaces.
This has the effect of taking down wlan0-1 (the Ad-Hoc
interface) and leaving wlan0 (the AP), the opposite of
the intended effect. It also has the effect of creating
an invalid olsrd config (via commotiond), and the wifi
interfaces are displayed incorrectly in the web
interface. Unresolved.</span></p>
</li>
</ol>
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">One
of the nodes would spew tons of duplicate packets when
pinged.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">This
may have been a hardware malfunction. It was replaced
with a newly flashed PS, and the problem disappeared.</span></p>
</li>
</ol>
<li dir="ltr"
style="list-style-type:decimal;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Some
people were confused by the splash page.</span></p>
</li>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:lower-alpha;font-size:16px;font-family:'Times
New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">I
got some feedback from some of the more tech-savvy folks
at the AMC that the port 80-only captive portal was
potentially confusing, especially if a user has an
SSL-encrypted homepage in their browser.</span></p>
</li>
</ol>
</ol>
<br>
<span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span><br>
<span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span>
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:bold;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Recommendations
for future Development</span></p>
<br>
<span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></span>
<ul style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Fix
the adhoc wifi channel hopping issue</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Implement
dynamic gain control so nodes don't drown each other out</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Increase
default DHCP timeout and add option to change it in the
web interface (these fixes have already been submitted)</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Check
for shielded windows when doing a deployment</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Refactor
the olsrd-dnssd plugin</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Add
firewall rule to allow port 80 connections from the WAN
zone</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Fix
the bug preventing disabling the AP and leaving adhoc.</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;">
<p dir="ltr"
style="line-height:1;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Captive
portal port 443 traffic with a self-signed cert by
default.</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc;font-size:13px;font-family:Verdana;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;margin-left:
-24px;"><span style="font-size:16px;font-family:'Times New
Roman';color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Setup
network monitoring before doing a deployment. It would have
been immensely useful to know how many folks used the
MagicNet, and if they used the local apps at all. It would
also have been useful to solicit feedback on the network and
what issues the users ran into.</span></li>
</ul>
</b>
<pre class="moz-signature" cols="72">--
Dan Staples
Open Technology Institute
<a class="moz-txt-link-freetext" href="https://commotionwireless.net">https://commotionwireless.net</a></pre>
</body>
</html>