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
Wirelessnetworkconfiguration
FromArchWiki
Configuringwirelessisatwopartprocessthefirstpartistoidentifyandensurethecorrect
driverforyourwirelessdeviceisinstalled(theyareavailableontheinstallationmedia,but
oftenhavetobeinstalledexplicitly),andtoconfiguretheinterface.Thesecondischoosing
amethodofmanagingwirelessconnections.Thisarticlecoversbothparts,andprovides
additionallinkstowirelessmanagementtools.
Contents
1Devicedriver
1.1Checkthedriverstatus
1.2Installingdriver/firmware
2Wirelessmanagement
2.1Manualsetup
2.1.1Gettingsomeusefulinformation
2.1.2Interfaceactivation
2.1.3Accesspointdiscovery
2.1.4Operatingmode
2.1.5Association
2.1.6GettinganIPaddress
2.1.7Customstartupscripts/services
2.1.7.1Manualwirelessconnectionatbootusingsystemdanddhcpcd
2.1.7.2Systemdwithwpa_supplicantandstaticIP
2.2Automaticsetup
2.2.1Connman
2.2.2Netctl
2.2.3Wicd
2.2.4NetworkManager
2.2.5WiFiRadar
3Troubleshooting
3.1Rfkillcaveat
3.2Respectingtheregulatorydomain
3.3ObservingLogs
3.4Powersaving
3.5FailedtogetIPaddress
3.6Connectionalwaystimesout
3.6.1Loweringtherate
3.6.2Loweringthetxpower
3.6.3Settingrtsandfragmentationthresholds
3.7Randomdisconnections
3.7.1Cause#1
3.7.2Cause#2
3.7.3Cause#3
4Troubleshootingdriversandfirmware
4.1Ralink
4.1.1rt2x00
4.1.2rt3090
4.1.3rt3290
4.1.4rt3573
4.1.5rt5572
4.2Realtek
4.2.1rtl8192cu
4.2.2rtl8192e
4.2.3rtl8188eu
4.2.4rtl8723be
4.3Atheros
4.3.1ath5k
4.3.2ath9k
4.3.2.1ASUS
4.4Intel
4.4.1ipw2100andipw2200
4.4.2iwlegacy
4.4.3iwlwifi
4.4.4DisablingLEDblink
4.5Broadcom
4.6Otherdrivers/devices
4.6.1Tendaw322u
4.6.2orinoco
4.6.3prism54
4.6.4ACX100/111
4.6.5zd1211rw
4.6.6hostap_cs
4.7ndiswrapper
4.8compatdriverspatched
5Seealso
Devicedriver
ThedefaultArchLinuxkernelismodular,meaningmanyofthedriversformachinehardwareresideontheharddriveand
areavailableasmodules.Atboot,udevtakesaninventoryofyourhardwareandloadsappropriatemodules(drivers)for
yourcorrespondinghardware,whichwillinturnallowcreationofanetworkinterface.
Somewirelesschipsetsalsorequirefirmware,inadditiontoacorrespondingdriver.Manyfirmwareimagesareprovided
bythelinux-firmware (https://www.archlinux.org/packages/?name=linux-firmware)packagewhichis
installedbydefault,however,proprietaryfirmwareimagesarenotincludedandhavetobeinstalledseparately.Thisis
describedin#Installingdriver/firmware.
Note:Udevisnotperfect.Ifthepropermoduleisnotloadedbyudevonboot,simplyloaditmanually.Notealsothat
udevmayoccasionallyloadmorethanonedriverforadevice,andtheresultingconflictwillpreventsuccessful
configuration.Makesuretoblacklisttheunwantedmodule.
Tip:Thoughnotstrictlyrequired,it'sagoodideatofirstinstalluserspacetoolsmentionedin#Manualsetup,especially
whensomeproblemshouldappear.
Checkthedriverstatus
Tocheckifthedriverforyourcardhasbeenloaded,checktheoutputofthe lspci -k or lsusb -v command,
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,running dmesg | grep usbcore shouldgivesomethinglike
usbcore: registered new interface driver rtl8187 asoutput.
Alsochecktheoutputof ip link commandtoseeifawirelessinterface(usuallyitstartswiththeletter"w",e.g.
wlp2s1 )wascreated.Thenbringtheinterfaceupwith ip link set interface up .Forexample,assumingthe
interfaceis wlan0 :
# ip link set wlan0 up
Ifyougetthiserrormessage: SIOCSIFFLAGS: No such file or directory ,itmostcertainlymeansthatyourwireless
chipsetrequiresafirmwaretofunction.
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( iwlwifi inthis
example)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)hasagoodlistof
wirelesscardsandwhetherornottheyaresupportedeitherintheLinuxkernelorbyauserspacedriver(includes
drivername).
LinuxWirelessSupport(http://linuxwless.passys.nl/)andTheLinuxQuestions'HardwareCompatibilityList
(http://www.linuxquestions.org/hcl/index.php?cat=10)(HCL)alsohaveagooddatabaseofkernelfriendly
hardware.
Thekernelpage(http://wireless.kernel.org/en/users/Devices)additionallyhasamatrixofsupportedhardware.
Ifyourwirelesscardislistedabove,followthe#Troubleshootingdriversandfirmwaresubsectionofthispage,which
containsinformationaboutinstallingdriversandfirmwareofsomespecificwirelesscards.Thencheckthedriverstatus
again.
Ifyourwirelesscardisnotlistedabove,itislikelysupportedonlyunderWindows(someBroadcom,3com,etc).Forthese,
youcantrytousendiswrapper.
Wirelessmanagement
Assumingthatyourdriversareinstalledandworkingproperly,youwillneedtochooseamethodofmanagingyour
wirelessconnections.Thefollowingsubsectionswillhelpyoudecide.
Procedureandtoolsrequiredwilldependonseveralfactors:
Thedesirednatureofconfigurationmanagementfromacompletelymanualcommandlineproceduretoan
automatedsolutionwithgraphicalfrontends.
Theencryptiontype(orlackthereof)whichprotectsthewirelessnetwork.
Theneedfornetworkprofiles,ifthecomputerwillfrequentlychangenetworks(suchasalaptop).
Tip:
Whateverisyourchoice,youshouldtrytoconnectusingthemanualmethodfirst.Thiswillhelpyou
understandthedifferentstepsthatarerequiredandtroubleshootpossibleproblems.
Ifpossible(e.g.ifyoumanageyourWiFiaccesspoint),tryconnectingwithnoencryption,tocheckthat
everythingworks.Thentryusingencryption,eitherWEP(simpletoconfigure,butcrackableinamatterof
seconds),WPAorWPA2.
Thefollowingtableshowsthedifferentmethodsthatcanbeusedtoactivateandmanageawirelessconnection,depending
ontheencryptionandmanagementtypes,andthevarioustoolsthatarerequired.Althoughtheremaybeotherpossibilities,
thesearethemostfrequentlyused:
Management
method
Interface
activation
Wirelessconnectionmanagement
(/=alternatives)
AssigningIPaddress
(/=alternatives)
Manually
managed,
withnoor
WEP
encryption
ip
iw
(https://www.archlinux.org/packages/?
name=iw)/iwconfig
name=wireless_tools)
ip/dhcpcd/dhclient
name=dhclient)
Manually
managed,
withWPAor
WPA2PSK
encryption
ip
iw
name=iw)/iwconfig
name=wireless_tools)+wpa_supplicant
ip/dhcpcd/dhclient
name=dhclient)
Automatically
managed,
withnetwork
profiles
support
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,butnotall
wirelesschip'smodulessupportit
or
wireless_tools (https://www.archlinux.org/packages/?name=wireless_tools)currently
deprecated,butstillwidelysupported.
AndforWPA/WPA2encryption,youwillalsoneed:
wpa_supplicant (https://www.archlinux.org/packages/?name=wpa_supplicant)
Thetablebelowgivesanoverviewofcomparablecommandsfor iw and wireless_tools (see[1]
(http://wireless.kernel.org/en/users/Documentation/iw/replaceiwconfig)formoreexamples).Theseuserspacetoolswork
extremelywellandallowcompletemanualcontrolofwirelessconnection.
Note:
Examplesinthissectionassumethatyourwirelessdeviceis wlan0 andthatyouareconnectingto your_essid
wifiaccesspoint.Replacebothaccordingly.
Notethatmostofthecommandshavetobeexecutedwithrootpermissions.Executedwithnormaluserrights,
someofthecommands(e.g.iwlist),willexitwithouterrorbutnotproducethecorrectoutputeither,whichcanbe
confusing.
iwcommand wireless_toolscommand Description
iwdevwlan0link iwconfigwlan0 Gettinglinkstatus.
iwdevwlan0scan iwlistwlan0scan Scanningforavailableaccesspoints.
iwdevwlan0settypeibss iwconfigwlan0modeadhoc Settingtheoperationmodetoadhoc.
iwdevwlan0connectyour_essid iwconfigwlan0essidyour_essid Connectingtoopennetwork.
iwdevwlan0connectyour_essid
2432
iwconfigwlan0essidyour_essid
freq2432M
Connectingtoopennetworkspecifying
channel.
key0:your_key
keyyour_key
ConnectingtoWEPencryptednetworkusing
hexadecimalkey.
key0:your_key
keys:your_key
ConnectingtoWEPencryptednetworkusing
ASCIIkey.
iwdevwlan0setpower_saveon iwconfigwlan0poweron Enablingpowersave.
Note:Dependingonyourhardwareandencryptiontype,someofthesestepsmaynotbenecessary.Somecardsare
knowntorequireinterfaceactivationand/oraccesspointscanningbeforebeingassociatedtoanaccesspointandbeing
givenanIPaddress.Someexperimentationmayberequired.Forinstance,WPA/WPA2usersmaytrytodirectlyactivate
theirwirelessnetworkfromstep#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:Ifyougeterrorslike RTNETLINK answers: Operation not possible due to RF-kill ,makesurethat
hardwareswitchison.See#Rfkillcaveatfordetails.
Toverifythattheinterfaceisup,inspecttheoutputofthefollowingcommand:
# ip link show wlan0
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> 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
The UP in <BROADCAST,MULTICAST,UP,LOWER_UP> iswhatindicatestheinterfaceisup,notthelater state DOWN .
Accesspointdiscovery
Seewhataccesspointsareavailable:
# iw dev wlan0 scan | less
Note:Ifitdisplays Interface doesn't support scanning ,thenyouprobablyforgottoinstallthefirmware.In
somecasesthismessageisalsodisplayedwhennotrunningiwasroot.
Tip:Dependingonyourlocation,youmightneedtosetthecorrectregulatorydomaininordertoseeallavailable
networks.
Theimportantpointstocheck:
SSID:thenameofthenetwork.
Signal:isreportedinawirelesspowerratioindbm(e.g.from100to0).Thecloserthenegativevaluegetstozero,
thebetterthesignal.Observingthereportedpoweronagoodqualitylinkandabadoneshouldgiveanideaabout
theindividualrange.
Security:itisnotreporteddirectly,checkthelinestartingwith capability .Ifthereis Privacy ,forexample
capability: ESS Privacy ShortSlotTime (0x0411) ,thenthenetworkisprotectedsomehow.
Ifyouseean RSN informationblock,thenthenetworkisprotectedbyRobustSecurityNetworkprotocol,
alsoknownasWPA2.
Ifyouseean WPA informationblock,thenthenetworkisprotectedbyWiFiProtectedAccessprotocol.
Inthe RSN and WPA blocksyoumayfindthefollowinginformation:
Groupcipher:valueinTKIP,CCMP,both,others.
Pairwiseciphers:valueinTKIP,CCMP,both,others.NotnecessarilythesamevaluethanGroup
cipher.
Authenticationsuites:valueinPSK,802.1x,others.Forhomerouter,you'llusuallyfindPSK(i.e.
passphrase).Inuniversities,youaremorelikelytofind802.1xsuitewhichrequiresloginandpassword.
Thenyouwillneedtoknowwhichkeymanagementisinuse(e.g.EAP),andwhatencapsulationit
uses(e.g.PEAP).FindmoredetailsatWikipedia:Authenticationprotocolandthesubarticles.
Ifyoudonotseeneither RSN nor WPA blocksbutthereis Privacy ,thenWEPisused.
Operatingmode
(Optional,butmayberequired)
Atthisstepyoumightneedtosettheproperoperatingmodeofthewirelesscard.Morespecifically,ifyouaregoingto
connectanadhocnetwork,youneedtosettheoperatingmodeto ibss :
# iw dev wlan0 set type ibss
Note:Changingtheoperatingmodeonsomecardsmightrequirethewirelessinterfacetobedown(
ip link set wlan0 down ).
Association
Dependingontheencryption,youneedtoassociateyourwirelessdevicewiththeaccesspointtouseandpassthe
encryptionkey.
Noencryption
# iw dev wlan0 connect your_essid
WEP
usingahexadecimalorASCIIkey(theformatisdistinguishedautomatically,becauseaWEPkeyhasafixedlength):
# iw dev wlan0 connect your_essid key 0:your_key
usingahexadecimalorASCIIkey,specifyingthethirdsetupkeyasdefault(keysarecountedfromzero,fourare
possible):
# iw dev wlan0 connect your_essid key d:2:your_key
WPA/WPA2
Accordingtowhatyougotfrom#Accesspointdiscovery,issuethiscommand:
# wpa_supplicant -i interface -c <(wpa_passphrase your_SSID your_key)
Thisisassumingyourdeviceusesthe wext driver.Ifthisdoesnotwork,youmayneedtoadjusttheseoptions.If
connectedsuccessfully,continueinanewterminal(orquit wpa_supplicant with Ctrl+c andaddthe -B switchtothe
abovecommandtorunitinthebackground).WPA_Supplicantcontainsmoreinformationonoptionsandonhowtocreate
apermanentconfigurationfileforthewirelessaccesspoint.
Regardlessofthemethodused,youcancheckifyouhaveassociatedsuccessfully:
# iw dev wlan0 link
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.Itis
startedonlyifaconfigurationfileat /etc/wpa_supplicant/wpa_supplicant.conf existsandnowpa_supplicant
processislisteningonthatinterface.Inmostcases,youdonotneedtocreateanycustomservice,justenable
dhcpcd@interface .
Customstartupscripts/services
Althoughthemanualconfigurationmethodwillhelptroubleshootwirelessproblems,youwillhavetoretypeevery
commandeachtimeyoureboot.Youcanalsoquicklywriteashellscripttoautomatethewholeprocess,whichisstilla
quiteconvenientwayofmanagingnetworkconnectionwhilekeepingfullcontroloveryourconfiguration.Youcanfind
someexamplesinthissection.
Manualwirelessconnectionatbootusingsystemdanddhcpcd
Thisexampleusessystemdforstartup,WPAsupplicantforconnecting,anddhcpcd
(https://www.archlinux.org/packages/?name=dhcpcd)forassigninganIPaddress.
Note:Makesurethatwpa_supplicant (https://www.archlinux.org/packages/?name=wpa_supplicant)is
installedandcreate /etc/wpa_supplicant/wpa_supplicant.conf .SeeWPAsupplicantfordetails.
Createasystemdunit,e.g /etc/systemd/system/network-wireless@.service :
/etc/systemd/system/network-wireless@.service
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.conf
ExecStart=/usr/bin/dhcpcd %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=multi-user.target
Startand/orenabletheunitasdescribedinsystemd#Usingunits,remembertopassthenameoftheinterface:
# systemctl enable network-wireless@wlan0.service
# systemctl start network-wireless@wlan0.service
Systemdwithwpa_supplicantandstaticIP
Note:Makesurethatwpa_supplicant (https://www.archlinux.org/packages/?name=wpa_supplicant)is
installedandcreateacustom /etc/wpa_supplicant/wpa_supplicant.conf .SeeWPAsupplicantfordetails.
Firstcreateconfigurationfileforthesystemdservice,replace interface withproperinterfacename:
/etc/conf.d/network-wireless@interface
address=192.168.0.10
netmask=24
broadcast=192.168.0.255
gateway=192.168.0.1
Createasystemdunitfile:
/etc/systemd/system/network-wireless@.service
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network-wireless@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.conf
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
ExecStart=/usr/bin/ip route add default via ${gateway}
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=multi-user.target
Enabletheunitandstartit,passingthenameoftheinterface:
# systemctl enable network-wireless@wlan0.service
# systemctl start network-wireless@wlan0.service
Automaticsetup
Therearemanysolutionstochoosefrom,butrememberthatallofthemaremutuallyexclusiveyoushouldnotruntwo
daemonssimultaneously.Thefollowingtablecomparesthedifferentconnectionmanagers,additionalnotesarein
subsectionsbelow.
Connectionmanager
Network
profiles
support
Roaming
(autoconnectdropped
orchangedlocation)
PPPsupport
(e.g.3Gmodem)
Official
GUI
Consoletools
Connman Yes Yes Yes No connmanctl
Netctl Yes Yes Yes No netctl , wifi-menu
NetworkManager Yes Yes Yes Yes nmcli
Wicd Yes Yes No Yes wicd-curses
Connman
ConnManisanalternativetoNetworkManagerandWicd,designedtobelightonresourcesmakingitidealfornetbooks,
andothermobiledevices.ItismodularindesigntakesadvandageofthedbusAPIandprovidesproperabstractionontop
ofwpa_supplicant.
See:Connman
Netctl
netctlisareplacementfornetcfgdesignedtoworkwithsystemd.Itusesaprofilebasedsetupandiscapableofdetection
andconnectiontoawiderangeofnetworktypes.Thisisnoharderthanusinggraphicaltools.
See:Netctl
Wicd
Wicdisanetworkmanagerthatcanhandlebothwirelessandwiredconnections.ItiswritteninPythonandGtkwithfewer
dependenciesthanNetworkManager,makingitanidealsolutionforlightweightdesktopusers.
See:Wicd
Note:wicdmaycauseexcessivedroppedconnectionswithsomedrivers,whileNetworkManagermightworkbetter.
NetworkManager
NetworkManagerisanadvancednetworkmanagementtoolthatisenabledbydefaultinmostpopularGNU/Linux
distributions.Inadditiontomanagingwiredconnections,NetworkManagerprovidesworryfreewirelessroamingwithan
easytouseGUIprogramforselectingyourdesirednetwork.
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.Itenablesyoutoscanfor
availablenetworksandcreateprofilesforyourpreferrednetworks.
See:WifiRadar
Troubleshooting
Thissectioncontainsgeneraltroubleshootingtips,notstrictlyrelatedtoproblemswithdriversorfirmware.Forsuchtopics,
seenextsection.
Rfkillcaveat
Manylaptopshaveahardwarebutton(orswitch)toturnoffwirelesscard,however,thecardcanalsobeblockedby
kernel.Thiscanbehandledbyrfkill (https://www.archlinux.org/packages/?name=rfkill).Userfkilltoshow
thecurrentstatus:
# rfkill list
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
Ifthecardishardblocked,usethehardwarebutton(switch)tounblockit.Ifthecardisnothardblockedbutsoftblocked,
usethefollowingcommand:
# rfkill unblock wifi
Note:Itispossiblethatthecardwillgofromhardblockedandsoftunblockedstateintohardunblockedandsoftblocked
statebypressingthehardwarebutton(i.e.thesoftblockedbitisjustswitchednomatterwhat).Thiscanbeadjustedby
tuningsomeoptionsofthe rfkill kernelmodule.
Moreinfo:http://askubuntu.com/questions/62166/siocsifflagsoperationnotpossibleduetorfkill
Respectingtheregulatorydomain
Theregulatorydomain(http://en.wikipedia.org/wiki/IEEE_802.11#Regulatory_domains_and_legal_compliance),or
"regdomain",isusedtoreconfigurewirelessdriverstomakesurethatwirelesshardwareusagecomplieswithlocallawsset
bytheFCC,ETSIandotherorganizations.RegdomainsuseISO31661alpha2countrycodes
(https://en.wikipedia.org/wiki/ISO_31661_alpha2).Forexample,theregdomainoftheUnitedStateswouldbe"US",
Chinawouldbe"CN",etc.
Regdomainsaffecttheavailabilityofwirelesschannels.Inthe2.4GHzband,theallowedchannelsare111fortheUS,1
14forJapan,and113formostoftherestoftheworld.Inthe5GHzband,therulesforallowedchannelsaremuchmore
complex.Ineithercase,consultthislistofWLANchannels(https://en.wikipedia.org/wiki/List_of_WLAN_channels)for
moredetailedinformation.
Regdomainsalsoaffectthelimitontheeffectiveisotropicradiatedpower(EIRP)
(https://en.wikipedia.org/wiki/Equivalent_isotropically_radiated_power)fromwirelessdevices.Thisisderivedfrom
transmitpower/"txpower",andismeasuredindBm/mBm(1dBm=100mBm)ormW(logscale)
(https://en.wikipedia.org/wiki/DBm).Inthe2.4GHzband,themaximumis30dBmintheUSandCanada,20dBminmost
ofEurope,and20dB30dBmfortherestoftheworld.Inthe5GHzband,maximumsareusuallylower.Consultthe
wirelessregdb(http://git.kernel.org/cgit/linux/kernel/git/linville/wirelessregdb.git/tree/db.txt)formoredetailedinformation
(EIRPdBmvaluesareinthesecondsetofbracketsforeachline).
Misconfiguringtheregdomaincanbeusefulforexample,byallowinguseofanunusedchannelwhenotherchannelsare
crowded,orbyallowinganincreaseintxpowertowidentransmitterrange.However,thisisnotrecommendedasit
couldbreaklocallawsandcauseinterferencewithotherradiodevices.
Toconfiguretheregdomain,installcrda (https://www.archlinux.org/packages/?name=crda)andwireless-
regdb (https://www.archlinux.org/packages/?name=wireless-regdb)andreboot(toreloadthe cfg80211
moduleandallrelateddrivers).CheckthebootlogtomakesurethatCRDAisbeingcalledby cfg80211 :
$ dmesg | grep cfg80211
ThecurrentregdomaincanbesettotheUnitedStateswith:
# iw reg set US
Andqueriedwith:
$ iw reg get
Note:Yourdevicemaybesettocountry"00",whichisthe"worldregulatorydomain"andcontainsgenericsettings.If
thiscannotbeunset,CRDAmaybemisconfigured.
However,settingtheregdomainmaynotalteryoursettings.Somedeviceshavearegdomainsetinfirmware/EEPROM,
whichdictatesthelimitsofthedevice,meaningthatsettingregdomaininsoftwarecanonlyincreaserestrictions
(http://wiki.openwrt.org/doc/howto/wireless.utilities#iw),notdecreasethem.Forexample,aCNdevicecouldbesetin
softwaretotheUSregdomain,butbecauseCNhasanEIRPmaximumof20dBm,thedevicewillnotbeabletotransmitat
theUSmaximumof30dBm.
Forexample,toseeiftheregdomainisbeingsetinfirmwareforanAtherosdevice:
$ dmesg | grep ath:
Forotherchipsets,itmayhelptosearchfor"EEPROM","regdomain",orsimplythenameofthedevicedriver.
Toseeifyourregdomainchangehasbeensuccessful,andtoquerythenumberofavailablechannelsandtheirallowed
transmitpower:
$ iw list | grep -A 15 Frequencies:
Amorepermanentconfigurationoftheregdomaincanbeachievedthroughediting /etc/conf.d/wireless-regdom
anduncommentingtheappropriatedomain. wpa_supplicant canalsousearegdomaininthe country= lineof
/etc/wpa_supplicant.conf .
Itisalsopossibletoconfigurethecfg80211(http://wireless.kernel.org/en/developers/Documentation/cfg80211)kernel
moduletouseaspecificregdomainbyadding,forexample, options cfg80211 ieee80211_regdom=EU to
/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.Inordernottomanuallyparsethroughthem
all,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/)mightgivea
firsthint.
Theindividualtoolsusedinthisarticlefurtherprovideoptionsformoredetaileddebuggingoutput,whichcanbeusedina
secondstepoftheanalysis,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's
powersavingfeatures:
# iwconfig wlan0 power off
Ifyougetatimeouterrorduetoawaitingforcarrierproblem,thenyoumighthavetosetthechannelmodeto
auto forthespecificdevice:
# iwconfig wlan0 channel auto
Beforechangingthechanneltoauto,makesureyourwirelessinterfaceisdown.Afterithassuccessfullychangedit,you
canbringtheinterfaceupagainandcontinuefromthere.
Connectionalwaystimesout
Thedrivermaysufferfromalotoftxexcessiveretriesandinvalidmiscerrorsforsomeunknownreason,resultinginalot
ofpacketlossandkeepdisconnecting,sometimesinstantly.Followingtipsmightbehelpful.
Loweringtherate
Trysettinglowerrate,forexample5.5M:
# iwconfig wlan0 rate 5.5M auto
Fixedoptionshouldensurethatthedriverdoesnotchangetherateonitsown,thusmakingtheconnectionabitmore
stable:
# iwconfig wlan0 rate 5.5M fixed
Loweringthetxpower
Youcantryloweringthetransmitpoweraswell.Thismaysavepoweraswell:
# iwconfig wlan0 txpower 5
Validsettingsarefrom 0 to 20 , auto and off .
Settingrtsandfragmentationthresholds
Defaultiwconfigoptionshavertsandfragmentationthresholdsoff.Theseoptionsareparticularlyusefulwhenthereare
manyadjacentAPsorinanoisyenvironment.
Theminimumvalueforfragmentationvalueis256andmaximumis2346.Inmanywindowsdriversthemaximumisthe
defaultvalue:
# iwconfig wlan0 frag 2346
Forrtsminimumis0,maximumis2347.Onceagainwindowsdriversoftenusemaximumasthedefault:
# iwconfig wlan0 rts 2347
Randomdisconnections
Cause#1
Ifdmesgsays wlan0: deauthenticating from MAC by local choice (reason=3) andyouloseyourWiFi
connection,itislikelythatyouhaveabittooaggressivepowersavingonyourWiFicard[2](http://us.generation
nt.com/answer/gentoouserwirelessdeauthenticatingbylocalchoicehelp204640041.html).Trydisablingthewireless
card'spowersavingfeatures:
# iwconfig wlan0 power off
SeePowersavingfortipsonhowtomakeitpermanent(justspecify off insteadof on ).
Ifyourcarddoesnotsupport iwconfig wlan0 power off ,checktheBIOSforpowermanagementoptions.Disabling
PCIExpresspowermanagementintheBIOSofaLenovoW520resolvedthisissue.
Cause#2
Ifyouareexperiencingfrequentdisconnectionsanddmesgshowsmessagessuchas
ieee80211 phy0: wlan0: No probe response from AP xx:xx:xx:xx:xx:xx after 500ms, disconnecting
trychangingthechannelbandwidthto 20MHz throughyourrouter'ssettingspage.
Cause#3
Onsomelaptopmodelswithhardwarerfkillswitches(e.g.,ThinkpadX200series),duetowearorbaddesign,theswitch
(oritsconnectiontothemainboard)mightbecomelooseovertimeresultinginseeminglyrandomhardblocks/disconnects
whenyouaccidentallytouchtheswitchormovethelaptop.Thereisnosoftwaresolutiontothis,unlessyourswitchis
electricalandtheBIOSofferstheoptiontodisabletheswitch.Ifyourswitchismechanical(mostare),therearelotsof
possiblesolutions,mostofwhichaimtodisabletheswitch:Solderingthecontactpointonthemainboard/wificard,glueing
orblockingtheswitch,usingascrewnuttotightentheswitchorremovingitaltogether.
Troubleshootingdriversandfirmware
Thissectioncoversmethodsandproceduresforinstallingkernelmodulesandfirmwareforspecificchipsets,thatdiffer
fromgenericmethod.
SeeKernelmodulesforgeneralinformationsonoperationswithmodules.
Ralink
rt2x00
UnifieddriverforRalinkchipsets(itreplaces rt2500 , rt61 , rt73 ,etc).ThisdriverhasbeenintheLinuxkernelsince
2.6.24,youonlyneedtoloadtherightmoduleforthechip: rt2400pci , rt2500pci , rt2500usb , rt61pci or
rt73usb whichwillautoloadtherespective rt2x00 modulestoo.
Alistofdevicessupportedbythemodulesisavailableattheproject'shomepage
(http://rt2x00.serialmonkey.com/wiki/index.php/Hardware).
Additionalnotes
Sincekernel3.0,rt2x00includesalsothesedrivers: rt2800pci , rt2800usb .
Sincekernel3.0,thestagingdrivers rt2860sta and rt2870sta arereplacedbythemainlinedrivers rt2800pci
and rt2800usb
[3](https://git.kernel.org/?p=linux/kernel/git/torvalds/linux
2.6.gita=commitdiffh=fefecc6989b4b24276797270c0e229c07be02ad3)
.
Somedeviceshaveawiderangeofoptionsthatcanbeconfiguredwith iwpriv .Thesearedocumentedinthe
sourcetarballs(http://web.ralinktech.com/ralink/Home/Support/Linux.html)availablefromRalink.
rt3090
Fordeviceswhichareusingthert3090chipsetitshouldbepossibletouse rt2800pci driver,however,isnotworking
withthischipsetverywell(e.g.sometimesit'snotpossibletousehigherratethan2Mb/s).
Thebestwayistousethert3090-dkms (https://aur.archlinux.org/packages/rt3090-dkms/)driverfromAUR.
Makesuretoblacklistthe rt2800pci moduleandsetupthe rt3090sta moduletoloadatboot.
Note:Thisdriveralsoworkswithrt3062chipsets.Alsothert3090
(https://aur.archlinux.org/packages/rt3090/)packageisnotsupportedbythelatestkernelandhasbeen
orphanedrt3090-dkms (https://aur.archlinux.org/packages/rt3090-dkms/)shouldbeusedinstead.
rt3290
Thert3290chipsetisrecognisedbythekernel rt2800pci module.However,someusersexperienceproblemsand
revertingtoapatchedRalinkdriverseemstobebeneficialinthesecases(https://bbs.archlinux.org/viewtopic.php?
id=161952).
rt3573
Newchipsetasof2012.ItmayrequireproprietarydriversfromRalink.Differentmanufacturersuseit,seetheBelkin
N750DBwirelessusbadapter(https://bbs.archlinux.org/viewtopic.php?pid=1164228#p1164228)forumsthread.
rt5572
Newchipsetasof2012withsupportfor5Ghzbands.ItmayrequireproprietarydriversfromRalinkandsomeeffortto
compilethem.AtthetimeofwritingahowtooncompilationisavailableforaDLINKDWA160rev.B2here
(http://bernaerts.dyndns.org/linux/229ubuntuprecisedlinkdwa160revb2).
Realtek
rtl8192cu
Thedriverisnowinthekernel,butmanyusershavereportedbeingunabletomakeaconnectionalthoughscanningfor
networksdoeswork.
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 2
rtl819xE: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),usechipsets
compatiblewiththisdriver.Inordertouseityouhavetoinstallthedkms-8188eu
(https://aur.archlinux.org/packages/dkms-8188eu/)packageintheAUR.
rtl8723be
ThedriverforthiscardisdesignatedtobeenteredintotheLinuxkernelasapartofversion3.15.Untilversion3.15is
released,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
Whenrunning make ,someusersmayencounteracompileerrorbasedonthekernelversion.If,andonlyifyouencounter
acompileerror:
$ nano rtl8723be/trx.c
Online621,changetheline
if ((_ieee80211_is_robust_mgmt_frame(hdr)) &&
to
if ((ieee80211_is_robust_mgmt_frame(hdr)) &&
Save,thencdbacktothemainrtl8723bedirectoryandcontinuefrom make install Additionally,someusersmay
encountererrorswithpowersaveonthiscard.Thisisshownwithoccasionaldisconnectsthatarenotrecognizedbyhigh
levelnetworkmanagers(netctl,NetworkManager).Thiserrorcanbeconfirmedbyrunning $ dmesg -w or
$ journalctl -f andlookingforoutputrelatedtopowersaveandthertl8723bemodule.Ifyouarehavingthisissue,
youneedtoaddakerneloption:
# nano /etc/modprobe.d/rtl8723be.conf
Addthislinetothenewfile:
#Prevents the WiFi card from automatically sleeping and halting connection
options rtl8723be fwlps=0
Thatshouldrectifyanyissueswithfirmwarepowersaving.
Atheros
TheMadWifiteam(http://madwifiproject.org/)currentlymaintainsthreedifferentdriversfordeviceswithAtheroschipset:
madwifi isanold,obsoletedriver.NotpresentinArchkernelsince2.6.39.1
[4]
(https://mailman.archlinux.org/pipermail/archdevpublic/2011June/020669.html)
.
ath5k isnewerdriver,whichreplacesthe madwifi driver.Currentlyabetterchoiceforsomechipsets,butnotall
chipsetsaresupported(seebelow)
ath9k isthenewestofthesethreedrivers,itisintendedfornewerAtheroschipsets.Allofthechipswith802.11n
capabilitiesaresupported.
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/ath5k
http://wiki.debian.org/ath5k
Ifyoufindwebpagesrandomlyloadingveryslow,orifthedeviceisunabletoleaseanIPaddress,trytoswitchfrom
hardwaretosoftwareencryptionbyloadingthe ath5k modulewith nohwcrypt=1 option.SeeKernelModules#Setting
moduleoptionsfordetails.
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/ath9k
http://wiki.debian.org/ath9k
Intheunlikelyeventthatyouhavestabilityissuesthattroubleyou,youcouldtryusingthecompatwireless
(http://wireless.kernel.org/en/users/Download)package.Anath9kmailinglist(https://lists.ath9k.org/mailman/listinfo/ath9k
devel)existsforsupportanddevelopmentrelateddiscussions.
ASUS
WithsomeASUSlaptops(testedwithASUSU32Useries),itcouldhelptoadd options asus_nb_wmi wapf=1 to
/etc/modprobe.d/asus_nb_wmi.conf tofixrfkillrelatedissues.
Youcanalsotrytoblacklistthemoduleasus_nb_wmi(testedwithASUSPROP550C):
# echo "blacklist asus_nb_wmi" >> /etc/modprobe.d/blacklist.conf
Intel
ipw2100andipw2200
Thesemodulesarefullysupportedinthekernel,buttheyrequireadditionalfirmware.Dependingonwhichofthechipsets
youhave,installeitheripw2100-fw (https://www.archlinux.org/packages/?name=ipw2100-fw)oripw2200-fw
(https://www.archlinux.org/packages/?name=ipw2200-fw).Thenreloadtheappropriatemodule.
Tip:Youmayusethefollowingmoduleoptions:
usethe rtap_iface=1 optiontoenabletheradiotapinterface
usethe led=1 optiontoenableafrontLEDindicatingwhenthewirelessisconnectedornot
iwlegacy
iwlegacy(http://wireless.kernel.org/en/users/Drivers/iwlegacy)isthewirelessdriverforIntel's3945and4965wireless
chips.Thefirmwareisincludedinthelinux-firmware (https://www.archlinux.org/packages/?name=linux-
firmware)package.
udevshouldloadthedriverautomatically,otherwiseload iwl3945 or iwl4965 manually.SeeKernelmodules#Loading
fordetails.
iwlwifi
iwlwifi(http://wireless.kernel.org/en/users/Drivers/iwlwifi)isthewirelessdriverforIntel'scurrentwirelesschips,suchas
5100AGN,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.11nandenable
softwareencryption:
/etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=1
options iwlwifi swcrypto=1
Incasethisdoesnotworkforyou,youmaytrydisablingpowersavingforyourwirelessadapter.Forapermanent
solution,addanewudevrule:
/etc/udev/rules.d/80-iwlwifi.rules
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="<your_mac_address>", RUN+="/usr/bin/iw dev %k set power_save off"
DisablingLEDblink
Note:Thisworkswiththe iwlegacy and iwlwifi drivers.
ThedefaultsettingsonthemodulearetohavetheLEDblinkonactivity.Somepeoplefindthisextremelyannoying.To
havetheLEDonsolidwhenWiFiisactive,youcanusethesystemdtmpfiles:
/etc/tmpfiles.d/phy0-led.conf
w /sys/class/leds/phy0-led/trigger - - - - phy0radio
Run systemd-tmpfiles --create phy0-led.conf forthechangetotakeeffect,orreboot.
ToseeallthepossibletriggervaluesforthisLED:
# cat /sys/class/leds/phy0-led/trigger
Tip:Ifyoudonothave /sys/class/leds/phy0-led ,youmaytrytousethe led_mode="1" moduleoption.It
shouldbevalidforboth iwlwifi and iwlegacy drivers.
Broadcom
SeeBroadcomwireless.
Otherdrivers/devices
Tendaw322u
TreatthisTendacardasan rt2870sta device.See#rt2x00.
orinoco
Thisshouldbeapartofthekernelpackageandbeinstalledalready.
SomeOrinocochipsetsareHermesII.Youcanusethe wlags49_h2_cs driverinsteadof orinoco_cs andgainWPA
support.Tousethedriver,blacklist orinoco_cs first.
prism54
Thedriver p54 isincludedinkernel,butyouhavetodownloadtheappropriatefirmwareforyourcardfromthissite
(http://linuxwireless.org/en/users/Drivers/p54#firmware)andinstallitintothe /usr/lib/firmware directory.
Note:There'salsoolder,deprecateddriver prism54 ,whichmightconflictwiththenewerdriver( p54pci or p54usb
).Makesuretoblacklist prism54 .
ACX100/111
Warning:Thedriversforthesedevicesarebroken(https://mailman.archlinux.org/pipermail/archdevpublic/2011
June/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,and
itisincludedinrecentversionsoftheLinuxkernel.See[5]
(http://www.linuxwireless.org/en/users/Drivers/zd1211rw/devices)foralistofsupporteddevices.Youonlyneedtoinstall
thefirmwareforthedevice,providedbythezd1211-firmware (https://www.archlinux.org/packages/?
name=zd1211-firmware)package.
hostap_cs
HostAP(http://hostap.epitest.fi/)isaLinuxdriverforwirelessLANcardsbasedonIntersil'sPrism2/2.5/3chipset.The
driverisincludedinLinuxkernel.
Note:Makesuretoblacklistthe orinico_cs driver,itmaycauseproblems.
ndiswrapper
NdiswrapperisawrapperscriptthatallowsyoutousesomeWindowsdriversinLinux.Seethecompatibilitylisthere
(http://ndiswrapper.sourceforge.net/mediawiki/index.php/List).Youwillneedthe .inf and .sys filesfromyour
Windowsdriver.Besuretousedriversappropriatetoyourarchitecture(x86vs.x86_64).
Tip:Ifyouneedtoextractthesefilesfroman *.exe file,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#Loadingtoautomaticallyload
themoduleatboot.
Theimportantpartismakingsurethatndiswrapperexistsonthisline,sojustadditalongsidetheothermodules.Itwould
bebesttotestthatndiswrapperwillloadnow,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.Pleaseinstallthe
compat-drivers-patched (https://aur.archlinux.org/packages/compat-drivers-patched/)packagefrom
theAUR.
compat-drivers-patched (https://aur.archlinux.org/packages/compat-drivers-patched/)doesnotconflict
withanyotherpackageandthemodulesbuiltresidein /usr/lib/modules/your_kernel_version/updates .
ThesepatcheddriverscomefromtheLinuxWirelessproject(http://wireless.kernel.org/)andsupportmanyoftheabove
mentionedchipssuchas:
ath5k ath9k_htc carl9170 b43 zd1211rw rt2x00 wl1251 wl12xx ath6kl brcm80211
Supportedgroups:
atheros ath iwlagn rtl818x rtlwifi wl12xx atlxx bt
Itisalsopossibletobuildaspecificmodule/driveroragroupofdriversbyeditingthePKGBUILD,particularly
uncommentingtheline#46.Hereisanexampleofbuildingtheatherosgroup:
scripts/driver-select atheros
Pleasereadthepackage'sPKGBUILDforanyotherpossiblemodificationspriortocompilationandinstallation.
Seealso
TheLinuxWirelessproject(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

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Wireless Network Configuration - ArchWiki

Diunggah oleh

Hak Cipta:

Format Tersedia

6/22/2014 Wireless network configuration - ArchWiki

Anda mungkin juga menyukai