217 lines
5.0 KiB
HTML
217 lines
5.0 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Troubleshooting tips</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="Linksys Blue Box Router HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Utilities"
|
|
HREF="utilities.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Related Resources"
|
|
HREF="resources.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Linksys Blue Box Router HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="utilities.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="resources.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="ts-tips"
|
|
></A
|
|
>9. Troubleshooting tips</H1
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="catatonia"
|
|
></A
|
|
>9.1. Occasional catatonia and epilepsy</H2
|
|
><P
|
|
>Linksys boxes freeze up occasionally (once every few months) and
|
|
have to be power-cycled. Suspect this is happening if your outside
|
|
Web access suddenly stops working; ping the Linksys box to check.</P
|
|
><P
|
|
>These catatonic episodes may be related to dirty power; at least,
|
|
they seems to happen more frequently in association with electrical storms
|
|
and brownouts. If you think this has happened, just pull the power
|
|
connector out of the back and plug it back in. The Linksys should reboot
|
|
itself within 30 seconds or so.</P
|
|
><P
|
|
>There is a more severe failure mode that I've only seen once; it's
|
|
more like an epileptic seizure than catatonia, and involves strange blink
|
|
patterns on the Link, Collision, and 100Mbit diagnostic lights (the 100Mbit
|
|
light should not normally ever blink).</P
|
|
><P
|
|
>If this happens, power-cycling the Linksys won't suffice; you'll have
|
|
to hard-reset the thing. Some versions (like the BEFSR41) have a reset pin
|
|
that you poke with a paperclip end through a small hole in the front panel
|
|
labeled Reset. Some versions (like the BEFW11S4 and WRT54G) have a reset
|
|
button on the back. You have to hold these down for about thirty seconds
|
|
to hard-reset the nonvolatile RAM. This will lose your configuration
|
|
settings.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="mozillaquirks"
|
|
></A
|
|
>9.2. Mozilla interface quirks under 1.38 and earlier firmware</H2
|
|
><P
|
|
>Linksys blue boxes have a webserver embedded in their firmware.
|
|
The normal way to administer one is to point a browser at its IP
|
|
address on your network. You program the box by filling out HTML
|
|
forms.</P
|
|
><P
|
|
>This is a nice bit of design that neatly avoids having OS-specific
|
|
client software. But some older versions of the webserver firmware have a
|
|
quirk that interacts with a bug in Mozilla (at least at release 1.0.1) to
|
|
make the interface almost unusable. Fortunately, the recovery procedure is
|
|
trivial. This bug was known to be present as late as 1.40, and also
|
|
interfered with Netscape; it is absent in 1.44 and a good reason to
|
|
upgrade. We have a report that Mozilla 1.3 fails with 1.43, so whatever
|
|
change fixed the problem likely came in with 1.44.</P
|
|
><P
|
|
>The symptom you're likely to see is a broken-image icon at the
|
|
upper left hand corner of each page. The broken image is a series of
|
|
file-folder tabs for an image map. That image map is how you get to
|
|
the other web pages.</P
|
|
><P
|
|
>You can recover by right-clicking on the broken-image icon.
|
|
Select <SPAN
|
|
CLASS="QUOTE"
|
|
>"View Image"</SPAN
|
|
>, then back out. This will build the
|
|
image map correctly.</P
|
|
><P
|
|
>You will almost always have to do this on the first page,
|
|
but it often won't trigger on later page loads.</P
|
|
><P
|
|
>Here's what's going on. Mozilla tries to stream multiple
|
|
concurrent requests at the webservers it talks to in order to speed up
|
|
page loading. The dimwitted little firmware webserver in the Linksys is
|
|
only single-threaded and doesn't handle concurrent requests. So there's
|
|
a race condition. When you hit the window just right, you get an
|
|
aborted request and a broken graphic.</P
|
|
><P
|
|
>Most other browsers are immune to this problem. Konqueror
|
|
doesn't trigger it. Neither does Internet Explorer.</P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="utilities.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="resources.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Utilities</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Related Resources</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |