Q: How can I access my router?

A: Settings are retrieved from nvram, lan and wireless should be as you
   last configured them, wan is currently hardcoded as dhcp. You may
   access the router via telnet. If the startup scripts were unable
   to find your previous settings the lan will be 192.168.1.1

- - - 

Q: Where is the configuration webpage?

A: OpenWrt is a core, a minimal distribution with addon packages.
   OpenWrt's cramfs filesystem contains a minimal set of applications
   to configure the router to an opperational state, this maximizes the
   resources available to user packages which will be stored on the jffs2
   partition. See next question.

- - -

Q: Where is the jffs2 partition / how can I boot off jffs2?

A: Upon bootup the router will run /etc.ro/boot and attempt to mount the
   jffs2 partition as /usr/local. If this is your first time there will
   be no jffs2 partition and the router will drop into failsafe mode and
   boot using /etc.ro/inittab and /etc.ro/rcS; to create a jffs2 partition
   run the command "firstboot" which will create the jffs2 partition and
   mount it as /usr/local. You may now copy /etc.ro/inittab and /etc.ro/rcS
   to /etc which is linked to the jffs2 partition and customize them.

- - -

Q: I screwed up my jffs2 partition, how can I boot failsafe?

A: If your jffs2 partition lacks a /etc/inittab or you hold down the
   reset button upon bootup the router will boot into failsafe mode.

- - -

Q: How do I upload a new firmware or revert to factory firmware?

A: There are two ways:

    #1 (recommended)
    Set boot_wait, reboot and send code.bin to pmon's tftp server

    #2
    upload the linux.trx file to the router and issue the command
    mtd write linux.trx linux

- - -

Q: How do I set boot_wait?

A: you need to execute the following two commands
   /usr/sbin/nvram set boot_wait=on
   /usr/sbin/nvram commit

   If you do not have commandline access use the ping.asp bug described
   on the seattlewireless wiki: (see 19.54)
   
   http://seattlewireless.net/index.cgi/LinksysWrt54g

   (We highly recommend reading the entire page)

- - -

Q: Where can I find packages?

A: OpenWrt is still in beta, packages will be posted to sourceforge
   as they become available. Developers wishing to submit packages
   should visit #wrt54g on irc.freenode.net or email us on sourceforge
   (email links provided on sourceforge)
   
- - -

Q: Why use telnet, why not ssh?

A:  The goal with OpenWrt is to provide the minimal sized distribution
    required to start the router and operate in failsafe modes.  The
    telnet daemon is an integral part of busybox, and is enough to get
    going.  The telnet daemon does not bind to the public port, only to
    the internal network.  If your internal network is not secure enough
    to allow initial configuration via telnet, you have larger scale problems.
    Feel free to create an rpm with an installable sshd added to the jffs
    partition.
    
- - -

Q:  How many times can I write to the flash before it dies?

A:  The jffs2 file system includes wear levelling to address the issues of
    lifetime on flash cells.  The flash chip contained in the Version 1.0
    WRT54G hardware is rated at minimum 1 million writes per cell.  If you
    are doing something silly like writing logs to the flash partition, you
    will wear out the flash in short order.  If you are just doing normal
    updates, this should be a complete non issue over the useful life of the
    unit, the flash will outlive the IPV4 protocol.  The million write cycles
    will last approximately 10 years if you are doing an update every 5 minutes,
    assuming no wear levelling.  Accounting for wear levelling, the flash will
    likely outlive the protocols on which it is based.
    
- - -

Q:  I was using WPA and my wireless connection is broken since I changed to OpenWrt.

A:  OpenWrt doesn't support WPA out of the box. There will be a package for it.
    Until that, You can use WEP only. However, You have to change a few nvram
    variables:

    nvram set wl_wep=wep
    nvram set wl_auth_mode=disabled
    nvram set security_mode=disabled

    and of course, don't forget the 'nvram commit', too.