[TriLUG] having trouble getting wpa setup

[Kevin J.]

I run Kubuntu on my laptop and it picks up every wireless network/protocol it comes in contact with. Your only limitation might be in the driver for your wireless card. If you're not running *ubuntu you may want to try a live cd of any one of them and give it a try first. If it picks up your card and a WPA(2) network then you're probably good to go. 

I have a a/b/g card built-in so I'm not sure about the "b" aspect being an issue, but as a/b/g are layer 1 technology, I don't think it would make any difference as most APs talk to all three. 

Kevin

----- Original Message ----
From: Matt Pusateri <mpusateri at wickedtrails.com>
To: Triangle Linux Users Group discussion list <trilug at trilug.org>
Sent: Sunday, June 24, 2007 6:14:28 PM
Subject: Re: [TriLUG] having trouble getting wpa setup

If your running gnome, you might give NetworkManager a try. I've had 
times when I couldn't get WPA to work, but NetworkManager did some 
voodoo behind the scenes and it worked without a hitch. Network Manager 
also will connect to wep.  Plus it's really nice for switching networks. 
I think there's a knetworkmanager as well for KDE, although I can't 
comment on it's functionality.

Matt P.

Joseph Mack NA3T wrote:
> I'm going to a conference this week where I'll need wpa to 
> get wifi access (I only found this out yesterday). I only 
> have wep here at home. wpa_supplicant seems to be able to 
> handle wep (acording to the docs), so I've spent the last 
> day trying to get wpa_supplicant to connect to a wep wap.
>
> here's my wpa_supplicant.conf
>
>
> ctrl_interface=/var/run/wpa_supplicant
>
> network={
>          ssid="MYSSID"
>          key_mgmt=NONE
>          wep_key0="abcde"
>          wep_key1=HEXKEY................
>          wep_tx_keyidx=1
> }
>
> I can give lots of debugging output if needed from 
> wpa_supplicant either driven by commands from wpa_cli or 
> from using the above conf file with wpa_supplicant in 
> debugging mode, but really have no idea what I'm doing.
>
> Sometimes the HEXKEY doesn't appear in the output of 
> iwconfig, and I get a dhcp IP from another network 
> (presumably a neighbor). Other times the HEXKEY is in the 
> output of iwconfig, but I don't get an IP; in this case I 
> dhcpcd from the command line, but I don't see any calls 
> arriving at my dhcpd server and the dhcpcd call times out.
>
> Any suggestions as to how to step through this?
>
> I have b cards. I don't know whether they're wpa-able. The 
> list of drivers in wpa_supplicant would seem to cover what I 
> have (PrismII) (I have an orinoco gold for which I can't 
> tell if I have a wpa_supplicant driver or not). I can 
> connect just fine to my local wap using my old wep scripts 
> (wireless utils or whatever)
>
> I'm using kernel 2.6.21.5
> wpa_supplicant 0.5.8
> wireless tools 28
>
> Thanks Joe
>   

-- 
TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ  : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/







      ____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/