Fedora Linux Support Community & Resources Center
Old 17th September 2009, 12:02 AM
snhemanthm Offline
Registered User
Join Date: Sep 2009
Posts: 7
Not able to connect to WPA2 secure wireless networks with broadcom 4312

Hi All,

I have a dell studio 14z with a 1397 card (broadcom 4312 b/g). I have the rpmfusion kmod-wl/broadcom-wl drivers installed since the b43 ones don't support my card. Am able to add unsecured networks using NM and connect to them but have problems connecting to my secured network at home - WPA2-PSK. NM doesn't let me add any connection with security enabled and using a tool like wlassistant causes the 'No encryption protocols were found' message when trying to connect to a password protected network (They do show up on the wlassistant list). I have wpa_supplicant installed and lsmod shows up the lib80211_crypto_tkip module (I forgot the exact name) along with the wl module. I have the latest stable kernel and the corresponding kmod-wl from rpmfusion installed. All packages are x86_64 btw. Please help me out. I have already removed any potential conflicting drivers like akmod-wl, b43, ssb etc

Reply With Quote
Old 2nd February 2012, 03:43 PM
oliverfoster Offline
Registered User
Join Date: Feb 2012
Location: England, Brighton
Posts: 1
Re: Not able to connect to WPA2 secure wireless networks with broadcom 4312

I'm not quite sure where else to put this information, so if anyone has any suggestions and it's useful I'll repost it elsewhere.

