Changeset 3e916e1 in freewrt for docs


Ignore:
Timestamp:
Jan 3, 2007, 10:22:04 AM (19 years ago)
Author:
Phil Sutter <n0-1@…>
Branches:
freewrt_1_0, freewrt_2_0
Children:
dab34c82
Parents:
e91877d
Message:

Added guide for flashing via web iface of original firmware

git-svn-id: svn://www.freewrt.org/branches/freewrt_1_0@1396 afb5a338-a214-0410-bd46-81f09a774fd1

Location:
docs/handbook/user
Files:
3 added
1 edited

Legend:

Unmodified
Added
Removed
  • docs/handbook/user/00-allinone.tex

    re91877d r3e916e1  
    319319
    320320\subsection{Web Interface Method}
    321 %TODO: may be filled in by someone who has done this before
     321The following text describes how to use the original firmware's web interface
     322to flash FreeWRT. The object of demonstration is an Asus WL500gP, but this
     323guide should fit more or less fine for other systems, too.
     324
     325There are some things that you should have done previously:
     326\begin{itemize}
     327\item a firmware image has to be built (matching the used hardware, of course)
     328\item the router has to be powered on
     329\item your computer needs to be connected to one of the LAN ports (using IP
     330address 192.168.1.2)
     331\end{itemize}
     332
     333\parbox{17em}{
     334After preparation is complete, open your favourite browser and type
     335\texttt{192.168.1.1} into the address bar. You should reach the web interface's
     336startup page:
     337}\hfill\parbox{20em}{\includegraphics[width=20em]{pics/asus-startup.png}} \\ [1em]
     338\parbox{17em}{
     339Then click \textit{System Setup}:
     340}\hfill\parbox{20em}{\includegraphics[width=20em]{pics/asus-system_setup.png}} \\ [1em]
     341\parbox{17em}{
     342Then click \textit{Firmware Upgrade}, and enter the name of your firmware image
     343into the appropriate field:
     344}\hfill\parbox{20em}{\includegraphics[width=20em]{pics/asus-fw_upgrade.png}} \\ [1em]
     345Finally click \textit{Upload}. As the whole process of writing the image to
     346flash and rebooting (don't forget that it creates ssh hostkeys on first boot)
     347takes quite long, better go and get coffee.
     348
     349When everything went good, you can login using ssh.
    322350
    323351\subsection{\texttt{mtd} -- The Flash Utility}
     352For this method to work, you need to copy the file containing the firmware
     353image to the router, preferably into /tmp (the tmpfs should be big enough to
     354hold the full image). Then the image is written to flash using
     355\texttt{mtd}, optionally giving additional options (see below).
     356
    324357The \texttt{mtd} utility was written with simplicity and code size in mind.
    325358It's features were derived from the mtd-utils, %TODO: insert \ref to homepage
     
    827860Same semantics as above.
    828861
     862\section{Troubleshooting}
     863
     864\subsection{Failsafe Mode}
     865
     866Failsafe mode is very useful if you misconfigured your embedded system,
     867so that you can not access it anymore. E.g. if you accidentially disabled
     868secure shell or misconfigured the firewall, so that you can not login any
     869more.
     870
     871\subsubsection{How It Works}
     872
     873To get FreeWRT into failsafe mode you need physical access to the device and
     874the failsafe utility. The failsafe utility is built inside our ADK and
     875is available in the directory bin/ after a successful build.
     876
     877If you just want to compile the tool and not a complete firmware image,
     878use following command:
     879
     880\begin{Verbatim}
     881$ make subdir=tools/failsafe install
     882\end{Verbatim}
     883
     884For some operating systems we provide ready to go binaries of failsafe.
     885Take a look at http://www.freewrt.org/downloads/tools/failsafe
     886% TODO: \ref fuer link
     887
     888The tool just opens a network socket and waits for a special UDP packet
     889from the embedded device. FreeWRT sends the UDP packet via the first
     890recognized network interface (eth0).
     891
     892\subsubsection{Enabling Failsafe Mode}
     893
     894Connect your computer to the embedded system via direct or crossed network
     895cable. Use the failsafe port (in most cases one of the LAN ports),
     896see the device specific page for the exact network port.
     897
     898Configure your network interface to the IP address 192.168.1.2 with network
     899mask 255.255.255.0. Now start the failsafe utility on your computer.
     900
     901\begin{Verbatim}
     902$ ./failsafe
     903\end{Verbatim}
     904
     905After that power on your embedded system and wait for the following message in
     906your failsafe application running on your computer:
     907
     908\begin{Verbatim}
     909Press reset now to enter Failsafe!
     910\end{Verbatim}
     911
     912As soon as this message is displayed you should push the reset button of
     913your embedded system. You have 2 seconds time to push the button. If you
     914successfully enabled the failsafe mode, following message will be displayed:
     915
     916\begin{Verbatim}
     917Entering Failsafe!
     918\end{Verbatim}
     919
     920Now you should be able to login to your embedded system via a telnet
     921application. Just use:
     922
     923\begin{Verbatim}
     924$ telnet 192.168.1.1
     925\end{Verbatim}
     926
     927\subsubsection{Repairing Your FreeWRT Configuration}
     928
     929If you want to repair your configuration, you first need to
     930mount the root filesystem via:
     931
     932\begin{Verbatim}
     933# mount_root
     934\end{Verbatim}
     935
     936After that you need to enable the FreeWRT configuration filesystem:
     937
     938\begin{Verbatim}
     939# fwcf setup
     940\end{Verbatim}
     941
     942Now you can change files in /etc and repair your broken configuration.
     943Do not forget to commit your changes afterwards.
     944
     945\begin{Verbatim}
     946# fwcf commit
     947\end{Verbatim}
     948
     949If you want to start over with the default /etc directory, just remove the fwcf
     950partition content with following command:
     951
     952\begin{Verbatim}
     953mtd erase fwcf
     954\end{Verbatim}
     955
     956You can either use "reboot -f" or "-r" for mtd to reboot the system.
     957
Note: See TracChangeset for help on using the changeset viewer.