Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[gentoo-user] Wireless...

1 view
Skip to first unread message

BRM

unread,
Dec 2, 2009, 11:10:02 PM12/2/09
to
I have wireless working (b43legacy driver for the Dell Wireless Broadcom) through a static configuration in /etc/conf.d/net - basically:

essid_wlan0="myWLAN"
key_MYWLAN="somekey"
config_MYWLAN=( "dhcp" )
preferred_APS= ( "myWLAN" )

I would like to use a tool like WPA Supplicant instead so I can have a more dynamic configuration.
I've tried to setup WPA supplicant but haven't been able to get it to work.

My last attempt was with:

modules=( "wpa_supplicant" )
wpa_supplicant_wlan0="-Dwext"
wpa_timeout_wlan0=15

I also tried the iwconfig setup:

modules=( "iwconfig" )
iwconfig_wlan0="mode managed"
wpa_timeout_wlan0=15

Both these were based on configurations I found while researching gentoo wireless configurations:

http://en.gentoo-wiki.com/wiki/Wireless_Networking

the wpa_supplicant man page possibly suggests uses "-Dbroadcom", but the following supports "-Dwext" since I have the b43legacy driver working (firmware extracted using b43-fwcutter a while back; dmesg reports version 0x127).

http://linuxwireless.org/en/users/Drivers/b43

I have both the iwconfig utilities and wpa supplicant installed. When I used wpa supplicant with either configuration it would just keep searching.

Now, my wireless configuration is currently WEP; and I'd like to upgrade to WPA/WPA2 once I can get a wireless tool on the system as well.

Is there anything I'm doing wrong with the configuration above?

Also - what is the correct GUI for configuring connections under KDE4? I know of the WPA Supplicant GUI; and the GNOME GUI; but would like something under more directly KDE4.

KNemo just puts up monitors that are pretty useless (though look pretty).

TIA,

Ben

P.S. It seems my Linksys WRT54G v3 needs a firmware update for WPA2. So right now, I'd just like to be able to configure dynamically for my WEP network; then I'll focus on going to WPA/WPA2.

Crístian Viana

unread,
Dec 3, 2009, 1:10:01 AM12/3/09
to
KDE 4 doesn't have an official network manager yet. you can use net-misc/wicd, it works nice.
--
Crístian Deives dos Santos Viana [aka CD1]
Sent from Campinas, SP, Brazil

Zeerak Waseem

unread,
Dec 3, 2009, 1:10:01 AM12/3/09
to
This is my etc/conf.d/net file:

modules=( "wpa_supplicant" )
wpa_supplicant_wlan0="-Dwext"

preferred_aps=("ESSID1" "ESSID2")
essid_wlan0="any"

All specific stuff is in /wpa_supplicant/supplicant.conf

Zeerak


--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Mike Edenfield

unread,
Dec 3, 2009, 9:10:03 AM12/3/09
to
On 12/2/2009 9:17 PM, BRM wrote:
> I have wireless working (b43legacy driver for the Dell Wireless Broadcom) through a static configuration in /etc/conf.d/net - basically:
>
> essid_wlan0="myWLAN"
> key_MYWLAN="somekey"
> config_MYWLAN=( "dhcp" )
> preferred_APS= ( "myWLAN" )
>
> I would like to use a tool like WPA Supplicant instead so I can have a more dynamic configuration.
> I've tried to setup WPA supplicant but haven't been able to get it to work.

Probably not what you wanted to hear, but I had the exact
same problem with the Dell bcm-based adapter in my Inspiron
laptop. It would work fine for open wireless and
WEP-secured wireless, but wouldn't associated with a
WPA-secured access point.

Eventually I spent about $30 to purchase an iwl3945
replacement from Dell, which worked fine, and never looked back.

--Mike

BRM

unread,
Dec 3, 2009, 7:10:01 PM12/3/09
to
----- Original Message ----

Thanks for the heads up.
At this point, I'll be happy if I can just get WEP working using WPA Supplicant/WiCD/etc. instead of a root user centric configuration file.

Ben

BRM

unread,
Jan 6, 2010, 1:10:02 PM1/6/10
to
----- Original Message ----

Well, it seems to be something with my home network; not sure what.
Over the holidays I did some traveling and took my laptop with me.
I was able to connect to other WEP networks just fine using WPA Supplicant;
however, when I got home I couldn't get WPA Supplicant to work with my home network and
had to revert back to setting it up via /etc/conf.d/net.

My home wireless network is a Linksys WRT54G version 3 hardware, with slightly outdated software (by 1 or 2 releases).
SSID is visible. It seems to find it, but then loses it pretty quickly and I have to restart wlan0 before I can try again.
Works fine when using a static WEP configuration though (e.g. no WPA Supplicant/WiCD/etc.).

Not sure what to look at next, but this is going to drive me a bit crazy.

Ben

0 new messages