Re: LinuxAP FAQ v.0.3 01/Feb/2004

Remind me next week I'll give you FTP to the Web Site....

--keith

PS... Got a 2.4.24 almost there for soekris.  Not sure about the back
port, but I'm using squashfs now.

Bruno Lopes F. Cabral wrote:
> LinuxAP Frequent Asked Questions V.0.3 01/02/04
> Copyright (c)-2003-2004 by Bruno Lopes F. Cabral
> 
> License
> 
>     Permission is granted to copy, distribute and/or modify this
>     document under the terms of the GNU Free Documentation License,
>     as published by the Free Software Foundation; either version 1.1,
>     or (at your option) any later version. A copy of the license is
>     included at: http://www.gnu.org/licenses/fdl.html
> 
>     This FAQ is distributed in the hope that it will be useful,
>     but WITHOUT ANY WARRANTY; without even the implied warranty of
>     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
>     General Public License for more details.
> 
>     For more information about licenses, see the GNU project
>     (http://www.gnu.org) and the OpenSource Initiative
>     (http://www.opensource.org).
> 
> 1. Questions about this FAQ
> 
> 1.1 Who is responsible for this FAQ?
> 
>     Bruno Lopes F. Cabral <[email protected]>
> 
> 1.2 What is the purpose of this FAQ?
> 
>     To help LinuxAP users to install and use the system and
>     aid to solve the more common issues.
> 
> 1.3 Where can I get the latest copy of this FAQ?
> 
>     FIXME: Soon to be included
> 
> 2. Basics
> 
> 2.1 What is LinuxAP?
> 
>     LinuxAP is a rework made by Keith Smith on OpenAP source code.
>     Original OpenAP is at http://opensource.instant802.com
> 
>     LinuxAP was heavily modified to be a complete linux router
>     distribution, with NAT, DHCP server, web/telnet configuration etc.
> 
> 2.2 Why do I need LinuxAP?
> 
>     "Mainly for fun."
> 
>     Another reasons would be the need of a s linux distribution,
>     with small footprint, easy to use yet powerfull.
> 
> 2.3 Which hardware do LinuxAP runs on?
> 
>     Current version runs on Eumitcomm WL11000 boards (i.e. USR2450)
>     or soekris.com or PC boxes (like mini-itx or micro-atx).
>     It also needs a prism2-based wireless card for AP server mode.
> 
> 2.4 Who contributed to LinuxAP?
> 
>     Keith Smith, Glenn Engel, Bruno Lopes F. Cabral, may be others.
> 
> 3. Getting & Installing
> 
> 3.1 Where can I find LinuxAP?
> 
>     You can get the latest version from:
>     http://linuxap.ksmith.com
> 
> 3.2 How do I install?
> 
>     Compile your own or make use of a pre-built image. The procedure
>     for reflashing using a pre-built image is detailed here:
> 
> 
> http://lists.instant802.com/pipermail/openap-dev/2002-August/001113.html
> 
> 3.3 What is running on it?
> 
>     Current version has:
>     - http server for configuration
>     - telnet server for configuration
>     - dhcp server / masquerading
>     - NAT capabilities (or soft of, i.e. no H323 or IRC DCC support
>     while NAT'ing)
> 
> 3.4 How do I configure LinuxAP?
> 
>     You can edit every feature of LinuxAP through it's shell,
>     either via console or telnet.  Here is a sample configuration
>     session:
> 
>     # cd /etc/rw/
>     # ls
>     # vi config-file-name
>     # save_config
>     # reboot
> 
>     To use a browser to config LinuxAP, point it to http://10.0.1.1
>     (the default LAN address, but default image also try to
>     discover it's own address through DHCP client mode)
> 
> 3.5. How do I change the telnet password?
> 
>     If your version already has telnetd -l /bin/login,
>     through the shell, edit the config file /etc/rw/passwd
> 
>     root:cryptedpassword:0:0:root:/
> 
>     Just to be sure, test the new password with a remote telnet
>     connection to your running LinuxAP _before_ saving the config
>     with
> 
>     # save_config
> 
>     If not, well, it is not so difficult to add tinylogin to LinuxAP.
> 
> 3.6. Explain to me the telnetd.hosts file
> 
>     It is used to enable the IP addresses or networks that will be
>     able to telnet to your running LinuxAP. I.e.
> 
>     10.0.1.1
> 
>     will allow 10.0.1.1, 10.0.1.10 e 10.0.1.100 to telnet in.
>     If you wan't to allow just, 10.0.1.1, just add an ending "."
>     to the IP address desired, as
> 
>     10.0.1.1.
> 
>     (this is a "feature" that MAY be corrected in the future)
> 
> 3.7. Explain to me the httpd.conf file
> 
>     It is used to enable the IP addresses or networks that will be
>     able to telnet to your running LinuxAP, or to setup password
>     level access. I.e.
> 
>     ip:10.0.1.1
> 
>     will allow 10.0.1.1, 10.0.1.10 e 10.0.1.100 to access the web server.
>     If you wan't to allow just, 10.0.1.1, just add an ending "."
>     to the IP address desired, as
> 
>     10.0.1.1.
> 
>     (this is a "feature" that MAY be corrected in the future)
> 
>     To put a password protected area (i.e. for setup), add a line like:
> 
>     /cgi-bin:user:password
> 
>     The password is unencrypted.
> 
> 3.8. What are the runlevels?
> 
>     LinuxAP has the following working runlevels:
> 
>     - 1 : Used to reflash the unit
>     - 2 (Managed): The wireless card will be an AP station
>     - 3 (Master) : Wireless and local network are bridge as an AP
>     - 4 (Router) : AP on the wireless side, router on the network side
>     - 5 : This mode needs to be tweaked by hand by YOU!
>     - 6 : Used to first flash the unit (by boot from SRAM card)
> 
>     Runlevel 3 only needs one IP address, while 2 and 4 use
>     two, one for the wireless card, another for the ethernet card.
>     IP Forwarding is activated by default on runlevels 2 and 4.
> 
> 4. Advanced
> 
> 4.1 How do I make a bridge?
> 
>     Most APs have proprietary bridging modes. LinuxAP also
>     behaves that way! To make two running LinuxAPs to act as one,
>     configure both with:
> 
>     - same ESSID string
>     - same channel number (1 to 11)
>     - same wep key (if using wep)
>     - runlevel 3 on both
>     - NWDS=1 (count the number of LinuxAPs that will communicate
>     with this one and put that number here)
> 
>     To see how things are going, use the following commands:
> 
>     # cat /proc/net/prism2/wlan0/wds
>     # brctl showmacs br0
> 
>     This post on list archive also talks about bridging:
> 
> http://lists.instant802.com/pipermail/openap-dev/2002-September/001315.h
> tml
> 
> 4.2 How do I know who is on-line on modes 3 & 4?
> 
>     # ls /proc/net/prism2/wlan0/0*
> 
> 4.3 How do I get the signal of a station or AP?
> 
>     If your version have iwspy, you can use it. If not, try
> 
>     # cat /proc/net/prism2/wlan0/0stationmac
> 
>     (search for signal=) or
> 
>     # cat /proc/net/wireless
> 
>     for the signal from the AP you're associated with.
> 
> 4.4 How do I choose the mac addresses that can associate with LinuxAP?
> 
>     Soon to be included
> 
> 4.5 How do I kick out some stations?
> 
>     Soon to be included
> 
> 4.6 Any recomendation on pccard firmwares?
> 
>     To know the station firmware you're using, check the
>     log just after the hostap_cs or hostap_pci load for
>     the string STA=
> 
>     The best station firmwares are 1.3.5 and from 1.4.9 on
> 
>     There are utilities to help updating the card firmware,
>     but it's known to be easier to do it through the own
>     card setup wizard on MS-Windows 2000/XP.
> 
>     Better ask on the hostap list on this!!
> 
> 5. Licensing
> 
> 5.1 What license is used for LinuxAP?
> 
>     Each package has their own preferred license. Generally licenses
>     are either GNU or BSD in nature.
> 
>     A BSD style license essentially states that no warranty is given,
>     the core may be distributed in source or binary form and the
>     authors copyright must be acknowledged.
> 
>     The GNU Public License (GPL) adds the important condition that
>     all modifications must be distributed under the GPL. When you
>     release something under the GPL, no-one can take away your right
>     to later access a modified version of it. Conversely, if you use
>     a GPLed item, you MUST distribute all information about it and
>     NOT prevent others from redistributing or modifying it. Stating
>     it as an oversimplification: you cannot keep secrets unless you
>     want your butt sued.
> 
>     For more information about licenses, see the GNU project
>     (http://www.gnu.org) and the OpenSource Initiative
>     (http://www.opensource.org).
> 
> History
> 
>     V.0.3 01/02/04 By Bruno Lopes F. Cabral <bruno at openline.com.br>
>     - Modified to talk only about Eumitcomm based LinuxAP
> 
>     V.0.2 30/04/03 By Bruno Lopes F. Cabral <bruno at openline.com.br>
>     - Updated license text, changed default language to english
> 
>     V.0.1 14/04/03 By Bruno Lopes F. Cabral <bruno at openline.com.br>
>     - Minor updates
> 
>     V.0.0 31/01/03 By Bruno Lopes F. Cabral <bruno at openline.com.br>
>     - Initial version
> 
> - EOF -
> 
> _______________________________________________
> LinuxAP-dev mailing list
> [email protected]
> http://linuxAP.ksmith.com/mailman/listinfo/linuxap-dev