Dave, Thanks. FWIW the HW is Airlink 101 both sides. I don't know the chipset. It is a PCMCIA card in the laptop and it does recognize it, although I had to yum down a new kernel and a driver.
I'll literally print your response out and work through it line by line, probably moving my lips. This is from the installation instructions I found: "I had success installing my Airlink101 AWLC4030 Super Gâ Wireless Cardbus Adapter. This device uses the atheros drivers which in linux are called the madwifi drivers and as you can see you can get these packages from atrpms. If you have this repository in your yum.conf you can install via yum and a dependency will be needed to install the drivers. The dependency is installed according to your kernel version." http://www.linuxforums.org/forum/ntopic36292.html On Sun, Apr 10, 2005 at 02:39:13PM -0700, David J. Looney wrote: > On Sun, 10 Apr 2005 11:13:50 -0700 > Lan Barnes <[EMAIL PROTECTED]> wrote: > > Lan, you don't say anything r.e. your wireless laptop card or chipset > (or even that you're talking linux vs. windows laptop). Does PCMCIA > recognize your card ? Or are we talking builtin chipset ? > > It looks like the router is 802.11g by default, supporting WPA/WPA-PSK, > but linux support on the laptop side is limited, with native support for > 802.11g being limited principally to prism32 chipsets. I think you can > use wpa_supplicant even with 802.11b (but I'm not positive) so it's > possible you could your 802.1x with WPA. > > If possible, you would probably like to run 802.11g (better speed) with > WPA-PSK (pre-shared key), but you could fall back on 802.1x with WPA or > WEP if you can't get WPA working on the laptop. > > To get something working at all -> try selecting 802.1x with WEP > enabled, and set the WEP key on the router and laptop using whatever > network configuration tool on the laptop, see if you can pick up your > wireless network on the laptop (good tools iwconfig, iwlist eg 'iwlist > wlan0 scan' should give some output of what's floating around your > neighborhood). > > OK, so if can work with 802.1x, then proceed to try 802.11g and WPA (WEP > is *very* crackable with easily available tools). If you're running > linux on the laptop and have a prism wireless chipset, you'll have to > pick up the prism32 drivers, and wpa_supplicant (and/or x_supplicant), > and compile these tools. The prism32 drivers require a 2.6 kernel and a > kernel patch (or used to, maybe the kernel has now caught up). The > wpa_supplicant package is standalone. You use the tools in the > wpa_supplicant package to make a key from the WPA passphrase which you > insert into a little script to negotiate the connection and encryptation > for the wireless connection. > > Alternatively, if you don't have 802.11g chipset supported under linux, > for a few $$ you can buy the linuxant driver loaders (works with most > everything, including Intel Centrino), which loads the windows drivers > software under linux (you'll also still need wpa_supplicant). There is > an opensource project that similarly tries to wrap the windows drivers > (blocking on the name, something-wrappers), but I don't know how wide > chipset support is (was pretty narrow when I looked). > > I use a WG511 802.11g card with linuxant drivers and wpa_supplicant to > connect with a netgear wireless router using WPA-PSK under Suse 9.0 on > my laptop. > > David Looney > > > I posted this to Newbie where it died of loneliness. Maybe it was the > > wrong list ... > > > > *** > > > > OK, I got the Airlink 101 working. The reason the headless server was > > failing to go out through it was that the MB eth cnx has no mac > > address (giving me a "huh" moment -- like, how did it ever work?). I > > put in a 3com card and that's doing fine. Had to turn off kudzu, edit > > some configs, etc. > > > > Now to tighten that puppy down. I've read all Tracy's recent rants, > > but I'm new to this. > > > > The router has the options: > > > > Shared key > > WPA > > WPA-PSK > > 802.1x > > > > Then there's a line that says > > > > WEP () Enabled () Disabled > > > > Then there's configuring the wireless card in the laptop. It would > > never do to lock up the router and be unable to connect. > > > > A little help here ... ? > > > > TIA, > > > > *** > > > > Maybe my questions weren't clear. Which option should I select? Should > > I enable WEP? How do I configure the laptop card to match the router > > choices? > > > > -- > > Lan Barnes [EMAIL PROTECTED] > > Linux Guy, SCM Specialist 858-354-0616 > > -- > > [email protected] > > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list > -- > [email protected] > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
