Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| wiki:setting_up_wifi [2019/03/13 09:39] – Corrected sudo wicd-start to sudo wicd start Rich | wiki:setting_up_wifi [2024/06/20 20:17] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Easy Way: wicd ====== | + | ===== A No-nonsense, |
| + | All you need to connect to a WiFi hotspot is wpa_supplicant, | ||
| - | If you want to set up wifi with minimum of fuss, just install wicd package (and its dependencies) from the package repository. You will then be able to setup your connection in a user-friendly GUI. | + | Just follow 3 easy steps: |
| - | See http:// | + | |
| - | After installing " | + | * If you have access |
| - | < | + | * Boot your TCL machine and establish a wired connection |
| - | sudo wicd start | + | * Download the wpa_supplicant extension (on x86_64 it's called wpa_supplicant-dbus) and all its dependencies: |
| - | </ | + | * Load the wpa_supplicant extension and its dependencies: |
| - | Then activate | + | |
| - | If you have problems getting wicd to see your wifi card, you may have driver issues. Atheros users can see this [[Network Setup - Atheros Wireless Cards]], but note that tinycore 2.0 and later ships with ath5k and ath9k open source drivers that should handle most Atheros cards. | + | * If you do NOT have access |
| + | * Using a different machine, establish an internet connection then manually download the wpa_supplicant extension (on x86_64 it's called wpa_supplicant-dbus) and all its dependencies from the repository | ||
| + | * Boot your TCL machine | ||
| + | * Load the wpa_supplicant extension | ||
| - | **TIP**: For a system that doesn' | + | Now you are ready to connect to any WiFi hotspot. You can do so manually or use a shell script to help you (e.g., https:// |
| - | **WICD is not available | + | ==== NOTES ==== |
| + | | ||
| + | | ||
| + | | ||
| + | * Despite its name, wpa_supplicant-dbus.tcz does not actually require dbus to be running in order to use wireless. | ||
| + | * These instructions assume you have a wireless card whose firmware is included in the linux kernel or modules (e.g., ath9k). If this is not the case, you also need to download the appropriate firmware extension.\\ Another easy way: wpa_gui | ||
| - | ====== Another easy way: wpa_gui ====== | + | **Note**: As of Tiny Core Linux 4.x you can probably just use the wpa_gui extension from the appbrowser and start the application from wbar. It will automatically start wpa_supplicant and udhcpc for all found wireless devices. |
| - | + | ||
| - | //**Note:** As of **Tiny Core Linux 4.x** you can probably just use the wpa_gui extension from the appbrowser and start the application from wbar. It will automatically start wpa_supplicant and udhcpc for all found wireless devices.// | + | |
| You should configure your network and choose File -> Save Configuration. If you want to automatically restart the WPA wireless connection after reboot, put "/ | You should configure your network and choose File -> Save Configuration. If you want to automatically restart the WPA wireless connection after reboot, put "/ | ||
| - | |||
| - | ---- | ||
| Another way to set up a wireless connection is to use wpa_supplicant with it's associated GUI interface. wpa_supplicant is the IEEE 802.1X/WPA component that is used in the client stations. It implements key negotiation with a WPA Authenticator and it controls the roaming and IEEE 802.11 authentication/ | Another way to set up a wireless connection is to use wpa_supplicant with it's associated GUI interface. wpa_supplicant is the IEEE 802.1X/WPA component that is used in the client stations. It implements key negotiation with a WPA Authenticator and it controls the roaming and IEEE 802.11 authentication/ | ||
| - | wpa_supplicant is designed to be a "daemon" | + | wpa_supplicant is designed to be a //daemon// program that runs in the background and acts as the backend component controlling the wireless connection. wpa_supplicant supports a text-based frontend (wpa_cli) and a GUI (wpa_gui). See http:// |
| - | See http:// | + | |
| Install wpa_supplicant and wpa_gui. Then configure wpa_supplicant for remote control by creating a configuration file (this has to be done only once): | Install wpa_supplicant and wpa_gui. Then configure wpa_supplicant for remote control by creating a configuration file (this has to be done only once): | ||
| - | Create a configuration file "/ | + | Create a configuration file **/ |
| - | < | + | < |
| - | ctrl_interface=/ | + | |
| ctrl_interface_group=staff | ctrl_interface_group=staff | ||
| - | update_config=1 | + | update_config=1</ |
| - | </ | + | |
| - | After creating the configuration file start the wpa_supplicant daemon using the following command | + | It's recommended |
| - | and to have wpa_supplicant start every boot, add this to /opt/ | + | |
| - | < | + | |
| - | wpa_supplicant -Dwext -iwlan0 -c/ | + | |
| - | </ | + | |
| - | Afterwards, all you need to do to connect to various networks is to run wpa_gui from the menu. | + | After creating the configuration file start the wpa_supplicant daemon using the following command and to have wpa_supplicant start every boot, add this to / |
| - | ====== More Advanced Setup: using wireless tools ====== | + | < |
| - | Prerequisites: | + | Replace wlan0 with the name of your wireless card. |
| - | 1. You have a working tinycore system with some support for persistence (a tce directory and either a backup/ | + | Afterwards, all you need to do to connect to various networks is to run wpa_gui from the menu. |
| - | 2. Your wireless | + | ===== More Advanced Setup : Using wireless |
| - | 3. You want to connect to an open access point, WEP or WPA-PSK secured AP (you do care about security don't you?) | + | === Prerequisites === |
| + | - You have a working tinycore system with some support for persistence (ie: A tce directory and either a backup/ | ||
| + | - Your wireless hardware is supported by a driver available in the repo. | ||
| + | - You want to connect to an open access point, WEP or WPA-PSK secured AP (you do care about security don't you?) | ||
| - | ===== Initial Preparation ===== | + | === Initial Preparation === |
| + | |||
| + | 1. Boot tinycore and install the needed wireless packages if you haven' | ||
| + | | wireless_tools.tcz | gives you iwconfig and other tools | | ||
| + | | wireless-`uname -r`-tinycore.tcz | in-kernel wifi drivers | | ||
| + | | wpa-supplicant.tcz | wpa_supplicant tool for negotiating secured access points | | ||
| - | 1. boot tinycore and install the needed wireless packages if you haven' | ||
| - | * wireless_tools.tcz -- gives you iwconfig and other tools | ||
| - | * wireless-`uname -r`-tinycore.tcz -- in-kernel wifi drivers | ||
| - | * wpa-supplicant.tcz (which depends on openssl-0.9.8.tcz) -- wpa_supplicant tool for negotiating secured access points | ||
| If you will be installing to a system that depends on wifi access you may find it easier to pre-download these files and copy them to your tinycore tce directory so that they are installed at boot time (or use tce-load to install them after boot). | If you will be installing to a system that depends on wifi access you may find it easier to pre-download these files and copy them to your tinycore tce directory so that they are installed at boot time (or use tce-load to install them after boot). | ||
| - | 2. Check whether you can see your wireless hardware. in the console run: | + | 2. Check whether you can see your wireless hardware. in the console run: **iwconfig** |
| - | + | ||
| - | ^iwconfig^ | + | |
| - | + | ||
| - | you should see a list of interfaces with some status info. your wireless interface may show up as wlan0 (but maybe ath0 or eth0?). You need to remember the name of this interface as it will be used later | + | |
| - | If you don' | + | You should |
| - | |^modprobe -l | grep ath^| | + | |
| + | If you don't see a connection, you may need to load or install drivers. The **wireless-`uname -r`-tinycore** contains all in-kernel wifi drivers. You can verify the drivers are present using something like (assuming Atheros card): | ||
| + | **modprobe -l < | ||
| you should see the ath9k.ko.gz and ath5k.ko.gz device driver files | you should see the ath9k.ko.gz and ath5k.ko.gz device driver files | ||
| - | verify | + | Verify |
| - | |^lsmod | grep ath^| | + | **lsmod < |
| - | you can use modprobe to temporarily load and unload drivers as needed. For instructions on setting up alternative Atheros drivers, see [[Network Setup - Atheros Wireless Cards]] | + | You can use modprobe to temporarily load and unload drivers as needed. For instructions on setting up alternative Atheros drivers, see Network Setup - Atheros Wireless Cards |
| - | ===== Connecting to an open access point ===== | + | === Connecting to an open access point === |
| - | + | | |
| - | 1. To connect to a particular access point, all you need to do is type in the console | + | |
| - | ^iwconfig *interface* essid *network-id*^ | + | |
| - | + | | |
| - | to search for access points, use the command | + | |
| - | ^iwlist scanning^ | + | |
| - | + | ||
| - | to connect to the nearest access point, just use: | + | |
| - | ^iwconfig *interface* essid any^ | + | |
| - | + | ||
| - | 2. To finalize the connection (getting IP address etc), go to control panel, open the netcardconfig tool. switch eth0 to the name of your interface (e.g. wlan0). Change | + | |
| - | + | ||
| - | Alternately, | + | |
| - | ^udhcpc -i *interface*^ | + | |
| - | + | ||
| - | 3. At this point you should have a working network connection. If it doesn' | + | |
| - | + | ||
| - | 4. If you don't want to have to run step 1 and 2 every time you boot, you can add the command to your / | + | |
| - | + | ||
| - | ===== Connecting to a WPA-PSK secured access point ===== | + | |
| + | === Connecting to a WPA-PSK secured access point === | ||
| Before you start, you need to look up your access point id (ssid) and passphrase (a string). | Before you start, you need to look up your access point id (ssid) and passphrase (a string). | ||
| - | + | * At the command line, run **< | |
| - | 1. At the command line, run | + | * Now create a file in your favorite editor replacing the ssid and psk values below with result from step 1: **ctrl_interface=/ |
| - | ^wpa_passphrase *essid* *passphrase*^ | + | < |
| - | + | ||
| - | For example: | + | |
| - | ^ | + | |
| - | ~$ wpa_passphrase mynetwork mypassphrase | + | |
| network={ | network={ | ||
| - | ssid="mynetwork" | + | |
| - | #psk=" | + | proto=WPA |
| - | psk=f242925f83787084d58101d5eb52485989e2a553983bfe6fc5b8d27fdfa063bd | + | |
| - | } | + | pairwise=TKIP |
| - | ^ | + | group=TKIP |
| + | | ||
| + | }</ | ||
| - | 2. Now create | + | Note: This assumes a fairly conventional WPA-PSK setup. If you need to use other security (e.g. WEP) or are connecting to a more sophisticated network you may have to tweak this file. See the wpa_supplicant manual for more info. (What if you connect to more than one WPA-PSK network? You can add as many network sections to the conf file as needed.) |
| + | save it as / | ||
| - | ^ | + | * to connect to the access point, run in the console: **wpa_supplicant -i*interface* -c/ |
| - | ctrl_interface=/var/run/wpa_supplicant | + | * now to finalize the connection (getting IP address etc), go to control panel, open the netcardconfig tool. switch eth0 to the name of your interface (e.g. wlan0). Change |
| - | network={ | + | Alternately, |
| - | ssid=mynetwork | + | * At this point you should have a working network connection. If it doesn' |
| - | proto=WPA | + | * If you don't want to have to run step 3 and 4 every time you boot, you can add the wpa_supplicant command in line 3 to your / |
| - | key_mgmt=WPA-PSK | + | |
| - | | + | |
| - | group=TKIP | + | |
| - | psk=f242925f83787084d58101d5eb52485989e2a553983bfe6fc5b8d27fdfa063bd | + | |
| - | } | + | |
| - | ^ | + | |
| - | Note that this assumes a fairly conventional WPA-PSK setup. If you need to use other security (e.g. WEP) or are connecting to a more sophisticated network you may have to tweak this file. See the wpa_supplicant manual for more info. (What if you connect to more than one WPA-PSK network -- can add as many network sections to the conf file as needed) | + | === Simple scripts to auto connect to specific networks === |
| - | + | Connect to non-secured access point. | |
| - | save it as / | + | * [[http:// |
| - | + | < | |
| - | 3. to connect to the access point, run in the console: | + | #!/bin/sh |
| - | ^wpa_supplicant -i*interface* -c/ | + | |
| - | + | ||
| - | For diagnostic run this command with debugging option -d | + | |
| - | ^sudo wpa_supplicant -i*interface* -c/ | + | |
| - | Close debugging mode with Ctrl+c. \\ | + | |
| - | You can verify the connection with '' | + | |
| - | Another simple method is watching card LINK diode. Diode shines with constant light, when Adapter is connected to AP. | + | |
| - | + | ||
| - | 4. now to finalize the connection (getting IP address etc), go to control panel, open the netcardconfig tool. switch eth0 to the name of your interface (e.g. wlan0). Change "use DHCP Broadcast?" | + | |
| - | + | ||
| - | Alternately, | + | |
| - | ^udhcpc -i *interface*^ | + | |
| - | + | ||
| - | 5. At this point you should have a working network connection. If it doesn' | + | |
| - | + | ||
| - | 6. If you don't want to have to run step 3 and 4 every time you boot, you can add the wpa_supplicant command in line 3 to your / | + | |
| - | + | ||
| - | ===== Simple scripts to auto connect to specific networks | + | |
| - | + | ||
| - | ==== Connect to non-secured access point. | + | |
| - | + | ||
| - | Script that displays local Access Points to connect to. Only works with unsecured APs. | + | |
| - | + | ||
| - | http:// | + | |
| - | + | ||
| - | ==== Connect to either non-secure or WEP protected access point ==== | + | |
| - | + | ||
| - | NOTE requires editing of shell script to set ESSID (network name) and wep key (set to blank if network is unsecured). | + | |
| - | + | ||
| - | NOTE to set your WEP key using a plain text string (i.e.: not HEX) then put an s: in front of the key. | + | |
| - | ^iwconfig wlan0 key s: | + | |
| - | + | ||
| - | < | + | |
| - Example usage: | - Example usage: | ||
| - | - | ||
| Line 187: | Line 129: | ||
| echo SID ${essid} | echo SID ${essid} | ||
| if [[ -n " | if [[ -n " | ||
| - | then | + | then |
| echo WEPKEY $wepkey | echo WEPKEY $wepkey | ||
| fi | fi | ||
| Line 208: | Line 150: | ||
| pkill udhcpc | pkill udhcpc | ||
| udhcpc -H box -b -i ${wlan} | udhcpc -H box -b -i ${wlan} | ||
| + | </ | ||
| - | |||
| - | </ | ||
