Revision history for HowToWifiFromCommand


Revision [29087]

Last edited on 2013-10-06 15:42:58 by darkcity
Additions:
[[HomePage]] > [[ComponentHowTo Components and HowTos]] > [[Networking]]
Deletions:
[[HomePage]] > [[ComponentHowTo Components and HowTos]] > [[Networking]] > [[HowToWifiFromCommand Wifi Commandline]]

Revision [29083]

Edited on 2013-10-06 15:41:28 by darkcity [page bar]
Additions:
====How to configure wifi from the commandline - Intro====
Deletions:
====How to configure wifi from the commandline - Intro==

Revision [29082]

Edited on 2013-10-06 15:41:06 by darkcity [page bar]
Additions:
====How to configure wifi from the commandline - Intro==
Deletions:
====How to configure wifi from the commandline====
==Intro==

Revision [29078]

Edited on 2013-10-06 15:38:49 by darkcity [page bar]

No Differences

Revision [29077]

Edited on 2013-10-06 15:38:40 by darkcity [page bar]
Additions:
{{include pagesHowToWifi}}
Deletions:
{{include pagesWifi}}

Revision [29076]

Edited on 2013-10-06 15:38:28 by darkcity [page bar]
Additions:
{{include pagesWifi}}
==Related Webpages==
----
==Categories==
CategoryTutorial
CategoryNetworking
Deletions:
{{image url="http://fc04.deviantart.net/fs71/f/2011/239/8/3/puppy_like_by_koulaxizis-d48076t.jpg" title="text" alt="text" height="120"}}
==Also see==

Revision [20748]

