Additions:

Deletions:

Additions:

==PART 2: WPA encryption.==
PART 2: WPA encryption.
For WPA encryption the "iwconfig" utility cannot be used at all. Instead, the "wpa_supplicant" utility is needed, and this is the utility which is used by Puppy's Network Wizard to configure WPA connections.
Exception:
Ralink drivers in Puppy versions older than ver 4.1 can be set up for WPA encryption with unique "iwpriv" commands. See -
"PART 3: WPA encryption with Ralink devices"
<a class="postlink" target="_blank" href="http://www.murga-linux.com/puppy/viewtopic.php?p=159339#159339">http://www.murga-linux.com/puppy/viewtopic.php?p=159339#159339</a>
wpa_supplicant needs to have a "-D" (driver) parameter specified, depending on which wifi driver is being used;
Compatible drivers using the "hostap" parameter:
hostap
Compatible drivers using the "ipw" parameter:
r8180
r8187
Compatible drivers using the "wext" (generic) parameter:
||acx
ath5k
ath_pci
b43
b43legacy
bcm43xx
ipw2100
ipw2200
ipw3945
iwl3945
||iwl4965
libertas_cs
libertas_sdio
ndiswrapper
p54pci
p54usb
rndis_wlan (Broadcom USB)
rt2400pci
rt2500pci
rt2500usb
rt2860sta
rt2870sta
rt61pci
rt73usb
rtl8180
rtl8187
usb8xxx
zd1211
zd1211b
zd1211rw||
Compatible drivers using the "ralink" parameter:
rt61
rt73
INSTRUCTIONS
Use Geany to modify the WPA configuration file to include your SSID and Personal Security Key (PSK).
Puppy already contains 2 different configuration files;
/etc/network-wizard/wireless/wpa_profiles/wpa_supplicant.conf - for WPA encryption
/etc/network-wizard/wireless/wpa_profiles/wpa_supplicant2.conf - for WPA2 encryption
As an example, let's assume your wifi driver is the ipw2200 (so the -D parameter will be "wext") and this driver has created the network interface "eth1", and your wifi router is set for WPA2 encryption. First you must load your driver if Puppy has not automatically done so already
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">modprobe ipw2200</td> </tr></tbody></table><span class="postbody">
It's often necessary to "bring up" the interface unconfigured
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">ifconfig eth1 up</td> </tr></tbody></table><span class="postbody">
Remove stale wpa_supplicant file if it exists
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">rm /var/run/wpa_supplicant/*</td> </tr></tbody></table><span class="postbody">
Start wpa_supplicant with debugging enabled (-dd) in case of problems
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">wpa_supplicant -i eth1 -D wext -c /etc/network-wizard/wireless/wpa_profiles/wpa_supplicant2.conf -dd</td> </tr></tbody></table><span class="postbody">
wpa_supplicant may take about 30 seconds to negotiate the connection.
Hopefully you will see a connection reported, then you can open a second console and proceed to obtain an IP address (DHCP).
It's possible to background the wpa_supplicant process in order to keep using the same xterminal by adding "-B" to the command
... but do this only once you know that the wpa_supplicant command is successful, because once backgrounded you won't see any error messages.
Now for DHCP with Puppy 3.x and earlier -
That's hyphen, capital i, space, apostrophe, apostrophe (not quotation marks). Thanks to rerwin for this information.
or to obtain a static IP address,
[[HowToWifiFromCommandWEP PART 1 WEP encryption]]

Deletions:

==PART 1: WEP encryption.==
To configure for WPA encryption, see [[HowToWifiFromCommandWPA PART 2]].)
To configure for WEP encryption -
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">iwconfig eth1 essid MY_ESSID
iwconfig eth1 key open 1234567890
iwconfig eth1 mode managed</td> </tr></tbody></table><span class="postbody">
You will often see reference to these 3 parameters, essid/key/mode, being used within a single iwconfig command instead of 3 separate commands, but apparently the configuration is more reliable when the parameters are run separately.
Obviously replace "MY_ESSID" with your SSID, and "1234567890" with your WEP encryption key - as hexadecimal digits.
If you want to use your WEP password (ASCII string) instead of the true WEP hex key, then you must use the s: prefix. In this case the 2nd command would be -
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">iwconfig eth1 key open s:MY_WEP_PASSWORD</td> </tr></tbody></table><span class="postbody">
And if your password contains spaces, you should enclose it in quotation marks.
Most wifi routers use "open" WEP authentication, but it could be "restricted", in which case the 2nd command should be
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">iwconfig eth1 key restricted 1234567890</td> </tr></tbody></table><span class="postbody">
Or if your router has no encryption, the 2nd command should be
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Code:</b></span></td> </tr> <tr> <td class="code">iwconfig eth1 key off</td> </tr></tbody></table><span class="postbody">
Now to obtain an automatic IP address (DHCP)
for Puppy 3.x and earlier -
That's hyphen, capital i, space, apostrophe, apostrophe (not quotation marks). Thanks to rerwin for this information.
Or to obtain a static IP address,
Puppy contains an alternative wifi configuration utility, RutilT. This is more than just a script, it's a full application, and may be useful if the Network Wizard fails, especially at the last point of setup; acquiring an IP address.
But RutilT supports WPA encryption ONLY with Ralink wifi drivers (for which RutilT was originally written) and even then, only the basic WPA/PSK-TKIP variant.</span>
<span class="gensmall"><br/>Edited_times_total<br/></span></td>
[[HowToWifiFromCommandWPA PART 2 WPA encryption]]