old-www/HOWTO/html_single/Wireless-Link-sys-WPC11/index.html

2398 lines
42 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Link-sys WPC11 Mini-HOWTO</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN2"
></A
>Link-sys WPC11 Mini-HOWTO</H1
><H3
CLASS="AUTHOR"
><A
NAME="AEN4"
>Gerardo Arnaez</A
></H3
><DIV
CLASS="AFFILIATION"
><DIV
CLASS="ADDRESS"
><P
CLASS="ADDRESS"
><TT
CLASS="EMAIL"
>&#60;<A
HREF="mailto:dude@mung.net"
>dude@mung.net</A
>&#62;</TT
></P
></DIV
></DIV
><DIV
CLASS="AFFILIATION"
><SPAN
CLASS="ORGNAME"
> <A
HREF="http://www.raintree.org"
TARGET="_top"
><SPAN
CLASS="TRADEMARK"
>Raintree
I.T.</SPAN
>&#8482;</A
>
<BR></SPAN
></DIV
><DIV
CLASS="AFFILIATION"
><SPAN
CLASS="ORGDIV"
> <EM
>Department of Advanced Skunk Works</EM
><BR></SPAN
></DIV
><DIV
CLASS="REVHISTORY"
><TABLE
WIDTH="100%"
BORDER="0"
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
COLSPAN="3"
><B
>Revision History</B
></TH
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.2.4</TD
><TD
ALIGN="LEFT"
>2004-06-03</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Cleaning up this HOW-TO. I have since moved on and
offer this document for adoption or at least consider it
obsolete at this time. Also my (ex) girl friend never did
write the documentation to how she got the card working with
Suse. Sorry.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.2.3</TD
><TD
ALIGN="LEFT"
>2003-07-31</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>WPC11 CARD DRIVERS HAVE CHANGED. Thanks to Bill
Atkins for providing information and solution</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.2.2</TD
><TD
ALIGN="LEFT"
>2003-07-05</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Most likely last update for this manual. The new
2.5 (to be 2.6) kernel appears to work fine with respect to
wireless cards and hence you can build wireless support
directly into the kernel and not have to go 'outside' it like this.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.2</TD
><TD
ALIGN="LEFT"
>2003-04-07</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Made a few typo corrections. Publish it on Freshmeat</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.0.2</TD
><TD
ALIGN="LEFT"
>2003-02-24</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Thanks to Justin Stockton for helping me eliminate a confusing bit of reading.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.0</TD
><TD
ALIGN="LEFT"
>2003-01-15</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>I have decided to generalize this document to other distributions then just Debian. The redhat section is due to the generous contribution of Tony Perrie of Involution (.DOT.) com. I also recently got a fast connection again and was able to update kernel and patches info. I also tried out the new wlan-ng module</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.2</TD
><TD
ALIGN="LEFT"
>2003-01-11</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Made clear where to get most up-to-date documents</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.1.4</TD
><TD
ALIGN="LEFT"
>2002-12-22</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>I forgot what i did here</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.1.3</TD
><TD
ALIGN="LEFT"
>2002-06-09</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Made clear what version on linux-wlan I actually used.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.1.2</TD
><TD
ALIGN="LEFT"
>2002-05-26</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>In part 2 of the HOWTO, the last item says make-kpkg --revision-custom.1.0 kernel_image when later on you used the correct one make-kpkg --revision=custom.1.0 kernel_image . Where there is an equal sign before the word custom and not a dash. This has been corrected. thanks to Raj Prakash, raj@rajeshprakash.com</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.1.1</TD
><TD
ALIGN="LEFT"
>2002-04-27</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>some more grammar improvements, and highlighting to make things clearer</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.1</TD
><TD
ALIGN="LEFT"
>2002-04-13</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Correct grammar, made things a little more clearer, made software requirements more explicit.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.0</TD
><TD
ALIGN="LEFT"
>2002-03-24</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Written because I spent enough figuring this out that I wanted to store "how I did it" somewhere I wouldn't lose it and figure you all might like it too.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 1.1.4</TD
><TD
ALIGN="LEFT"
>2002-8-10</TD
><TD
ALIGN="LEFT"
>Revised by: gea</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>I attempted to follow my own instruction on re-installing on the same laptop and found my how-to a little lacking. Have made things a bit clearer on what I am using. Also made a table to two</TD
></TR
></TABLE
></DIV
><DIV
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN88"
></A
><P
></P
><P
>This is a Cookbook on how to set up a Wireless Link-Sys WPC11 card using a Link-SYS Wireless Access Point/DSL/Switch on a Debian system. Other systems are addressed.
</P
><P
></P
></DIV
></DIV
><HR></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="#AEN92"
>Preliminaries</A
></DT
><DD
><DL
><DT
>1.1. <A
HREF="#AEN94"
>Where to Get Most Recent Updates</A
></DT
></DL
></DD
><DT
>2. <A
HREF="#AEN98"
>WARNING ABOUT WPC11 VERSION 4</A
></DT
><DT
>3. <A
HREF="#AEN134"
>Link-sys WPC11 install on Debian</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="#AEN136"
>Why Debian and why just this card?</A
></DT
><DT
>3.2. <A
HREF="#AEN145"
>Required Hardware</A
></DT
><DT
>3.3. <A
HREF="#AEN154"
>Software Requirements</A
></DT
><DT
>3.4. <A
HREF="#AEN242"
>Notes on additional helpful software</A
></DT
></DL
></DD
><DT
>4. <A
HREF="#AEN258"
>Debian Kernel Configuration</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="#AEN260"
>What TO enable</A
></DT
><DT
>4.2. <A
HREF="#AEN271"
>What <EM
>NOT</EM
> to Enable</A
></DT
></DL
></DD
><DT
>5. <A
HREF="#AEN284"
>Building PCMCIA-SOURCE</A
></DT
><DT
>6. <A
HREF="#AEN295"
>Using make-kpkg to build the new kernel and pcmcia-source modules</A
></DT
><DT
>7. <A
HREF="#AEN328"
>Wlan Drivers for You Link-Sys Card</A
></DT
><DT
>8. <A
HREF="#AEN348"
>Checking things in case they don't work</A
></DT
><DT
>9. <A
HREF="#AEN371"
>Wireless tools</A
></DT
><DT
>10. <A
HREF="#AEN380"
>RedHat Installation</A
></DT
><DD
><DL
><DT
>10.1. <A
HREF="#AEN385"
>Drivers</A
></DT
><DT
>10.2. <A
HREF="#AEN395"
>Hermes.conf Hack</A
></DT
><DT
>10.3. <A
HREF="#AEN401"
>Redhat PCMCIA Services</A
></DT
><DT
>10.4. <A
HREF="#AEN405"
>Redhat System Tools</A
></DT
><DT
>10.5. <A
HREF="#AEN409"
>Restart the network.</A
></DT
></DL
></DD
><DT
>11. <A
HREF="#AEN412"
>Wireless Access Point</A
></DT
><DT
>12. <A
HREF="#AEN415"
>Request for comments</A
></DT
></DL
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN92"
></A
>1. Preliminaries</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN94"
></A
>1.1. Where to Get Most Recent Updates</H2
><P
>The most recent updates to this mini-doc are at the <A
HREF="http://www.mung.net"
TARGET="_top"
>mung[dot]net</A
>. If you mirror this document, please try to keep it the most recent one.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN98"
></A
>2. WARNING ABOUT WPC11 VERSION 4</H1
><DIV
CLASS="CAUTION"
><P
></P
><TABLE
CLASS="CAUTION"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
><EM
>The NEW WPC11 CARDS HAVE Realtek 8180 CHIPSET
INSTEAD OF THE RTL8180.</EM
> Thanks to Juan Natera for
clarification</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="CAUTION"
><P
></P
><TABLE
CLASS="CAUTION"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>It had come to my attention that the new version,
Version 4 are not compatible with my old instructions. I include a set of
instruction provided by bill atkins</P
></TD
></TR
></TABLE
></DIV
><P
>Until I can clean this up, I include Bill atkins email for
sake of urgency</P
><P
>Quote from Bill Atkins</P
><P
>OK.
</P
><P
>First of all, make sure you have a V4 card. Type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>cardctl ident</PRE
></FONT
></TD
></TR
></TABLE
> as root.
If one of the entries shown is a <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>RealTek RTL8180L</PRE
></FONT
></TD
></TR
></TABLE
> or something similar,
then you have a version 4 card.</P
><DIV
CLASS="CAUTION"
><P
></P
><TABLE
CLASS="CAUTION"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If not, then you can probably just follow
the rest of the instructions in the HOWTO.</P
></TD
></TR
></TABLE
></DIV
><P
>Now you need to get drivers for the card. Go to RealTek's download
AND do a search fo 8180 from the downloads section</P
><P
>or you can download the driver that works with Bill's email
at
<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>ftp://152.104.125.40/cn/wlan/rtl8180l/rtl8180_24x_suse82.zip</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>and pick up the drivers for SuSE (you don't need to be running SuSE for
the drivers to work - I used them with Gentoo. However, the other divers
don't seem to work at all).
</P
><P
>Unpack the incoming tarball. As of this writing, there is a minor bug in
the driver code that must be repaired in order to make the card work.</P
><P
>Open up r8180_type.h.</P
><DIV
CLASS="CAUTION"
><P
></P
><TABLE
CLASS="CAUTION"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>On line 128, you'll see a line with two slashes
before the text. Remove these slashes. Now you're ready to build.</P
></TD
></TR
></TABLE
></DIV
><P
>At the shell prompt, type make. The drivers will build themselves. If
there are any problems making the drivers, open up the Makefile and check
the kernel version settings on the first few lines.
</P
><P
>Now open up the wlanup file.</P
><P
>Uncomment line 5 (remove the #) and change
the SSID to the SSID of your network.</P
><P
>Uncomment line 8 and set the
ssid2scan to your network's SSID. Uncomment line 9 and set the networktype
to infra (unless you really are using adhoc). Save your changes.</P
><P
>&#13; </P
><P
>Now eject the card <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>cardctl eject</PRE
></FONT
></TD
></TR
></TABLE
> and plug it in again.</P
><P
>From the
directory where you unpacked the drivers, type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>insmod -f rtl8180_24x.o</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>You will get a warning - ignore it.
</P
><P
>Now run the wlanup script found in the driver package. Your card should
now appear when you type ifconfig. You should configure your IP address
at this point. If you use DHCP, just type "dhcpd wlan0". Try pinging
google.com. You should get replies back. If so, your card is working!
</P
><P
>Now copy rtl8180_24x.o to /lib/modules/YOURKERNELNAME, where
YORUKERNELNAME is the name of the directory in /lib/modules.</P
><P
>Then copy
the wlanup and wlandown scripts to /sbin.
</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN134"
></A
>3. Link-sys WPC11 install on Debian</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN136"
></A
>3.1. Why Debian and why just this card?</H2
><P
>I have been trying for months to get wireless working on Debian and after reading far and wide and getting help from irc.debian.org, I realized that there really is no Cookbook in getting wireless set up. Thus having just done it I want to commit to 'paper' so that you all can use it and I can refer to it knowing it is safe somewhere. :)</P
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="AEN139"
></A
>3.1.1. Redhat installation</H3
><P
>I have gotten a few requests for help on getting the card installed on other distributions. I will try to address the RedHat Installation in this mini-how-to</P
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="AEN142"
></A
>3.1.2. Suse Installation</H3
><P
>My girlfriend got the WPC-11 card working on Suse. I am waiting for her to give me her how to</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN145"
></A
>3.2. Required Hardware</H2
><P
>By required I mean, here is what I used to get this to work, and may serve as guide to anyone who wants to know what really works.</P
><P
> <EM
>BEFW11S4- EtherFast? Wireless AP + Cable/DSL Router w/4-Port Switch.</EM
> I really really like this WAP (Wireless Access Point). It is OS independent (read, linux friendly) and is configured using a browser so no need to touch Microsoft software at all, even to configure it. And if you don't know what a switch is, let me tell ya, they rock. Essentially they allow the NIC to communicate in both directions at the same time. I highly recommend one.</P
><P
>Link-sys WPC11. I have a version 3.0 and don't recommend any thing less than a version 2.5 Cost about 80 dollars</P
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="AEN151"
></A
>3.2.1. What is the linksys card based on?</H3
><P
>It is an Inersil Prism 3-based card</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN154"
></A
>3.3. Software Requirements</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN156"
></A
>3.3.1. Debian Software Requirements</H3
><P
> <DIV
CLASS="TABLE"
><A
NAME="AEN159"
></A
><P
><B
>Table 1. Debian Software Requirements</B
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><THEAD
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Software</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Version</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>URL link</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>notes</TH
></TR
></THEAD
><TBODY
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Debian Distribution</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Stable ("Woody")</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><A
HREF="http://www.debian.org"
TARGET="_top"
>www.debian.org</A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>linux-2.4.20.tar, patched with patch-2.4.21-pre3.bz<A
NAME="AEN175"
HREF="#FTN.AEN175"
><SPAN
CLASS="footnote"
>[a]</SPAN
></A
>
</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Absolute Systems</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>0.1.16-pre8</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><A
HREF="http://www.linux-wlan.com/linux-wlan/"
TARGET="_top"
>Absolute systems</A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Make sure you download the <EM
>11Mbps</EM
> version. Works for 0.1.16-pre8</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>pcmcia-source</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Stable</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install pcmcia-source</PRE
></FONT
></TD
></TR
></TABLE
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>&#60;---type this</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>pcmcia-cs</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>stable</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install pcmcia-cs</PRE
></FONT
></TD
></TR
></TABLE
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>&#60;---type this</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>wireless-tools</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Stable</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install wireless-tools</PRE
></FONT
></TD
></TR
></TABLE
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>&#60;--type this</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>pump</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>stable</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install pump</PRE
></FONT
></TD
></TR
></TABLE
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Useful to see if card works</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>kernel-package</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>stable</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install kernel-package</PRE
></FONT
></TD
></TR
></TABLE
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Good way to build kernel and the one I describe.</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Kernel</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>2.4.20, patched with patch-2.4.21-pre3.bz2 </TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><A
HREF="http://www.kernel.org"
TARGET="_top"
>www.kernel.org</A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>You must know how to build and patch a kernel to do this. Its not hard and I will show you<A
NAME="AEN220"
HREF="#FTN.AEN220"
><SPAN
CLASS="footnote"
>[b]</SPAN
></A
></TD
></TR
></TBODY
><TR
><TD
COLSPAN="4"
>Notes:<BR><A
NAME="FTN.AEN175"
>a. </A
>This new patched kernel worked amazingly well<BR><A
NAME="FTN.AEN220"
>b. </A
>Note to patch a kernel you type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>bzip2 -dc patch-2.4.21-pre3.bz2 | patch -p0</PRE
></FONT
></TD
></TR
></TABLE
><BR></TD
></TR
></TABLE
></DIV
>
</P
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="AEN223"
></A
>3.3.2. RedHat Software Requirements</H3
><P
> <DIV
CLASS="TABLE"
><A
NAME="AEN226"
></A
><P
><B
>Table 2. RedHat Software Requirements</B
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><THEAD
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Software</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Version</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>URL link</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>notes</TH
></TR
></THEAD
><TBODY
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Redhat 8.0</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>stock kernel</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>*</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><A
HREF="http://www.redhat.com"
TARGET="_top"
>RedHat</A
></TD
></TR
></TBODY
></TABLE
></DIV
></P
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN242"
></A
>3.4. Notes on additional helpful software</H2
><P
>You will also need some way to setup you IP address on your wireless card, I recommend either <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install DHCP-client</PRE
></FONT
></TD
></TR
></TABLE
> to install the DHCP-client that will automatically configure your IP address, if you have a DHCP server. The WAP-11 hardware does provide DHCP server capabilities</P
><P
>Or at least have the <EM
>pump</EM
> application, which also will query a DHCP server and get you an IP address from the DHCP server. Note I tend to use <EM
>pump</EM
> when I am trying out new hardware to see if there is a connection, since to test a particular device, say <EM
>eth0</EM
> I would type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>pump -i eth0</PRE
></FONT
></TD
></TR
></TABLE
> where the option <EM
>-i</EM
> tells <EM
>pump</EM
> what device to try to get an IP address. In this particular case, when I could not get Debian to automatically set up my wireless card, which was device <EM
>wlan0</EM
>, I would type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>pump -i wlan0</PRE
></FONT
></TD
></TR
></TABLE
> and <EM
>pump</EM
> would try to set up the device. Anyway, the point is, that it is a good trouble shooting command, and you should know about it, and I talk more about it later.</P
><P
>I also recommend you use the "kernel-package" package when you want to build your new kernel, which I will get to. This tool is very good and you should be using it anyway when you are building new kernel for the Debian distribution. You can install it by typing <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install kernel-package</PRE
></FONT
></TD
></TR
></TABLE
> Also, be sure to read the documentation it comes with, in case I don't do a good job explaining how to use it, later in this document</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN258"
></A
>4. Debian Kernel Configuration</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN260"
></A
>4.1. What TO enable</H2
><P
>In order to use the wireless tools, like <EM
>iwconfig</EM
>, which will allow you tell how good your connection is, you need to enable support for <EM
>Wireless LAN (Non-Ham Radio)</EM
>.</P
><P
>In these examples, I use <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make menuconfig</PRE
></FONT
></TD
></TR
></TABLE
> to configure my kernel.</P
><P
>You can do this by:</P
><P
CLASS="LITERALLAYOUT"
>Go&nbsp;to:<br>
<br>
Network&nbsp;Device&nbsp;support&nbsp;--&#62;<br>
<br>
then&nbsp;Select:<br>
<br>
&nbsp; Wireless&nbsp;LAN&nbsp;(non-hamradio)&nbsp;&nbsp;---&#62;</P
><P
>Then Choose the options,
so that it looks like below, or something
as close to this.
Note I am using 'make menuconfig'
to configure my kernel</P
><P
CLASS="LITERALLAYOUT"
>&nbsp;&nbsp;[*]&nbsp;Wireless&nbsp;LAN&nbsp;(non-hamradio)<br>
&nbsp;&nbsp;&#60;&nbsp;&#62;&nbsp;&nbsp;&nbsp;STRIP&nbsp;(Metricom&nbsp;starmode&nbsp;radio&nbsp;IP)<br>
&nbsp;&nbsp;&#60;&nbsp;&#62;&nbsp;&nbsp;&nbsp;AT&nbsp;T&nbsp;WaveLAN&nbsp;&#38;&nbsp;DEC&nbsp;RoamAbout&nbsp;DS&nbsp;support<br>
&nbsp;&nbsp;&#60;&nbsp;&#62;&nbsp;&nbsp;&nbsp;Aironet&nbsp;Arlan&nbsp;655&nbsp;&#38;&nbsp;IC2200&nbsp;DS&nbsp;support<br>
&nbsp;&nbsp;&#60;&nbsp;&#62;&nbsp;&nbsp;&nbsp;Aironet&nbsp;4500/4800&nbsp;series&nbsp;adapters<br>
&nbsp;&nbsp;&#60;&nbsp;&#62;&nbsp;&nbsp;&nbsp;Cisco/Aironet&nbsp;34X/35X/4500/4800&nbsp;ISA&nbsp;and&nbsp;PCI&nbsp;cards<br>
&nbsp;&nbsp;&#60;*&#62;&nbsp;&nbsp;&nbsp;Hermes&nbsp;chipset&nbsp;802.11b&nbsp;support&nbsp;(Orinoco/Prism2/Symbol)<br>
&nbsp;&nbsp;&#60;&nbsp;&#62;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Hermes&nbsp;in&nbsp;PLX9052&nbsp;based&nbsp;PCI&nbsp;adaptor&nbsp;support<br>
&nbsp;&nbsp;&#60;*&#62;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Prism&nbsp;2.5&nbsp;PCI&nbsp;802.11b&nbsp;adaptor&nbsp;support&nbsp;</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN271"
></A
>4.2. What <EM
>NOT</EM
> to Enable</H2
><P
>One of the main stumbling blocks was to realize that the <EM
>pcmcia support in the kernel is not as good as the pcmcia-source support</EM
> that one gets when you build it from pcmcia-source.</P
><P
>I use either <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make xconfig</PRE
></FONT
></TD
></TR
></TABLE
> or <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make menuconfig</PRE
></FONT
></TD
></TR
></TABLE
> to configure my kernel, so when you configure your kernel, be sure to not have pcmcia support enabled under <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>General setup</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>Nor do you want to select any particular pcmcia card under <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>Network device support</PRE
></FONT
></TD
></TR
></TABLE
>. I repeat you do not want this under the kernel and you will be building it when you download pcmcia-source.</P
><DIV
CLASS="CAUTION"
><P
></P
><TABLE
CLASS="CAUTION"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Be sure to download all the necessary components before you take pcmcia support out of the kernel, otherwise, if you were using a pcmcia card for net access, you will not be able to connect to the Internet using the new kernel, until you have built both pcmcia support and module drivers for the wireless card</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN284"
></A
>5. Building PCMCIA-SOURCE</H1
><P
>Download pcmcia-source, by typing <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install pcmcia-source</PRE
></FONT
></TD
></TR
></TABLE
> This will download the source into <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/usr/src</PRE
></FONT
></TD
></TR
></TABLE
> as <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>pcmcia-cs.tar.gz</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>You now need to gunzip the file by <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>gunzip pcmcia-cs.tar.gz</PRE
></FONT
></TD
></TR
></TABLE
> and then untar the file by <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>tar xvf pcmcia-cs.tar</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>You should see pcmcia-source unpacked into the directory <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/usr/src/modules/pcmcia-cs</PRE
></FONT
></TD
></TR
></TABLE
></P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN295"
></A
>6. Using make-kpkg to build the new kernel and pcmcia-source modules</H1
><P
>Steps to build the kernel</P
><P
></P
><UL
><LI
><P
>Be sure the pcmcia-source is under /usr/src/modules.</P
></LI
><LI
><P
>Go ahead and configure your kernel and be sure that pcmcia support IS NOT compiled in as an option in the kernel.</P
></LI
><LI
><P
>To build the kernel and pcmcia-source, be sure you are under the <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/usr/src/linux</PRE
></FONT
></TD
></TR
></TABLE
> or have a symbolic link from /usr/src/linux pointing to whatever kernel source you have set up.</P
></LI
><LI
><P
>Type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make-kpkg clean</PRE
></FONT
></TD
></TR
></TABLE
> to clean</P
></LI
><LI
><P
>Then type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make-kpkg --revision=custom.1.0 kernel_image modules_image</PRE
></FONT
></TD
></TR
></TABLE
></P
></LI
></UL
><P
>The <EM
>kernel_image</EM
> option will build the kernel while the <EM
>modules_image</EM
> option will build all modules located under <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/usr/src/modules/</PRE
></FONT
></TD
></TR
></TABLE
>. So be sure that you do indeed want to rebuild any other modules that are located in source when you are ready to build your new kernel.</P
><P
>After some chugging, go up one level to <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/usr/src</PRE
></FONT
></TD
></TR
></TABLE
> and you should see two new Debian packages that should look something like this:
<P
CLASS="LITERALLAYOUT"
>kernel-image-2.4.19-pre4_custom.1.0_i386.deb<br>
pcmcia-modules-2.4.19-pre4_3.1.31-7+custom.1.0_i386.deb</P
></P
><P
>You first want to install the kernel image so you would type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>dpkg -i kernel-image-etc....</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>Now install the modules by typing <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>dpkg -i pcmcia-modules.etc...</PRE
></FONT
></TD
></TR
></TABLE
></P
><DIV
CLASS="CAUTION"
><P
></P
><TABLE
CLASS="CAUTION"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/caution.gif"
HSPACE="5"
ALT="Caution"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>There are a couple of assumptions that make-kpkg makes about your lilo.conf file. One is that you have not radically changed it. Make-kpgk will make make symbolics links from '/boot' where the actual kernel resides to 'vmlinuz' which is under '/'. In other words, under '/', you will see <EM
>vmlinuz</EM
> and <EM
>vmlinuz.old</EM
> which are symbolic links to the real kernel images under <EM
>/boot/</EM
>. Anyway if you have any questions ask me.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN328"
></A
>7. Wlan Drivers for You Link-Sys Card</H1
><P
>You have downloaded the 11 Wlan project. Go a head and read the instruction, and put it under modules. Follow the instructions when you <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make config</PRE
></FONT
></TD
></TR
></TABLE
> The one key is to make sure you specify the pcmcia-source as under <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/usr/src/modules/pcmcia-cs</PRE
></FONT
></TD
></TR
></TABLE
> and not choose the default it gives you.</P
><P
>Go ahead and <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make all</PRE
></FONT
></TD
></TR
></TABLE
> and <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>make install</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>I suggest you read the documentation that comes with it, but essentially, <EM
>if you have a WAP that is connected to your DSL or cable modem then you have a <EM
>infrastructure set up.</EM
></EM
> I found that it was best to edit the <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>networks.opt</PRE
></FONT
></TD
></TR
></TABLE
> under the <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/etc/pcmcia</PRE
></FONT
></TD
></TR
></TABLE
> directory.</P
><P
>To make things easier edit the option
<P
CLASS="LITERALLAYOUT"
>#&nbsp;Use&nbsp;DHCP&nbsp;(via&nbsp;/sbin/dhcpcd,&nbsp;/sbin/dhclient,&nbsp;or&nbsp;/sbin/pump)?&nbsp;[y/n]<br>
DHCP="y"</P
> to what I have, i.e., set it to yes.</P
><P
>The documentation talks about setting ESSID but when you edit the <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>wlan-ng.opts</PRE
></FONT
></TD
></TR
></TABLE
> you will only see
<P
CLASS="LITERALLAYOUT"
>#=======INFRASTRUCTURE&nbsp;STATION&nbsp;START===================<br>
#&nbsp;SSID&nbsp;is&nbsp;all&nbsp;we&nbsp;have&nbsp;for&nbsp;now<br>
AuthType="opensystem"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;#&nbsp;opensystem&nbsp;|&nbsp;sharedkey&nbsp;(requires&nbsp;WEP)<br>
DesiredSSID="howardnet"</P
></P
><P
>From what I can gather,DesiredSSID means ESSID and it works when the WAP and link-sys pcmcia card share the same name.</P
><P
>At this point, you should reboot and should have a working link-sys card that gets its address via DHCP.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN348"
></A
>8. Checking things in case they don't work</H1
><P
>1. Be sure to type <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>ifconfig</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>You should something like this</P
><P
CLASS="LITERALLAYOUT"
>lo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Link&nbsp;encap:Local&nbsp;Loopback<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;inet&nbsp;addr:127.0.0.1&nbsp;&nbsp;Mask:255.0.0.0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;UP&nbsp;LOOPBACK&nbsp;RUNNING&nbsp;&nbsp;MTU:16436&nbsp;&nbsp;Metric:1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;packets:0&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;frame:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TX&nbsp;packets:0&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;carrier:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;collisions:0&nbsp;txqueuelen:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;bytes:0&nbsp;(0.0&nbsp;b)&nbsp;&nbsp;TX&nbsp;bytes:0&nbsp;(0.0&nbsp;b)<br>
<br>
wlan0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Link&nbsp;encap:Ethernet&nbsp;&nbsp;HWaddr&nbsp;00:06:25:A8:AE:64<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;inet&nbsp;addr:192.168.1.104&nbsp;&nbsp;Bcast:192.168.1.255&nbsp;&nbsp;Mask:255.255.255.0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;UP&nbsp;BROADCAST&nbsp;RUNNING&nbsp;MULTICAST&nbsp;&nbsp;MTU:1500&nbsp;&nbsp;Metric:1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;packets:35197&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;frame:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TX&nbsp;packets:57676&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;carrier:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;collisions:0&nbsp;txqueuelen:100<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;bytes:43386657&nbsp;(41.3&nbsp;MiB)&nbsp;&nbsp;TX&nbsp;bytes:2670811&nbsp;(2.5&nbsp;MiB)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Interrupt:3&nbsp;Base&nbsp;address:0x100</P
><P
>The keys point here are that <EM
>inet addr:</EM
>has a real IP address, and that <EM
>Bcast</EM
> and <EM
>Netmask</EM
> are set up such that they are on the same "wave-length" as your Wireless Access Point.</P
><P
>2. If you don't, you might have had the same problem i did which was that there was no easy script to initiate the wlan0 device setup. That is to say, if the card was recognized but you still did not get a connection and say that ifconfig showed wlan0 present but with no IP address. In other words, you might see something like this:</P
><P
><P
CLASS="LITERALLAYOUT"
>text:/home/dude#&nbsp;ifconfig<br>
<br>
lo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Link&nbsp;encap:Local&nbsp;Loopback<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;inet&nbsp;addr:127.0.0.1&nbsp;&nbsp;Mask:255.0.0.0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;UP&nbsp;LOOPBACK&nbsp;RUNNING&nbsp;&nbsp;MTU:16436&nbsp;&nbsp;Metric:1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;packets:14&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;frame:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TX&nbsp;packets:14&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;carrier:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;collisions:0&nbsp;txqueuelen:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;bytes:700&nbsp;(700.0&nbsp;b)&nbsp;&nbsp;TX&nbsp;bytes:700&nbsp;(700.0&nbsp;b)<br>
<br>
wlan0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Link&nbsp;encap:Ethernet&nbsp;&nbsp;HWaddr&nbsp;00:06:25:A8:AE:64<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;UP&nbsp;BROADCAST&nbsp;RUNNING&nbsp;MULTICAST&nbsp;&nbsp;MTU:1500&nbsp;&nbsp;Metric:1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;packets:1&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;frame:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TX&nbsp;packets:0&nbsp;errors:0&nbsp;dropped:0&nbsp;overruns:0&nbsp;carrier:0<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;collisions:0&nbsp;txqueuelen:100<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RX&nbsp;bytes:46&nbsp;(46.0&nbsp;b)&nbsp;&nbsp;TX&nbsp;bytes:0&nbsp;(0.0&nbsp;b)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Interrupt:3&nbsp;Base&nbsp;address:0x100<br>&#13;</P
></P
><P
>As you can see, the interface device, the Wireless pcmcia card, is noted, but there is no <EM
>inet addr</EM
>. The pcmcia software recognized the card, but it has not successfully connected with the Wireless Access Point.</P
><P
>I used the command,<EM
>pump</EM
> to send a simple DHCP request to the DHCP server for the device in question. I used<TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>pump -i wlan0</PRE
></FONT
></TD
></TR
></TABLE
> which essentially runs a simple DHCP request to set up that card, wlan0, in this case.</P
><P
>You can get the <EM
>pump</EM
> by <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>apt-get install pump</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
>While I needed to use <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>pump -i wlan0</PRE
></FONT
></TD
></TR
></TABLE
> on my laptop, I did not need this when I set up the link-sys wireless WPC11 card on my girlfriend's laptop. She has a Link-Sys WPC11 version 2.5 pcmcia card.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN371"
></A
>9. Wireless tools</H1
><P
>While it is not necessary to include this in your kernel configuration, you can enable Wireless tool extensions by going (i assume you use xconfig or menuconfig) to <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>Network device support</PRE
></FONT
></TD
></TR
></TABLE
> and then go to <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>Wireless LAN (non-hamradio)</PRE
></FONT
></TD
></TR
></TABLE
> and enable support for the <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)</PRE
></FONT
></TD
></TR
></TABLE
>. This will let you use the Wireless Tools like <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>iwconfig</PRE
></FONT
></TD
></TR
></TABLE
>, <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>iwspy</PRE
></FONT
></TD
></TR
></TABLE
> and such.</P
><P
>The one thing I found this good for is that by repeated typing iwconfig, you can see your Link Quality. Its quite good</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN380"
></A
>10. RedHat Installation</H1
><P
>This is a summary of what Mr.Tony Perrie of <A
HREF="http://involution.com"
TARGET="_top"
>involution.com</A
> fame has wriiten. I include here with his permission. I encourage you to visit his site because he has a great "how-to" on <A
HREF="http://involution.com/iptables_demo/"
TARGET="_top"
>IPtables</A
>.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN385"
></A
>10.1. Drivers</H2
><P
>The stock kernel driver to use with the WPC11 is the orinoco_cs. Make sure that it's loaded.</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>modprobe orinoco_cs</PRE
></FONT
></TD
></TR
></TABLE
><P
>If you get some error messages after executing modprobe, insure that the wavelan_cs and wvlan_cs drivers are unloaded. By doing</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>lsmod | egrep lan</PRE
></FONT
></TD
></TR
></TABLE
><P
>If they are loaded do the following:</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>rmmod wavelan_cs</PRE
></FONT
></TD
></TR
></TABLE
><P
>and</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>rmmod wvlan_cs</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN395"
></A
>10.2. Hermes.conf Hack</H2
><P
>The hack is putting the following in</P
><P
> <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>/etc/pcmcia/hermes.conf.</PRE
></FONT
></TD
></TR
></TABLE
>
<P
CLASS="LITERALLAYOUT"
>card&nbsp;"Instant&nbsp;Wireless&nbsp;Network&nbsp;PC&nbsp;Card"<br>
manfid&nbsp;0x0274,0x1613<br>
bind&nbsp;"orinoco_cs"<br>
</P
>
</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN401"
></A
>10.3. Redhat PCMCIA Services</H2
><P
>You'll then need to restart pcmcia service.</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>service pcmcia restart</PRE
></FONT
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN405"
></A
>10.4. Redhat System Tools</H2
><P
>Go to the Redhat System Tools and hit Configure. Then add a wireless device in Managed mode if you have an access point.</P
><P
> Setup dhcp, and the WEP key. The channel autoconfigures to 6 in managed mode.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN409"
></A
>10.5. Restart the network.</H2
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>service network restart</PRE
></FONT
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN412"
></A
>11. Wireless Access Point</H1
><P
>Perhaps its it missing the forest for the trees, but I did not spend any discussion setting up the actual Wireless Access Point. The reason is that the documentation that comes with the WAP is well written. The only thing I haven't spoken about is enabling Wireless Encryption Protocol in the WAP (Wireless Access Point) which I really don't suggest as I don't think WEP has been properly set up in the drivers for the Pcmcia Wireless Cards. However, let me know if you have any problems and I will be glad to help.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN415"
></A
>12. Request for comments</H1
><P
>I will be glad to help anyone out and if things are a bit confusing in this quite mini how to, please tell me how I can fix it to make it better.</P
><P
>Thanks!</P
></DIV
></DIV
></BODY
></HTML
>