Edited on 2012-02-24 13:05:07 by darkcity [remove som more html and intro]
Additions:
==Intro==
**Puppy's Network Wizard** is one of the best in the business. It supports all currently available Linux wifi drivers including the unconventional linux-wlan-ng (prism2) drivers, plus ndiswrapper. And it fully supports WPA and WPA2 encryption via wpa_supplicant, even with the Ralink drivers, which out-of-the-box are not normally compatible with wpa_supplicant.
In a [[http://distrowatch.com/weekly.php?issue=20071008#review DistroWatch review of Puppy 3.00]]
Deletions:
Puppy's Network Wizard is one of the best in the business. It supports all currently available Linux wifi drivers including the unconventional linux-wlan-ng (prism2) drivers, plus ndiswrapper. And it fully supports WPA & WPA2 encryption via wpa_supplicant, even with the Ralink drivers, which out-of-the-box are not normally compatible with wpa_supplicant.
<br/>
<br/>
In a DistroWatch review of Puppy 3.00 <a class="postlink" target="_blank" href="http://distrowatch.com/weekly.php?issue=20071008#review">http://distrowatch.com/weekly.php?issue=20071008#review</a>
<br/>
<br/>""

Revision [20744]

Edited on 2012-02-24 12:56:08 by darkcity [split]
Additions:
Continue to-
[[HowToWifiFromCommandWEP PART 1: WEP encryption.]]
[[HowToWifiFromCommandWPA PART 2: WPA encryption.]]
[[http://www.murga-linux.com/puppy/viewtopic.php?p=159339#159339 PART 3: WPA encryption with Ralink devices (pre-Puppy 4.1 ONLY)]]
Deletions:
PART 1: WEP encryption.
(To configure for WPA encryption, see 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 -
</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 /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d eth1</td> </tr></tbody></table><span class="postbody">
for Puppy 4.0 onwards, the version of dhcpcd is different, thus -
</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 -f /var/lib/dhcpcd/*.info
rm -f /var/run/*.pid
dhcpcd -t 30 -h puppypc -d eth1</td> </tr></tbody></table><span class="postbody">
If this dhcpcd command fails, try it with extra parameters which avoid any use of the new logic for ipv6-compatible Client ID, like this -
</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">dhcpcd -I '' -t 30 -h puppypc -d eth1</td> </tr></tbody></table><span class="postbody">
That's hyphen, capital i, space, apostrophe, apostrophe (not quotation marks). Thanks to rerwin for this information.
Or to obtain a static IP address,
modify /etc/resolv.conf to include your nameservers, then
</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 192.168.0.xx broadcast 192.168.0.255 netmask 255.255.255.0
route add default gw 192.168.0.1 eth1</td> </tr></tbody></table><span class="postbody">
Obviously replace the appropriate IP addresses.
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>

Revision [20741]

Edited on 2012-02-24 12:46:44 by darkcity [split]
Additions:
[[HomePage]] > [[ComponentHowTo Components and HowTos]] > [[Networking]] > [[HowToWifiFromCommand Wifi Commandline]]
Deletions:
[[HomePage]] > [[ComponentHowTo Components and HowTos]] > [[Networking]]

Revision [20720]

Edited on 2012-02-21 14:06:06 by darkcity [correct ifconfig!]
Additions:
%%ifconfig eth1 up%%
Deletions:
%%fconfig eth1 up%%

Revision [20680]

Edited on 2012-02-18 06:06:01 by darkcity [remove some html]
Additions:
<br/>""
~Quote:
~The network wizard requires several steps and clicking back and forth, but it works even with Wi-Fi Protected Access (WPA). I've tested maybe three distros with graphical network configurations that actually work for my chip. It's an amazing accomplishment.
%%lsmod%%
%%ifconfig -a%%
%%iwconfig%%
%%fconfig eth1 up%%
Deletions:
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Quote:</b></span></td> </tr> <tr> <td class="quote">The network wizard requires several steps and clicking back and forth, but it works even with Wi-Fi Protected Access (WPA). I've tested maybe three distros with graphical network configurations that actually work for my chip. It's an amazing accomplishment.</td> </tr></tbody></table><span class="postbody">
</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">lsmod</td> </tr></tbody></table><span class="postbody">
</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 -a</td> </tr></tbody></table><span class="postbody">
</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</td> </tr></tbody></table><span class="postbody">
</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">

Revision [20679]

Edited on 2012-02-18 05:56:03 by darkcity [remove some html]
Additions:
====How to configure wifi from the commandline====
""
Puppy's Network Wizard is one of the best in the business. It supports all currently available Linux wifi drivers including the unconventional linux-wlan-ng (prism2) drivers, plus ndiswrapper. And it fully supports WPA & WPA2 encryption via wpa_supplicant, even with the Ralink drivers, which out-of-the-box are not normally compatible with wpa_supplicant.
<br/>
<br/>
In a DistroWatch review of Puppy 3.00 <a class="postlink" target="_blank" href="http://distrowatch.com/weekly.php?issue=20071008#review">http://distrowatch.com/weekly.php?issue=20071008#review</a>
<br/>
Susan Linton said this -
<br/>
</span><table width="90%" cellspacing="1" cellpadding="3" border="0" align="center"><tbody><tr> <td><span class="genmed"><b>Quote:</b></span></td> </tr> <tr> <td class="quote">The network wizard requires several steps and clicking back and forth, but it works even with Wi-Fi Protected Access (WPA). I've tested maybe three distros with graphical network configurations that actually work for my chip. It's an amazing accomplishment.</td> </tr></tbody></table><span class="postbody">
<br/>
<br/>
But it's worth knowing the commands that operate behind the Wizard, especially if you need to troubleshoot a problem, or you have an unconventional setup.
<br/>
First it's worth knowing what module (driver) is being used for your wifi device. The correct module is NOT determined by the manufacturer of the wifi adaptor, but by the CHIPSET contained within the wifi adaptor.
<br/>
From version 2.12 onwards, Puppy Linux includes EXTENSIVE wifi driver support, including many Linux drivers written by independent development projects not aligned with the official Linux kernel.
<br/>
<br/>
For wifi chipsets not supported by a native Linux driver, Puppy also includes ndiswrapper, which will "wrap" a Windows driver. Obviously, you must supply the Windows driver files.
<br/>
ndiswrapper is a workaround solution, but sometimes it's the ONLY solution.
<br/>
<br/>
Usually, Puppy will automatically detect your wifi device, and load the suitable driver from its "zdrv" compressed driver collection.
<br/>
Run this command to see which modules are currently loaded
<br/>
</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">lsmod</td> </tr></tbody></table><span class="postbody">
<br/>
When a wifi module loads, it creates a network interface, which will be called "eth0" "wlan0" "ra0" "ath0" or "rausb0".
<br/>
But if you also have an ethernet interface, this has probably taken the interface name "eth0" so the wifi interface will be "eth1".
<br/>
First check that your wifi module has created an interface, with these 2 commands
<br/>
</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 -a</td> </tr></tbody></table><span class="postbody">
<br/>
</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</td> </tr></tbody></table><span class="postbody">
<br/>
For the sake of this example, let's assume your wifi interface is "eth1".
<br/>
It's often necessary to "bring up" the interface unconfigured with this command
<br/>
</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">
<br/>
<br/>
PART 1: WEP encryption.
<br/>
(To configure for WPA encryption, see PART 2.)
<br/>
<br/>
To configure for WEP encryption -
<br/>
</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
<br/>
iwconfig eth1 key open 1234567890
<br/>
iwconfig eth1 mode managed</td> </tr></tbody></table><span class="postbody">
<br/>
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.
<br/>
Obviously replace "MY_ESSID" with your SSID, and "1234567890" with your WEP encryption key - as hexadecimal digits.
<br/>
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 -
<br/>
</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">
<br/>
And if your password contains spaces, you should enclose it in quotation marks.
<br/>
<br/>
Most wifi routers use "open" WEP authentication, but it could be "restricted", in which case the 2nd command should be
<br/>
</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">
<br/>
Or if your router has no encryption, the 2nd command should be
<br/>
</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">
<br/>
<br/>
Now to obtain an automatic IP address (DHCP)
<br/>
for Puppy 3.x and earlier -
<br/>
</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 /etc/dhcpc/*.pid
<br/>
dhcpcd -t 30 -h puppypc -d eth1</td> </tr></tbody></table><span class="postbody">
<br/>
<br/>
for Puppy 4.0 onwards, the version of dhcpcd is different, thus -
<br/>
</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 -f /var/lib/dhcpcd/*.info
<br/>
rm -f /var/run/*.pid
<br/>
dhcpcd -t 30 -h puppypc -d eth1</td> </tr></tbody></table><span class="postbody">
<br/>
<br/>
If this dhcpcd command fails, try it with extra parameters which avoid any use of the new logic for ipv6-compatible Client ID, like this -
<br/>
</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">dhcpcd -I '' -t 30 -h puppypc -d eth1</td> </tr></tbody></table><span class="postbody">
<br/>
That's hyphen, capital i, space, apostrophe, apostrophe (not quotation marks). Thanks to rerwin for this information.
<br/>
<br/>
Or to obtain a static IP address,
<br/>
modify /etc/resolv.conf to include your nameservers, then
<br/>
</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 192.168.0.xx broadcast 192.168.0.255 netmask 255.255.255.0
<br/>
route add default gw 192.168.0.1 eth1</td> </tr></tbody></table><span class="postbody">
<br/>
Obviously replace the appropriate IP addresses.
<br/>
<br/>
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.
<br/>
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>
""
[[http://www.murga-linux.com/puppy/viewtopic.php?t=22469 How to configure wifi from the commandline thread]]
Deletions:
==== Networking Index ====
Information about networking in Puppy Linux.
General Information
~-[[FileTransferClient File Transfer Client]]
Software
~[[SoftwareInternet Internet Software]]
~[[SoftwareNetwork Network Software]]
~[[HowToWifiFromCommand]]

Revision [20678]

The oldest known version of this page was created on 2012-02-18 05:53:19 by darkcity [remove some html]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki