Added the config.* files and made a legibility change to mysteries.

This commit is contained in:
mark 2000-02-07 19:01:47 +00:00
parent 4b6149c9fe
commit 3860705b7f
3 changed files with 154 additions and 1 deletions

doc/config.debug Normal file
View File

@ -0,0 +1,36 @@
The kernel components of linux-wlan-ng currently have debugging code
enabled permanently (we'll make it optional later). To enable the
debug output, you set the value of the module parameter xxx_debug
where xxx is the name of the component. There are five levels of
debugging (1-5). Here's a summary of the levels and their usage:
1 - Enables most error messages for exception (but rare) conditions
2 - Enables more exceptions
3 - Enables MAC status output
4 - More status
5 - Function entry and exit
The levels are additive. For example, level 3 includes level 3
messages plus levels 1 and 2.
To configure p80211.o for debug output, put the following line (with
your own level number) in your /etc/conf.modules file:
options p80211 wlan_debug=2
To configure the prism2 driver for debug output, put the following
line (with your own level number) in your /etc/pcmcia/config.opts
module "prism2sta_cs" opts "prism2_debug=2"
Then configure the collection and display of your kernel output. This
is usually done using syslog. Here are the relevant entries from the
/etc/syslog.conf file on one of my test machines:
kern.* /var/log/kernel
kern.* /dev/tty9
*.info;mail.none;news.none;authpriv.none /var/log/messages
*.info;mail.none;news.none;authpriv.none /dev/tty10

doc/config.linux-wlan-ng Normal file
View File

@ -0,0 +1,116 @@
Here we describe a little more of the detail behind configuring the
linux-wlan system.
The linux-wlan-ng package consists of the following components:
p80211.o Kernel module for 802.11 services
prism2sta_cs.o Kernel module for the Prism2 PCMCIA device
wlanctli-ng User-mode utility for sending commands to
802.11 services and MAC-specific drivers.
wland User-mode daemon for receiving and handling
events from 802.11 services and MAC-specific
drivers (not used in this version).
wlandump User-mode utility for viewing MAC-level 802.11
/etc/pcmcia/wlan-ng* PCMCIA event and configuration scripts
*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
When a 'make install' is performed, the modules are copied to the
/usr/lib/modules/<kernelver>/net and /usr/lib/modules/pcmcia
directory, the user-mode utilities are copied to /sbin, and the
contents of linux-wlan-ng/etc/pcmcia are copied to the /etc/pcmcia
directory. The pcmcia config files are altered to include a reference
to the wlan-ng.conf file containing the information cardmgr uses to
match card CIS information to specific device drivers at card
insertion time.
NOTE: It is very important that you restart your pcmcia services after
installing linux-wlan-ng. cardmgr will not recognize the information
in the wlan-ng.conf file until after it has been restarted.
To configure your installation for use, it will probably be necessary
to edit the /etc/pcmcia/wlan-ng.opts file. This file contains a
collection of variable assignments that are used by the wlan-ng script
to intialize your card at insertion time. To determine which
variables you need to set and what you want to set them to, you must
first determine what kind of installation you are doing: a Station
(STA) or an Access Point (AP).
To configure for a STA (the most common), there must be an Access Point
already available. To enable STA configuration there are only two variables
you need to worry about. The first is the IS_AP variable. For a STA
installation, it should always be be set to 'n'. The second variable
is DESIRED_SSID. DESIRED_SSID should be set to the SSID string
currently being used by your access point. If the SSID has whitespace
in it, make sure you quote the string. The remainder of variables in
/etc/pcmcia/wlan-ng.opts don't matter for a STA installation.
If you have access to the necessary hardware and firmware, this driver
can be used to set up a Access Point. To configure for an access
point, set the IS_AP variable to 'y'. The following is a quick
summary of the other AP configuration variables:
Defines the location of a firmware image for those cards that
need code downloaded at initialization time.
Defines the ethernet device that will be the 'other' port for
bridging 802.11 frames.
Defines the SSID that the AP will use in creating the network.
Defines the beacon interval (in Kus) that the AP will use.
Defines the DTIM interval (in beacon intervals).
false | false | No point coordination by this AP
false | true | AP will point coordinate for delivery only
true | false | AP will point coordinate for deliver and polling
true | true | Reserved
Defines how often the contention free period occurrs (in
Defines the maximum length of the contention free period (in
Not used for infrastructure networks, any value is valid.
Channel that the AP will create the network on.
A whitespace separated list of data rates in units of 500Kb/s.
The basic rate set is the set of rates that stations MUST
support to be allowed to join the network.
APOPRATES="2 4 11 22"
A whitespace separated list of data rates in units of 500Kb/s.
The operational rate set is the set of rates that are allowed
in the network. It must be a superset of the basic rates
To complete the configuration of an Access Point, you will need to
make sure you have kernel bridging enable in your currently running
kernel and have the brcfg utility installed. One version of the brcfg
utility can be found at
To start the access point running, make sure the ethernet card is in the
system first. Then insert the WLAN card and everything should be
configured automatically by the /etc/pcmcia/wlan-ng script.

View File

@ -10,7 +10,8 @@ Sun Feb 6 17:25:35 EST 2000
Any use of the prism2 card.
F/W is returning the same FID for both allocation.
F/W is returning the same FID for both the infofid and the txfid