VERY OBSOLETE linux-wlan-ng master repository
Go to file
mark d4484f3de0 Added "unhandled" messages for the info frames we're doing nothing with. 2000-07-02 15:20:04 +00:00
doc Updated the information to match the changes in Configure and such. 2000-04-05 03:36:30 +00:00
etc Added Brian Denheyer's patch. 2000-07-01 14:43:46 +00:00
man Added or refreshed the license and copyright statements at the top of 2000-02-08 03:35:44 +00:00
src Added "unhandled" messages for the info frames we're doing nothing with. 2000-07-02 15:20:04 +00:00
CHANGES Initial checkin. 2000-04-05 03:31:38 +00:00
COPYING Intial add 2000-02-07 19:25:37 +00:00
Configure Updates for kernel based pcmcia. 2000-06-15 17:17:01 +00:00
LICENSE Initial add of the MPL version 1.1. 2000-02-07 19:26:25 +00:00
Makefile Fixes for some makefiles. Added sash to initrd flist. 2000-05-17 19:27:19 +00:00
README Removed a version dependency. 2000-04-05 03:59:35 +00:00
TODO Updated some documentation for the 0.1.5 release. 2000-02-23 20:19:42 +00:00 Removed the HardHat cross compiler prefix. 2000-04-27 00:08:44 +00:00



Copyright (C) 1999 AbsoluteValue Software, Inc.

The linux-wlan-ng package is a linux device driver and subsystem
package that is designed to provide the full range of IEEE 802.11 MAC
management capabilities for use in user-mode utilities and scripts.
The package currently supports the Intersil Prism2 11Mb/s reference design
PCMCIA wireless LAN (WLAN) card.

For a list of elements that are still undone, see the TODO file in 
this directory

See the COPYING and LICENSE files.

Top level directory for linux-wlan-ng:
./doc		- source distribution documentation
./man		- man pages
./etc		- scripts used at run-time
./src		- source code for various components

Some of the subdirectories have empty README files.  This means we haven't 
gotten to the contents of these directories.  The empty README is just a trick
to prevent CVS from pruning the directory.

prism2dl	This utility is used for loading firmware
   		images into prism2 cards.  DO NOT USE IT! 
		This utility has the capability to damage a
		card in a way that can only be repaired by the

This software has currently been tested on the following

   linux-2.2.9  + pcmcia-cs-3.1.8  + RedHat6.0
   linux-2.2.12 + pcmcia-cs-3.0.14 + RedHat6.1

The following build and install instructions assume you have configured source
code for both the linux kernel package and pcmcia-cs package installed on your
system.  It's important that the configured code for these packages match
the kernel and pcmcia-cs you currently have running.

Build Instructions:

1) untar the package using the command:

   tar zxvf linux-wlan-ng-X.Y.Z.tar.gz

2) Make sure you have configured kernel and pcmcia sources on your system.

3) To clean up any unwanted files accidentally included in the tar package,
   run 'make clean'.  If make clean behaves badly (infinite loop, for
   example), you may have a date/time mismatch.  Run the command:

   find . -type f -exec touch {} \;

   to fix the date&time stamps, then run 'make clean' again.

4) To configure the linux-wlan-ng package, run 'make config' and respond 
   to the questions.  The defaults should be sufficient for most
   users.  'make config' must be run after a 'make clean' and 
   before 'make all'.

5) To build the package, run 'make all'

6) To install the package, run 'make install' (as root).

7) Edit the /etc/pcmcia/wlan-ng.opts file to configure. These options are
   set every time you insert a card.  If you want to change an option
   after the initial configuration, a) pop your card out, b) alter the 
   file, c) insert your card.  For more information see the file(s)

8) Edit your network.opts file to set up your IP settings.  Note: for a 
   station, the SSID you're connecting to will be appended to the 
   current pcmcia scheme name.  You can use this to have different
   IP setups for different wireless LANs you connect to (e.g. home vs. work).

9) Restart pcmcia-cs with the command:

    /etc/rc.d/init.d/pcmcia restart

10) Insert the card.  For most cards, a solid LED indicates that the 
   SSID you specified was found, a bss was joined, and the firmware 
   completed the authenticate and associate processes.

11) Run ifconfig and route to determine if your IP and route settings are
    listed as you wanted them.  It's also a good idea to look at the file
    /etc/resolv.conf to see if your nameserver address has been set up 

12) If you are trying to set up an AP, you will need bridging support
    compiled into your kernel.  You will also need the brcfg utility.
    A version of this utility can be found on the AVS ftp site.