<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Sean,<br>
<br>
see comments in-line below.<br>
<br>
On 02/16/13 20:43, Sean McIntyre wrote:<br>
</div>
<blockquote
cite="mid:CAM_NihTKUuZE2ocWsBpVsR+1UiXC9p4m9vzGqdG-c6Us8yaHKA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Hey list,<br>
<br>
</div>
<div>I went out yesterday to set up some NanoStation M2's but
overall failed wholly. Wanted to report back on the
experience for everybody's benefit. I'm interested to hear
if I did anything wrong so I can adjust my techniques for
next time.<br>
<br>
</div>
<div>A major usability field ops feature I would love is the
NanoStation M2 reset button to do a "manufacturer reset" on
the firmware. That would have saved me some headaches. Let
me know if it actually does that and I'm doing it wrong.
(Also let me know if I just volunteered to implement this.
;))<br>
</div>
</div>
</div>
</blockquote>
<br>
So would we, this is on the hardware level and sadly out of our code
range. OpenWRT has a hard reset into the default OpenWRT, but until
you have loaded OpenWRT this functionality is not baked into the
router.<br>
<br>
<blockquote
cite="mid:CAM_NihTKUuZE2ocWsBpVsR+1UiXC9p4m9vzGqdG-c6Us8yaHKA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
</div>
<div><br>
</div>
<div>Okay, here we go:<br>
</div>
<div><br>
</div>
<div>Router #1 issue: Could not log in to web interface /
unknown password<br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
The OpenWRT initial flash does not have a password. Did you try
logging in without entering a password? That is the only way to get
past that interface before you have set a password. You can also set
the password by logging in over telnet.<br>
<br>
<blockquote
cite="mid:CAM_NihTKUuZE2ocWsBpVsR+1UiXC9p4m9vzGqdG-c6Us8yaHKA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Version: "Powered by LuCI Trunk (trunk+svn8676)
CommotionWRT Pre-Release PR3"<br>
<br>
</div>
<div>It could be a case of forgetfulness, but I became unable
access this router via the web interface. The password
prompt always failed, despite trying every password I know.
;)<br>
</div>
<div><br>
</div>
<div>So time to reset! But holding the master reset button
(powered on) doesn't seem to have any effect, the
configuration doesn't wipe / allow me to set a new password.
I reflashed it.<br>
<br>
</div>
</div>
</div>
</blockquote>
<br>
The reset button simply re-boots a router. It can also be used to
put the router into tftp mode or with the right combination into the
default OpenWRT image. You will have to look at the openwrt site for
the instructions for various routers.<br>
<br>
<blockquote
cite="mid:CAM_NihTKUuZE2ocWsBpVsR+1UiXC9p4m9vzGqdG-c6Us8yaHKA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>This one has been left outdoors for the last month.<br>
<br>
</div>
<div>Luckily I brought a second router with me, so I swapped
the device, but...<br>
</div>
<div><br>
</div>
<div>Router #2 issue: Adding bridge interface between mesh and
LAN interfaces made device inaccessible over LAN interface<br>
</div>
<div><br>
Version (same): "Powered by LuCI Trunk (trunk+svn8676)
CommotionWRT Pre-Release PR3"<br>
<br>
</div>
<div>This could also be operator error, but here's the
scenario:<br>
<br>
</div>
<div>1. Nanostation M2 (call it "A") setup with stock
Commotion on my roof<br>
</div>
<div>2. Nanostation M2 (call it "B") setup with stock
Commotion on target roof<br>
</div>
<div>3. Station A was connected to my home router with an
Internet uplink<br>
</div>
<div>4. Station B was successfully connected to Internet from
Station A via the mesh interface, and its LAN port was
connected to an Ethernet hub (not router)<br>
</div>
<div>5. My computer (OS X) was connected to the Ethernet hub
via Ethernet cable and could access the LAN interface
(192.168.1.x). Set up a default route on my computer to send
upstream packets to Station B, but the default setup didn't
pass packets from my laptop, through the hub, through
Station B, to Station A (and to the Internet)<br>
<br>
</div>
<div>My next move was to set up a new bridge interface over
Station B's LAN interface and mesh interface in hopes this
would pass along the packets. Saved, waited, and could no
longer connect to Station B's LAN interface.<br>
<br>
</div>
<div>Tried to reset device with reset button and revert back
to original config, but like before, this did not reset the
configuration.<br>
<br>
</div>
<div>Had to give up, came home with the device and saw that
the device was accessible over the WiFi interface and
successfully logged in. So that makes me think that it could
be my error, would love to know if so.<br>
</div>
</div>
</div>
</blockquote>
<br>
Will is going to send you another e-mail with some questions on this
specific setup in a few minutes.<br>
<br>
<blockquote
cite="mid:CAM_NihTKUuZE2ocWsBpVsR+1UiXC9p4m9vzGqdG-c6Us8yaHKA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
</div>
<div><br>
</div>
<div>Anyways, looking forward to hearing back!<br>
</div>
<div><br>
</div>
Thanks,<br>
</div>
<div><br>
Sean<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Commotion-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a>
<a class="moz-txt-link-freetext" href="https://lists.chambana.net/mailman/listinfo/commotion-dev">https://lists.chambana.net/mailman/listinfo/commotion-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>