Talk:Linux Wireless

From The University of Akron Support Wiki
Jump to: navigation, search

Broadcom

more LEAP successes

Misha Koshelev
Tue, 05 Sep 2006 16:41:17 -0700

Alright, just wanted to let y'all know I installed NetworkManager CVS on
my friend's newly Ubuntized laptop (Compaq Presario 5xxxUS something I
think it was like a $600 or $700 laptop) with a Broadcom wireless card,
and LEAP works great. I had to install the latest stable version of
ndiswrapper from sourceforge.org and after that it worked great with the
supplied Windows network drivers. This was significant to me because in
Windows on the same laptop with the same drivers and the same network
adapter I was not able to figure out a way to use LEAP networking (and I
don't think such a way exists), so it's pretty neat that my friend can
use LEAP on Linux but not on Windows.

Just thought I'd share.

Misha

From http://www.mail-archive.com/networkmanager-list@gnome.org/msg04283.html

I am willing to try this with my new laptop once I get it setup in Linux. --Dustin 14:39, 29 September 2006 (EDT)

So far it still attempts to authenicate to a Mac Address of zeros. Tried older and newer wpa_supplicant, I think its a issue between broadcom drivers and ndiswrapper. --Dustin 18:35, 31 October 2006 (EST)

Kwifimanager

Doesn't seem to scan with a Broadcom 4311 using ndiswrapper. iwconfig seems to work for non-leap access points. --Dustin 18:35, 31 October 2006 (EST)

This is not a good solution unless you are only connecting to WEP and open networks. --Dustin 10:29, 10 April 2007 (EDT)

NetworkManger tested

I tested NetworkManager using the newest ndiswrapper. This does not work with LEAP and the Broadcom 4318 card. --23:22, 31 October 2006 User:Tce3

Ubuntu 7.10's NetworkManager now works with leap, as does knetworkmanager. The instructions on the article are for knetworkmanager but I will add instructions for NetworkManager in the near future User:Mec9

PEAP settings

File: /etc/wpa_supplicant.conf
eapol_version=1
ap_scan=2
fast_reauth=1
network={
    ssid="tsunami"
    key_mgmt=IEEE8021X
    scan_ssid=1
    eap=PEAP
    identity="uanetid"
    password="passwordhere"
    phase1="peaplabel=0"
    phase2="auth=MSCHAPV2"
 }

Broadcom/Dell support

PEAP Authentication with Broadcom based wireless cards (included Dells) is hit-or-miss at best. PEAP authentication works with out any known issues with the Intel Based cards.

Augment with AutoNDIS?

Possibly rewrite or augment with instructions on using the new AutoNDIS utility? https://launchpad.net/auto-ndiswrapprer