If have a 14E4:4312 BCM4311 mini pci wireless card for my netbook, it was originally from a laptop (so I'll not include my netbook specs).
I'm using F16 (Fedora 16) : Linux 3.2.2-1.fc16.i686 #1 SMP Thu Jan 26 03:38:31 UTC 2012 i686 i686 i386 GNU/Linux

Originally I couldn't connect to a WPA-Enterprise network so I used b43-fwcuter from the yum to try to cut in other firmware. I found that the b43-fwcutter in yum wasn't version 015 as it claimed and therefore could not install the latest broadcom firmware.

I managed to install the latest firmware version that is compatible with b43-fwcutter that comes with F16 but I had problems with 'destination host unreachable' on a ping google.com after a few minutes of being connected.

Following the "If you are using the b43 driver from 3.2 kernel or newer:" section of http://linuxwireless.org/en/users/Drivers/b43 i was able to get the correct version of b43-fwcutter although it has to be run from it's installation directory /usr/sbin/b43-fwcutter (i believe).

At this point I had the 5.100.138 666.2 version firmware.

This solved my connection issue, but the NetworkManager was asking me for authorisation every few minutes, suggesting that it was losing the connection or something similar.

To solve this is looked at the iwconfig options and found that iwconfig wlan0 retry 40 worked well (20 also worked but I thought I'd jump it up just to be on the safe side). This is set to 7 normally.

I then added this to /etc/sysconfig/network-scripts/ifup-wireless so the file looks like the file at the bottom of this message.

This has completely solved my disconnect/reconnect/connection issues with WPA-enterprise. I had no problem connecting to WEP and unsecured networks earlier and still do not.

Hope this helps someone.

# Network Interface Configuration System
# Copyright (c) 1996-2009 Red Hat, Inc. all rights reserved.
# Based on PCMCIA wireless script by (David Hinds/Jean Tourrilhes)
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License, version 2,
# as published by the Free Software Foundation.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
# Configure wireless network device options. See iwconfig(8) for more info.
# Valid variables:
# MODE: Ad-Hoc, Managed, etc.
# ESSID: Name of the wireless network
# NWID: Name of this machine on the network. Hostname is default
# FREQ: Frequency to operate on. See CHANNEL
# CHANNEL: Numbered frequency to operate on. See FREQ
# SENS: Sensitivity threshold for packet rejection.
# RATE: Transfer rate. Usually one of Auto, 11, 5, 2, or 1.
# KEY: Encryption key for WEP.
# RTS: Explicit RTS handshake. Usually not specified (auto)
# FRAG: Fragmentation threshold to split packets. Usually not specified.
# SPYIPS: List of IP addresses to "spy" on for link performance stats.
# IWCONFIG: Extra parameters to pass directly to IWCONFIG
# SECURITYMODE: Security mode, e.g: 'open' or 'restricted'
# IWPRIV: Extra parameters to pass directly to IWPRIV

# Only meant to be called from ifup.

# Mode need to be first : some settings apply only in a specific mode !
if [ -n "$MODE" ] ; then
iwconfig $DEVICE mode $MODE

# Set link up (some cards require this.)
/sbin/ip link set dev ${DEVICE} up

# This is a bit hackish, but should do the job right...
if [ -n "$ESSID" -o -n "$MODE" ] ; then
iwconfig $DEVICE nick "$NICKNAME" >/dev/null 2>&1
# Regular stuff...
if [ -n "$NWID" ] ; then
iwconfig $DEVICE nwid $NWID
if [ -n "$FREQ" -a "$MODE" != "Managed" ] ; then
iwconfig $DEVICE freq $FREQ
elif [ -n "$CHANNEL" -a "$MODE" != "Managed" ] ; then
iwconfig $DEVICE channel $CHANNEL
if [ -n "$SENS" ] ; then
iwconfig $DEVICE sens $SENS
if [ -n "$RATE" ] ; then
iwconfig $DEVICE rate "$RATE"
if [ -n "$KEY" -o -n "$KEY1" -o -n "$KEY2" -o -n "$KEY3" -o -n "$KEY4" ] ; then
[ -n "$KEY1" ] && iwconfig $DEVICE key "[1]" $KEY1
[ -n "$KEY2" ] && iwconfig $DEVICE key "[2]" $KEY2
[ -n "$KEY3" ] && iwconfig $DEVICE key "[3]" $KEY3
[ -n "$KEY4" ] && iwconfig $DEVICE key "[4]" $KEY4
[ -n "$DEFAULTKEY" ] && iwconfig $DEVICE key "[${DEFAULTKEY}]"
[ -n "$KEY" ] && iwconfig $DEVICE key $KEY
iwconfig $DEVICE key off
if [ -n "$SECURITYMODE" ]; then
if [ -n "$RTS" ] ; then
iwconfig $DEVICE rts $RTS
if [ -n "$FRAG" ] ; then
iwconfig $DEVICE frag $FRAG

# More specific parameters passed directly to IWCONFIG
if [ -n "$IWCONFIG" ] ; then

iwconfig $DEVICE retry 40

if [ -n "$SPYIPS" ] ; then
for IP in $SPYIPS; do
iwspy $DEVICE + $IP
if [ -n "$IWPRIV" ] ; then

# ESSID need to be last : most device re-perform the scanning/discovery
# when this is set, and things like encryption keys are better be
# defined if we want to discover the right set of APs/nodes.
if [ -n "$ESSID" ] ; then
iwconfig $DEVICE essid "$ESSID"
# use any essid
iwconfig $DEVICE essid any >/dev/null 2>&1

Last edited by oliverfoster; 2nd February 2012 at 03:54 PM. Reason: Additional important problem symptoms
Reply With Quote

4312, broadcom, connect, networks, secure, wireless, wpa2

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Wireless connects and drops secure networks (broadcom) abovenbeyond Hardware & Laptops 2 29th August 2008 06:02 PM
fedora 9 - connect to secure wireless network with broadcom drivers rphegde Servers & Networking 6 25th May 2008 10:24 AM
Broadcom 4603 Will see Networks but will not connect! SummerShudder Hardware & Laptops 1 5th May 2008 08:37 AM
wireless-broadcom 4312 help! arthur.m Servers & Networking 17 2nd April 2008 03:36 AM
Broadcom 4312 wireless configuration: How to buchalkalan Hardware & Laptops 9 9th December 2007 11:11 AM

Current GMT-time: 00:32 (Wednesday, 23-08-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat