wireless network configuration - archwiki

6/22/2014 Wireless network configuration - ArchWiki

https://wiki.archlinux.org/index.php?title=Wireless_network_configuration&printable=yes 1/21

Relatedarticles

Networkconfiguration

Softwareaccesspoint

Adhocnetworking

Internetsharing

WirelessnetworkconfigurationFromArchWiki

Configuringwirelessisatwopartprocessthefirstpartistoidentifyandensurethecorrectdriverforyourwirelessdeviceisinstalled(theyareavailableontheinstallationmedia,butoftenhavetobeinstalledexplicitly),andtoconfiguretheinterface.Thesecondischoosingamethodofmanagingwirelessconnections.Thisarticlecoversbothparts,andprovidesadditionallinkstowirelessmanagementtools.

Contents

1Devicedriver1.1Checkthedriverstatus1.2Installingdriver/firmware

2Wirelessmanagement2.1Manualsetup

2.1.1Gettingsomeusefulinformation2.1.2Interfaceactivation2.1.3Accesspointdiscovery2.1.4Operatingmode2.1.5Association2.1.6GettinganIPaddress2.1.7Customstartupscripts/services

2.1.7.1Manualwirelessconnectionatbootusingsystemdanddhcpcd2.1.7.2Systemdwithwpa_supplicantandstaticIP

2.2Automaticsetup2.2.1Connman2.2.2Netctl2.2.3Wicd2.2.4NetworkManager2.2.5WiFiRadar

3Troubleshooting3.1Rfkillcaveat3.2Respectingtheregulatorydomain3.3ObservingLogs3.4Powersaving3.5FailedtogetIPaddress3.6Connectionalwaystimesout

3.6.1Loweringtherate3.6.2Loweringthetxpower3.6.3Settingrtsandfragmentationthresholds

3.7Randomdisconnections3.7.1Cause#13.7.2Cause#23.7.3Cause#3

4Troubleshootingdriversandfirmware4.1Ralink

4.1.1rt2x004.1.2rt30904.1.3rt32904.1.4rt35734.1.5rt5572

4.2Realtek4.2.1rtl8192cu4.2.2rtl8192e4.2.3rtl8188eu4.2.4rtl8723be



4.3Atheros4.3.1ath5k4.3.2ath9k

4.3.2.1ASUS4.4Intel

4.4.1ipw2100andipw22004.4.2iwlegacy4.4.3iwlwifi4.4.4DisablingLEDblink

4.5Broadcom4.6Otherdrivers/devices

4.6.1Tendaw322u4.6.2orinoco4.6.3prism544.6.4ACX100/1114.6.5zd1211rw4.6.6hostap_cs

4.7ndiswrapper4.8compatdriverspatched

5Seealso

Devicedriver

ThedefaultArchLinuxkernelismodular,meaningmanyofthedriversformachinehardwareresideontheharddriveandareavailableasmodules.Atboot,udevtakesaninventoryofyourhardwareandloadsappropriatemodules(drivers)foryourcorrespondinghardware,whichwillinturnallowcreationofanetworkinterface.

