<div class="gmail_quote">On May 4, 2014 10:15 AM, "Bart Kus" <<a href="mailto:me@bartk.us">me@bartk.us</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>There's some confusion here, so allow
me to clear it up.<br>
<br>
What Mike's talking about is a utility called Netinstall
(<a href="http://wiki.mikrotik.com/wiki/Manual:Netinstall" target="_blank">http://wiki.mikrotik.com/wiki/Manual:Netinstall</a>) that allows
recovery of truly crashed devices. "Truly crashed" means that
RouterOS is not booting. It doesn't scan for devices, it just
serves as a PXE server, and it's up to the devices to request a
PXE boot. The code that controls PXE booting is in a different
part of flash than the RouterOS itself, and does not depend on
RouterOS.<br>
<br>
Winbox can indeed use a layer 2 protocol (called mac-winbox), and
it can also use IP (layer 3). Which protocol it uses depends on
the address (MAC vs IP) you tell it to connect to. However, it
doesn't provide the PXE flashing capability. If RouterOS is truly
crashed, Winbox won't work.<br>
<br>
Another layer 2 protocol is mac-telnet. This is configured as a
separate service from mac-winbox on RouterOS. Recently we had a
case where mac-telnet was inaccessible (was not configured to
listen on any interfaces) but mac-winbox was set to its default of
listening on all interfaces. We were able to regain control of
the router by using the alternative layer 2 protocol.<br>
<br>
In Dean's case, we don't know what he means by "dead". It could
be that the ethernet link is up and IP just stopped working. He
can try the 2 MAC protocols. If those fail, he can try the
Netinstall recovery.<br>
<br>
--Bart<br>
<br>
<br>
On 5/4/2014 9:40 AM, Kenny Richards wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">The
Winbox application allows the Layer2 connection....</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
On Sun, May 4, 2014 at 8:46 AM, Mike Culver <span dir="ltr"><<a href="mailto:mculver@extencia.com" target="_blank">mculver@extencia.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can't find the cheat sheet; however I also thought that I
bricked my unit. Was able to connect to it and re-flash.; if
memory serves me correctly it was with software that scanned
for a Mac address and connected via Layer 2.<br>
<br>
Hopefully someone here remembers how to do this, or better
yet can point you to instructions on the manufacturer's
website.<br>
<br>
Mike<br>
WA9QHP<br>
<div>
<div><br>
-----Original Message-----<br>
From: PSDR [mailto:<a href="mailto:psdr-bounces@hamwan.org" target="_blank">psdr-bounces@hamwan.org</a>]
On Behalf Of Dean Gibson AE7Q<br>
Sent: Sunday, May 4, 2014 1:44 AM<br>
To: Puget Sound Data Ring<br>
Subject: Re: [HamWAN PSDR] Metal 5SHPn firmware 6.12 is
current (addendum)<br>
<br>
Well, this did not end well.<br>
<br>
As you can see from Nigel's SNMP data for my site, right
after I installed firmware v6.12 at 9pm, my wireless
signal strength dropped by about 10dB. In other
respects, everything seems to work, and I at first I
thought perhaps it was the rain. However, we've had
rain on and off all day, and as you can see from Nigel's
site, the signal strength was fairly uniform until the
very sudden drop at 9pm.<br>
<br>
Reboots did not solve the problem, so I reverted to
v6.10 using the "downgrade" command line option. That
did not improve the signal strength, so I upgraded back
to v6.12. I checked all the configuration settings, and
everything looked normal. Data transfer through the
radio worked fine.<br>
<br>
So, I decided to reset the configuration (using the
command line) to make sure nothing had changed. I'd
done that a couple times a month ago, with no ill
effects.<br>
<br>
However, this time it appears to have "bricked" the
radio.<br>
<br>
It draws about 160ma (about the value from a week ago,
when I first measured it). There is no light on the
side of the unit, and the Ethernet port is dead.<br>
<br>
I'm going to bed. Sunday morning I will go out onto the
roof and attempt to reset the unit via the pinhole.<br>
<br>
I hope this is not indicative of MikroTik quality. I'm
glad the thing is not up on a tower ...<br>
<br>
_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
<br>
_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
PSDR mailing list
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
<br></blockquote></div>