readme.isa

Linux Wireless LAN Project 的目标是开发一个完整的

README.isa

This release of linux-wlan has integrated the work of Peter Teuben and
others to include support for the ISA PnP cards sold by YDI, Samsung,
and probably ImasDe (not tested).  NOTE: The information in this document 
does NOT have anything to do with the Zoom ZoomAir ISA product.  The 
ZoomAir ISA is a PCMCIA card shipped with an ISA to PCMCIA bridge card.  
Use the PCMCIA instructions.

Much of this document is copied from Peter's README.isa from his
wlan-isa package.  We've removed the parts regarding the requirement
that pcmcia sources be present for compiling linux-wlan.

Basically you will see the following things below:

   * installing the WLAN software
   * make your WLAN card PnP aware
   * activate the card and install the networking software


- install the source code for wlan (or whatever tar.gz file comes with this
  release:

	tar -C /usr/src -zxf linux-wlan-x.x.x.tar.gz
	cd /usr/src
	ln -s linux-wlan-isa-0.2.6 wlan
	cd wlan

- edit the config.mk file in wlan (see README), if you are _only_
  building for ISA, make sure the MAKE_CS variable is set to 'n'.

- now compile and install the code in the wlan directory:

        make all
        make install

  this should have installed the /sbin/wlanctl program, as well as your
  isa module in /lib/modules/<version>/net/am930_isa.o

- you probably should do
        depmod -a
  to double check if there are not some worrysome module dependancy problems.

- Your WLAN card is a PnP card, and I assume you know how to install those.

  If not, you can skip this section, but somehow you need to figure out
  what the IRQ and IOBASE of your card are.

  Before you install the card, check out your /proc/interrupts and
  /proc/ioports files. Maybe make a logfile of them.
  Also helpful is reading the PnP HOWTO in the Linux Documentation Project
  (LPD).
  First of all, it's probably best to turn PnP on in your BIOS.

  [MSM Note:  On one of my machines (K6, SiS530 chipset, AMI BIOS), it was 
  necessary to turn the setting "PnP Aware O/S" to NO before my IRQ 
  would work correctly.]

  Next, you need to run pnpdump to detect your devices:

	pnpdump > /tmp/isapnp.conf

  Inspect this file, and one of your card should read something like

	# Card 2: (serial identifier b7 f8 06 64 f0 c9 30 96 04)
	# Vendor Id ADV30c9, Serial Number 4161168624, checksum 0xB7.
	...
	#  (IO 0 (SIZE 16) (BASE 0x0240))
	...
	# (INT 0 (IRQ 9 (MODE +E)))
	# (NAME "ADV30c9/4161168624[0]{AMD PCnet-Mobile    }")
	# (ACT Y)

  You can see this card can run at IRQ 9 and IO address 0x240. So, commment
  out those last 4 lines, and put this file in /etc/isapnp.conf, and activate
  it (normally your boot process will do this if it finds a /etc/isapnp.conf
  file):

	isapnp /etc/isapnp.conf

  and you should see no problems with this install. If you do, make sure
  you don't have IRQ and/or IO conflict, by inspecting
	/proc/interrupts
  and
	/proc/ioports
  In my case I had to reconfigure my ethernet card to use another IRQ from
  the 9 that the WLAN appeared to like to use.

- Now insert the module, using the IRQ and IOBASE derived from the previous
  step:

	insmod am930_isa am930_irq=9 am930_iobase=0x240

  but sometimes it's needed to manually insert this

	cd /lib/modules/2.2.7/pcmcia
	insmod ./am930_isa.o am930_irq=9 am930_iobase=0x240

  if module dependancies have not been properly registered.

  CAVEAT: Be very careful, currently the "rmmod" command *may* crash your 
  machine. Count on rebooting if you must *rmmod* this module for some reason. 
  We are working on solving this. If you must rmmod, better "umount -a" all
  unimportant devices.


- Now the WLAN network can be installed. Here's a manual example of
  this (assuming this is in bash-shell notation)

    E=eth1

    IP=192.168.2.31         <-  your IP
    BC=192.168.2.255
    NM=255.255.255.0        <- C-class network
    NW=192.168.2.0


    #  note here we are using channel 6 !
    wlanctl $E scan 1 11 100 ff:ff:ff:ff:ff:ff both active ""
    wlanctl $E bsscreate  6 300 0 WLAN_AVS

    # start up the network (this is normally
    ifconfig $E $IP broadcast $BC netmask $NM 
    # on kernel 2.2 don't need to route, ifconfig does it, on 2.0 we do need it
    #route add -net $NW  netmask $NM $E


- You can find some of this setup in the attached file rc.wlan. You can
  tailor your file and put it in /etc/rc.d, and for example let /etc/rc.local
  execute this file at boot time.

  One extra thing you probably want to do it set routing from eth1 (the wlan
  in my case) through the eth1/eth0 gateway to the internet, assuming that
  that gateway had its routing setup properly. This way you can directly
  acccess the internet from any wlan machine. To visualize, my home setup
  is as follows:

           (ISP)
            ppp0
               \
                +------------+-----------+-----     
192.168.1.x    28           31          13              local ether-net
                             |
                             |
                             |
192.168.2.x                 31                5         2.4GHz wlan-net
                        ~~~~~+~~~~~~~~~~~~~~~~+~~~~~~~~


    E.g. on 192.168.2.5 you need to setup another routing entry to get to
    192.168.1.28 network, e.g. on 192.168.2.5
	route -add net 192.168.1.0 gw 192.168.2.31
    Equally so, you must tell the other machines how to get back to close
    the loop, e.g. on 192.168.1.28;
	route -add net 192.168.2.0 gw 192.168.1.31
	
    In redhat you would just add a static route, which "ifup" would 
    automatically pick up. In slackware you will have to add some
    manual routing to /etc/rc.d/rc.inet1

    See network.ps for a graphics layout of my home network.


- Known problems - anecdotal.

  * SuSe 6.1 gave me serious problems, code compiles but coredumps
    Suse 6.2 code compiles fine, but pnpdump crashed machine
  * rmmod may crash your machine -- probably solved ?? --
  * ftp large files can hang the device, and some problems have been
    seen on PC-card transfers also.

- 
  

Please feel free to send me email with questions (or patches):

Peter Teuben
[e-mail]

This document was modified/annotated by Mark Mathews
<[e-mail]>