Somewirelesschipsetsalsorequirefirmware,inadditiontoacorrespondingdriver.Manyfirmwareimagesareprovidedbythelinux-firmware (https://www.archlinux.org/packages/?name=linux-firmware)packagewhichisinstalledbydefault,however,proprietaryfirmwareimagesarenotincludedandhavetobeinstalledseparately.Thisisdescribedin#Installingdriver/firmware.

Note:Udevisnotperfect.Ifthepropermoduleisnotloadedbyudevonboot,simplyloaditmanually.Notealsothatudevmayoccasionallyloadmorethanonedriverforadevice,andtheresultingconflictwillpreventsuccessfulconfiguration.Makesuretoblacklisttheunwantedmodule.

Tip:Thoughnotstrictlyrequired,it'sagoodideatofirstinstalluserspacetoolsmentionedin#Manualsetup,especiallywhensomeproblemshouldappear.

Checkthedriverstatus

Tocheckifthedriverforyourcardhasbeenloaded,checktheoutputofthelspci -kor lsusb -vcommand,dependingonifthecardisconnectedbyPCI(e)orUSB.Youshouldseethatsomekerneldriverisinuse,forexample:

$ lspci -k

06:00.0 Network controller: Intel Corporation WiFi Link 5100 Subsystem: Intel Corporation WiFi Link 5100 AGN Kernel driver in use: iwlwifi Kernel modules: iwlwifi

Note:IfthecardisaUSBdevice,runningdmesg | grep usbcoreshouldgivesomethinglikeusbcore: registered new interface driver rtl8187asoutput.

Alsochecktheoutputofip linkcommandtoseeifawirelessinterface(usuallyitstartswiththeletter"w",e.g.wlp2s1)wascreated.Thenbringtheinterfaceupwith ip link set interface up.Forexample,assumingtheinterfaceiswlan0:



# ip link set wlan0 up

Ifyougetthiserrormessage:SIOCSIFFLAGS: No such file or directory,itmostcertainlymeansthatyourwirelesschipsetrequiresafirmwaretofunction.

Checkkernelmessagesforfirmwarebeingloaded:

$ dmesg | grep firmware

[ 7.148259] iwlwifi 0000:02:00.0: loaded firmware version 39.30.4.1 build 35138 op_mode iwldvm

Ifthereisnorelevantoutput,checkthemessagesforthefulloutputforthemoduleyouidentifiedearlier(iwlwifiinthisexample)toidentifytherelevantmessageorfurtherissues:

$ dmesg | grep iwlwifi

[ 12.342694] iwlwifi 0000:02:00.0: irq 44 for MSI/MSI-X[ 12.353466] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 35138 op_mode iwldvm[ 12.430317] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled...[ 12.430341] iwlwifi 0000:02:00.0: Detected Intel(R) Corporation WiFi Link 5100 AGN, REV=0x6B

Ifthekernelmoduleissuccessfullyloadedandtheinterfaceisup,youcanskipthenextsection.

Installingdriver/firmware

Checkthefollowingliststodiscoverifyourcardissupported:

TheUbuntuWiki(https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported)hasagoodlistofwirelesscardsandwhetherornottheyaresupportedeitherintheLinuxkernelorbyauserspacedriver(includesdrivername).LinuxWirelessSupport(http://linuxwless.passys.nl/)andTheLinuxQuestions'HardwareCompatibilityList(http://www.linuxquestions.org/hcl/index.php?cat=10)(HCL)alsohaveagooddatabaseofkernelfriendlyhardware.Thekernelpage(http://wireless.kernel.org/en/users/Devices)additionallyhasamatrixofsupportedhardware.

Ifyourwirelesscardislistedabove,followthe#Troubleshootingdriversandfirmwaresubsectionofthispage,whichcontainsinformationaboutinstallingdriversandfirmwareofsomespecificwirelesscards.Thencheckthedriverstatusagain.

Ifyourwirelesscardisnotlistedabove,itislikelysupportedonlyunderWindows(someBroadcom,3com,etc).Forthese,youcantrytousendiswrapper.

Wirelessmanagement

Assumingthatyourdriversareinstalledandworkingproperly,youwillneedtochooseamethodofmanagingyourwirelessconnections.Thefollowingsubsectionswillhelpyoudecide.

Procedureandtoolsrequiredwilldependonseveralfactors:

Thedesirednatureofconfigurationmanagementfromacompletelymanualcommandlineproceduretoanautomatedsolutionwithgraphicalfrontends.Theencryptiontype(orlackthereof)whichprotectsthewirelessnetwork.Theneedfornetworkprofiles,ifthecomputerwillfrequentlychangenetworks(suchasalaptop).

Tip:

Whateverisyourchoice,youshouldtrytoconnectusingthemanualmethodfirst.Thiswillhelpyouunderstandthedifferentstepsthatarerequiredandtroubleshootpossibleproblems.Ifpossible(e.g.ifyoumanageyourWiFiaccesspoint),tryconnectingwithnoencryption,tocheckthat



everythingworks.Thentryusingencryption,eitherWEP(simpletoconfigure,butcrackableinamatterofseconds),WPAorWPA2.

Thefollowingtableshowsthedifferentmethodsthatcanbeusedtoactivateandmanageawirelessconnection,dependingontheencryptionandmanagementtypes,andthevarioustoolsthatarerequired.Althoughtheremaybeotherpossibilities,thesearethemostfrequentlyused:

Managementmethod

Interfaceactivation

Wirelessconnectionmanagement(/=alternatives)

AssigningIPaddress(/=alternatives)

Manuallymanaged,withnoorWEPencryption

ip

iw(https://www.archlinux.org/packages/?name=iw)/iwconfig(https://www.archlinux.org/packages/?name=wireless_tools)

ip/dhcpcd/dhclient(https://www.archlinux.org/packages/?name=dhclient)

Manuallymanaged,withWPAorWPA2PSKencryption

ip

iw(https://www.archlinux.org/packages/?name=iw)/iwconfig(https://www.archlinux.org/packages/?name=wireless_tools)+wpa_supplicant

ip/dhcpcd/dhclient(https://www.archlinux.org/packages/?name=dhclient)

Automaticallymanaged,withnetworkprofilessupport

netctl,Wicd,NetworkManager,etc.

Thesetoolspullintherequireddependenciesfromthelistofpackagesinthemanualmethod.

Manualsetup

Justlikeothernetworkinterfaces,thewirelessonesarecontrolledwithipfromtheiproute2(https://www.archlinux.org/packages/?name=iproute2)package.

Youwillneedtoinstallabasicsetoftoolsformanagingthewirelessconnection,either:

iw (https://www.archlinux.org/packages/?name=iw)thecurrentnl80211standard,butnotallwirelesschip'smodulessupportit

or

wireless_tools (https://www.archlinux.org/packages/?name=wireless_tools)currentlydeprecated,butstillwidelysupported.

AndforWPA/WPA2encryption,youwillalsoneed:

wpa_supplicant (https://www.archlinux.org/packages/?name=wpa_supplicant)

Thetablebelowgivesanoverviewofcomparablecommandsforiwand wireless_tools(see[1](http://wireless.kernel.org/en/users/Documentation/iw/replaceiwconfig)formoreexamples).Theseuserspacetoolsworkextremelywellandallowcompletemanualcontrolofwirelessconnection.

Note:

Examplesinthissectionassumethatyourwirelessdeviceiswlan0andthatyouareconnectingto your_essidwifiaccesspoint.Replacebothaccordingly.Notethatmostofthecommandshavetobeexecutedwithrootpermissions.Executedwithnormaluserrights,someofthecommands(e.g.iwlist),willexitwithouterrorbutnotproducethecorrectoutputeither,whichcanbeconfusing.



iwcommand wireless_toolscommand Descriptioniwdevwlan0link iwconfigwlan0 Gettinglinkstatus.iwdevwlan0scan iwlistwlan0scan Scanningforavailableaccesspoints.iwdevwlan0settypeibss iwconfigwlan0modeadhoc Settingtheoperationmodetoadhoc.iwdevwlan0connectyour_essid iwconfigwlan0essidyour_essid Connectingtoopennetwork.iwdevwlan0connectyour_essid2432

iwconfigwlan0essidyour_essidfreq2432M

Connectingtoopennetworkspecifyingchannel.

iwdevwlan0connectyour_essidkey0:your_key

iwconfigwlan0essidyour_essidkeyyour_key

ConnectingtoWEPencryptednetworkusinghexadecimalkey.

iwdevwlan0connectyour_essidkey0:your_key

iwconfigwlan0essidyour_essidkeys:your_key

ConnectingtoWEPencryptednetworkusingASCIIkey.

iwdevwlan0setpower_saveon iwconfigwlan0poweron Enablingpowersave.

Note:Dependingonyourhardwareandencryptiontype,someofthesestepsmaynotbenecessary.Somecardsareknowntorequireinterfaceactivationand/oraccesspointscanningbeforebeingassociatedtoanaccesspointandbeinggivenanIPaddress.Someexperimentationmayberequired.Forinstance,WPA/WPA2usersmaytrytodirectlyactivatetheirwirelessnetworkfromstep#Association.

Gettingsomeusefulinformation

Tip:Seeofficialdocumentation(http://wireless.kernel.org/en/users/Documentation/iw)oftheiwtoolformoreexamples.

Firstyouneedtofindthenameofwirelessinterface.Youcandoitwithfollowingcommand:

$ iw dev

phy#0 Interface wlan0 ifindex 3 wdev 0x1 addr 12:34:56:78:9a:bc type managed channel 1 (2412 MHz), width: 40 MHz, center1: 2422 MHz

Tochecklinkstatus,usefollowingcommand.ExampleoutputwhennotconnectedtoanAP:

$ iw dev wlan0 link

Not connected.

WhenconnectedtoanAP,youwillseesomethinglike:

$ iw dev wlan0 link

Connected to 12:34:56:78:9a:bc (on wlan0) SSID: MyESSID freq: 2412 RX: 33016518 bytes (152703 packets) TX: 2024638 bytes (11477 packets) signal: -53 dBm tx bitrate: 150.0 MBit/s MCS 7 40MHz short GI

bss flags: short-preamble short-slot-time dtim period: 1 beacon int: 100

Youcangetstatisticinformation,suchastheamountoftx/rxbytes,signalstrengthetc.,withfollowingcommand:

$ iw dev wlan0 station dump



Station 12:34:56:78:9a:bc (on wlan0) inactive time: 1450 ms rx bytes: 24668671 rx packets: 114373 tx bytes: 1606991 tx packets: 8557 tx retries: 623 tx failed: 1425 signal: -52 dBm signal avg: -53 dBm tx bitrate: 150.0 MBit/s MCS 7 40MHz short GI authorized: yes authenticated: yes preamble: long WMM/WME: yes MFP: no TDLS peer: no

Interfaceactivation

(Usuallynotrequired)

Somecardsrequirethatthekernelinterfacebeactivatedbeforeyoucanuseiworwireless_tools:

# ip link set wlan0 up

Note:IfyougeterrorslikeRTNETLINK answers: Operation not possible due to RF-kill,makesurethathardwareswitchison.See#Rfkillcaveatfordetails.

Toverifythattheinterfaceisup,inspecttheoutputofthefollowingcommand:

# ip link show wlan0

3: wlan0: mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000 link/ether 12:34:56:78:9a:bc brd ff:ff:ff:ff:ff:ff

TheUPin iswhatindicatestheinterfaceisup,notthelater state DOWN.

Accesspointdiscovery

Seewhataccesspointsareavailable:

# iw dev wlan0 scan | less

Note:IfitdisplaysInterface doesn't support scanning,thenyouprobablyforgottoinstallthefirmware.Insomecasesthismessageisalsodisplayedwhennotrunningiwasroot.

Tip:Dependingonyourlocation,youmightneedtosetthecorrectregulatorydomaininordertoseeallavailablenetworks.

Theimportantpointstocheck:

SSID:thenameofthenetwork.Signal:isreportedinawirelesspowerratioindbm(e.g.from100to0).Thecloserthenegativevaluegetstozero,thebetterthesignal.Observingthereportedpoweronagoodqualitylinkandabadoneshouldgiveanideaabouttheindividualrange.Security:itisnotreporteddirectly,checkthelinestartingwithcapability.Ifthereis Privacy,forexamplecapability: ESS Privacy ShortSlotTime (0x0411),thenthenetworkisprotectedsomehow.

IfyouseeanRSNinformationblock,thenthenetworkisprotectedbyRobustSecurityNetworkprotocol,alsoknownasWPA2.IfyouseeanWPAinformationblock,thenthenetworkisprotectedbyWiFiProtectedAccessprotocol.IntheRSNand WPAblocksyoumayfindthefollowinginformation:



Groupcipher:valueinTKIP,CCMP,both,others.Pairwiseciphers:valueinTKIP,CCMP,both,others.NotnecessarilythesamevaluethanGroupcipher.Authenticationsuites:valueinPSK,802.1x,others.Forhomerouter,you'llusuallyfindPSK(i.e.passphrase).Inuniversities,youaremorelikelytofind802.1xsuitewhichrequiresloginandpassword.Thenyouwillneedtoknowwhichkeymanagementisinuse(e.g.EAP),andwhatencapsulationituses(e.g.PEAP).FindmoredetailsatWikipedia:Authenticationprotocolandthesubarticles.

IfyoudonotseeneitherRSNnor WPAblocksbutthereis Privacy,thenWEPisused.

Operatingmode

(Optional,butmayberequired)

Atthisstepyoumightneedtosettheproperoperatingmodeofthewirelesscard.Morespecifically,ifyouaregoingtoconnectanadhocnetwork,youneedtosettheoperatingmodetoibss:

# iw dev wlan0 set type ibss

Note:Changingtheoperatingmodeonsomecardsmightrequirethewirelessinterfacetobedown(ip link set wlan0 down).

Association

Dependingontheencryption,youneedtoassociateyourwirelessdevicewiththeaccesspointtouseandpasstheencryptionkey.

Noencryption

# iw dev wlan0 connect your_essid

WEP

usingahexadecimalorASCIIkey(theformatisdistinguishedautomatically,becauseaWEPkeyhasafixedlength):

# iw dev wlan0 connect your_essid key 0:your_key

usingahexadecimalorASCIIkey,specifyingthethirdsetupkeyasdefault(keysarecountedfromzero,fourarepossible):

# iw dev wlan0 connect your_essid key d:2:your_key

WPA/WPA2

Accordingtowhatyougotfrom#Accesspointdiscovery,issuethiscommand:

# wpa_supplicant -i interface -c



GettinganIPaddress

Note:SeeNetworkconfiguration#ConfiguretheIPaddressformoreexamples.Thispartisidentical.

Finally,provideanIPaddresstothenetworkinterface.Simpleexamplesare:

# dhcpcd wlan0

or

# dhclient wlan0

forDHCP,or

# ip addr add 192.168.0.2/24 dev wlan0# ip route add default via 192.168.0.1

forstaticIPaddressing.

Tip:dhcpcdcontainsahook(enabledbydefault)toautomaticallylaunchWPAsupplicantonwirelessinterfaces.Itisstartedonlyifaconfigurationfileat/etc/wpa_supplicant/wpa_supplicant.confexistsandnowpa_supplicantprocessislisteningonthatinterface.Inmostcases,youdonotneedtocreateanycustomservice,justenabledhcpcd@interface.

Customstartupscripts/services

Althoughthemanualconfigurationmethodwillhelptroubleshootwirelessproblems,youwillhavetoretypeeverycommandeachtimeyoureboot.Youcanalsoquicklywriteashellscripttoautomatethewholeprocess,whichisstillaquiteconvenientwayofmanagingnetworkconnectionwhilekeepingfullcontroloveryourconfiguration.Youcanfindsomeexamplesinthissection.

Manualwirelessconnectionatbootusingsystemdanddhcpcd

Thisexampleusessystemdforstartup,WPAsupplicantforconnecting,anddhcpcd(https://www.archlinux.org/packages/?name=dhcpcd)forassigninganIPaddress.

Note:Makesurethatwpa_supplicant (https://www.archlinux.org/packages/?name=wpa_supplicant)isinstalledandcreate/etc/wpa_supplicant/wpa_supplicant.conf.SeeWPAsupplicantfordetails.

Createasystemdunit,e.g/etc/systemd/system/[email protected]:

/etc/systemd/system/[email protected]

[Unit]Description=Wireless network connectivity (%i)Wants=network.targetBefore=network.targetBindsTo=sys-subsystem-net-devices-%i.deviceAfter=sys-subsystem-net-devices-%i.device

[Service]Type=oneshotRemainAfterExit=yes

ExecStart=/usr/bin/ip link set dev %i upExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.confExecStart=/usr/bin/dhcpcd %i

ExecStop=/usr/bin/ip link set dev %i down

[Install]WantedBy=multi-user.target



Startand/orenabletheunitasdescribedinsystemd#Usingunits,remembertopassthenameoftheinterface:

# systemctl enable [email protected]# systemctl start [email protected]

Systemdwithwpa_supplicantandstaticIP

Note:Makesurethatwpa_supplicant (https://www.archlinux.org/packages/?name=wpa_supplicant)isinstalledandcreateacustom/etc/wpa_supplicant/wpa_supplicant.conf.SeeWPAsupplicantfordetails.

Firstcreateconfigurationfileforthesystemdservice,replaceinterfacewithproperinterfacename:

/etc/conf.d/network-wireless@interface

address=192.168.0.10netmask=24broadcast=192.168.0.255gateway=192.168.0.1

Createasystemdunitfile:

/etc/systemd/system/[email protected]

[Unit]Description=Wireless network connectivity (%i)Wants=network.targetBefore=network.targetBindsTo=sys-subsystem-net-devices-%i.deviceAfter=sys-subsystem-net-devices-%i.device

[Service]Type=oneshotRemainAfterExit=yesEnvironmentFile=/etc/conf.d/network-wireless@%i

ExecStart=/usr/bin/ip link set dev %i upExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.confExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %iExecStart=/usr/bin/ip route add default via ${gateway}

ExecStop=/usr/bin/ip addr flush dev %iExecStop=/usr/bin/ip link set dev %i down

[Install]WantedBy=multi-user.target

Enabletheunitandstartit,passingthenameoftheinterface:

# systemctl enable [email protected]# systemctl start [email protected]

Automaticsetup

Therearemanysolutionstochoosefrom,butrememberthatallofthemaremutuallyexclusiveyoushouldnotruntwodaemonssimultaneously.Thefollowingtablecomparesthedifferentconnectionmanagers,additionalnotesareinsubsectionsbelow.



ConnectionmanagerNetworkprofilessupport

Roaming(autoconnectdroppedorchangedlocation)

PPPsupport(e.g.3Gmodem)

OfficialGUI Consoletools

Connman Yes Yes Yes No connmanctlNetctl Yes Yes Yes No netctl, wifi-menuNetworkManager Yes Yes Yes Yes nmcliWicd Yes Yes No Yes wicd-curses

Connman

ConnManisanalternativetoNetworkManagerandWicd,designedtobelightonresourcesmakingitidealfornetbooks,andothermobiledevices.ItismodularindesigntakesadvandageofthedbusAPIandprovidesproperabstractionontopofwpa_supplicant.

See:Connman

Netctl

netctlisareplacementfornetcfgdesignedtoworkwithsystemd.Itusesaprofilebasedsetupandiscapableofdetectionandconnectiontoawiderangeofnetworktypes.Thisisnoharderthanusinggraphicaltools.

See:Netctl

Wicd

Wicdisanetworkmanagerthatcanhandlebothwirelessandwiredconnections.ItiswritteninPythonandGtkwithfewerdependenciesthanNetworkManager,makingitanidealsolutionforlightweightdesktopusers.

See:Wicd

Note:wicdmaycauseexcessivedroppedconnectionswithsomedrivers,whileNetworkManagermightworkbetter.

NetworkManager

NetworkManagerisanadvancednetworkmanagementtoolthatisenabledbydefaultinmostpopularGNU/Linuxdistributions.Inadditiontomanagingwiredconnections,NetworkManagerprovidesworryfreewirelessroamingwithaneasytouseGUIprogramforselectingyourdesirednetwork.

See:NetworkManager

Note:GNOME'snetwork-manager-applet (https://www.archlinux.org/packages/?name=network-manager-applet)alsoworksunderXfceifyouinstallxfce4-xfapplet-plugin(https://aur.archlinux.org/packages/xfce4-xfapplet-plugin/)(availableintheAUR)first.Additionally,thereareappletsavailableforKDE.

WiFiRadar

WiFiRadarisaPython/PyGTK2utilityformanagingwireless(andonlywireless)profiles.Itenablesyoutoscanforavailablenetworksandcreateprofilesforyourpreferrednetworks.

See:WifiRadar

Troubleshooting

Thissectioncontainsgeneraltroubleshootingtips,notstrictlyrelatedtoproblemswithdriversorfirmware.Forsuchtopics,seenextsection.



Rfkillcaveat

Manylaptopshaveahardwarebutton(orswitch)toturnoffwirelesscard,however,thecardcanalsobeblockedbykernel.Thiscanbehandledbyrfkill (https://www.archlinux.org/packages/?name=rfkill).Userfkilltoshowthecurrentstatus:

# rfkill list

0: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes

Ifthecardishardblocked,usethehardwarebutton(switch)tounblockit.Ifthecardisnothardblockedbutsoftblocked,usethefollowingcommand:

# rfkill unblock wifi

Note:Itispossiblethatthecardwillgofromhardblockedandsoftunblockedstateintohardunblockedandsoftblockedstatebypressingthehardwarebutton(i.e.thesoftblockedbitisjustswitchednomatterwhat).Thiscanbeadjustedbytuningsomeoptionsoftherfkillkernelmodule.

Moreinfo:http://askubuntu.com/questions/62166/siocsifflagsoperationnotpossibleduetorfkill

Respectingtheregulatorydomain

Theregulatorydomain(http://en.wikipedia.org/wiki/IEEE_802.11#Regulatory_domains_and_legal_compliance),or"regdomain",isusedtoreconfigurewirelessdriverstomakesurethatwirelesshardwareusagecomplieswithlocallawssetbytheFCC,ETSIandotherorganizations.RegdomainsuseISO31661alpha2countrycodes(https://en.wikipedia.org/wiki/ISO_31661_alpha2).Forexample,theregdomainoftheUnitedStateswouldbe"US",Chinawouldbe"CN",etc.

Regdomainsaffecttheavailabilityofwirelesschannels.Inthe2.4GHzband,theallowedchannelsare111fortheUS,114forJapan,and113formostoftherestoftheworld.Inthe5GHzband,therulesforallowedchannelsaremuchmorecomplex.Ineithercase,consultthislistofWLANchannels(https://en.wikipedia.org/wiki/List_of_WLAN_channels)formoredetailedinformation.

Regdomainsalsoaffectthelimitontheeffectiveisotropicradiatedpower(EIRP)(https://en.wikipedia.org/wiki/Equivalent_isotropically_radiated_power)fromwirelessdevices.Thisisderivedfromtransmitpower/"txpower",andismeasuredindBm/mBm(1dBm=100mBm)ormW(logscale)(https://en.wikipedia.org/wiki/DBm).Inthe2.4GHzband,themaximumis30dBmintheUSandCanada,20dBminmostofEurope,and20dB30dBmfortherestoftheworld.Inthe5GHzband,maximumsareusuallylower.Consultthewirelessregdb(http://git.kernel.org/cgit/linux/kernel/git/linville/wirelessregdb.git/tree/db.txt)formoredetailedinformation(EIRPdBmvaluesareinthesecondsetofbracketsforeachline).

Misconfiguringtheregdomaincanbeusefulforexample,byallowinguseofanunusedchannelwhenotherchannelsarecrowded,orbyallowinganincreaseintxpowertowidentransmitterrange.However,thisisnotrecommendedasitcouldbreaklocallawsandcauseinterferencewithotherradiodevices.

Toconfiguretheregdomain,installcrda (https://www.archlinux.org/packages/?name=crda)andwireless-regdb (https://www.archlinux.org/packages/?name=wireless-regdb)andreboot(toreloadthecfg80211moduleandallrelateddrivers).CheckthebootlogtomakesurethatCRDAisbeingcalledbycfg80211:

$ dmesg | grep cfg80211

ThecurrentregdomaincanbesettotheUnitedStateswith:

# iw reg set US



Andqueriedwith:

$ iw reg get

Note:Yourdevicemaybesettocountry"00",whichisthe"worldregulatorydomain"andcontainsgenericsettings.Ifthiscannotbeunset,CRDAmaybemisconfigured.

However,settingtheregdomainmaynotalteryoursettings.Somedeviceshavearegdomainsetinfirmware/EEPROM,whichdictatesthelimitsofthedevice,meaningthatsettingregdomaininsoftwarecanonlyincreaserestrictions(http://wiki.openwrt.org/doc/howto/wireless.utilities#iw),notdecreasethem.Forexample,aCNdevicecouldbesetinsoftwaretotheUSregdomain,butbecauseCNhasanEIRPmaximumof20dBm,thedevicewillnotbeabletotransmitattheUSmaximumof30dBm.

Forexample,toseeiftheregdomainisbeingsetinfirmwareforanAtherosdevice:

$ dmesg | grep ath:

Forotherchipsets,itmayhelptosearchfor"EEPROM","regdomain",orsimplythenameofthedevicedriver.

Toseeifyourregdomainchangehasbeensuccessful,andtoquerythenumberofavailablechannelsandtheirallowedtransmitpower:

$ iw list | grep -A 15 Frequencies:

Amorepermanentconfigurationoftheregdomaincanbeachievedthroughediting/etc/conf.d/wireless-regdomanduncommentingtheappropriatedomain.wpa_supplicantcanalsousearegdomaininthe country=lineof/etc/wpa_supplicant.conf.

Itisalsopossibletoconfigurethecfg80211(http://wireless.kernel.org/en/developers/Documentation/cfg80211)kernelmoduletouseaspecificregdomainbyadding,forexample,options cfg80211 ieee80211_regdom=EUto/etc/modprobe.d/modprobe.conf.However,thisispartoftheoldregulatoryimplementation(http://wireless.kernel.org/en/developers/Regulatory#The_ieee80211_regdom_module_parameter).

Forfurtherinformation,readthewireless.kernel.orgregulatorydocumentation(http://wireless.kernel.org/en/developers/Regulatory/).

ObservingLogs

Agoodfirstmeasuretotroubleshootistoanalyzethesystem'slogfilesfirst.Inordernottomanuallyparsethroughthemall,itcanhelptoopenasecondterminal/consolewindowandwatchthekernelsmessageswith

$ dmesg -w

whileperformingtheaction,e.g.thewirelessassociationattempt.

Whenusingatoolfornetworkmanagement,thesamecanbedoneforsystemdwith

# journalctl -f

Frequentlyawirelesserrorisaccompaniedbyadeauthenticationwithaparticularreasoncode,forexample:

wlan0: deauthenticating from XX:XX:XX:XX:XX:XX by local choice (reason=3)

Lookingupthereasoncode(http://www.aboutcher.co.uk/2012/07/linuxwifideauthenticatedreasoncodes/)mightgiveafirsthint.



Theindividualtoolsusedinthisarticlefurtherprovideoptionsformoredetaileddebuggingoutput,whichcanbeusedinasecondstepoftheanalysis,ifrequired.

Powersaving

SeePowersaving#Networkinterfaces.

FailedtogetIPaddress

IfgettinganIPaddressrepeatedlyfailsusingthedefaultdhcpcd (https://www.archlinux.org/packages/?name=dhcpcd)client,tryinstallingandusingdhclient (https://www.archlinux.org/packages/?name=dhclient)instead.DonotforgettoselectdhclientastheprimaryDHCPclientinyourconnectionmanager!

IfyoucangetanIPaddressforawiredinterfaceandnotforawirelessinterface,trydisablingthewirelesscard'spowersavingfeatures:

# iwconfig wlan0 power off

Ifyougetatimeouterrorduetoawaitingforcarrierproblem,thenyoumighthavetosetthechannelmodetoautoforthespecificdevice:

# iwconfig wlan0 channel auto

Beforechangingthechanneltoauto,makesureyourwirelessinterfaceisdown.Afterithassuccessfullychangedit,youcanbringtheinterfaceupagainandcontinuefromthere.

Connectionalwaystimesout

Thedrivermaysufferfromalotoftxexcessiveretriesandinvalidmiscerrorsforsomeunknownreason,resultinginalotofpacketlossandkeepdisconnecting,sometimesinstantly.Followingtipsmightbehelpful.

Loweringtherate

Trysettinglowerrate,forexample5.5M:

# iwconfig wlan0 rate 5.5M auto

Fixedoptionshouldensurethatthedriverdoesnotchangetherateonitsown,thusmakingtheconnectionabitmorestable:

# iwconfig wlan0 rate 5.5M fixed

Loweringthetxpower

Youcantryloweringthetransmitpoweraswell.Thismaysavepoweraswell:

# iwconfig wlan0 txpower 5

Validsettingsarefrom0to 20, autoandoff.

Settingrtsandfragmentationthresholds

Defaultiwconfigoptionshavertsandfragmentationthresholdsoff.TheseoptionsareparticularlyusefulwhentherearemanyadjacentAPsorinanoisyenvironment.



Theminimumvalueforfragmentationvalueis256andmaximumis2346.Inmanywindowsdriversthemaximumisthedefaultvalue:

# iwconfig wlan0 frag 2346

Forrtsminimumis0,maximumis2347.Onceagainwindowsdriversoftenusemaximumasthedefault:

# iwconfig wlan0 rts 2347

Randomdisconnections

Cause#1

Ifdmesgsayswlan0: deauthenticating from MAC by local choice (reason=3)andyouloseyourWiFiconnection,itislikelythatyouhaveabittooaggressivepowersavingonyourWiFicard[2](http://us.generationnt.com/answer/gentoouserwirelessdeauthenticatingbylocalchoicehelp204640041.html).Trydisablingthewirelesscard'spowersavingfeatures:

# iwconfig wlan0 power off

SeePowersavingfortipsonhowtomakeitpermanent(justspecifyoffinsteadof on).

Ifyourcarddoesnotsupportiwconfig wlan0 power off,checktheBIOSforpowermanagementoptions.DisablingPCIExpresspowermanagementintheBIOSofaLenovoW520resolvedthisissue.

Cause#2

Ifyouareexperiencingfrequentdisconnectionsanddmesgshowsmessagessuchas

ieee80211 phy0: wlan0: No probe response from AP xx:xx:xx:xx:xx:xx after 500ms, disconnecting

trychangingthechannelbandwidthto20MHzthroughyourrouter'ssettingspage.

Cause#3

Onsomelaptopmodelswithhardwarerfkillswitches(e.g.,ThinkpadX200series),duetowearorbaddesign,theswitch(oritsconnectiontothemainboard)mightbecomelooseovertimeresultinginseeminglyrandomhardblocks/disconnectswhenyouaccidentallytouchtheswitchormovethelaptop.Thereisnosoftwaresolutiontothis,unlessyourswitchiselectricalandtheBIOSofferstheoptiontodisabletheswitch.Ifyourswitchismechanical(mostare),therearelotsofpossiblesolutions,mostofwhichaimtodisabletheswitch:Solderingthecontactpointonthemainboard/wificard,glueingorblockingtheswitch,usingascrewnuttotightentheswitchorremovingitaltogether.

Troubleshootingdriversandfirmware

Thissectioncoversmethodsandproceduresforinstallingkernelmodulesandfirmwareforspecificchipsets,thatdifferfromgenericmethod.

SeeKernelmodulesforgeneralinformationsonoperationswithmodules.

Ralink

rt2x00



UnifieddriverforRalinkchipsets(itreplacesrt2500, rt61, rt73,etc).ThisdriverhasbeenintheLinuxkernelsince2.6.24,youonlyneedtoloadtherightmoduleforthechip:rt2400pci, rt2500pci, rt2500usb,rt61pciorrt73usbwhichwillautoloadtherespective rt2x00modulestoo.

Alistofdevicessupportedbythemodulesisavailableattheproject'shomepage(http://rt2x00.serialmonkey.com/wiki/index.php/Hardware).

Additionalnotes

Sincekernel3.0,rt2x00includesalsothesedrivers:rt2800pci, rt2800usb.Sincekernel3.0,thestagingdriversrt2860staand rt2870staarereplacedbythemainlinedrivers rt2800pciandrt2800usb[3](https://git.kernel.org/?p=linux/kernel/git/torvalds/linux2.6.gita=commitdiffh=fefecc6989b4b24276797270c0e229c07be02ad3).Somedeviceshaveawiderangeofoptionsthatcanbeconfiguredwithiwpriv.Thesearedocumentedinthesourcetarballs(http://web.ralinktech.com/ralink/Home/Support/Linux.html)availablefromRalink.

rt3090

Fordeviceswhichareusingthert3090chipsetitshouldbepossibletousert2800pcidriver,however,isnotworkingwiththischipsetverywell(e.g.sometimesit'snotpossibletousehigherratethan2Mb/s).

Thebestwayistousethert3090-dkms (https://aur.archlinux.org/packages/rt3090-dkms/)driverfromAUR.Makesuretoblacklistthert2800pcimoduleandsetupthe rt3090stamoduletoloadatboot.

Note:Thisdriveralsoworkswithrt3062chipsets.Alsothert3090(https://aur.archlinux.org/packages/rt3090/)packageisnotsupportedbythelatestkernelandhasbeenorphanedrt3090-dkms (https://aur.archlinux.org/packages/rt3090-dkms/)shouldbeusedinstead.

rt3290

Thert3290chipsetisrecognisedbythekernelrt2800pcimodule.However,someusersexperienceproblemsandrevertingtoapatchedRalinkdriverseemstobebeneficialinthesecases(https://bbs.archlinux.org/viewtopic.php?id=161952).

rt3573

Newchipsetasof2012.ItmayrequireproprietarydriversfromRalink.Differentmanufacturersuseit,seetheBelkinN750DBwirelessusbadapter(https://bbs.archlinux.org/viewtopic.php?pid=1164228#p1164228)forumsthread.

rt5572

Newchipsetasof2012withsupportfor5Ghzbands.ItmayrequireproprietarydriversfromRalinkandsomeefforttocompilethem.AtthetimeofwritingahowtooncompilationisavailableforaDLINKDWA160rev.B2here(http://bernaerts.dyndns.org/linux/229ubuntuprecisedlinkdwa160revb2).

Realtek

rtl8192cu

Thedriverisnowinthekernel,butmanyusershavereportedbeingunabletomakeaconnectionalthoughscanningfornetworksdoeswork.

Package8192cu-dkms (https://aur.archlinux.org/packages/8192cu-dkms/)intheAURincludesmanypatches,trythisifitdoesn'tworkfinewiththedriverinkernel.

rtl8192e



Thedriverispartofthecurrentkernelpackage.Themoduleinitializationmayfailatbootgivingthiserrormessage:

rtl819xE:ERR in CPUcheck_firmware_ready()rtl819xE:ERR in init_firmware() step 2rtl819xE:ERR!!! _rtl8192_up(): initialization is failed!r8169 0000:03:00.0: eth0: link down

Aworkaroundistosimplyunloadthemodule:

# modprobe -r r8192e_pci

andreloadthemodule(afterapause):

# modprobe r8192e_pci

rtl8188eu

Somedongles,liketheTPLinkTLWN725Nv2(notsure,butitseemsthatusesthertl8179chipset),usechipsetscompatiblewiththisdriver.Inordertouseityouhavetoinstallthedkms-8188eu(https://aur.archlinux.org/packages/dkms-8188eu/)packageintheAUR.

rtl8723be

ThedriverforthiscardisdesignatedtobeenteredintotheLinuxkernelasapartofversion3.15.Untilversion3.15isreleased,thekernelmoduleforthecardcanbedownloadedfromlwfinger'sgithub(https://github.com/lwfinger/rtl8723be).Ifgitisnotinstalled,pleaseinstallit.

$ cd ~/temp$ git clone https://github.com/lwfinger/rtl8723be.git$ cd rtl8723be$ make# make install# modprobe rtl8723be

Whenrunningmake,someusersmayencounteracompileerrorbasedonthekernelversion.If,andonlyifyouencounteracompileerror:

$ nano rtl8723be/trx.c

Online621,changetheline

if ((_ieee80211_is_robust_mgmt_frame(hdr)) &&

to

if ((ieee80211_is_robust_mgmt_frame(hdr)) &&

Save,thencdbacktothemainrtl8723bedirectoryandcontinuefrommake installAdditionally,someusersmayencountererrorswithpowersaveonthiscard.Thisisshownwithoccasionaldisconnectsthatarenotrecognizedbyhighlevelnetworkmanagers(netctl,NetworkManager).Thiserrorcanbeconfirmedbyrunning$ dmesg -wor$ journalctl -fandlookingforoutputrelatedtopowersaveandthertl8723bemodule.Ifyouarehavingthisissue,youneedtoaddakerneloption:

# nano /etc/modprobe.d/rtl8723be.conf



Addthislinetothenewfile:

#Prevents the WiFi card from automatically sleeping and halting connectionoptions rtl8723be fwlps=0

Thatshouldrectifyanyissueswithfirmwarepowersaving.

Atheros

TheMadWifiteam(http://madwifiproject.org/)currentlymaintainsthreedifferentdriversfordeviceswithAtheroschipset:

madwifiisanold,obsoletedriver.NotpresentinArchkernelsince2.6.39.1[4](https://mailman.archlinux.org/pipermail/archdevpublic/2011June/020669.html).ath5kisnewerdriver,whichreplacesthe madwifidriver.Currentlyabetterchoiceforsomechipsets,butnotallchipsetsaresupported(seebelow)ath9kisthenewestofthesethreedrivers,itisintendedfornewerAtheroschipsets.Allofthechipswith802.11ncapabilitiesaresupported.

TherearesomeotherdriversforsomeAtherosdevices.SeeLinuxWirelessdocumentation(http://wireless.kernel.org/en/users/Drivers/Atheros#PCI_.2F_PCIE_.2F_AHB_Drivers)fordetails.

ath5k

Externalresources:

http://wireless.kernel.org/en/users/Drivers/ath5khttp://wiki.debian.org/ath5k

Ifyoufindwebpagesrandomlyloadingveryslow,orifthedeviceisunabletoleaseanIPaddress,trytoswitchfromhardwaretosoftwareencryptionbyloadingtheath5kmodulewith nohwcrypt=1option.SeeKernelModules#Settingmoduleoptionsfordetails.

SomelaptopsmayhaveproblemswiththeirwirelessLEDindicatorflickeringredandblue.Tosolvethisproblem,do:

# echo none > /sys/class/leds/ath5k-phy0::tx/trigger# echo none > /sys/class/leds/ath5k-phy0::rx/trigger

Foralternatives,seethisbugreport(https://bugzilla.redhat.com/show_bug.cgi?id=618232).

ath9k

Externalresources:

http://wireless.kernel.org/en/users/Drivers/ath9khttp://wiki.debian.org/ath9k

Intheunlikelyeventthatyouhavestabilityissuesthattroubleyou,youcouldtryusingthecompatwireless(http://wireless.kernel.org/en/users/Download)package.Anath9kmailinglist(https://lists.ath9k.org/mailman/listinfo/ath9kdevel)existsforsupportanddevelopmentrelateddiscussions.

ASUS

WithsomeASUSlaptops(testedwithASUSU32Useries),itcouldhelptoaddoptions asus_nb_wmi wapf=1to/etc/modprobe.d/asus_nb_wmi.conftofixrfkillrelatedissues.

Youcanalsotrytoblacklistthemoduleasus_nb_wmi(testedwithASUSPROP550C):

# echo "blacklist asus_nb_wmi" >> /etc/modprobe.d/blacklist.conf



Intel

ipw2100andipw2200

Thesemodulesarefullysupportedinthekernel,buttheyrequireadditionalfirmware.Dependingonwhichofthechipsetsyouhave,installeitheripw2100-fw (https://www.archlinux.org/packages/?name=ipw2100-fw)oripw2200-fw(https://www.archlinux.org/packages/?name=ipw2200-fw).Thenreloadtheappropriatemodule.

Tip:Youmayusethefollowingmoduleoptions:

usethertap_iface=1optiontoenabletheradiotapinterfaceusetheled=1optiontoenableafrontLEDindicatingwhenthewirelessisconnectedornot

iwlegacy

iwlegacy(http://wireless.kernel.org/en/users/Drivers/iwlegacy)isthewirelessdriverforIntel's3945and4965wirelesschips.Thefirmwareisincludedinthelinux-firmware (https://www.archlinux.org/packages/?name=linux-firmware)package.

udevshouldloadthedriverautomatically,otherwiseloadiwl3945or iwl4965manually.SeeKernelmodules#Loadingfordetails.

iwlwifi

iwlwifi(http://wireless.kernel.org/en/users/Drivers/iwlwifi)isthewirelessdriverforIntel'scurrentwirelesschips,suchas5100AGN,5300AGN,and5350AGN.Seethefulllistofsupporteddevices(http://wireless.kernel.org/en/users/Drivers/iwlwifi#Supported_Devices).Thefirmwareisincludedinthelinux-firmware(https://www.archlinux.org/packages/?name=linux-firmware)package.

Ifyouhaveproblemsconnectingtonetworksingeneraloryourlinkqualityisverypoor,trytodisable802.11nandenablesoftwareencryption:

/etc/modprobe.d/iwlwifi.conf

options iwlwifi 11n_disable=1options iwlwifi swcrypto=1

Incasethisdoesnotworkforyou,youmaytrydisablingpowersavingforyourwirelessadapter.Forapermanentsolution,addanewudevrule:

/etc/udev/rules.d/80-iwlwifi.rules

ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="", RUN+="/usr/bin/iw dev %k set power_save off"

DisablingLEDblink

Note:Thisworkswiththeiwlegacyand iwlwifidrivers.

ThedefaultsettingsonthemodulearetohavetheLEDblinkonactivity.Somepeoplefindthisextremelyannoying.TohavetheLEDonsolidwhenWiFiisactive,youcanusethesystemdtmpfiles:

/etc/tmpfiles.d/phy0-led.conf

w /sys/class/leds/phy0-led/trigger - - - - phy0radio



Runsystemd-tmpfiles --create phy0-led.confforthechangetotakeeffect,orreboot.

ToseeallthepossibletriggervaluesforthisLED:

# cat /sys/class/leds/phy0-led/trigger

Tip:Ifyoudonothave/sys/class/leds/phy0-led,youmaytrytousethe led_mode="1"moduleoption.Itshouldbevalidforbothiwlwifiand iwlegacydrivers.

Broadcom

SeeBroadcomwireless.

Otherdrivers/devices

Tendaw322u

TreatthisTendacardasanrt2870stadevice.See#rt2x00.

orinoco

Thisshouldbeapartofthekernelpackageandbeinstalledalready.

SomeOrinocochipsetsareHermesII.Youcanusethewlags49_h2_csdriverinsteadof orinoco_csandgainWPAsupport.Tousethedriver,blacklistorinoco_csfirst.

prism54

Thedriverp54isincludedinkernel,butyouhavetodownloadtheappropriatefirmwareforyourcardfromthissite(http://linuxwireless.org/en/users/Drivers/p54#firmware)andinstallitintothe/usr/lib/firmwaredirectory.

Note:There'salsoolder,deprecateddriverprism54,whichmightconflictwiththenewerdriver(p54pcior p54usb).Makesuretoblacklistprism54.

ACX100/111

Warning:Thedriversforthesedevicesarebroken(https://mailman.archlinux.org/pipermail/archdevpublic/2011June/020669.html)anddonotworkwithnewerkernelversions.

Packages:tiacx tiacx-firmware(deletedfromofficialrepositoriesandAUR)

Seeofficialwiki(http://sourceforge.net/apps/mediawiki/acx100/index.php?title=Main_Page)fordetails.

zd1211rw

zd1211rw(http://zd1211.wiki.sourceforge.net/)isadriverfortheZyDASZD1211802.11b/gUSBWLANchipset,anditisincludedinrecentversionsoftheLinuxkernel.See[5](http://www.linuxwireless.org/en/users/Drivers/zd1211rw/devices)foralistofsupporteddevices.Youonlyneedtoinstallthefirmwareforthedevice,providedbythezd1211-firmware (https://www.archlinux.org/packages/?name=zd1211-firmware)package.

hostap_cs

HostAP(http://hostap.epitest.fi/)isaLinuxdriverforwirelessLANcardsbasedonIntersil'sPrism2/2.5/3chipset.ThedriverisincludedinLinuxkernel.



Note:Makesuretoblacklisttheorinico_csdriver,itmaycauseproblems.

ndiswrapper

NdiswrapperisawrapperscriptthatallowsyoutousesomeWindowsdriversinLinux.Seethecompatibilitylisthere(http://ndiswrapper.sourceforge.net/mediawiki/index.php/List).Youwillneedthe.infand .sysfilesfromyourWindowsdriver.Besuretousedriversappropriatetoyourarchitecture(x86vs.x86_64).

Tip:Ifyouneedtoextractthesefilesfroman*.exefile,youcanusecabextract(https://www.archlinux.org/packages/?name=cabextract).

Followthesestepstoconfigurendiswrapper.

1.Installndiswrapper (https://aur.archlinux.org/packages/ndiswrapper/)packagefromtheAUR

2.Installthedriverto/etc/ndiswrapper/*

# ndiswrapper -i filename.inf

3.Listallinstalleddriversforndiswrapper

$ ndiswrapper -l

4.Letndiswrapperwriteitsconfigurationin/etc/modprobe.d/ndiswrapper.conf:

# ndiswrapper -m# depmod -a

NowthendiswrapperinstallisalmostfinishedfollowtheinstructionsonKernelmodules#Loadingtoautomaticallyloadthemoduleatboot.

Theimportantpartismakingsurethatndiswrapperexistsonthisline,sojustadditalongsidetheothermodules.Itwouldbebesttotestthatndiswrapperwillloadnow,so:

# modprobe ndiswrapper# iwconfig

andwlan0shouldnowexist.Checkthispageifyouarehavingproblems:Ndiswrapperinstallationwiki(http://ndiswrapper.sourceforge.net/joomla/index.php?/component/option,com_openwiki/Itemid,33/id,installation/).

compatdriverspatched

Patchedcompatwirelessdriverscorrectthe"fixedchannel1"issue,whilstprovidingbetterinjection.Pleaseinstallthecompat-drivers-patched (https://aur.archlinux.org/packages/compat-drivers-patched/)packagefromtheAUR.

compat-drivers-patched (https://aur.archlinux.org/packages/compat-drivers-patched/)doesnotconflictwithanyotherpackageandthemodulesbuiltresidein/usr/lib/modules/your_kernel_version/updates.

ThesepatcheddriverscomefromtheLinuxWirelessproject(http://wireless.kernel.org/)andsupportmanyoftheabovementionedchipssuchas:

ath5k ath9k_htc carl9170 b43 zd1211rw rt2x00 wl1251 wl12xx ath6kl brcm80211

Supportedgroups:



atheros ath iwlagn rtl818x rtlwifi wl12xx atlxx bt

Itisalsopossibletobuildaspecificmodule/driveroragroupofdriversbyeditingthePKGBUILD,particularlyuncommentingtheline#46.Hereisanexampleofbuildingtheatherosgroup:

scripts/driver-select atheros

Pleasereadthepackage'sPKGBUILDforanyotherpossiblemodificationspriortocompilationandinstallation.

SeealsoTheLinuxWirelessproject(http://wireless.kernel.org/)Aircrackngguideoninstallingdrivers(http://aircrackng.org/doku.php?id=install_drivers)

Retrievedfrom"https://wiki.archlinux.org/index.php?title=Wireless_network_configuration&oldid=320903"Category: WirelessNetworking

Thispagewaslastmodifiedon21June2014,at03:11.ContentisavailableunderGNUFreeDocumentationLicense1.3orlaterunlessotherwisenoted.

wireless network configuration - archwiki

Documents