[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
slackbook:wifi [2012/09/17 00:05 (UTC)] – [Wifi Protected Access] corrected a section heading mfillpot | slackbook:wifi [2012/09/17 01:26 (UTC)] (current) – [Sources] updated authors and tags mfillpot | ||
---|---|---|---|
Line 109: | Line 109: | ||
===== Wifi Protected Access ===== | ===== Wifi Protected Access ===== | ||
- | Wifi Protected Access (or WPA for short) was the successor for WEP that aimed to fix several problems with wireless encryption. Unfortunately, | + | Wifi Protected Access (or WPA for short) was the successor for WEP that |
+ | aimed to fix several problems with wireless encryption. Unfortunately, | ||
+ | WPA had some flaws as well. An update called WPA2 offers even stronger | ||
+ | protection. At this time, WPA2 is supported by nearly all wireless | ||
+ | network cards and access points, but some older devices may only | ||
+ | support WEP. If you need to secure your wireless network traffic, WPA2 | ||
+ | should be considered the minimum level of protection required. | ||
+ | Unfortunately, | ||
+ | WPA2 encryption on its own. For that, we need a helper daemon, | ||
+ | **//wpa_supplicant//**(8). | ||
- | Unfortunately, | ||
- | | + | Unfortunately, |
- | # ======================== | + | protected network; you'll have to edit |
- | # This line enables the use of wpa_cli which is used by rc.wireless | + | ''/ |
- | # if possible (to check for successful association) | + | editor. Here we will discuss the simplest form of WPA2 protection, the |
- | ctrl_interface=/ | + | Pre-Shared Key, or PSK for short. For details on setting up Slackware |
- | # By default, only root (group 0) may use wpa_cli | + | to connect to more complicated WPA2 encrypted networks, see the man |
- | ctrl_interface_group=0 | + | page for '' |
- | eapol_version=1 | + | |
- | ap_scan=1 | + | |
- | fast_reauth=1 | + | < |
- | # | + | |
- | + | # / | |
- | # WPA protected network, supply your own ESSID and WPAPSK here: | + | # ======================== |
- | network={ | + | # This line enables the use of wpa_cli which is used by rc.wireless |
- | scan_ssid=1 | + | # if possible (to check for successful association) |
- | ssid=" | + | ctrl_interface=/ |
- | key_mgmt=WPA-PSK | + | # By default, only root (group 0) may use wpa_cli |
- | psk=" | + | ctrl_interface_group=0 |
- | } | + | eapol_version=1 |
+ | ap_scan=1 | ||
+ | fast_reauth=1 | ||
+ | # | ||
+ | |||
+ | # WPA protected network, supply your own ESSID and WPAPSK here: | ||
+ | network={ | ||
+ | scan_ssid=1 | ||
+ | ssid=" | ||
+ | key_mgmt=WPA-PSK | ||
+ | psk=" | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | |||
+ | The block of text we're interested in is the network block enclosed by | ||
+ | curly braces. | ||
+ | //" | ||
+ | passphrase"// | ||
+ | configured. | ||
+ | then obtain an IP address via DHCP or set a static address. | ||
+ | course, this is a lot of work; there must be an easier way to do this. | ||
- | The block of text we're interested in is the network block enclosed by curly braces. Here we have set the ssid for the network " | ||
+ | <!-- not closing this yet /section --> | ||
==== rc.inet1.conf revisited ==== | ==== rc.inet1.conf revisited ==== | ||
- | Welcome back to rc.inet1.conf. You will recall that in Chapter 14, Networking | + | Welcome back to '' |
+ | that in [[: | ||
+ | to automatically configure NICs whenever Slackware boots. | ||
+ | will use it to configure wifi as well. | ||
- | < | ||
- | Recall that each NIC had a name or number that identified the variables that correspond with it? The same holds true for wifi NICs, only they have even more variables due to the added complexity of wireless networking. | + | < |
+ | |||
+ | If you're using WPA2, you'll still need to setup | ||
+ | wpa_supplicant.conf properly first, however. | ||
- | # rc.inet1.conf (excerpt) | + | </ |
- | # ====================== | + | |
- | ## Example config information for wlan0. | + | |
- | ## in your info. (You may not need all of these for your wireless network) | + | |
- | IFNAME[4]=" | + | |
- | IPADDR[4]="" | + | |
- | NETMASK[4]="" | + | |
- | USE_DHCP[4]=" | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | WLAN_ESSID[4]=" | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # set EncrypType=TKIP | \ | + | |
- | # set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16" | + | |
- | WLAN_WPA[4]=" | + | |
- | # | + | |
- | When we discussed wired ethernet, | + | Recall that each NIC had a name or number that identified |
+ | that correspond | ||
+ | have even more variables due to the added complexity | ||
+ | networking. | ||
- | To begin, WLAN_ESSID[n] and WLAN_CHANNEL[n] should be self-explanatory by now; they refer the the essid and frequency to use. WLAN_MODE[n] is either managed or ad-hoc. Anyone connecting to an access point will want to use managed mode. WLAN_KEY[n] is the WEP key to use, if you're forced to use WEP. WLAN_IWPRIV[n] is a very complicated variable that sets other variables inside itself. WLAN_IWPRIV[n] is used for WPA2 networks. Here you tell Slackware what authentication mode, encryption type, and key to use for WPA2 connections. Please note that WLAN_KEY[n] and WLAN_IWPRIV[n] are mutually exclusive; you can't use both on the same interface. If you successfully configure all this, then Slackware will attempt to connect to your wireless network as soon as the system boots. | ||
- | But wait, that's so much work! And what if I need to connect to multiple wireless networks? I take my laptop to work and school and need to seamlessly setup those wireless connections as soon as one is within range. Doing things this way is simply too much work. You're absolutely correct. | + | < |
+ | # rc.inet1.conf (excert) | ||
+ | # ====================== | ||
+ | ## Example config information for wlan0. | ||
+ | ## in your info. (You may not need all of these for your wireless network) | ||
+ | IFNAME[4]=" | ||
+ | IPADDR[4]="" | ||
+ | NETMASK[4]="" | ||
+ | USE_DHCP[4]=" | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | WLAN_ESSID[4]=" | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # set EncrypType=TKIP | \ | ||
+ | # set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16" | ||
+ | WLAN_WPA[4]=" | ||
+ | # | ||
+ | </ | ||
+ | |||
+ | |||
+ | When we discussed wired ethernet, each //n// in the | ||
+ | variable corresponded with the //n// in | ||
+ | // | ||
+ | no longer holds true. Notice that the variable IFNAME[4] has a value | ||
+ | of //wlan0//. It is common for wireless cards to have an interface name | ||
+ | other than //ethn// and that is reflected here. When | ||
+ | '' | ||
+ | Slackware knows to apply all these options to the //wlan0// wifi NIC | ||
+ | instead of the (probably non-existant) eth4 wired NIC. Many of the | ||
+ | other options are the same. IP address information is added in | ||
+ | exactly the same way we discussed for wired network cards in [[: | ||
+ | some explanation. | ||
+ | |||
+ | |||
+ | To begin, // | ||
+ | // | ||
+ | they refer the the essid and frequency to | ||
+ | use. // | ||
+ | **managed** or **ad-hoc**. | ||
+ | Anyone connecting to an access point will want to use managed mode. | ||
+ | // | ||
+ | to use WEP. // | ||
+ | variable that sets other variables inside itself. | ||
+ | // | ||
+ | tell Slackware what authentication mode, encryption type, and key to | ||
+ | use for WPA2 connections. | ||
+ | // | ||
+ | are mutually exclusive; you can't use both on the same interface. | ||
+ | you successfully configure all this, then Slackware will attempt to | ||
+ | connect to your wireless network as soon as the system boots. | ||
+ | |||
+ | |||
+ | But wait, that's so much work! And what if I need to connect to | ||
+ | multiple wireless networks? | ||
+ | need to seemlessly setup those wireless connections as soon as one is | ||
+ | within range. | ||
+ | absolutely correct. | ||
===== Wicd ===== | ===== Wicd ===== | ||
- | Introducing wicd(8), the premier wired and wireless network connection manager for the laptop user on the go. Pronounced " | + | Introducing |
+ | wireless network connection manager for the laptop user on the go. | ||
+ | Pronounced | ||
+ | storing information for any number of wireless networks you need and | ||
+ | connecting to them with a simple command or the click of a mouse. | ||
+ | **//wicd//** is not part of the default Slackware | ||
+ | installation at this time, as it interferes somewhat with the normal | ||
+ | way of configuring network adapters, but you can find it in the | ||
+ | '' | ||
+ | or at your favorite mirror. | ||
+ | network connection daemon and a graphical application for configuring | ||
+ | networks. | ||
+ | **//wicd-curses//**(8) is every bit as powerful as | ||
+ | the traditional GUI front-end. | ||
+ | **//wicd//**, you will need to disable support for | ||
+ | any interfaces you have in '' | ||
- | # rc.inet1.conf | ||
- | # ============= | ||
- | # Config information for eth0: | ||
- | IPADDR[0]="" | ||
- | NETMASK[0]="" | ||
- | USE_DHCP[0]=" | ||
- | DHCP_HOSTNAME[0]="" | ||
- | # Default gateway IP address: | ||
- | GATEWAY="" | ||
- | Now we can install wicd, setup the daemon to run on system boot-up, and begin using a more friendly application. | + | < |
- | darkstar:~# installpkg / | + | # rc.inet1.conf |
- | | + | # ============= |
- | | + | # Config information for eth0: |
+ | IPADDR[0]="" | ||
+ | NETMASK[0]="" | ||
+ | USE_DHCP[0]=" | ||
+ | DHCP_HOSTNAME[0]="" | ||
+ | # Default gateway IP address: | ||
+ | GATEWAY="" | ||
+ | </code> | ||
- | If you're predominately using the console, simply run wicd-curses from your command line. If instead, you are using a graphical desktop provided by X, you can start the graphical front-end from either the KDE or XFCE menu. | ||
- | The wicd interface | + | Now we can install **//wicd//**, setup the daemon to |
+ | run on system boot-up, and begin using a more friendly application. | ||
- | Optionally, you could manually run wicd-client(1) from a terminal or run dialogue. | ||
- | On the graphical front-end, options for different networks are available via the Preferences button adjacent | + | < |
+ | darkstar:~# installpkg /path/to/ | ||
+ | darkstar:~# chmod +x / | ||
+ | darkstar:~# / | ||
+ | </ | ||
+ | |||
+ | If you're predominately using the console, simply run | ||
+ | **// | ||
+ | instead, you are using a graphical desktop provided by | ||
+ | **//X//**, you can start the graphical front-end | ||
+ | from either the KDE or XFCE menu. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Optionally, you could manually run | ||
+ | **// | ||
+ | dialogue// | ||
+ | |||
+ | |||
+ | On the graphical front-end, options for different networks are | ||
+ | available via the **Preferences** button adjacent | ||
+ | to the ESSID listed. In the terminal client, the same options can be | ||
+ | reached by highlighting the ESSID you wish to use and | ||
+ | pressing the right arrow key, which opens a configuration page for | ||
+ | that network. | ||
====== Chapter Navigation ====== | ====== Chapter Navigation ====== | ||
Line 206: | Line 319: | ||
**Next Chapter: [[slackbook: | **Next Chapter: [[slackbook: | ||
- | ======Sources====== | + | ====== Sources ====== |
- | + | <!-- If you copy information from another source, then specify that source --> | |
- | * Original source: http:// | + | * Original source: |
+ | <!-- Authors are allowed to give credit to themselves! --> | ||
+ | * Originally written by Alan Hicks, Chris Lumens, David Cantrell, Logan Johnson | ||
+ | <!-- * Contrbutions by [[wiki: | ||
+ | <!-- Please do not modify anything below, except adding new tags.--> | ||
+ | <!-- You must also remove the tag-word " | ||
+ | {{tag> |